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.
Story
ARIN Described a Two-Person Rule for AI Drafts. It Did Not Describe the Receipt
ARIN’s public answer was unusually concrete: generative AI may assist a narrow class of drafts, the drafter remains responsible, and a second person reviews the result before release. The missing piece is not another principle but the durable record that proves those decisions…
IETF
A YANG Minimum Version Is Not a Compatibility Floor
An importer asks for version 3.1.0 of a YANG module. On the shelf it finds 3.1.2 marked `_non_compatible` and 4.1.2, whose major number announces a breaking change. Both can satisfy the request. The result is not a loophole hidden in an implementation: it is the deliberately…
IETF
A second Netnews cancel lock can add another cancellation authority
A field that looks like extra protection can preserve a second actor’s ability to authenticate withdrawal. For an archive operator, the consequential questions are who retains the secret, which old articles it covers and what happens when the service relationship ends.
IETF
A guest TURN relay still needs an admission policy
Letting a visitor use a network’s communications relay without long-term credentials simplifies arrival. It does not decide whose capacity the visitor consumes—or who must return an allocation that the application never uses.
IETF
A Packet-Discard Counter Needs an Intent Epoch Before Automation Acts
At 02:14, an egress no-buffer counter starts climbing. The automation can move traffic in seconds. What it cannot see in the number is that a new service profile went live at 02:12, the line card restarted at 02:13, and the approved loss budget belongs to the configuration that…
Global Datacenter Trends
IEEE’s 200G MMF Review Puts One Unset Limit Behind Several Link-Budget Rows
A September contribution makes the dependence unusually clear: the optical budget and several acceptance conditions move with the same transmitter-quality limit. Buyers need a coherent test definition, not a collection of promising numbers.
IETF
When a credit-control timeout still permits service
A Diameter policy called RETRY_AND_TERMINATE can keep an established service running when one timer expires. The consequential boundary is the later request outcome—and who is accountable for consumption while that outcome remains unresolved.
IETF
One Shared Nameserver Is a Continuity Test, Not Proof of Delegation Control
A resolver looks again at a delegation it has cached. The parent now lists a mostly different set of nameservers, but one familiar name survives. That intersection can be enough to treat the delegation as continuous, provided any relevant signer overlap also holds. It is a useful…
Story
APNIC’s NIR SIG Asked Four Charter Questions. Its Deck Shows One Unlabelled Result
An APNIC 62 charter-review deck asks seven National Internet Registries four different questions, then places one 86% support chart beside them without saying which question it answers. The proposed charter may still deserve support. But if the NIR SIG is to consolidate views for…
IETF
An IPv4 lease has an IPv6 moving part
Dynamic softwire provisioning gives an IPv4 service more freedom over where it starts. The price of that freedom is a binding whose location, update rate and privacy properties cannot be read from the IPv4 allocation alone.
IETF
DNS GREASE Needs an Experiment Charter Before It Becomes a Default
A resolver deliberately puts a value with no useful meaning into a DNS query. A correct peer ignores it. A brittle peer may reject the query, stay silent or provoke a retry. The experiment protects tomorrow’s protocol by creating a small inconvenience today. That bargain is…
IETF
The repair window inside an EVPN address conflict
Removing a duplicate endpoint and releasing the network state it disturbed are different parts of recovery. Their separation exposes a decision that a closed incident ticket can easily conceal.
IETF
Dry-Run DNSSEC Tests a Resolver Cohort, Not the Internet
A zone is signed, a validator finds the signature wrong, and the user still gets an answer. That apparent contradiction is the point of dry-run DNSSEC. Failure is exposed to an operator without yet becoming failure for the ordinary client. The rehearsal can reveal a broken…
IETF
The network passed the speed test. Who accepted the waiting?
A managed connection can deliver the expected volume of data while leaving an unresolved choice between delay, retransmission and individual transfer performance. That choice belongs in the service handover, not in an unexplained headline rate.
History
Who pays while a network upgrade waits for everyone else?
A protocol can coexist with old equipment long before it delivers a return to its first users. The history of Quick-Start exposes the cost of that interval—and why a smaller deployment can sometimes be the more ambitious business.
IETF
A Deprecation Date Retires an RDAP Label, Not Its Clients
An IANA registry can mark an RDAP extension obsolete. An operator can publish an end date. Yet somewhere beyond both records, a client may still ask for yesterday’s interface. That is not a contradiction. It is a map of divided authority—and a warning against treating one date as…
Story
The RIR Draft Calls the System Bottom-Up. Status-Change Consultations Stay Optional
The recommended RIR Governance Document describes the Internet Numbers Registry System as open and bottom-up. A few pages later, its new Article 2.7 says neither the RIRs nor ICANN are obliged to consult their communities when assessing a proposal to recognise or derecognise a…
IETF
A CDN must carry a loop warning it cannot authenticate
A cooperative defence can depend on preserving information that remains untrusted. CDN-Loop exposes the division between a customer's configuration freedom, a provider's protective decision and the evidence needed to explain a failed request.
IETF
DNSSEC Recovery Runs on Clocks No Signer Controls Alone
The private key is unusable. The zone is still answering, and yesterday’s signatures still validate. That is not recovery; it is borrowed time. A new DNSOP draft explains how to use that interval without destroying the trust that remains. Its harder lesson is institutional: the…
CASE FILE
A DNS Failure Drew 51 Queries. The Cause Was Still Unresolved
APNIC Labs sent several kinds of “no” from an experimental authoritative DNS service. Definitive negatives drew roughly four queries per test. `SERVFAIL` drew 51.73 and silence 83.46. Those are measurements of received traffic—not a verdict on which resolver layer multiplied it.