1 VCID Notification over ATM Link N. SonyCSL K. Toshiba L. Ericsson Ennovate Networks H. Toshiba G.Swallow.

Slides:



Advertisements
Similar presentations
Leading Edge Routing MPLS Enhancements to Support Layer 2 Transport Services Jeremy Brayley
Advertisements

IETF draft-jeyatharan-mext-flow-tftemp-reference-01 Mohana Jeyatharan panasonic.com Chan-Wah Ng 1 IETF.
Gursharan Singh Tatla SLIP and PPP 27-Mar
Pseudowire Endpoint Fast Failure Protection draft-shen-pwe3-endpoint-fast-protection-00 Rahul Aggarwal Yimin Shen
Doc.: IEEE xxxxx Submission doc. : IEEE Slide 1 Junbeom Hur and Sungrae Cho, Chung-Ang University Project: IEEE P
Ipbb.PPT / / Risto Mononen page: 1 IP over networks Heikki Almay Kari Melkko Risto Mononen IP seminar
PCEP Extensions for Segment Routing draft-ietf-pce-segment-routing-01
Copyright: RSVP The ReSerVation Protocol by Sujay koduri.
D Channel Data Link Protocol Link access procedure on the D channel - LAPD.
MPLS H/W update Brief description of the lab What it is? Why do we need it? Mechanisms and Protocols.
IPv4-Embedded IPv6 Multicast Address draft-ietf-mboned-64-multicast-address-format IETF 84 Vancouver 1.
© 2009 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 IETF 84 – Vancouver August 2012 LSP Ping Support for P2MP PWs (draft-jain-pwe3-p2mp-pw-lsp-ping-00.txt)
1Traffic Eng. © 1999, Cisco Systems, Inc. Cisco Systems Change to Hello Protocol Three way handshake Carry both Source and Destination Instance When establishing.
QoS in MPLS SMU CSE 8344.
Atm-signaling1 ATM Signaling ATM signaling is mainly used for setup/release of virtual connections. A phased approach was taken for the introduction of.
GSM Signaling Protocol Architecture. Protocols above the link layer of the GSM signaling protocol architecture provide specific functions: Radio Resource.
Draft-li-mpls-global-label-framework-02IETF 90 MPLS WG1 A Framework of MPLS Global Label draft-li-mpls-global-label-framework-02 Zhenbin Li, Quintin Zhao,
Giuseppe Bianchi Layer 2 Framing HDLC (High-level Data Linl Control)
Jun Li DHCP Option for Access Network Information draft-lijun-dhc-clf-nass-option-01.
1 VCID Notification over ATM Link - Inband / Outband Notifications - SonyCSL TOSHIBA Ennovate Networks TOSHIBA Esaki.
Draft-jounay-pwe3-p2mp-pw-requirements-00.txt IETF 68 PWE3 Working Group Prague, March 2007 F. Jounay, P. Niger, France Telecom Y. Kamite, NTT Communications.
CS4550 Computer Networks II IP : internet protocol, part 2 : packet formats, routing, routing tables, ICMP read feit chapter 6.
Multimedia Wireless Networks: Technologies, Standards, and QoS Chapter 3. QoS Mechanisms TTM8100 Slides edited by Steinar Andresen.
InterDomain-QOSM: The NSIS QoS Model for Inter-domain Signaling J. Zhang, E. Monteiro, P. Mendes, G. Karagiannis, J. Andres-Colas 66 th IETF – Montreal,
BGP Point-to-Multipoint LSP draft-satoru-mpls-bgp-multipoint-02 Satoru Matsushima Tetsuya Murakami Kenichi.
1 Policy Routing Related IETF WGs George Lee. 2 Policy Routing Related IETF WGs Policy Framework (policy) Resource Allocation Protocol (rap) Routing Policy.
June 4, 2003Carleton University & EIONGMPLS - 1 GMPLS Generalized Multiprotocol Label Switching Vijay Mahendran Sumita Ponnuchamy Christy Gnanapragasam.
1. Tag Switching RFC Cisco systems Tag Switching architecture overview. Switching In IP Networks - B.Davie, P.Doolan, Y.Rekhter. Presnted By - Shmuel.
© NOKIAMSF Paris drieft-ietf-grmp-04.PPT / 28 March, 2000/ ADo page: 1 Review of draft-ietf-gsmp-04 Avri Doria, Nokia Fiffi Hellstrand, Nortel Networks.
1 MPLS Architectural Considerations for a Transport Profile ITU-T - IETF Joint Working Team Dave Ward, Malcolm Betts, ed. April 16, 2008.
PCE 64 th IETF PCE Policy Architecture draft-berger-pce-policy-architecture-00.txt Lou Berger Igor Bryskin Dimitri Papadimitriou.
November 8, 2005"Field of Use" RFC Modification1 “Field of Use” RFC Modification Permissions David L. Black EMC Corporation November 8, 2005.
Dean Cheng 81 st IETF Quebec City RADIUS Extensions for CGN Configurations draft-cheng-behave-cgn-cfg-radius-ext
© 2009 Cisco Systems, Inc. All rights reserved. Cisco Public Presentation_ID 1 Upstream mapping in Echo Request draft-ankur-mpls-upstream-mapping-00 Ankur.
1 © 2002, Cisco Systems, Inc. All rights reserved. draft-sathappan-pw-atm-mib- 00.txt IETF #56 San Francisco, CA USA Thomas D. Nadeau
55th IETF GSMP WG, Atlanta 1 General Switch Management Protocol (GSMP) v3 for Optical Support 55 th IETF GSMP WG, Atlanta Jun Kyun Choi
Generalized MPLS RSVP-TE Signaling for Layer-2 LSPs D.Papadimitriou D.Brungard A.Ayyangar
26/07/2011 IETF 81 CDNI WG - draft-xiaoyan-cdni-requestrouting-01 1 CDNI WG draft-xiaoyan-cdni-requestrouting-01 IETF81 - Quebec Xiaoyan He
IETF 69, July 2007Slide 1 Preferential Forwarding Status bit Definition draft-muley-dutta-pwe3-redundancy-bit-01.txt Praveen Muley, Pranjal K. Dutta, Mustapha.
Pseudo Wire (PW) Virtual Circuit Connection Verification (VCCV) Update Thomas D. Nadeau Cisco Systems, Inc Rahul Aggarwal (Presenter) Juniper Networks.
LMP Test Messages Extensions for Evolutive OTN draft-ceccarelli-ccamp-gmpls-g709-lmp-test-01 CCAMP WG, IETF 77 th Anaheim.
Precision Time Protocol over MPLS draft-ronc-ptp-mpls-00.txt PWE3 WG IETF Chicago 2007 Ron Cohen
Draft-beckhaus-ldp-dod-01IETF 82: 14 November LDP DoD draft-beckhaus-ldp-dod-01.txt Thomas Beckhaus (Deutsche Telekom AG) Bruno Decraene (France.
82 nd Taipei Protection Mechanisms for LDP P2MP/MP2MP LSP draft-zhao-mpls-mldp-protections-00.txt Quintin Zhao, Emily Chen, Huawei.
1 K. Salah Module 5.1: Internet Protocol TCP/IP Suite IP Addressing ARP RARP DHCP.
GSMPv3 Packet Capable Switch Support 56th IETF GSMP WG, San Francisco Kenneth Sundell
Draft-ietf-ccamp-lmp-02.txt Link Management Protocol (LMP) LMP draft updates…  draft-ietf-ccamp-lmp-07.txt  draft-ietf-ccamp-lmp-wdm-01.txt  draft-ietf-ccamp-lmp-test-sonet-sdh-00.txt.
Advertising Generic Information in IS-IS
IETF#67 – 5-10 November 2006 FECFRAME requirements (draft-ietf-fecframe-req-01) Mark Watson.
PCEP Extensions For Transporting Traffic Engineering (TE) Data
NAT State Synchronization using SCSP draft-xu-behave-nat-state-sync-01
LMP Behavior Negotiation
Bundle Protocol Specification
ROLL RPL Security IETF 77 status
draft-jeyatharan-netext-pmip-partial-handoff-02
ITU-T Study Group 15 Update to IETF CCAMP
78th IETF Meeting - Maastricht 27th, July 2010
M3UA (MTP3-User Adaptation Layer)
CHAPTER 8 Network Management
Robert Moskowitz, Verizon
Robert Moskowitz, Verizon
1/2/2019<month year> doc.: IEEE Jan 2013
Robert Moskowitz, Verizon
Robert Moskowitz, Verizon
Random Access RU Allocation in the Trigger Frame
Controller Area Networks (CAN)
Random Access RU Allocation in the Trigger Frame
Congestion control timer
Extended BFD draft-mirmin-bfd-extended
E. Bellagamba, Ericsson P. Sköldström, Acreo D. Ward, Juniper
Presentation transcript:

1 VCID Notification over ATM Link N. SonyCSL K. Toshiba L. Ericsson Ennovate Networks H. Toshiba 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) => 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 | VCID Type | VCID Length | Reserved | | VCID Value | / / >

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 VCID Format Example for UUI Bits 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 | WP | | 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 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 The VC is ready to be used! ACK via ATM Forum Signaling 2.

8 VCID Format Example for BLLI | 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 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 VCID Format Example for Inband | 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 to join the VCID document drafting;