RFC 3212: Constraint-Based LSP Setup using LDP
In plain English — editorial summary, not part of the RFC
This document specifies mechanisms and TLVs (Type/Length/Value) for support of CR-LSPs (constraint-based routed Label Switched Path) using LDP (Label Distribution Protocol). [STANDARDS-TRACK]
Document record
- Document ID
- RFC3212
- Published
- January 2002
- Authors
- B. Jamoussi; L. Andersson; R. Callon; R. Dantu; L. Wu; P. Doolan; T. Worster; N. Feldman; A. Fredette; M. Girish; E. Gray; J. Heinanen; T. Kilty; A. Malis
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 42
- Also known as
- —
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.
- RFC 3038VCID Notification over ATM link for LDPUpdated
January 2001
- RFC 3035MPLS using LDP and ATM VC SwitchingCurrent
January 2001
- RFC 3478Graceful Restart Mechanism for Label Distribution ProtocolCurrent
February 2003
- RFC 3479Fault Tolerance for the Label Distribution Protocol (LDP)Current
February 2003
- RFC 3815Definitions of Managed Objects for the Multiprotocol Label Switching (MPLS), Label Distribution Protocol (LDP)Current
June 2004
- RFC 3988Maximum Transmission Unit Signalling Extensions for the Label Distribution ProtocolCurrent
February 2005
- RFC 5443LDP IGP SynchronizationUpdated
March 2009
- RFC 5561LDP CapabilitiesCurrent
July 2009
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?