MPLSTP OAM Framework Italo Busi Editor Ben NivenJenkins

MPLS-TP OAM Framework Italo Busi (Editor) Ben Niven-Jenkins (Editor)

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

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

Changes from v 00 to v 01 • Terminology alignment with draft-ietf-mpls-tprequirements-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 p 2 mp transport paths

p 2 mp 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

p 2 mp Transport Paths Leaf 1 (d. LOC) Root Leaf 2 (d. LOC) Leaf 3 (d. LOC)

p 2 mp Transport Paths Leaf 1 (d. LOC) Root Leaf 2 (d. LOC) Leaf 3

p 2 mp Transport Paths Leaf 1 (d. LOC) Root Leaf 2 Leaf 3

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

Next Steps • Close the open issues • Complete the framework part – Complete considerations for p 2 mp transport paths – Diagnostic (? ) – Route Tracing – Lock Instruct