Requested revision
Standard: | 802.1Q-2011 | Clause: | 11.2.5 |
Clause title: | Use of "new" declaration capability |
Rationale for revision
11.2.5 describes MVRP’s use of new, says that when new is received:
"any entries in the filtering database for that Port and for the VID
corresponding to the attribute value in the MAD_Join primitive are removed.”
What is removed?
According to 8.8 The Filtering Database, the following entry types may
contain information about the relevant port and VID:
Dynamic Filtering Entry
(Contains: A MAC address, FID, and Port Map for “each outbound Port”)
Dynamic VLAN Registration Entry
(Contains: A VID, and a Port Map for “each outbound Port”)
MAC Address Registration Entry
(Contains: A MAC address, VID, and Port Map for “each outbound Port”)
Dynamic Reservation Entry
(Contains: A VID, a MAC address specification, and a Port Map for “each
outbound Port”)
Static Filtering Entry
(Contains: A MAC address, VID, and Port Map for “each outbound Port”)
Static VLAN Registration Entry
(Contains: A VID, and a Port Map for “each outbound Port”)
===============
Every type of entry contains information about some VID (or FID, in the
case
of Dynamic Filtering Entries), and every port.
One (bad) interpretation of 11.2.5 (which is consistent with 11.2.5)
would be, upon
receiving a “new” event, to remove all of the listed entries which match
the
VID which the “new” event was for.
This is highly undesirable; in fact, this interpretation puts 11.2.5 in
direct
conflict with 8.8, because Static Filtering Entries and Static VLAN
Registration Entries may only be removed by management
The only reasonable thing to discard are Dynamic Filtering Entries.
Beyond the type of entry, “removing an entry” (because they contain a port
map), effectively unregisters all ports
In the case of Dynamic Filtering Entries (8.8.3), this will only deregister
it from one port
11.2.5 should more clearly state what information will be removed when a
new
indication is received.
Proposed text
Clarify that only the "Dynamic Filtering Entry" is affected.
Change the last paragraph of 11.2.5 from:
"
When any MVRP declaration marked as “new” is received on a given Port,
either
as a result of receiving an MVRPDU from the attached LAN
(MAD_Join.indication),
or as a result of receiving a request from MAP or the MVRP Application
(MAD_Join.request), any entries in the filtering database for that Port
and for
the VID corresponding to the attribute value in the MAD_Join primitive are
removed.
"
To:
"
When any MVRP declaration marked as “new” is received on a given Port,
either
as a result of receiving an MVRPDU from the attached LAN
(MAD_Join.indication),
or as a result of receiving a request from MAP or the MVRP Application
(MAD_Join.request), any Dynamic Filtering Entries in the filtering database
for that Port and for the VID corresponding to the attribute value in the
MAD_Join primitive are removed.
"
Impact on existing networks
None, clarifying. Alternate behavior would be bad.
Originator
Name: | Aaron Stewart, Bob Noseworthy | Email: | astewart@iol.unh.edu; ren@iol.unh.edu |
Affiliation: | University of New Hamsphire's InterOperability Lab | ||
Submitted: | 2012-08-23 |