MPLSTP Lock Instruct MPLS WG IETF 76 Hiroshima
- Slides: 7
MPLS-TP Lock Instruct MPLS WG, IETF 76, Hiroshima, 9 Nov 2009 draft-dai-mpls-tp-lock-instruct-00 ZTE Corporation Xuehui Dai ( dai. xuehui@zte. com. cn ) Bo Wu ( wu. bo@zte. com. cn ) Jian Yang ( jian_yang@zte. com. cn )
Agenda p Introduction p Message Format p Procedures p Examples p 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 MEP A MIP B C MEP D 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 u ACH Encapsulation （RFC 5586） u Message PDU 0 1 2 3 0 1 23456 78 9012345 6 78901 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |0 0 0 1 |Version| Reserved | 0 x. HH(MPLS-TP Lock Instruct) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 0 1 2 3 012 3 456 78 901234567 8 9 0123 4 5 678 901 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 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
