1 / 7

Flow Aware PW for VPLS draft-yong-l2vpn-fat-pw-4-vpls-00.txt

Flow Aware PW for VPLS draft-yong-l2vpn-fat-pw-4-vpls-00.txt. lucyyong@huawei.com. ECMP Paths. Flow Aware PW (FA-PW). Flow Aware PW & VPLS. Flow Aware PW (FA-PW) lets a PW to take advantage of ECMP and LAG Flow label provides addition flow granularity in a PW

uta-boyle
Download Presentation

Flow Aware PW for VPLS draft-yong-l2vpn-fat-pw-4-vpls-00.txt

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. Flow Aware PW for VPLS draft-yong-l2vpn-fat-pw-4-vpls-00.txt lucyyong@huawei.com IETF79, Beijing China

  2. ECMP Paths Flow Aware PW (FA-PW) Flow Aware PW & VPLS • Flow Aware PW (FA-PW) lets a PW to take advantage of ECMP and LAG • Flow label provides addition flow granularity in a PW • Individual flows in a PW are distributed over multi-paths • FA-PW BW may be larger than individual path BW • Draft-ietf-pwe3-fat-pw-04.txt • VPLS uses PW for transport between PEs • RFC4761 is BGP based • RFC4762 is LDP based IETF79, Beijing China

  3. FA-PW VSI VSI ACs ACs PE1 PE2 Flow Aware PW for VPLS • Advantage to use FA-PW for VPLS • Most of VPLS services carry IP payload • VPLS traffic between a pair of PEs can be larger than single path capacity • ECMP and LAG may apply to VPLS traffic • RFC4761 and RFC4762 extension to inform peer PE about the presence of flow label on PW IETF79, Beijing China

  4. RFC4761 Extension Use two new bits in Control Flag Bit Vector 0 1 2 3 4 5 6 7 +-+-+-+-+-+-+-+-+ | MBZ |T|R|C|S| (MBZ = MUST Be Zero) +-+-+-+-+-+-+-+-+ Name C and S remain the same meaning as [RFC4761] Name T and R are defined in the draft o When T=1 the PE can send a PW packet with a flow label present. When T=0, the PE sends a PW packet without a flow label. o When R=1 the PE can receive a PW packet with a flow label present. When R=0 the PE is unable to receive a PW packet with the flow label present. Support Backward Compatibility IETF79, Beijing China

  5. RFC4762 Extension • Adopt Flow Label Sub-TLV as optional interface parameters to inform the presence of flow label on VPLS PW • PE process procedure is identical to the draft • Draft-ietf-pwe3-fat-pw-04.txt • Support Backward Compatibility IETF79, Beijing China

  6. Other Consideration • MAC learning in VSI is done per a FA-PW association • Identical as a PW w/o flow label • One VPLS may use a FA-PW b/w a pair of PEs and a PW b/w another pair of PEs • Great support for network migration • Flow identification is done locally at ingress PE • Outside the scope of the draft IETF79, Beijing China

  7. Acknowledgement • Thank Adrian Farrel and Mach Chen for the review and valuable suggestions Next Step • Open for the feedback • Suggest to adopt it as WG draft IETF79, Beijing China

More Related