Share via

3.2.3.5.5.2 Virtual Connection Cookie Not Found

  • Article

If the virtual connection cookie is not found in the virtual connection cookie table, an implementation of this protocol MUST execute these steps:

  1. The inbound proxy MUST conform to IN_R1 protocol sequence.

  2. Establish a TCP connection to the server using the server name and port from the IN channel request, as specified in section 2.2.2.

  3. Add the virtual connection cookie to the virtual connection cookie table.

  4. Send IN_R1/A2 RTS PDU, as specified in section 2.2.4.11, to the server.

    The IN_R1/A2 RTS PDU InboundProxyReceiveWindowSize and InboundProxyConnectionTimeout fields come from the IN channel protocol variables ReceiveWindowSize (section 3.2.1.1.5.1.1) and ConnectionTimeout (section 3.2.1.1.6.1), respectively.

  5. Set the value of ProtocolVersion in the IN_R1/A2 RTS PDU to the value of ProtocolVersion from the inbound proxy Virtual Connection.

  6. Set the value of NonDefaultInChannelCookie in the inbound proxy Virtual Connection to the value of PredecessorChannelCookie from the IN_R1/A1 PDU.

  7. Set the value of DefaultInChannelCookie in the inbound proxy Virtual Connection to the value of SuccessorChannelCookie from the IN_R1/A1 PDU.

  8. Switch the successor IN channel to plugged channel mode.

  9. Transition to state Wait_B2.