Multi Domain Traffic Engineered Transport Networks EOTN PTN

Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P 2 P, P 2 MP, RMP and MP 2 MP Ethernet Services An overview of architecture and functionality in terms of 802. 1 Q modelling Maarten Vissers 2010 -11 -08

Introduction E-OTN and PTN are multi domain, traffic engineered transport networks which support P 2 P, P 2 MP, RMP and MP 2 MP Ethernet services OTN network contains multiple OTN carrier networks contain OTN access, metro and core domains OTN network contains OTN network termination (NT), electrical switching and optical switching (SW) equipment OTN equipment at edge of domains is extended with Ethernet Switch functionality

EOTN example OTN Access Ethernet Switch ODU ODU OCH XC/ADM OCH XC N-degree ROADM NT ODU XC OEO OEO OEO OCH XC/ADM N-degree ROADM OCH XC/ADM OTN Core ODU XC OE OE OE NT Ethernet Switch OE OE OCH XC/ADM OE OE OEO OEO ODU ODU OEO OEO OE OE NT OTN Metro OEO OEO OEO OCH XC N-degree ROADM OE OE OCH XC/ADM OCH XC N-degree ROADM OEO OEO MAC Relay functions are interconnected via OTN ODU connections or Sor I-Tagged LANs N-degree ROADM OCH XC/ADM N-degree ROADM OTN Network Termination OCH XC N-degree ROADM OCH XC/ADM NT OEO OEO N-degree ROADM OE OE ODU XC OEO OEO OCH XC N-degree ROADM OE OE ODU XC OEO OEO OE OE Ethernet Switch ODU ODU OEO OEO OEO OE OE ODU XC OE OE OTN Metro OEO OEO OE OE ODU ODU NT OE OE Ethernet Switch OE OE NT OCH XC N-degree ROADM NT NT MAC Relay functions are interconnected via OTN ODU connections ODU XC OE OE OE NT Ethernet Network Termination NT Hybrid Ethernet & OTN Network Termination SW OTN/EOTN Switch

EOTN and PBN EOTN adds one transport VLAN layer on top of its OTN layer stack EOTN can be viewed in this respect as a transport PBN in which the 802. 3 physical ports are replaced by G. 709/G. 7041 physical ports and TPMR type reserved address transparency EOTN deploys the 802. 1 Q features complemented by specific transport network features defined in Y. 1731, G. 8021, G. 8031, G. 8051 and G. 8052 4

802. 1 Q Provider (Edge) Bridges (starting point) Provider Network Ports Provider Bridge S-VLAN Component 88 -a 8 Table 8 -2 Provider Network Ports S-VLAN Component with 88 -a 8 and Table 8 -2 Provider Edge Bridge Customer Edge Ports Customer System C-VLAN Component 81 -00 Table 8 -1 C-tagged service interfaces (CTSI) Provider Edge Port S-tagged service interface (STSI) Customer Network Port C-tagged service interfaces C-VLAN Component 81 -00 Table 8 -1 Provider Access Ports S-VLAN Component 88 -a 8 Table 8 -2 Customer’s Provider Bridge S-VLAN PNP Component 88 -a 8 Table 8 -2 Port-based service interface (PBSI) Access Network’s Provider Bridge S-VLAN Component 88 -a 8 Table 8 -2 Port-based service interface Remote customer service interfaces (RCSI) Provider Network Ports S-VLAN Components operating on TPID 88 -a 8 with S-VLAN Reserved Address transparency (Table 8 -2), IVL and SVL (multi-vid E-Tree), VID translation, x. STP/x. VRP 5

802. 1 Q port types Many of the 802. 1 Q port types are variations of a common port which supports a single VLAN multiplexing instance (clause 6. 9) with configurable: Tag type (TPIDs: 81 -00, 88 -a 8), Acceptable Frames Type untagged set member Up MEPs, Up MIPs Down MIPs, Down MEPs Down MEP below clause 8. 5 6

802. 1 Q port types Specific Configurations of Common Port CEP PEP CNP port based CNP tag’d PNP RCAP PAP Common Port Tag type C C S S S C/S Admit Only VLAN-tagged frames Y Y N Y/N Admit Only Untagged and Prioritytagged frames Y N N N Y Y/N Admit All frames Y Y N ? N Y/N PVID Y Y Y/N N Y/N Enable Ingress Filtering N Member of untagged set O O Y Up MEP N N Y Up MIP Y N Down MIP Y Down MEP below c 8. 5 Y N - Y Y/N Y N N N Y/N N|Y Y Y N N Y/N N N N N Y/N Y N N|Y Y N Y/N 7

EOTN (Edge) Bridges (based on provider (edge) bridges) Customer System EOTN Edge Bridge OTN Network Ports V L A N EOTN Bridge ONP VLAN Component ONP ONP EOTN Bridge ONP ONP VLAN Component ONP C o m p o n e n t CNP C-VLAN Component PEP Component 81 -00 Table 8 -1 CEP Table 8 -1 PEP Table 8 -1 CTSI Customer’s Provider Bridge Transparent Service S-VLAN Interface PNP Component 88 -a 8 Port Based Service Table 8 -2 Interface CNP CNP CNP C-VLAN Component PEP Component 81 -00 8 -1 CEP Table 8 -1 PEP Table 8 -1 Individual S-VLAN Service Interface PAP S-VLAN Component 88 -a 8 Table 8 -2 RCAP 88 -a 8 Table 8 -2 Customer’s Provider Bridge S-VLAN PNP Component 88 -a 8 Table 8 -2 PNP EOTN’s VLAN Component deploys: • ONP instead of PNP ports, and • transport Ethernet specific features 8

OTN Network Port functionality OTN Network Ports combine 802. 1 Q’s Provider Network Port functionality with an OTN physical layer Ethernet MEP and MIP functions Includes support for Y. 1731 Ethernet OAM, G. 8021 OAM processing and G. 8031 APS OAM Ethernet to OTN (de)mapping/(de)muxing functions: Support of the EISS Tag insertion/extraction Support of the ISS by additional technologies GFP-F/OTN Frame filtering (8. 6. 3) EISS Up MPs (6. 17, 19. 2, 19. 3) EISS Port filtering entities (8. 6. 1/2/4/5) EISS PNP equivalent Down MPs (6. 17, 19. 2, 19. 3) EISS Linktrace Output Multiplexer (19. 5) EISS Queuing entities (8. 6. 6/7/8) EISS OTN specific Support of the EISS Support of the ISS by additional technologies (6. 15) OTN ODU Down MP OTN other functions EISS O T N N E T W O R K P O R T s Up MPs (6. 17, 19. 2, 19. 3) EISS Port filtering entities (8. 6. 1/2/4/5) EISS Down MPs (6. 17, 19. 2, 19. 3) EISS Supports G. 8031 SNC Protection Supports Y. 1731 OAM Linktrace Output Multiplexer (19. 5) EISS Queuing entities (8. 6. 6/7/8) EISS Support of the ISS by additional technologies (6. 15) OTN ODU Down MP OTN other functions Tagging GFP-F

ODUk with GFP-F encapsulated Ethernet frames with VLAN Tag 16 3808 O D U k GFP IDLEs PTI PFI PLI EXI c. HEC t. HEC UPI DA DA TPID TYPE SA SA PCP DEI ODUk bit rates 1. 25 G 2. 5 G 3. 75 G 5 G 6. 25 G 7. 5 G 8. 75 G 10 G 11. 25 G : : 100 G 4 MAC SDU MAC FCS VID GFP Core Header GFP Payload Header PTI=000: Client Data PFI=0: no Payload FCS EXI=000: Null Extension Header UPI=0000 0001: Frame Mapped Ethernet VLAN Tag

EOTN service set

EOTN Requirements http: //www. ieee 802. org/1/files/public/docs 2010/liaison-itut-sg 15 -o. LS-197 -0710. docx Transport all MEF (G. 8011. x) services over OTN Transport all 802. 1 service interfaces over OTN Support the management of all above services simultaneously using a single forwarding function Transport by using a unique edge-to-edge layer that is separated from the customer 12

EOTN Edge Bridge – Extended service set EOTN is required to support any type of Tagged service, including bundled STagged and I-Tagged services, over a single Ethernet (ETH) layer EOTN Edge Bridge can support those services by deploying additional CNPs and CBPs and connecting those to customer PIPs and CBPs as illustrated in the next slide 13

EOTN Edge Bridge – Extended service set Customer System EOTN Edge Bridge CNP C-VLAN Component PEP Component 81 -00 Table 8 -1 CEP Table 8 -1 PEP Table 8 -1 CTSI Customer’s Provider Bridge EOTN Bridge VLAN ONP Component ONP ONP V L A N CNP CNP EOTN Bridge ONP ONP VLAN Component ONP Reuse of existing CNP and CBP ports on the EEB supports BSI individual and/or bundled services, transparent services and SVID/S-PCP/S-DEI preserving (bundled) STagged services C o m p o n e n t Transparent Service S-VLAN Interface PNP Component 88 -a 8 Port Based Service Table 8 -2 Interface CNP C-VLAN Component PEP Component 81 -00 8 -1 CEP Table 8 -1 PEP Table 8 -1 Individual S-VLAN Service Interface bundled S-VLAN service interface CNP PAP S-VLAN Component 88 -a 8 S-VLAN 88 -a 8 Table 8 -2 RCAP Component Table 8 -2 88 -a 8 PAP Table 8 -2 PNP Customer’s Provider Bridge S-VLAN PNP Component 88 -a 8 PNP Table 8 -2 Customer’s I-BEB/B-BEB/T-BEB BSI transparent service interface CNP PIP TComponent CNP BSI transparent service interface CNP BSI (bundled) service interface CBP PIP ICNP Component PIP CNP CBP BPNP Component CBP PNP BSI (bundled) service interface CBP BSI transparent service interface CNP 14

EOTN (Edge) Bridges – Transparency Support of Transparent Services by the EOTN’s Ethernet service (ETH VC) layer requires TPMR type transparency (Table 83) S-Tag does not provide such transparency EOTN should deploy a new VLAN Tag associated with: TPMR type transparency Transport network type operation, management and control 15

Choice of Tag in EOTN (Edge) Bridge Tag choice 16 New VLAN Tag 4 -octets TPID = xx-xx 3 1 PCP DEI New Transport VLAN Tag with 12 -bit T-VID (ETH VC ID) & TPMR Reserved Address transparency (table 8 -3/802. 1 Q) 12 T-VID (ETH VC ID) TPID = 88 -E 7 PCP RES 1 I-Tag 18 -octets DEI UCA I-Tag with 24 -bit I-SID; UCA-bit deals with T-VLAN (ETH VC) frames with or without network MAC addresses (N-DA, S-DA) 16 3 1 1 1 2 24 RES 2 I-SID (ETH VC ID) DA SA Tag is terminated in the “Support of the EISS” functions in ONP vlan_identifier parameter represents in EM_UNITDATA the 12 bit T-VLAN ID or 24 -bit I-SID Existing devices already support VLAN Tag with 12 -bit ID; Ether. Type is configurable per port Devices do not support an I-SID based vlan_identifier parameter VLAN Tag with new “Transport VLAN” type TPID value is best fit

EOTN port types (based on provider (edge) bridge ports) Specific Configurations of Common Port CEP PEP CNP port based CNP tag’d PNP RCAP PAP Common Port ONP Tag type C C S/T S S C/S/T T Admit Only VLAN-tagged frames Y Y N Y/N Y Admit Only Untagged and Prioritytagged frames Y N N N Y Y/N N Admit All frames Y Y N ? N Y/N N PVID Y Y Y/N N Same basic set of ports N Y Member of untagged set O Tag O Y Additional type Up MEP N N Y Y Additional Port type N - Y Y/N N N Y/N N|Y Up MIP Y N N|Y Y Y N N Y/N Y Down MEP N N N N Y/N N|Y Down MEP below c 8. 5 Y N N|Y Y N Y/N N Enable Ingress Filtering 17

EOTN (Edge) Bridge Customer System EOTN Edge Bridge EOTN Bridge CNP ONP EOTN Bridge T-VLAN ONP Component ONP <T-Tag> ONP Table 8 -3 ONP T-VLAN component is a VLAN type Component operating on TPID: <T-Tag> with TPMR Reserved Address transparency (Table 8 -3), ONP instead of PNP ports, IVL and SVL (multivid E-Tree/E-LAN), independent ingress/egress VID translation, disabled x. STP/x. VRP, Y. 1731/G. 8021 OAM and G. 8031 Ethernet VLAN SNC protection. ONP T-VLAN Component with <T-Tag> and Table 8 -3 T-VLAN ONP Component ONP <T-Tag> ONP Table 8 -3 ONP C-VLAN Component PEP Component 81 -00 Table 8 -1 CEP Table 8 -1 PEP Table 8 -1 CTSI Customer’s Provider Bridge Transparent Service S-VLAN Interface PNP Component 88 -a 8 Port Based Service Table 8 -2 Interface CNP CNP C-VLAN Component PEP Component 81 -00 8 -1 CEP Table 8 -1 PEP Table 8 -1 PAP CNP Individual S-VLAN Service Interface S-VLAN Component 88 -a 8 S-VLAN 88 -a 8 Table 8 -2 RCAP Component Table 8 -2 88 -a 8 PAP Table 8 -2 CNP bundled S-VLAN service interface PNP Customer’s Provider Bridge S-VLAN PNP Component 88 -a 8 PNP Table 8 -2 Customer’s I-BEB/B-BEB/T-BEB BSI transparent service interface CNP PIP TComponent CNP BSI transparent service interface CNP BSI (bundled) service interface CBP PIP ICNP Component PIP CNP CBP BPNP Component CBP PNP BSI (bundled) service interface CBP BSI transparent service interface CNP 18

ODUk with GFP-F encapsulated Ethernet frames with T-VLAN Tag 16 3808 O D U k GFP IDLEs PTI PFI PLI EXI c. HEC t. HEC UPI DA DA SA SA TPID=<T-Tag> PCP TYPE DEI ODUk bit rates 1. 25 G 2. 5 G 3. 75 G 5 G 6. 25 G 7. 5 G 8. 75 G 10 G 11. 25 G : : 100 G 4 MAC SDU MAC FCS T-VID GFP Core Header GFP Payload Header PTI=000: Client Data PFI=0: no Payload FCS EXI=000: Null Extension Header UPI=0000 0001: Frame Mapped Ethernet Transport-VLAN Tag

EOTN summary

EOTN Summary EOTN requires a minimal extension of 802. 1 Q functions and ports: Additional OTN Network Port with a Support of the EISS function which operates on a new T-Tag associated with TPMR Reserved Address transparency Existing CNPs and CBPs with a Support of the EISS function which operates on a new T-Tag associated with TPMR Reserved Address transparency

PTN

Q. 9/15 liaison on G. ptneq: “Next Step” http: //www. ieee 802. org/1/files/public/docs 2010/new-itu-1 -G-ptneq-IEEE-Final-0510 -v 1. ppt PTN VC/VP/VS layers may be supported by the Ethernet technology including ETH OAM(Y. 1731, G. 8021), ETH protection switching(G. 8031, G. 8032), ETH connection management (G. 8051, G. 8052). The use of Ethernet technology in PTN requires an extension of the tagging option defined in 802. 1 Q to support VC, VP, VS stacking in single and multi-domain scenarios. ITU-T Q 9/15 would like to progress this work in cooperation with IEEE 802. 1 23

Ethernet PTN network contains a PBN like transport VLAN (ETH VC) layer (same as EOTN) Those transport VLANs may be transported in P 2 P server VLANs (ETH VPs) instead of in P 2 P ODUs in EOTN, or P 2 P LSPs in MPLS-TP/VPLS This requires PTN Network Ports (PTNP) which support 2 -stage VLAN multiplexing and optional prioritytagging 24

PTN Network Port (PTNP) Frame filtering (8. 6. 3) EISS Up MPs (6. 17, 19. 2, 19. 3) EISS Port filtering entities (8. 6. 1/2/4/5) EISS ISS Down MPs (6. 17, 19. 2, 19. 3) P T N P EISS Linktrace Output Multiplexer (19. 5) ISS EISS Support of the EISS (6. 9) Nx. ISS VC Tag EISS Down MPs (6. 17, 19. 2, 19. 3) EISS Linktrace Output Multiplexer (19. 5) EISS Support of the EISS (6. 9) ISS ISS Down MPs (6. 17, 19. 2) ISS Linktrace Output Multiplexer (19. 5) ISS Priority Tag (6. 13) ISS VP Tag VS Tag Support of the ISS (6. 7) MAC PTN-Tagged LAN 25

Hierarchy Multi-stage connection hierarchy is a normal means deployed in the latest generation circuit and packet transport networks to scale these networks OTN supports up to 4 ODU multiplexing stages (more to follow) MPLS-TP supports an unrestricted number of LSP multiplexing stages An Ethernet based PTN should have the capability to support such multi-stage connection hierarchy VLAN Tags should therefore be stackable VP and VS transport VLANs are P 2 P VLANs (without MAC based forwarding) set up by transport network management and control systems 26

Hierarchy for multiple domains Domain 1 Domain 2 VP VS VC VP VS V S Domain 3 V S VP VS In multi-domain case the layer relationship is relative and the names represent their role in each domain; some examples: Top VC VP VS Middle VP in Domain 1 is VC in Domain 2 VP in Domain 2 is VC in Domain 3 Bottom VC VP VS Default case, no additional hierarchy VC VP VS VS in Domain 1 is VC in Domain 2 VS in Domain 2 is VC in Domain 3 Each domain operates on the lower three layers and is unaware of the higher layers Page 27

Domain interconnect examples VLAN Hierarchy Extension DOMAIN A DOMAIN B Frame filtering (8. 6. 3) EISS Up MPs (6. 17, 19. 2, 19. 3) EISS Port filtering entities (8. 6. 1/2/4/5) EISS ISS EISS Down MPs (6. 17, 19. 2, 19. 3) EISS Linktrace Output Multiplexer (19. 5) EISS Support of the EISS (6. 9) Nx. ISS EISS Nx. ISS Down MPs (6. 17, 19. 2, 19. 3) EISS Down MPs (6. 17, 19. 2, 19. 3) Nx. ISS EISS Down MPs (6. 17, 19. 2, 19. 3) EISS Up MPs (6. 17, 19. 2, 19. 3) EISS Linktrace Output Multiplexer (19. 5) EISS Support of the EISS (6. 9) ISS Down MPs (6. 17, 19. 2) ISS ISS ISS Down MPs (6. 17, 19. 2) ISS Linktrace Output Multiplexer (19. 5) ISS ISS Priority Tag (6. 13) ISS ISS Linktrace Output Multiplexer (19. 5) ISS Priority Tag (6. 13) ISS Down MPs (6. 17, 19. 2, 19. 3) ISS Linktrace Output Multiplexer (19. 5) ISS Priority Tag (6. 13) ISS Support of the ISS (6. 7) MAC MAC ISS VCA VPA VSA VPA=VCB VPB VSB VCA VPA VSA=VCB VPB VSB 28

E-PTN (Edge) Bridges (based on eotn (edge) bridges) PTN Network Ports PTNP E-PTN Bridge T-VLAN PTNP Component PTNP <T-Tag> PTNP Table 8 -3 PTNP ONPs are replaced by PTNPs PTNP T-VLAN Component with <T-Tag> and Table 8 -3 E-PTN Bridge T-VLAN PTNP Component PTNP <T-Tag> PTNP Table 8 -3 PTNP Customer System E-PTN Edge Bridge CNP PEP CNP MPEP C-VLAN Component C-VLAN 81 -00 Component Table 8 -1 CEP Table 81 -00 Table 8 -1 CTSI Customer’s Provider Bridge Transparent Service S-VLAN Interface PNP Component 88 -a 8 Port Based Service Table 8 -2 Interface CNP CNP C-VLAN Component PEP Component 81 -00 8 -1 CEP Table 8 -1 PEP Table 8 -1 PAP Individual S-VLAN Service Interface PAP CNP S-VLAN bundled service interface PNP CNP MPNP CNP S-VLAN Component 88 -a 8 S-VLAN Table 8 -2 RCAP Table 8 -2 Component 88 -a 8 Table 8 -2 BSI transparent service interface CNP Customer’s Provider Bridge S-VLAN PNP Component 88 -a 8 PNP Table 8 -2 Customer’s I-BEB/B-BEB/T-BEB TPIP Component CNP BSI transparent service interface CNP BSI (bundled) service interface CBP PIP ICNP Component PIP CNP CBP BPNP Component CBP PNP BSI (bundled) service interface CBP BSI transparent service interface CNP 29

PTN Summary An Ethernet based PTN requires the development of a PTN Network Port (PTNP), which supports 2 stage VLAN multiplexing and transport specific Ethernet features A stackable VLAN Tag is required to support the single and multi-domain ETH VC/VP/VS (VLAN) hierarchy 30

Annex 31

Transport network specific Ethernet features Alarm suppression Additional Y. 1731, G. 8021, G. 8032 Ethernet OAM frames G. 8031 VLAN linear protection (ETH SNC protection) G. 8032 VLAN ring protection VLAN IDs have a link local scope and VID Translation is used to map the local VID on each link onto the Relay VID inside a node Number of FIDs is equipment specific and not limited to 4094 (as specified in 8. 8. 8/802. 1 Q); e. g. could also be 16 k, 32 k, 64 k, 128 k, . . . VLAN connection management with network management or GMPLS control plane without spanning tree protocol (MSTP) and without VLAN registration protocol (MVRP) 32