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
Steve Crocker and the Note That Stayed Provisional Long Enough to Build a Network
RFC 1 did not arrive after the network had proved itself. Steve Crocker dated it 7 April 1969, months before the first ARPANET node began service, and filled it with Host Software questions that still needed other sites to answer. Its authority lay not in pretending the design…
IETF
The Channel Ended. The Claims Kept Moving: RFC 9781 and the UCCS Source Break
A verifier can receive an authenticated, integrity-protected claims set and still lose the basis for that assurance one function call later. RFC 9781 makes this boundary unusually concrete: tag 601 identifies an unprotected CWT Claims Set whose protection belongs to a channel…
IETF
The Rule Chose the Sub-Interface. The Wire Still Owed Proof
A six-step precedence order can make VLAN classification deterministic without making forwarding observable. Revision 18 closes one ambiguity at the configuration boundary; operators still need counters, captures and path evidence to close the operational claim.
Global Cloud Services
AlmazCloud’s AS210328: The Operating Footprint Still Has to Be Shown
AlmazCloud’s AS210328: The Operating Footprint Still Has to Be Shown intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow.…
History
Butler Lampson and the Request That Had a Speaker Before It Had Permission
A request reaches a computer before any person does. It arrives on a wire, through a process, under a key or across a network connection. Butler Lampson and his colleagues made that apparently mundane arrival the start of a disciplined question: what, exactly, is entitled to…
History
The MIB Saw the Binding. It Did Not See the Journey: RFC 2006
RFC 2006 gave operators a disciplined view of Mobile IP’s moving parts. Its tables, counters and alert could expose what a management agent believed had happened, while leaving delivery, identity, authority and continuity outside the frame.
Global Cloud Services
AlmazCloud’s AS210328: The Operating Footprint Still Has to Be Shown
AlmazCloud’s AS210328: The Operating Footprint Still Has to Be Shown intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow.…
IETF
The Header Found the Verifier. It Did Not Earn the Decision: RFC 9782
An API gateway can read `application/eat+cwt`, select a handler and produce a clean routing log before anyone has established what the bytes contain. RFC 9782 makes that first step interoperable. Its importance lies equally in what it refuses to collapse: a media type can name a…
IETF
The Server Said “Immutable.” That Was Only the First Receipt
Revision 14 gives a client a machine-readable explanation for configuration the server will not let it override. The annotation is useful precisely because its authority is narrow: it describes one node instance, not an eternal property of the device or proof of the service it…
History
Sandy Fraser and the Call That Had to Exist Before the Bytes Could Move
The quietest moment in a network can carry the most responsibility. Before Datakit moved a user's bytes, Sandy Fraser's design asked the network to recognize a call, install a path and remember what its short channel label meant.
Number Resource Society
Datatokni ForoyaTele: What AS210417 Shows—and What It Does Not
Datatokni ForoyaTele: What AS210417 Shows—and What It Does Not intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
History
Danny Cohen and the Byte-Order War the Network Could Not Win
Four bytes can describe one number and still tell two incompatible stories. Danny Cohen saw that the useful question was not which machine deserved to prevail, but what every machine had to promise at the boundary.
History
The Tunnel Rebuilt the Header from What It Chose to Remember: RFC 2004
RFC 2004 did not put an IPv4 packet inside a second complete IPv4 envelope. It edited the packet’s own header for the tunnel journey, tucked the displaced fields into an eight- or twelve-octet forwarding slip, and made the exit responsible for putting selected facts back. The…
Global Institutional
DFINFRA and AS210860: What Would Prove an Operating Network?
DFINFRA and AS210860: What Would Prove an Operating Network? intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The Global…
Global Regional ISP
ROYA’s AS210837: What Would Prove a Network Is Still Operating?
ROYA’s AS210837: What Would Prove a Network Is Still Operating? intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
IETF
The Port Won the Election. Its Services Still Owed Receipts: RFC 9786
A single access interface can carry bridging, routed VPNs, IRB state and customer expectations at once. RFC 9786 deliberately elects that interface as one Port-Active unit. The gain is deterministic active/standby control; the liability is equally concentrated. A common…
IETF
The Interface Still Said Up While the Carrier Was Down
A quiet status light can be the most dangerous signal in a recovery room. Revision 19 of the IETF's common interface-extension draft deliberately permits an interface to remain reported as up while a short down timer is running beneath it. That is useful engineering, not…
History
Protocol 4 Is an Envelope Label, Not a Delivery Receipt: RFC 2003
A monitor sees an IPv4 packet from one router to another and reads `4` in the outer Protocol field. That observation is precise but small: it says another IPv4 datagram should follow. It does not name the original sender, validate the inner route or show that the letter inside…
Global Institutional
Where ISC’s Control Ends—and the Evidence of Recovery Begins
Where ISC’s Control Ends—and the Evidence of Recovery Begins intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The Global…
IETF
The Preference Won the Election. It Did Not Prove the Forwarder Was Ready: RFC 9785
An operator can make one EVPN Provider Edge router the obvious administrative favourite. RFC 9785 gives that intention a precise place in the DF election. What it does not give is a shortcut from “preferred” to “safe to carry traffic”. The standard opens a control surface…