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

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

Embed Size (px)

Citation preview

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

Common Framework for OAM

IEEE 802.1 Meeting San DiegoJuly 16th-20th, 2012

byTissa SenevirathneDonald Eastlake 3rd

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

Objective

Explore complementary OAM model between IEEE 802.1 and IETF/TRILL

Explore Leveraging Existing OAM Framework for the purpose

2

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

OAM ModelGoal 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

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

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

MIP4

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

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 La

yers

OS

I Mod

el

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

Common OAM Frame Structure

Encapsulation Header

Flow Entropy Message 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

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

Common OAM Concepts/Functional Elements

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

7

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

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

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

Next StepsYour 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