Presentation is loading. Please wait.

Presentation is loading. Please wait.

Common Framework for OAM IEEE 802.1 Meeting San Diego July 16 th -20 th, 2012 by Tissa Senevirathne Donald Eastlake 3 rd.

Published byHugh Lewis Modified over 9 years ago

Similar presentations

Presentation on theme: "Common Framework for OAM IEEE 802.1 Meeting San Diego July 16 th -20 th, 2012 by Tissa Senevirathne Donald Eastlake 3 rd."— Presentation transcript:

1 Common Framework for OAM IEEE 802.1 Meeting San Diego July 16 th -20 th, 2012 by Tissa Senevirathne Donald Eastlake 3 rd

2 Objective Explore complementary OAM model between IEEE 802.1 and IETF/TRILL Explore Leveraging Existing OAM Framework for the purpose 2

3 OAM Model Goal of OAM ◦Complement and coexist rather than re-invent and compete OAM Framework ◦Common OAM frame structure ◦Common OAM concepts/semantics/Functional elements ◦Common OAM messaging format ◦This allow us to reuse the same framework  Faster Time to Market  Uniform user experience 3

4 Scope of TRILL OAM vs 802.1ag (CFM) MEP 802.1ag TRILL OAM TRILL Network 802.1 LAN 802.1 Bridge TRILL Switch MIP 4

5 Scope TRILL OAM vs 802.1ag (CFM) Link Network 802.1ag/802.3ah TRILL OAM Transport (end-end) 802.1ag 5 Physical Session Presentation Application Media Layers Host Layers OSI Model

6 Common OAM Frame Structure Encapsulation Header Flow EntropyMessage Channel 1.Technology Dependent 2.Addresses MEP (end Points) 3.Drives Forwarding decisions 1.Technology Dependent 2.Influence Forwarding decisions 1.Drives OAM Functions 2.SHOULD be common across Technologies (SDO) OAM Message structures are similar between many technologies Most OAM functions are common across technologies Yet, there are no established common OAM framework 6

7 Common OAM Concepts/Functional Elements Common OAM Functional elements ◦Maintenance Domains ◦Maintenance Associations (MA) ◦Maintenance End Points (MEP) ◦Maintenance Intermediate Points (MIP) 7

8 Common OAM Message Channel Utilize 802.1ag Messaging ◦Re-use TLV and opcodes where commonality exist ◦IETF/TRILL specific opcodes for Technology specific functions. 8

9 Next Steps Your comment/Feedback on the general direction of having a common OAM framework between IEEE and TRILL/IETF If we do agree this is the right thing to do ◦Then how can we collaborate and workout the details ? 9

10 References TRILL OAM Requirements (WG document) ◦draft-ietf-trill-oam-req-00draft-ietf-trill-oam-req-00 TRILL OAM Framework (Individual submission) ◦draft-salam-trill-oam-framework-00draft-salam-trill-oam-framework-00 Use of 802.1ag for TRILL (Individual submission) ◦draft-tissa-trill-8021ag-00draft-tissa-trill-8021ag-00 10

Download ppt "Common Framework for OAM IEEE 802.1 Meeting San Diego July 16 th -20 th, 2012 by Tissa Senevirathne Donald Eastlake 3 rd."

Similar presentations

FCoE over TRILL draft-mme-trill-fcoe-00 Informational

FCoE over TRILL draft-mme-trill-fcoe-00 Informational
802.1ag - Connectivity Fault Management Tutorial – Part 1 Dinesh Mohan July 12, 2004.

802.1ag - Connectivity Fault Management Tutorial – Part 1 Dinesh Mohan July 12, 2004.
July 2006IETF TRILL1 Multicast MAC Addresses for Standards Use Donald E. Eastlake 3 rd +1-508-786-7554.

July 2006IETF TRILL1 Multicast MAC Addresses for Standards Use Donald E. Eastlake 3 rd
Directory Assisted TRILL Encapsulation by non-TRILL nodes (Directory Reliant Smart End Node) Linda Dunbar Donald Eastlake Radia Perlman Igor Gashinsky.

Directory Assisted TRILL Encapsulation by non-TRILL nodes (Directory Reliant Smart End Node) Linda Dunbar Donald Eastlake Radia Perlman Igor Gashinsky.
v3.1 CIS151 Module 2 JEOPARDY K. MartinG. Valencia.

v3.1 CIS151 Module 2 JEOPARDY K. MartinG. Valencia.
Common OAM between IEEE 802.1 and IETF/TRILL Tissa Senevirathne Donald Eastlake September, 2012.

Common OAM between IEEE and IETF/TRILL Tissa Senevirathne Donald Eastlake September, 2012.
Protocols and the TCP/IP Suite

Protocols and the TCP/IP Suite
1 Review of Important Networking Concepts Introductory material. This module uses the example from the previous module to review important networking concepts:

1 Review of Important Networking Concepts Introductory material. This module uses the example from the previous module to review important networking concepts:
Networking Solutions Chapter 2 – The OSI Model. The Layered Approach Similar to a company like ◦ Advantages ◦Divides the network into ◦Multiple vendors.

Networking Solutions Chapter 2 – The OSI Model. The Layered Approach Similar to a company like ◦ Advantages ◦Divides the network into ◦Multiple vendors.
The OSI Model. 001 011 0 1 1 0 FTP API 7. Application 6. Presentation 5. Session 4. Transport 3. Network 2. Data Link 1. Physical HTTP Software.

The OSI Model FTP API 7. Application 6. Presentation 5. Session 4. Transport 3. Network 2. Data Link 1. Physical HTTP Software.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Communicating over the Network Network Fundamentals – Chapter 2.

© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Communicating over the Network Network Fundamentals – Chapter 2.
LECTURE 2 CT1303 LAN. STANDARD MODELS: OSI Model : Open system Interconnection. is a conceptual model that characterizes and standardizes the internal.

LECTURE 2 CT1303 LAN. STANDARD MODELS: OSI Model : Open system Interconnection. is a conceptual model that characterizes and standardizes the internal.
Session Policy Framework using EAP draft-mccann-session-policy-framework-using-eap-00.doc IETF 76 – Hiroshima Stephen McCann, Mike Montemurro.

Session Policy Framework using EAP draft-mccann-session-policy-framework-using-eap-00.doc IETF 76 – Hiroshima Stephen McCann, Mike Montemurro.
1 Review of Important Networking Concepts Introductory material. This slide uses the example from the previous module to review important networking concepts:

1 Review of Important Networking Concepts Introductory material. This slide uses the example from the previous module to review important networking concepts:
Chapter 2 Network Models Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.

Chapter 2 Network Models Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
1 Introducing the Specifications of the Metro Ethernet Forum.

1 Introducing the Specifications of the Metro Ethernet Forum.
Protocols and the TCP/IP Suite Chapter 4. Multilayer communication. A series of layers, each built upon the one below it. The purpose of each layer is.

Protocols and the TCP/IP Suite Chapter 4. Multilayer communication. A series of layers, each built upon the one below it. The purpose of each layer is.
CECS 5460 – Assignment 3 Stacey VanderHeiden Güney.

CECS 5460 – Assignment 3 Stacey VanderHeiden Güney.
TRILL OAM draft-eastlake-trill-rbridge-channel-00 draft-bond-trill-rbridge-oam-01 draft-manral-trill-bfd-encaps-01 Donald Eastlake 3 rd Huawei Technologies.

TRILL OAM draft-eastlake-trill-rbridge-channel-00 draft-bond-trill-rbridge-oam-01 draft-manral-trill-bfd-encaps-01 Donald Eastlake 3 rd Huawei Technologies.
Internet Addresses. Universal Identifiers Universal Communication Service - Communication system which allows any host to communicate with any other host.

Internet Addresses. Universal Identifiers Universal Communication Service - Communication system which allows any host to communicate with any other host.

Similar presentations

Ads by Google