Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
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…
History
The Border That Could Not Live in a Header: How Distribution Scoped Usenet Without Making It Private
Usenet could carry a request for an article to remain local, national or organizational. It could not carry the border itself. That boundary existed in the agreements between relays, the names each site recognized and the gateways an operator controlled. `Distribution` was…
History
The Second Date That Refused to Replace the First: How Injection-Date Separated Writing from Entry
A Netnews article could be finished on Monday, wait on a disconnected machine, and enter the network on Friday. One clock described when the writer declared the text ready; another was needed to decide whether the network was seeing fresh traffic or an old duplicate. The design…
Story
ARIN-2026-4 Calls Two Clauses Redundant. The Replacement Needs a Scope Map
ARIN’s consolidation draft says two IPv6 clauses can be retired without meaningful change. That may be right. But the old and proposed sentences do not name the same subjects, duties or qualifiers, so redundancy should be demonstrated proposition by proposition while the text is…
CASE FILE
The Proxy Opened a Port. It Did Not Authorize the Internet.
The IESG has approved an HTTP extension that lets one proxy-bound UDP socket serve many remote peers. Its operational lesson is sharper than the feature: advertising a reachable address allocates a path, while Context IDs, tuple policy and observed forwarding decide who may use…
IETF
A Green Box Is Not Evidence When It Answers the Wrong Question
An assessment table can look more settled than the decision behind it. On 14 August 2026, the IETF Administration LLC invited community input on preliminary venue reports for Milan and Montevideo. Both reports deliberately carried no recommendation. Yet one green square in the…
History
The Timeout That Could Speak Only After Fragment Zero
The receiver had pieces of the datagram, an identity for the unfinished whole and a timer measuring how long its memory would remain committed. What it did not have was the beginning. When the timer expired, IPv4 required the state to disappear; whether the failure could speak…
CASE FILE
The Signature Was Valid. The Token Was Wrong.
The IESG has approved a replacement for the JWT security playbook. Its hardest rule is also its most practical: a receiver must prove not only that a token is authentic, but that this exact kind of token is entitled to cross this exact application boundary.
History
The Number That Meant Somewhere, Not Something: How Xref Made Usenet Location Local
One Usenet article could sit at a different number in every group and on every server. Xref turned that apparent contradiction into useful metadata: keep the article's identity global, but let each server publish its own filing coordinates.
Story
APNIC’s prop-167 Status Needs Two Rows
APNIC did publish the hourly directory statistics its community asked to see. The live files make that success unusually easy to verify. They also make a second fact harder to ignore: `prop-167-v002` asked for another output, and the Executive Council gave it a different…
IETF
An IETF Remote Room Is an Access Point, Not a Constituency
A room can improve access without acquiring a voice of its own. That is the institutional line exposed by the IETF 125 Remote Rooms experiment in Tokyo. The privately operated hub brought entities into shared rooms, supplied a collective audio-and-video connection and restored…
CASE FILE
The Path Kept Its ID. Its Instructions Changed.
The IESG has approved a compact identifier for segment lists carried in BGP SR Policy. The number can simplify telemetry and cross-system configuration, but it stays meaningful only inside its Candidate Path—and it can remain unchanged while the actual SID sequence changes.