[rbridge] Core Rbridge instance PDU packet encapsulation

[Sanjay Sane (sanjays)]

Hi,
 
It seems PDUs of core Rbridge instance are supposed to go without VLAN
Tag, i.e. no .1Q tag. typically, when a classical bridge gets an
untagged packet (either on an access port or trunk port), it treats the
packet as if its coming on the default port-vlan. It will forward the
packet only within that vlan. 
 
Consider the the case where 2 Rbridges are connected through a classical
bridge. Lets say the 2 ports of this classical bridge, on which the 2
Rbridges are connected, are configured as trunk ports. Both these ports
also have a default port-vlan. 
Now, untagged packets coming from one Rbridge will reach the other
Rbridge *only* if the default port-vlans are the same. 
 
If the 2 Rbridges were connected through a network of classical bridges
(instead of a single classical bridge), are we relying on the assumption
that default port-vlans are the same. Why not use a VLAN tag (.1Q) for
the PDU packets of the core Rbridge instance as well ? 
 
Thanks.
Sanjay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.postel.org/pipermail/rbridge/attachments/20060711/a5e6babb/attachment.html