Primary Domain
Infrastructure
Within the Primary Domain facet, 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 Channel Number Was Not the Circuit: RFC 1613 and X.25 over TCP
Two calls could arrive with the same twelve-bit channel number and still be different calls. RFC 1613 solved that 1994 X.25-over-TCP problem by refusing to make the enclosed number carry more identity than its local interface allowed. The TCP stream, the logical XOT interface and…
History
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…
CASE FILE
Removing a PyPI Collaborator Is Not Trusted-Publisher Revocation
Taking a name off a project’s collaborator list is a real access decision. It should not be described as a complete release-channel revocation when the publishing identity is governed on a separate surface.
History
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…
CASE FILE
A CODEOWNERS File Is Not a Review Receipt
A `CODEOWNERS` file can tell GitHub where review responsibility should be routed for a changed path. That is useful machinery. It is not a historical record of who was selected for a particular pull request, whether the eligible person received or completed a review, or whether…
History
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…
CASE FILE
An SPDX License Expression Is Not a Compliance Verdict
An SPDX expression can make a licensing statement easier to exchange, compare and correct. That is valuable precisely because the statement has limits. A syntax-valid string can identify information that an author declared, information someone found in a file, or a conclusion…
History
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…
CASE FILE
A Rust Trademark Permission Is Not a Rust Project Decision
A permission to use the Rust name or logo can be important: it tells a reader something constrained about how an identity claim may be presented. It cannot, by itself, make its holder part of the Rust Project, establish that a team reviewed code, turn a repository into an…
History
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…
Story
RIPE NCC’s Fibre Returned in Minutes. Access Recovery Took About Thirty Minutes
On 27 May, a supplier’s work in a manhole disconnected RIPE NCC’s fibre for only a couple of minutes. The connection came back and recovery was automatic. Yet RIPE NCC says it took about thirty minutes for everything to recover. The useful question is not whether automation…
History
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…
History
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…
History
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…
History
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…
History
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…
CASE FILE
A SLSA Attestation Is Evidence, Not the Acceptance Decision
A SLSA provenance statement can say something precise about one artifact and the build that produced it. That precision matters. But it does not choose which builders a verifier trusts, define a package’s expected source and parameters, declare a release complete, or decide what…
AFNOG
AfNOG’s Partial-Input Invitation Opens the Door Without Mapping the Process
AfNOG’s 2007 call welcomed suggestions and expressions of interest even without all requested proposal information, but the cited page did not explain beside that invitation how these inputs related to a complete proposal.
IETF
A QUIC STREAM Frame Carries Byte Ranges, Not Application Messages
A packet trace can show a complete STREAM frame while telling you nothing conclusive about whether an application request was complete, parsed, accepted, or committed.
IETF
An MPLS Alarm Can Suppress Client Noise Without Proving Server Failure
An AIS may suppress cascaded client alarms while its L-Flag remains clear, so alarm suppression is not proof of server failure. The server or intermediate node can send the indication downstream in affected client LSPs, but the receiving MEP still validates it and decides the…