VPLS Using IS-IS: Draft-Xu-L2vpn-Vpls-Isis-00
VPLS Using IS-IS: Draft-Xu-L2vpn-Vpls-Isis-00
draft-xu-l2vpn-vpls-isis-00
Page 2
Page 3
Auto-Discovery and Signaling in IS-IS VPLS
l Auto-Discovery
p Each PE router could automatically discover which other PE routers
are part of a given VPLS instance identified by the globally unique
VPLS ID.
p PE router's configuration consists only of the identities of the VPLS
instances established on this PE router, not the identities of any other
PE routers belonging to that VPLS instance.
l Signaling
p PE router assigns the same MPLS label for a given VPLS instance to
any other PE routers.
p The VPLS label doesn’t need to be globally unique.
Page 4
l The extended IS-IS TLV for VPLS is partially transparent to P
routers.
p P routers don't need to process the VPLS membership information
contained in that IS-IS TLV, but only need to synchronize the Link
State PDUs with their IS-IS neighbors.
Page 5
l Data encapsulation and data forwarding are not changed.
l The only change is to the data-driven MAC learning:
p The VPLS label in the received VPLS packet is only intended to
identify a given VPLS instance on the egress PE.
p Hence, the source IP address in the IP-based tunnel header should
be resorted to identify the ingress PE of the received VPLS packet.
Page 6
Next Steps
l Solicit more comments from the WG.
l Ask for WG adoption.
Page 7