1. 1 VCID Notification over ATM Link N. Demizu @ SonyCSL K. Nagami @ Toshiba L. Anderson @ Ericsson P.Doolan @ Ennovate Networks H. Esaki @ Toshiba G.Swallow @ Cisco IETF MPLS-WG Los Angels, April 1998.

2. 2 Current Consensus - VCID Draft : WG Internet-Draft draft-ietf-mpls-vcid-atm-00.txt - Describe the VCID stuff in MPLS Framework document (draft-ietf-mpls-framework-02.txt) ==> had sent sentences to drafting team - VCID document specifies VCID notification over label swapped datalink (e.g., ATM link) (1) Inband notification (2) Outband notification (2)-a. using BLLI user specific field (7 bits) (2)-b. using UUI field (variable length) (*) p-p and p-mpt use different mechanism

3. 3 Proposed Consensus 1. Describe the VCID stuff in MPLS architecture document (draft-ietf-mpls-arch-01.txt) 2. Add the operation with manual configuration without VCID notification procedure 3. Specifies VCID format and related messages (1) Inband notification (2) Outband notification (2)-a. using BLLI field (7 bits) (2)-b. using UUI field (variable length) => MPLS@IETF specifies 4. Specifies VCID notification procedure - inband/outband VCID notification

4. 4 Common VCID Format Example - we should define a common VCID format for explicit and piggy-back LDP ==> we do not need to specify VCID format for each case. - MPLS VCID format MPLS VCID == VCID ::= Type + Length + Value 0 8 16 24 32 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | VCID Type | VCID Length | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | VCID Value | / / +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >

5. 5 Master node Slave Node VCID ACK via Signaling VC 2. associates VCID and VC(VPI/VCI) 3. associates VCID and VC(VPI/VCI) Within UUI using Signaling VC 1. The VC is ready to be used! Procedure with UUI

6. 6 VCID Format Example for UUI Bits 8 7 6 5 4 3 2 1 Octet +-----+-----+-----+-----+-----+-----+-----+-----+ --- | Information element identifier | | | = User-user information element (0x7E) | 1 | +-----+-----+-----+-----+-----+-----+-----+-----+ | | 1 | Coding | IE instruction field | | | Ext | standard |Flag |Res. | IE action ind. | 2 | by ITU-T +-----+-----+-----+-----+-----+-----+-----+-----+ | SG11 | Length of contents of information element | 3-4 | WP1 +-----+-----+-----+-----+-----+-----+-----+-----+ | | Protocol discriminator | | | = Internet protocol/application (TBD) | 5 | +-----+-----+-----+-----+-----+-----+-----+-----+ --- | Internet protocol/application identifier | | | = MPLS VCID (0x01) | 6 | +-----+-----+-----+-----+-----+-----+-----+-----+ | | VCID Type | 7 | +-----+-----+-----+-----+-----+-----+-----+-----+ | | VCID Length | 8 | by IETF +-----+-----+-----+-----+-----+-----+-----+-----+ | MPLS-WG | Reserved | 9-10 | +-----+-----+-----+-----+-----+-----+-----+-----+ | | VCID Value | 11-TBD | +-----+-----+-----+-----+-----+-----+-----+-----+ --- (*) VCID Value Example : ESI(48bits)+ID(48bits)

7. 7 Procedure with BLLI Master nodeSlave Node ATM Forum Signaling with unique BLLI VCID&BLLI ACK 4. associates VCID and VC(BLLI) 5. associates VCID and VC(BLLI) by a dedicated protocol or within a BIND message 1. 3. The VC is ready to be used! ACK via ATM Forum Signaling 2.

8. 8 VCID Format Example for BLLI 0 8 16 24 31 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | VCID Type |VCID Length=12 | Reserved | LLID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ESI of master node | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ LLID (1 byte) : BLLI value ESI field (6 bytes) : ESI of master node ID (6 bytes) : master node decides unique identifier. (*) Master node; point-to-point link : upstream node or downstream node point-to-multipoint link : only upstream node

9. 9 Master node Slave Node VCID ACK via shared control VC 2. associates VCID and VC(VPI/VCI) 3. associates VCID and VC(VPI/VCI) Within BIND mesasge via labeled VC 1. The VC is ready to be used! Procedure with Inband notification

10. 10 VCID Format Example for Inband 0 8 16 24 31 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | VCID Type |VCID Length=12 | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ESI of master node | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ESI field (6 bytes): ESI of master node ID (6 bytes) : master node decides unique identifier. (*) Master node; point-to-point link : upstream node or downstream node point-to-multipoint link : only upstream node

11. 11 Drafting VCID document - VCID mechanism can be an additional mechanism to current LDP (and to piggy-back LDP) (*) Only we have to do is having a consistency on label ID field length in LDP - How to proceed; (1) Put in VCID mechanism in existing LDP spec. (2) Complete VCID mechanism as a separate document. Then, (a) put it in the LDP spec. (b) refer it in the LDP spec. with a brief description - Send e-mail to join the VCID document drafting; hiroshi@isl.rdc.toshiba.co.jp