Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
History
The Layer Was Not the Module: How RFC 817 Cut Across the Stack
One typed character could make three answers leave a server: a TCP acknowledgement, a window update and a Telnet echo. The protocol layers were each behaving correctly. The implementation was still wasting packets. RFC 817 used that small inefficiency to make a larger…
Story
RIPE NCC Needed 394 Supporters Before a Member Resolution Could Reach the Agenda
The number 394 was not a vote result. It was the price of admission to the vote: a cycle-specific calculation deciding whether a member-authored subject and its verbatim resolution would enter the General Meeting agenda. The rule has a sound institutional purpose. The public…
Story
LACNIC Published a 98% Outreach Score. The Response Count Is Missing
LACNIC says more than 330 organizations attended its 2025 member gatherings and that 98% of the feedback it received fell in the highest satisfaction levels. Both statements may be accurate. The public post does not disclose the number of responses, so the percentage cannot be…
IETF
Mark Nottingham and the User Agent That Could Not Speak for Every User
The browser can deny a service direct access to a person's machine, carry a narrow preference and make another implementation possible. Those powers make the user agent a valuable intermediary. They do not turn software, its vendor or a standards entity into the authorized voice…
IETF
IETF Invoked Its Emergency Plan. The Trigger Must Survive the One-Page Guide
The IETF Administration LLC says its Disaster/Emergency Recovery Plan was rolled out for IETF 126 and invoked when a hotel guest stole equipment. For IETF 127, one page will guide staff, contractors and volunteers. That is a promising conversion of experience into operating…
CASE FILE
The Address Was Unique. The Wire Still Saw a Collision: RFC 10019 and the Authority to Reconcile Zeroconf Multicast
Two isolated network segments can each make a locally correct multicast allocation. Join them, and both histories may remain truthful while the merged wire can no longer honour both claims. RFC 10019 turns that edge case into an operating principle: an address is not unique until…
History
The Error Message Was Advice, Not a Verdict: How RFC 816 Layered Failure Decisions
A gateway that has crashed cannot send the error message explaining why packets disappear into it. RFC 816 began with that silence and built a layered answer: let routing repair distant failures, make the host replace a dead first hop, let TCP expose retransmission and timeout…
North America Institutional Trends
Green Dot's US$42.3bn B2B Gross Dollar Volume Rose 22% as Purchase Volume Rose 1%
Green Dot moved US$42.253 billion onto B2B account programmes in its second quarter, US$7.633 billion more than a year earlier. Reported B2B purchase volume increased by only US$25 million. That contrast is not a spending-conversion ratio: the two measures have different…
Story
LACNIC Reported 99.5% Completion. An Earlier 98% Minute Also Recorded 6% Cancelled Actions
LACNIC's Board has approved unusually high strategic-completion figures. The numbers may be sound. What the two checked minutes do not supply is the calculation bridge that would show whether cancelled, replaced or reweighted work remained in the denominator, left it or…
Story
ARIN Put 17,000 Legacy Networks in a Blog Post. The Status Table Is Missing
ARIN has published an unusually concrete warning about the contact records attached to legacy IPv4 space: roughly 17,000 networks, an `about half` risk description, 11% currently validated, another 20% incomplete, and a 76% comparison for resources under agreement. The figures…
History
The Missing Segment Did Not Stop the Next One: How RDP Separated Reliability from Order
In 1984, the Reliable Data Protocol made a choice that still unsettles casual descriptions of transport: a later message could be safely received, individually acknowledged and even handed to an application while an earlier message was still missing. Reliability described whether…
IETF
Dieter Sibold and the Cookie That Let the Time Server Forget
Network Time Security performs its expensive act first: authenticate a key-establishment service, derive two directional keys and close the TLS connection. Later NTP requests carry the missing association state back inside an opaque encrypted cookie. RFC 8915 made forgetting…
CASE FILE
W3C Opened Two Doors Into One Immersive Web Charter. It Needs One Disposition Record
W3C’s proposed Immersive Web charter can be discussed through a public GitHub issue or, by Members, on a confidential mailing list. That is a defensible division of access: useful review does not always arrive in publishable form. But both routes feed one charter-refinement…
History
The Name Was Not the Address: How RFC 814 Kept Identity Separate from Route
In 1982, a stale host table could send queued mail to an unexpected machine after the intended host had moved. RFC 814 treated that failure as more than bad data. It exposed four different references—name, address, route and port—and argued that an Internet host should translate…
Europe and Middle East Regional ISP Trends
Two fibre circuits are not diverse until their routes are proven
Two access services can arrive on separate invoices and still disappear in the same civil-works incident. Resilience begins when the shared failure domains are made visible, not when procurement adds a second supplier name.
CASE FILE
The Request Signature Survived. The Certificate Could Still Change: RFC 10002 and the Authority Inside CMC
RFC 10002 makes certificate enrolment look less like one approval and more like a chain of bounded decisions. An end entity can sign an intact request, an RA can attest to identity or key possession and request changes in an outer layer, and a CA can apply policy before issuing a…
Story
APNIC Signed a 2026 SANOG MoU. Its Public Link Still Shows “xxx” in the 2003 Text
APNIC says its Director General and the SANOG Chair formalized a Memorandum of Understanding at SANOG 44 in 2026. Yet APNIC's current partnership table still links readers to a three-page document whose operative date says `xxx day of August, 2003` and whose APNIC signature…
IETF
David Lawrence and the DNS Answer That Outlived Its TTL
When a DNS answer reaches the end of its TTL, a recursive resolver normally discards or refreshes it. RFC 8767 allows a narrower choice during failure: preserve the expired copy for a bounded time, return it only after a real refresh attempt cannot produce usable data, and keep…
Global Institutional Trends
Deere's US$7.7bn Sales Receivables Rose as Its US$56.6bn Finance Book Fell
Deere finished its third quarter with two large credit balances moving in opposite directions. Trade accounts and notes receivable rose to US$7.723 billion, while financing receivables and equipment on operating leases fell to US$56.576 billion. The contrast is not a verdict on…
CASE FILE
The Probe Took the Same Path. It Still Did Not Share the Queue: RFC 10014 and the OAM Evidence Boundary
An operations team can truthfully report that its probe crossed the same nodes and links as customer traffic while missing the congestion that harmed that traffic. RFC 10014 explains why: packet participation, topological path and forwarding treatment are different properties.…