MIP-related aspects of MPLS-TP OAM Greg Mirsky IETF-79

Requirements and State of OAM Art in regard to MIP Proactive CC/CV  Addresses MEP to MEP OAM  MIP directed OAM have to use SPME On-demand CC/CV  Target MIP Identifier  Uses MPLS TTL Data-plane Loopback of bi-directional co-routed connection  Target MIP Identifier  Uses MPLS TTL Segment OAM, including proactive CC/CV, LM & DM  supported through use of Sub-Path Maintenance Element (SPME)

Concerns with MIP directed OAM What is relationship between MIP (nodal, as well as in- and out- MIP) with MEP on an LER or T-PE?  Is MEP identical to nodal MIP and in-MIP or is it different MP? Clarify that on LER/T-PE nodal MIP and in-MIP identical with MEP.  How LER/T-PE processes OAM messages targeted to out-MIP if latter supported on the node? On LER/T-PE directed to out-MIP OAM packets must not be forwarded. Such packets might be dropped or send response with indication of erroneous request. Location of OAM target TLV varies  On-demand CV uses ACH TLV Header and MIP TLV is optional  Loopback OAM does not use ACH TLV format Canonical format of OAM packets?