1 / 6

Ravi Singh (ravis@juniper.net) Kireeti Kompella (kireeti@juniper.net)

draft-singh-l2vpn-bgp-vpls-control-flags-00.txt Updated processing of control flags for BGP VPLS. Ravi Singh (ravis@juniper.net) Kireeti Kompella (kireeti@juniper.net). IETF-88 (Vancouver) speaker: Ravi Singh. BGP VPLS : Summary and an issue.

sage
Download Presentation

Ravi Singh (ravis@juniper.net) Kireeti Kompella (kireeti@juniper.net)

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. draft-singh-l2vpn-bgp-vpls-control-flags-00.txt • Updated processing of control flags for BGP VPLS Ravi Singh (ravis@juniper.net)Kireeti Kompella (kireeti@juniper.net) IETF-88 (Vancouver) speaker: Ravi Singh

  2. BGP VPLS: Summary and an issue • Summary of BGP VPLS: efficiency of control messaging • A PE’s NLRI specifies behavior expected from all otherPEs in that block (per VPLS): • VPLS label to use • Behavior regarding acting on control flags, etc • Issue: PE behavior when mismatching settings of control flags: • Expectation of NLRI-originating PE cannot be met by every remote PE (w.r.t. acting on received control flags) • No support for selectively asking only some PEs to act on control flags • What do the other PEs do? What does NLRI-originating-PE do? • Ignore the mismatch? • Not bring up the PW? Updated processing of control flags for BGP VPLS IETF-88

  3. What is this draft about? • Supporting mixed-settings of control flags in a given VPLS: • Making BGP VPLS work when PEs differ in their settings of the control flags • For every (per-VPLS) PE-pair, if one PE does not have the same value for C-bit, the PW between the pair still comes up. However, does not use CW. • Similarly for other bits in the control-flags • Works in a backward compatible fashion • Enabling use of p2mp LSPs as transport when PEs in per-VPLS PE-set have mismatching control flags Updated processing of control flags for BGP VPLS IETF-88

  4. Illustrative BGP VPLS: 1/2 Using C-bit to illustrate the issue Assume: CW-capable PE s: PE1, PE2 CW-non-capable PE: PE3 Can each PE forward customer traffic to sites behind every other PE? Customer 2 Customer 1 … … RR Customer 2 PE1 … E PE2 B A D PE3 … C Customer 1 … … Customer 1 Customer 2 Updated processing of control flags for BGP VPLS IETF-88

  5. Illustrative BGP VPLS: 2/2 Using C-bit to illustrate the issue Assume: CW-capable PE s: PE1, PE2 CW-non-capable PE: PE3 Can each PE forward customer traffic to sites behind every other PE? Customer 2 Customer 1 … … RR Customer 2 PE1 … E PE2 B A D PE3 … C Before this draft: UP PW (uses CW): PE1-PE2 Down PWs: PE1-PE3, PE2-PE3 With this draft: all PWs come up. UP PW (uses CW): PE1-PE2 UP PWs (not using CW): PE1-PE3, PE2-PE3 Customer 1 … … Customer 1 Customer 2 Updated processing of control flags for BGP VPLS IETF-88

  6. Next steps • Soliciting feedback • Progressing in the WG Updated processing of control flags for BGP VPLS IETF-88

More Related