History of the Internet

Firewall Allowed HTTP. It Had Not Approved the Packet Inside: RFC 3093

The Firewall Allowed HTTP. It Had Not Approved the Packet Inside: RFC 3093

RFC 3093 proposed putting a complete IP datagram inside an HTTP message, passing it through the ordinary web opening, and reinserting it behind the firewall. Published on 1 April 2001, the comic design exposed a serious limit: a policy decision about an outer envelope says nothing by itself about the packet hidden inside.

Same Zone Was Secure Here and Unsecured Elsewhere: RFC 3090

The Same Zone Was Secure Here and Unsecured Elsewhere: RFC 3090

In 2001, DNSSEC could not answer “is this zone secure?” without first asking who was resolving it, which trust anchor that resolver held, and which path it followed. RFC 3090 named that awkward reality. A signed zone could belong to a local island of security and still look unsecured to the rest of the Internet.

Root Returned a Referral, Not the Directory: RFC 3088

The Root Returned a Referral, Not the Directory: RFC 3088

In a distributed directory, the first server may know where the next one lives without knowing the answer to the user's search. RFC 3088 made that distinction concrete: OpenLDAP's experimental root service read DNS service records and handed clients LDAP URLs, leaving the referred directory to answer.

URI Chose the Voicemail Menu. It Did Not Authenticate the Caller: RFC 3087

The URI Chose the Voicemail Menu. It Did Not Authenticate the Caller: RFC 3087

In 2001, SIP could carry a call to voicemail without carrying every trustworthy clue that an old telephone system used to choose the first greeting or menu. RFC 3087 turned the request target itself into a service instruction. That solved a routing problem, but it deliberately left identity and permission to another decision.

Policy Server Pushed the Rules. A Reconnect Had to Reconcile What the Device Kept: RFC 3084

The Policy Server Pushed the Rules. A Reconnect Had to Reconcile What the Device Kept: RFC 3084

RFC 3084 tried to make policy provisioning a disciplined conversation between a server and a network device. Its most revealing work began after delivery: a transaction needed a receipt, a failure needed rollback, and a broken connection left two machines that could remember different versions of the truth.

A Revision Number Could Order a NewsItem. It Could Not Fetch One: RFC 3085

NewsML could let one logical news item live at several addresses, so RFC 3085 gave it one URN and a per-item revision number. The design was precise about which edition came later and what kind of update it represented; it left resolution and validation to a provider that might offer either service—or might not.

Cable Link Encrypted Traffic. Its Management Plane Could Still Disable Privacy: RFC 3083

The Cable Link Encrypted Traffic. Its Management Plane Could Still Disable Privacy: RFC 3083

RFC 3083 turned DOCSIS Baseline Privacy into something operators could inspect, tune and reset through SNMP. That visibility helped diagnosis and incident response, but it created a second security boundary: the interface that observed encryption state could also change lifetimes, restart authorization, invalidate traffic keys and control multicast access.

TCP Was Reliable. One Channel Could Still Starve the Others: RFC 3081

RFC 3081 placed one BEEP session on one TCP connection, then confronted a consequence TCP could not solve for it. Reliable delivery for the connection did not guarantee progress for every application channel inside it. The mapping therefore added local credit, priority control frames and a scheduling recommendation above the reliable stream.

Notices Continued After the Directory Agent. New Services Could Still Be Missed: RFC 3082

The Notices Continued After the Directory Agent. New Services Could Still Be Missed: RFC 3082

RFC 3082 tried to replace wasteful polling with event-driven service discovery. Its recovery rules expose a more precise trade-off: a Directory Agent can lose subscription state while service agents already informed of that subscription keep announcing. A new service may enter during the gap without ever learning that anyone is listening.

One Connection Was Not One Conversation: RFC 3080

A BEEP connection could be healthy while no application conversation had yet been agreed. RFC 3080 began with channel zero, a deliberately thin management plane that advertised profiles and negotiated new channels. Only an accepted profile gave an application channel meaning. That separation—wire, session, lane, exchange, effect—was the architecture’s most durable lesson.

Master Key Never Encrypted a Packet: RFC 3079

The Master Key Never Encrypted a Packet: RFC 3079

RFC 3079 called one value a master key, then forbade it from touching traffic. Its job was to feed two role-aware branches, which in turn produced transient send and receive keys for separate cipher contexts. That hierarchy made a quiet point about interoperability: deriving plausible bytes was not enough. Both ends had to agree about the credential event, endpoint role, direction and negotiated strength that gave those bytes meaning.

Counter Detected the Lost Packet. It Could Not Decrypt the Next One: RFC 3078

The Counter Detected the Lost Packet. It Could Not Decrypt the Next One: RFC 3078

RFC 3078 placed a twelve-bit counter beside encrypted PPP traffic so a receiver could notice when the stream had jumped. In stateful mode, that knowledge arrived with an uncomfortable consequence: the packet that exposed the gap still had to be thrown away. Recovery needed a message in the other direction and a new boundary from the sender. Detection was evidence of failure, not restoration of service.

Satellite Was One-Way. The Link-Layer Model Was Not: RFC 3077

The Satellite Was One-Way. The Link-Layer Model Was Not: RFC 3077

In a satellite network, a receiver could hear a feed without being able to answer it on the same medium. RFC 3077 did not make that asymmetry disappear. It joined the broadcast path to a separate Internet backchannel, then tried to let ordinary link-layer protocols behave as though both directions belonged to one network.

Bytes Became Canonical Only After the Parser Had Already Changed the Document: RFC 3076

The Bytes Became Canonical Only After the Parser Had Already Changed the Document: RFC 3076

Canonical XML promised a stable byte stream, not a time machine. Before RFC 3076 could sort a single attribute, an XML processor had already normalized line endings, expanded entities, replaced CDATA and built an XPath node-set. The resulting octets could be repeated exactly. They could not, by themselves, tell you which file, parser context or external resources had produced that model.

Signature Verified the Transform. It Did Not Verify the Document You Saw: RFC 3075

The Signature Verified the Transform. It Did Not Verify the Document You Saw: RFC 3075

In XML Signature, a green cryptographic result belonged to a deliberately constructed object: referenced data after its declared transforms, represented by digests inside canonicalized `SignedInfo`. RFC 3075 made that receipt precise. It also warned that the source document, the screen shown to a person, the key’s institutional meaning and the application’s decision could all be different things.

Hash Chose Which DHCP Server Could Answer. It Could Not Promise Service

The Hash Chose Which DHCP Server Could Answer. It Could Not Promise Service

RFC 3074 turned a configured share into 256 buckets and a repeatable answer to one narrow question: which server was eligible to respond? The map did not measure work or prove a lease arrived.

Hash Assigned the Server. It Did Not Prove the Server Was Ready: RFC 3074

The Hash Assigned the Server. It Did Not Prove the Server Was Ready: RFC 3074

RFC 3074 let cooperating DHCP servers compute who should answer without negotiating each request. The same calculation could not say whether the chosen server was reachable, had an address to offer or completed the client's configuration.

MIME Name Was Public. The Font Specification Still Lived at the Vendor: RFC 3073

The MIME Name Was Public. The Font Specification Still Lived at the Vendor: RFC 3073

RFC 3073 gave Portable Font Resource files a public MIME name. It did not make that name a substitute for the complete specification, a compatible decoder or evidence that a recipient rendered the intended glyphs.

Parser Could Skip the Chunk. It Could Not Know What It Meant: RFC 3072

The Parser Could Skip the Chunk. It Could Not Know What It Meant: RFC 3072

RFC 3072 made an unfamiliar SDXF chunk traversable by giving it a boundary a reader could locate. But reaching the next chunk is not the same as understanding what was skipped—or knowing whether an application can safely ignore it.

Label Was a Country Code. The Registry Could Still Be Generic: RFC 3071

The Label Was a Country Code. The Registry Could Still Be Generic: RFC 3071

In 2001, John Klensin argued that two characters could identify a country-code namespace without telling readers how its registry actually behaved. RFC 3071’s proposed categories followed operating practice—not the shape of the label—and stopped short of asking DNS administrators to decide who counted as a country.