Routing Bridges : Adjacency
RFC 6327, “Routing Bridges : Adjacency”, is a Proposed Standard document published in July 2011 by D. Eastlake 3rd, R. Perlman, A. Ghanwani, D. Dutt, V. Manral. It updates RFC 6325. It has since been updated by RFC 7180. It has been obsoleted by RFC 7177 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6327 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6326 Transparent Interconnection of Lots of Links Use of IS-IS
- RFC 6328 IANA Considerations for Network Layer Protocol Identifiers
- RFC 6325 Routing Bridges : Base Protocol Specification
- RFC 6324 Routing Loop Attack Using IPv6 Automatic Tunnels: Problem Statement and Proposed Mitigations
- RFC 6330 RaptorQ Forward Error Correction Scheme for Object Delivery
- RFC 6323 Sender RTT Estimate Option for the Datagram Congestion Control Protocol
- RFC 6331 Moving DIGEST-MD5 to Historic
- RFC 6322 Datatracker States and Annotations for the IAB, IRTF, and Independent Submission Streams