The translation has come to an end.
Exit Zen
78
../../protocols/tcp.rst:249
English
`sequence number`. TCP uses a 32 bits sequence number. The `sequence number` placed in the header of a TCP segment containing data is the sequence number of the first byte of the payload of the TCP segment.
0/2060 · 206
79
../../protocols/tcp.rst:250
English
`acknowledgment number`. TCP uses cumulative positive acknowledgments. Each TCP segment contains the `sequence number` of the next byte that the sender of the acknowledgment expects to receive from the remote host. In theory, the `acknowledgment number` is only valid if the `ACK` flag of the TCP header is set. In practice, almost all [#fackflag]_ TCP segments have their `ACK` flag set.
0/3880 · 388
80
../../protocols/tcp.rst:251
English
`window`. a TCP receiver uses this 16 bits field to indicate the current size of its receive window expressed in bytes.
0/1190 · 119
81
../../protocols/tcp.rst:255
English
The Transmission Control Block
0/300 · 30
82
../../protocols/tcp.rst:257
English
For each established TCP connection, a TCP implementation must maintain a Transmission Control Block (:term:`TCB`). A TCB contains all the information required to send and receive segments on this connection :rfc:`793`. This includes [#ftcpurgent]_ :
0/2500 · 250
83
../../protocols/tcp.rst:259
English
the local IP address
0/200 · 20
84
../../protocols/tcp.rst:260
English
the remote IP address
0/210 · 21
85
../../protocols/tcp.rst:261
English
the local TCP port number
0/250 · 25
86
../../protocols/tcp.rst:262
English
the remote TCP port number
0/260 · 26
87
../../protocols/tcp.rst:263
English
the current state of the TCP FSM
0/320 · 32
88
../../protocols/tcp.rst:264
English
the `maximum segment size` (MSS)
0/320 · 32
89
../../protocols/tcp.rst:265
English
`snd.nxt` : the sequence number of the next byte in the byte stream (the first byte of a new data segment that you send uses this sequence number)
0/1460 · 146
90
../../protocols/tcp.rst:266
English
`snd.una` : the earliest sequence number that has been sent but has not yet been acknowledged
0/930 · 93
91
../../protocols/tcp.rst:267
English
`snd.wnd` : the current size of the sending window (in bytes)
0/610 · 61
92
../../protocols/tcp.rst:268
English
`rcv.nxt` : the sequence number of the next byte that is expected to be received from the remote host
0/1010 · 101
93
../../protocols/tcp.rst:269
English
`rcv.wnd` : the current size of the receive window advertised by the remote host
0/800 · 80
94
../../protocols/tcp.rst:270
English
`sending buffer` : a buffer used to store all unacknowledged data
0/650 · 65
95
../../protocols/tcp.rst:271
English
`receiving buffer` : a buffer to store all data received from the remote host that has not yet been delivered to the user. Data may be stored in the `receiving buffer` because either it was not received in sequence or because the user is too slow to process it
0/2600 · 260
96
../../protocols/tcp.rst:274
English
The original TCP specification can be summarized as a transport protocol that provides a byte stream service and uses `go-back-n` with a `selective-repeat` reception strategy.
0/1750 · 175
97
../../protocols/tcp.rst:276
English
To send new data on an established connection, a TCP entity performs the following operations on the corresponding TCB. It first checks that the `sending buffer` does not contain more data than the receive window advertised by the remote host (`rcv.wnd`). If the window is not full, up to `MSS` bytes of data are placed in the payload of a TCP segment. The `sequence number` of this segment is the sequence number of the first byte of the payload. It is set to the first available sequence number : `snd.nxt` and `snd.nxt` is incremented by the length of the payload of the TCP segment. The `acknowledgment number` of this segment is set to the current value of `rcv.nxt` and the `window` field of the TCP segment is computed based on the current occupancy of the `receiving buffer`. The data is kept in the `sending buffer` in case it needs to be retransmitted later.
0/8680 · 868