idnits 2.17.1 draft-ietf-mpls-vcid-atm-05.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 3038 5 Title: VCID Notification over ATM link for LDP 6 Author(s): K. Nagami, Y. Katsube, N. Demizu, H. Esaki, 7 P. Doolan 8 Status: Standards Track 9 Date: January 2001 10 Mailbox: ken.nagami@toshiba.co.jp, 11 demizu@dd.iij4u.or.jp, hiroshi@wide.ad.jp, 12 yasuhiro.katsube@toshiba.co.jp, 13 pdoolan@ennovatenetworks.com 14 Pages: 19 15 Characters: 39134 16 Updates/Obsoletes/SeeAlso: None 18 I-D Tag: draft-ietf-mpls-vcid-atm-05.txt 20 URL: ftp://ftp.isi.edu/in-notes/rfc3038.txt 22 The Asynchronous Transfer Mode Label Switching Router (ATM-LSR) is one 23 of the major applications of label switching. Because the ATM layer 24 labels (VPI and VCI) associated with a VC rewritten with new value at 25 every ATM switch nodes, it is not possible to use them to identify a 26 VC in label mapping messages. The concept of Virtual Connection 27 Identifier (VCID) is introduced to solve this problem. VCID has the 28 same value at both ends of a VC. This document specifies the 29 procedures for the communication of VCID values between neighboring 30 ATM-LSRs that must occur in order to ensure this property. 32 This document is a product of the Multiprotocol Label Switching 33 Working Group of the IETF. 35 This is now a Proposed Standard Protocol. 37 This document specifies an Internet standards track protocol for 38 the Internet community, and requests discussion and suggestions 39 for improvements. Please refer to the current edition of the 40 "Internet Official Protocol Standards" (STD 1) for the 41 standardization state and status of this protocol. Distribution 42 of this memo is unlimited. 44 This announcement is sent to the IETF list and the RFC-DIST list. 45 Requests to be added to or deleted from the IETF distribution list 46 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 47 added to or deleted from the RFC-DIST distribution list should 48 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 50 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 51 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 52 help: ways_to_get_rfcs. For example: 54 To: rfc-info@RFC-EDITOR.ORG 55 Subject: getting rfcs 57 help: ways_to_get_rfcs 59 Requests for special distribution should be addressed to either the 60 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 61 specifically noted otherwise on the RFC itself, all RFCs are for 62 unlimited distribution.echo 63 Submissions for Requests for Comments should be sent to 64 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 65 Authors, for further information.