metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 6325: Routing Bridges (RBridges): Base Protocol Specification

Still current, but amended. Parts of this document are changed or extended by RFC 6327, RFC 6439, RFC 7172, RFC 7177, RFC 7179, RFC 7180, RFC 7357, RFC 7455, RFC 7780, RFC 7783, RFC 8139, RFC 8249, RFC 8361, RFC 8377. Read both.

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

Routing Bridges (RBridges) provide optimal pair-wise forwarding without configuration, safe forwarding even during periods of temporary loops, and support for multipathing of both unicast and multicast traffic. They achieve these goals using IS-IS routing and encapsulation of traffic with a header that includes a hop count. RBridges are compatible with previous IEEE 802.1 customer bridges as well as IPv4 and IPv6 routers and end nodes. They are as invisible to current IP routers as bridges are and, like routers, they terminate the bridge spanning tree protocol. The design supports VLANs and the optimization of the distribution of multi-destination frames based on VLAN ID and based on IP-derived multicast groups. It also allows unicast forwarding tables at transit RBridges to be sized according to the number of RBridges (rather than the number of end nodes), which allows their forwarding tables to be substantially smaller than in conventional customer bridges. [STANDARDS-TRACK]

Document record

Document ID
RFC6325
Published
July 2011
Authors
R. Perlman; D. Eastlake 3rd; D. Dutt; S. Gai; A. Ghanwani
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
99
Also known as
—
Updated by:
RFC 6327, RFC 6439, RFC 7172, RFC 7177, RFC 7179, RFC 7180, RFC 7357, RFC 7455, RFC 7780, RFC 7783, RFC 8139, RFC 8249, RFC 8361, RFC 8377

Topics

Referenced by

14 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/6325-routing-bridges-rbridges-base-protocol-specification