Content Type
Research
Within the Content Type facet, Research intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
AFNOG
AfNOG’s NII Service Award Turns Recognition Into a Governance Signal
AfNOG’s published award language does more than celebrate individuals. It identifies service, sustained technical contribution and mentorship as conduct the institution wants its community to value.
IETF
The Ports That Outlived Their Protocols: RFC 9900 and the Discipline of Giving Numbers Back
Ports 831, 832, and 833 can persist in diagrams, service files, and filters even after the NETCONF transports once attached to them never reached known production deployment. RFC 9900 therefore retires the number bindings without erasing their semantic history.
AFNOG
AfNOG’s Bursary Criteria Turn Travel Funding Into a Knowledge-Sharing Mandate
A dated AfNOG-hosted bursary application ties individual travel support to the ability to reuse and share meeting knowledge within an African country and region.
IETF
One Name, Many Rules: RFC 9899 and the Control Surface of Reusable ACL Sets
A security team changes one named prefix set once, and every ACL that references it can inherit the change without rewriting each parent rule. That mechanism is the promise—and the control problem—behind RFC 9899’s reusable policy entities.
History
The Deadline That Was Not a Retransmission Timer: TCP User Timeout
TCP can decide to retransmit a segment and still decide, on a different clock, that the connection has waited too long. The first decision schedules another attempt. The second ends the connection. RFC 5482 made that persistence preference visible to a peer without turning it…
IETF
Shrink the Trust Domain: RFC 9898 and the IPv6 Neighbor-Discovery Isolation Choice
On one IPv6 access segment, three different root causes can surface together: multicast load, implicit trust of every on-link node, and router Neighbor Cache Entries created on demand. The practical question is therefore not which symptom to patch, but which part of the Neighbor…
Story
LACNIC Whois owner-c Marks Administrative Authority, Not Network Operation
LACNIC Whois owner-c Marks Administrative Authority, Not Network Operation 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’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.
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 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.
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
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.