Difference between revisions of "Transmission Control Protocol"
(Created page with "The '''Transmission Control Protocol''' is the reliable byte stream protocol of the TCP/IP protocol suite. It runs on top of the Internet Protocol -...") |
(Early documents discussing the Transmission Control *Program*.) |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | The '''Transmission Control Protocol''' is the [[reliable byte stream]] [[protocol]] of the [[TCP/IP]] [[protocol suite]]. | + | The '''Transmission Control Protocol''' (usually '''TCP''') is the [[reliable byte stream]] [[protocol]] of the [[TCP/IP]] [[protocol suite]]. It provides [[connection]]s, identified by a pair of [[Internet Protocol]] host [[address]]es and a 16-bit [[networking port|port]] number on each end, between pairs of [[host]]s. |
| − | It runs on top of the | + | It runs on top of the Internet Protocol - the [[internetworking layer]] in TCP/IP. That layer is unreliable - [[packet]]s carried by it may be delayed, damaged, duplicated, re-ordered, or lost. TCP therefore has to use a number of mechanisms to built a reliable stream out of the unreliable substrate. |
To do that, it uses [[checksum]]s (to prevent and detect damaged data), [[sequence number]]s (each byte sent over the channel is individually numbered), [[acknowledgement]]s, [[timeout]]s (to look for missing acknowledgements), and [[re-transmission]]s (of data which was damaged, or never acknowledged, and thus was somehow lost). | To do that, it uses [[checksum]]s (to prevent and detect damaged data), [[sequence number]]s (each byte sent over the channel is individually numbered), [[acknowledgement]]s, [[timeout]]s (to look for missing acknowledgements), and [[re-transmission]]s (of data which was damaged, or never acknowledged, and thus was somehow lost). | ||
| − | A number of major | + | A number of major [[application]] protocols (including [[Hypertext Transfer Protocol|HTTP]], [[email]], etc) are built on top of TCP. |
| + | |||
| + | ==See also== | ||
| + | |||
| + | * [[TCP and Internet Meetings]] | ||
| + | * [[TCP and IP bake offs]] | ||
| + | |||
| + | ==External links== | ||
| + | |||
| + | * [https://www.cs.princeton.edu/courses/archive/fall06/cos561/papers/cerf74.pdf A Protocol for Packet Network Intercommunication] | ||
| + | * [https://datatracker.ietf.org/doc/html/rfc675 RFC 675 - Specification of Internet Transmission Control Program] | ||
| + | |||
| + | {{semi-stub}} | ||
[[Category: TCP/IP Protocols]] | [[Category: TCP/IP Protocols]] | ||
Latest revision as of 09:16, 5 August 2024
The Transmission Control Protocol (usually TCP) is the reliable byte stream protocol of the TCP/IP protocol suite. It provides connections, identified by a pair of Internet Protocol host addresses and a 16-bit port number on each end, between pairs of hosts.
It runs on top of the Internet Protocol - the internetworking layer in TCP/IP. That layer is unreliable - packets carried by it may be delayed, damaged, duplicated, re-ordered, or lost. TCP therefore has to use a number of mechanisms to built a reliable stream out of the unreliable substrate.
To do that, it uses checksums (to prevent and detect damaged data), sequence numbers (each byte sent over the channel is individually numbered), acknowledgements, timeouts (to look for missing acknowledgements), and re-transmissions (of data which was damaged, or never acknowledged, and thus was somehow lost).
A number of major application protocols (including HTTP, email, etc) are built on top of TCP.
