1 / 6

IETF-90 (Toronto) speaker: Ravi Singh

draft-singh-l2vpn-bgp-vpls-control-flags-01.txt Updated processing of control flags for BGP VPLS. Ravi Singh (ravis@juniper.net) Kireeti Kompella (kireeti@juniper.net) Senad Palislamovic (senad.palislamovic@alcatel-lucent.com). IETF-90 (Toronto) speaker: Ravi Singh.

penn
Download Presentation

IETF-90 (Toronto) speaker: Ravi Singh

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-01.txt • Updated processing of control flags for BGP VPLS Ravi Singh (ravis@juniper.net)Kireeti Kompella (kireeti@juniper.net)Senad Palislamovic (senad.palislamovic@alcatel-lucent.com) IETF-90 (Toronto) 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-90

  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-90

  4. Feedback on “-00” @ IETF-88 (Vancouver) • Address multi-homing cases • Get feedback Updated processing of control flags for BGP VPLS IETF-90

  5. New in “-01” • Additional co-author • Single-homed sites: • Behavior for S-bit mismatch handling changed w.r.t. “-00” • Use of p2mp transport clarified due to change (w.r.t. “-00”) of behavior for handling S-bit mismatch • Multi-homed site use-cases addressed: • C-bit mismatch behavior specified for multi-homed sites • S-bit mismatch behavior specified for multi-homed sites • Use of p2mp transport for above mismatches specified Updated processing of control flags for BGP VPLS IETF-90

  6. Next steps • Requesting WG adoption: • Draft addresses valid deployment scenarios that operators face • Scope of draft specifies behavior for mismatch of standardized bits in the control-flags field • Work-in-progress drafts that are defining new (not already standardized) bits in control-flags would address mismatch for those bits separately Updated processing of control flags for BGP VPLS IETF-90

More Related