Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
CASE FILE
The Route Reflector Distributed the Link. It Never Witnessed It: RFC 9815's Sparse-Peering Evidence Boundary
A route reflector can hold the newest authenticated account of a data-centre link and still know nothing directly about whether that link carries a packet. RFC 9815 makes this separation operationally useful: BGP can distribute a link-state graph over far fewer sessions than the…
CASE FILE
The Packet Had No SRH. It Could Still Target an SRv6 SID
An edge filter inspects an IPv6 packet, finds no Segment Routing Header and lets it pass. The packet still carries a locally instantiated SRv6 SID as its destination. The visible header test succeeded; the admission decision examined the wrong fact.
History
The MX Record Found a Gateway. It Did Not Prove the Fax Machine Existed: RFC 1486
A wildcard in the Domain Name System could announce that a mail gateway was willing to serve thousands of telephone numbers. It could not say whether any one of those numbers existed, answered, belonged to a fax machine or put a page into the intended person's hands. RFC 1486…
CASE FILE
The HSM Signed a Small Attribute Set. The Large CMS Content Was Bound Through One Digest: RFC 9814
An operator can truthfully say that a hardware security module produced an SLH-DSA signature while still leaving the most important question unanswered: which bytes did the module actually sign? RFC 9814 makes that question decisive for CMS. A multi-gigabyte archive may never…
History
The String Carried the Distinguished Name. It Did Not Become the Directory Entry: RFC 1485
The String Carried the Distinguished Name. It Did Not Become the Directory Entry: RFC 1485 intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
CASE FILE
The IP Address Stopped Naming the RADIUS Client. The Cleartext PSK Identity Took Over: RFC 9813
Two network access servers can stand behind one public address, while one mobile appliance can appear from several addresses in a week. RFC 9813 lets RADIUS/TLS distinguish those relationships with a PSK Identity. The useful part is not the new name. It is the sequence of checks…
History
The String Could Be Parsed Without Ambiguity. It Still Was Not the Directory Entry: RFC 1485
The String Could Be Parsed Without Ambiguity. It Still Was Not the Directory Entry: RFC 1485 intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
CASE FILE
The HTTP Request Returned 200. The Certificate Decision Was Still Inside: RFC 9811
A green transport result is tempting because it is immediate, familiar and easy to graph. RFC 9811 makes that result useful without letting it impersonate the certificate-management decision carried inside it. The distinction is small enough to fit in one response and important…
History
The Name Was Easy to Type. Its Identity Still Depended on the Directory Around It: RFC 1484
A person could say a short, natural name and let the directory fill in types, hierarchy and spelling. The convenience was real because the omitted context still existed: inside the local environment, current entries, matching rules and the user’s final choice.
History
The PDU Arrived. Its Protocol May Still Have Been Agreed Elsewhere: RFC 1483
RFC 1483 offered two ways to tell an ATM receiver what it had received. One put a protocol label in every AAL5 PDU. The other removed that label and made the virtual circuit carry its meaning. The bytes grew leaner, but the missing fact did not vanish; it moved into provisioning…
History
The IAB Endorsed CIDR. Four Different Actors Still Had to Make It Real: RFC 1481
In July 1993, the Internet Architecture Board used a sentence that sounds like a finish line: it “endorses the CIDR architecture and its implementation.” The sentence mattered. It still did not allocate an address block, add classless code to a router, install that code in a…
History
The Aggregate Had a Home AS. That Did Not Mean Every Announcement Came From Home: RFC 1482
RFC 1482 gave one aggregate a Home AS, then listed other ASs that would announce the same prefix to different neighbors. The table did not contradict itself. It recorded a chain of intended propagation in which origin, onward announcement, acceptance, installation and delivery…
History
The Name Existed in .US. That Did Not Mean the Zone Had Been Delegated: RFC 1480
Two names could appear equally real beneath `.US` in 1993. One might be a direct MX entry for a UUCP host; another might sit inside a branch whose manager ran its own name servers. The resolver made both names visible. RFC 1480 did not give them the same authority, network…
History
The Route Was Advertised. Five Decisions Still Controlled Its Fate: RFC 1476
A routing announcement is easy to mistake for a forwarding fact. RFC 1476 made that shortcut impossible. Its experimental Route Access Protocol put every received offer through a sequence of local decisions: filter it, transform its attributes, aggregate it, choose whether to…
History
The Table Said the Remote Bridge Would Accept It. That Was Still a Local Belief: RFC 1474
A management station finds a green `accept` value beside a remote PPP bridge. It looks like a statement about the other machine. RFC 1474 chose a more careful verb: the local entity *believes* the remote entity will accept that MAC type. The table offered a usable conclusion…
History
The Prototype Kept the Telnet Session Alive. It Had Omitted the Source Policy: RFC 1477
An early policy-routing experiment rerouted a live Telnet session after a gateway failure and again after a transit rule changed. That was valuable running-code evidence. The same report also recorded the functions its prototype did not implement, the lookup service it replaced…
History
The Compression Setting Changed. The Link Had to Restart Before It Mattered: RFC 1473
A manager changes one value on a live PPP interface and immediately reads the operational table. The console returns a compression method and a slot number. RFC 1473 treated those numbers with unusual honesty: until IPCP reached Opened, they were undefined. The write belonged to…
History
The Packet Carried a Route Identifier. It Did Not Carry a Route: RFC 1475
A field named “forward route identifier” sounds like a path folded into a packet. TP/IX proposed something more local and more interesting. Each router could lend the datagram a private handle for the next decision, then the next router could consume it and write another. The…
History
The Secret Row Was Marked Valid. No Peer Had Yet Authenticated: RFC 1472
In 1993 a network manager could inspect a PPP security table and find an identity/secret row marked `valid`. The word looked conclusive. RFC 1472 used it much more carefully: it meant that the configuration entry was currently usable, not that a peer had appeared, answered a…
History
The Charset Was Declared. The Byte Stream Still Had to Return to ASCII: RFC 1468
RFC 1468 gave Japanese Internet mail a portable name, `ISO-2022-JP`, but the name was only the entrance to the contract. Meaning still depended on a seven-bit stream changing character sets at exact escape sequences, returning to a safe state at every line boundary, surviving…