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
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 Updated and revised the technical content. 2/27/2009 5.0 Major 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 Clarified the meaning of the technical content. 9/25/2009 7.0 Major Updated and revised the technical content. 11/6/2009 8.0 Major 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 Major Updated and revised the
technical content. 11/19/2010 10.0 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 Updated and revised the technical content. 3/30/2012 13.0 None No changes to the meaning,
language, or formatting of the technical content. 7/12/2012 13.1 Minor Clarified the meaning of the technical content. 10/25/2012 13.1 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 13.1 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 14.0 Major Updated and revised the technical content. 11/14/2013 14.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 14.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 14.0 None No changes to the meaning,
OUT_R1/A1 RTS PDU The OUT_R1/A1 RTS PDU MUST be sent from the server to the outbound proxy on the OUT channel to initiate the establishment of a successor OUT channel. 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) ... ... Destination ... RTS Header (20 bytes): See section . The Flags field of the RTS Header MUST be the value RTS_FLAG_RECYCLE_CHANNEL. The NumberOfCommands field of the RTS Header MUST be the value 1. Destination (8 bytes): MUST be a command. The Destination field for the Destination command MUST be set to the value FDClient as specified in section . The Destination command format is defined in section 2.2.3.5.14. OUT_R1/A2 RTS PDU The OUT_R1/A2 RTS PDU MUST be sent from the outbound proxy to the client on the OUT channel to initiate the establishment of a successor OUT channel. 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) ... ... Destination ... RTS Header (20 bytes): See section . The Flags field of the RTS Header MUST be the value RTS_FLAG_RECYCLE_CHANNEL. The NumberOfCommands field of the RTS Header MUST be the value 1. Destination (8 MUST be a command. The Destination field for the Destination command MUST be set to the value FDClient as specified in section . The Destination command format is defined in section 2.2.3.5.14.
Index A Abstract data model 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 proxy ( 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 proxy ( 91, 115)
outbound ( 91, 122) server ( 91, 132) 18 18 I 144 52 53 54 56 56 57 57 58 59 59 60 60 Inbound proxy RPC over HTTP v2 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 rules ( 92, 115) timer events ( 101, 120) timers ( 90, 114) 31 144 16 Initialization RPC over HTTP v1 80 82 83 v2 client ( 91, 104) inbound proxy ( 91, 115) outbound proxy ( 91, 122) server ( 91, 131) 11 33 33 K 76 L Local events RPC over HTTP v1 81 83 84 v2 client ( 101, 112) inbound proxy ( 101, 120) outbound proxy ( 101, 129) server ( 101, 140) M Message processing RPC over HTTP v1 81 82 84 v2 client ( 92, 107) inbound proxy ( 92, 115) outbound proxy ( 92, 122) server ( 92, 133) Messages 31 32 22 43 31 22 22 RPC over HTTP v1 22 24 22 v2 client to 25 25 31 31 24 31 Mixed proxy RPC over HTTP v1 82 82 82 83 82 81 82 83 82 24 N 55 43 39 15 O 61 68 68 61 62 63 64
65 66 67 67 68 69 69 71 71 72 72 73 74 74 75 75 Outbound proxy RPC over HTTP v2 abstract data model ( 85, 121) higher-layer triggered events ( 91, 122) initialization ( 91, 122) 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 15 16 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 proxy 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 rules ( 92, 115) timer events ( 101, 120) timers ( 90, 114) outbound proxy abstract data model ( 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)