All specs
RFC 791RFCShould KnowBack OfficeProduct1981

Internet Protocol version 4

Transport·RFC Editor
WHY YOU NEED THIS

Your servers, load balancers, firewalls, and security groups are all defined in IPv4/CIDR. Know the addressing model.

What It Defines

Defines IP addressing, packet structure, and routing for IPv4. Still the dominant addressing scheme for most internet traffic.

Canonical (Normative)

Convenient (Practical)

ipnetworkingaddressing
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 8200RFCShould Know

IPv6

ISPs and cloud providers are rolling out IPv6 dual-stack. AAAA records, IPv6 CIDR, and dual-stack routing are real concerns.

Back OfficeProductTransport
Details
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 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