History of the Internet

Printer Had to Accept the Whole Request Before Replying: RFC 3196

The Printer Had to Accept the Whole Request Before Replying: RFC 3196

In 2011, a small correction to an older printing guide changed a deceptively important boundary: an IPP printer’s final answer to a print request could no longer be treated as implementation-dependent while the document itself was still arriving.

Registry Assigned the Multicast Address. It Still Had to Ask Whether Anyone Used It: RFC 3171

The Registry Assigned the Multicast Address. It Still Had to Ask Whether Anyone Used It: RFC 3171

An entry in a registry can look permanent because the number does not move. RFC 3171 treated that stillness with suspicion. A globally coordinated IPv4 multicast address was scarce enough to require a reason, alternatives, periodic review and—where possible—reclamation. The ledger could preserve a decision without proving that the application still ran.

A BEEP receipt did not authenticate the event: RFC 3195

RFC 3195 moved syslog from a best-effort datagram into a reliable, ordered BEEP channel, then offered a second, per-entry reply model. Neither receipt says that an event is true, durably stored, or acted upon.

Index Named the Policy Row. It Did Not Explain What the Row Meant: RFC 3159

The Index Named the Policy Row. It Did Not Explain What the Row Meant: RFC 3159

A provisioning system receives two rows. Both contain the same values. Only their row numbers differ. Does that mean the network has received two different policies, the same policy twice, or merely two addressable records awaiting interpretation? RFC 3159 chose a precise answer for one part of that question: its `InstanceId` identified a row and nothing more. The number was a coordinate. Policy meaning, installation and effect had to be proved elsewhere.

Server Decided. The NAS Still Had to Act: RFC 3169

The Server Decided. The NAS Still Had to Act: RFC 3169

RFC 3169 drew a clean line between evidence sent by an access device, the authority to decide who may connect, and the equipment that must make that decision real. Its 2001 checklist is not proof that any network completed the whole chain.

Translator Changed the Packets. It Had to Change the Reports Too: RFC 3158

The Translator Changed the Packets. It Had to Change the Reports Too: RFC 3158

An RTP translator could make a stream fit a different link by changing its encoding, packet size, sequence numbers or timestamp rate while preserving the source identifier. That success created a quieter obligation. The RTCP reports had to be translated into the same packet history. Otherwise the media could play while the control channel confidently counted bytes, packets and losses that no longer existed on the receiver’s side. RFC 3158 turned that mismatch into a testable boundary.

RFC Still Said Standards Track. Its Record Said Historic: RFC 3167

The RFC Still Said Standards Track. Its Record Said Historic: RFC 3167

An old standard can keep its original publication language while its live record changes. RFC 3167 captures one such handoff: a request grounded in a claim about use, followed in today’s catalog by a Historic label.

Server Did Not Need the Plaintext. It Still Controlled Availability: RFC 3157

The Server Did Not Need the Plaintext. It Still Controlled Availability: RFC 3157

In August 2001, RFC 3157 asked how one cryptographic identity could follow a user or router from one device to another. Its answer began with confidentiality but did not end there. A credential server might store an object it could not use as plaintext and still decide whether that object could be listed, downloaded, replaced or deleted. Direct transfer avoided that repository but needed its own authenticated sender and receipt. Moving the secret was one event. Preserving identity, authority and a usable outcome required several more.

Junior Operator Could Start It. The Senior Operator Built It: RFC 3165

The Junior Operator Could Start It. The Senior Operator Built It: RFC 3165

In 2001, the Script MIB made remote management code a set of visible, controllable objects. Its emergency example drew a consequential line: junior operators could press a prepared launch button, while senior operators kept the right to install the script and configure that button.

Sender Saw Loss. It Could Not See the Cause: RFC 3155

The Sender Saw Loss. It Could Not See the Cause: RFC 3155

In August 2001, RFC 3155 confronted a problem hidden inside one of TCP's most useful habits. A missing acknowledgement told the sender that progress had failed, but not why. A congested queue, a corrupted radio transmission, reordered packets and a damaged acknowledgement could leave overlapping traces. TCP kept the conservative response because guessing wrong about congestion could injure everyone sharing the path. Faster recovery could reduce the penalty. It could not turn a symptom into a cause.

Relay Added a Header. The Message Lost Its Ending: RFC 3164

The Relay Added a Header. The Message Lost Its Ending: RFC 3164

In the older BSD syslog format, a relay could make a bare event easier to read by adding a timestamp and hostname. RFC 3164 also gave the whole packet a hard 1,024-byte ceiling—so that helpful header could consume the space reserved for the message itself.

Receiver Offered Multiplexing. The Sender Still Chose Whether to Use It: RFC 3153

The Receiver Offered Multiplexing. The Sender Still Chose Whether to Use It: RFC 3153

In August 2001, RFC 3153 offered a way to make small PPP packets spend fewer bytes on envelopes. Several packets could travel as subframes inside one multiplexed frame. Yet the standard drew an unusually useful line: a receiver could negotiate the ability to understand that format, while the sender remained free not to use it. The control exchange created permission, not an optimization result. Only running frames could show whether any headers disappeared—and only measurements could show what the waiting cost.

Server Needed a Third Challenge: RFC 3163

The Server Needed a Third Challenge: RFC 3163

The extra random value in RFC 3163 was not decorative. In its mutual-authentication mode, it addressed an asymmetry created by the order of the exchange: the client chose its own nonce only after it had already seen the server's first challenge. The fix was narrow, and so were the guarantees.

New Reverse Tree Existed Before the Old One Disappeared: RFC 3152

The New Reverse Tree Existed Before the Old One Disappeared: RFC 3152

In August 2001, the Internet moved IPv6 reverse naming from `IP6.INT` toward `IP6.ARPA` without pretending that a sentence in an RFC could move every resolver at once. RFC 3152 chose the infrastructure root, requested its delegation and aligned the hierarchy with address allocation. It also called for an orderly phase-out of the old name. That modest wording exposes how Internet migrations actually work: policy can change before delegations, software, caches, records and applications converge.

IPv6 Had to Wait for Authentication: RFC 3162

The access server had to authorize the session before it knew which Internet protocol the host would use. RFC 3162 let one RADIUS exchange carry both possibilities, then left the final applicability decision at the network edge.

Old Name Became a URN. It Still Did Not Resolve Itself: RFC 3151

The Old Name Became a URN. It Still Did Not Resolve Itself: RFC 3151

XML inherited public identifiers that could outlive a machine but could not enter every URI-only interface. RFC 3151 gave those strings a precise `urn:publicid:` transcription. The bridge preserved a name's visible structure and made normalized outputs comparable. It did not register the owner, choose a catalog, authenticate a target or prove that a parser received the intended bytes. The history is a lesson in the difference between carrying identity and completing resolution.

A Packet Could Hold Up Everyone Else: RFC 3150

On a very slow link, packet size also determines how long everyone sharing the interface must wait. RFC 3150 turned that interval into a design constraint rather than treating MTU as a matter of byte efficiency alone.

Call Agent Controlled the Features. The Mute Button Stayed Local: RFC 3149

The Call Agent Controlled the Features. The Mute Button Stayed Local: RFC 3149

MGCP placed call-control intelligence outside the phone, yet RFC 3149 refused to send every touch across the network. A numbered feature key could acquire its meaning from a remote Call Agent, and an XML display could become a separately addressed endpoint. But volume, the immediate choice between handset and speaker, and microphone mute remained local. The boundary reveals a durable design truth: central interpretation does not require central custody of every physical act.

One Path Could Yield Two Valid Capacity Numbers: RFC 3148

A single-flow bulk-transfer measurement looked like one number. RFC 3148 showed why transport choices could make that number method-dependent—and why the trace beside it mattered.

New Management Network Had to Cross the Old One: RFC 3147

The New Management Network Had to Cross the Old One: RFC 3147

A network migration is usually drawn as an arrow from old to new. RFC 3147 captured the harder topology hidden beneath that arrow: a newly IP-managed device could stand on the far side of a CLNS network that operations could not yet remove. The proposed bridge—GRE carried inside CLNP—was small. The history it preserved was larger: replacement begins as coexistence, and a path through yesterday's system is not evidence that tomorrow's system has taken control.