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’.