RFC 3036: LDP Specification
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5036.
Current version: RFC 5036 — LDP Specification
In plain English — editorial summary, not part of the RFC
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
- RFC3036
- Published
- January 2001
- Authors
- L. Andersson; P. Doolan; N. Feldman; A. Fredette; B. Thomas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 132
- Also known as
- —
- Obsoleted by:
- RFC 5036
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3037LDP ApplicabilityCurrent
January 2001
- RFC 3213Applicability Statement for CR-LDPCurrent
January 2002
- RFC 3215LDP State MachineCurrent
January 2002
- RFC 3210Applicability Statement for Extensions to RSVP for LSP-TunnelsCurrent
December 2001
- RFC 4364BGP/MPLS IP Virtual Private Networks (VPNs)Updated
February 2006
- RFC 2966Domain-wide Prefix Distribution with Two-Level IS-ISObsoleted
October 2000
- RFC 3214LSP Modification Using CR-LDPCurrent
January 2002
- RFC 2858Multiprotocol Extensions for BGP-4Obsoleted
June 2000
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?