OAM IEEE 8021 Meeting San Diego July 16 th 20 th 2012 b y Tissa Senevirathne Donald Eastlake 3 rd Objective Explore complementary OAM model between IEEE 8021 and IETF TRILL ID: 586409
Download Presentation The PPT/PDF document "Common Framework for" is the property of its rightful owner. Permission is granted to download and print the materials on this web site 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.
Slide1
Common Framework for OAM
IEEE
802.1 Meeting
San Diego
July
16
th
-20
th
, 2012
b
y
Tissa Senevirathne
Donald Eastlake 3
rdSlide2
Objective
Explore complementary
OAM
model between IEEE 802.1 and IETF/TRILLExplore Leveraging Existing OAM Framework for the purpose
2Slide3
OAM Model
Goal of
OAM
Complement and coexist rather than re-invent and competeOAM
Framework
Common
OAM frame structureCommon OAM concepts/semantics/Functional elementsCommon OAM messaging formatThis allow us to reuse the same frameworkFaster Time to MarketUniform user experience
3Slide4
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
4Slide5
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
ModelSlide6
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 technologiesYet, there are no established common OAM framework
6Slide7
Common
OAM
Concepts/Functional Elements
Common OAM Functional elementsMaintenance DomainsMaintenance Associations (MA)Maintenance End Points (MEP)
Maintenance Intermediate Points (MIP)
7Slide8
Common
OAM
Message Channel
Utilize 802.1ag Messaging Re-use TLV and opcodes where commonality existIETF
/TRILL specific
opcodes
for Technology specific functions.8Slide9
Next Steps
Your comment/Feedback on the general direction of having a common
OAM
framework between IEEE and TRILL/IETFIf we do agree this is the right thing to doThen how can we collaborate and workout the details ?
9Slide10
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