Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
IETF
Cullen Jennings and the Capability Document That Was Not a Live SIP Trunk
An enterprise edge device can discover the right URL, pass TLS and OAuth, receive HTTP 200 and parse a valid provider capability document while no production call can cross the trunk. RFC 10006 makes configuration exchange easier; it does not collapse retrieval, activation…
JPNOG
JANOG Gives Officers a Separate Route to Rewrite Its Rules
JANOG’s public rules make mailing-list subscribers members, but they also let an officer supermajority amend the rules—or dissolve the voluntary association—without using the separate membership-approval route.
ICANN
ICANN Changed ‘Five-Year’ to ‘Periodic’—the Audit Clock Still Runs
One word disappeared from ICANN’s Board Risk Committee charter, but the obligation behind it did not necessarily disappear. The adopted text now promises external assessment “periodically” under professional standards. Those standards still contain a five-year outer limit. The…
History
A Policy Sentence Was Not a Network Control: RFC 1087 and the Limits of “Acceptable Use”
In 1989, the Internet Activities Board could identify conduct that threatened a shared research facility. It could say that intentional intrusion, disruption, waste, destruction and privacy compromise were unacceptable. What it could not do with a sentence was observe an act…
History
The Bit Preserved a Return Path. It Did Not Authenticate the Request: RFC 1044's HYPERchannel SRC
In a physical network, an address can do something concrete without saying who is entitled to act. RFC 1044 gave HYPERchannel messages a Source Address Correct bit that could survive only while the declared return address remained usable in reverse. That was valuable path…
History
The Speed Was a Display Hint. It Was Not the Link: RFC 1079’s Telnet Boundary
In 1988, a remote terminal program could know something useful about the terminal at the other end without pretending to know the network between them. RFC 1079 made that distinction unusually crisp. It let one Telnet peer request a pair of terminal speeds and let the other peer…
Europe and Middle East National Telecom Trends
A 2G device inventory is not a safe switch-off plan until each replacement path is confirmed
A facilities list can show that a building owns a pendant, lift alarm or fire alarm. It cannot show that the device is 2G-only, that its supplier has accepted an upgrade, or that the function will still work after the mobile network changes.
IETF
Tobias Fiebig and the Four DNS Reachability Receipts
A zone can display two A records, two AAAA records and a reassuring “dual stack” label while still withholding names from an IPv6-only resolver. RFC 10001 replaces that label with four bounded claims: two authoritative services must answer over IPv4 and two must answer over IPv6…
History
Before DHCP, Four Bytes Chose the Grammar: RFC 1048 and BOOTP's 64-Octet Limit
Before a diskless machine could fetch its operating system, it needed enough network knowledge to ask for one. BOOTP carried that knowledge in a field only 64 octets long. RFC 1048 made the field intelligible across vendors with four opening bytes and a compact option…
History
The Name Was the Address. It Was Not a Route: RFC 1088’s IP-over-NetBIOS Mapping
In February 1989, RFC 1088 made an unusually literal bargain between two naming systems. A host carrying IP over NetBIOS would derive a 16-byte NetBIOS name from its IP address: `IP.XX.XX.XX.XX`, with each `XX` written as ASCII hexadecimal. The name was meant to let a NetBIOS…
ICANN
ICANN’s Name Collision Assessment Is Not a Delegation Decision. What Does a High-Risk String Need to Prove Next?
An ICANN name-collision assessment is a risk-management step in the 2026 New gTLD Program, not a confirmation that a proposed label will—or will not—reach the DNS. Its practical importance is in the next gate: a string identified as high risk can require a mitigation plan that…
CASE FILE
W3C’s Human-Rights Note Proposed a Group Six Days After It Launched
On 4 August, W3C’s Advisory Board published five proposals for bringing human-rights considerations further into the consortium’s technical work. The third proposal treated a Threats and Harms Community Group as a possible next step. W3C’s own community record tells the…
History
Four Bytes Put a Message in TCP. They Did Not Rebuild the OSI Network: RFC 1006’s TPKT Boundary
TCP can deliver every byte in order and still decline to say where one application-shaped entity ends. In 1987, RFC 1006 addressed that awkward fact for ISO Transport over TCP with a remarkably small intervention: put four octets before a TPDU, then make the receiver count. The…
MYNOG
MYNOG Can Rewrite Attendance Terms After Registration
MYNOG’s published registration terms do more than set an entry price. They let the organisers amend the terms through publication on the conference website, treat later attendance as acceptance, and retain discretion to exclude a entity without refunding the registration fee.
History
The Token Found the Connection. It Did Not Admit the Subflow: MPTCP's MP_JOIN Boundary
One new TCP SYN can propose to become part of a connection that began somewhere else, on another address pair, minutes earlier. That is the useful oddity in Multipath TCP. It is also where a casual description—“the session moved”—loses the decisions that keep continuity from…
IETF
Weiqiang Cheng and the SRv6 Locator Lease That Still Needed a Route
The DHCPv6 log can show a valid Reply, a locator, an IAID and two working clocks while the route table still has nothing to say. RFC 10038 makes that gap explicit: assignment is one controlled event; reachability must be created, distributed and observed through separate systems.
ICANN
ICANN Names a Safeguard Assessment Provider. When Does String Review Become a Registry Agreement Obligation?
ICANN has appointed Mirror Group LLC for 2026 Round Safeguard Assessments. The important boundary is between a string-risk assessment and a safeguard that becomes part of a Registry Agreement.
Story
LACNIC and the economics of transition architecture beyond RIRs
A transition test built around functions, records and authority—not around the fantasy that scarce network resources can govern themselves.
Europe and Middle East National Telecom Trends
A final digital-landline notice is not a safe cessation until the critical call path is confirmed
A dated notice can prove that a provider started a final process. It cannot by itself prove that the person, telecare service or critical call path at the address has been safely carried through that process.
History
The Banner Marked the Screen. It Did Not Make the Policy: RFC 933 and Telnet's Display Boundary
A security banner could be sent once and kept visible by the workstation instead of being mixed into every screenful of application output. RFC 933 made that presentation bargain explicit—and left the security level, access decision and truth of the label outside the banner…