metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 6327: Routing Bridges (RBridges): Adjacency

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7177.

Current version: RFC 7177 — Transparent Interconnection of Lots of Links (TRILL): Adjacency

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC6327
Published
July 2011
Authors
D. Eastlake 3rd; R. Perlman; A. Ghanwani; D. Dutt; V. Manral
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
26
Also known as
—
Obsoleted by:
RFC 7177
Updates:
RFC 6325
Updated by:
RFC 7180

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6327-routing-bridges-rbridges-adjacency