History of the Internet

Rerouting Wasn’t Session Recovery: RFC 3234

When a router failed, the familiar remedy was to find another path. In February 2002, RFC 3234 asked what happened when the failed device did more than route. A middlebox could hold state that the session needed, so restoring reachability did not restore the conversation.

End-of-Frame Bit Could Be the Packet That Vanished: RFC 3189

The End-of-Frame Bit Could Be the Packet That Vanished: RFC 3189

The receiver wanted one clean fact: the picture was finished. RFC 3189 put that news in the marker bit of the last packet, then warned that the packet carrying the news might be the one the network lost. The convenient signal could shorten delay. It could not be the authority for where a frame ended.

Country Prefix Found the Resolver. It Did Not Prove the Archive Kept the Object: RFC 3188

The Country Prefix Found the Resolver. It Did Not Prove the Archive Kept the Object: RFC 3188

The prefix `fi` could tell a client where Finland's branch of the NBN world began. It could not make a harvested Web page survive, authenticate the service answering today, or prove that the returned file was the original. RFC 3188 made a federation of local library numbers globally nameable. Persistence still lived in institutions, archives and running resolvers.

An HTTP Library Was Not an Interoperability Plan: RFC 3205

In 2002, protocol designers were tempted to borrow HTTP for its installed base: browsers, server code, security machinery and access through existing network boundaries. RFC 3205 did not reject that bargain. It asked designers to account for the assumptions that came with it—especially what proxies, caches and ordinary HTTP software would do when an application meant something different.

ISBN Named an Edition. It Could Resolve to Many Copies—or the Wrong Book: RFC 3187

The ISBN Named an Edition. It Could Resolve to Many Copies—or the Wrong Book: RFC 3187

A persistent name was supposed to survive changing locations. RFC 3187 made the bargain concrete and awkward: one ISBN URN might lead to many URLs, no digital object at all, or two bibliographic records because a publisher had reused a number by mistake. Persistence belonged to the identifier. Singularity did not.

RFC 1180 Explained TCP/IP, Then Sent Readers Back to the Standards

In January 1991, T.J. Socolofsky and C.J. Kale offered network professionals a practical way to follow an IP datagram from one host, through a router, to another. They also drew a bright line: the memo explained TCP/IP; it did not define it.

Customer Saw a Private Wire. The Operator Held the Hidden Address Pair: RFC 3186

The Customer Saw a Private Wire. The Operator Held the Hidden Address Pair: RFC 3186

At one edge, customer equipment emitted an ordinary PPP frame. At the other, customer equipment received one. Between them, switches replaced the frame’s first octets, forwarded it through a shared MAPOS fabric, restored the original values and withheld the machinery from view. RFC 3186 called the result transparent. Its more durable lesson is that a simple interface can conceal a dense control surface without making that surface disappear.

Recipient List Shrunk. The Old Key Still Opened the Message: RFC 3185

The Recipient List Shrunk. The Old Key Still Opened the Message: RFC 3185

The second encrypted message named fewer recipients than the first. One omitted member could still open it. Nothing had malfunctioned: RFC 3185 warned that this was the expected consequence of deriving a later key-encryption key from content-key material already delivered to the original group. The visible envelope had narrowed; effective decryption authority had not.

Domain Signed the Message. The Individual Was Still Unnamed: RFC 3183

The Domain Signed the Message. The Individual Was Still Unnamed: RFC 3183

A recipient could verify that a message had crossed an authenticated organizational boundary and still be unable to display the name of the person who sent it. RFC 3183 made that distinction unusually explicit. Its domain-security machinery did not offer one generic act called “signing”; it assigned different authorities to origin, release, review, attribute binding, encryption and decryption—and required the recipient to know which claim each cryptographic layer actually carried.

Firewall Was Allowed to Say No. It Wasn't Supposed to Break the Conversation: RFC 2979

The Firewall Was Allowed to Say No. It Wasn't Supposed to Break the Conversation: RFC 2979

In October 2000, an Informational RFC drew a line that packet filters often blurred: a site could refuse traffic for security reasons, but a firewall should not accidentally make legitimate, standards-compliant communication fail. That distinction assigned the repair bill to the intermediary—not to every application trying to work around it.

Name Entered RSVP. Authority Still Had to Decide What It Meant: RFC 3182

The Name Entered RSVP. Authority Still Had to Decide What It Meant: RFC 3182

In 2001, an RSVP request could carry a user name, an application name, a Kerberos ticket or a certificate toward the router deciding whether a flow deserved scarce resources. That sounds like identity becoming authority. RFC 3182 documented something more conditional. The name located a policy, the credential supported authentication, a decision point interpreted the rule and an enforcement point acted locally. Along a multicast tree, even the identity that survived could be selected. The protocol’s history is therefore not a story about putting a passport in a packet. It is about preserving every hand that turned identity into a resource decision—and refusing to call that decision a delivered service.

A Secure Peer Link Could Still Carry an Untrusted MASC Claim: RFC 2909

MASC divided multicast address space into temporary, nested claims. Its 2000 security section identified a harder boundary: protecting the next peer did not make every relayed update trustworthy.

New Flow Won Admission. Its Defending Priority Still Had to Survive the Next Arrival: RFC 3181

The New Flow Won Admission. Its Defending Priority Still Had to Survive the Next Arrival: RFC 3181

A flow could arrive late and still displace an earlier reservation. RFC 3181 made that reversal deliberate, but it did not give one number permanent authority. The new flow competed with a preemption priority; after admission, another value became its defence against the next arrival. Between those moments stood policy origin, merge rules, local capacity, enforcement and error signalling. Beyond them stood packet treatment and application outcome. The protocol’s useful history is the distance between a rank and the service people assume it purchased.

One AS, 256 Multicast Addresses—and a Four-Byte Limit

GLOP made a static multicast block calculable from an existing network number: useful when groups had to stay put, but only as flexible as the two-byte AS field it borrowed.

Runtime Replied 231. The Script Still Owed a Termination Receipt: RFC 3179

The Runtime Replied 231. The Script Still Owed a Termination Receipt: RFC 3179

A control system can answer correctly before the work is done. RFC 3179 made that temporal gap explicit: one reply said a management script had reached a runtime state, other messages carried intermediate output or errors, and a later reply marked termination. None of them alone proved that the intended change reached the network. The protocol’s lasting lesson was not remote scripting. It was how to keep command acceptance, execution evidence and operational outcome from collapsing into one green light.

IPv6 /48 Was a Starting Point, Not a Size for Every Site

The IPv6 /48 Was a Starting Point, Not a Size for Every Site

The story of the IPv6 /48 is not that the IETF discovered it was too large. It is that a tidy architectural recommendation became awkward when different kinds of real networks had to live inside the same prefix table.

Core Forgot the Flow. The Edges Still Had to Prove Its Reservation: RFC 3175

The Core Forgot the Flow. The Edges Still Had to Prove Its Reservation: RFC 3175

RFC 3175 offered an attractive bargain in 2001: stop making every core router remember every reserved flow, but preserve end-to-end admission at the edges. The bargain worked only if state compression did not become evidence compression. One large reservation could carry thousands of promises; it could not prove that any particular promise had been honoured.

IETF Removed a Conduct Rule That Could Discourage Newcomers

The IETF Removed a Conduct Rule That Could Discourage Newcomers

In 2014, an IETF revision did more than refresh a conduct guide: it recorded that one warning to newcomers could be read as a reason not to participate—and removed it.

DNS MIBs Never Reached Deployment. RFC 3197 Made That the Point.

The DNS MIBs Never Reached Deployment. RFC 3197 Made That the Point.

RFC 3197 is a rare standards postmortem: it says two DNS management MIBs never found deployment, then treats that absence as evidence about the project—not about DNS itself.

Zone Was Critical. That Did Not Make It a Permanent Root-Server Job: RFC 3172

The Zone Was Critical. That Did Not Make It a Permanent Root-Server Job: RFC 3172

In 2001, `.arpa` was important enough to inherit the operating expectations of the DNS root. Yet RFC 3172 did not convert that importance into a permanent claim on root-server machines. It recorded the shared service arrangement as something likely to change. The name could remain stable while the operators, delegations and proof of service moved.