RFC 6329: IS-IS Extensions Supporting IEEE 802.1aq Shortest Path Bridging
In plain English — editorial summary, not part of the RFC
802.1aq Shortest Path Bridging (SPB) has been standardized by the IEEE as the next step in the evolution of the various spanning tree and registration protocols. 802.1aq allows for true shortest path forwarding in a mesh Ethernet network context utilizing multiple equal cost paths. This permits it to support much larger Layer 2 topologies, with faster convergence, and vastly improved use of the mesh topology. Combined with this is single point provisioning for logical connectivity membership, which includes point-to-point, point-to-multipoint, and multipoint-to-multipoint variations. This memo documents the IS-IS changes required to support this IEEE protocol and provides some context and examples. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6329
- Published
- April 2012
- Authors
- D. Fedyk; P. Ashwood-Smith; D. Allan; A. Bragg; P. Unbehagen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 37
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7813IS-IS Path Control and ReservationCurrent
June 2016
- RFC 6327Routing Bridges (RBridges): AdjacencyObsoleted
July 2011
- RFC 6326Transparent Interconnection of Lots of Links (TRILL) Use of IS-ISObsoleted
July 2011
- RFC 6325Routing Bridges (RBridges): Base Protocol SpecificationUpdated
July 2011
- RFC 6344Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS)Current
August 2011
- RFC 6310Pseudowire (PW) Operations, Administration, and Maintenance (OAM) Message MappingCurrent
July 2011
- RFC 6348Requirements for Point-to-Multipoint Extensions to the Label Distribution ProtocolCurrent
September 2011
- RFC 6307Encapsulation Methods for Transport of Fibre Channel Traffic over MPLS NetworksCurrent
April 2012
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?