API Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 6327
[SUPERSEDED]

Routing Bridges (RBridges): Adjacency

Metadata

Publisher
IETF
Doc Type
Standard
Pages
26
Abstract
The IETF TRILL (TRansparent Interconnection of Lots of Links) protocol provides optimal pair-wise data forwarding without configuration, 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 Routing Bridges (RBridges). TRILL supports multi-access LAN (Local Area Network) links that can have multiple end stations and RBridges attached. This document describes four aspects of the TRILL LAN Hello protocol used on such links, particularly adjacency, designated RBridge selection, and MTU (Maximum Transmission Unit) and pseudonode procedures, with state machines. There is no change for IS-IS point-to-point Hellos used on links configured as point-to-point in TRILL. [STANDARDS-TRACK]
Publication Date
2011-07-01
Status Note
Proposed Standard
DOI
10.17487/RFC6327
Link
https://doi.org/10.17487/RFC6327
Author(s)
Donald E. Eastlake 3rd
Radia Perlman
Anoop Ghanwani
Dinesh G. Dutt
Vishwas Manral
Keyword(s)
TRILL, Adjacency
Latest version of IETF RFC 6327

Document Versions — IETF RFC 6327

  • ▶ IETF RFC 6327 (2011-07-01)
    THIS DOC [SUPERSEDED] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • IEEE.STD802.1AX.2008 — 802.1AX EXTERNAL
  • IEEE.STD802.1Q.2005 — 802.1Q EXTERNAL
  • From www.t11.org discussion of "FCoE Max Size" generated from T11/09-251v1, 04/27/2009, "FCoE frame or FCoE PDU". EXTERNAL
  • RFC3719 — RFC3719 EXTERNAL
  • IETF RFC 5880 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC6327.json

Amends:
IETF RFC 6325 [Active*]
Amended by:
IETF RFC 7180 [Superseded*]
Superseded by:
IETF RFC 7177 [Active*]

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 6327, Routing Bridges (RBridges): Adjacency. Available at https://doi.org/10.17487/RFC6327
Snippet:
IETF RFC 6327, Routing Bridges (RBridges): Adjacency. Available at https://doi.org/10.17487/RFC6327

HTML (ISO 690 compliant)

Preview:
IETF RFC 6327, Routing Bridges (RBridges): Adjacency. Available at https://doi.org/10.17487/RFC6327
Snippet:
<span class="citation"><cite>IETF RFC 6327</cite>, Routing Bridges (RBridges): Adjacency. Available at <a href="https://doi.org/10.17487/RFC6327" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6327</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 6327, Routing Bridges (RBridges): Adjacency
doi: 10.17487/RFC6327
url: https://doi.org/10.17487/RFC6327
Snippet:
<li>
<cite id="bib-rfc6327">IETF RFC 6327</cite>, Routing Bridges (RBridges): Adjacency
<span class="doi">10.17487/RFC6327</span>
</li>

Referenced By