VPLS.US

I could see a couple different ways of addressing this issue:

1. Through the use of NNIs. Which by the way is something I’m seeing as missing from the Ethernet VPN draft. The ability to cross different AS realms. Having a link between two PEs become the path between a BGP signaled Ethernet VPN and a LDP Signaled VPLS domain.

2. Through the use of something like Juniper’s option E… Having a PE that can speak both Ethernet VPN and LDP VPLS and having it keep two LARGE forwarding tables that allows it to do the forwarding between the different domains.

3. What else???