1 / 11

LDP Extensions for Pseudo Wire (PW) Transfer in an MPLS-TP Network

LDP Extensions for Pseudo Wire (PW) Transfer in an MPLS-TP Network. draft-bao-pwe3-pw-transfer-00.txt. Yuanlin Bao: bao.yuanlin@zte.com.cn Lizhong Jin: lizhong.jin@zte.com.cn Ruiquan Jing: jingrq@ctbri.com.cn Xiaoli Huo: huoxl@ctbri.com.cn. Background. Merged the following drafts

oya
Download Presentation

LDP Extensions for Pseudo Wire (PW) Transfer in an MPLS-TP Network

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LDP Extensions for Pseudo Wire (PW) Transfer in an MPLS-TP Network • draft-bao-pwe3-pw-transfer-00.txt Yuanlin Bao: bao.yuanlin@zte.com.cn Lizhong Jin: lizhong.jin@zte.com.cn Ruiquan Jing: jingrq@ctbri.com.cn Xiaoli Huo: huoxl@ctbri.com.cn

  2. Background • Merged the following drafts • draft-bao-mpls-tp-path-transfer-reqs-00.txt • presented on the 77th meeting • disscussed in MPLS mailing list • draft-fuxh-mpls-tp-transfer-framework-00.txt • presented on the 77th meeting • draft-bao-pwe3-pw-transfer-ldp-ext • Contents of this draft • discusses the advantage compared with MBB • LDP extensions and procedures • the PW Transfer Capability TLV • PW Ownership Transfer TLV • S-PE TLV and Sub-TLV (draft-ietf-pwe3-segmented-pw)

  3. Comparison with Make Before Break(MBB)

  4. Requirements • Requirements • Requirement 55 of RFC5654 • draft-ietf-ccamp-mpls-tp-cp-framework-03.txt • Requirement 47 • Section 5.3.3 • Requirements in RFC5493 also apply • Additional requirements • PW attributes MUST not be changed • PW transfer MUST be independent of LSP • Support partial MS-PW segments transfer

  5. LDP Extension • PW Transfer Capability TLV 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |1|0|PW Transfer Capability(TBD)| Length (= 1) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |1| Reserved | +-+-+-+-+-+-+-+-+ • Carried in LDP Initialization Message (RFC5561) • Negotiating the PW transfer capability between LDP Peers • PW switching point TLV (S-PE TLV) and Sub-TLV • defined in draft-ietf-pwe3-segmented-pw • used to carry the data plane PW path

  6. LDP Extension (cont.) • PW Ownership TransferTLV • Carried in LDP Label Mapping and Notification message • 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| PW Transfer | Length | • +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • |POT| Reserved | • +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • POT(2 bits): PW Ownership Transfer • 1 - PW ownership transfer from MP to CP • 2 - PW ownership transfer from CP to MP

  7. MP to CP Transfer Procedure(SS-PW) • T-PEs • Negotiate PW transfer capability • Send/Receive Label Mapping message with PW Transfer TLV • Create/Maintain PW signaling state in CP

  8. MP to CP Transfer Procedure (MS-PW) • T-PEs • Perform all the procedures in MP2CP SS-PW transfer plus • encoding PW path into S-PE TLV and Sub-TLV • S-PEs • create PW LDP signaling state in CP • decode the S-PE TLV and Sub-TLV to find the next hop • forward Label Mapping message to the next hop

  9. CP to MP Transfer Procedure • T-PEs • send CP2MP PW transfer Notification message • delete T-LDP session according to the local policy • S-PEs • forward Notification message • delete T-LDP session according to the local policy

  10. Next Steps • Refine the document according to the feedback of this meeting and mailing list.

  11. Comments ? Thank you !

More Related