Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
History
The Group That Existed in a Message but Not on Every Server: How newgroup Separated Namespace Declaration from Local Adoption
A Netnews control article could carry a proposed group name across the network, yet the name became usable only where a serving agent chose to adopt it. The gap between declaration and local state was not a flaw around the protocol. It was the authority boundary that made a…
IETF
The IETF Side-Meeting Queue Allocates Rooms, Not Priority
The smallest public side-meeting room advertised for IETF 126 held about fifteen people. Its larger counterpart held forty. A requester could select one hour, ninety minutes or two hours; if a block did not appear, the room was unavailable. Those are unusually concrete facts for…
Story
RIPE NCC Put “Public Arguments” Inside Its Sponsorship Conflict Test
RIPE-866 is designed to protect neutrality from money and influence. Its hardest line does something broader: it treats litigation, arbitration, public argument and other conflict as neighbours, then carries the test from a disputing party to anyone associated with one. That may…
CASE FILE
The Library Named a Direct Modifier. It Did Not Calculate the Dependency Graph.
Module B inserts a container into Module A. Module C then inserts a leaf into B’s new container. RFC 10035 lets the server report B as a direct augmenter of A and C as a direct augmenter of B. It deliberately does not place C on A’s list. The new inventory exposes immediate…
History
The Header That Opened the Gate but Could Not Authenticate Its Approver: How Approved Separated Moderation from Authorship
One Usenet article could carry its author's identity and somebody else's authority to publish it. The `Approved` header made that second role portable across the network, but it did not prove the person behind the mailbox name. Moderation worked only when an injecting agent…
History
The Message That Chose Failure Over Cleartext
Two messages could wait in the same relay queue for the same domain and deserve different outcomes. One might travel without TLS when security negotiation failed. The other carried `REQUIRETLS`, turning non-delivery from an accident into the only permitted result.
ICANN
Before a Complaint Becomes a Board Case, What Can ICANN's Ombuds Office Actually Change?
ICANN's Ombuds Office can change the route, information and voluntary resolution around a fairness problem—but contact is not formal notice and does not create a binding remedy.
IETF
Ten Segments Before the Network Answers: TCP's Initial Window Bet
A new TCP sender once waited for the path to reveal itself three or four segments at a time. RFC 6928 permitted a first flight of ten. That shortened many small transfers, but it also concentrated more traffic in the only moment when the sender had almost no evidence about the…
Story
The Estate Cannot Route Itself
A liquidator can inventory equipment, contracts and claims. That does not make an Internet number delegation an ordinary asset that moves merely because a sale schedule says so. Insolvency creates two records that must meet: the court-supervised estate and LACNIC's…
CASE FILE
The Charter Opened a Work Queue. It Did Not Migrate a Certificate.
The LAMPS charter now contemplates an unsigned X.509 certificate as a slimmer way to carry trust-anchor subject information. Removing a self-signature can save expensive bytes. It does not make the container trusted, choose a post-quantum algorithm or move one relying party.…
History
The Revision That Could Not Recall Its Predecessor: How Supersedes Separated Replacement from Erasure
A corrected Usenet article could reach every willing server even when the article it replaced did not disappear from all of them. `Supersedes` joined those two intentions in one publication, but the protocol kept their outcomes apart: the revision was a new article, while…
IETF
One Cohort Match Does Not Clear IETF’s 2025 Survey
The IETF Administration LLC’s fifth annual community survey is a substantial public record: 52 pages of method, counts, question-level results and caveats drawn from 1,480 valid responses. Its most consequential weakness fits inside two passages. The report first accepts that…
History
The Reply That Did Not Have to Return to the Room: How Followup-To Separated Audience from Destination
A Usenet article could be read in several newsgroups while asking that the next response appear somewhere else. `Followup-To` did not move the original or close its audience. It gave a posting agent a default for the new act of replying—and left the next poster able to choose…
History
The Exit That Was Also a Delete: Why IMAP Needed UNSELECT
A mail client wanted to release one open mailbox. The most obvious command would also erase every message already marked for deletion. IMAP's later `UNSELECT` extension separated an ordinary state transition from an irreversible act.
CASE FILE
The Policy Named a Partition. It Did Not Reserve the Resources.
Two candidate paths can point to the same endpoint while carrying different Network Resource Partition identifiers. One 32-bit value changes which underlay resources the headend is meant to invoke. The BGP field can state that association; it cannot create the resources, install…
Story
LACNIC Cut Its Recovery Window to Three Months in 2015. One Procedure Page Still Says Six
LACNIC has a clean public record of shortening its resource-recovery publication period from six months to three. It also has a current operational page and policy manual that use the shorter clock. The unresolved problem is simpler and more practical: another public procedure…
History
The Date That Could Not Reserve Disk: How Expires Let Usenet Separate Relevance from Retention
An article can carry a precise date and still make no promise about how long it will remain available. Usenet's `Expires` field let a poster say when a notice would stop being useful. The disks, deletion rules and archive exceptions remained under each serving site's control. The…
History
The Session Ticket Could Not Remember the Protocol
A resumed TLS connection could reuse evidence from an earlier cryptographic session, but it could not inherit the grammar spoken over the old wire. ALPN made application-protocol choice a fresh, bounded decision: the client named what it could accept, the server chose one common…
IETF
An IETF CCG Seat Is Not Title to IANA
On 11 August 2026, the Internet Architecture Board reappointed Tim Wicinski to the Community Coordination Group. He occupies one of three IETF-selected positions in a nine-person body drawn equally from the names, numbers and protocol-parameters communities. The CCG advises the…
CASE FILE
Fourteen ACKs Did Not Prove a Window of Twenty-Four
An application sends ten segments, pauses, then supplies four more. Every segment is acknowledged. A naive slow-start counter can call the resulting congestion window twenty-four, although the path has never carried more than ten in one round trip. The IESG has now approved a…