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
The Requirements Were Written. The Solution Was Not Proven
Revision 14 gives YANG versioning work a disciplined list of obligations: evolve modules without detonating dependency graphs, disclose compatibility, protect old clients, clarify retired nodes and explain migration. Its value is the questions it preserves. A requirements…
History
Mary Ann Horton and the Dial-Up Network That Had to Publish Its Own Map
Before an email address became a name, it could look like a set of directions. Every exclamation mark told a queued message which machine to visit next — and every omitted or stale hop could leave it stranded.
History
One Class A Subnet Could Defeat the Default: RFC 2036’s Compatibility Test
Opening unused Class A space in 1996 was not just a registry decision. It changed what every provider, customer domain and peer had to mean by a route: once a small component of an old classful parent appeared, inherited assumptions could send the rest of that parent away from an…
History
Jean Armour Polly and the Internet Connection That Still Needed a Librarian
In 1992, “going online” at a public library did not begin with a browser. It began with a desk computer, communications software, a modem, a telephone line — and somebody who could turn that fragile stack into a public service.
IETF
Two YANG Versions Can Coexist While the Effective Schema Still Diverges
An upgrade can look calm precisely when its most consequential uncertainty has moved downstream: `draft-ietf-netmod-yang2-00` lets an older importer and a YANG 2.0 dependency remain together, but that accommodation proves far less than a shared client view of the network.
IETF
The Router Remembered a Listener. The Receiver Saw Nothing: RFC 9777
MLDv2 gives an IPv6 router a disciplined account of multicast interest on one attached link. The danger begins when that local, aging account is promoted into proof that an authorized application still wants the traffic—or that the traffic arrived.
History
The Org Chart Was Not the Decision Log: RFC 2028 and the Map of IETF Responsibility
In 1996, RFC 2028 put the people and institutions of the IETF standards process into seven public pages. The map made responsibility easier to locate. It did not prove that any named role had acted, that a record was complete, or that the same allocation of authority still…
IETF
Two Published Copies Can Match Before Any Device Changes
Revision 03 of a NETMOD working-group draft proposes a careful handoff for normative YANG modules: keep them visibly provisional through IESG approval, finish the bytes under RFC Editor control, validate again, and only then let the RFC and IANA copies appear together. That…
History
Nancy Hafkin and the Network Before the Connection
Long before an always-on Internet line became ordinary across Africa, Nancy Hafkin’s programmes had to solve a harder problem: how to make information, institutions and people form a network when the connection itself was intermittent.
IETF
A Standards Action Can Authorize a Field. It Cannot Certify the Firewall: RFC 9778
RFC 9778 gives new IGMP values a high-visibility approval path. It also exposes a harder operational truth: a legitimate Type, Code, or extension flag can still be unknown to the security device deciding whether the packet is declined, inspected, or forwarded.
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…