Re: VPLS model for L2VPN Framework document

Matt> So this  is where I  may (or may  not) offer a different  opinion from
Matt> Norm and/or Ali. 

Well, trying  to figure out  when the bridge  experts are agreeing  and when
they are disagreeing is one of the challenges we face ;-) 

Matt> Using a separate  VPLS instance for discovery and  setup (as discussed
Matt> below) creates a likely opportunity of the 'discovery' VPLS being in a
Matt> different  state than  the 'data'  VPLS, which  of course  would screw
Matt> everything up. 

I think the  vision here is that a service  provider's network might consist
of several Q-in-Q islands, where  some VPLS instances are intra-island, some
are inter-island,  and some are  inter-provider.  However, an  MSTP instance
would always  be intra-island, by definition.   I'm not sure  how your model
handles this. 

However, I  don't think  anything in my  proposed writeup prevents  you from
setting  up a  single VPLS  instance which  contains multiple  VLANs, though
there is the question of how the encapsulation would distinguish the VLANs.