<font face="trebuchet ms,sans-serif"><span style="font-family: trebuchet ms,sans-serif;">Hi Bruce & all,</span><br style="font-family: trebuchet ms,sans-serif;">
<br style="font-family: trebuchet ms,sans-serif;">
<span style="font-family: trebuchet ms,sans-serif;">interface foo {</span><br style="font-family: trebuchet ms,sans-serif;">
<span style="font-family: trebuchet ms,sans-serif;">vif vlan 10.200 {</span><br style="font-family: trebuchet ms,sans-serif;">
<span style="font-family: trebuchet ms,sans-serif;">}</span><br style="font-family: trebuchet ms,sans-serif;">
<span style="font-family: trebuchet ms,sans-serif;">}</span><br style="font-family: trebuchet ms,sans-serif;">
<br style="font-family: trebuchet ms,sans-serif;">
<span style="font-family: trebuchet ms,sans-serif;">Is the above syntax makes clear view for QinQ support ?.</span><br style="font-family: trebuchet ms,sans-serif;">
<br style="font-family: trebuchet ms,sans-serif;">
<span style="font-family: trebuchet ms,sans-serif;">Thanks,</span><br style="font-family: trebuchet ms,sans-serif;">
<span style="font-family: trebuchet ms,sans-serif;">Regards,</span><br style="font-family: trebuchet ms,sans-serif;">
<span style="font-family: trebuchet ms,sans-serif;">Suresh kannan.</span></font><br><br><div class="gmail_quote">On Tue, Mar 25, 2008 at 2:00 AM, Bruce M Simpson <<a href="mailto:bms@incunabulum.net">bms@incunabulum.net</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">Pavlin Radoslavov wrote:<br>
> I have to admit that when comes to VLANs I am thinking the IEEE<br>
> 802.1Q Standard.<br>
> How the relationships you describe above fit with 802.1Q?<br>
> If you have an URL with detailed description that would be useful.<br>
><br>
<br>
</div>There are folk out there using multiple 802.1Q encapsulation headers,<br>
particularly for stuff like Metro Ethernet. It is sometimes called "Q-in-Q".<br>
<br>
The encapsulation thing was a requirement crunch when rethinking the<br>
FreeBSD ether_input() path this time last year -- and all I wanted to do<br>
was make 802.1p work with my VoIP ATA...<br>
<br>
I didn't see any reason to support more than 2 levels of encapsulation<br>
on the same link layer, however it's entirely possible people are doing<br>
more than 2.<br>
<br>
Having said that, I'd like to see how Q-in-Q is configured on vendor<br>
equipment before making any radical changes anywhere. For XORP,<br>
personally I prefer the interface foo0 { vif vlan10 { ... } } style<br>
syntax, but how to capture Q-in-Q in that syntax is an open question.<br>
<br>
cheers<br>
<font color="#888888">BMS<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Xorp-hackers mailing list<br>
<a href="mailto:Xorp-hackers@icir.org">Xorp-hackers@icir.org</a><br>
<a href="http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers" target="_blank">http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers</a><br>
</div></div></blockquote></div><br>