1 / 10

Common Framework for OAM

Common Framework for OAM. IEEE 802.1 Meeting San Diego July 16 th -20 th , 2012 b y Tissa Senevirathne Donald Eastlake 3 rd. Explore complementary OAM model between IEEE 802.1 and IETF /TRILL Explore Leveraging Existing OAM Framework for the purpose. Objective. Goal of OAM

jinelle-taylor
Download Presentation

Common Framework for OAM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. 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 OAM Model

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

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

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

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

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

  9. 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 ? Next Steps

  10. 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 References

More Related