Revision Summary Date Revision History Revision Class Comments 10/22/2006 0.01 New Version 0.01 release 1/19/2007 1.0 Major Version 1.0 release 3/2/2007 1.1 Minor Version 1.1 release 4/3/2007 1.2 Minor Version 1.2 release 5/11/2007 1.3 Minor Version 1.3 release 6/1/2007 1.3.1 Editorial Changed language and formatting in the technical content. 7/3/2007 1.3.2 Editorial Changed language and formatting in the technical content. 7/20/2007 1.3.3 Editorial Changed language and formatting in the technical content. 8/10/2007 1.3.4 Editorial Changed language and formatting in the technical content. 9/28/2007 1.3.5 Editorial Changed language and formatting in the technical content. 10/23/2007 1.3.6 Editorial Changed language and
formatting in the technical content. 11/30/2007 1.3.7 Editorial Changed language and formatting in the technical content. 1/25/2008 1.3.8 Editorial Changed language and formatting in the technical content. 3/14/2008 1.3.9 Editorial Changed language and formatting in the technical content. 5/16/2008 1.3.10 Editorial Changed language and formatting in the technical content. 6/20/2008 1.3.11 Editorial Changed language and formatting in the technical content. 7/25/2008 1.3.12 Editorial Changed language and formatting in the technical content. 8/29/2008 1.3.13 Editorial Changed language and formatting in the technical content.
10/24/2008 2.0 Major Updated and revised the technical content. 12/5/2008 3.0 Major Updated and revised the technical content. 1/16/2009 4.0 Major Updated and revised the technical content. 2/27/2009 5.0 Updated and revised the technical content. 4/10/2009 6.0 Major Updated and revised the technical content. 5/22/2009 6.0.1 Editorial Changed language and formatting in the technical content. 7/2/2009 6.0.2 Editorial Changed language and formatting in the technical content. 8/14/2009 6.1 Minor Clarified the meaning of the technical content. 9/25/2009 7.0 Major Updated and revised the technical content. 11/6/2009 8.0 Updated and revised the
technical content. 12/18/2009 8.1 Minor Clarified the meaning of the technical content. 1/29/2010 8.2 Minor Clarified the meaning of the technical content. 3/12/2010 8.2.1 Editorial Changed language and formatting in the technical content. 4/23/2010 8.2.2 Editorial Changed language and formatting in the technical content. 6/4/2010 8.2.3 Editorial Changed language and formatting in the technical content. 7/16/2010 8.2.3 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 8.2.3 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 9.0 Updated and revised the
technical content. 11/19/2010 10.0 Major Updated and revised the technical content. 1/7/2011 10.1 Minor Clarified the meaning of the technical content. 2/11/2011 11.0 Major Updated and revised the technical content. 3/25/2011 12.0 Major Updated and revised the technical content. 5/6/2011 12.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 12.1 Minor Clarified the meaning of the technical content. 9/23/2011 12.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 13.0 Major Updated and revised the technical content. 3/30/2012 13.0 None No changes to the meaning,
language, or formatting of the technical content. 6/30/2015 15.0 Major Significantly changed the technical content. 10/16/2015 15.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 15.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 15.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 16.0 Major Significantly changed the technical content. 12/1/2017 16.0 None No changes to the meaning, language, or formatting of the technical content.
ANCE (0x0000000A) The command indicates that a successor channel was established successfully. ClientAddress (0x0000000B) The command carries the client IP address. The IP address is encoded as specified in section . Regardless of who sends this PDU, the address MUST be interpreted to be the address of the client. AssociationGroupId (0x0000000C) The command carries the client association group ID as specified in section 2.2.3.5.13. Regardless of who sends this PDU, the association group ID MUST be interpreted to be that of the client. Destination (0x0000000D) The command carries the destination to a PDU MUST be forwarded. PingTrafficSentNotify (0x0000000E) The command carries the number of sent by the outbound proxy to the client as part of ping traffic. ReceiveWindowSize The ReceiveWindowSize command specifies the size of the ReceiveWindow of a party. The party from which the ReceiveWindow originated is specified in the section for the that contains this command. The structure of the command is as follows. 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 CommandType
... ... ANCE RTS Header (20 bytes): See section . The Flags field of the RTS Header MUST be the value RTS_FLAG_NONE. The NumberOfCommands field of the RTS Header MUST be the value 1. ANCE (4 bytes): MUST be an command. The format of the ANCE command is defined in section 2.2.3.5.11. OUT_R2/B2 RTS PDU The OUT_R2/B2 RTS PDU MUST be sent from the server to the outbound proxy to indicate to it that the successor was not established successfully. 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 RTS Header (20 bytes) ... ... NANCE RTS Header (20 bytes): See section . The Flags field of the RTS Header MUST be the value RTS_FLAG_NONE. The NumberOfCommands field of the RTS Header MUST be the value 1. NANCE (4 bytes): MUST be a command. The format of the NegativeANCE command is defined in section 2.2.3.5.10. OUT_R2/B3 RTS PDU The OUT_R2/B3 RTS PDU MUST be sent from the outbound proxy to the client to indicate to it that the successor was established successfully. 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 RTS Header (20 bytes) ... ... ANCE RTS Header (20 bytes): See section . The Flags field of the RTS Header MUST be the value RTS_FLAG_EOF. The NumberOfCommands field of the RTS Header MUST be the value 1.
Index A Abstract data RPC over HTTP v1 80 82 83 v2 client ( 85, 103) inbound proxy ( 85, 113) outbound ( 85, 121) server ( 85, 131) 39 21 39 C 21 149 37 Client 33 RPC over HTTP v1 80 80 80 81 81 79 81 81 80 v2 abstract data model ( 85, 103) higher-layer triggered events ( 91, 105) initialization ( 91, 104) local events ( 101, 112) message processing ( 92, 107) overview ( 85, 101) sequencing rules ( 92, 107) timer events ( 101, 112) timers ( 90, 104) to 25 22 25 37 39 31 31 32 44 45 46 47 48 49 50 51 36 31 37 D Data model - abstract RPC over HTTP v1 80 82 83 v2 client ( 85, 103) inbound proxy ( 85, 113) outbound ( 85, 121) server ( 85, 131) 32 40 16 43 E 77 38 Examples 142 141 141 16 F 34 34 34 34 21 34 142 36 77 34 78 34 G 11 H Higher-layer triggered events RPC over HTTP v1 80 82 84 v2 client ( 91, 105) inbound ( 91, 115)
65 66 67 67 68 69 69 71 71 72 72 73 74 74 75 75 Outbound proxy RPC over HTTP v2 abstract data ( 85, 121) higher-layer triggered events ( 91, 122) initialization ( 91, 122) local events ( 101, 129) message processing ( 92, 122) overview ( 85, 120) sequencing ( 92, 122) timer events ( 101, 129) timers ( 90, 122) 31 Overview 16 16 18 18 16 16 16 P 38 144 77 76 40 20 20 145 Protocol Details 79 Proxy to server 31 31 R 142 35 14 15 15 19 16 RPC over HTTP v1 client 80 80 80 81 81 79 81 81 80 mixed proxy 82 82 82 83 82 81 82 83 82 overview ( 79, 79) server 83 84 83 84 84 83 84 84 84 transport 22 24 22 v2 client abstract data model ( 85, 103) higher-layer triggered events ( 91, 105) initialization ( 91, 104) local events ( 101, 112) message processing ( 92, 107) overview ( 85, 101) sequencing rules ( 92, 107) timer events ( 101, 112) timers ( 90, 104) inbound abstract data model ( 85, 113) higher-layer triggered events ( 91, 115) initialization ( 91, 115) local events ( 101, 120) message processing ( 92, 115) overview ( 85, 112) sequencing ( 92, 115) events ( 101, 120) timers ( 90, 114) outbound proxy abstract data ( 85, 121) higher-layer triggered events ( 91, 122) initialization ( 91, 122) local events ( 101, 129) message processing ( 92, 122) overview ( 85, 120) sequencing rules ( 92, 122) timer events ( 101, 129) timers ( 90, 122)
overview ( 79, 84) server abstract data ( 85, 131) higher-layer triggered events ( 91, 132) initialization ( 91, 131) local events ( 101, 140) message processing ( 92, 133) overview ( 85, 129) sequencing rules ( 92, 133) timer events ( 101, 140) timers ( 90, 131) transport client to 25 25 31 31 24 RTS 35 41 PDUs 43 43 43 43 32 41 S Security 144 144 Sequencing RPC over HTTP v1 81 82 84 v2 client ( 92, 107) inbound proxy ( 92, 115) outbound proxy ( 92, 122) server ( 92, 133) Server RPC over HTTP v1 83 84 83 84 84 83 84 84 84 v2 abstract data model ( 85, 131) higher-layer triggered events ( 91, 92, 132, 133) initialization ( 91, 131) events ( 101, 140) overview ( 85, 129) timer events ( 101, 140) timers ( 90, 131) 21 Syntax 31 32 31 31 T Timer events RPC over HTTP v1 81 83 84 v2 client ( 101, 112) inbound proxy ( 101, 120) outbound proxy ( 101, 129) server ( 101, 140) Timers RPC over HTTP v1 80 82 84 v2 client ( 90, 104) inbound proxy ( 90, 114) outbound proxy ( 90, 122) server ( 90, 131) 149 22 Triggered events - RPC over HTTP v1 80 82 84 v2 client ( 91, 105) inbound proxy ( 91, 115) outbound proxy ( 91, 122) server ( 91, 132) U 31 31 V 21 38 21 141