1 / 11

VCID Notification Mechanism in MPLS: Consensus Document Overview

This document outlines the consensus reached during the MPLS working group meeting in April 1998 regarding VCID (Virtual Channel Identifier) notifications over ATM links within the MPLS framework. It details inband and outband notification methods, which utilize user-specific fields (BLLI and UUI) for VCID communication. The proposed document expands on VCID formats and notification procedures, providing a general structure for VCID messages in MPLS architecture. The draft ensures standardization and clarity in handling VCID notifications across different network scenarios.

arissa
Télécharger la présentation

VCID Notification Mechanism in MPLS: Consensus Document Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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. 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. 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. 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 | / / +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ << MPLS VCID Format >>

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

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

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

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

More Related