Primary Domain
Internet Infrastructure
Within the Primary Domain facet, Internet Infrastructure intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
History
The Cable Was Real. The IP and OSI Maps Could Disagree: RFC 1609
A router can sit in one rack and play different parts in different networks. In 1994, RFC 1609 tried to give those parts separate entries in an X.500 directory, all pointing back to the same equipment. The proposal's useful question still bites: when an operator asks for a…
History
MD5 Came with the Answers in the Back
In April 1992, Ronald Rivest published an algorithm for turning a message of any length into a 128-bit digest. He also packed the Internet memo with C source code, a test driver and the answers that driver should print. A programmer could read the recipe, compile the example and…
History
Please Find a Person Attached
Email had learned to carry pictures, sound and files. On 1 April 1993, two engineers offered it a new attachment: a human being. Their RFC specified the size of the box, the resolution of the scan and the unhappy fate of a laboratory rat at a full disk. The joke worked because…
History
The Mail Connection Broke. The Server Asked for Byte 6,135: RFC 1845
The broken connection in RFC 1845's 1995 example did not force its client to send the whole message again. The receiving SMTP server answered the retry with a number: `355 6135`. It had kept the first 6,135 octets of message data. The client could resume with the rest, provided…
History
FTP Had Six Slots. The Future Internet Brought More Luggage.
A file could be ready to move while its address could not fit into the command that told FTP where to send it. The old `PORT` command carried four decimal octets for an IPv4 host and two for a TCP port. In 1993, with several next-generation Internet designs on the table, David…
History
One Envelope Saved the Mailing List. The Route Slips Went in the Bin.
Before an inbox could be called a fire hose, busy mailing lists had a simpler problem: sending every submission to every subscriber cost work and headers. Moderators began packing many messages into one digest. RFC 1153 wrote down the house rules in 1990, including a brisk…
History
The Email Was Still in Flight. X.25 Reached for the Hang-Up Switch.
A telephone call has a tidy ending: say goodbye, put down the receiver. A computer circuit can be less polite. X.25 could discard data still travelling when its virtual circuit was cleared. In 1989, RFC 1090 put SMTP directly on that circuit and discovered that the final act of…
History
NTP Stopped Counting Missed Calls and Checked the Line
Network Time Protocol had a practical way to decide whether a distant clock peer was still answering: remember the replies to the last eight exchanges. In a 1990 experiment, Jon Crowcroft and Julian Onions put NTP over OSI Remote Operations and a connection-oriented service such…
History
The Character Was There. The Screen Was Told Not to Invent It: RFC 1502
An international email could arrive intact and still lie to its reader. In 1993, RFC 1502 gave X.400 GeneralText a blunt rule for that gap: if a terminal could not show a character, it had to show that something was missing. Printing a plausible local character from the same byte…
History
Every Keystroke Bought a Packet. The Form Fought Back.
Type one character, send a packet carrying TCP/IP headers, wait for the host to echo another packet back. That was the network conversation the authors of RFC 1043 wanted to quiet. Their 1988 Data Entry Terminal option for TELNET let a remote application build a full-screen form…
History
A Tilde Gave Chinese Text a Seven-Bit Side Door
Some old mail paths had room for seven bits per character; Chinese text lived on machines with incompatible eight-bit habits. HZ answered with a bit of punctuation that did more work than its size suggested. In the format published as RFC 1843 in 1995, a tilde could announce a…
History
Type a Host Name. The Manager Builds a Read-Only Identity: RFC 1503
In 1993, an SNMPv2 manager could make a user’s life easier by doing a surprising amount of administration behind one typed name. RFC 1503 proposed a resolver that could turn an unfamiliar host into temporary parties, a context and an access-control entry. The keyboard shortcut…
History
The Mac File Had Two Forks. Email Brought One Envelope.
In 1994, sending a Macintosh file by email could be like mailing a photograph with its frame, the label on the back, and a tiny instruction manual glued to the glass. A recipient on another computer might want the photograph alone. A Mac recipient wanted the rest of the file too.…
History
The IAB Wanted a DNS Deadline. DISA Sent It to Study
The reply arrived before the requested date. The decision did not arrive with it. In 1992, the Internet Architecture Board pressed the Defense Information Systems Agency to move lingering host-table users toward DNS; DISA promised to examine the technical and economic costs. RFC…
History
SMTP Told the Pager “OK.” Which OK?
In 1994, the Internet was asked to page people. Email already knew how to say “250 OK,” but a pager made that little green light dangerously vague. Was the message sitting in a mail queue, accepted by a radio network, or actually sent over the air? Marshall Rose’s RFC 1703 turned…
History
TCP Held the Second Record Hostage
The database asked for four records. One was late, another had already arrived, and the user would happily have read the second one first. TCP kept it waiting anyway. In 1994, three researchers proposed telling transport exactly which records must precede which others. The IESG…
History
The Packet Had an IP Address. X.25 Wanted Another Number: RFC 1461
An IP packet could carry a perfectly good destination and still leave an X.25 router unable to place the call. In May 1993, RFC 1461 put that missing step on the management console: find the peer's X.121 number, or record exactly where the lookup failed.
History
The Internet's New Media Types Took a Number and Waited Two Weeks
In 1994, naming a new kind of Internet content involved a public mailing list, a two-week wait and a trip to IANA. The form looked modest: type, subtype, parameters, encoding, known risks and a contact. Yet the queue solved a large coordination problem. A common name could follow…
History
Five Reviews, Then the Paper Vanished: RFC 1438's Process Joke
On 1 April 1993, an Informational RFC invented a standards track for documents so empty that reviewers approved them by falling asleep. The punchline was not the nap. It was a committee process that could bestow authority on a result with no useful content.
Academics
The BGP generator that best fit one collector missed 35–41% elsewhere
Shadi Motaali tested 13 generators from RIPE RIS RRC4 against RRC5. The one most faithful to its home collector missed up to 41% of anomalies at the next view.