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

DATE: July 6, 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.7
     CLAUSE TITLE: Applicant State Machine


RATIONALE FOR REVISION:

Note 11 of Table 10-3 (Applicant SM) states: 
In implementations where dynamic creation and discarding of state machines is 
desirable, the state machine can be discarded when in any of these states, 
pending a future requirement to declare or register that attribute value

A similar NOTE in 10.7.8 (Registrar SM) states: 
As with the Applicant, state information is conceptually maintained for all 
possible values of all Attribute types that are defined for a given 
application; however, in real implementations of MRP, it is likely 
that the range of possible Attribute values in some applications will 
preclude this, and the implementation will limit the state to those 
Attribute values in which the Participant has an immediate interest.


The behavior in the LO state of the Applicant state machine when tx! 
occurs requires s followed by a transition to the VO state.  By 
requiring s, the Applicant SM requires all attribute values to be sent 
in response to (for example) an rLA! while in the VO state.

This is clearly not desirable, but it is unclear when to consider the 
Applicant and Registrar state machines as discarded.


PROPOSED REVISION TEXT:

Insert a new note 9 before MRP design notes to Table 10-3 
(applied to the intersections of STATE columns VO, AO, QO & 
EVENTS rLv! || rLA! || Re-declare!): 

This state transition is ignored if responding to rLA! and the Registrar 
state machine associated with this attribute value is MT.  


Insert a new note 10 before MRP design notes to Table 10-3 
(applied to the intersections of STATE columns VO, AO, QO and 
EVENTS txLA! and txLAF!): 

This state transition is ignored if the Registrar state machine associated 
with this attribute value is MT.


IMPACT ON EXISTING NETWORKS:

None.  The change makes clear that MT need not be sent for all possible 
attribute values.

+---------------------------------------------------------------------+
| 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                                |             |
|            +------------------------------------------+             |
+---------------------------------------------------------------------+