History of the Internet

One Retry Saved the Frame. The Delay Belonged to Every Flow Behind It: RFC 3366

In August 2002, the IETF made a small link-layer choice visible as an Internet-wide design problem: how long should a damaged frame keep another packet waiting? A retry can recover a transmission before TCP reaches across the end-to-end path. But every attempt spends time, and the link may not know which waiting traffic can afford it.

Lease Named the Proxy. It Did Not Prove the Call Path Worked: RFC 3361

The Lease Named the Proxy. It Did Not Prove the Call Path Worked: RFC 3361

A DHCP reply could tell a SIP client where to begin, but the small option that named an outbound proxy was never a receipt for the path beyond it. RFC 3361 encoded that distinction in two forms whose bytes delegated later decisions to very different control surfaces.

List Had No Authority. It Still Kept Two Extensions from Choosing the Same Number: RFC 3359

The List Had No Authority. It Still Kept Two Extensions from Choosing the Same Number: RFC 3359

Before IS-IS had a plausible central allocator for every TLV value, it still needed a way to stop two extensions from teaching the same byte two incompatible meanings. RFC 3359 made coordination useful without pretending it was sovereignty.

Frame Passed Its Check. The Routing Summary Could Still Be Corrupt: RFC 3358

The Frame Passed Its Check. The Routing Summary Could Still Be Corrupt: RFC 3358

A successful lower-layer check was a receipt for a frame, not for every byte the routing process later trusted. RFC 3358 put a narrow integrity test exactly where that assumption could fail.

A DNS Alias Could Move a Service. It Could Not Prove One Existed: RFC 2219

In 1997, familiar labels such as `www` and `ftp` offered a convenient front door to a service that might move between machines. RFC 2219 turned that custom into guidance, while drawing a firm line between a useful naming hint and proof that a service was running.

Loss Rate Counted the Missing Packets. It Did Not Show Whether They Fell Together: RFC 3357

The Loss Rate Counted the Missing Packets. It Did Not Show Whether They Fell Together: RFC 3357

One percentage can describe two packet streams that feel nothing alike. RFC 3357 preserved the order that an average throws away, while refusing to turn a pattern into a diagnosis.

Delegate Spoke for an Institution. The Working Group Still Had to Decide: RFC 3356

The Delegate Spoke for an Institution. The Working Group Still Had to Decide: RFC 3356

RFC 3356 solved a problem that standards bodies often blur: how can a person carry an institution’s authorized position into another institution without carrying the power to decide there? Its answer was a chain of provenance, not a transfer of sovereignty.

Tunnel Hid the Bearer. The Bearer Still Set the Envelope: RFC 3355

The Tunnel Hid the Bearer. The Bearer Still Set the Envelope: RFC 3355

L2TP was designed to be largely indifferent to the medium beneath it. RFC 3355 showed the price of that abstraction: ATM could disappear from the inner protocol’s view, while one AAL5 virtual circuit still fixed the size, identity and lifetime of the outer envelope.

Fifteen Fields Could Travel. Their Meaning Still Needed a Local Contract: RFC 2413

In 1998, Dublin Core offered the growing Web a small shared vocabulary for describing resources. Its deliberate looseness made the vocabulary portable—but left collections and search systems to decide what those fields meant in practice.

Protocol Could Propose Any Sequence. It Could Not Pre-Approve the Charge: RFC 3354

The Protocol Could Propose Any Sequence. It Could Not Pre-Approve the Charge: RFC 3354

An online trade can be arranged as a sequence: offer, approval, shipment, payment and receipt. RFC 3354 wanted IOTP to make that order flexible. Its more durable lesson is that arranging the steps did not grant authority to perform them.

Tag Stayed 96 Bits. The Hash Behind It Changed: RFCs 2403 and 2404

The Tag Stayed 96 Bits. The Hash Behind It Changed: RFCs 2403 and 2404

Two IPsec transforms kept the transmitted authenticator at 96 bits while changing the hash underneath it. That stable field made packet formats comparable; it did not make the algorithms, key sizes or later implementation advice identical.

First Packet Had to Arrive Before Its Labelled Branch Could Exist: RFC 3353

The First Packet Had to Arrive Before Its Labelled Branch Could Exist: RFC 3353

In 2002, multicast over MPLS contained a small operational paradox. A router could wait for traffic before spending a label on a new branch. But the downstream router that needed the branch could not see that traffic at Layer 2 until the branch had already been built. RFC 3353 turned that loop into an engineering choice instead of hiding it behind the word “automatic.”

URI Worked Before the Profile Was Permanent: RFC 3349

The URI Worked Before the Profile Was Permanent: RFC 3349

A development name can already move a protocol conversation while remaining institutionally unfinished. RFC 3349 made that tension explicit: it gave an IETF working group a controlled BEEP Profile URI for use during drafting, then refused to let the useful string masquerade as the permanent assignment that might follow publication.

Key Could Change. The Known Plaintext Still Could: RFC 2405

The Key Could Change. The Known Plaintext Still Could: RFC 2405

RFC 2405 treated key lifetime as a risk decision, not a stopwatch that could make single DES strong. Its 1998 account put known plaintext, attacker economics and authentication in separate places—and later ESP requirements moved DES from required to prohibited without proving when every network stopped using it.

CLDAP Could Not Outgrow Its Security Limits: RFC 3352

In 1995, CLDAP promised a shorter route to a small directory answer. Eight years later, the IETF recorded why that shortcut had not matured into a maintainable standard—and why “Historic” was a status judgment, not an order to erase running code.

MPLS Chose Another Path. It Did Not Create Capacity: RFC 3346

In 2002, MPLS traffic engineering offered backbone operators something ordinary shortest-path routing did not: the ability to move selected traffic onto an explicit route. RFC 3346 also recorded the harder lesson. A path can redistribute load only across capacity that already exists, and the bandwidth configured on an LSP is a model that must be tested against the traffic actually carried.

New Address Was Accepted. The Old One Stayed Live: RFC 3344

The New Address Was Accepted. The Old One Stayed Live: RFC 3344

The registration succeeded, but nothing in that success required the previous route to disappear. RFC 3344 gave a mobile node one bit with which to preserve the older binding, and required a supporting home agent to send a separate copy of every intercepted datagram down every still-active path.

SIP Could Add Text Without Ending the Call: RFC 3351

In 2002, an accessibility proposal treated voice, text, video and relay services as parts of one changing conversation. Its most revealing idea was not a new codec: a caller should not have to restart the call just to add a way to communicate.

Subscription Ended. Its Updates Had Not: RFC 3343

The Subscription Ended. Its Updates Had Not: RFC 3343

The cancellation receipt arrived first. Then came another presence update tied to the subscription that had just ended. RFC 3343 treated both messages as valid: the service had stopped the operation, but an update sent earlier could still be crossing the relay mesh. Termination closed the source; it did not rewrite the network's past.

Delay Report Fired. The Message Kept Moving: RFC 3342

The Delay Report Fired. The Message Kept Moving: RFC 3342

At one relay, a timer reached zero and a warning went back to the sender. The data did not stop. It crossed into the next relay because RFC 3342 had assigned observation and enforcement to different clocks. The distinction is small in syntax and large in consequence: a truthful alarm can coexist with a message still in flight.