Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
AFNOG
AfNOG’s Direct-Contact Field Lists Reachability Without Stating Its Handling Boundary
AfNOG’s 2007 call requested four published contact points without publishing an adjacent purpose, access or retention notice.
IETF
The Link Is a Snapshot: RFC 9910 Makes RIR Hierarchies Searchable
A single-result RDAP search link may become a lookup URL, but registry state can change before a client follows it. The link is therefore a time-bound snapshot of a registry view, not a timeless statement about a resource.
Leaders
Warren Kumari and the Design of DNS Failure You Can Survive
Warren Kumari’s standards work shows that resilient DNS is not the absence of failure. It is the disciplined design of limited continuity, explicit freshness, fallback and legible error signals.
History
Why IPv4 Options Carry a Copy Bit
Two fragments of the same IPv4 datagram can legitimately carry different option sets. That is not an accident of implementation. A single bit inside every option type tells a fragmenter whether the option must follow all fragments or remain only with the first.
History
The Link Was Open. Configuration Still Belonged to a Second Negotiator: RFC 1552
In one 1993 PPP design, reaching `Opened` could mean the network protocol was ready. In another, the very same state was only permission for a second negotiator to begin. RFC 1552 made that difference explicit—and showed why a state name is never a complete receipt.
AFNOG
AfNOG’s Requested-Time Field Leaves Its Relation to Programme Planning Unexplained
AfNOG’s 2007 call asked contributors how much time they wanted without explaining how that request would relate to programme planning.
IETF
The Server Writes the Blank Form: RFC 9908 Makes EST CSR Attributes Operational
An EST server can now send a partially filled CSR form: it fixes the values it requires while leaving explicit blanks for the client to complete.
IETF
The Review Is the Interface: RFC 9907 Turns YANG Documents into Operational Controls
A YANG module may parse cleanly yet still create incompatible operations when its specification leaves lifecycle, datastore, or registry authority ambiguous. RFC 9907 makes authoring and review discipline part of the control surface for management specifications.
CASE FILE
The Cipher Was Approved. Its Key Budget Still Had to Be Counted
An AEAD name in a configuration proves which construction was selected, not how much cryptographic authority remains under the live keys. Revision 13 of CFRG’s usage-limits draft makes the missing control plane visible: applications choose the risk target, deployments count the…
CASE FILE
The Interface Name Was Required Locally. It Had to Vanish Before Transmission
An IPv6 link-local address can be perfectly valid and still fail to identify a usable path. RFC 9844 supplies the missing local selector—a zone identifier—while imposing an equally important limit: the label has meaning only inside one node and must not become identity on the…
History
Why IPv4 Fragment Offsets Count in Eights
An IPv4 Fragment Offset is not a byte number. Its 13 bits count blocks of eight octets, turning a compact header field into a coordinate that can span the protocol's full datagram size. That economy comes with a precise cost: every fragment that is not last must end on an…
AFNOG
AfNOG’s Proposal-Type Field Names Formats Without Defining Their Evidence
AfNOG’s 2007 call named three proposal formats without publishing format-specific evidence fields.
IETF
Every Cell Says Stop: RFC 9906 Completes ECC-GOST’s DNSSEC Retirement
Every affected ECC-GOST registry cell now says **MUST NOT**: RFC 9906 closes both the production and validation lanes, unlike RFC 9905’s SHA-1 compatibility transition. The result is not merely a recommendation to stop signing; it is a coordinated retirement covering signing…
Leaders
Seyed Pouria Mousavizadeh Tehrani and the State Hidden Before IPv6’s First Reply
A first IPv6 exchange can expose network state that steady-state reachability leaves invisible.
AFNOG
AfNOG’s 200-Word Abstract Cap Leaves the Required Signal Unspecified
AfNOG’s 2007 call capped abstracts at 200 words without stating what those words had to establish.
History
When IPv4 Identification Stopped Identifying Every Datagram
IPv4 still carries a 16-bit field called Identification in every header. Yet the current standard says that field has no meaning in an atomic datagram. The apparent contradiction records a deliberate narrowing: an identifier created to reunite fragments no longer has to pretend…
IETF
Stop Signing, Keep Reading: RFC 9905 Makes SHA-1 Retirement Asymmetric
RFC 9905 changes the DNSSEC operating rule at the algorithm-row level: the affected SHA-1 algorithms MUST NOT be used to create new material, while validator implementations MUST continue to support validation during the remaining installed-base transition. The result is…
History
The Attachment Named Its Type. The Local Machine Chose the Command: RFC 1524
A multimedia message could say what it carried, but it could not legitimately appoint the program that would open it. RFC 1524 placed that decision in a local `mailcap` policy—a small indirection that made new formats portable across mail readers while exposing exactly where…
IETF
Four Cells, One Trust Chain: RFC 9904 Moves DNSSEC Algorithm Policy into the Registry
A DNSSEC algorithm number has four separately governed recommendation cells: validator implementation, signer implementation, validation use, and signing use. RFC 9904 changes where that guidance is maintained, not the recommendation status inherited on day one.
History
The Message Arrived Intact. Its Reading Order Still Had Three Owners: RFC 1556
A mixed Hebrew-and-English line could survive every mail relay with its characters unchanged and still arrive as a different sentence on two screens. RFC 1556 named the missing contract: transport had delivered the sequence, but somebody still had to own its order.