Presentation is loading. Please wait.

Presentation is loading. Please wait.

Alternative solution for EC Type II support

Published byStephanie Holt Modified over 6 years ago

Similar presentations

Presentation on theme: "Alternative solution for EC Type II support"— Presentation transcript:

1 Alternative solution for EC Type II support
Maarten Vissers v01

2 Introduction liaison-haddock-proposed- response-q eotn v01 presents the model of a Transport Bridge supporting EC Type I and II signals new-vissers-generalized-ec-type- 2-support-0711-v01 reports negative feedback from the operator community on the I+S- Tagging of EC Type II signals This tagging is Not backwards compatible with existing S-Tagging on NNI ports Not client agnostic on NNI ports An alternative solution is required which is backwards compatible with S-Tagging on NNI ports and is client agnostic on NNI ports

3 Alternative Solution TB S-Component Transport Bridge (TB) is supported by a S-Component with Provider, OTN and/or SDH Network Ports providing S-Tagging of the all types of EC signals Backwards compatible tagging  Client agnostic tagging  EC Type II service primitive is a B- VLAN service primitive, and is indistinguishable from a S-VLAN service primitive S-Tagged Service Interface and Transparent Service Interface UNI-N port functions comprise an I-/T-Component and a CBP PNP PNP PNP PNP ONP ONP ONP ONP ONP ONP SNP SNP SNP SNP ONP: OTN Network Port PNP: Provider Network Port SNP: SDH Network Port EC Signals Transparent Service Interface S-Tagged Service Interface CBP T-Comp. I-Comp. UNI-N port C-Tagged Service Interface S-VLAN MAC Relay CNP C-Comp. PNP ONP SNP

4 Alternative Solution TB S-Component Transport Bridge (TB) is supported by a S-Component with Provider, OTN and/or SDH Network Ports providing S-Tagging of the all types of EC signals Backwards compatible tagging  Client agnostic tagging  EC Type II service primitive is a B- VLAN service primitive, and is indistinguishable from a S-VLAN service primitive S-Tagged Service Interface and Transparent Service Interface UNI-N port functions comprise an I-/T-Component and a CBP PNP PNP PNP PNP ONP ONP ONP ONP ONP ONP SNP SNP SNP SNP ONP: OTN Network Port PNP: Provider Network Port SNP: SDH Network Port EC Signals EISS Transparent Service Interface S-Tagged Service Interface CBP T-Comp. I-Comp. S-Comp B-Comp UNI-N port C-Tagged Service Interface S-VLAN MAC Relay CNP C-Comp. PNP ONP SNP

5 Alternative Solution UNI-N Port function S-VLAN MAC Relay Use the B-VLAN MEP as EC MEP Do not use BSI MEP/MIPs B-VLAN is deployed as EC and carries one EVC Question: How to set the I-SID and B-SID values without need for complex negotiation between UNI-N ports? CBP T-Comp. Transparent Service Interface B-SID I-SID I-SID CBP I-Comp. S-Tagged Service Interface No BSI MEP/MIPs EC MEP = B-VLAN MEP EC Signals I-SID C Service Interface UNI-N EC Service Interface UNI-N Service Interface UNI-N I-SID A 2 to 8192 UNI-N ports in EC; determined by 13-bit MEPID field in CCM PDU I-SID B Backbone-SID

6 I-SID value Option I Backbone Service Instance Table (c6.10 PIP function) VIP-ISS VIP-ISID Default Backbone Destination adminPointToPointMAC enableConnectionIdentifier A a B b C c D d E e Backbone Service Instance Table (c6.11 CBP function) Backbone-VID Backbone-SID ABC a DEF b GHI c JKL d MNO e VIP-ISID/Backbone-SID values must be negotiated amongst the EC UNI-N ports High probability that the M UNI-N ports (2≤M≤8192) in an EC have at least one B/I-SID value available; not guaranteed however Request to set up 8192 port EC. Those 8192 ports support already other ECs. E.g. port 1 supports 2048 ECs using B-SID 256 – 2303, port 2 supports 2048 ECs using B-SID 2304 – 4351, port 3 using B-SIDs 4352 – 6399, etc. These 8192 ports do not have a common B-SID value available.

7 I-SID value Option II Backbone Service Instance Table (c6.10 PIP function) VIP-ISS VIP-ISID Default Backbone Destination adminPointToPointMAC enableConnectionIdentifier A 4096+A B 4096+B C 4096+C D 4096+D E 4096+E c does not support “per B-VID” B-SID values VIP-ISID and Local-SID parameters have local significance only No need to coordinate B-SID value with other EC UNI-N ports Text in c supports this approach. Text in c does not support this approach; B-SIDs must be unique as B-VID is not used in row selection process. Correct? Backbone Service Instance Table (c6.11 CBP function) Backbone-VID Backbone-SID Local-SID Default Backbone Destination A 4096 4096+A B 4096+B C 4096+C D 4096+D E 4096+E

8 I-SID value Option III Backbone Service Instance Table (c6.10 PIP function) VIP-ISS VIP-ISID Default Backbone Destination adminPointToPointMAC enableConnectionIdentifier A S-VID B C D E requires coordination of S-VID values between UNI-N ports of multiple ECs; S-VID range is not large enough VIP-ISID and Backbone-SID parameter values are locked to the S-VID of the carried S-VLAN. If a bundle of S-VLANs is carried, or if an individual S-VLAN is carried which has multiple S-VID values (e.g. to indicate root, leaf, leaf group), then the lowest S-VID value is used. If a transparent service is supported, assume S-VID=0 and set VIP-ISID and Backbone-SID to = 4096. No need to coordinate Backbone-SID with other EC UNI-N ports. Backbone Service Instance Table (c6.11 CBP function) Backbone-VID Backbone-SID A S-VID B C D E

9 I-SID value Option IV Other?

10 No other I-SID value option
Select Option I Future enhancement would be support of “per B-VID” B-SID in c6.11.2

11 Conclusion A backward compatible and client agnostic NNI port solution supporting EC Type II is available using existing 802.1Q ports and components It is proposed to select this alternative solution and liaise this to ITU-T Q.10/15 (IEEE 802 November meeting)

12 Backup

13 Alternative EC Type I&II supp. PEB
EC Type 1 & 2 supporting Provider Edge Bridge Line Port Tributary Port functonality S-VLAN Component C-VLAN Component CNP C-Tagged Service Interface (un-, priority-C-. C-Tagged) PEP S-Tagged LANs CEP CNP PEP To/from PEB & PB & IBBEB & MEF E-NNI Port Based Service Interface (un- C-, priority-S- I-Tagged) PNP CNP Individual S-VLAN Service S-Tagged Service Interface (S-Tagged) CNP PNP Remote Customers C-Tagged service interface C-VLAN Component CNP PEP S-VLAN Component CEP PAP Port-based, S- & C-Tagged Service Interface (S-, S+C-Tagged) CNP PEP PNP RCAP Remote Customer Port-based Service Interface EC Type 1&2 CNP PAP Remote Customers S-Tagged Service interface EC Type 1 PNP Alternative EC Type I&II supp. PEB CNP Individual or bundled I-Tagged Services I-Tagged service interface (I-Tagged) CBP I- Component C-VLAN Component C-Tagged Service Interface (un-, priority-C-, C-Tagged) CNP CBP PEP PIP CEP Regular PNP ports are capable to support any EC type EC Type 2 UNI-N tributary ports are added to PEB node CNP PEP Port Based Service Interface (un-, C-, priority-S- I-Tagged) CBP PIP CNP S-Tagged Service Interface (S-Tagged) CNP Remote Customers C-Tagged service interface C-VLAN Component CNP PEP S-VLAN Component CEP PAP Port-based , S- & C-Tagged Service Interface (S-, S+C-Tagged) CNP PEP RCAP Remote Customer Port-based Service Interface CNP PAP Remote Customers S-Tagged Service interface CNP PNP Transparent Service Interface (un-, C-, S-, I-Tagged) T- Component CBP PIP CNP EC Type 2

14 Alternative EC Type I&II supp. TEB
EC Type 1 & 2 supporting Transport Edge Bridge Line Port Tributary Port functonality S-VLAN Component C-VLAN Component CNP C-Tagged Service Interface (un-, priority-C-. C-Tagged) PEP S-Tagged LANs CEP CNP PEP To/from PEB & PB & IBBEB & MEF E-NNI Port Based Service Interface (un- C-, priority-S- I-Tagged) PNP CNP Individual S-VLAN Service S-Tagged Service Interface (S-Tagged) CNP PNP Remote Customers C-Tagged service interface C-VLAN Component CNP PEP S-VLAN Component CEP PAP Port-based, S- & C-Tagged Service Interface (S-, S+C-Tagged) To/from TEB & TB & OTN XC CNP PEP ONP RCAP Remote Customer Port-based Service Interface CNP PAP ONP Remote Customers S-Tagged Service interface EC Type 1 EC Type 1&2 CNP PNP Alternative EC Type I&II supp. TEB Individual or bundled I-Tagged Services I-Tagged service interface (I-Tagged) CBP I- Component C-VLAN Component C-Tagged Service Interface (un-, priority-C-, C-Tagged) CNP CBP PEP PIP CEP Regular PNP & ONP ports are capable to support any EC type EC Type 2 UNI-N tributary ports are added to TEB node CNP PEP Port Based Service Interface (un-, C-, priority-S- I-Tagged) CBP PIP CNP S-Tagged Service Interface (S-Tagged) CNP Remote Customers C-Tagged service interface C-VLAN Component CNP PEP S-VLAN Component CEP PAP Port-based , S- & C-Tagged Service Interface (S-, S+C-Tagged) CNP PEP RCAP Remote Customer Port-based Service Interface CNP PAP Remote Customers S-Tagged Service interface CNP PNP Transparent Service Interface (un-, C-, S-, I-Tagged) T- Component CBP PIP CNP EC Type 2

Download ppt "Alternative solution for EC Type II support"

Similar presentations

Experiences with IEEE 802.1ah (Provider Backbone Bridges) Ronald van der Pol SARA 16-18 Sep 2009NORDUnet meeting, Copenhagen.

Experiences with IEEE 802.1ah (Provider Backbone Bridges) Ronald van der Pol SARA Sep 2009NORDUnet meeting, Copenhagen.
1 PBB MEPs and MIPs [Intended only for discussion purposes - DWM] MIP MEP MHF 1 35 1 35 B CompI Comp Customer MD Levels SP MD Service Level IB Link Access.

1 PBB MEPs and MIPs [Intended only for discussion purposes - DWM] MIP MEP MHF B CompI Comp Customer MD Levels SP MD Service Level IB Link Access.
M Vinod Kumar Problem with Peering PBBN. Introduction We present one problem related to Interop between two PBBN operators –We use packet flow in forward.

M Vinod Kumar Problem with Peering PBBN. Introduction We present one problem related to Interop between two PBBN operators –We use packet flow in forward.
Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and.

Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and.
Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality.

Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality.
Port group model in G.8021 Akira Sakurai G.8021 Co-editor IEEE 802.1 and ITU-T Q.9/15 Ethernet Transport issues (Geneva, 27 May 2010)

Port group model in G.8021 Akira Sakurai G.8021 Co-editor IEEE and ITU-T Q.9/15 Ethernet Transport issues (Geneva, 27 May 2010)
Extending OTN Standards to Support Ethernet Services

Extending OTN Standards to Support Ethernet Services
Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 79th IETF - Beijing VPLS PE Model with E-Tree Support Yuanlong Jiang.

Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 79th IETF - Beijing VPLS PE Model with E-Tree Support Yuanlong Jiang.
1 Introducing the Specifications of the Metro Ethernet Forum.

1 Introducing the Specifications of the Metro Ethernet Forum.
1 DRNI Examples and DAS position Maarten Vissers 2011-08-10.

1 DRNI Examples and DAS position Maarten Vissers
1 DRNI Examples and DAS position Maarten Vissers 2011-08-16 Version 01.

1 DRNI Examples and DAS position Maarten Vissers Version 01.
1 Alternative solution for EC Type II support Maarten Vissers 2011-09-20.

1 Alternative solution for EC Type II support Maarten Vissers
1 Generalized EC Type 2 support EC Type 1&2 supporting bridges Maarten Vissers 2011-07-21 v01.

1 Generalized EC Type 2 support EC Type 1&2 supporting bridges Maarten Vissers v01.
MEF Reference Presentation November 2011

MEF Reference Presentation November 2011
1 Distributed Network Protection (DNP) architecture study Maarten Vissers 2011-11-18 v4 v2: includes a few slides at the end illustrating segment protection.

1 Distributed Network Protection (DNP) architecture study Maarten Vissers v4 v2: includes a few slides at the end illustrating segment protection.
802.1Qay PBB-TE Protection Switching Overview

802.1Qay PBB-TE Protection Switching Overview
Topic 7 Local Area Networks (LAN)

Topic 7 Local Area Networks (LAN)
1 DRNI and Distributed Protection Examples Maarten Vissers 2011-09-26 v01 Based on slides presented in 802.1 IW meeting in Nanjing on Thursday Sept 22.

1 DRNI and Distributed Protection Examples Maarten Vissers v01 Based on slides presented in IW meeting in Nanjing on Thursday Sept 22.
CMPE 150- Introduction to Computer Networks 1 CMPE 150 Fall 2005 Lecture 19 Introduction to Computer Networks.

CMPE 150- Introduction to Computer Networks 1 CMPE 150 Fall 2005 Lecture 19 Introduction to Computer Networks.
1 Distributed Network Protection (DNP) architecture study Maarten Vissers 2011-11-10 v3 v2: includes a few slides at the end illustrating segment protection.

1 Distributed Network Protection (DNP) architecture study Maarten Vissers v3 v2: includes a few slides at the end illustrating segment protection.

Similar presentations

Ads by Google