Port group model in G.8021 Akira Sakurai G.8021 Co-editor IEEE 802.1 and ITU-T Q.9/15 Ethernet Transport issues (Geneva, 27 May 2010)

Slides:



Advertisements
Similar presentations
Ethernet OAM Update Overview & Technical Aspects Dinesh Mohan May 18, 2004.
Advertisements

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.
Extending OTN Standards to Support Ethernet Services
Geneva, 27 May 2010 Types and Characteristics of Packet Transport Network (PTN) Equipment (Draft Recommendation - G.ptneq) Jia He and Hilmar Hofmann G.ptneq.
EVC structure for a Protected E-Line service
Nortel Confidential Information 1 MPLS & Ethernet OAM Interworking (draft-mohan-pwe3-mpls-eth-oam-iwk) L2VPN WG, IETF-71 (Philadelphia) Mar 13, 2008 Dinesh.
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.
1 Introducing the Specifications of the Metro Ethernet Forum.
1 Introducing the Specifications of the Metro Ethernet Forum MEF 17 Service OAM Framework and Requirements February 2008.
Introducing the Specifications of the MEF
Satoshi NARIKAWA NTT (G.8032 Acting Co-editor)
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
Geneva, Switzerland, 13 July 2013 Moderator Summary Ethernet Protection Summary Ghani Abbas, Ericsson – ITU-T SG15 vice chair Steve Haddock – IEEE
Identifying MPLS Applications
Ethernet Access Services Definition and Implementation
MEF Service Types and Service Definitions Overview and Use Cases
1 Transport Services Layer Protection Switching Types Interacting with DRNI Maarten Vissers
1 DRNI Examples and DAS position Maarten Vissers Version 01.
Application-Based Network Operations (ABNO) IETF 88 – SDN RG
© 2006 Cisco Systems, Inc. All rights reserved. ICND v2.3—2-1 Extending Switched Networks with Virtual LANs Introducing VLAN Operations.
MEF Reference Presentation November 2011
IETF88 Framework for Point-to-Multipoint MPLS-TP draft-hmk-mpls-tp-p2mp-oam-framework-03.txt Nov 6, 2013 Yoshinori Koike Takafumi Hamano Masatoshi Namiki.
1 Distributed Network Protection (DNP) architecture study Maarten Vissers v4 v2: includes a few slides at the end illustrating segment protection.
802.1Qay PBB-TE Protection Switching Overview
802.1ag - Connectivity Fault Management Tutorial – Part 1 Dinesh Mohan July 12, 2004.
1 DRNI and Distributed Protection Examples Maarten Vissers v01 Based on slides presented in IW meeting in Nanjing on Thursday Sept 22.
1 Distributed Network Protection (DNP) architecture study Maarten Vissers v3 v2: includes a few slides at the end illustrating segment protection.
Internetworking Different networks –Different bit rates –Frame lengths –Protocols.
1 Switching and Forwarding Bridges and Extended LANs.
1 Switching and Forwarding Bridges and Extended LANs.
1 MEF 35: Service OAM Performance Monitoring Implementation Agreement July 2012 Introducing the Specifications of the MEF.
1 Multipoint Ethernet Connection Protection
1 MEF 35: Service OAM Performance Monitoring Implementation Agreement (includes MEF ) December 2013 Introducing the Specifications of the MEF.
1 MEF 35.0.x: Service OAM Performance Monitoring Implementation Agreement December 2013 Introducing the Specifications of the MEF.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 3: Implementing VLAN Security Routing And Switching.
Submission doc.: IEEE 11-12/0589r2 July 2012 Donald Eastlake 3rd, Huawei R&D USASlide 1 General Links Date: Authors:
15.1 Chapter 15 Connecting LANs, Backbone Networks, and Virtual LANs Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or.
25-Oct-15Network Layer Connecting Devices Networks do not normally operate in isolation.They are connected to one another using connecting devices. The.
UNI Manager Project Proposal to OpenDaylight
Congestion Management Study Group1 September 2004 PAR Title Information technology -- Telecommunications and information exchange between systems -- Local.
McGraw-Hill©The McGraw-Hill Companies, Inc., Chapter 16 Connecting LANs, Backbone Networks, and Virtual LANs.
1 Introduction filtering-0710-v04.pdfhttp://
Winter 2008CS244a Handout 111 CS244a: An Introduction to Computer Networks Handout 11: Interconnecting LANs Nick McKeown Professor of Electrical Engineering.
1 1 Carrier Ethernet Services Overview 26 September2007 Moderator: Ralph Santitoro - Turin Networks Panelists: Tony Tam - Anda Networks Dr. Sarath Kumar.
LAN Switching Virtual LANs. Virtual LAN Concepts A LAN includes all devices in the same broadcast domain. A broadcast domain includes the set of all LAN-connected.
Supporting VUNI in DRNI Maarten Vissers v00
Marc Holness, Product Line Architect, Ciena
CS 3700 Networks and Distributed Systems
: An Introduction to Computer Networks
Congestion Management Study Group
Hubs Hubs are essentially physical-layer repeaters:
Switching and Forwarding Bridges and Extended LANs
CS 3700 Networks and Distributed Systems
Hubs Hubs are essentially physical-layer repeaters:
CS 4700 / CS 5700 Network Fundamentals
Connecting LANs, Backbone Networks,
E-OTN status update and service interface question [associated with ITU-T liaison statement liaison-itut-sg15-ols ] version 01 New slides:
ITU-T compliant B-PON system Multi-vendor Inter-operability demo.
Chapter 16 Connecting LANs, Backbone Networks, and Virtual LANs
CS 4700 / CS 5700 Network Fundamentals
Presentation transcript:

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)

Background The introduction of the Port Group construct in Ethernet Flow Forwarding (ETH_FF) process in ITU-T Recommendation G.8021 Amendment 2 is based on 12 months study and the development of a set of requirements based on carriers and vendors contributions to support E-Tree and E- LAN services. These services have already been specified in G.8011.x series of Recommendations. G Ethernet Services Framework G Ethernet Virtual Private Rooted Multipoint Service G Ethernet Private LAN Service

Requirements for E-Tree/E-LAN services 1. A single Ethernet Virtual Connection (EVC) to support E-Tree and E-LAN services 2. Capability to reduce latency in EVC 3. Capability to support Y.1731 OAM for EVC and server/EVC adaptation functions located in NNI ports 4. Capability to traffic-engineered rmp and mp2mp EVCs by means of performing Traffic Conditioning (TC) at the ingress of each EVC link connection 5. Support of EVC by a mix of server layer technologies such as: ETH MPLS-TP SDH VC-n OTN ODUk

Principle of the Port Group Frames arriving via an input port in a Port Group may be forwarded to one or more output ports, with the exception of the output ports that are member of the Port Group. Frames arriving on an input port which is not a member of the Port Group may be forwarded to one or more output ports, with exception of the port over which the frame arrived. A B C X Y Z Port Group {A,B,C} ETH_FF {A,B,C,X,Y,Z}

Applications for the Port Group Primary is to allow for configuration of a rooted-multipoint EVC. Additional application is Split horizon. Rooted multipoint EVC Split horizon Root Leaf Port group

Reduction of latency Full mesh of ETH VC link connections in a domain contributes to the reduction of latency for forwarding frames. However, it does require an additional loop-prevention mechanism. The Port Group performs this mechanism at the bridging points without changing any of MEP/MIP/TC functionalities.

Location of the Port Group functionality Option1 - between the ETH_FF process and the ETH MEP/MIP/TC functions in the interface ports The Port Group functionality is collocated with the original ETH_FF process inside an ETH Connection (ETH_C) function. Option 2 - inside a Server/ETH_A function This does not support the possibility of traffic conditioning at the Ingress of the EVC link connections, nor the use of different server layer technologies. For these reasons, G.8021 selected the option 1 to achieve the Port Group functionality. Option1 ETH_FF Srv/ETH Srv ETH Srv/ETH Srv ETH Srv/ETH Srv ETH Srv/ETH Srv ETH ETH_FF Srv/ETH Srv ETH ETH/ETHm ETH_C Option2

Conclusion The introduction of the Port Group defined in G.8021 Amd2 enables operators to deploy E-Tree/E-LAN services efficiently. ITU-T SG15 Q9 would like to express its appreciation for the continued useful exchange of information with IEEE on Ethernet technology standards. We look forward to continuing this coordination in the future.