Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 45
- Abstract
- The IETF Transparent Interconnection of Lots of Links (TRILL) protocol provides optimal pair-wise data frame forwarding without configuration in multi-hop networks with arbitrary topology and link technology; it also provides support for multipathing of both unicast and multicast traffic. This document specifies the data formats and code points for the IS-IS extensions to support TRILL. These data formats and code points may also be used by technologies other than TRILL. This document obsoletes RFC 6326.
- Publication Date
- 2014-05-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC7176- Link
- https://doi.org/10.17487/RFC7176
- Author(s)
- Donald E. Eastlake 3rdTissa SenevirathneAnoop GhanwaniDinesh DuttAyan Banerjee
- Keyword(s)
- Affinity, Multicast, Multi-Topology, VLAN
Latest version of IETF RFC 7176
Document Versions — IETF RFC 7176
-
▶ IETF RFC 7176 (2014-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- ISO.10589.2002 — 1 EXTERNAL
- IETF RFC 1195 [Active*]
- IETF RFC 1982 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 4971 [Superseded*]
- IETF RFC 5120 [Active*]
- IETF RFC 5226 [Superseded*]
- IETF RFC 5305 [Active*]
- IETF RFC 6165 [Active*]
- IETF RFC 6325 [Active*]
- IETF RFC 6328 [Active*]
- IETF RFC 6329 [Active*]
- IETF RFC 6439 [Superseded*]
- IETF RFC 7172 [Active*]
- IETF RFC 7177 [Active*]
- IETF RFC 7178 [Active*]
- IETF RFC 7179 [Active*]
- IETF RFC 7180 [Superseded*]
Bibliographic Reference(s)
- Zhang, M. Senevirathne, T., Pathangi, J., Banerjee, A., and A. Ghanwani, "TRILL Resilient Distribution Trees", Work in Progress, December 2013. EXTERNAL
- Senevirathne, T., Pathangi, J., and J. Hudson, "Coordinated Multicast Trees (CMT) for TRILL", Work in Progress, April 2014. EXTERNAL
- Perlman, R., Eastlake 3rd, D., Ghanwani, A., and H. Zhai, "Flexible Multilevel TRILL (Transparent Interconnection of Lots of Links)", Work in Progress, January 2014. EXTERNAL
- IETF RFC 5304 [Active*]
- IETF RFC 5310 [Active*]
- IETF RFC 6039 [Active*]
- IETF RFC 6326 [Superseded*]
- IETF RFC 7042 [Superseded*]
- IETF RFC 7175 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7176.json
Supersedes:
IETF RFC 6326 [Superseded*]
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7176, Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS. Available at https://doi.org/10.17487/RFC7176
Snippet:
IETF RFC 7176, Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS. Available at https://doi.org/10.17487/RFC7176
HTML (ISO 690 compliant)
Preview:
IETF RFC 7176, Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS. Available at https://doi.org/10.17487/RFC7176
Snippet:
<span class="citation"><cite>IETF RFC 7176</cite>, Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS. Available at <a href="https://doi.org/10.17487/RFC7176" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7176</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7176, Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
doi: 10.17487/RFC7176
url: https://doi.org/10.17487/RFC7176
doi: 10.17487/RFC7176
url: https://doi.org/10.17487/RFC7176
Snippet:
<li> <cite id="bib-rfc7176">IETF RFC 7176</cite>, Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS <span class="doi">10.17487/RFC7176</span> </li>
Referenced By
- IETF draft-eastlake-trill-group-keying-00 [Active*]
- IETF RFC 7172 [Active*]
- IETF RFC 7177 [Active*]
- IETF RFC 7178 [Active*]
- IETF RFC 7179 [Active*]
- IETF RFC 7180 [Superseded*]
- IETF RFC 7356 [Active*]
- IETF RFC 7357 [Active*]
- IETF RFC 7379 [Active*]
- IETF RFC 7455 [Active*]
- IETF RFC 7780 [Active*]
- IETF RFC 7781 [Active*]
- IETF RFC 7782 [Active*]
- IETF RFC 7783 [Active*]
- IETF RFC 7978 [Active*]
- IETF RFC 8139 [Active*]
- IETF RFC 8249 [Active*]
- IETF RFC 8361 [Active*]
- IETF RFC 8377 [Active*]