RFC 3480: Signalling Unnumbered Links in CR-LDP (Constraint-Routing Label Distribution Protocol)
In plain English — editorial summary, not part of the RFC
Current signalling used by Multi-Protocol Label Switching Traffic Engineering (MPLS TE) does not provide support for unnumbered links. This document defines procedures and extensions to Constraint-Routing Label Distribution Protocol (CR-LDP), one of the MPLS TE signalling protocols that are needed in order to support unnumbered links. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3480
- Published
- February 2003
- Authors
- K. Kompella; Y. Rekhter; A. Kullberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3612Applicability Statement for Restart Mechanisms for the Label Distribution Protocol (LDP)Current
September 2003
- RFC 3812Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)Current
June 2004
- RFC 3785Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) MetricCurrent
May 2004
- RFC 3479Fault Tolerance for the Label Distribution Protocol (LDP)Current
February 2003
- RFC 3477Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE)Updated
February 2003
- RFC 3811Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) ManagementUpdated
June 2004
- RFC 3814Multiprotocol Label Switching (MPLS) Forwarding Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) Management Information Base (MIB)Current
June 2004
- RFC 3815Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)Current
June 2004
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?