Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
IETF
A Token Status Bit Is Not a Revocation Timeline
A relying party reads one compact value and declines a credential. The decision may be correct. Yet the bit alone cannot say when the underlying state changed, who authorised that change, when the list exposed it, which cached copy was consulted or why this application treated…
Story
APNIC’s Priority Survey Has Three Bases: 1,039, 1,038 and 1,037.
APNIC asked its community to divide exactly 100 points among eight strategic activities. The resulting chart looks unusually complete: every point is accounted for and no priority overwhelms the rest. The publication trail is less settled. Three official artifacts attach three…
History
The Configuration Row Vanished. RFC 2051 Kept the Session Alive
RFC 2051 turned an obscure APPC management model into a durable lesson about evidence: the record of what should exist can disappear while the record of what is already running remains true.
IETF
The Zone Was Still Answering. The Signing Key Was Already Gone
A correctly signed zone can outlive the private key that produced it. That interval is not recovery; it is a perishable option whose value depends on preserving old cryptographic state while proving, clock by clock, that a replacement chain has taken over.
Story
AFRINIC-38 Has a Named Safety Concern. A Hybrid Format Is Not a Risk Assessment.
A public message from an experienced Malawian operator does not prove that Cape Town is unsafe. It does something more precise: it puts a concrete delegate concern into AFRINIC-38’s record. AFRINIC’s own meeting guide already treats security as a location-selection input. The…
History
Karen Banks and the Gateway That Did Not Need to Stay Online
A message could wait on a local machine, travel during one brief telephone call and still reach an international public. Karen Banks’s work on GreenNet’s GnFido gateway shows why early access was a chain of queues, operators and partners—not a light that simply switched from…
IETF
A Signed Transaction Token Does Not Attest Every Claim
A service accepts a correctly signed Transaction Token and treats every nested value as independently verified by the signer. The signature is real, the token is intact, and the conclusion is still too broad. What the Transaction Token Service chose to carry is not the same…
History
The Registry Issued the Address. RFC 2050 Refused to Promise the Route
In 1996, an organisation could receive globally unique address space, appear in the public registry and still lack the one thing a casual reader might assume came with both: a route across the Internet. RFC 2050 made that limit explicit because the registry was only one actor in…
Story
RIPE Atlas Put Reconnects and Liveness Through One Event Processor. A Slow Backend Blocked Both.
A RIPE Atlas software probe could have working Internet access on 8 June and still be shut out of the measurement network after a routine disconnect. The public incident record explains why: reconnect work and controller-liveness evidence passed through the same event processor.…
History
Yvonne Marie Andrés and the Classroom That Had to Write Back
A school could own a computer, find a telephone line and deliver a message without yet creating a networked classroom. Yvonne Marie Andrés understood the missing test early: somewhere beyond the school, another class had to care enough to write back.
IETF
A TLS Flag Is Not a Feature-State Record
A monitor stores flag 8 as `true`. That compact fact does not say whether a client proposed a feature, a server announced it in a ticket, an acknowledgement was required, early data was involved, or the feature was ever exercised. The bit can be exact while the state inferred…
IETF
The Counter Rose. Which Bytes Did the ACL Actually See?
RFC 9899 gives operators a precise vocabulary for matching a binary pattern inside a packet. It does not collapse the distance between a valid YANG node, an installed ACE, the bytes present at a particular forwarding hook, a counter increment and the fate of an application…
Story
RIPE NCC’s Four Stale IPv6 Glue Records Are Now Three. Root Repair Was Never a Batch.
One of four old IPv6 glue mappings identified after RIPE NCC’s AuthDNS renumbering has aligned with the nameserver’s current address. The other three have not. That split result reveals the real unit of root-zone maintenance: one delegation, one authorised decision and one…
IETF
A QUIC Flow Record Is Not a Reconstructed Connection
Two values can sit in adjacent IPFIX columns and have completely different authority. A version number may have been read by a router from a visible long header. A stream ID may have been disclosed by an endpoint after removing packet protection. Standardising both field names…
Story
AFRINIC Calls 122 New Members a 4% Increase. The Baseline Is Missing.
AFRINIC’s statistics portal compresses five year-to-date counts into five whole-number growth labels. The figures look self-explanatory until one asks the ordinary questions behind any percentage: compared with what, at what time, under which inclusion rules, and rounded how? The…
History
Gihan Dias and the Two Names Sri Lanka Added to the Root
The smallest-looking part of a national network can expose its largest unfinished business. For Sri Lanka, two names in the DNS root showed that connecting a country and letting it recognise itself online were separate engineering tasks.
History
The Unknown Attachment Was Not Text: RFC 2049’s Minimum Promise
MIME conformance did not mean that a mail program understood every format. In 1996 it meant something smaller and more useful: decode the common transfer forms, preserve the distinction between text and opaque bytes, and retreat predictably when a type was unknown.
IETF
The Server Accepted the View. It Did Not Authorize the Write
An expired 2020 NETMOD proposal tried to let each NETCONF session or RESTCONF request select a versioned YANG view. The useful question is not whether a schema-set name was accepted, but which authority—and which evidence—survives after that acceptance.
History
Susan Estrada and the Network That Had to Account for Its Customers
An early Internet provider could prove that packets moved and still leave its customer unable to judge the service. Susan Estrada's work at CERFnet shows why commercial acceptance required another layer: reports, monitoring, support and a shared language for responsibility.
Story
LACNIC Counts 2.223 Billion BGP Messages. Its Family Table Totals 853 Million Updates
Two sums on LACNIC’s noisy-BGP study close perfectly. A third opens a 1.37-billion-count question. That does not make the research wrong; “messages” and “updates” may describe different stages. It does make the missing bridge between raw RIS files and the published tables the…