1 / 7

L2VPN Signaling Draft And VPLS Autodiscovery issue.

L2VPN Signaling Draft And VPLS Autodiscovery issue. L2 Signaling RD issue. Current document proposes to use RD:Ip_addr construct in NLRI RD is then put into AGI field of PW LDP signaling FEC 129 requires AGI to match in both directions of a PW to bring up the PW.

yaakov
Download Presentation

L2VPN Signaling Draft And VPLS Autodiscovery issue.

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. L2VPN Signaling DraftAndVPLS Autodiscovery issue.

  2. L2 Signaling RD issue • Current document proposes to use RD:Ip_addr construct in NLRI • RD is then put into AGI field of PW LDP signaling • FEC 129 requires AGI to match in both directions of a PW to bring up the PW. • We want to remain backward compatible with draft-ietf-l2vpn-vpls-bgp-06

  3. Protocol issue: • RD is just a route distinguisher, Not an Identifier. • L2 vpn VFI requires an identifier.

  4. Possible solutions • Keep RD and make it match. • Use RT instead in AGI. • Use BGP Opaque Extended Community - per [RFC4360] to transport the VPLS-ID.

  5. VPLS-ID • Use BGP community to signal VPLS-ID == AGI • Allows the current RD/RT definition to be exactly as L3VPN. • Can be a true VSI identifier to signal in AGI. • AGI type 1 definition does not match. • However I will make change the allocation to be “AGI encoded as Route Distinguisher”.

  6. Opaque Extended Community • FCFS allocation • 6 bytes long • Will request 0x0300,0x0301,0x0302 to match respective RD encoding. • Change to RFC4446 ( yet to be published) OLD: AGI Type Length Description Reference =================================================================== 0x01 8 Route distinguisher (RD) [SIG] NEW: AGI Type Length Description Reference =================================================================== 0x01 8 AGI encoded as Route Distinguisher [SIG]

  7. The END ! • Questions ?

More Related