History of the Internet

A Reply Could Outlive the Application That Asked: RFC 3340

In one of the Internet’s more candid protocol examples, an application asks a service a question, disconnects, and disappears. Another application later assumes the same endpoint name. The answer arrives to the successor, still carrying the first application’s transaction identifier. RFC 3340 did not confuse that correlation with continuity. Neither should we.

Same Instant Did Not Carry the Same Provenance: RFC 3339

The Same Instant Did Not Carry the Same Provenance: RFC 3339

Two timestamps can resolve to the same instant and still tell different stories about how that instant was expressed. RFC 3339 made that distinction explicit in 2002, then RFC 9557 changed part of it in 2024. The lesson is not merely how to print a date. It is that normalization can preserve chronology while erasing provenance, and that the standard revision used to interpret the original bytes belongs in the evidence record.

IPv4 Address Was Only a Local Handle: RFC 3338

The IPv4 Address Was Only a Local Handle: RFC 3338

The old application believed it had received an IPv4 address. On the wire, no such destination needed to exist. RFC 3338's Bump-in-the-API mechanism intercepted name and socket calls, assigned a temporary IPv4-shaped value from a private local pool, and used that value to recover the real IPv6 peer inside the host. The address was not a global identity. It was a handle whose meaning lived in a table, a scope and a moment.

A Class Identifier Was Not a Latency Guarantee: RFC 3337

The network had recognized the voice packet. That did not mean it would move first. RFC 3337 gave PPP over AAL2 a way to assign fragments from different traffic classes to separate Channel Identifiers, but it deliberately left the scheduler to the implementation and the service requirement. Classification created an opportunity to preempt. Only scheduling, capacity and the rest of the delivery chain could turn that opportunity into measured latency.

One Lost ATM Cell No Longer Had to Destroy the Whole Bundle: RFC 3336

A packet can fail because its bits were lost. It can also fail because an engineer chose to bind it to other packets before deciding whether any of them survived. RFC 3336, published in December 2002, addressed that second kind of failure. By carrying PPP through AAL2's Common Part Sublayer, it moved multiplexing beside segmentation and reassembly. The gain was not simply a shorter trailer. It was a smaller unit of waiting and a smaller unit of loss.

Meter Counted Only What the Policy Asked It to See: RFC 3334

The Meter Counted Only What the Policy Asked It to See: RFC 3334

An accounting record looks retrospective: a statement of what a customer used. RFC 3334 exposed the prior decision hidden inside it. Before a byte became a record, policy could decide which flows existed for accounting purposes, which attributes survived, how often the meter looked, how finely the collector grouped the result and how long anyone could inspect it. The record was evidence, but evidence with a configured field of view.

Routing Key Chose the Traffic. Network Appearance Named the SS7 Context: RFC 3332

The Routing Key Chose the Traffic. Network Appearance Named the SS7 Context: RFC 3332

M3UA moved MTP3-user messages across IP, but it did not give every identifier the same job. A Routing Key described which SS7 traffic an Application Server should receive; a Routing Context named that key; and Network Appearance supplied a locally coordinated view of which SS7 network a point code belonged to. One SCTP association could carry several such relationships, so “connected” was never a complete routing claim.

Gateway Turned the Route Into a Key: RFC 3332

The Gateway Turned the Route Into a Key: RFC 3332

RFC 3332 described a gateway that did more than carry signalling from one network to another. It terminated the SS7 network layer, inspected the coordinates of each message and used a configured Routing Key to decide which remote application should receive it. That key made distributed call control possible, but it also created a dangerous ambiguity: a rule that selects an application is not evidence that the SS7 destination can be reached.

SS7 Link Stayed at the Gateway. Its User Moved Across IP: RFC 3331

The SS7 Link Stayed at the Gateway. Its User Moved Across IP: RFC 3331

In M2UA, “user” did not mean the person making a call. It meant MTP3, the layer immediately above an SS7 signalling link. RFC 3331 kept the wire and MTP2 machinery at a gateway, then carried that upper boundary across SCTP to a remote controller. The resulting system could show a healthy IP association, an active application process and a failed physical link at the same time.

Address Looked Ordinary. The Packet Was Not Allowed to Behave Ordinarily: RFC 3330

The Address Looked Ordinary. The Packet Was Not Allowed to Behave Ordinarily: RFC 3330

Every IPv4 address fits into the same 32 bits. Its operational meaning does not. A destination can describe this host, one link, a private interior, an example, a laboratory or a public endpoint. RFC 3330 gathered those exceptions into one catalog—and exposed why the catalog could never be a timeless blacklist.

Stronger Lock Was Offered. The Attacker Removed It Before Selection: RFC 3329

The Stronger Lock Was Offered. The Attacker Removed It Before Selection: RFC 3329

The first security offer traveled before there was any agreed security to protect it. That circular problem made a one-line deletion powerful: erase the stronger mechanism, and two capable SIP peers might settle for less. RFC 3329 answered with a receipt delivered later, after protection had begun.

A REGISTER Was Temporary. Its Route Was for Later: RFC 3327

A registrar could know which contact to call without knowing every proxy that a future call had to cross. RFC 3327 attached an ordered Path to a contact binding so the home proxy could reuse those route references after REGISTER had finished. That Path prescribed later routing; it was not a trace of the packet path that had already occurred.

Registrar Knew the Contact. It Still Did Not Know How to Reach It: RFC 3327

The Registrar Knew the Contact. It Still Did Not Know How to Reach It: RFC 3327

A successful registration can answer the wrong question perfectly. SIP could tell a registrar which Contact belonged to a public address, yet still leave the home network unable to reproduce the route required to reach that Contact. RFC 3327 turned that missing route into state of its own.

Phone Stopped Ringing. The Protocol Had to Preserve Why: RFC 3326

The Phone Stopped Ringing. The Protocol Had to Preserve Why: RFC 3326

Two phones can stop ringing at the same instant for opposite reasons. One was abandoned; the other lost a race because the call was answered elsewhere. RFC 3326 gave SIP a place to preserve that difference after the visible action had become identical.

A CANCEL Carried the Cause. SIP Still Did the Canceling: RFC 3326

When one branch of a forked call answers, a proxy can stop the other branches and attach a short explanation. RFC 3326 made that explanation portable without letting it take over the protocol action.

User Chose a Preferred Identity. The Proxy Had to Remove the Choice: RFC 3325

The User Chose a Preferred Identity. The Proxy Had to Remove the Choice: RFC 3325

RFC 3325 gave the user a way to name the identity they preferred. Then it ordered the proxy to delete that preference before forwarding the message. The deletion was not cleanup; it was the line between a user-selected hint and a network assertion.

They Shared a Trust Domain. They Still Did Not Trust Each Other: RFC 3324

RFC 3324 drew one of its most important security boundaries with an apparently paradoxical example: two SIP nodes could belong to the same trust domain while one did not trust the other. Membership described a common rule set. Trust described a verified edge known to the receiver.

Caller Was Anonymous to the Recipient, Not to the Privacy Service: RFC 3323

The Caller Was Anonymous to the Recipient, Not to the Privacy Service: RFC 3323

RFC 3323 did not define anonymity as disappearance. It defined a route through which one party could stop seeing an identity only because another party was trusted to see, remove and route around it.

Anonymous to the Other Party, Reachable Inside the Dialog: RFC 3323

RFC 3323 did not make a SIP caller disappear. It asked a narrower question: which identity-bearing details should a recipient see, and what state must a service retain so the conversation can still work?

4.131-Second Call Setup Existed Only Inside the Model: RFC 3322

The 4.131-Second Call Setup Existed Only Inside the Model: RFC 3322

RFC 3322 produced a memorable total: 4,131 milliseconds of SIP/SDP signaling delay. The number looked precise because the assumptions were precise. It was not a stopwatch reading, and the document was unusually candid about the difference.