IETF 77, Anaheim, March 21-26, 2010Page - 1 Requirements for Path Ownership Transfer between Management Plane and Control Plane in a MPLS-TP network draft-bao-mpls-tp-path-transfer-reqs-00.txt Yuanlin Bao Xihua Fu Malcolm Betts ZTE Corporation

IETF 77, Anaheim, March 21-26, 2010Page - 2 Requirements Current status – Some service providers have deployed MPLS-TP network for mobile backhaul. – Most of MPLS-TP paths are statically configured by Management Plane in the first stage. – It is desirable to transfer the control of path from the MP to CP in the future. Transfer from CP to MP should also be supported. – Ownership transfer must not impact traffic.

IETF 77, Anaheim, March 21-26, 2010Page - 3 Requirements (cont.) Current status – Ownership transfer requirement in MPLS-TP rfc5654 draft-abfb-mpls-tp-control-plane-framework-02.txt – Ownership transfer requirement of unidirectional and bidirectional LSP rfc5493 – RSVP-TE extension for LSP transfer draft-ietf-ccamp-pc-spc-rsvpte-ext-07.txt

IETF 77, Anaheim, March 21-26, 2010Page - 4 Motivations Explore other requirement – Ownership transfer of PW LDP sessions must be set up or deleted between the PW endpoints during the transfer. – Between T-PEs in SS-PW. – Between T-PE and S-PE, S-PE and S-PE in MS-PW. Support some PW segments transfer while others not – CP isnt used in all domains PW ownership transfer should be independent of LSP. It needs to define the extension of LDP for PW control transfer between MP and CP.

IETF 77, Anaheim, March 21-26, 2010Page - 5 Motivations (cont.) Explore other requirement – Ownership transfer of associated bidirectional LSP Ownership transfer of each unidirectional LSP must be independent. Both unidirectional LSP must be associated in order that edge nodes or transit nodes can be aware about the pairing relationship of the forward and the backward directions. It needs to define the extension of RSVP-TE or use the current solution for associated LSP control transfer.

IETF 77, Anaheim, March 21-26, 2010Page - 6 Motivations (cont.) Requirements in rfc5493 can be applied to MPLS- TP pathrfc5493 – Data plane path consistency – No disruption of user traffic – Support path transfer between MP and CP – Synchronization of state among nodes during conversion – Revertion after transfer failure

IETF 77, Anaheim, March 21-26, 2010Page - 7 Next Steps Refine the document according the feedback of meeting and mailing list