MPLSTP OAM Framework

1
MPLS-TP OAM Framework

• Italo Busi (Editor)
• Ben Niven-Jenkins (Editor)

2
Current contributors

• Annamaria Fulignoli, Enrique Hernandez-Valencia,
  Lieven Levrau, Dinesh Mohan, Vincenzo Sestito,
  Nurit Sprecher, Huub van Helvoort, Martin
  Vigoureux, Yaacov Weingarten, Rolf Winter

3
Document History

• First presented at IETF 73 (Nov 08)
• Accepted as WG draft at IETF 74 (Mar 09)
• Version 01 uploaded for IETF 75

4
Changes from v00 to v01

• Terminology alignment with draft-ietf-mpls-tp-requ
  irements-02
• Scoped to be just a framework.
• A new draft will be developed for providing the
  overview.
• Added new OAM functionality
• Delay Measurement
• Loss Measurement
• Detailed description of pro-active CC-V defects
• Added considerations for p2mp transport paths

5
p2mp Transport Paths

• OAM measurements are different for each Root,
  Leaf relationship
• Fault conditions depending from where the
  failure is located
• Packet loss depending from where the packets
  are lost
• Packet delay depending on different paths
• Each leaf terminates OAM messages to monitor its
  own Root, Leaf relationship

6
p2mp Transport Paths
Leaf1
(dLOC)
Root
Leaf2
(dLOC)
Leaf3
(dLOC)
7
p2mp Transport Paths
Leaf1
(dLOC)
Root
Leaf2
(dLOC)
Leaf3
8
p2mp Transport Paths
Leaf1
(dLOC)
Root
Leaf2
Leaf3
9
Open Issues

• Further clarifications
• Fate sharing for pro-active CC/CV is related to
  the forwarding behavior and not to the QoS
  behavior
• Actions of a MEP/MIP when it receives an
  unexpected packet
• Lock Behavior
• Tandem connection vs Path Segment Tunnel
• ME vs MEG with p2mp transport paths

10
Next Steps

• Close the open issues
• Complete the framework part
• Complete considerations for p2mp transport paths
• Diagnostic (?)
• Route Tracing
• Lock Instruct