Common Framework for OAM IEEE 802.1 Meeting San Diego July 16th-20th, 2012 by Tissa Senevirathne Donald Eastlake 3rd Objective Explore complementary OAM model between IEEE 802.1 and IETFTRILL Explore Leveraging Existing OAM Framework for
"Common Framework for OAM IEEE 802.1 Meeting San" is the property of its rightful owner. Permission is granted to
download and print the materials on this website for personal, non-commercial use only, and to display it
on your personal computer provided you do not modify the materials and that you retain all copyright
notices contained in the materials. By downloading content from our website, you accept the terms of this
agreement.
Presentation Transcript
01
Common Framework for OAM IEEE 802.1 Meeting San Diego
July 16th-20th, 2012
by
Tissa Senevirathne
Donald Eastlake 3rd<br>
02
Objective Explore complementary OAM model between IEEE 802.1 and IETF/TRILL
Explore Leveraging Existing OAM Framework for the purpose 2<br>
03
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<br>
04
Scope of TRILL OAM vs 802.1ag (CFM) MEP 802.1ag TRILL OAM TRILL Network 802.1 LAN 802.1 LAN 802.1 Bridge TRILL Switch MIP 4<br>
05
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<br>
06
Common OAM Frame Structure Encapsulation Header Flow Entropy Message Channel Technology Dependent
Addresses MEP (end Points)
Drives Forwarding decisions Technology Dependent
Influence Forwarding decisions Drives OAM Functions
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<br>
07
Common OAM Concepts/Functional Elements Common OAM Functional elements
Maintenance Domains
Maintenance Associations (MA)
Maintenance End Points (MEP)
Maintenance Intermediate Points (MIP) 7<br>
08
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<br>
09
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<br>
10
References TRILL OAM Requirements (WG document)
draft-ietf-trill-oam-req-00
TRILL OAM Framework (Individual submission)
draft-salam-trill-oam-framework-00
Use of 802.1ag for TRILL (Individual submission)
draft-tissa-trill-8021ag-00 10<br>