idnits 2.17.1 draft-ietf-mpls-cr-ldp-06.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3212 5 Title: Constraint-Based LSP Setup using LDP 6 Author(s): B. Jamoussi, Editor, L. Andersson, 7 R. Callon, R. Dantu, L. Wu, P. Doolan, T. Worster, 8 N. Feldman, A. Fredette, M. Girish, E. Gray, 9 J. Heinanen, T. Kilty, A. Malis 10 Status: Standards Track 11 Date: January 2002 12 Mailbox: Jamoussi@nortelnetworks.com, 13 loa.andersson@utfors.se, 14 rcallon@juniper.net, 15 rdantu@netrake.com, liwwu@cisco.com, 16 pdoolan@acm.org, 17 fsb@thefsb.org, Nkf@us.ibm.com, 18 afredette@charter.net, muckai@atoga.com, 19 eric.gray@sandburst.com, 20 jh@song.fi, tim-kilty@mediaone.net, 21 Andy.Malis@vivacenetworks.com 22 Pages: 42 23 Characters: 87591 24 Updates/Obsoletes/SeeAlso: None 26 I-D Tag: draft-ietf-mpls-cr-ldp-06.txt 28 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3212.txt 30 This document specifies mechanisms and TLVs (Type/Length/Value) for 31 support of CR-LSPs (constraint-based routed Label Switched Path) 32 using LDP (Label Distribution Protocol). 34 This specification proposes an end-to-end setup mechanism of a CR-LSP 35 initiated by the ingress LSR (Label Switching Router). We also 36 specify mechanisms to provide means for reservation of resources 37 using LDP. 39 This document is a product of the Multiprotocol Label Switching 40 Working Group of the IETF. 42 This is now a Proposed Standard Protocol. 44 This document specifies an Internet standards track protocol for 45 the Internet community, and requests discussion and suggestions 46 for improvements. Please refer to the current edition of the 47 "Internet Official Protocol Standards" (STD 1) for the 48 standardization state and status of this protocol. Distribution 49 of this memo is unlimited. 51 This announcement is sent to the IETF list and the RFC-DIST list. 52 Requests to be added to or deleted from the IETF distribution list 53 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 54 added to or deleted from the RFC-DIST distribution list should 55 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 57 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 58 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 59 help: ways_to_get_rfcs. For example: 61 To: rfc-info@RFC-EDITOR.ORG 62 Subject: getting rfcs 64 help: ways_to_get_rfcs 66 Requests for special distribution should be addressed to either the 67 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 68 specifically noted otherwise on the RFC itself, all RFCs are for 69 unlimited distribution.echo 70 Submissions for Requests for Comments should be sent to 71 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 72 Authors, for further information.