Time Horizon
Multi-year
Within the Time Horizon facet, Multi-year time-horizon intelligence organises articles by the period over which a signal is expected to matter. The page helps readers distinguish immediate operational changes from longer-cycle governance, investment, standards, and infrastructure shifts that may unfold across quarters or years. It connects timing assumptions with public evidence, related actors, market context, customer exposure, policy pressure, and infrastructure planning so readers can judge whether a development is urgent, strategic, or still waiting on confirming evidence. The page also explains how time horizon changes the meaning of a signal, which organisations may be exposed, and which infrastructure decisions require short-term action or long-cycle monitoring.
NPNOG
Who opens the room? What npNOG-10's welcome order can—and cannot—prove
The first twenty minutes of a conference can reveal institutional relationships. They cannot, without supporting records, tell us who held the decisive authority.
Europe and Middle East Cloud Services Trends
Sovereignty is a dependency map before it is a location label
AWS's European Sovereign Cloud makes a serious case for regional separation. The harder procurement question is whether every consequential decision path—not only stored data—can be kept, tested and evidenced inside the promised boundary.
History
The Forwarding Evidence an IP Error Left Out
The router removed the labels before it prepared the error. What remained could identify the original IP conversation while omitting the state that had governed its passage through the network. Adding that state to ICMP made a report more useful. It did not make the report a…
IETF
The secret server name still needs a public front door: ECH’s new privacy boundary
Encrypted ClientHello gives a TLS connection two introductions: one the network may see, and one only the service can open. That is a real privacy gain, but it is not disappearance. The destination’s protection now depends on DNS configuration, a shared front door, key rotation…
Story
ARIN’s RDAP Bottom Search Is a Coverage Answer, Not a Leaf List
One query for a `/21` returns a direct `/22` allocation and an administrative `/8`. The result looks upside down only if `rdap-bottom` is mistaken for a list of descendants; its real job is to account for registry coverage.
ICANN
The Forged Letter That Moved Sex.com: Kremen v. Cohen and Network Solutions
A forged instruction did not move a physical entity. It changed the authoritative registration record for a domain name—and forced a federal appellate court to ask what, exactly, the registrant controlled.
Story
LACNIC’s Last Waitlist Applicant Faces 12 Years for at Most 1,024 Addresses
LACNIC’s IPv4 queue does not preserve a block for every approved applicant. It preserves an identity-bound place in a sequence whose supply, order, final approval and address quality remain unsettled until recovered space is actually released.
History
The Number That Came Back Unchanged: PPP’s Magic-Number
A PPP endpoint could receive the exact number it had just sent and be entirely satisfied. It could receive the same number in another kind of packet and suspect a loop. The distinction was not in the four bytes. It was in the action those bytes belonged to—and in the small…
ICANN
A Proxy Clause Without a Private Enforcer: Balsam v Tucows
Daniel Balsam had a seven-figure judgment and a contract clause that seemed to point straight at the missing identity. What he did not have was the legal position from which to enforce that clause against the registrar.
Story
ARIN’s NET Route List Stops at the Direct Allocation
An empty collection can look decisive until the query boundary is drawn. In ARIN’s routing-registry API, the ordinary NET route list ends at the direct registration; the downstream tree belongs to a different request.
ICANN
A Domain Name in a Receiver’s Hands: Office Depot v Zuccarini
The judgment was entered in Florida, the debtor lived elsewhere, the registrars were scattered across three countries, and the `.com` registry sat in Northern California. To collect the debt, the Ninth Circuit had to decide where an intangible domain name could be found.
History
The Message SMTP Could Forget Without Hanging Up: How RSET Defined Transaction Scope
One rejected recipient can leave a mail server holding an awkward remainder: a valid sender, one accepted destination and a message that should no longer be sent. SMTP’s quiet answer was `RSET`, an acknowledged way to forget that unfinished message while keeping the conversation…
History
Borrowed Bytes: How DHCP Reused Its Boot Fields
A thirteen-byte filename could be too large—not for a DHCP message, and not for an option, but for the space left in one field. Reusing old boot fields solved one shortage. Reassembling the pieces in an agreed order solved another. The distinction made a small extension into a…
History
Two Queries, Two Servers: Why DNS Needed NSID
A service address can stay the same while the machine answering changes. DNS needed a way to identify the instance behind a particular reply, not merely whichever instance answered the next question. The resulting standard made the association precise while leaving the identity…
History
The Random Bit That Congestion Erased: The ECN Nonce Experiment
An experiment can work and still lose its claim on shared protocol space. ECN Nonce made a receiver's congestion report testable by exploiting information a router had destroyed. Its withdrawal illuminates both the limits of that test and the cost of keeping an experiment alive…
History
The Name That Entered Through Port One: TCPMUX and the Scope of Coordination
A two-page proposal from 1988 let a new service borrow a common entrance instead of acquiring its own official TCP port. The interesting question was not whether numbers disappeared, but which decisions could now remain inside the host.
History
The Bit That Could Not Keep a Service Running: Why DNS WKS Never Became a Live Directory
Before opening a connection, an early Internet mailer could inspect one bit in DNS and decide whether a server existed. The bit was exact. The world behind it was not.
CASE FILE
The Template ID Was Familiar. The Flow Still Needed Its Exporter: IPFIX and the Authority of an Observation Domain
The collector saw Template ID 256 after an exporter reconnected. It reused the definition cached from the old transport session, and the incoming bytes still produced plausible counters. The dashboard was orderly, the parser was satisfied and every field name was wrong. Nothing…
History
The Answer That Could Only Name What One Server Knew: Why DNS Retired IQUERY
A DNS request once arrived with no question at all. Instead, it placed a resource record in the Answer section and asked the server to supply every name that matched it. The reversal looked elegant on paper: if an ordinary query mapped a name to a value, an inverse query would…
CASE FILE
The TXT Record Was Correct. The Vendor Still Wasn't the Domain: ACME DNS-01 and the Authority of Delegated Validation
The vendor had been removed from the application, CI and staff accounts. One control survived: `_acme-challenge` still delegated to its validation zone. When the vendor's ACME account requested a wildcard certificate, the expected TXT digest appeared and every protocol check…