Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
Story
APNIC Whois mnt-lower Marks Maintainer Hierarchy, Not Routing Hierarchy
The word “lower” invites a network diagram: upstream, downstream, and packets moving between them. In APNIC Whois, `mnt-lower` describes something narrower. It identifies a maintainer in the registry’s update-authorisation structure. That is useful accountability evidence, but it…
CASE FILE
The Parody Began After the Address Bar: PETA v Doughney
A joke can be obvious on a page and absent from the address that brought the reader there. That timing problem sat at the centre of *PETA v Doughney*. Michael Doughney said his “People Eating Tasty Animals” site parodied People for the Ethical Treatment of Animals. The Fourth…
IETF
When May the Router Send? RFC 9893 and DLEP's Credit-Window Control Loop
A packet may be ready at the router, but transmission is permitted only after the router finds the matching classifier and FID credit window, confirms enough credits, and counts the packet with its MAC overhead.
History
The Neighbor That Stayed in the Cache After It Became Unreachable: How RFC 7048 Separated Failover from Forgetting
IPv6 Neighbor Discovery once treated the last unanswered unicast probe as both a warning to seek another path and a reason to erase the path it already knew. RFC 7048 split those decisions: a neighbor could become officially unreachable without its final link-layer address being…
AFNOG
AfNOG Says Community Needs Determine Its Content Without Publishing the Trace Between Them
AfNOG publicly says community needs determine its content. The reviewed pages do not publish a dated needs-to-programme trace.
Story
ARIN Net Type Records Registration Path, Not a Current Customer Relationship
“Reallocated” and “reassigned” look like labels for a business relationship. In ARIN’s registry, they do something narrower: they describe how an address block entered a downstream registration chain and what the recipient intended to do with it. That history is useful, but it is…
IETF
Who Tells the Router Which Queue? RFC 9892 and DLEP's Traffic-Classification Boundary
A modem can supply a replaceable Traffic Classification Identifier (TID) set to a router. Flow Identifiers (FIDs) then group DSCP or VLAN/PCP matches; when both classifier families match, Ethernet VID/PCP wins. The important boundary is that RFC 9892 describes how classification…
Story
AFRINIC Set a Deadline for Its Second Constitution Consultation. The Later Review Stages Remain Undated
AFRINIC dated the public comment window and described what follows, but the frozen announcement does not date the legal review, Board consideration or membership decision.
Europe and Middle East National Telecom Trends
A priority telecom restoration register is not a local continuity plan until eligibility, escalation and service recovery are verified
The outage call begins with confidence. Someone opens the “priority sites” spreadsheet. The rows name a civic coordination room, two health facilities and a transport control point. Then the useful questions begin. Which access service serves each building? Has the provider…
History
The Address That Spoke Before It Was Proven Unique: How Optimistic DAD Bounded Early Use
A newly attached IPv6 host used to wait for a uniqueness test before speaking. RFC 4429 shortened that silence without pretending the test had already passed: the address could carry traffic, but not yet exercise the Neighbor Discovery powers of an uncontested owner.
AFNOG
AfNOG’s Host Call Makes the Selection Final Without Publishing a Reconsideration Path
AfNOG’s dated host call says the named selectors’ decision is final. The reviewed page does not publish a limited correction path for procedural error or material new information.
IETF
When ACME Crosses a Delayed Network: RFC 9891 and the DTN Node-ID Proof Boundary
ACME authorization material is split between the ordinary ACME channel and delayed Bundle Protocol challenge and response Bundles: the server sends a challenge Bundle to the claimed singleton DTN Node ID, while the client binds the ACME account challenge to receipt of a…
Story
LACNIC WHOIS nslastaa Records the Last Successful Check, Not Current DNS Health
A date in a registry response can look like a present-tense assurance. LACNIC gives `nslastaa` a narrower meaning: it is the last date on which a correct reverse-DNS configuration was observed on a listed server. That historical success is useful evidence, but it is not a promise…
AFNOG
AfNOG’s Host Call Prefers a Different Region Without Publishing the Rotation Rule
AfNOG’s dated host call prefers regions other than the immediately previous hosting location. The reviewed page does not define the geographic decision rule behind that preference.
Story
AFRINIC Constituted Its Governance Committee. The Published Notice Does Not State a First Meeting Date
AFRINIC has named the members and their term ends, but the frozen constitution notice does not say when the committee will first meet or publish an initial work programme.
IETF
When a YANG Name Survives Revision: RFC 9890 and the Registry Identity Boundary
A revised YANG module keeps the initial module name and XML namespace. That makes a stable registry identity useful for locating the module, but it does not by itself identify the deployed revision or prove semantic compatibility. The operational question is therefore precise…
History
The Clock Moved Only for Useful News: How TCP Tied Its Timer to New Acknowledgment
An acknowledgment can arrive without changing what a TCP sender knows. RFC 6298 made that distinction control the retransmission clock: progress receives a fresh interval, repetition does not.
AFNOG
AfNOG’s Host Call Strongly Prefers Prior Workshop Familiarity Without Publishing an Equivalent Path
AfNOG’s dated host call strongly prefers hosts familiar with its workshop requirements through prior participation. The reviewed page does not publish an equivalent proof route for a first-time host.
Story
LACNIC’s IRR turns route filters into a derived registry view
A route filter can look like a policy decision even when several of its inputs were generated from other registry systems. LACNIC’s Internet Routing Registry makes that provenance part of the operating question.
IETF
Extended BGP OPEN Removes a 255-Byte Ceiling Without Making Every Peer Ready for More Capabilities
BGP speakers announce capabilities before they exchange routes, but the original OPEN message gives all optional parameters together only one octet of length. RFC 9072 removes that 255-byte aggregate ceiling by defining an extended encoding. The change creates room; it does not…