cnp3-ebook/protocols/tcp — English @ Weblate

Exit Zen

1 ../../protocols/tcp.rst:9
	English The Transmission Control Protocol
	English The Transmission Control Protocol The Transmission Control Protocol 33/10000 · 33 Needs editing
2 ../../protocols/tcp.rst:12
	English The Transmission Control Protocol (TCP) was initially defined in :rfc:`793`. Several parts of the protocol have been improved since the publication of the original protocol specification [#ftcpspecs]_. However, the basics of the protocol remain and an implementation that only supports :rfc:`793` should inter-operate with today's implementation.
	English The Transmission Control Protocol (TCP) was initially defined in :rfc:`793`. Several parts of the protocol have been improved since the publication of the original protocol specification [#ftcpspecs]_. However, the basics of the protocol remain and an implementation that only supports :rfc:`793` should inter-operate with today's implementation. The Transmission Control Protocol (TCP) was initially defined in :rfc:`793`. Several parts of the protocol have been improved since the publication of the original protocol specification [#ftcpspecs]_. However, the basics of the protocol remain and an implementation that only supports :rfc:`793` should inter-operate with today's implementation. 346/10000 · 346 Needs editing
3 ../../protocols/tcp.rst:14
	English TCP provides a reliable bytestream, connection-oriented transport service on top of the unreliable connectionless network service provided by :term:`IP`. TCP is used by a large number of applications, including :
	English TCP provides a reliable bytestream, connection-oriented transport service on top of the unreliable connectionless network service provided by :term:`IP`. TCP is used by a large number of applications, including : TCP provides a reliable bytestream, connection-oriented transport service on top of the unreliable connectionless network service provided by :term:`IP`. TCP is used by a large number of applications, including : 212/10000 · 212 Needs editing
4 ../../protocols/tcp.rst:16
	English Email (:term:`SMTP`, :term:`POP`, :term:`IMAP`)
	English Email (:term:`SMTP`, :term:`POP`, :term:`IMAP`) Email (:term:`SMTP`, :term:`POP`, :term:`IMAP`) 47/10000 · 47 Needs editing
5 ../../protocols/tcp.rst:17
	English World wide web ( :term:`HTTP`, ...)
	English World wide web ( :term:`HTTP`, ...) World wide web ( :term:`HTTP`, ...) 35/10000 · 35 Needs editing
6 ../../protocols/tcp.rst:18
	English Most file transfer protocols ( :term:`ftp`, peer-to-peer file sharing applications , ...)
	English Most file transfer protocols ( :term:`ftp`, peer-to-peer file sharing applications , ...) Most file transfer protocols ( :term:`ftp`, peer-to-peer file sharing applications , ...) 89/10000 · 89 Needs editing
7 ../../protocols/tcp.rst:19
	English remote computer access : :term:`telnet`, :term:`ssh`, :term:`X11`, :term:`VNC`, ...
	English remote computer access : :term:`telnet`, :term:`ssh`, :term:`X11`, :term:`VNC`, ... remote computer access : :term:`telnet`, :term:`ssh`, :term:`X11`, :term:`VNC`, ... 83/10000 · 83 Needs editing
8 ../../protocols/tcp.rst:20
	English non-interactive multimedia applications (flash, ...)
	English non-interactive multimedia applications (flash, ...) non-interactive multimedia applications (flash, ...) 52/10000 · 52 Needs editing
9 ../../protocols/tcp.rst:22
	English On the global Internet, most of the applications used in the wide area rely on TCP. Many studies [#ftcpusage]_ have reported that TCP was responsible for more than 90% of the data exchanged in the global Internet.
	English On the global Internet, most of the applications used in the wide area rely on TCP. Many studies [#ftcpusage]_ have reported that TCP was responsible for more than 90% of the data exchanged in the global Internet. On the global Internet, most of the applications used in the wide area rely on TCP. Many studies [#ftcpusage]_ have reported that TCP was responsible for more than 90% of the data exchanged in the global Internet. 213/10000 · 213 Needs editing
10 ../../protocols/tcp.rst:26
	English To provide this service, TCP relies on a simple segment format that is shown in the figure below. Each TCP segment contains a header described below and, optionally, a payload. The default length of the TCP header is twenty bytes, but some TCP headers contain options.
	English To provide this service, TCP relies on a simple segment format that is shown in the figure below. Each TCP segment contains a header described below and, optionally, a payload. The default length of the TCP header is twenty bytes, but some TCP headers contain options. To provide this service, TCP relies on a simple segment format that is shown in the figure below. Each TCP segment contains a header described below and, optionally, a payload. The default length of the TCP header is twenty bytes, but some TCP headers contain options. 268/10000 · 268 Needs editing
11 ../../protocols/tcp.rst:32
	English TCP header format
	English TCP header format TCP header format 17/10000 · 17 Needs editing
12 ../../protocols/tcp.rst:35
	English A TCP header contains the following fields :
	English A TCP header contains the following fields : A TCP header contains the following fields : 44/10000 · 44 Needs editing
13 ../../protocols/tcp.rst:37
	English the `source and destination ports`. The source and destination ports play an important role in TCP, as they allow the identification of the connection to which a TCP segment belongs. When a client opens a TCP connection, it typically selects an ephemeral TCP port number as its source port and contacts the server by using the server's port number. All the segments that are sent by the client on this connection have the same source and destination ports. The server sends segments that contain as source (resp. destination) port, the destination (resp. source) port of the segments sent by the client (see figure :ref:`fig-tcpports`). A TCP connection is always identified by four pieces of information :
	English the `source and destination ports`. The source and destination ports play an important role in TCP, as they allow the identification of the connection to which a TCP segment belongs. When a client opens a TCP connection, it typically selects an ephemeral TCP port number as its source port and contacts the server by using the server's port number. All the segments that are sent by the client on this connection have the same source and destination ports. The server sends segments that contain as source (resp. destination) port, the destination (resp. source) port of the segments sent by the client (see figure :ref:`fig-tcpports`). A TCP connection is always identified by four pieces of information : the `source and destination ports`. The source and destination ports play an important role in TCP, as they allow the identification of the connection to which a TCP segment belongs. When a client opens a TCP connection, it typically selects an ephemeral TCP port number as its source port and contacts the server by using the server's port number. All the segments that are sent by the client on this connection have the same source and destination ports. The server sends segments that contain as source (resp. destination) port, the destination (resp. source) port of the segments sent by the client (see figure :ref:`fig-tcpports`). A TCP connection is always identified by four pieces of information : 706/10000 · 706 Needs editing
14 ../../protocols/tcp.rst:39
	English the address of the client
	English the address of the client the address of the client 25/10000 · 25 Needs editing
15 ../../protocols/tcp.rst:40
	English the address of the server
	English the address of the server the address of the server 25/10000 · 25 Needs editing
16 ../../protocols/tcp.rst:41
	English the port chosen by the client
	English the port chosen by the client the port chosen by the client 29/10000 · 29 Needs editing
17 ../../protocols/tcp.rst:42
	English the port chosen by the server
	English the port chosen by the server the port chosen by the server 29/10000 · 29 Needs editing
18 ../../protocols/tcp.rst:44
	English the `sequence number` (32 bits), `acknowledgment number` (32 bits) and `window` (16 bits) fields are used to provide a reliable data transfer, using a window-based protocol. In a TCP bytestream, each byte of the stream consumes one sequence number. Their usage is described in more detail in section :ref:`TCPReliable`
	English the `sequence number` (32 bits), `acknowledgment number` (32 bits) and `window` (16 bits) fields are used to provide a reliable data transfer, using a window-based protocol. In a TCP bytestream, each byte of the stream consumes one sequence number. Their usage is described in more detail in section :ref:`TCPReliable` the `sequence number` (32 bits), `acknowledgment number` (32 bits) and `window` (16 bits) fields are used to provide a reliable data transfer, using a window-based protocol. In a TCP bytestream, each byte of the stream consumes one sequence number. Their usage is described in more detail in section :ref:`TCPReliable` 318/10000 · 318 Needs editing
19 ../../protocols/tcp.rst:45
	English the `Urgent pointer` is used to indicate that some data should be considered as urgent in a TCP bytestream. However, it is rarely used in practice and will not be described here. Additional details about the utilization of this pointer may be found in :rfc:`793`, :rfc:`1122` or [Stevens1994]_
	English the `Urgent pointer` is used to indicate that some data should be considered as urgent in a TCP bytestream. However, it is rarely used in practice and will not be described here. Additional details about the utilization of this pointer may be found in :rfc:`793`, :rfc:`1122` or [Stevens1994]_ the `Urgent pointer` is used to indicate that some data should be considered as urgent in a TCP bytestream. However, it is rarely used in practice and will not be described here. Additional details about the utilization of this pointer may be found in :rfc:`793`, :rfc:`1122` or [Stevens1994]_ 293/10000 · 293 Needs editing
20 ../../protocols/tcp.rst:46
	English the flags field contains a set of bit flags that indicate how a segment should be interpreted by the TCP entity receiving it :
	English the flags field contains a set of bit flags that indicate how a segment should be interpreted by the TCP entity receiving it : the flags field contains a set of bit flags that indicate how a segment should be interpreted by the TCP entity receiving it : 126/10000 · 126 Needs editing