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

Name: Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and.
Uploaded: 2017-08-23T04:28:50+00:00
Duration: PTM47S19
Channel: Bailey Walker
Description: 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 in terms of 802.1Q modelling Maarten Vissers

Introduction E-OTN and PTN are multi domain, traffic engineered transport networks which support P2P, P2MP, RMP and MP2MP Ethernet services OTN network contains multiple OTN carrier networks 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 OTN Metro OTN Core OTN Metro
MAC Relay functions interconnected via OTN ODU connections MAC Relay functions are interconnected via OTN ODU connections OE OEO OCH XC N-degree ROADM ODU XC Ethernet Switch NT NT OTN Metro ODU OE ODU XC OE NT OE OEO OCH XC N-degree ROADM ODU XC Ethernet Switch OE OE OE OE OEO OEO OCH XC/ADM N-degree ROADM OTN Core OCH XC/ADM N-degree ROADM OEO OEO ODU NT OE ODU XC OE NT OEO OE OCH XC/ADM N-degree ROADM ODU XC OE OE OE OE OEO OCH XC N-degree ROADM OEO OCH XC/ADM N-degree ROADM OEO OCH XC N-degree ROADM NT OEO OEO NT OEO OCH XC N-degree ROADM OTN Metro NT ODU OE ODU XC ODU OE OEO OCH XC N-degree ROADM OEO OCH XC/ADM N-degree ROADM ODU XC OE OE OE OE OE OE OEO NT Ethernet mapping in Network Termination devices (Packet (e.g. Ethernet) NTs and hybrid Packet/OTN NTs). Packet switching at selected OTN XC systems located in metro edge and metro core nodes. OEO OCH XC/ADM N-degree ROADM OEO OE OE OE OE OEO OCH XC N-degree ROADM OEO OEO MAC Relay functions interconnected via OTN ODU connections MAC Relay functions are interconnected via OTN ODU connections or S- or I-Tagged LANs OEO OCH XC/ADM N-degree ROADM NT OEO OE OCH XC/ADM N-degree ROADM ODU XC Ethernet Network Termination Hybrid Ethernet & OTN Network Termination OTN Network Termination NT SW OTN/EOTN Switch NT NT

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 physical ports are replaced by G.709/G.7041 physical ports and TPMR type reserved address transparency EOTN deploys the 802.1Q features complemented by specific transport network features defined in Y.1731, G.8021, G.8031, G.8051 and G.8052

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

802.1Q port types Many of the 802.1Q 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-a8), Acceptable Frames Type untagged set member Up MEPs, Up MIPs Down MIPs, Down MEPs Down MEP below clause 8.5

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

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

OTN Network Port functionality
OTN Network Ports combine 802.1Q’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) Supports G.8031 SNC Protection EISS EISS Up MPs (6.17, 19.2, 19.3) O T N E W R K P s Up MPs (6.17, 19.2, 19.3) EISS EISS Port filtering entities (8.6.1/2/4/5) Port filtering entities (8.6.1/2/4/5) Supports Y.1731 OAM EISS EISS Down MPs (6.17, 19.2, 19.3) Down MPs (6.17, 19.2, 19.3) PNP equivalent EISS EISS Linktrace Output Multiplexer (19.5) Linktrace Output Multiplexer (19.5) EISS EISS Queuing entities (8.6.6/7/8) Queuing entities (8.6.6/7/8) EISS EISS Tagging Support of the EISS Support of the EISS ISS ISS Support of the ISS by additional technologies (6.15) Support of the ISS by additional technologies (6.15) GFP-F OTN specific OTN ODU Down MP OTN ODU Down MP OTN other functions OTN other functions

ODUk with GFP-F encapsulated Ethernet frames with VLAN Tag
16 3808 ODUk 4 GFP IDLEs ODUk bit rates 1.25G 2.5G 3.75G 5G 6.25G 7.5G 8.75G 10G 11.25G : 100G PLI cHEC GFP Core Header PTI PFI EXI UPI tHEC GFP Payload Header PTI=000: Client Data PFI=0: no Payload FCS EXI=000: Null Extension Header UPI= : Frame Mapped Ethernet DA DA SA SA TPID PCP DEI VID VLAN Tag TYPE MAC SDU MAC FCS

EOTN service set

EOTN Requirements http://www. ieee802
Transport all MEF (G.8011.x) services over OTN Transport all 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

EOTN Edge Bridge – Extended service set
EOTN is required to support any type of Tagged service, including bundled S-Tagged 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

EOTN Edge Bridge – Extended service set
Customer System EOTN Edge Bridge C-VLAN Component 81-00 Table 8-1 VLAN Component C-VLAN Component 81-00 Table 8-1 C-VLAN Component 81-00 Table 8-1 CNP PEP CTSI CEP CNP PEP Customer’s Provider Bridge EOTN Bridge Transparent Service Interface S-VLAN Component 88-a8 Table 8-2 CNP PNP VLAN Component Port Based Service Interface ONP ONP CNP C-VLAN Component 81-00 Table 8-1 C-VLAN Component 81-00 Table 8-1 C-VLAN Component 81-00 Table 8-1 ONP ONP ONP S-VLAN Component 88-a8 Table 8-2 CNP PEP S-VLAN Component 88-a8 Table 8-2 S-VLAN Component 88-a8 Table 8-2 Customer’s Provider Bridge CEP PAP CNP PEP EOTN Bridge S-VLAN Component 88-a8 Table 8-2 RCAP PNP VLAN Component ONP Individual S-VLAN Service Interface PNP ONP ONP CNP PAP ONP ONP bundled S-VLAN service interface CNP PNP Customer’s I-BEB/B-BEB/T-BEB BSI transparent service interface T- Component Reuse of existing CNP and CBP ports on the EEB supports BSI individual and/or bundled services, transparent services and S-VID/S-PCP/S-DEI preserving (bundled) S-Tagged services CNP PIP CNP BSI transparent service interface I- Component CNP PIP CNP BSI (bundled) service interface CBP PIP CNP BSI (bundled) service interface B- Component CBP CBP PNP BSI transparent service interface CNP CBP PNP

EOTN (Edge) Bridges – Transparency
Support of Transparent Services by the EOTN’s Ethernet service (ETH VC) layer requires TPMR type transparency (Table 8-3) 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

Choice of Tag in EOTN (Edge) Bridge
Tag choice New Transport VLAN Tag with 12-bit T-VID (ETH VC ID) & TPMR Reserved Address transparency (table 8-3/802.1Q) 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) 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; EtherType 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 16 3 1 12 New VLAN Tag 4-octets TPID = xx-xx PCP DEI T-VID (ETH VC ID) 16 3 1 1 1 2 24 I-Tag 18-octets TPID = 88-E7 PCP DEI UCA RES1 RES2 I-SID (ETH VC ID) DA SA

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 S / T S C/S/T T Admit Only VLAN-tagged frames Y N Y/N Admit Only Untagged and Priority-tagged frames Admit All frames ? PVID Enable Ingress Filtering Member of untagged set O - Up MEP N|Y Up MIP Down MIP Down MEP Down MEP below c8.5 Same basic set of ports Additional Tag type Additional Port type

EOTN (Edge) Bridge T-VLAN Component with <T-Tag> and Table 8-3
Customer System EOTN Edge Bridge EOTN Bridge T-VLAN Component with <T-Tag> and Table 8-3 C-VLAN Component 81-00 Table 8-1 C-VLAN Component 81-00 Table 8-1 C-VLAN Component 81-00 Table 8-1 CNP PEP CTSI T-VLAN Component <T-Tag> Table 8-3 ONP ONP CEP CNP PEP Customer’s Provider Bridge ONP ONP ONP Transparent Service Interface S-VLAN Component 88-a8 Table 8-2 CNP PNP EOTN Bridge Port Based Service Interface T-VLAN Component <T-Tag> Table 8-3 ONP CNP ONP ONP C-VLAN Component 81-00 Table 8-1 C-VLAN Component 81-00 Table 8-1 C-VLAN Component 81-00 Table 8-1 S-VLAN Component 88-a8 Table 8-2 CNP PEP S-VLAN Component 88-a8 Table 8-2 S-VLAN Component 88-a8 Table 8-2 Customer’s Provider Bridge ONP ONP CEP PAP CNP PEP S-VLAN Component 88-a8 Table 8-2 RCAP PNP Individual S-VLAN Service Interface 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 (multi-vid E-Tree/E-LAN), independent ingress/egress VID translation, disabled xSTP/xVRP, Y.1731/G.8021 OAM and G.8031 Ethernet VLAN SNC protection. CNP PAP PNP bundled S-VLAN service interface CNP PNP Customer’s I-BEB/B-BEB/T-BEB BSI transparent service interface T- Component CNP PIP CNP BSI transparent service interface I- Component CNP PIP CNP BSI (bundled) service interface CBP PIP CNP BSI (bundled) service interface B- Component CBP CBP PNP BSI transparent service interface CNP CBP PNP

ODUk with GFP-F encapsulated Ethernet frames with T-VLAN Tag
16 3808 ODUk 4 GFP IDLEs ODUk bit rates 1.25G 2.5G 3.75G 5G 6.25G 7.5G 8.75G 10G 11.25G : 100G PLI cHEC GFP Core Header PTI PFI EXI UPI tHEC GFP Payload Header PTI=000: Client Data PFI=0: no Payload FCS EXI=000: Null Extension Header UPI= : Frame Mapped Ethernet DA DA SA SA TPID=<T-Tag> PCP DEI T-VID Transport-VLAN Tag TYPE MAC SDU MAC FCS

EOTN summary

EOTN Summary EOTN requires a minimal extension of 802.1Q 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

Q. 9/15 liaison on G. ptneq: “Next Step” http://www. ieee802
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.1Q to support VC, VP, VS stacking in single and multi-domain scenarios. ITU-T Q9/15 would like to progress this work in cooperation with IEEE 802.1

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

PTN Network Port (PTNP)
Frame filtering (8.6.3) EISS EISS Up MPs (6.17, 19.2, 19.3) EISS Port filtering entities (8.6.1/2/4/5) EISS EISS ISS Down MPs (6.17, 19.2, 19.3) EISS Linktrace Output Multiplexer (19.5) P T N EISS Support of the EISS (6.9) VC Tag ISS NxISS EISS Down MPs (6.17, 19.2, 19.3) EISS Linktrace Output Multiplexer (19.5) EISS Support of the EISS (6.9) VP Tag ISS ISS ISS Down MPs (6.17,19.2) ISS Linktrace Output Multiplexer (19.5) ISS ISS Priority Tag (6.13) VS Tag ISS ISS ISS ISS Support of the ISS (6.7) MAC PTN-Tagged LAN

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 P2P VLANs (without MAC based forwarding) set up by transport network management and control systems

Hierarchy for multiple domains
In multi-domain case the layer relationship is relative and the names represent their role in each domain; some examples: Top Default case, no additional hierarchy Middle VP in Domain 1 is VC in Domain 2 VP in Domain 2 is VC in Domain 3 Bottom 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 Domain 1 Domain 2 Domain 3 VC VP V S VP V S VP VS VS VS VC VP VC VS VP VC VS VP VS VC VP VS VC VP VS VC VP VS Page 27

Domain interconnect examples VLAN Hierarchy Extension
DOMAIN A DOMAIN B Up MPs (6.17, 19.2, 19.3) Linktrace Output Multiplexer (19.5) Support of the EISS (6.9) Down MPs (6.17, 19.2, 19.3) Priority Tag (6.13) Down MPs (6.17,19.2) Support of the ISS (6.7) Port filtering entities (8.6.1/2/4/5) EISS ISS NxISS MAC Frame filtering (8.6.3) VCAVPAVSAVPA=VCBVPBVSB VCAVPAVSA=VCBVPBVSB

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

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

Transport network specific Ethernet features
Alarm suppression Additional Y.1731, G.8021, G.8031, 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.1Q); e.g. could also be 16k, 32k, 64k, 128k,... VLAN connection management with network management or GMPLS control plane without spanning tree protocol (MSTP) and without VLAN registration protocol (MVRP)

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

Similar presentations

Presentation on theme: "Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

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

Similar presentations

Presentation on theme: "Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and."— Presentation transcript:

Similar presentations

About project

Feedback