Skip to main content
Definition Website Computer and Technology

Transmission Control Protocol

Subject: Computer and Technology noun /trænzˈmɪʃ.ən kənˈtroʊl ˈproʊ.tə.kɔːl/ 1 definition

  1. Definition (noun)

    Entry #12 · Updated

    The Transmission Control Protocol (TCP) is a connection-oriented transport-layer protocol in the Internet protocol suite that establishes a stateful session between two hosts to deliver a reliable, ordered, and error-checked stream of bytes. Using a three-way handshake, sequence numbers, acknowledgments, checksums, and adaptive flow and congestion control, it detects lost, duplicated, or corrupted packets and retransmits missing segments transparently to the application. Unlike the underlying Internet Protocol (IP), which only routes individual packets on a best-effort basis, or connectionless protocols like the User Datagram Protocol (UDP) that prioritize minimal latency, TCP guarantees complete, in-order data delivery for workloads such as web browsing, file transfers, and email.

    Common Forms

    • Standard Single-Path TCP: The baseline specification used by protocols such as HTTP/1.1, HTTP/2, SSH, and SMTP, maintaining a single stateful byte stream between one client socket and one server socket.

    • Loss-Based Variants (TCP Reno and CUBIC): Congestion-control implementations that treat dropped packets as signs of network saturation and reduce the sending window accordingly, with CUBIC serving as the default in Linux and Windows.

    • Bottleneck-Model Variants (TCP BBR): Algorithms that pace outgoing traffic by continuously estimating bottleneck bandwidth and minimum round-trip propagation time rather than waiting for packet loss, reducing queuing delay and bufferbloat.

    • Multipath TCP (MPTCP): A standardized extension that distributes a single logical TCP connection across multiple network interfaces—such as Wi-Fi and cellular—simultaneously for seamless failover and higher aggregate throughput.

    Example

    When a user downloads a 50 MB software update over HTTPS, the client's operating system completes a TCP three-way handshake (SYN, SYN-ACK, ACK) with the server on port 443 before any application data is exchanged. If a segment is dropped mid-transfer by a congested router, the receiver buffers out-of-order arrivals and sends duplicate acknowledgments until the server retransmits the missing byte range, reconstructing an intact file for the browser.