3.2.2.5.4 CONN/C2 RTS PDU

  • Article

A client implementation MUST NOT accept the CONN/C2 RTS PDU in any state other than Wait_C2. If received in any other state, this PDU is a protocol error and the client MUST consider the virtual connection opening a failure and indicate this to higher layers in an implementation-specific way.

If this RTS PDU is received in Wait_C2 state, the client implementation MUST do the following:

  1. Transition the state machine to opened state.

  2. Set the connection time-out protocol variable to the value of the ConnectionTimeout field from the CONN/C2 RTS PDU.

  3. Set the PeerReceiveWindow value in the SendingChannel of the Client IN Channel to the ReceiveWindowSize value in the CONN/C2 PDU.

  4. Indicate to higher-layer protocols that the virtual connection opening is a success.

From this moment on, the client implementation MUST conform to the virtual IN channel and virtual OUT channel state machines separately as specified in the beginning of section 3.2.2. Both of these state machines start in opened state.