+---------------------------------------------------------------------+
| IEEE 802.1 REVISION REQUEST XXXX                                    |
+------------------===================================----------------+

DATE: July 3, 2012
NAME: Aaron Stewart, Bob Noseworthy
COMPANY/AFFILIATION: University of New Hamsphire's InterOperability Lab with support from the AVnu Alliance
E-MAIL: astewart@iol.unh.edu; ren@iol.unh.edu


REQUESTED REVISION:
     STANDARD: 802.1Q-2011
     CLAUSE NUMBER: 10.7.5.2
     CLAUSE TITLE: Flush!


RATIONALE FOR REVISION:

The current behavior of the Registrar state table (Table 10-4) does not cause a "Lv" (10.7.6.14) to be sent when in the "IN" state and a Flush! event occurs.

This results in the permanent registration of the associated attribute, as the MRP application is never made aware of the Registrar's state change.


PROPOSED REVISION TEXT:

Regarding Table 10-4, state "IN", event "Flush!":
Replace "MT" 
with 
"
Lv
MT
"

IMPACT ON EXISTING NETWORKS:

The intention of the informatively named state names "IN" and "MT" is maintained when a "Lv" is signaled, as this will trigger a MAD_Leave.indication to the MRP application.

The intentions outlined in 10.3.1.1 will similarly be maintained by this change, specifically, quoting from the end of 10.3.1.1:

"""
For implementations running over RSTP or MSTP, this gives rise to the risk of information loops when Port
roles change; because of the store and forward nature of attribute propagation and the potentially rapid
transitions of Port roles (compared to the relatively slow transitions that occurred with STP), these can arise
even when there are no data loops.

To prevent such information loops from occurring, the information held by MADs Registrars for a Port (i.e.,
information registered on a Port as a result of protocol activity on the LAN to which that Port is connected)
is discarded whenever the Port transitions from an Alternate port or Root Port role to become a Designated
Port. No such discard is needed for changes in the other direction, i.e., changes from Designated Port to Root
Port or Alternate Port.
"""

+---------------------------------------------------------------------+
| Please attach supporting material, if any                           |
| Submit to:- Tony Jeffree, Chair IEEE 802.1                          |
|  and copy:- Paul Congdon, Vice-Chair IEEE 802.1                     |
|    E-Mail: stds-802-1-maint-req@ieee.org                            |
|                                                                     |
|            +------- For official 802.1 use -----------+             |
|            | REV REQ NUMBER:                          |             |
|            | DATE RECEIVED:                           |             |
|            | EDITORIAL/TECHNICAL                      |             |
|            | ACCEPTED/DENIED                          |             |
|            | BALLOT REQ'D YES/NO                      |             |
|            | Status: X                                |             |
|            +------------------------------------------+             |
+---------------------------------------------------------------------+