MPLS-TP Lock Instruct MPLS WG, IETF 76, Hiroshima, 9 Nov 2009 draft-dai-mpls-tp-lock-instruct-00draft-dai-mpls-tp-lock-instruct-00 ZTE Corporation Xuehui Dai ( Bo Wu ( Jian Yang (

Agenda Introduction Message Format Procedures Examples Next step

Introduction The aim of this document is to define an MPLS-TP OAM mechanism to meet the requirements for Lock Instruction functionality as required in MPLS-TP OAM Requirements. Function: enable an End Point of a PW, LSP or Section to instruct its associated End Point(s) to lock the PW, LSP or Section.

Background Related draft draft-boutros-mpls-tp-loopback-02.txt Applications Loopback: full loopback ( OAM& user traffic ) Performance monitor: out-of-service Diagnostic test: out-of-service

Example: bidirectional LSP Bidirectional LSP: A---B---C---D, and bidirectional lock operations A BC D MEP MIP 1 lock requests periodically 2 examines the received lock requests and creates lock responses according to results 3 send lock responses 5 unlock requests periodcally 7 send unlock responses successful 8 stop sending unlock requests while receive a successful response 6 examines the received lock requests and creates unlock responses according to results

Message Format ACH Encapsulation RFC | |Version| Reserved | 0xHH(MPLS-TP Lock Instruct) | Message PDU | Version | Message Type | Lock Type | Period | | Return Code | Cause Code | Reserved | | TLV's | ~ ~ Message type: lock/unlock request/response Lock type: unidirectional/bidirectional lock lock clear Unidirectional lock locks one direction of a bidirectional path Bidirectional lock locks both directions of a bidirectional path Return Code: success/failure Cause code: indicates the reason why lock/unlock fails TLVs: Source and Destination MEP TLV Authentication TLV. Both are optional

Next step Comments and feedback of the WG draft will be updated according to these comments