Presentation on theme: "BGP VPLS Auto Site ID Bhupesh Kothari"— Presentation transcript:
1 BGP VPLS Auto Site ID Bhupesh Kothari (firstname.lastname@example.org) Kireeti KompellaThomas Spencer
2 VPLS Site ID Requirements Site IDs configured on each VPLS PE must be unique per VPLS domain.Exception is multi-homing.Site IDs must be dense per VPLS domain.Good allocation: 10,11,12,13,50,51,52,53
3 VPLS Auto Site ID Goals Eliminate the need to provision site IDs Distributed approach with no central device (like PE, RR) allocating site IDs for better scaling and fault tolerance propertiesNo extra state on PEs beyond what already exist todayBackwards compatibility with current explicit site ID allocation approachProcedures should work when VPLS domain span multiple AS
4 VPLS Auto Site ID Approach Each PE keeps track of site IDs already in use and claims an unused ID when it needs oneIf two PEs claim the same site ID, then they run a collision resolution algorithm to resolve the collision in favor of one of the claimantsAlgorithm guarantees convergence: all sites will ultimately pick unique site IDsSimple optimizations make the chance of a collision extremely small in real lifeExplicitly configured site IDs always win over dynamically generated ones
5 Auto Site ID Negotiation 12ClaimWait to receive NLRIsSend a claim adv.Wait for collisionNo collision=>send areal adv.Withdraw claim adv.RealClaim384Real581518EDAC18618VE IDB218OffsetRangeBGP VPLS NLRI
6 VPLS Auto Site Restrictions Site IDs need to be explicitly configured with multi-homingPEs cannot tell that they are connected to the same site and coordinate site ID allocation
7 VPLS Auto Site ID Details are in: Questions? draft-kothari-l2vpn-auto-site-id-00.txtQuestions?