RFC 5036: LDP Specification
In plain English — editorial summary, not part of the RFC
The architecture for Multiprotocol Label Switching (MPLS) is described in RFC 3031. A fundamental concept in MPLS is that two Label Switching Routers (LSRs) must agree on the meaning of the labels used to forward traffic between and through them. This common understanding is achieved by using a set of procedures, called a label distribution protocol, by which one LSR informs another of label bindings it has made. This document defines a set of such procedures called LDP (for Label Distribution Protocol) by which LSRs distribute labels to support MPLS forwarding along normally routed paths. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5036
- Published
- October 2007
- Authors
- L. Andersson; I. Minei; B. Thomas
- Status
- DRAFT STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 135
- Also known as
- —
- Obsoletes:
- RFC 3036
Topics
Referenced by
4 later RFCs formally update or obsolete part of this document.
- RFC 6720The Generalized TTL Security Mechanism (GTSM) for the Label Distribution Protocol (LDP)Updated
August 2012
- RFC 6790The Use of Entropy Labels in MPLS ForwardingUpdated
November 2012
- RFC 7358Label Advertisement Discipline for LDP Forwarding Equivalence Classes (FECs)Current
October 2014
- RFC 7552Updates to LDP for IPv6Current
June 2015
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3215LDP State MachineCurrent
January 2002
- RFC 3213Applicability Statement for CR-LDPCurrent
January 2002
- RFC 3037LDP ApplicabilityCurrent
January 2001
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
- RFC 3210Applicability Statement for Extensions to RSVP for LSP-TunnelsCurrent
December 2001
- RFC 4456BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)Updated
April 2006
- RFC 4223Reclassification of RFC 1863 to HistoricCurrent
October 2005
- RFC 6041Forwarding and Control Element Separation (ForCES) Applicability StatementCurrent
October 2010
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?