RFC 768RFCShould KnowProduct1980

User Datagram Protocol

Transport·RFC Editor

WHY YOU NEED THIS

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

What It Defines

Connectionless, unreliable transport protocol. Used directly for DNS queries and as the basis for QUIC (HTTP/3).

Canonical (Normative)

RFC 768

udptransportnetworking

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 9293RFCShould Know

TCP

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

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