1 / 32

Maarten Vissers 2010-11-08

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 2010-11-08. Introduction.

devorah
Download Presentation

Maarten Vissers 2010-11-08

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet ServicesAn overview of architecture and functionality in terms of 802.1Q modelling Maarten Vissers 2010-11-08

  2. Introduction E-OTN and PTN are multi domain, traffic engineeredtransport 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

  3. EOTN example MAC Relay functions are interconnected via OTN ODU connections MAC Relay functions interconnected via OTN ODU connections MAC Relay functions interconnected via OTN ODU connections Ethernet Switch Ethernet Switch OE OE NT OE OE OE OE OE OE OE OE OE OE ODU ODU ODU ODU ODU ODU ODU ODU ODU ODU ODU ODU ODU XC ODU XC OE OE OE OE OE OE OE OE OE OE OE OE OEO OEO OCH XC N-degree ROADM OCH XC N-degree ROADM OEO OEO OEO OEO NT ODU XC ODU XC OE OE OE OE NT Ethernet Switch Ethernet Switch OE OE OE OE OE OE OE OE OE OE OEO OEO OE OE OCH XC/ADM N-degree ROADM OCH XC/ADM N-degree ROADM OEO OEO OEO OEO OE OE OE OE OE OE OE OE NT ODU XC ODU XC OE OE OE OE OE OE OE OE OE OE OE OE OEO OEO OEO OCH XC N-degree ROADM OCH XC N-degree ROADM OCH XC N-degree ROADM OEO OEO OCH XC N-degree ROADM OCH XC N-degree ROADM OEO OEO OEO 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 MAC Relay functions interconnected via OTN ODU connections OEO OEO OEO OEO OEO NT SW OEO OEO OEO OEO OCH XC/ADM N-degree ROADM OCH XC/ADM N-degree ROADM OCH XC/ADM N-degree ROADM OCH XC/ADM N-degree ROADM OEO OEO OEO OEO OEO OEO OEO OEO OTN Access NT OTN Metro ODU XC OE OE NT OE OE OE OE OTN Core OEO OCH XC/ADM N-degree ROADM OEO OEO NT ODU XC OE OE NT OE OE OE OE OEO OCH XC N-degree ROADM OEO NT OEO NT OTN Metro NT ODU XC OE OE ODU XC OE OE OE OE OE OE OEO OCH XC/ADM N-degree ROADM NT OEO OEO OE OE OE OE OEO OCH XC N-degree ROADM OEO OEO NT Ethernet Network Termination Hybrid Ethernet & OTN Network Termination OTN/EOTN Switch OTN Network Termination NT NT NT

  4. 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.1Q features complemented by specific transport network features defined in Y.1731, G.8021, G.8031, G.8051 and G.8052

  5. 802.1Q Provider (Edge) Bridges(starting point) Customer System Provider Edge Bridge Customer Edge Ports C-VLAN Component 81-00 Table 8-1 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 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 PNP Provider Bridge 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 S-VLAN Component 88-a8 Table 8-2 Access Network’s Provider Bridge S-VLAN Component 88-a8 Table 8-2 Provider Bridge Provider Access Ports 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 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

  6. 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

  7. 802.1Q port types Specific Configurations of Common Port

  8. 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 Transparent Service Interface S-VLAN Component 88-a8 Table 8-2 EOTN Bridge 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 CNP PEP S-VLAN Component 88-a8 Table 8-2 Customer’s Provider Bridge CEP PAP CNP PEP S-VLAN Component 88-a8 Table 8-2 EOTN Bridge PNP RCAP ONP Individual S-VLAN Service Interface VLAN Component S-VLAN Component 88-a8 Table 8-2 S-VLAN Component 88-a8 Table 8-2 CNP PAP ONP ONP PNP ONP ONP • EOTN’s VLAN Component deploys: • ONP instead of PNP ports, and • transport Ethernet specific features

  9. 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 EISS EISS EISS EISS EISS EISS ISS EISS EISS EISS EISS EISS ISS EISS Frame filtering (8.6.3) Supports G.8031 SNC Protection Up MPs (6.17, 19.2, 19.3) Up MPs (6.17, 19.2, 19.3) O T N N E T W O R K P O R T s Port filtering entities (8.6.1/2/4/5) Port filtering entities (8.6.1/2/4/5) Supports Y.1731 OAM Down MPs (6.17, 19.2, 19.3) Down MPs (6.17, 19.2, 19.3) PNP equivalent Linktrace Output Multiplexer (19.5) Linktrace Output Multiplexer (19.5) Queuing entities (8.6.6/7/8) Queuing entities (8.6.6/7/8) Tagging Support of the EISS Support of the EISS 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

  10. 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 GFP Core Header PLI cHEC GFP Payload Header PTI PFI EXI UPI tHEC PTI=000: Client Data PFI=0: no Payload FCS EXI=000: Null Extension Header UPI=0000 0001: Frame Mapped Ethernet DA DA SA SA VLAN Tag TPID PCP DEI VID TYPE MAC SDU MAC FCS

  11. EOTN service set

  12. EOTN Requirementshttp://www.ieee802.org/1/files/public/docs2010/liaison-itut-sg15-oLS-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

  13. 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

  14. EOTN Edge Bridge – Extended service set Customer System EOTN Edge Bridge 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 Transparent Service Interface S-VLAN Component 88-a8 Table 8-2 EOTN Bridge PNP CNP 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 CNP PEP Customer’s Provider Bridge S-VLAN Component 88-a8 Table 8-2 CEP PAP CNP PEP S-VLAN Component 88-a8 Table 8-2 EOTN Bridge PNP RCAP ONP Individual S-VLAN Service Interface VLAN Component S-VLAN Component 88-a8 Table 8-2 S-VLAN Component 88-a8 Table 8-2 PNP CNP PAP ONP ONP bundled S-VLAN service interface ONP ONP 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 PNP CBP

  15. 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

  16. 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_identifierparameter 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) 1 16 3 1 1 2 24 I-Tag 18-octets UCA TPID = 88-E7 PCP DEI RES1 RES2 I-SID (ETH VC ID) DA SA

  17. EOTN port types(based on provider (edge) bridge ports) Specific Configurations of Common Port Same basic set of ports Additional Tag type Additional Port type

  18. EOTN (Edge) Bridge Customer System EOTN Edge Bridge C-VLAN Component 81-00 Table 8-1 C-VLAN Component 81-00 Table 8-1 EOTN Bridge T-VLAN Component with <T-Tag> and Table 8-3 C-VLAN Component 81-00 Table 8-1 CNP PEP CTSI T-VLAN Component <T-Tag> Table 8-3 CEP ONP ONP CNP PEP Customer’s Provider Bridge ONP ONP ONP Transparent Service Interface S-VLAN Component 88-a8 Table 8-2 PNP CNP EOTN Bridge Port Based Service Interface CNP ONP T-VLAN Component <T-Tag> Table 8-3 C-VLAN Component 81-00 Table 8-1 C-VLAN Component 81-00 Table 8-1 ONP ONP C-VLAN Component 81-00 Table 8-1 CNP PEP Customer’s Provider Bridge S-VLAN Component 88-a8 Table 8-2 ONP ONP CEP PAP CNP PEP S-VLAN Component 88-a8 Table 8-2 PNP RCAP Individual S-VLAN Service Interface S-VLAN Component 88-a8 Table 8-2 S-VLAN Component 88-a8 Table 8-2 PNP 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 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 PNP CBP

  19. 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 GFP Core Header PLI cHEC GFP Payload Header PTI PFI EXI UPI tHEC PTI=000: Client Data PFI=0: no Payload FCS EXI=000: Null Extension Header UPI=0000 0001: Frame Mapped Ethernet DA DA SA SA Transport-VLAN Tag TPID=<T-Tag> PCP DEI T-VID TYPE MAC SDU MAC FCS

  20. EOTN summary

  21. 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

  22. PTN

  23. Q.9/15 liaison on G.ptneq: “Next Step”http://www.ieee802.org/1/files/public/docs2010/new-itu-1-G-ptneq-IEEE-Final-0510-v1.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.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

  24. 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

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

  26. 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

  27. Hierarchy for multiple domains Domain 1 Domain 2 Domain 3 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 VC VP VP VP V S V S VS VS VS VC VP VC VS VP VC VS VP VS VC VP VS VC VP VS VC VP VS

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

  29. 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 CNP PEP Customer’s Provider Bridge S-VLAN Component 88-a8 Table 8-2 CEP PAP E-PTN Bridge CNP PEP PTNP T-VLAN Component <T-Tag> Table 8-3 S-VLAN Component 88-a8 Table 8-2 PTNP PTNP PNP RCAP Individual S-VLAN Service Interface S-VLAN Component 88-a8 Table 8-2 S-VLAN Component 88-a8 Table 8-2 PNP CNP PAP PTNP PTNP S-VLAN bundled service interface CNP PNP ONPs are replaced by PTNPs 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 PNP CBP

  30. 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

  31. Annex

  32. Transport network specificEthernet 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)

More Related