technologybriefs
8:41in productionCh. 1 · A protocol unbound/ 8:41 · ceiling 15 min
Internet culture · Tech history

IPv4

1981

IPv4 didn’t build the Internet — it split the protocol stack, then ran out of numbers.

IPv4 is the foundational, standalone Internet Protocol specification. It introduced the 32-bit address space and decoupled IP from TCP. Its best-effort delivery model enabled rapid early internetworking — but baked in exhaustion, fragility, and reliance on add-ons like NAT and TCP.

Internet cultureTech historyComputingInfrastructureThe internetComputing across the network →
Chapters & takeaways4
  1. 0:58
    A protocol unbound

    IPv4 was the first time IP existed as its own spec — no longer bundled with TCP.

  2. 2:47
    From paper to packet

    RFC 791 (September 1981) defined it; production began on SATNET in 1982 and ARPANET in January 1983.

  3. 4:31
    The arithmetic of scarcity

    32 bits yield 4.3 billion addresses — but large blocks are reserved, shrinking the usable pool.

  4. 5:49
    Best effort, not best outcome

    No delivery guarantee. No sequencing. No duplicate suppression. That’s by design.

Worth your time?

Yes. Study the whole thing.

4/ 5
What works
  • inter-network routing
  • header-based forwarding
  • heterogeneous link integration
  • stateless packet switching
What does not
  • scale
  • secure
  • self-configure
  • avoid exhaustion
Study it if
  • network architects
  • protocol historians
  • embedded systems maintainers
Skip it if
  • cloud infrastructure designers
  • IoT deployment leads
  • zero-trust security engineers
The written brief1 min read

What it is and the problem it solves

IPv4 is the first standalone specification of the Internet Protocol. It solves the problem of defining a universal packet-switching layer distinct from transport logic. It replaces the combined TCP/IPv3 specification.

How it works

IPv4 is a connectionless protocol. It routes packets independently. It makes no guarantees about delivery, order, or duplication. It relies on higher-layer protocols like TCP to handle reliability.

What works

The 32-bit address space delivers 4,294,967,296 unique identifiers. The best-effort model works across dissimilar physical networks. The header format enables routers to forward packets with minimal processing. Deployment on SATNET in 1982 and ARPANET in January 1983 proves operational viability.

What does not

IPv4 does not scale to global end-user growth. It does not prevent address collisions without NAT. It does not support built-in encryption, authentication, or autoconfiguration. It does not recover from packet loss or reorder errors.

What it changes

IPv4 separates IP from TCP for the first time. It establishes IP as an independent, routable layer. It enables heterogeneous networks to interconnect via a common packet format. It locks in the 32-bit addressing model that defines the Internet’s first scaling crisis.

Is it worth your time

Yes — if you are working on network fundamentals, legacy interoperability, or understanding address exhaustion’s root cause. No — if you assume modern routing, security, or scalability features exist in IPv4 itself.

Same field · Internet culture4 of 6
8:48
ARPANET1969ARPANET proved packet-switched networking could work across distance and institutional boundaries—but only for trusted researchers, over custom hardware, with no security, no scalability guarantees, and no plan for public use.
10:34
Internet Message Access Protocol1986IMAP establishes email as a shared, persistent, server-managed resource—not a transient download. It works by defining precise commands for mailbox operations, flag persistence, partial message fetches, and extensibility—all over port 143. What works is its concurrency model, server-side search, and folder management. What does not is any guarantee of implementation fidelity, security defaults, or performance. It changes how email scales across devices and teams. It is worth your time if you rely on synchronised, searchable, cross-platform access to live mailboxes.
10:24
IPv61996IPv6 delivers on its core architectural promises: vast address space, simplified forwarding, standardised subnets, and host-managed fragmentation. But it does not deliver automatic deployment, backward compatibility, or operational simplicity. Its value is real—but only where the cost of maintaining IPv4 workarounds exceeds the cost of adopting IPv6’s stricter host responsibilities.
9:48
Simple Mail Transfer Protocol1982SMTP is a minimal, text-based relay protocol. It enables interoperable server-to-server mail exchange but provides no sender identity, no encryption, and no delivery guarantees. Its longevity stems from its narrow scope—not its completeness.
Up next in Technology

IPv6

1996 · 10:24

IPv6 fixes IPv4’s address math—but forces hosts to solve problems routers used to handle.

Play nextBack to Internet culture
10:24