RFC 4972: Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh Membership
In plain English — editorial summary, not part of the RFC
The setup of a full mesh of Multi-Protocol Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths (LSP) among a set of Label Switch Routers (LSR) is a common deployment scenario of MPLS Traffic Engineering either for bandwidth optimization, bandwidth guarantees or fast rerouting with MPLS Fast Reroute. Such deployment may require the configuration of a potentially large number of TE LSPs (on the order of the square of the number of LSRs). This document specifies Interior Gateway Protocol (IGP) routing extensions for Intermediate System-to-Intermediate System (IS-IS) and Open Shortest Path First (OSPF) so as to provide an automatic discovery of the set of LSRs members of a mesh in order to automate the creation of such mesh of TE LSPs. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4972
- Published
- July 2007
- Authors
- JP. Vasseur; JL. Leroux; S. Yasukawa; S. Previdi; P. Psenak; P. Mabbey
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4726A Framework for Inter-Domain Multiprotocol Label Switching Traffic EngineeringCurrent
November 2006
- RFC 4920Crankback Signaling Extensions for MPLS and GMPLS RSVP-TECurrent
July 2007
- RFC 4201Link Bundling in MPLS Traffic Engineering (TE)Current
October 2005
- RFC 3988Maximum Transmission Unit Signalling Extensions for the Label Distribution ProtocolCurrent
February 2005
- RFC 6571Loop-Free Alternate (LFA) Applicability in Service Provider (SP) NetworksCurrent
June 2012
- RFC 3359Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate SystemCurrent
August 2002
- RFC 7917Advertising Node Administrative Tags in IS-ISCurrent
July 2016
- RFC 8099OSPF Topology-Transparent ZoneCurrent
February 2017
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?