RFC 5037: Experience with the Label Distribution Protocol (LDP)
In plain English — editorial summary, not part of the RFC
The purpose of this memo is to document how some of the requirements specified in RFC 1264 for advancing protocols developed by working groups within the IETF Routing Area to Draft Standard have been satisfied by LDP (Label Distribution Protocol). Specifically, this report documents operational experience with LDP, requirement 5 of section 5.0 in RFC 1264. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5037
- Published
- October 2007
- Authors
- L. Andersson; I. Minei; B. Thomas
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 7
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5036LDP SpecificationUpdated
October 2007
- RFC 5038The Label Distribution Protocol (LDP) Implementation Survey ResultsCurrent
October 2007
- RFC 5029Definition of an IS-IS Link Attribute Sub-TLVUpdated
September 2007
- RFC 5059Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM)Updated
January 2008
- RFC 5015Bidirectional Protocol Independent Multicast (BIDIR-PIM)Updated
October 2007
- RFC 5060Protocol Independent Multicast MIBCurrent
January 2008
- RFC 5063Extensions to GMPLS Resource Reservation Protocol (RSVP) Graceful RestartCurrent
October 2007
- RFC 5065Autonomous System Confederations for BGPUpdated
August 2007
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?