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 Packet Got a New Lifetime at Every Border: RFC 1326
A tunnel is often described as a clean bargain: put one protocol inside another, cross a network that understands the outer wrapper, then recover the original packet at the exit. RFC 1326 asked what happens when two such bargains face each other and routing sends the packet back…
History
The Analysis Could Not Stand In for the Test Network: RFC 1245 and RFC 1246
In July 1991, OSPF arrived with more than a protocol specification. Its supporting case was deliberately divided into an analysis and an experience report. That division preserved a distinction Internet engineering still needs: a model can bound expected behaviour, but only…
History
The NIC Owned the Question. It Did Not Own the Network: RFC 1302
A help desk can keep faith with a user without pretending to control every system behind the problem. RFC 1302 made that distinction unusually clear in 1992. A Network Information Center was expected to take responsibility for an inquiry until it was resolved in some way. Yet…
Global Institutional
ARTEMIS and the minute between a BGP alert and a safe response
ARTEMIS compares public BGP observations with an operator’s own model of permitted routing to classify suspicious announcements and respond faster. Its history exposes the harder problem: when visibility is incomplete and a counter-announcement can itself cause harm, speed helps…
History
The MIB Had to Redraw Who Could Change AppleTalk: RFC 1243 and RFC 1742
A management model is also a map of responsibility. In 1991, the first AppleTalk MIB let an SNMP manager write route fields and zone mappings while reporting how port settings had been obtained. Four years later, its replacement moved several of those lines. The revision matters…
History
The Box Dropped No Frames. It Had Not Passed the Other Tests: RFC 1242
A clean throughput trial is seductive because it ends in one number. RFC 1242 gave that number a strict meaning, then surrounded it with other terms that refused to disappear. Zero loss at one offered rate did not answer latency, burst tolerance, overload, restart, filtering or…
History
The Counter Was Total. Subscription Discards Were Somewhere Else: RFC 1304
A number labelled total looks like the end of an investigation. In RFC 1304, it was the beginning of one. The 1992 MIB could count SIP packets discarded for protocol or bit errors, list other address-related failures and remember the latest disagreement of each syntactic type.…
History
The Tunnel Carried the Packet. The Error Lost the Question: RFC 1241
A tunnel can look transparent in the forward direction and become opaque the moment something fails. RFC 1241 drew that asymmetry with unusual precision. Its outer packet could carry an untouched IP datagram through a separate routing space. But an ICMP error from inside that…
History
The MIB Arc Changed. Vendors Still Had to Revise: RFC 1239
Nothing in a management console announces that a number has become architecture. RFC 1239 did. Five MIBs kept describing familiar interfaces, yet their entity identifiers moved from an experimental branch to standard branches. The standards record changed in two pages; every…
History
The Master Said Accepted. The Applications Had Not Reported an Outcome: RFC 1301
Twelve small verdicts travelled inside every Multicast Transport Protocol packet. One could say accepted, another pending, a third rejected. They looked like receipts, but they were not votes from twelve receivers. RFC 1301 gave one master the right to set those values after…
History
The Agent Spoke with One Voice. The Subtree Had Another Owner: RFC 1227
To a management station, an SNMP agent looked like one speaker. RFC 1227 placed a switchboard behind that voice: local processes registered branches of the MIB, priorities chose which process answered, and a broader branch could hide a narrower one. The reply was real, but its…
History
The Trap Carried 0.0.0.0. The Envelope Named the Agent: RFC 1298
An SNMP trap crossed an IPX network with four zeroes where its agent address might have been expected. That was not missing data by accident. RFC 1298 deliberately emptied the Trap-PDU field and told the receiving manager to take the source from the transport layer instead. The…
History
The Radio Frame Entered IP. Its Physical Edges Did Not: RFC 1226
A packet can cross a boundary without carrying every trace of the medium it came from. RFC 1226 put an AX.25 frame inside one IP datagram, discarded the HDLC marks that had framed it on a serial link, and retained the checksum. That choice made a useful tunnel format—and a…
History
The Host Said Down Before the Controller Had Finished: RFC 1307
A transport provider asked to release an expensive switched link. Its local control layer answered that the link was down, yet the external controller had not necessarily finished—or even recognised—the teardown transaction. RFC 1307 made that apparent contradiction part of a…
History
The Alarm Flood Stopped Itself. The Silence Still Needed a Ledger: RFC 1224
A quiet management console can mean that nothing is wrong. It can also mean that the alarm path deliberately shut itself down. RFC 1224 made that second possibility explicit: cap an agent's alert rate with a sliding-window pin, then keep a separate numbered log so silence did not…
CASE FILE
The Rule Did Not Change. What It Matched Did: RFC 9899
An ACL can remain byte-for-byte unchanged while the named set behind it gains or loses members. RFC 9899 makes that separation useful for operations—and impossible to ignore in an audit.
History
The Desktop Showed One Directory. No Server Held the Whole Thing: RFC 1309
The promise looked almost magical in 1992. A person at one workstation could search what appeared to be a single worldwide directory, even though no central machine owned the complete collection. RFC 1309 explained the machinery behind that appearance: user agents, system agents…
History
The Protocol Asked for Multicast. The Network Sent a List of Copies: RFC 1223
HYPERchannel could carry the routing protocols of an imagined broadcast LAN, but it could not broadcast. RFC 1223 bridged that mismatch with a more revealing mechanism: keep a list of intended listeners, make one copy for each, and space the transmissions so the imitation did not…
CASE FILE
The Router Could Reach the Address. It Still Could Not Name the Subscriber: RFC 9898
An IPv6 neighbor-cache entry is executable forwarding state. It can tell a router where to send the next frame and whether recent reachability has been confirmed. It cannot, by itself, tell an investigator who was entitled to use the address.
History
One Router Held Two Domains. It Still Needed Two Owners: RFC 1222
The cheaper router in RFC 1222 was not supposed to abolish a boundary. It was supposed to house both sides of it. One routing process would speak for a service subscriber, another for the NSFNET Backbone, and an exterior protocol would still cross between them—even if the…