2.2.4.5 CONN/B1 RTS PDU

The CONN/B1 RTS PDU MUST be sent from the client to the inbound proxy on the IN channel to initiate the establishment of a virtual connection.

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)
...
...
Version
...
VirtualConnectionCookie (20 bytes)
...
...
INChannelCookie (20 bytes)
...
...
ChannelLifetime
...
ClientKeepalive
...
AssociationGroupId (20 bytes)
...
...

RTS Header (20 bytes): See section 2.2.3.6.1. 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 6.

Version (8 bytes): MUST be a Version command containing the version of RPC over HTTP v2 that the client supports, formatted as specified in section 2.2.3.5.7.

VirtualConnectionCookie (20 bytes): MUST be a Cookie command identifying the virtual connection that this protocol sequence is trying to establish. The Cookie command format is defined in section 2.2.3.5.4.

INChannelCookie (20 bytes): MUST be a Cookie command identifying the IN channel cookie that this protocol sequence is trying to establish. The Cookie command format is defined in section 2.2.3.5.4.

ChannelLifetime (8 bytes): MUST be a ChannelLifetime command containing the lifetime in bytes of the IN channel from the client to the inbound proxy. The ChannelLifetime command format is defined in 2.2.3.5.5. This field is used for troubleshooting only and has no protocol significance. Inbound proxies SHOULD ignore the value of this field.

ClientKeepalive (8 bytes): MUST be a ClientKeepalive command containing the keep-alive interval that the client wants the inbound proxy to use on the IN channel between the inbound proxy and the server. The ClientKeepalive command format is defined in section 2.2.3.5.6.

AssociationGroupId (20 bytes): MUST be an AssociationGroupId command containing the association group ID for the client. The AssociationGroupId command format is defined in section 2.2.3.5.13.