Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
AFNOG
AfNOG’s Sponsor-Visibility Gate Is a Governance Firewall, Not a Branding Rule
AfNOG’s hosting rules make sponsor advertising conditional on advance approval and the event’s non-commercial purpose. That gate is an allocation of authority, not a cosmetic branding choice.
Global Institutional Trends
Apogee can integrate Groglass. It must still keep the earn-out legible.
Apogee has signed to acquire Groglass through the purchase of Groglass parent Alzette. The public announcement gives the market a compact strategic story: European coatings capability, an expected revenue contribution, an anticipated margin and prospective cost synergies. The…
History
The Offer That Was Not a Negotiation: How TCP MSS Bounded Each Direction
Each side of a TCP connection can place a four-byte option in its opening SYN. The number does not settle a shared packet size. It says how much TCP data the option's sender is prepared to receive in one segment—a directional boundary that the other endpoint must combine with…
IETF
Authenticated Is Not Reachable: RFC 9897 and the MP-DCCP Path-Join Boundary
An authenticated `MP_ADDADDR` advertisement is control data, not permission to send traffic on a new path. That path becomes usable only when `MP_JOIN` binds a new subflow to the original connection and completes the nonce/HMAC reachability handshake.
Story
AFRINIC’s Results Notice Lists Three Governance Committee Terms Ending in 2027–2029. It Gives No Vote Totals
The result notice names three elected members and three different term end dates. It does not show the vote totals, turnout or the rule used to allocate those durations.
Story
AFRINIC Whois notify Sends Change Notices, Not Operations Responsibility
AFRINIC Whois notify Sends Change Notices, Not Operations Responsibility intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may…
AFNOG
AfNOG Treats Its Mailing-List Archive as a Technical Resource Without Publishing a Correction Policy
AfNOG presents its public mailing-list archive as a technical resource, but the reviewed pages do not explain how archived material is corrected, annotated or removed after publication.
Story
AFRINIC’s WHOIS Dump Still Carries 1,345 Deprecated Authentication Labels
AFRINIC’s public database can show that an old authentication label remains attached to a maintainer. It cannot show whether the deployed update service would honour that method, reject it, or allow it only long enough to replace it. The difference between those states is where a…
IETF
Which Marking Wins? RFC 9895 and DLEP's Ethernet Credit Boundary
One packet matches both its Diffserv field and its tagged IEEE 802.1Q fields. Under RFC 9895, Ethernet classification takes precedence, so the Ethernet result determines the credit window against which transmission is accounted.
Story
RIPE Database sponsoring-org Records Administrative Sponsorship, Not Network Operation
The word “sponsor” can sound like ownership, financing or operational command. In the RIPE Database, `sponsoring-org` has a narrower and more useful meaning: it identifies the organisation administratively responsible for sponsoring an independent Internet number resource under…
AFNOG
AfNOG Publishes Mailing-List Boundaries Without Publishing the Moderation Procedure
AfNOG’s public mailing-list rules define what belongs in the forum, but the reviewed page does not explain the procedure used when a moderator must apply those boundaries.
History
The Handshake That Had to Remember Its Previous Handshake: How RFC 5746 Bound TLS Renegotiation
A TLS handshake could authenticate its own conclusion while saying nothing cryptographic about the bytes that came before it on the same connection. RFC 5746 repaired that gap by requiring every renegotiation to carry evidence from the immediately previous handshake.
IETF
Advertise, Subset or Reset? RFC 9894 and DLEP's Diffserv Credit Boundary
A modem can advertise more DSCP-linked credit windows than a router can realize. The operator therefore has to select a supported subset or reset the session; silently pretending that the two capability shapes match is not a safe operating state.
Story
AFRINIC Published Version Three of the RIR Governance Draft. It Separates Regular Audits from Compliance Reviews
The recommended draft gives routine assurance and exception review different jobs: a five-year audit cycle on one track, and a safeguarded Compliance Review on another.
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…