Donour Sizemore wrote: > On Feb 2, 2010, at 5:23 PM, James Carlson wrote: > >> On Feb 2, 2010, at 6:00 PM, Nicolas Droux <Nicolas.Droux at sun.com> wrote: >> >>> Yes there is the performance issue, but I'm more concerned that enabling >>> the feature by default would cause these GVRP messages to start propagating >>> on the networks of our customers who have configured VLANs. >>> >>> It's fine to use these messages in an environment which is expecting them >>> to perform VLAN configuration, such as a cloud-like infrastructure. However >>> GVRP messages might not be welcome in other environments where all VLAN >>> configuration is done from the switch side, and no such messages are >>> expected to be seen on the network. >> They don't propagate. They're in a multicast range that, like STP, isn't >> forwarded by bridges. Either the bridge uses them, or doesn't. >> > > Doesn't 802.1Q::11.2.3.1.1 dictate that they should? > > "b) In Bridges that do not support the operation of GVRP, all such PDUs > shall be submitted to the Forwarding Process."
Good point. I was assuming we were concerned about bridges that support GVRP but that have it disabled. They could end up being forwarded like that. In any event, it wasn't a request for a change of any sort, but rather probing for information. When basic informational things like this are disabled by default, it usually ends up with serious deployment problems ... except, of course, in walled gardens. -- James Carlson 42.703N 71.076W <carlsonj at workingcode.com>
