History of the Internet

Permission That Survived Deletion: How IMAP Separated ACL Entries from Effective Rights

The Permission That Survived Deletion: How IMAP Separated ACL Entries from Effective Rights

The administrator removed Fred from the mailbox list. Fred could still write to it. Nothing supernatural had happened, and the server did not need to be broken: Fred might also belong to a group, or receive the same authority through `anyone`. In the access-control language that IMAP began standardising in 1997, deleting one visible rule was not the same operation as revoking the result. The protocol had to make that distinction observable without dictating every server’s local identity system.

Address That Had to Be Empty: How SMTP Stopped Errors from Mailing Errors

The Address That Had to Be Empty: How SMTP Stopped Errors from Mailing Errors

The most important address in SMTP is sometimes no address at all. A delivery failure has to travel back to the system responsible for the original message, yet a failure to deliver that failure must not produce another failure notice, and another after that. `MAIL FROM:<>` closes the recursive edge. The empty reverse-path does not erase accountability; it moves the last problem from an unbounded remote conversation into a bounded local duty for logs, queues and the postmaster.

Quarter-Hour Had Ended. Its Counters Had Not: RFC 1595

The Quarter-Hour Had Ended. Its Counters Had Not: RFC 1595

A performance window can be over without being final. RFC 1595 made that awkward truth visible in 1994: if ten severely errored seconds straddled a SONET/SDH quarter-hour boundary, the agent could later move seconds in the completed interval from error counters into unavailable time. Its successors offered a choice—revise the early answer or report ten seconds late. Either way, a counter needed a layer, an end, a threshold, a window and a read time before it could be treated as evidence.

Number That Stopped Naming Every Packet: How IPv4 Narrowed the Identification Field

The Number That Stopped Naming Every Packet: How IPv4 Narrowed the Identification Field

IPv4 put a 16-bit Identification value in every header so a receiver could reunite fragments of one datagram. Over time, the value was treated as a more general packet identity—even when fragmentation was impossible. Link speeds then outran the number space, implementations exposed activity through counters, and middleboxes learned to depend on meaning that reassembly did not need. RFC 6864 repaired the field by drawing a boundary: identity remains strict where fragments may exist; an atomic datagram's number means nothing.

Address That Recruited a Subnet: Why Routers Stopped Forwarding Directed Broadcasts

The Address That Recruited a Subnet: Why Routers Stopped Forwarding Directed Broadcasts

One IPv4 datagram could cross the Internet as an ordinary routed packet, reach the router responsible for a remote network and become a local broadcast there. With a victim's address forged as the source, that last-hop conversion could turn willing hosts on someone else's subnet into a reply engine. The durable repair was not to abolish broadcast. It was to stop treating remote fan-out as the router's automatic duty.

Area Learned the Route. The Backbone Had Not: RFC 1587

The Area Learned the Route. The Backbone Had Not: RFC 1587

Published on the Standards Track in March 1994, RFC 1587 described how one external route could be present, current and usable inside an OSPF area while the backbone had no advertisement for it. That was not necessarily delay or failure. In the Not-So-Stubby Area, it was the design. A leaf network could import selected outside knowledge without receiving the whole exterior table, but that knowledge had to be translated before it could travel farther.

Link That Borrowed Its Address: How Relative URLs Made Documents Movable

The Link That Borrowed Its Address: How Relative URLs Made Documents Movable

A short hyperlink is not a small absolute address. It is an instruction to borrow missing components from a base. That dependency let authors omit repeated schemes, hosts and path prefixes, and it let a collection of pages move while preserving its internal edges. The economy came with a boundary: the same relative text can legitimately resolve to different targets under different bases. Early Web standards therefore turned context into an algorithm—choose one base by precedence, inherit components, merge paths, remove complete dot segments and recompose one target.

Line Went Silent. The Route Stayed Reachable: RFC 1581

The Line Went Silent. The Route Stayed Reachable: RFC 1581

A quiet circuit used to look like missing evidence. Demand RIP made quietness the intended operating state. In February 1994, RFC 1581 and RFC 1582 described how routers on X.25 and ISDN could stop waking every peer with periodic updates, close idle calls, and keep the last accepted routes. The saving was real. So was the transfer of authority: once silence stopped expiring a route, another component had to say when the presumption of reachability had failed.

Sender Named the File. The Receiver Still Owned the Disk: RFC 1806

The Sender Named the File. The Receiver Still Owned the Disk: RFC 1806

An attachment can arrive with a name and an instruction to stay closed until requested. Neither statement proves that a file was created, that the name is safe, or that the recipient surrendered control of the machine. Content-Disposition became durable because it carried intent across the network without pretending that intent was a local effect.

School Got a Connection. Its Policy Still Had to Be Written: RFC 1578

The School Got a Connection. Its Policy Still Had to Be Written: RFC 1578

The circuit could come up before the institution was ready. In February 1994, RFC 1578 explained Internet access to primary and secondary schools by separating things that the verb “connect” made too easy to merge: a path, a set of usable applications, trained people, technical support, filtering, provider rules, school rules and evidence of what actually happened. The line changed what was possible. It did not decide what the school should permit or prove that its safeguards worked.

Provider Was Written into the Address. Then the Field Disappeared

The Provider Was Written into the Address. Then the Field Disappeared

IPv6 did not begin with a timeless answer to who should sit between a site and the global routing table. Its early documents tried several physical layouts for that authority—and left a remarkably frank account of who would pay when aggregation, portability and resilience pulled in different directions.

Three Telnet Options Made a Terminal. None Named the Session: RFC 1576

A standard had already designed one explicit switch into 3270 mode. Running systems chose three switches instead. By 1994, Terminal-Type, Binary and End of Record could make an ordinary Telnet connection carry a block-oriented IBM display stream, even though the client still could not name the logical unit behind the gateway or learn whether the host had processed the last block. RFC 1576 documented a practical victory without confusing it with a complete account of reality.

New Root Address Took Most Queries. The Old One Stayed: Net 39

The New Root Address Took Most Queries. The Old One Stayed: Net 39

For 38 days in 1995, one root-server installation answered through an experimental address inside Net 39 as well as through its familiar address. Well over half of roughly 400 million queries reached the new interface. The striking fact is not only that the unfamiliar address worked. The old one remained live because an experiment about compatibility was designed not to turn reluctant clients into a black hole.

RFC Said Every Host Must Answer. Running Code Said Otherwise: RFC 1788

The RFC Said Every Host Must Answer. Running Code Said Otherwise: RFC 1788

In 1995, an RFC said every host and router had to answer a new kind of name query. In 2013, another RFC recorded that the messages had never been widely implemented or deployed. Between those two sentences lies a useful history of how an Internet standard acquires—or fails to acquire—operational authority.

Filter Looked Readable. The Server Executed a Predicate: RFC 1558

The Filter Looked Readable. The Server Executed a Predicate: RFC 1558

In one short LDAP expression, `*` could ask whether an attribute existed, widen a value into a substring pattern, or survive as a literal character only if the writer escaped it. The line was made for people to read. The server did not read it as prose. RFC 1558 gave executable search structure a portable textual face—and made the boundary between characters, predicate and result impossible to ignore.

Octet That Changed Its Contract: From IPv4 Type of Service to DSCP and ECN

The Octet That Changed Its Contract: From IPv4 Type of Service to DSCP and ECN

The second octet of the IPv4 header did not move, but its contract did. What began as precedence and desired service qualities became a configurable per-hop behavior selector plus an explicit congestion signal—a history of compatibility managed by redefining bits in place.

Name Looked Complete. The Resolver Still Rewrote It: RFC 1535

The Name Looked Complete. The Resolver Still Rewrote It: RFC 1535

`UnivHost.University.EDU` looks like an address already supplied. To one 1993 resolver, it was only the beginning of a search. Before asking for the rooted name the user appeared to mean, the software could manufacture three longer candidates, cross from a locally managed suffix into an unrelated public branch, and stop at the first answer. The typed name had not changed on screen. Its administrative owner had.

Length That Outranked the Frame: Why IPv4 Counts Its Own Header

The Length That Outranked the Frame: Why IPv4 Counts Its Own Header

An IPv4 packet can sit inside a link-layer frame that is longer than the packet itself. The small field that resolves the ambiguity does more than count payload: it declares the complete IP datagram, header included, so the network layer keeps its own boundary when the enclosing medium adds bytes of its own.

Number IPv4 Could Not Freeze: How the Protocol Field Became a Live Registry

The Number IPv4 Could Not Freeze: How the Protocol Field Became a Live Registry

IPv4 devoted one octet to a deceptively simple question: what protocol should receive the payload next? The answer could not live in the packet format alone. It required a shared assignment system that could change while the eight bits on the wire stayed fixed.

Header Shrunk to One Octet. The Missing Bytes Moved into Shared State: RFC 1553

The Header Shrunk to One Octet. The Missing Bytes Moved into Shared State: RFC 1553

A packet crosses a slow link with a one-octet compression header. Its ordinary thirty-octet IPX header is absent. Nothing has been lost—if the receiver still holds exactly the right prior header in exactly the right slot. Let one earlier packet vanish, however, and the same economical octet may point into a different history.