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.
IETF
Four Buckets Did Not Make a Standard
Revision 00 of YANG Next Agreement turns a crowded GitHub issue pool into four decision lanes. That is useful scope control. It is not, however, a vote, a language specification or evidence that any tool or network can safely run what the lanes contain.
History
The Tokens Diverged. The Endpoint Was Still Unproven: RFC 2023
RFC 2023 gave early IPv6-over-PPP links a precise local bargain: establish the data link, enter PPP’s network phase, negotiate different 32-bit tokens, and only then admit IPv6. Every receipt in that sequence stopped short of identity, ownership, reachability and delivery.
Number Resource Society
AS211513: What the public record can—and cannot—establish about EBL
AS211513: What the public record can—and cannot—establish about EBL 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…
ICANN
Anne-Marie Eklund Löwinder and the Key That Could Not Sign the Root
The physical key in Anne-Marie Eklund Löwinder’s custody helped open one compartment in a carefully divided ceremony. Its significance lay not in the power it gave her, but in the power the surrounding system withheld from everyone acting alone.
History
RFC 2022: The Roster Named the Receivers, but the Packet Still Needed a Circuit
RFC 2022 did not turn an IP multicast group into one ATM connection. It split the problem in two: MARS reported the endpoints believed to be listening, while each sender still had to build and repair the one-way circuit that might reach them. The roster was actionable control…
IETF
The Reply Came Back. It Did Not Prove the Path Was Measured: RFC 9779
RFC 9779 gives operators a standards-track way to measure loss and delay on SR-MPLS links and policies. Its most important operational lesson is less comfortable: a valid response can arrive by a route different from the traffic direction under examination. Protocol success, path…
IETF
A Path Can Parse and Still Prove Almost Nothing: The Boundary Proposed by ypath
The Internet-Draft `draft-jgc-netmod-yang-path-00` proposes one compact path notation for YANG schema nodes, data instances and filters. Its value is precision at the interface. Its danger begins when a valid string is mistaken for evidence that the named node exists, the…
Global Regional ISP
ROYA’s AS210837: The Evidence Chain Between Network Identity and Operation
ROYA’s AS210837: The Evidence Chain Between Network Identity and Operation 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…
IETF
The Schema Rejected the Sum. It Did Not Prove the Scope
A proposed YANG extension gives telemetry systems a disciplined reason to refuse an aggregation before it reaches a dashboard. That is a useful control. The harder question begins one step earlier: who proves that the scope written into the schema describes the network that…
History
The Catalogue Was Verified. The Training Material Could Still Be Gone: RFC 2007
In 1996, a volunteer directory tried to keep Internet training reusable by recording three different clocks: when a resource changed, when its catalogue entry changed, and when someone last checked it. RFC 2007 shows why those dates were useful—and why none was a promise about…
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.