Carrier grade Ethernet the Ethernet Upfate

Transcription

1 Carrier grade Ethernet the Ethernet Upfate ITG-FG Next Generation Networks 19. Sitzung am Darmstadt Thomas Martin Knoll TU Chemnitz - Professur Daten- und Kommunikationstechnik Telefon knoll@etit.tu-chemnitz.de Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

2 Table of contents 1. Starting point: L3 and L VPN services. Metro Ethernet Forum 3. IEEE 80.3 / 80.1 variants (VLAN XC, Q-in-Q, MAC-in-MAC PBB/PBT) 4. Ethernet protection and limitations 5. T-MPLS 6. ITU-T hints / Atrica 7. Summary / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

3 VPN MEF 80.3 Prot. T-MPLS Hints Summary Starting Point Current needs of networked computer users Private User: fast and cheap Internet connection (IP connectivity) is sufficient Business User: fast and cheap Internet connection (IP connectivity) + IP VPN between subsidiaries and home office workers Future User: fast and cheap Internet connection (IP connectivity) + ease of mind Ethernet VPN between subsidiaries and home office workers AND maybe friends, clubs etc. multi tunnel support Ethernet connectivity as provider service: Ethernet interconnect Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll 3 / 48

4 VPN MEF 80.3 Prot. T-MPLS Hints Summary L3 VPNs for IP connection service L3VPN Service L3 MPLS VPN IPSec tunnel VPN MPLS = privacy through lack of knowledge! Components of L3 MPLS VPNs: MPLS forwarding node to enable LSP tunneling MP-BGP to communicate VPN-IP-Addresses between PE routers VRF (Virtual Routing/Forwarding) deamons on the BGP nodes for route origin and route target based redistribution into customer specific routing information bases (RIBs) 4 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

5 VPN MEF 80.3 Prot. T-MPLS Hints Summary PWE3 - Pseudowire Emulation Edge to Edge Different emulations types are defined for: Ethernet, Frame Relay, PPP, HDLC, ATM, SONET/SDH and Fibre Channel. Identified by an encapsulation control word Site A Site B virtual Pipe = pair of opposite LSPs v. pipe label v. pipe label tunnel label PW/VC label v. pipe label v. pipe label v. pipe label v. pipe label Pseudo-Wire (PW) : pair of point-to-point single hop unidirectional LSPs in opposite directions each LSP identified by a PW / Virtual Connection (VC) label. LSP setup through LDP / RSVP-TE 6/ 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

6 VPN MEF 80.3 Prot. T-MPLS Hints Summary VPWS - Virtual Private Wire Service Synonyms: Virtual Leased Line (VLL), Ethernet over MPLS (EoMPLS) PWE3 for Ethernet point-to-point traffic transport over MPLS LSPs across an IP/MPLS backbone Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll 7/ 48

7 VPN MEF 80.3 Prot. T-MPLS Hints Summary VPLS - Virtual Private LAN Service Synonyms: TLS (Transparent LAN Services) Emulation of a virtual Ethernet switch on top of IP/MPLS using PWE3 encapsulation and either BGP (including auto-discovery) or LDP tunnel setup methods. A full mesh of tunnels between PEs limits scalability. BGP solution -> Route Reflectors LDP solution -> H-VPLS with Multi-Tenant Unit (MTU) switch 8/ 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

8 VPN MEF 80.3 Prot. T-MPLS Hints Summary Metro Ethernet Forum - MEF MetroEthernetForum.org Industry alliance of more than 10 vendors, providers and others formed in 001 e.g. Alcatel-Lucent, Broadcom, BT, Cisco, Ericsson, Extreme Networks, Ixia, Juniper, NSN, Nortel, T-Systems, TATA Communications, etc. The MEF s mission is to accelerate the worldwide adoption of Carrier-class Ethernet networks and services. MEF develops technical specifications and implementation agreements to promote interoperability and deployment of Carrier Ethernet worldwide. MEF Deliverables 1. Implementation Agreements on existing standards. Test Procedures 3. Position Statements to propose new standards for existing standards bodies 4. Technical Specifications of new standards in the MEF 5. Marketing evangelism and collateral 6. Certification Program 7. Education Programs and Demonstrations 8. Practical examples of Implementation of Carrier Ethernet Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll [MEF] 9/ 48

9 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF defintion of Carrier Ethernet Carrier Ethernet Carrier Ethernet is a ubiquitous, standardized, carrier-class Service and Network defined by five attributes that distinguish Carrier Ethernet from familiar LAN based Ethernet It brings the compelling business benefit of the Ethernet cost model to achieve significant savings Standardized Services Carrier Ethernet Attributes Scalability Service Management Reliability Quality of Service [MEF] AnIntroductiontotheMEF.ppt 10 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

10 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Standardized Services E-Line, E-LAN provide transparent, private line, virtual private line and LAN services A ubiquitous service providing globally & locally via standardized equipment Requires no changes to customer LAN equipment or networks and accommodates existing network connectivity such as, time-sensitive, TDM traffic and signaling Ideally suited to converged voice, video & data networks Wide choice and granularity of bandwidth and quality of service options [MEF] 11 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

11 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Standardized Services [MEF] 1 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

12 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Standardized Services [MEF] 13 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

13 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Ethernet connectivity services Ethernet connectivity services using different separation options and transport technologies Transport VOIP VLAN IP-based Services Internet IP-VPN E-LINE Ethernet Connectivity Services E-LAN Connectivity Services Separation MAC in MAC WDM RPR Ethernet ATM PDH PON SONET/SDH DSL Multiple Transport Technologies Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll IPTV MPLS [MEF] 14 / 48

14 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: E-Line service type E-Line Service used to create Ethernet Private Lines Virtual Private Lines Ethernet Internet Access EVC Ethernet Virtual Connection E-Line Service type Point-to-Point EVC UNI UNI CE Carrier Ethernet Network CE [MEF] 15 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

15 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: E-LAN service type E-LAN Service used to create Multipoint L VPNs Transparent LAN Service Foundation for IPTV and Multicast networks etc. see E-Tree E-LAN Service type CE UNI Carrier Ethernet Network Multipoint-to-Multipoint EVC UNI CE [MEF] 16 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

16 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: E-Tree service type E-Tree Service used to create Point-to-Multipoint private L tree interconnection Foundation for content distribution and Multicast tree networks etc. Carrier Ethernet Network UNI CE Root Leaf Leaf CE UNI Leaf UNI CE Rooted-Multipoint EVC UNI [MEF] CE 17 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

17 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Ethernet Private Line (EPL) E-Line service type, which uses point-to-point EVCs between sites in place of TDM leased lines UNI CE UNI Carrier Ethernet Network CE UNI ISP POP Internet Point-to-Point EVCs UNI [MEF] CE 18 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

18 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Ethernet Virtual Private Line (EVPL) E-Line service type, which uses point-to-point EVCs with service differentiation between sites in place of FR and ATM services Service Multiplexed Ethernet UNI UNI CE UNI Carrier Ethernet Network CE Point-to-Point EVCs UNI CE [MEF] 19 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

19 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Ethernet [Virtual] Private LAN E-LAN service type, which uses multipoint-to-multipoint EVCs with or without service differentiation between sites. This virtual bridge service supports transparent LAN services and multipoint Layer VPNs. UNI CE CE UNI Carrier Ethernet Network UNI Multipoint-to-Multipoint EVC Ethernet Private LAN example CE [MEF] 0 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

20 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Ethernet [Virtual] Private Tree (EP-Tree / EVP-Tree) E-Tree service type, which uses routed point-to-multipoint EVCs with or without service differentiation between sites. This virtual tree interconnection allows for bidirectional leaf-to-root communication, but blocks direct leaf-to-leaf communication. Enables Point-to-Multipoint Services with less provisioning than typical hub and spoke configuration using E-Lines CE Root UNI Carrier Ethernet Network Leaf Rooted-Multipoint EVC Leaf Leaf UNI UNI UNI CE CE [MEF] CE 1 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

21 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: TDM support TDM support through Circuit Emulation Services (CES) MEF 3 adopted from ATM CES Customer TDM Service TDM Service Interface TSP (optional) (e.g. framing, mux/demux) CES TDM Interface CES IWF Type CES IWF TDM IWF Packetization IWF CES Payload Adapted Payload ECDX Adds ECID and Length /Type field EFT Adds DA, SA, and CRC fields Ethernet Interface example: SONET/SDH emulation service provides emulation of the following services: 1. Higher order Virtual Container (HOVC): VC-3/STS-1, VC-4/STS-3c, VC-4-4c/STS- 1c. Lower order Virtual Container (LOVC): VC-11/VT-1.5, VC-1/VT-, none/vt-3, VC-/VT-6, VC-3/none [MEF] / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

22 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Scalability The ability for millions to use a network service that is ideal for the widest variety of business, information, communications and entertainment applications with voice, video and data Spans Access & Metro to National & Global Services over a wide variety of physical infrastructures implemented by a wide range of Service Providers Scalability of bandwidth from 1Mbps to 10Gbps and beyond, in granular increments [MEF] Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll 3 / 48

23 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Reliability The ability for the network to detect & recover from incidents without impacting users Meeting the most demanding quality and availability requirements Rapid recovery time when problems do occur, as low as 50ms End-toEnd path protection and (aggregated) line and node protection [MEF] 4 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

24 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Quality of Service see Standardized Services Wide choice and granularity of bandwidth and quality of service options Service Level Agreements (SLAs) that deliver end-to-end performance matching the requirements for voice, video and data over converged business and residential networks Provisioning via SLAs that provide end-to-end performance based on CIR, frame loss, delay and delay variation characteristics Traffic prioritization based on: Ethernet Port VLAN-ID or S-ID 80.1p bits IP DSCP, if deep frame (packet) inspection is used [MEF] 5 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

25 VPN MEF 80.3 Prot. T-MPLS Hints Summary MEF: Service Management The ability to monitor, diagnose and centrally manage the network, using standards-based vendor independent implementations Carrier-class OAM Rapid service provisioning [MEF] 6 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

26 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet frame structure 80.3 / 80.1q & 80.1p Original (untagged) and VLAN or Priority tagged frame structure single tagged 6 DA 6 SA T/L DATA PAD 4 FCS Bytes Bytes DA SA TPI = 8100 VLAN TCI T/L DATA PAD FCS TPI VLAN TCI Tag Protocol Identifier VLAN Tag Control Information 3 User Priority Priority Code Point 1 CFI 1 VID VLAN Identifier Bits 3 bit PCP 8 classes 1 bit VID 4096 VLANs Q-tag 1 bit Canonical Format Indicator = 0 compatibility for Token Ring VLAN-tagged frame: VLAN identification and Priority information Priority-tagged frame: Priority information and no VLAN identification information Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll 7 / 48

27 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet features 80.3 / 80.1q & 80.1p Original (untagged) and VLAN or Priority tagged frame structure ordinary Ethernet service with 4096 VLAN and 8 class priority support predominant technology in LAN networks (>95%) usage remains unchanged Carrier Ethernet interconnection service will provide transparent transport for those customers frames 8 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

28 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet frame structure VLAN XC Synonyms: VLAN XC, VLAN Cross Connect Customer Edge C-tag (Customer VLAN tag ) C-tag 4 Bytes tag exchange at the edge and tag swap at each node DA 6 DA SA 6 SA TPI = 8100 TPI = 8100 VLAN TCI VLAN TCI T/L T/L DATA DATA PAD PAD FCS 4 FCS Bytes XC-tag XC-tag double tagged EVXC (4bit) Bytes DA SA TPI = 88A8 VLAN TCI TPI = 8100 VLAN TCI T/L DATA PAD FCS Supported by: Siemens 9 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

29 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet frame structure VLAN XC Synonyms: VLAN XC, VLAN Cross Connect destination address (MAC) is not provider controlled forwarding is based on ingress port & VLAN-XC VLAN Cross Connect limited to 4096 or 16M services per port in tree structure VLAN ID with local significance + ID swapping per hop coexistence with pure Ethernet possible (ID space partitioning) VLAN translation L forwarding with flooding and DA/SA learning (VLAN-XC based) xstp for loop prevention IEEE 80.1 Minutes, July 006: A spontaneous motion was made to spend no further time on VLAN XC Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll 30 / 48

30 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet frame structure - Q-in-Q ad Synonyms: Q-in-Q, PVT, stacked VLAN, Provider Bridges Customer Edge C-tag (Customer VLAN tag ) double tagged 6 DA 6 SA TPI = 8100 VLAN TCI T/L DATA C-tag PAD 4 FCS Bytes Bytes DA SA TPI = 88A8 VLAN TCI TPI = 8100 VLAN TCI T/L DATA PAD FCS 3 User Priority Priority Code Point 1 DEI 1 S-VID Service VLAN Identifier Bits 3 bit PCP 8 classes 1 bit VID 4096 VLANs 1 bit Drop Eligible Indicator drop first, if congestion occurs Provider Edge S-tag (Service VLAN tag 88A8) S-tag 31 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

31 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet features - Q-in-Q ad Synonyms: Q-in-Q, PVT, stacked VLAN, Provider Bridges destination address (MAC) is not provider controlled forwarding is based on DA & S-VID limited to 4096 services with unique Service ID coexistence with pure Ethernet possible (ID space partitioning) L forwarding with flooding and DA/SA learning (S-VID based) xstp for loop prevention Supported by: Siemens, Huawei, Alcatel-Lucent, Ericsson and others 3 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

32 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet frame structure - MAC-in-MAC ah Synonyms: MAC-in-MAC, Provider Backbone Bridges (PBB) Customer Edge C-tag (Customer VLAN tag ) MAC encap DA 6 SA TPI = 8100 VLAN TCI 16 T/L DATA C-tag PAD 4 FCS 4 Bytes w / wo Bytes DA SA TPI = 88A8 VLAN TCI TPI = 88E7 I-Tag TCI T/L DATA PAD FCS B-tag I-tag 3 PCP DEI NCA Res Res 4 I-SID Backbone Service Instance Identifier 48 C-DA 48 C-SA Bits 3 bit PCP 8 classes 4 bit I-SID B-Services instances 1 bit Drop Eligible Indicator 1 bit No Customer Addresses Backbone Edge B-tag & I-tag (Instance VLAN tag 88E7) IEEE standard s page: Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll B-tag = S-tag 33 / 48

33 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet frame structure - MAC-in-MAC ah Synonyms: MAC-in-MAC, Provider Backbone Bridges (PBB) Customer Edge C-tag & S-tag double tagged C-tag 4 Bytes DA SA TPI = 88A8 VLAN TCI TPI = 8100 VLAN TCI T/L DATA PAD FCS MAC encap. S-tag C-tag w / wo Bytes DA SA TPI = 88A8 VLAN TCI TPI = 88E7 I-Tag TCI T/L DATA PAD FCS B-tag I-tag Backbone Edge B-tag & I-tag (Instance VLAN tag 88E7) IEEE standard s page: Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll B-tag = S-tag structure 34 / 48

34 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet features - MAC-in-MAC ah Synonyms: MAC-in-MAC, Provider Backbone Bridges (PBB) short / long I-Tag: long format (16 Byte) prevailed No Customer Addresses (NCA) field required; C-DA & C-SA within I-Tag TCI; no further Ethertype required 4 bit I-SID 4 provider service instances with unique LAN-ID forwarding is based on B-DA und B-VID only L forwarding with flooding and B-DA/B-SA learning (B-VID based) C-DA/C-SA learning confined to service instance xstp for loop prevention Supported by: 35 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

35 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet frame structure PBB-TE / PBT Qay Synonyms: PBB Traffic Engineering, Provider Backbone Transport Frame structure identical to 80.1ah MAC encap DA 6 SA TPI = 8100 C-tag VLAN TCI 16 T/L DATA PAD 4 FCS 4 Bytes w / wo Bytes DA SA TPI = 88A8 VLAN TCI TPI = 88E7 I-Tag TCI T/L DATA PAD FCS B-tag I-tag 3 PCP DEI NCA Res Res 4 I-SID Backbone Service Instance Identifier 48 C-DA 48 C-SA Bits 3 bit PCP 8 classes 4 bit I-SID B-Services instances 1 bit Drop Eligible Indicator 1 bit No Customer Addresses IEEE standard s page: Ethertype: 36 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

36 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet features PBB-TE / PBT Qay Synonyms: PBB Traffic Engineering, Provider Backbone Transport 80.1ah frame structure reuse point-to-point tunnel technology with transparent transport 4 bit I-SID 4 provider service instances with unique LAN-ID forwarding is based on B-DA und B-VID only bit tunnels L flooding and MAC learning is turned off! loop prevention through tunnel design only no STP! currently: Tunnel setup through SNMP GMPLS Control of 80.1Qay Networks IEEE & IETF liasion 80.1ag for CFM (connectivity fault management) using CCM (continuity check messages) Supported by: Nortel 37 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

37 VPN MEF 80.3 Prot. T-MPLS Hints Summary Provider Backbone Transport (PBT) Wiki: Provider Backbone Transport (PBT) aka PBB-TE (defined by IEEE 80.1Qay March 006) is a set of enhancements to Ethernet technology that allows the use of Ethernet as a carrier class transport network. This uses the concepts of VLAN tagging as per IEEE 80.1Q, Q-inQ in-q Q as per IEEE 80.1ad and MAC-in in-mac as per IEEE 80.1ah (Provider Backbone Bridges (PBB)) but disables the concept of flooding/broadcasting and spanning tree protocol. The idea here is to use Ethernet for connection oriented purpose as is the case with present SDH/SONET transport by stripping down the complexity involved with the present Ethernet LAN. It simplifies the operational administration and maintenance (OAM), as in SDH/SONET world, by using additional extensions based on IEEE 80.1ag. It also provides extensions so as to provide path protection levels similar to the UPSR protection in SDH/SONET network. Source: 38 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

38 VPN MEF 80.3 Prot. T-MPLS Hints Summary Current Ethernet Limitations Broadcast / Flooding Spanning Tree -> convergence time, loop prevention through single tree structure -> no multi-path, no optimized routing MAC address learning -> scalability -> additional hierarchy spanning tree convergence multiple spanning tree STP blocked ressources through deactivated ports loop generation through tunnelling? 80.1q -> only 1 bit VLAN-ID -> only 4096 VPNs 80.1ad -> only 1 bit S-VID -> only 4096 services per port 39 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

39 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet protection Known mechanisms: STP / RSTP / MSTP (xstp) Link aggregation MPLS Fast Reroute RPR (IEEE 80.17) Ethernet Protection Switching (ITU-T Y.134) linear, point-to-point protection non-revertive and revertive type uni- & bi-directional 1+1 protection switching 1:1 protection switching Ethernet Automatic Protection Switching (RFC 3619 Extreme Networks) ring protection with health check messages Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll 40 / 48

40 VPN MEF 80.3 Prot. T-MPLS Hints Summary T-MPLS (ITU) Synonyms: T-MPLS, Transport MPLS G.8110/Y MPLS layer network architecture G /Y Architecture of T-MPLS Layer Network G.811/Y.1371 Interfaces for the T-MPLS hierarchy G.811/Y.1381 Characteristics of T-MPLS equipment functional blocks G.8131/Y.1381 Linear protection switching for T-MPLS networks Y.Sup4 (01/08) Y.1300 series - Supplement on transport requirements for T-MPLS OAM G.8151/Y.1374 Management aspects of the T-MPLS network element Supported by: Alcatel-Lucent, Huawei, Ericsson and others 41 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

41 VPN MEF 80.3 Prot. T-MPLS Hints Summary T-MPLS (ITU) T-MPLS frame structure and usage Bytes DA SA TPI = 88A8 VLAN TCI TPI = 8100 VLAN TCI T/L DATA PAD FCS Layer Header (eg. GFP, Ethernet, SDH VC-n, OTH ODU-k) MPLS Shim Headers (1.. n) n 1 Customer Ethernet frame Label Stack Entry Format MAC DA MAC SA 4 Octets Label Exp. S TTL Label: Label Value, 0 bits (0-16 reserved) Exp.: Experimental, MPLS 3 bits (was Class of Service) S: Ethertype Bottom of Stack, label stack 1 bit (indicates Payload start of L3 FCS Header) TTL: Time to Live, 8 bits x8847 = MPLS Unicast x8848 = MPLS Multicast [Nortel99] 4 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

42 VPN MEF 80.3 Prot. T-MPLS Hints Summary T-MPLS (ITU) Synonyms: T-MPLS, Transport MPLS similar to ordinary MPLS with certain differences identical frame format, forwarding mechanism and data link ID e.g. Ethertype with 0x8847 and PPP with 0x081 for unicast no PHP (penultimate hop popping) bidirectional LSPs as well as unidirectional LSPs same transit node usage for both directions support for E-LSPs and L-LSPs incl. EXP marking for DiffServ support platform or per interface label space is possible OAM as with Y.1711 Protection as with Y.170 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll 43 / 48

43 VPN MEF 80.3 Prot. T-MPLS Hints Summary T-MPLS (ITU) Synonyms: T-MPLS, Transport MPLS SCN (signalling communication network) in-band within same DL technology (different frame type), in-band using separate T-MPLS LSP, out-of band using T-MPLS independent technology) no support for ECMP and tunnel merging pmp supported joint working team (JWT) created with ITU-T and IETF T/newslog/IETF+And+ITUT+Form+Joint+Working+Team+For+TMPLS.aspx aim: same Ethertype + responsibility of IETF for MPLS + ITU-T SG15 for Transport part seamless interworking between Ethernet and MPLS Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll 44 / 48

44 VPN MEF 80.3 Prot. T-MPLS Hints Summary Ethernet-TE (Vissers-ITU) G.8010 G.801 G.801 G.8031, Y.1731 for OAM functions 005 cancelled through lack of industry support 45 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

45 VPN MEF 80.3 Prot. T-MPLS Hints Summary ITU-T recommendations "Free access for all to ITU-T standards" ( ) Important Link: provides List of Standard Series (letter encoding) and direct links to latest work items Examples: G X G Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll 46 / 48

46 VPN MEF 80.3 Prot. T-MPLS Hints Summary Atrica solution Atrica is Carrier Ethernet pioneer and was first? in using LCAS/VCAT mechanisms in their NG SDH platform. Their early solution was based on VLAN XC and offered an one click service provisioning system (ASPEN). E-Line, E-LAN and CES (using PWE3 methods) was supported. Atrica a major Carrier Ethernet company has been acquired by Nokia Siemens Networks on January 7th / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

47 VPN MEF 80.3 Prot. T-MPLS Hints Summary Summary Tunnel technologies are there enough. The easy setup, monitoring and provider interworking will be the clinching argument for the Up- and Down-Fate. 48 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

48 Thank you. Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

49 Outlook: IETF GELS / Ethernet OAM GMPLS controlled Ethernet tunnels, Ethernet OAM options and T-MPLS OAM should be shown next time? 50 / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll

50 Sources [MEF] Reproduced with permission of the Metro Ethernet Forum. [Light03] Light Reading: VPN Capabilities Report, / 48 Darmstadt, FG-Treffen ITG TU Chemnitz - DI Th. Knoll