Skip to main content

LDP Applicability

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3037.
Authors Bob Thomas , Eric Gray
Last updated 2020-01-21 (Latest revision 2000-08-07)
RFC stream Internet Engineering Task Force (IETF)
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state RFC 3037 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3037

        Title:      LDP Applicability
        Author(s):  B. Thomas, E. Gray
        Status:     Standards Track
        Date:       January 2001
        Pages:      7
        Characters: 13601
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-mpls-ldp-applic-02.txt


Multiprotocol Label Switching (MPLS) is a method for forwarding
packets that uses short, fixed-length values carried by packets,
called labels, to determine packet nexthops.  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
describes the applicability of a set of such procedures called LDP
(for Label Distribution Protocol) by which LSRs distribute labels to
support MPLS forwarding along normally routed paths.

This document is a product of the Multiprotocol Label Switching
Working Group of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.