3.2.5.5.5 IN_R1/A2 RTS PDU

A server implementation MUST NOT accept the IN_R1/A2 RTS PDU in any state other than Open_Start. If this condition is not met, the server MUST treat this PDU as a protocol error as specified in section 3.2.5.5.13.

If this RTS PDU is received in Open_Start state, an implementation of this protocol MUST perform the following actions in the sequence given:

  1. Retrieve the virtual connection cookie from this RTS PDU and find it in the virtual connection cookie table. If the connection is not found, an implementation of this protocol MUST treat this as a protocol error, MUST handle this as specified in section 3.2.5.5.13, and MUST skip the rest of the processing in this section. If found, an implementation of this protocol MUST execute steps two through six.

  2. Once the virtual connection is found, the IN channel on which this RTS PDU arrived MUST be attached as a component to the virtual IN channel for the virtual connection, and it MUST also be set as nondefault and successor IN channel. The existing IN channel is considered the predecessor channel.

  3. Verify that the PredecessorChannelCookie from this RTS PDU matches the IN channel cookie on the predecessor IN channel. If they do not match, an implementation of this protocol MUST treat this as a protocol error, MUST handle this as specified in section 3.2.5.5.13, and MUST skip the rest of the processing in this section. If they match, an implementation of this protocol MUST execute steps four through six.

  4. Set up the connection setup timer defined in section 3.2.5.2.1.

  5. Send IN_R1/A3 RTS PDU on the default OUT channel to the outbound proxy.

    Incoming IN_R1/A2 RTS PDU elements MUST be copied to the IN_R1/A3 RTS PDU and MUST be copied to the virtual connection ReceiveWindowSize (3.2.1.1.5.1.1) and ConnectionTimeout (3.2.1.1.6.1) ADM elements.

  6. Set the value of ProtocolVersion in the IN_R1/A3 RTS PDU to the value of ProtocolVersion from the server Virtual Connection.

  7. Transition to the A6W state.

Show: