idnits 2.17.1 draft-ietf-mpls-ldp-11.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 3036 5 Title: LDP Specification 6 Author(s): L. Andersson, P. Doolan, N. Feldman, A. Fredette, 7 B. Thomas 8 Status: Standards Track 9 Date: January 2001 10 Mailbox: loa.andersson@nortelnetworks.com, 11 pdoolan@ennovatenetworks.com, nkf@us.ibm.com, 12 fredette@photonex.com, rhthomas@cisco.com 13 Pages: 132 14 Characters: 274855 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-mpls-ldp-11.txt 19 URL: ftp://ftp.isi.edu/in-notes/rfc3036.txt 21 The architecture for Multi Protocol Label Switching (MPLS) is 22 described in RFC 3031. A fundamental concept in MPLS is that two 23 Label Switching Routers (LSRs) must agree on the meaning of the labels 24 used to forward traffic between and through them. This common 25 understanding is achieved by using a set of procedures, called a label 26 distribution protocol, by which one LSR informs another of label 27 bindings it has made. This document defines a set of such procedures 28 called LDP (for Label Distribution Protocol) by which LSRs distribute 29 labels to support MPLS forwarding along normally routed paths. 31 This document is a product of the Multiprotocol Label Switching 32 Working Group of the IETF. 34 This is now a Proposed Standard Protocol. 36 This document specifies an Internet standards track protocol for 37 the Internet community, and requests discussion and suggestions 38 for improvements. Please refer to the current edition of the 39 "Internet Official Protocol Standards" (STD 1) for the 40 standardization state and status of this protocol. Distribution 41 of this memo is unlimited. 43 This announcement is sent to the IETF list and the RFC-DIST list. 44 Requests to be added to or deleted from the IETF distribution list 45 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 46 added to or deleted from the RFC-DIST distribution list should 47 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 49 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 50 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 51 help: ways_to_get_rfcs. For example: 53 To: rfc-info@RFC-EDITOR.ORG 54 Subject: getting rfcs 56 help: ways_to_get_rfcs 58 Requests for special distribution should be addressed to either the 59 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 60 specifically noted otherwise on the RFC itself, all RFCs are for 61 unlimited distribution.echo 62 Submissions for Requests for Comments should be sent to 63 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 64 Authors, for further information.