Internet DRAFT - draft-ietf-mpls-crldp-applic
draft-ietf-mpls-crldp-applic
A new Request for Comments is now available in online RFC libraries.
RFC 3213
Title: Applicability Statement for CR-LDP
Author(s): J. Ash, M. Girish, E. Gray, B. Jamoussi, G. Wright
Status: Informational
Date: January 2002
Mailbox: gash@att.com, eric.gray@sandburst.com,
gwright@nortelnetworks.com, muckai@atoga.com,
Jamoussi@nortelnetworks.com
Pages: 7
Characters: 14489
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-crldp-applic-01.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3213.txt
This document discusses the applicability of Constraint-Based
LSP Setup using LDP. It discusses possible network applications,
extensions to Label Distribution Protocol (LDP) required to implement
constraint-based routing, guidelines for deployment and known
limitations of the protocol. This document is a prerequisite to
advancing CR-LDP on the standards track.
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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
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.