Network Demarcation in 802.1aj Alan McGuire IEEE 802.1 Eilat Interim May 2008.

Slides:

Advertisements

Similar presentations

Introduction to PrimeEnterprise. PrimeEnterprise What is PrimeEnterprise? PrimeEnterprise is a tool set that overlays multiple PrimeSuite sites Enterprise.

Advertisements

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

Achieving Seamless IP Optical Network Integration OIF Interoperability Update Amy Wang, Avici Systems.

Ethernet Switch Features Important to EtherNet/IP

Experiences with IEEE 802.1ah (Provider Backbone Bridges) Ronald van der Pol SARA Sep 2009NORDUnet meeting, Copenhagen.

Steps towards an 802.1ad draft Style of specification : A recommendation Mick Seaman.

PAR for Media Converters r2IEEE interim, October, PAR for Media Converters revision 2 Norman Finn Cisco Systems.

802.1H Revision Project Kevin Nolish Michael Wright.

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 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)

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 MEF 17 Service OAM Framework and Requirements February 2008.

Colombo, Sri Lanka, 7-10 April 2009 Efficient Backhauling Strategies for NGNs using Carrier-Ethernet SIVA RAMAMOORTHY, Group Director, Marketing Tejas.

1 DRNI Examples and DAS position Maarten Vissers

1 DRNI Examples and DAS position Maarten Vissers Version 01.

1 MEF Reference Presentation November 2011 Carrier Ethernet Service OAM.

Doc.: IEEE /243r0 Submission March 2002 James Kempf, DoCoMo LabsSlide and IP James Kempf Seamoby WG Co-chair DoCoMo Labs USA

Submission doc.: IEEE 11-13/ ak July 2013 Finn and Hart, Cisco SystemsSlide 1 P802.1Qbz + P802.11ak Proposed Division of Work Date:

MEF Reference Presentation November 2011

Submission doc.: IEEE /1186r2 September 2014 Pengfei Xia, Interdigital CommunicationsSlide 1 Comparisons of Simultaneous Downlink Transmissions.

1 Distributed Network Protection (DNP) architecture study Maarten Vissers v4 v2: includes a few slides at the end illustrating segment protection.

802.1ag - Connectivity Fault Management Tutorial – Part 1 Dinesh Mohan July 12, 2004.

M Vinod Kumar Tejas Networks Ltd.  Example  Requirements  Possible solutions.

1 Distributed Network Protection (DNP) architecture study Maarten Vissers v3 v2: includes a few slides at the end illustrating segment protection.

Load Sharing with 1:1 Protection Switching Alan McGuire IEEE Eilat.

TCP/IP Networks. Table of Contents Computer networks, layers, protocols, interfaces; OSI reference model; TCP/IP reference model; Internet Protocol (operations,

I.1 ii.2 iii.3 iv.4 1+1=. i.1 ii.2 iii.3 iv.4 1+1=

I.1 ii.2 iii.3 iv.4 1+1=. i.1 ii.2 iii.3 iv.4 1+1=

Submission doc.: IEEE 11-10/0897r0 July 2014 Jon Rosdahl, CSRSlide PAR Review – July 2014 Date: Authors:

1 Introducing the Specifications of the Metro Ethernet Forum.

A Novel Approach to WLAN Mesh Interworking with Multiple Mesh Portals 指導教授：許子衡教授學生：王志嘉.

7.1 and 7.2: Spanning Trees. A network is a graph that is connected –The network must be a sub-graph of the original graph (its edges must come from the.

Network 101 By Tom Battaglia Dell Connectivity 2 RR2 DC Drawing 3 Heterogeneous Network 4 OSI Model.

Module 11: Read-Only Domain Controllers. Overview Describe the Read-Only Domain Controllers role Use Read-Only Domain Controllers.

8.1.4 Can it still be factored? Factoring Completely I can factor out a common factor.

Defining the Border Between P and P Myung Lee CUNY/Samsung.

1 Local Hashing for ECMP Ali Sajassi September 21, 2011 IEEE Interim Meeting.

PCE 64 th IETF PCE Policy Architecture draft-berger-pce-policy-architecture-00.txt Lou Berger Igor Bryskin Dimitri Papadimitriou.

Slide title In CAPITALS 50 pt Slide subtitle 32 pt Authentication/Authorization for possible deployments Relevant scenarios for CAFE.

EFM Common MIB Issues. Common MIB or OAM MIB? “Common” MIB currently covers OAM Does not have anything common between EFM subjects –OAM, EoCu, and EPON.

1 Generalized EC Type 2 support EC Type 1&2 supporting bridges Maarten Vissers

1 Two Port MAC Relay Scope - Revised David W. Martin Nortel v00 IEEE May 9-13, 2005 Berlin.

1 Distributed Network Protection (DNP) architecture study Maarten Vissers v1.

ΟΡΓΑΝΩΣΗ ΚΑΙ ΔΙΟΙΚΗΣΗ ΕΠΙΧΕΙΡΗΣΕΩΝ 3 Ο ΜΑΘΗΜΑ. ΟΙ ΜΕΓΑΛΕΣ ΕΠΙΧΕΙΡΗΣΕΙΣ Η δημιουργία μεγάλων επιχειρήσεων είναι ένα από τα χαρακτηριστικά του 20 ου αιώνα.

Supporting VUNI in DRNI Maarten Vissers v00

Media Access Methods MAC Functionality CSMA/CA with ACK

DetNet Service Model draft-varga-detnet-service-model-00

FRD Examples November 28, 2017 L. Ong.

Multi Domain Segmented network Protection (MDSP)

RNI Requirements Imposed by PBB-TE

Mixing Calling Plan and Direct Routing connectivity for the same user is optional, but could be useful, for example, when the user is assigned a.

E-OTN status update and service interface question [associated with ITU-T liaison statement liaison-itut-sg15-ols ] version 01 New slides:

ОПЕРАТИВНА ПРОГРАМА “ИНОВАЦИИ И КОНКУРЕНТОСПОСОБНОСТ“ „Подобряване на производствения капацитет в МСП“

5 × 7 = × 7 = 70 9 × 7 = CONNECTIONS IN 7 × TABLE

5 × 8 = 40 4 × 8 = 32 9 × 8 = CONNECTIONS IN 8 × TABLE

4 × 6 = 24 8 × 6 = 48 7 × 6 = CONNECTIONS IN 6 × TABLE

5 × 6 = 30 2 × 6 = 12 7 × 6 = CONNECTIONS IN 6 × TABLE

Solving Equations 3x+7 –7 13 –7 =.

10 × 8 = 80 5 × 8 = 40 6 × 8 = CONNECTIONS IN 8 × TABLE MULTIPLICATION.

3 × 12 = 36 6 × 12 = 72 7 × 12 = CONNECTIONS IN 12 × TABLE

5 × 12 = × 12 = × 12 = CONNECTIONS IN 12 × TABLE MULTIPLICATION.

5 × 9 = 45 6 × 9 = 54 7 × 9 = CONNECTIONS IN 9 × TABLE

3 × 7 = 21 6 × 7 = 42 7 × 7 = CONNECTIONS IN 7 × TABLE

8 Core Steps of success: I.Step:1 : DREAM SETTING: II. Step: 2 : LIST MAKING : IV. Step: 4 : SHOW THE PLAN: III. Step: 3 : INVITATION: V. Step: 5 : FOLLOW.

U A B II III I IV 94.

Presentation transcript:

Network Demarcation in 802.1aj Alan McGuire IEEE Eilat Interim May 2008

Introduction Annex K of 802.1aj contains some use cases and invites suggestions for more! Following slides suggest some other scenarios –Provider to provider cases rather than enterprise to provider –Also current models do not consider End 2 End Discuss –Are they allowed in the 802.1aj model? –Can they be managed? –Should any be included as Use Cases in annex K? Use Cases –Multiple TPMRs, Multiple Domains –Use with PBB

Multiple TPMRs, Multiple Domains TPMR Provider Bridge Provider Bridge Ext Link Ext Link NNI User Link User Link Domain A Domain B Ext Link Notes -Management of Domain A is separate from that of Domain B -Can TPMRs in Domain B be managed in this scenario? > need something between them -NNI is UNI in Enterprise-Provider examples

Multiple TPMRs, Multiple Domains TPMR Provider Bridge Provider Bridge User Link User Link NNI Ext Link Ext Link Domain A Domain B Ext Link Notes -Management of Domain A is separate from that of Domain B -Can TPMRs in Domain B be managed in this scenario? > need something else

Multiple TPMRs, Multiple Domains TPMR Provider Bridge Provider Bridge Ext Link Ext Link NNI User Link User Link Domain A Domain B Ext Link Notes -Management of Domain A is separate from that of Domain B -Can TPMRs in Domain B be managed in this scenario? -NNI is UNI in Enterprise-Provider examples 802.1ah encaps

Options to consider-I UserSP1SP2User UNI ENNI User Link Extension Links Extension Links Would seem to be ok since -user link should prevent E-W OAM issues - SNMP issues

Options to consider-II UserSP1SP2User UNI ENNI Ext Link Extension Links Extension Links Would seem to present problems since Ext Link will likely: -not present SPx access to SPy TPMRs for E-W OAM beyond pt of connectivity -not prevent SPx access via SNMP stack to SPy TPMRs User Link

Options to consider-III UserSPASPA’ User UNI ENNI Extension Links Extension Links Same as option I however limitation with A=A’ No access from SPa(1) to SPa(2) between 1 and 2 User Link OP1 Extension Links ENNI A=A’ Or A  A’

Options to consider-IV UserSPASPA’ User UNI ENNI Extension Links Extension Links Same issues as II User Link OP1 Extension Links ENNI A=A’ Or A  A’ User Link Ext Link

Options to consider-V SPA ENNI Extension Links Extension Links OP1 Extension Links ENNI mgmt OAM Can this be achieved via hierarchy?