Geneva, 27 May 2010 Types and Characteristics of Packet Transport Network (PTN) Equipment (Draft Recommendation - G.ptneq) Jia He and Hilmar Hofmann G.ptneq.

Slides:



Advertisements
Similar presentations
Intra-Carrier Solutions Enabled by the OIF NNI Erning Ye Nortel Networks.
Advertisements

ITU-T SG15 liaisons on Ethernet topics Glenn Parsons
1 Metro Ethernet Forum OAM An Update Matt Squire Hatteras Networks.
1 IEEE Media Independent Handoff Overview of services and scenarios for 3GPP2 Stefano M. Faccin Liaison officer to 3GPP2.
Ethernet OAM Update Overview & Technical Aspects Dinesh Mohan May 18, 2004.
Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and.
Link Selection and OAM Version 01 Stephen Haddock July 18,
Multi Domain Traffic Engineered Transport Networks (E-OTN, PTN) supporting P2P, P2MP, RMP and MP2MP Ethernet Services An overview of architecture and functionality.
Port group model in G.8021 Akira Sakurai G.8021 Co-editor IEEE and ITU-T Q.9/15 Ethernet Transport issues (Geneva, 27 May 2010)
Extending OTN Standards to Support Ethernet Services
ITU-T SG15 liaisons on Ethernet topics Glenn Parsons
Nov 2009 draft-ietf-mpls-tp-framework-06.txt A framework for MPLS in Transport networks draft-ietf-mpls-tp-framework-06.txt Stewart Bryant (Cisco), Matthew.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum MEF 19 Abstract Test Suite for UNI Type 1 February 2008.
1 Introducing the Specifications of the Metro Ethernet Forum MEF 17 Service OAM Framework and Requirements February 2008.
Introducing the Specifications of the Metro Ethernet Forum
Introducing the Specifications of the Metro Ethernet Forum
Optical Control Plane Activities in IETF and OIF L. Ong 9 July 2002 L. Ong 9 July 2002
NTT 2002 © 1 General Principles and Requirements for OAM Functions July 10, 2002 Hiroshi Ohta (NTT, Q.3/13 rapporteur)
ITU-T Workshop on IP/Optical Chitose, 9-11 July 2002 Session Network Performance N eal Seitz, Chair SG 13/WP 4 IP Performance Specifications: Progress.
Network Protection and Restoration Session 5 - Optical/IP Network OAM & Protection and Restoration Presented by: Malcolm Betts Date:
Geneva, Switzerland, 17 October 2011 ITU Workshop on Service Delivery Platforms (SDP) for Telecommunication Ecosystems: from todays realities to requirements.
International Telecommunication Union Practical Issues In Managing Optical Networks by Wesam Alanqar and Tammy Ferris ITU-T Workshop IP/Optical (Chitose,
Steve Joiner, Technical Committee Chair John McDonough, Member OIF Board of Directors Optical Internetworking Forum.
ITU-T Solutions Session 2 – Switched Optical Networks Presented by: Stephen Shew Date:
Satoshi NARIKAWA NTT (G.8032 Acting Co-editor)
Slide title minimum 48 pt Slide subtitle minimum 30 pt Service Resiliency - ITU-T SG15 Q9 Activities Ghani Abbas Ericsson 25 th.,June, 2012 Geneva Workshop.
Multi-service Architecture: Evolution of Network Architecture Keith Knightson Khalid Ahmad Carrier Data Networks Nortel Networks, Canada IP-Networking/Mediacom.
Geneva, Switzerland, 13 July 2013 M ulti D omain S egmented network P rotection (MDSP) Huub van Helvoort, Senior Researcher Huawei Technologies Joint IEEE-SA.
Marc Holness, Product Line Architect, Ciena
Synchronization architecture
An SAIC Company The views expressed in this presentation are the presenters and do not necessarily represent the views and policies of Telcordia Technologies,
Data over Transport with ASON Session 12 – Optical Network Clients and Services Presented by: Stephen Shew Date:
Colombo, Sri Lanka, 7-10 April 2009 Efficient Backhauling Strategies for NGNs using Carrier-Ethernet SIVA RAMAMOORTHY, Group Director, Marketing Tejas.
Identifying MPLS Applications
Chapter 1: Introduction to Scaling Networks
Application Server Based on SoftSwitch
1 Transport Services Layer Protection Switching Types Interacting with DRNI Maarten Vissers
1 DRNI Examples and DAS position Maarten Vissers Version 01.
Data Link Layer B. Konkoth. PDU  Protocol Data Unit  A unit of data which is specified in a protocol of a given layer  Layer 5, 6, 7 – Data  Layer.
Doc.: IEEE /0578r0 Submission 2008 May Jarkko Kneckt, NokiaSlide 1 Forwarding in mesh containing MPs in power save Date: Authors:
© 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—2-1 Extending Switched Networks with Virtual LANs Introducing VLAN Operations.
(omniran TG) Short introduction into OmniRAN P802.1CF Date: Authors: NameAffiliationPhone Max RiegelNokia.
MEF Reference Presentation November 2011
Transmission of IP Packets over Ethernet over IEEE draft-riegel-16ng-ip-over-eth-over Max Riegel
1 ATM: What it is, and what it isn't Carey Williamson University of Calgary.
A Possible New Dawn for the Future GÉANT Network Architecture
Omniran TG 1 Cooperation for OmniRAN P802.1CF Max Riegel, NSN (Chair OmniRAN TG)
Next Generation SDH LCAS Ethernet GFP VCAT.
Abstraction and Control of Transport Networks (ACTN) BoF
ITU-T Study Group 13 Communications to IETF CCAMP Working Group Marco Carugi ITU-T SG13 Liaison Officer to IETF CCAMP
1 Introducing the Specifications of the Metro Ethernet Forum.
Metro Ethernet UNI Standards Update Gary Southwell VP of Product Marketing Internet Photonics MEF Marketing Collateral co-chair
What is Bandwidth on Demand ? Bandwidth on Demand (BoD) is based on a technology that employs a new way of managing and controlling SONET-based equipment.
MPLS-TP INTER-OP: WHAT, WHY, AND HOW? General Objectives for MPLS-TP Inter-Op Test Program at UNH-IOL.
12/8/2015 draft-blb-mpls-tp-framework-01.txt A framework for MPLS in Transport networks draft-blb-mpls-tp-framework-01.txt Stewart Bryant (Cisco), Matthew.
Session 10: Optical Switching and Equipment ITU-T Study Group 15, Q12 Michael Mayer Nortel Networks.
Multi layer implications in GMPLS controlled networks draft-bcg-ccamp-gmpls-ml-implications-05 D.Papadimitriou (Alcatel-Lucent) D.Ceccarelli (Ericsson)
Synchronization architecture
P802.1CM Time-Sensitive Networking for Fronthaul
Multi Domain Segmented network Protection (MDSP)
Network Architecture Introductory material
Review of Important Networking Concepts
Connecting to the Network
Synchronous Optical Network (SONET)
Presentation transcript:

Geneva, 27 May 2010 Types and Characteristics of Packet Transport Network (PTN) Equipment (Draft Recommendation - G.ptneq) Jia He and Hilmar Hofmann G.ptneq editors

Introduction Since 2002, the ITU-T has been developing recommendations for packet transport network architecture, equipment, OAM, NNI, protection and management with specific emphasis on technology such as Ethernet and MPLS The Ethernet recommendations have been developed in a close cooperation with IEEE These recommendations use functional decomposition/ components to describe packet transport networks Missing today is a recommendation which provides guidance on how to combine these functional components in equipment and networks This gap has been identified and a new recommendation G.ptneq is a work in progress Geneva, 27 May

3 G.ptneq: Rationale The objective is to describe PTN equipment functionality independent of existing and future packet based technologies (ie. generic part) A second part is to describe technology specific equipment functionality such as Ethernet or MPLS-TP. Enable any PTN equipment to use common features: management plane control plane survivability schemes OAM behaviour PTN equipment built for different packet technologies shall have common characteristics

Geneva, 27 May G.ptneq: Background ITU-T develops generic description of functional reference models for transport network equipment which are used in a Packet Transport Network to efficiently provide packet based services. The objective is: To provide a variety of equipment type examples (VC Term, VC Switch, VP Switch, etc.) To describe the equipment using atomic functions To avoid constraints on the implementation PTN equipment types are described in terms of functional blocks

Geneva, 27 May G.ptneq: Timetable Consent a recommendation by June 2010 which contains the basic concept and generic/technology agnostic information. Consent a second version in Feb 2011 which contains additional technology specific functionality (e.g. Ethernet, MPLS-TP).

Geneva, 27 May G.ptneq: Scope This recommendation describes an overview of the functions of packet transport network (PTN) equipment and provides examples of various PTN equipment types. It is by no means restricting the way equipment may be built. G.ptneq does not mandate the way equipment should be built.

Geneva, 27 May G.ptneq: Content Current draft version contains basic concept and generic/technology agnostic aspects. PTN Layer Hierarchy Functions to be supported on PTN equipment Multiplexing/Demultiplexing OAM and provisioning/management Protection switching Timing and Synchronization PTN Interface ports PTN Equipment types

Geneva, 27 May G.ptneq: PTN Domain Model VC Term: demarcation between Client and carrier (PTN) Generation/Termination of VC layer VC Switch: Switch function on VC layer Generation/Termination of VP layer VP Switch Switch function on VP layer

Geneva, 27 May G.ptneq: PTN Layer Hierarchy PTN provides up to 3 packet based layers Virtual Channel Layer Virtual Path Layer Virtual Section Layer (as part of the transmission media layer) Client/Server Mode: customers signal is treated as a client layer signal of the PTN VC layer and is encapsulated into the PTN VC signal

Geneva, 27 May G.ptneq: PTN Layer Hierarchy Peering Mode customers signal is passed through the PTN VC layer without encapsulation only a subset of clients that must be of the same technology as PTN VC can be supported

G.ptneq: PTN Layer Hierarchy for multiple domains In multi-domain case the layer relationship is relative. VP in Domain 1 is VC in Domain 2 VS in Domain 1 is VP in Domain 2 VP in Domain 2 is VC in Domain 3 VS in Domain 2 is VP in Domain 3 11 Geneva, 27 May 2010 VC VP VS VC VP VS VC VP VS Domain 1Domain 2Domain 3

Next Step 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 Geneva, 27 May 2010

Thanks You Any Q?

Backup Slides

Geneva, 27 May G.ptneq: Generic overview of PTN functional Model

Geneva, 27 May G.ptneq: Port Model Examples

Geneva, 27 May G.ptneq: Port Model Examples (contd.)