queue
Click on the red underlined text to get to the source
... segment is deleted from the queue. If the acknowledgment is not
received before the timer runs out, the segment ...
... connection, pointers to the user's send and receive
buffers, pointers to the retransmit queue and to the current segment.
In addition several variables relating to the send and receive
...
... A segment on the retransmission queue is fully acknowledged if the sum
of its sequence number and length is less or equal than the
...
... segment is formed and
entered into the network output queue at a source host. The
duplicate detection and sequencing algorithm ...
... segment can be constructed and placed on the
outgoing segment queue. No further SENDs from the user will be
accepted by the TCP, and it enters the FIN-WAIT-1 state ...
... Multiple SENDs are served in first come, first served order, so
the TCP will queue those it cannot service immediately.
...
... segments sent as a result of this command. If there is no room to
queue the request, respond with "error: insufficient resources".
If Foreign socket was not specified, then return "error: foreign
...
... requested in the command must be sent with the data segments sent
as a result of this command. If there is no room to queue the
request, respond with "error: insufficient resources". If
Foreign socket ...
... STATE
Queue the data for transmission after entering ESTABLISHED state.
If no space to queue ...
... Queue the data for transmission after entering ESTABLISHED state.
If no space to queue, respond with "error: insufficient
resources".
...
... Queue for processing after entering ESTABLISHED state. If there
is no room to queue this request, respond with "error:
insufficient resources".
...
... If insufficient incoming segments are queued to satisfy the
request, queue the request. If there is no queue space to
remember the RECEIVE, respond with "error: insufficient
...
... segments are queued to satisfy the
request, queue the request. If there is no queue space to
remember the RECEIVE, respond with "error: insufficient
resources".
...
... segment and send it, and enter FIN-WAIT-1 state;
otherwise queue for processing after entering ESTABLISHED state.
...
... STATE
Queue this until all preceding SENDs have been segmentized, then
form a FIN segment and send it. In any case, enter FIN-WAIT-1
...
... STATE
Queue this request until all preceding SENDs have been
segmentized; then send a FIN segment, enter CLOSING state ...
... ACK), and any segments on the retransmission queue which
are thereby acknowledged should be removed.
...
... and send it. If there are other controls or text in the
segment, queue them for processing after the ESTABLISHED state
has been reached, return.
...
... SEND
should receive "reset" responses. All segment queues should be
flushed. Users should also receive an unsolicited general
"connection ...
... SEND should
receive "reset" responses. All segment queues should be
flushed. Users should also receive an unsolicited general
"connection ...
... SEND should receive "reset" responses,
all segment queues should be flushed, the user should also
receive an unsolicited general "connection reset" signal, enter
...
... Any segments on the retransmission queue which are thereby
entirely acknowledged are removed. Users should receive
...
... state, if
the retransmission queue is empty, the user's CLOSE can be
acknowledged ("ok") but do not delete the TCB ...
...
For any state if the user timeout expires, flush all queues, signal
the user "error: connection aborted due to user timeout" in general
...
... segment at the front of the
retransmission queue again, reinitialize the retransmission timer,
and return.
...