Skip to main content

Constraint-Based LSP Setup using LDP

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 3212.
Authors Andrew G. Malis , Tom Worster , Loa Andersson , Ross Callon , Liwen Wu , Timothy Kilty, Dr. Muckai K. Girish , Dr. Andre N. Fredette , Dr. Juha Heinanen , Paul Doolan , Ram Dantu , Nancy Feldman , Eric Gray , Bilel Jamoussi
Last updated 2013-03-02 (Latest revision 2001-11-29)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Became RFC 3212 (Proposed Standard)
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 3212

        Title:      Constraint-Based LSP Setup using LDP
        Author(s):  B. Jamoussi, Editor, 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:     Standards Track
        Date:       January 2002
        Pages:      42
        Characters: 87591
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-mpls-cr-ldp-06.txt


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).

This specification proposes an end-to-end setup mechanism of a CR-LSP
initiated by the ingress LSR (Label Switching Router).  We also
specify mechanisms to provide means for reservation of resources
using LDP.

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

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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.