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.
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.
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.
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…
Story
AFRINIC WHOIS source identifies a database namespace, not a record’s provenance
AFRINIC WHOIS source identifies a database namespace, not a record’s provenance 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…
IETF
When 5G Slice Intent Reaches the Transport Network: RFC 9889 and the Handoff Control Boundary
An S-NSSAI that the transport domain cannot see must cross a handoff through a VLAN, IP or MPLS identifier before it can be bound to a transport service. That identifier is a translation point, not a complete promise of isolation, quality or capacity.
AFNOG
AfNOG’s Host Call Makes Impact a Selection Criterion Without Publishing How It Is Measured
AfNOG’s published hosting page gives preference to locations where a local workshop and meeting would have the greatest impact. The reviewed page does not define that comparative standard or publish how selection reasons are recorded.
History
The Old Mean Had to Move Last: How TCP Kept Its Timeout Variance Honest
A new round-trip measurement does two jobs inside TCP: it changes the expected delay and tests how wrong that expectation was. RFC 6298 fixed the order so the sample could not soften its own surprise before variance was recorded.
IETF
Enhanced Route Refresh Draws a Reconciliation Boundary Without Resetting the BGP Session
Enhanced Route Refresh Draws a Reconciliation Boundary Without Resetting the BGP Session intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
IETF
When Caller Identity Leaves SIP: RFC 9888 and the Control Plane Behind Out-of-Band STIR
A call can cross a gateway that cannot preserve an SIP Identity header while the PASSporT moves separately over HTTPS to a destination service provider’s Call Placement Service (CPS). RFC 9888 therefore treats caller-identity delivery as a control-plane problem: discover the…
AFNOG
AIS 2026 Invokes Decades of Collaboration Without Publishing an Institutional Memory Trail
AfNOG describes AIS as a long-standing community of practice in which each edition builds on decades of collaboration. The current first-party page reviewed here does not publish the cross-edition trail that would make that institutional memory inspectable.