Kireeti Kompella kireetijunipernet Senad Palislamovic senadpalislamovicalcatellucentcom IETF90 Toronto speaker Ravi Singh draftsinghl2vpnbgpvplscontrolflags01txt Updated processing of control flags for BGP VPLS ID: 344233
Download Presentation The PPT/PDF document "Ravi Singh (ravis@juniper.net)" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Ravi Singh (ravis@juniper.net)Kireeti Kompella (kireeti@juniper.net)Senad Palislamovic (senad.palislamovic@alcatel-lucent.com)
IETF-90 (Toronto)speaker: Ravi Singh
draft-singh-l2vpn-bgp-vpls-control-flags-01.txt
Updated processing of control flags for BGP VPLSSlide2
BGP VPLS: Summary and an issue
Summary of BGP VPLS: efficiency of control messagingA PE’s NLRI specifies behavior expected from all other
PEs in that block (per VPLS):
VPLS label to useBehavior regarding acting on control flags, etcIssue: 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 flagsWhat do the other PEs do? What does NLRI-originating-PE do?Ignore the mismatch?Not bring up the PW?
2
Updated processing of control flags for BGP VPLS
IETF-90Slide3
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 fashionEnabling use of p2mp LSPs as transport when PEs in per-VPLS PE-set have mismatching control flagsUpdated processing of control flags for BGP VPLSIETF-903Slide4
Feedback on “-00” @ IETF-88 (Vancouver)
Address multi-homing cases
Get feedback
Updated processing of control flags for BGP VPLS
IETF-904Slide5
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 sitesS-bit mismatch behavior specified for multi-homed sitesUse of p2mp transport for above mismatches specifiedUpdated processing of control flags for BGP VPLSIETF-905Slide6
Next stepsRequesting WG adoption:
Draft addresses valid deployment scenarios that operators face
Scope of draft
specifies behavior for mismatch of standardized
bits in the control-flags fieldWork-in-progress drafts that are defining new (not already standardized) bits in control-flags would address mismatch for those bits separately6Updated processing of control flags for BGP VPLSIETF-90