Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
CASE FILE
The EPP Extension Registry Records Coexistence, Not a Winner
Two extensions can solve much the same provisioning problem, use different XML namespaces and both deserve a place in the same public registry. That is not a defect in the catalogue. It is the governance fact the catalogue must preserve.
Story
AFRINIC's Six-Month Implementation Rule Has Two Start Dates
A policy clock is useful only when the institution and its community can identify the event that started it. AFRINIC's current Consolidated Policy Manual starts its six-month implementation expectation at the end of Last Call. AFRINIC's current public explanation starts it at…
IETF
Barry Leiba and the Capital Letters That Could Not Create Authority
A requirements scanner finds `MUST` in a specification and reports certainty. It has found a word, not yet an obligation. Barry Leiba’s RFC 8174 drew a clean boundary around the special vocabulary of BCP 14, but the boundary works in both directions: capitals activate defined…
IETF
The Price of Keeping Only the Latest Notification
Web Push can spare a returning device a backlog of obsolete updates. The difficult decision is not how to replace a waiting message, but which information the business can afford to leave behind.
CASE FILE
Every Outer Bundle Was Delivered. The Inner Bundle Still Had Not Been Received
Bundle-in-Bundle Encapsulation gives a delay-tolerant network two journeys to observe. The outer bundles can reach their configured endpoint one by one, each with a valid delivery report, while the bundle carried inside them never reaches the Bundle Protocol Agent. The new DTN…
CASE FILE
A DNS Filtering Notice Is a Chain of Three Decisions, Not One Explanation
A link that explains why a name was filtered looks like a simple act of transparency. By the time it reaches a user, however, a resolver, an application and the user have each made a different decision. The record must preserve all three.
IETF
Michelle Cotton and the Code Point That Arrived Before Its RFC
The awkward moment comes before a standard is finished: two implementations need the same numeric language to meet, but the registry would normally wait for publication. Michelle Cotton’s RFC 7120 turned that timing gap into a visible, expiring state. Its most important word is…
IETF
The Mount Point Changes What a Valid Configuration Means
A reusable network model carries its rules with it. It does not necessarily carry all the data against which those rules will be judged. YANG Schema Mount makes that distinction an operational responsibility.
CASE FILE
The Firewall Matched the Return Flow. The Source Still Was Not an Identity
A new SPRING working-group draft proposes a neat repair for a stubborn SRv6 middlebox problem: put the service SID in the outer source address so the two directions form the pair a stateful firewall expects. The packet may then pass. What the address proves, however, has changed.…
Story
LACNIC Says to Email the Bulk WHOIS Form. The Same Page Says Email Is Not Accepted
LACNIC’s public instructions give a Bulk WHOIS applicant two doors and no label for the threshold between them. The signed form is to be emailed first, the original is to be posted after approval, yet the same page ends by saying emailed forms are not accepted. The problem is not…
CASE FILE
HTTP 200 Is Not an EPP Registry Decision
Putting a registry protocol inside HTTPS creates two answers to one request: what happened to the web exchange, and what happened to the registry command. Governance fails when an operator stores only the easier answer.
IETF
The Meeting Operator Still Chooses What Reaches the Screen
SFrame can keep a conferencing relay out of the conversation's plaintext. It does not take away the relay's choice of which streams and quality layers to forward—or make the first usable picture arrive on time.
IETF
Erik Kline and the DHCP Code That Was Assigned but Not Vacant
A standards registry said 160; a live network said the number already had another life. The resulting collision did not make the registry irrelevant, nor did it make undocumented use legitimate. It showed something more operationally useful: an authoritative assignment can define…
CASE FILE
The Algorithm Name Matched. The Hash Receipt Did Not: RFC 9861
KangarooTwelve and TurboSHAKE give operators fast, extendable cryptographic output, but the label on a library call is only the beginning of the evidence. Reproduction depends on the exact function, byte stream, domain or customization input, output length and execution path that…
CASE FILE
Who Gets to Ask the User to Authenticate Again?
An API can reject a perfectly usable token because the user's authentication does not meet the needs of this particular request. RFC 9470 gives that refusal an interoperable language. It does not settle a more consequential question: who may turn a local risk decision into…
Story
RIPE Database Is Switching to OIDC. Maintainer Authority Does Not Move With the Session
RIPE NCC plans to replace a site-wide cookie with an OIDC session for interactive RIPE Database use. That can improve authentication, but the harder acceptance question begins after login: which `mntner` authorises this identity to change this entity, under which session regime…
IETF
James Gould and the Redaction Signal That Is Not Policy Proof
An empty place in an RDAP response can mean that no value exists, that a value was withheld, or that the question exposed a shape the server chose not to acknowledge. RFC 9537 gives one of those absences a machine-readable explanation. James Gould’s work on the specification…
CASE FILE
A Public Sponsor for a Private Namespace
An enterprise can need outside confirmation of an internal DNS arrangement without wanting to publish its internal directory. RFC 9704 offers a way to separate those disclosures. The difficult decisions concern what remains visible, how much authority one approval covers, and who…
CASE FILE
A Private Address Can Be a Familiar Address
A Wi-Fi identifier can be randomly chosen and remain recognizable for years. RFC 9724 makes that distinction explicit. The managerial question is how much continuity a service needs, within which boundary, and who decides when it ends.
Story
ARIN Closed the ROA Wording Fix. The Published Example Drops the Mask Interval
ARIN answered a precise operator complaint in five weeks and marked the documentation repair complete. That is the constructive part of the record. The harder question is why the live example no longer contains the length boundary that made the requested correction capable of…