1 802.1ag discussion may 18, 2004 ali sajassi [email protected] paul bottorf...
TRANSCRIPT
222
Where are we ?
• We have come along a long way since first preso on this topic to 802.1 group was made a year ago (June 2003)
• Since then, lots of work has been done in ITU and MEF
• Since then, many presentations/contributions (in coordination with ITU & MEF) have been made on this topic to this group
• Since then, a PAR has been approved
333
What’s the Scope ?
• The following Connectivity Fault Management functionality
- Fault Detection: Continuity Check
- Fault Verification: Loop Back
- Fault Isolation: Trace Route
• Concept of Domain & Domain Level
• Concept of Maintenance Entity
- Maintenance End Point (MEP)
- Maintenance Intermediate Point (MIP)
444
What’s outside of the Scope ?
• Performance Management Functionality such as
- Frame Loss Measurement
- Delay Measurement
- Delay Variation Measurement
- Availability Measurement
• Connectivity Fault Indication such as AIS and alarm suppression ?
• Connectivity Fault Recovery (it is assumed to be taken care by xSTP) – e.g., not intention to do protection switching here
555
What’s need to be decided ?
• Where to put the Maintenance Entity
- What functionality is needed at different MAC sub-layers
- What functionality is needed at LLC level
- How to model a bridge
• Domain Level- Absolute versus Relative
- Multicast versus Unicast traffic
666
Maintenance Entity
• 802.1ad defines three types of services- Port based
- VLAN based
- VLAN bundling
• ITU defined Maintenance Points based on IEEE Provider Bridge models for the above services
• Now need to define IEEE bridge model(s) for these Maintenance Points
777
Port-based Service
C-Tag
CustomerEquipment
CustomerEquipment
Operator ABridges
Operator BBridges
ETH
1 2b 3 4 5 6b 7
11122122
10S-Tag
Untagged
888
802.1Q T
agg
ing
“Y”80
2.1Q
Tag
gin
g “
Y”
Provider Bridge: S-VLAN aware component - 2b
LLCHigher Layer Entities
LLC LLC
802.
1ag
Up
CM
Sh
im
802.
1ag
Do
wn
CM
Sh
im
802.1ag U
p C
M S
him
802.1ag D
ow
n C
M S
him
Relay
LLCLLC LLC
MEP
MEP
MIPMIPMIPMIP MIPMIP
999
C-Tag
CustomerEquipment
CustomerEquipment
Operator ABridges
Operator BBridges
ETH
1 2a 2b 3 4 5 6b 6a 7
11122122
11122122
1020S-Tag
Untagged
C-Tag
VLAN Bundling Service
101010
802.1Q T
agg
ing
“Y”80
2.1Q
Tag
gin
g “
Y”
C-VLAN aware Component – 2a
LLCHigher Layer Entities
LLC LLC
802.
1ag
Up
CM
Sh
im
802.
1ag
Do
wn
CM
Sh
im
802.1ag U
p C
M S
him
802.1ag D
ow
n C
M S
him
Relay
LLCLLC LLC
MIP
MEP
MIP
MEP
MIP
MEP
MIP
MEP
111111
802.1Q T
agg
ing
“Y”80
2.1Q
Tag
gin
g “
Y”
S-VLAN aware component – 2b
LLCHigher Layer Entities
LLC LLC
802.
1ag
Up
CM
Sh
im
802.
1ag
Do
wn
CM
Sh
im
802.1ag U
p C
M S
him
802.1ag D
ow
n C
M S
him
Relay
LLCLLC LLC
MEP
MEP
MIP
MEP
MEP
MIP
121212
Different ways of Implementing ITU models
1. Bridge “Brain” LLC
2. Bridge Port LLC
3. Bridge Port MAC sub-layer
131313
Bridge “Brain” LLC
141414
Bridge Port LLC
151515
Bridge Port MAC sub-layer
161616
802.1ad Model
Clause 6.5
MAC RelayEntity
Clause 6.5
Clauses8.5, 6.7,S-TAG
Clauses8.5, 6.7,
S-TAG
C-VLAN awareBridge
S-VLAN awareBridge
ISSISS
Clause 6.5 Clause 6.5
MAC RelayClauses8.5, 6.7,9.5 (b)
Clauses8.5, 6.7,
9.5(b)ISSISS
Provider Bridge
171717
802.1ag Model – Which one ?
C-VLAN awareBridge
S-VLAN awareBridge
Clause 6.5 Clause 6.5
MAC Relay
Provider Bridge
ISSISS
(2) (1)
(3)
MAC Relay
(2) (2)(1)
(3)(3)
Clause 6.5 Clause 6.5
ISSISS