1 Common network architectures for PBB, PBB-TE and EOTN networks Maarten Vissers 2011-05-11.

Slides:



Advertisements
Similar presentations
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.
Advertisements

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.
Link Selection and OAM Version 01 Stephen Haddock July 18,
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 and ITU-T Q.9/15 Ethernet Transport issues (Geneva, 27 May 2010)
Extending OTN Standards to Support Ethernet Services
EVC structure for a Protected E-Line service
1 Introducing the Specifications of the Metro Ethernet Forum MEF 17 Service OAM Framework and Requirements February 2008.
1 Transport Services Layer Protection Switching Types Interacting with DRNI Maarten Vissers
1 DRNI Examples and DAS position Maarten Vissers
1 DRNI Examples and DAS position Maarten Vissers Version 01.
1 Alternative solution for EC Type II support Maarten Vissers
1 Generalized EC Type 2 support EC Type 1&2 supporting bridges Maarten Vissers v01.
M Vinod Kumar Dr. Abhay Karandikar. Multiplex Entity CBP PIP Towards Core Towards Core All fault indications are available on one port All fault indications.
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
Core Wholesale EVC Option I Service Edge router connects via E-Tree service with e.g. 20 ATM DSLAMs located in offices  Rooted-mp EVC starts in router.
802.1ag - Connectivity Fault Management Tutorial – Part 1 Dinesh Mohan July 12, 2004.
1 DRNI and Distributed Protection Examples Maarten Vissers v01 Based on slides presented in IW meeting in Nanjing on Thursday Sept 22.
1 Distributed Network Protection (DNP) architecture study Maarten Vissers v3 v2: includes a few slides at the end illustrating segment protection.
1 UNI-N Trib Card in PE node Two operational modes:  service model 1 (client/server)  service model 2 (peer) Two stack modes:  EVC only  EVC & MS-PW.
DRNI Examples, DAS position, MEP/MIP position
11 NETWORK CONNECTION HARDWARE Chapter 3. Chapter 3: NETWORK CONNECTION HARDWARE2 NETWORK INTERFACE ADAPTER  Provides the link between a computer and.
IETF 73 November aq Shortest Path Bridging Overview for IETF Don Fedyk Editor 802.1aq.
© 2010 Tata Communications Ltd., All Rights Reserved Presented by © 2010 Tata Communications Ltd., All Rights Reserved Tata Communications’ Ethernet Evolution.
1 Common network architectures for PBB, PBB-TE and EOTN networks version 01 Maarten Vissers v01 includes new slides 10 and 12: Slide 10 presents.
1 DRNI and G.8031 ETH SNCP interworking Maarten Vissers
1 Multipoint Ethernet Connection Protection
Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 77th IETF - Anahaim VPLS PE Model with E-Tree Support Yuanlong Jiang.
1 DRNI Data Plane Model I/II Comparison & MAC Address Values in DRNI Maarten Vissers v00.
1 Data Plane Summary Maarten Vissers v1.
1 Supporting VUNI in DRNI Maarten Vissers v01 v01: added multiple virtual UNI with hairpin.
1 Introducing the Specifications of the Metro Ethernet Forum.
VPLS Extensions for Provider Backbone Bridging - draft-balus-l2vpn-vpls-802.1ah-01.txt John Hoffmans – KPN Geraldine Calvignac - France Telecom Raymond.
Omniran PtP Links across IEEE 802 Bridged Infrastructure Date: Authors: NameAffiliationPhone Max
IETF68 CCAMP1 GMPLS Control of Ethernet Forwarding Don Fedyk Loa Andersson
Q description of G.8031 Ethernet Connection (EC) SubNetworkConnection (SNC) Protection “VLAN Segment Protection” Maarten Vissers v2.
VLAN Trunking Protocol
Slide title In CAPITALS 50 pt Slide subtitle 32 pt PBB-TE Status Report Panagiotis Saltsidis.
1/28/2010 Network Plus Network Device Review. Physical Layer Devices Repeater –Repeats all signals or bits from one port to the other –Can be used extend.
1 Portal Models Maarten Vissers v1. 2 DRNI Applicability DRNI model is applicable to many different portal types 1.PB Portal (S-DRNI) 2.BCB.
VLAN V irtual L ocal A rea N etwork VLAN Network performance is a key factor in the productivity of an organization. One of the technologies used to.
VPLS Extensions for Provider Backbone Bridging - draft-balus-l2vpn-vpls-802.1ah-02.txt John Hoffmans – Geraldine Calvignac -
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 draft-martini-pwe ah-pw-03.txt Ali Sajassi July 29, ah.
Setup and Manage PBB-based Tunnels with PWE3 Mechanism Ping Pan (Hammerhead Systems) Shane Amante (Level 3) Nasser El-Aawar (Level 3) Chicago, IETF 69.
Carrier-Grade Ethernet Technology
Data Link Layer and Ethernet COM211 Communications and Networks CDA College Theodoros Christophides
1 VLANs Relates to Lab 6. Short module on basics of VLAN switching.
Omniran CF00 1 VLANs in relation to P802.1CF NRM Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
1 Introduction filtering-0710-v04.pdfhttp://
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Draft-sajassi-l2vpn-pbb-vpls-mpls- access-00.txt July 28, 2008 PBB-VPLS.
1 Generalized EC Type 2 support EC Type 1&2 supporting bridges Maarten Vissers
Portal Models Maarten Vissers v2
HUAWEI TECHNOLOGIES CO., LTD. Page 1 25 March 2009 Peer Interworking Ethernet and PDH service cases Maarten Vissers.
M Vinod Kumar Tejas Networks Ltd.  Example  Requirements  Possible solutions.
Precision Time Protocol over MPLS draft-ronc-ptp-mpls-00.txt PWE3 WG IETF Chicago 2007 Ron Cohen
1 Distributed Network Protection (DNP) architecture study Maarten Vissers v1.
Supporting VUNI in DRNI Maarten Vissers v00
VLANs: Virtual Local Area Networks
FRD Examples November 28, 2017 L. Ong.
Alternative solution for EC Type II support
Connecting Networks Repeater: physical layer Bridge: data link layer
Ethernet : Framing and Addressing
RNI Requirements Imposed by PBB-TE
E-OTN status update and service interface question [associated with ITU-T liaison statement liaison-itut-sg15-ols ] version 01 New slides:
Stephen Haddock September 13, 2012
DRNI and Distributed Network Protection Model Evolution: Maarten  Norm  Steve Maarten Vissers v1  
Lecture#7: Trunking and STP
Task 63 Scope – Ethernet Examples
Presentation transcript:

1 Common network architectures for PBB, PBB-TE and EOTN networks Maarten Vissers

2 1. PBB and PBB-TE network EVC(C-VLAN) via EC(S-VLAN) IB-BEB UNI PNP S mp2mp B-VLAN or p2p TESI mp2mp B-VLAN or p2p TESI mp2mp B-VLAN or p2p TESI EVC = C-VLAN EC = S-VLAN S-VID Translation at PBBN domain boundaries (in CNPs) mp2mp B-VLANs or p2p TESIs in each domain no MAC address collisions in PBBN domains (multiple single- domain PBBNs) S-VID Translation locations

3 2. PBB network EVC(S-VLAN) via EC(BSI) IB-BEB UNI PNP S EVC = S-VLAN EC = BSI I-SID Translation at PBBN domain boundaries (in CBPs) mp2mp B-VLANs in each domain potential MAC address collisions in PBBN domains (multi-domain PBBN) mp2mp B-VLAN I-SID Translation locations

4 3. PBB network EVC(C-VLAN) via EC1(S-VLAN) over EC2(BSI) IB-BEB UNI PNP S EVC = C-VLAN EC1 = S-VLAN, EC2 = BSI S-VID Translation at PBBN network boundary (in CNP) I-SID Translation at PBBN domain boundaries (in CBPs) mp2mp B-VLANs in each domain potential MAC address collisions in PBBN domains (multi-domain) B-VLAN I-SID Translation locations S-VID Translation location

5 4. EOTN network EVC(C-VLAN) via EC(S-VLAN) EVC = C-VLAN EC = S-VLAN S-VID Translation at EOTN network boundary (in ONP and PNP) p2p ODUk connections in each domain no MAC address collisions (no PBBN domains) ONP p2p ODUk S-VID Translation locations

6 EC frame tagging in PB, PBB, PBB-TE, EOTN NetworkEC type 1 frame tagEC type 2 frame tag PB + PBB I (PEB, PB, IB-BEB, BCB only) S-Tag Note: in B-VLAN an I-Tag or S+I-Tag is used To be defined PB + PBB II (PEB, PB, IB-BEB, TB-BEB, I-BEB, B- BEB, BCB) S-Tag Note: Inside PBB network the EC frames are carried inside a 2 nd EC frame, which is I-Tagged I-Tag PB + PBB-TE (PEB, PB, IB-BEB, BCB) S-Tag Note: in ESP an I-Tag or S+I-Tag is used To be defined EOTN (TEB,TB, OTN XC) S-TagTo be defined EC Type 1: EC carrying an EVC which is not-MAC-in-MAC encapsulated EC Type 2: EC carrying an EVC which is MAC-in-MAC encapsulated

7 EC awareness in PB, PBB, PBB-TE, EOTN NetworkEVC-to-EC mapping EC MEP/MIP functions EC AIS/LCK insertion EC-to-server mapping PB + PBB I (PEB, PB, IB-BEB, BCB only) PEP CNP PIP PNP CNP PIP PNP CNP PIP PNP PB + PBB II (PEB, PB, IB-BEB, TB-BEB, I-BEB, B- BEB, BCB) PEP CNP PIP CBP CNP PIP CBP PNP CNP PIP CBP PNP CNP PIP CBP PNP PB + PBB-TE (PEB, PB, IB-BEB, BCB) CEP CNP PIP PNP CNP PIP PNP CNP PIP PNP EOTN (TEB,TB, OTN XC) CEP CNP PNP ONP PNP ONP PNP ONP

8 Analysis of EC Type 2 Tagging options For deployment in PB+PBB I, PB+PBB-TE and EOTN

9 Untagged EC Type 2 frame format Untagged EC Type 2 frames are EVC frames with additional MAC Header including TYPE (89-10), B-SA, B-DA fields Format is present at input/output ports of EC MEP and MIP functions Untagged EC Type 2 OAM frames are OAM PDUs with additional MAC Header including TYPE (89-02), B-SA, B-DA MSDU Type EVC Frame C-DA C-SA Untagged EC Type 2 Frame (= untagged BSI Frame) B-DA B-SA C-DA C-SA MSDU Type = Type Untagged EC Type 2 OAM Frame B-DA B-SA OAM PDU Type = 89-02

10 Tagged EC Type 2 frame format alternatives There are three EC Type 2 frame tagging alternatives 1.I-Tagging 2.S-Tagging 3.I+S-Tagging TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 B-DA I-SID B-SA C-DA C-SA MSDU Type I-Tagged EC Type 2 Frame B-DA B-SA C-DA C-SA MSDU Type S-Tagged EC Type 2 Frame Type = S-VIDPCP DEI TPID = 88-a8 B-DA B-SA C-DA C-SA MSDU Type I+S-Tagged EC Type 2 Frame S-VIDPCP DEI TPID = 88-a8 TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 I-SID = S-VID TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 B-DA = f(B-DA,DBD) I-SID = f(ETH_FP) B-SA C-DA = B-DA C-SA = B-SA OAM PDU Type = I-Tagged EC Type 2 OAM Frame B-DA B-SA OAM PDU Type = S-Tagged EC Type 2 OAM Frame S-VIDPCP DEI TPID = 88-a8 TPID = 88-E7 I-SIDPCP DEI Res2 0 Res1 B-DA = f(B-DA,DBD) I-SID = S-VID C-DA = B-DA C-SA = B-SA B-SA OAM PDU Type = I+S-Tagged EC Type 2 OAM Frame S-VIDPCP DEI TPID = 88-a8

11 S-Tagged EC Type 2 implications in PB, PBB I, PBB-TE, EOTN networks New UNI-N port is to be specified to support this format  Today’s NID devices do not support MAC-in-MAC encapsulation  Next gen NID device can include this MAC-in-MAC encapsulation format with S-Tagged EC NNI ports with EC awareness can support this format  NNI ports: CNP, PNP, PIP, ONP NNI ports can treat the EC Type 1 and EC Type 2 signals as a single EC signal type; this behaviour is consistent with NNI requirement to be agnostic to the type of client encapsulation

12 I+S-Tagged EC Type 2 implications in PB, PBB I, PBB-TE, EOTN networks UNI-N and NNI ports need to distinguish between EC Type 1 and EC Type 2 signals; EC Type 1 and 2 signals require different tagging  Tag type to be administered on a per S-VID (EC) basis  Violates requirement that NNI is agnostic to client mapping  EC Type 1 MEP/MIP will not be able to detect EC Type 2 OAM  EC Type 2 MEP/MIP will not be able to detect EC Type 1 OAM New UNI-N port is to be specified to support this format  Today’s NID devices do not support MAC-in-MAC encapsulation  Next gen NID device can include this MAC-in-MAC encapsulation format with I+S-Tagged EC NNI ports with EC awareness do not support this format  CNP, PNP, PIP, ONP need to be extended with I+S-tagging capability, configurable on a per S-VID basis