1 | initial version |
If the first packet has expected SEQ (in-order), a client will: - accept the first packet, advance slidin window and generate an ACK containing next expected SEQ; - discard the second packet and in response once more generate an ACK containing next expected SEQ (same as before).
The same behavior will continue until a client gets a packet with expected SEQ.
2 | No.2 Revision |
If the first packet has expected SEQ (in-order), a client will:
- will:
The same behavior will continue until a client gets a packet with expected SEQ.
3 | No.3 Revision |
If the first packet has expected SEQ (in-order), a client will:
The same behavior will continue until a client gets a packet with expected SEQ.
4 | No.4 Revision |
If the first packet has expected SEQ (in-order), a client will:
The same behavior will continue until a client gets a packet with expected SEQ.
5 | No.5 Revision |
If the first packet has expected SEQ (in-order), a client will:
The same behavior will continue until a client gets a packet with expected SEQ.
6 | No.6 Revision |
If I assume you're speaking about TC, so if the first packet has expected SEQ (in-order), a client will:
The same behavior will continue until a client gets a packet with expected SEQ.
7 | No.7 Revision |
I assume you're speaking about TC, TCP, so if the first packet has expected SEQ (in-order), a client will:
The same behavior will continue until a client gets a packet with expected SEQ.