1. 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 ( dai.xuehui@zte.com.cn )dai.xuehui@zte.com.cn Bo Wu ( wu.bo@zte.com.cn )wu.bo@zte.com.cn Jian Yang ( jian_yang@zte.com.cn )jian_yang@zte.com.cn

2. Agenda Introduction Message Format Procedures Examples Next step

3. 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.

4. 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

5. 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

6. Message Format ACH Encapsulation RFC 5586 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0 0 0 1 |Version| Reserved | 0xHH(MPLS-TP Lock Instruct) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Message PDU 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 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

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