Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
History
Six Control Codes Became Letters. The Label Had to Tell Readers Which: RFC 1456
The octet `0x02` could arrive unchanged at two machines and assert two different things. An ASCII-oriented program would meet a control code. A VISCII decoder would render a Vietnamese capital letter. In RFC 1456, the disagreement was not corruption. It was the price of fitting a…
History
The Packet Asked for the Safest Route. The Network Promised Nothing: RFC 1455
A packet reaches a router carrying four bits set to one. They do not lock its contents, certify the next hop or bind the operator to an outcome. In RFC 1455, they expressed something narrower and more revealing: a request that the network prefer the physical route it considered…
History
The Party Had a Name. The Triple Still Had to Permit the Operation: RFC 1447
A received SNMPv2 message could survive decoding, identify a known sender and still stop before a single managed entity was touched. The 1993 Party MIB put four separate questions in its path: who was asking, which party was being asked, which context held the resources, and what…
IETF
Juliusz Chroboczek and the Babel Metric That Was Not a Global Score
A route metric can be indispensable without being universal. RFC 8966 lets Babel nodes compute link costs and route metrics as local policy, then insists on a small common discipline: the resulting metric must be strictly monotonic if the protocol is to avoid persistent loops.…
Story
APNIC’s Resource Quality Check Is Not an Address Attribute
APNIC made a careful change in 2019: “assurance” became “check”. The distinction matters because a registry can observe routes, filters and reputation signals, but it cannot make thousands of other networks carry the result forward.
History
The Agent Claimed the Group. The Object Still Had to Answer: RFC 1444
A capability card can shorten an inspection. It cannot become the inspection. In 1993, RFC 1444 gave SNMPv2 authors a disciplined way to name entity groups, state the minimum required for conformance and describe what a product release claimed to implement. Yet its hardest…
History
The Network Had Bandwidth. The Application Was Still Starving: RFC 1453
A fast network can be perfectly real and completely irrelevant to the frozen face on a conference screen. In 1993, RFC 1453 located that contradiction inside the machine: capacity had reached the link, perhaps even the transport, while buffers, operating-system paths and…
Global Datacenter Trends
Flex Has a $4.4bn Bridge for a $4.4bn Deal, Not SpinCo’s Final Balance Sheet
The acquisition price, the temporary funding ceiling and the planned separation sit on three different clocks. Investors still need the permanent financing and allocation record that connects them.
IETF
Rohan Mahy and the Certificate Purpose That Did Not Deliver an Instant Message
An IM certificate can say that a key is meant for an instant-messaging identity. That narrower purpose is useful security design. It does not say that an application submitted a message, that a service accepted it, or that any person received and read it.
IETF
Neil Jenkins and the StateChange That Did Not Audit a Mailbox
A JMAP client that sees a new state string has learned something important: its local view may no longer match the server. That is a signal to synchronize. It is not, by itself, a record of which message changed, which mailbox moved, which principal made a request, which policy…
IETF
A Signature Is Not Proof of the Other Key: RFC 9883 and Private-Key Possession Statements
A second certificate request can be validly signed by an already certified signature key, yet that signature is only an assertion—not technical proof—that the requester controls the different private key behind the requested key-establishment certificate. RFC 9883 defines how a…
History
The Packet That Had to Answer Back: TCP's Challenge ACK Repair
TCP once treated a reset that landed anywhere inside the receive window as sufficiently believable to tear down a connection. RFC 5961 replaced that destructive shortcut with a narrower rule: exact sequence alignment could act immediately; merely plausible input had to survive a…
History
The ACK That Could Not Say Which Packet Arrived: Karn's Retransmission Ambiguity Rule
The same sequence range crossed the network twice. The acknowledgment that returned proved the bytes had arrived, but not which transmission had earned the reply. Karn's rule turned that uncertainty into a discipline: delivery evidence could advance while the round-trip estimator…
Number Resource Society
A Ghostbusters Record Is Not an Incident Command Roster
An RPKI relying party can validate every byte of a Ghostbusters Record and still not know whether anyone is watching the listed channel when action is needed. The signed entity solves discovery of minimal CA-maintainer contact data; operational accountability begins where that…
IETF
The Signature Algorithm Is Not the Signed Byte Sequence: RFC 9882 and ML-DSA in CMS
Two CMS systems choose ML-DSA-65 for identical content, yet verification fails when one signs a final implicit-tag representation and the other verifies the complete DER SignedAttrs value with its explicit SET OF tag. The algorithm is the same; the signed byte domain is not.
Story
AFRINIC Deemed Two NRO NC/ASO AC Candidates Elected Unopposed. Its Linked 2026 Rulebook Now Returns 404
AFRINIC’s final 2026 candidate slate said Stephen Musa Honlue and Nitin Kelawon Sookun would be deemed elected unopposed to the NRO NC/ASO AC, while voting would still decide the duration of their terms. The Election Guidelines page linked as the basis for that procedure returned…
Number Resource Society
A Trust Anchor Rollover Needs an Acceptance Ledger
An RPKI trust-anchor operator can publish a successor key without making every relying party ready to use it. The transition is a sequence of verified observations, not a launch date: a defensible record must show what was announced, what remained stable, which validators crossed…
History
The Packet That Waited for Its Predecessor: Nagle's Small-Segment Rule
A one-byte write did not need a universal delay timer. It needed a rule about whether the connection already had data in flight. Nagle's answer made acknowledgment state—not the wall clock—the gate for another short TCP segment.
IETF
The Algorithm Name Is Not the Certificate Profile: RFC 9881 and ML-DSA in PKIX
The Algorithm Name Is Not the Certificate Profile: RFC 9881 and ML-DSA in PKIX intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
AFNOG
AfNOG Publishes Mailing-List Rules, Not the Moderation Procedure Behind Them
AfNOG’s mailing-list page sets clear expectations for a technical community: keep discussion operational, avoid disrespect, and do not use the list for blatant product marketing. The published page establishes the rules. It does not explain the procedure used when a post is…