Share via

3.2.4.5.10 OUT_R2/B1 RTS PDU

  • Article

An outbound proxy implementation MUST NOT accept the OUT_R2/B1 RTS PDU in any state other than B1W or B1OrC1W. If this condition is not met, the outbound proxy MUST treat this PDU as a protocol error as specified in section 3.2.4.5.14.

If this RTS PDU is received in B1W state, the outbound proxy implementation MUST perform the following actions in the sequence given:

  1. Send all RPC PDUs that might be queued due to flow control to the client on the default OUT channel, observing flow control rules as specified in section 3.2.1.4.1.3.

  2. Send OUT_R2/B3 RTS PDU to the client on the default OUT channel. Implementations SHOULD NOT send any additional bytes on the channel after the OUT_R2/B3 RTS PDU.<48>

  3. Switch the default OUT channel to the successor OUT channel instance.

  4. Switch the default OUT channel to unplugged channel mode.

  5. Send OUT channel response header as specified in section 2.1.2.1.4 on the successor OUT channel instance.

  6. Transition the state to opened.

  7. Close the predecessor OUT channel to the client.

If this RTS PDU is received in the B1OrC1W state, the outbound proxy implementation MUST perform the following actions in the sequence given:

  1. Send all RPC PDUs that might be queued due to flow control to the client on the default OUT channel, observing flow control rules as specified in section 3.2.1.4.1.3

  2. Send OUT_R2/B3 RTS PDU to the client on the default OUT channel. Implementations SHOULD NOT send any additional bytes on the channel after the OUT_R2/B3 RTS PDU.<49>

  3. Switch the default OUT channel to the successor OUT channel instance.

  4. Switch the default OUT channel to unplugged channel mode.

  5. Transition the state to R2C1W state and wait for further network events.

  6. Close the predecessor OUT channel to the client.