Profile
Briefing
Briefing 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.
IETF
The Server Returned the Old Object. It Did Not Return an Audit Trail.
JMAP Entity History proposes a practical way to recover previous and destroyed entity versions. Its own rules also explain why retained snapshots cannot prove every change, its actor, its authority or its outcome.
IETF
The Client Named a Trust Anchor. It Did Not Promise to Trust It
A server can follow a client's certificate-path hint exactly, send the path that the hint appears to request, and still watch the handshake fail. That is not a contradiction in the proposed TLS trust-anchor negotiation. It is the design's most important boundary: the client is…
IETF
The Exporter Produced 128 Bytes. It Did Not Bind the Token Holder to the Tunnel.
Revision 04 of EAP-PPT deletes an output that looked like inner-method keying material. The correction matters because a tunnel exporter can produce bytes without proving that the same party both terminated the tunnel and possessed the bearer token.
IETF
The Tag Froze the Module. It Did Not Freeze Consensus
A proposed IETF workflow would move YANG source out of RFC prose and point publication at an exact repository tag. That can settle which bytes were reviewed. It cannot, on its own, settle who agreed, what was shipped, what a device loaded or whether the network behaved as…
CASE FILE
GoCodeIT Support: a role label, a corporation, and where accountability actually sits
GoCodeIT Support is a name that looks like a person in the registry, but the public evidence shows it is an institutional contact role — and the accountability behind it sits with a company in two RIRs at once.
IETF
The Sender Received a Standard CNP. It Could Not See What the Proxy Dropped.
A new congestion-notification proposal gives old RoCEv2 senders a compatible warning through a proxy. Compatibility solves the packet-format problem; it does not preserve the whole evidence chain from congestion point to sender.
IETF
The Prompt Listed the Rules. The Device Change Needed a Different Receipt
An Internet-Draft on autonomous network management makes the essential distinction: telling an AI what it may do is not the same as enforcing those limits. For operators, the durable proof is the policy snapshot actually evaluated at execution, joined to the device change and its…
History
The Password Had No Directory Entry to Change: RFC 3062
In 2001, LDAP's ordinary edit operation could not reach every password. RFC 3062 introduced a separate password-change request that could target a session's user or a non-DN identity, even when the credential lived outside the directory. Its success rule was strict; its view of…
CASE FILE
The Chain That Was Touched: Where Attention Fell in the Svea Abuse-Contact Record
The Chain That Was Touched: Where Attention Fell in the Svea Abuse-Contact Record intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…
IETF
Every Checkpoint Verified. The Producer Could Still Have Forked the Log.
A September 2026 Internet-Draft proposes a private append-only log whose compact checkpoints can be witnessed without publishing the records. Its hardest lesson is that a cryptographically consistent history can still be only one of two histories.
IETF
A Registry Can Name the Error. It Still Cannot Explain the Failure
The IETF’s first working-group revision for canonical YANG error registries solves a real compilation problem. It also exposes a more consequential operating boundary: a stable error name governs vocabulary, while only the surrounding event record can establish cause, impact and…
IETF
The CDN Accepted the Cancel. The Purge Could Still Finish.
A September 2026 CDNI draft gives interconnected content networks a richer language for prepositioning, invalidating and purging content. Its most important operational lesson is narrower: asking a distributed system to stop is not evidence that the work did not happen.
IETF
The Tunnel Negotiated Over TCP. Its Protected Traffic Still Had No Road
A large post-quantum IKE exchange can finish cleanly over TCP while the ESP path that must carry the protected service remains blocked. Revision 07 of the IETF’s separate-transport draft turns that awkward fact into an operating discipline: control-plane success is not data-plane…
Global Regional ISP
The Customer Ledger Is the Weakest Layer: What AS17494's Own Records Prove About Its ISP Claim
The Customer Ledger Is the Weakest Layer: What AS17494's Own Records Prove About Its ISP Claim intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
IETF
Silence Is Not Availability: The Multicast Address That Survives Until the Partition Heals
Two senders can each complete a clean probe, retain the same multicast group ID and continue without an alarm. The contradiction appears only when the switch comes back and the network becomes whole again. An IETF draft now makes that delayed failure unusually legible: its…
CASE FILE
Filing the Complaint: The Public Remedy Path Behind the Svea Abuse Contact
Svea's abuse contact in the RIPE registry passes every automated check the registry runs, and no public source shows it has ever answered a report. This briefing sets out the filing test: the channels a reporter can actually use today, and the observable responses that would…
Number Resource Society
RIPE NCC's Excess-Contribution Redistribution: A Codified Remedy, Not a Gesture
When the RIPE NCC returned EUR 8,365,249 to its members in 2020, the money moved under a written procedure that predates the decision — and the October 2019 General Meeting vote that authorised it was split hard enough to reveal how contested the choice between reserve and…
IETF
The Compensation Ran Forward. It Did Not Prove the Past Was Restored
An AI-assisted network workflow can carry a carefully structured recovery plan and still fail to put the world back. In the first NAIM Operation IR draft, compensation is another authorized, validated and logged operation—an attempt to reverse or mitigate a prior change, not a…
Global Cloud Services
AS210328 After the August 2026 Registry Edit: What Changed, and What Still Cannot Be Verified
AS210328 After the August 2026 Registry Edit: What Changed, and What Still Cannot Be Verified intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Global Institutional
DFINFRA/AS210860: The Routing Table Says Zero, the Directory Says Ten
DFINFRA/AS210860: The Routing Table Says Zero, the Directory Says Ten 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 follow.…