connect communicate collaborate JRA1 Task 1 Investigation of Emerging Carrier Class Transport Network Technologies (CCTNT) Victor Olifer (JANET) TNC 2010, Vilnius,

connect communicate collaborate Agenda Introduction to JRA1 Task1 CCTNT Introduction. Why are CCTNT necessary?. Requirements. Benefits. CCTNT Descriptions: Ethernet developments NG-OTN. MPLS-TP. PBB-TE. JRA1 Task1 Future Plans.

connect communicate collaborate Introduction to JRA1 Task 1 JRA1 Task 1 will research the exploitation of the hybrid infrastructure by emerging transport technologies such as Carrier Class PBT and MPLS-TP in order to support point-to-point, point-to-multipoint and VPN services. Stage 1 – theoretical investigation of promising technologies: to what extent they can be called carrier-class transport Both emerging and established technologies were in scope: (only new carrier- class features investigated for the latter) The expected results of the work are the: Production of reference papers for GÉANT and NREN’s future transport network technologies. Not about photonic layer – this is JRA1 Task 2 “GN3 will be revolutionary in terms of the services it provides. Whilst the underlying technology at the lower layers of the network is not going to undergo substantial change, there will be a dramatic change in the services that will be developed and offered to end users”

connect communicate collaborate Carrier Class Transport Network Technologies (CCTNT) What is CCTNT? Requirements: Effective data transmission: to combine flexible multiplexing and provisioning with good performance (latency, bandwidth granularity) for each traffic type Support for standardised services.(e.g. MEF E-LINE & E-LAN) P-OTS readiness Manageability (OAM functionality similar to the traditional SDH/SONET) Simplicity Scalability and versatility. Reliability (Protection & Restoration). QoS. Dynamic provisioning (support for Control plane or NMS-based provisioning) Environmental requirements Low cost Benefits: Better and more reliable customer services built upon the transport CAPEX and OPEX reduction: simpler infrastructure, converged Possibility to satisfied the special needs from the research community Additional functionality (e.g. BoD ) Higher bandwidth Better possibilities for interoperability and interworking

connect communicate collaborate JRA1 Task1 Technologies & focus areas Technologies considered as relevant under the scope of JRA1 Task1: Next-Generation OTN (NG-OTN) Ethernet (new features) Layer 2 Routing Synchronous Ethernet Ethernet over Multi-Protocol Label Switching (EoMPLS) Multi-Protocol Label Switching Transport Profile (MPLS-TP) Provider Backbone Bridge Traffic Engineering (PBB-TE) GMPLS and focus areas: Scalability Quality of Service (QoS) Protection and restoration Operations, Administration and Maintenance (OAM) functionality Multicasting. Control plane protocols (including GMPLS) Multi-domain Standardisation Applications Cost-effectiveness

connect communicate collaborate OTN Optical Transport Networks (OTN) Single technology Better scalability and flexibility Transparent for Client Signals (does not transfer network synchronization) Better Forward Error Correction Hierarchical Tandem Connection Monitoring functionality – multidomain support Fast Protection Restoration through GMPLS Physical Medium - Fibre SDH/SONET Ethernet IP/MPLS A big step from SDH/SONET:

connect communicate collaborate Next Generation OTN NG-OTN promises a much more flexible mutiplexing hierarchy, designed for data traffic: ODU Flex – Flexible low order container that can be ”right sized”. ODU 0 and OPU0 to accomodate 1 GE signals. ODU2e and OPUe2 for transport of CBR10G3 for 10 GE. New ODU3e and OTU3e for transport of 4 x ODU2e. ODU 4 and OTU4 for transport of 100GE. Enhanced OAM features: OTN Alarms and defects being reviewed by Study Group 15. Control Plane: GMPLS signalling extensions for G.709 (RFC 4328). Conclusion : Carrier-class technology without any doubts Worth to trial NG feaqtures: OAM, dynamic provisioning, P-OTS capabilities Evolution towards Packet-Optical Transport Sysytem

connect communicate collaborate Ethernet developments Ethernet is evolving producing : Some strands that can be treated as separate transport technologies, i.e. PBB-TE or EoMPLS New elements that might be seen as native Ethernet developments: MEF technology-agnostic definitions of Ethernet global services: E-LINE (EPL & EVPL), E-LAN and E-TREE Ethernet OAM Ethernet QoS 40G/100G Ethernet

connect communicate collaborate Ethernet OAM CFM (802.1ag) from IEEE : Y.1731 from ITU-T adds Performance Monitoring to CFM : Continuity Check Messages (CCM) with end-to-end hierarchy: Loopback and Linktrace Messages – service troubleshooting  service status monitoring Frame Loss Messages. Frame Delay Messages.

connect communicate collaborate MPLS-TP (MPLS–Transport Profile) Background & Definition MPLS-TP is the result of a joint effort between the ITU-T and the IETF. MPLS-TP is a subset of MPLS with extensions to support the requirements for transport networks. T-MPLS

connect communicate collaborate MPLS-TP Transport requirements (I) MPLS-TP OAM Sould be independent on IP forwarding and control plane MPLS-TP provides In-band OAM similar to transport model MPLS-TP generalises the use of Generic Associated Channel (G-ACh) to provide a mechanism to carry management and OAM information (RFC 5586). MPLS-TP defines a set of tools to provide “pro-active” and “on-demand” OAM. On going work in the IETF for definition of these tools. Tools under discussion: ITU-T Y.1731 LSP Ping BFD Virtual Circuit Connectivity Verification (VCCV).

connect communicate collaborate MPLS-TP Transport requirements (II) Protection Protection for different transport entities: sections, LSPs and PWs < 50 ms switching time. 1+1, 1:1, n:1 protection. Protection for uni-directional and bi-directional paths. Linear and ring protection Restoration (Control plane & Management Plane) Manual control. Triggered by operator. Failure triggered actions. OAM signalling. Control plane (GMPLS).

connect communicate collaborate MPLS-TP Conclusions & Status Conclusions: MPLS-TP provides packet effiencicy inherited from MPLS, adds transport capabilities and removes some unnessary features Worth to trial and demonstrate Current status: MPLS-TP is currently under development. There are five published RFCs and a lot if Internet Drafts At MPLS World Congress in Paris (February 2010) it was said that the core MPLS-TP standards would be complete by July 2010

connect communicate collaborate Provider Backbone Bridge Traffic Engineering Initially developed by Nortel (in 2006) as Provider Backbone Transport (PBT) – it was Provider Backbone Bridges extension to support: Deterministic paths for point-to-point services (E-LINE) with bandwidth guarantees and QoS. Fast path protection switching (1:1 and m:n) Standardised by the IEEE as PBB TE (802.1Qay) in 2009 (E-TREE services were added). Switches off MAC learning and STP but preserves the forwarding table format, population of which might be: Manual NMS-based GMPLS-based

connect communicate collaborate PBB TE scalability: Two-tier connection hierarchy мс Provider network Customer A Customer B Customer C Customer D Outer transport tunnel : {B-VID, B-MAC DA} as a globally unique transport label Inner service connections: - identified by I-SID as a service label: up to 16 millions per tunnel B-MAC=0x35 B-VID=117 B-MAC=0x35 B-VID=117 B-MAC=0x35 B-VID=117 B-MAC=0x35 B-VID=117 B-MAC=0x35 The technique is very similar to MPLS “tunnels+pseudowires” scheme but it uses well-known MAC addresses and VLAN Ids – globally unique labels Edge switches know: Nothing about customer VIDs & MACs for EPL (port-based) service Customer VIDs for EVPL (VLAN-based) service PE-1 PE-2

connect communicate collaborate PBB TE features and status Resilience Primary and backup tunnels (1:1) or groups (n:m); 50 ms. CFM heartbeat messages test tunnels and trigger protection switching. OAM No specific mechanisms; all new Ethernet OAM features can be used; CFM – mandatory for protection switching Control Plane Zero control plane – main option; NMS-based provisioning systems. GMPLS - Internet draft exists, no implementations known. Multi-domain support Mostly a single-domain technology (access for IP/MPLS) Can be used in multi-domain environment a cording MEF E-NNI spec Current status Standardised but immature yet (early releases). Eco-system shrunk after early enthusiasm – but there are several major vendors that support it Conclusion: worth to trial

connect communicate collaborate Comprehensive study and demonstration CCTNT Carrier Class Transport Network Technologies CCTNT Carrier Class Transport Network Technologies JRA1 T1 Status: Carrier Class Transport Network Technologies Next step: NGN IP MPLS Ethernet over MPLS MPLS-TP PBB-TE NGN OTN Control Plane (GMPLS) Ethernet Synchronous Ethernet Layer 2 routing NGN OTN Control Plane (GMPLS) Further study and testing - OAM. - Protection & Restoration. - Control Plane (GMPLS). - Cost-effectiveness. - Multi-domain implications. Further study and testing - OAM. - Protection & Restoration. - Control Plane (GMPLS). - Cost-effectiveness. - Multi-domain implications. Deliverable DJ1.1.1

connect communicate collaborate JRA1 Task 1 participants Contributors: Alberto Colmenero – NORDUnet (Task Leader) Rebecca Corn – DANTE Marcin Garstka – PSNC Jac Kloots – SURFNET Victor Olifer – JANET Jan Radil – CESNET Krzysztof Stanecki – PSNC Sue Tyley – DANTE (Technical writer) Please check JRA1 Task1 report at: