draft-ietf-mpls-vcid-atm

Last Version:	draft-ietf-mpls-vcid-atm-05.txt		Tracker Entry
Date:	29-Mar-2004
Disposition:	RFC3038 (diff)
Previous Versions:	draft-ietf-mpls-vcid-atm-05.txt (diff)    - 30-Nov-2001
	draft-ietf-mpls-vcid-atm-05.txt (diff)    - 20-Jan-2001
	draft-ietf-mpls-vcid-atm-04.txt (diff)    - 09-Aug-2000
	draft-ietf-mpls-vcid-atm-03.txt (diff)    - 24-Jul-1999
	draft-ietf-mpls-vcid-atm-02.txt (diff)    - 03-Apr-1999
	draft-ietf-mpls-vcid-atm-01.txt (diff)    - 09-Apr-2002
	draft-ietf-mpls-vcid-atm-00.txt (diff)    - 09-Apr-2002

A new Request for Comments is now available in online RFC libraries.


        RFC 3038

        Title:      VCID Notification over ATM link for LDP
        Author(s):  K. Nagami, Y. Katsube, N. Demizu, H. Esaki,
                    P. Doolan 
        Status:     Standards Track
        Date:       January 2001
        Mailbox:    ken.nagami@toshiba.co.jp,
                    demizu@dd.iij4u.or.jp, hiroshi@wide.ad.jp, 
                    yasuhiro.katsube@toshiba.co.jp,
                    pdoolan@ennovatenetworks.com 
        Pages:      19
        Characters: 39134
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-ietf-mpls-vcid-atm-05.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc3038.txt


The Asynchronous Transfer Mode Label Switching Router (ATM-LSR) is one
of the major applications of label switching.  Because the ATM layer
labels (VPI and VCI) associated with a VC rewritten with new value at
every ATM switch nodes, it is not possible to use them to identify a
VC in label mapping messages.  The concept of Virtual Connection
Identifier (VCID) is introduced to solve this problem.  VCID has the
same value at both ends of a VC.  This document specifies the
procedures for the communication of VCID values between neighboring
ATM-LSRs that must occur in order to ensure this property.

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