Routing Bridges (RBridges): Appointed Forwarders
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 15
- Abstract
- The IETF TRILL (TRansparent Interconnection of Lots of Links) protocol provides least cost pair-wise data forwarding without configuration in multi-hop networks with arbitrary topology, safe forwarding even during periods of temporary loops, and support for multipathing of both unicast and multicast traffic. TRILL accomplishes this by using IS-IS (Intermediate System to Intermediate System) link state routing and by encapsulating traffic using a header that includes a hop count. Devices that implement TRILL are called "RBridges" (Routing Bridges). TRILL supports multi-access LAN (Local Area Network) links that can have multiple end stations and RBridges attached. Where multiple RBridges are attached to a link, native traffic to and from end stations on that link is handled by a subset of those RBridges called "Appointed Forwarders", with the intent that native traffic in each VLAN (Virtual LAN) be handled by at most one RBridge. The purpose of this document is to improve the documentation of the Appointed Forwarder mechanism; thus, it updates RFC 6325. [STANDARDS-TRACK]
- Publication Date
- 2011-11-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC6439- Link
- https://doi.org/10.17487/RFC6439
- Author(s)
- Radia PerlmanDonald E. Eastlake 3rdYizhou LiAyan Banerjeefangwei hu
- Keyword(s)
- TRILL
Latest version of IETF RFC 6439
Document Versions — IETF RFC 6439
-
▶ IETF RFC 6439 (2011-11-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Normative Reference(s)
- IEEE.STD802.1Q.2011 — 802.1Q EXTERNAL
- ISO.10589.2002 — 1 EXTERNAL
- IETF RFC 1195 [Active*]
- IETF RFC 2119 [Active*]
- IETF RFC 6325 [Active*]
- RFC6326 — RFC6326 EXTERNAL
- IETF RFC 6327 [Superseded*]
Bibliographic Reference(s)
- Perlman, R., Dutt, D., Banerjee, A., Rijhsinghani, A., and D. Eastlake, "RBridges: Campus VLAN and Priority Regions", Work in Progress, October 2011. Appendix. VLAN Inhibition Example EXTERNAL
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6439.json
Amends:
IETF RFC 6325 [Active*]
Amended by:
IETF RFC 7180 [Superseded*]
Superseded by:
IETF RFC 8139 [Active*]
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 6439, Routing Bridges (RBridges): Appointed Forwarders. Available at https://doi.org/10.17487/RFC6439
Snippet:
IETF RFC 6439, Routing Bridges (RBridges): Appointed Forwarders. Available at https://doi.org/10.17487/RFC6439
HTML (ISO 690 compliant)
Preview:
IETF RFC 6439, Routing Bridges (RBridges): Appointed Forwarders. Available at https://doi.org/10.17487/RFC6439
Snippet:
<span class="citation"><cite>IETF RFC 6439</cite>, Routing Bridges (RBridges): Appointed Forwarders. Available at <a href="https://doi.org/10.17487/RFC6439" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6439</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6439, Routing Bridges (RBridges): Appointed Forwarders
doi: 10.17487/RFC6439
url: https://doi.org/10.17487/RFC6439
doi: 10.17487/RFC6439
url: https://doi.org/10.17487/RFC6439
Snippet:
<li> <cite id="bib-rfc6439">IETF RFC 6439</cite>, Routing Bridges (RBridges): Appointed Forwarders <span class="doi">10.17487/RFC6439</span> </li>
Referenced By
- IETF RFC 7172 [Active*]
- IETF RFC 7177 [Active*]
- IETF RFC 7180 [Superseded*]
- IETF RFC 7780 [Active*]
- IETF RFC 7783 [Active*]
- IETF RFC 8139 [Active*]