All specs
RFC 9293RFCShould KnowProduct2022

Transmission Control Protocol

Transport·RFC Editor
WHY YOU NEED THIS

Every HTTP request your app makes rides on TCP. Understanding TCP helps with latency, timeouts, keep-alives, and connection pooling.

What It Defines

Defines reliable, ordered, connection-oriented byte-stream transport over IP. The foundation for HTTP/1.1, HTTP/2, SMTP, IMAP, and most internet application protocols.

Canonical (Normative)

Convenient (Practical)

tcptransportnetworking
Standards Body
RFC Editor

The canonical publication point for finalized RFCs. If a protocol is standardized as an RFC, the RFC Editor text is the normative final reference. Published by the IETF, IRTF, IAB, and independent stream.

Visit

Related Specs

RFC 768RFCShould Know

UDP

DNS runs over UDP. QUIC and HTTP/3 run over UDP. Media and gaming often use UDP for low-latency delivery.

ProductTransport
Details
RFC 9000RFCShould Know

QUIC

HTTP/3 runs on QUIC. Modern CDNs and browsers use it by default. It fixes TCP's head-of-line blocking problem for multiplexed requests.

ProductTransport
Details
RFC 8446RFCMust Know

TLS 1.3

Every HTTPS connection, SMTP/IMAP over TLS, OAuth token exchange, and API call uses TLS. It is the foundational security layer.

Back OfficeProductTransport Security
Details