Revision Summary Date Revision History Revision Class Comments 4/8/2008 0.1 New Version 0.1 release 6/20/2008 0.1.1 Editorial Changed language and formatting in the technical content. 7/25/2008 0.1.2 Editorial Changed language and formatting in the technical content. 8/29/2008 0.1.3 Editorial Changed language and formatting in the technical content. 10/24/2008 0.1.4 Editorial Changed language and formatting in the technical content. 12/5/2008 0.1.5 Editorial Changed language and formatting in the technical content. 1/16/2009 0.1.6 Editorial Changed language and formatting in the technical content. 2/27/2009 0.1.7 Editorial Changed language and formatting in the technical content.
4/10/2009 0.1.8 Editorial Changed language and formatting in the technical content. 5/22/2009 0.1.9 Editorial Changed language and formatting in the technical content. 7/2/2009 0.1.10 Editorial Changed language and formatting in the technical content. 8/14/2009 0.1.11 Editorial Changed language and formatting in the technical content. 9/25/2009 0.2 Minor Clarified the meaning of the technical content. 11/6/2009 0.2.1 Editorial Changed language and formatting in the technical content. 12/18/2009 1.0 Updated and revised the technical content. 1/29/2010 1.0.1 Editorial Changed language and formatting in the technical content. 3/12/2010 2.0 Major Updated and revised
the technical content. 4/23/2010 2.0.1 Editorial Changed language and formatting in the technical content. 6/4/2010 2.0.2 Editorial Changed language and formatting in the technical content. 7/16/2010 3.0 Major Updated and revised the technical content. 8/27/2010 4.0 Major Updated and revised the technical content. 10/8/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 4.0 None No changes to the meaning, language, or formatting of the technical content.
2/11/2011 4.0 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 4.0 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 4.1 Minor Clarified the meaning of the technical content. 9/23/2011 4.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 5.0 Major Updated and revised the technical content. 3/30/2012 5.0 None No changes to the meaning, language, or formatting of the technical content.
7/12/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 5.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 5.1 Minor Clarified the meaning of the technical content. 8/8/2013 5.1 None No changes to the meaning, language, or formatting of the technical content. 11/14/2013 5.1 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 6.0 Updated and revised the technical content. 5/15/2014 7.0 Major Updated and revised the technical content. 6/30/2015 8.0 Major Significantly changed the
technical content. 10/16/2015 8.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 8.0 None No changes to the meaning, language, or formatting of the technical content. 3/16/2017 9.0 Major Significantly changed the technical content.
Signal the FAULT event. Remove the Request Holder from the Request List. For each Sequence Number acknowledged in the Acknowledgement elements in the SequenceAcknowledgement header block in the Header element of Response: Look up the Sequence Number in the Response Sequence Number List. If the lookup is not successful: Add the Sequence Number to the Response Sequence Number List. If the Request List is and the value of the State field is CLOSING_SEQUENCES_PENDING: Signal the SEQUENCES_COMPLETE Otherwise: Signal the FAULT event. Otherwise, if the value of the State field is CLOSING_SEQUENCES_COMPLETE: If Response is a : Set the value of the State field to TERMINATING. Create a new . Set the of the Identifier element in the TerminateSequence element in the body of the TerminateSequence message to the value of the Outbound Sequence Identifier field. Signal the PREPARE_ACKNOWELDGEMENT event passing the TerminateSequence message. Send the TerminateSequence message on the underlying protocol. Otherwise: Signal the FAULT event. Otherwise, if the value of the State field is TERMINATING: Set the value of the State field to CLOSED. Otherwise: Do nothing. Timer Events No timer events are defined for the role. Other Local Events FAULT Event If the FAULT event is signaled, the role MUST perform the following actions:
Index A Abstract data model 23 15 10 13 13 C 10 44 12 12 11 12 D Data model - abstract 23 15 Destination role 23 26 26 30 27 27 30 26 E 13 F 10 G 6 H Higher-layer triggered events 26 19 I 42 42 8 Initialization 26 19 6 L Local events 30 22 M Message processing 27 20 Messages 13 13 12 12 11 12 13 14 11 11 11 13 13 11 N 7 14 O 8 P 42 10 10 43 Protocol Details 15 R 7 8 7 9 11 11 S Security 42 42 Sequencing rules 27