Profile
Research
Research profile intelligence connects person, company, institution, and other entity coverage for readers comparing the subjects behind BTW.MEDIA reporting. The page helps compare public profiles, related events, evidence packs, role changes, operating footprints, governance exposure, organisational links, and market relevance while keeping organisation and people records distinct from ordinary news chronology. Readers can understand the subject behind the headline, the evidence supporting that profile, and the infrastructure or market relationships that make the profile relevant. They can see who or what the profile represents, which public sources support it, how it connects to companies, markets, governance bodies, or events, and what changes may deserve continued attention as the subject evolves.
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.
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…
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.
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.