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.
CASE FILE
Three Months After the Fine: No Follow-Up, No Appeal, No Documented Remedy for Svea Bank
On 17 December 2025, Sweden's financial supervisor Finansinspektionen (FI) gave Svea Bank AB (org. no. 556158-7634) a formal remark (anmärkning) and a sanction fee of SEK 170 million for breaches of core anti-money-laundering rules…
IETF
The Configuration Succeeded. Its Trace Began Again
A device can accept a management change after rejecting the identifier meant to follow that change across the control stack. Two current IETF drafts make that split explicit—and force operators to decide how they will prove an action whose observability chain starts halfway…
IETF
The Old Mechanism Was Deprecated. The Link Had Not Migrated.
One sentence in a new Internet-Draft can change the preferred future of a protocol. It cannot change the packet a router will accept tonight. The first draft to deprecate IPsec AH for OSPFv3 exposes the gap between standards direction and a live link: every attached router must…
IETF
The Route Was Installed. The Next Hop Did Not Understand Its Source Constraint.
The change record showed a clean install: destination, source prefix, next hop, metric. One hop later, the source qualifier had vanished from the forwarding decision. Revision 06 of an IETF routing draft turns that quiet compatibility gap into a leadership problem: the same route…
IETF
A Healthy RadSec Proxy Could Not Prove the Home Realm
The access controller had a protected RadSec connection, a valid peer certificate and a prompt `Status-Server` reply. One customer realm still timed out. Nothing in those observations is contradictory: each belongs to a different hop, and revision 18 of the RadSec draft makes the…
IETF
The Dashboard Still Showed 10,000 Valid Routes. They Were Not the Same 10,000.
The number survived the maintenance window without moving. That looked reassuring—until the operators compared the routes behind it. A new IETF YANG draft makes several RPKI validation totals observable across the BGP pipeline. It also makes clear why a total, detached from its…
Europe and Middle East Cloud Services
NovaCloud-Hosting one month on: PletX still listed, Trustpilot still closed
A month after NovaCloud-Hosting's own status pages declared the 19-day July 2026 Frankfurt outage resolved, the public record around the operator still points in several directions at once. The storefront advertises; a review platform declares the website closed; the operator's…
Story
Call for Nominations to the RIPE NCC Executive Board: What the 2026 Record Actually Publishes
The RIPE NCC has run a complete Executive Board nomination cycle for its May 2026 General Meeting. Reading the registry's own instruments — the call for nominations, the candidate and nomination procedure pages, and the document submission guidelines — shows a process that is…
IETF
The Collector Counted CE. It Could Not Tell Which Service Was Marked
A dashboard reports 12,000 Congestion Experienced packets and divides them by the ECT(1) total. The percentage looks exact enough to justify a change to the low-latency service. Yet the packets now carrying CE no longer say whether they arrived at the marker as ECT(1) or ECT(0).…
Global Regional ISP
Three Clocks, One Handle: What the ACSK-RIPE Record Does and Does Not Settle
Three Clocks, One Handle: What the ACSK-RIPE Record Does and Does Not Settle 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
The Voucher Promised Another Voucher. Renewal Had Not Happened.
ANIMA's current onboarding draft gives a MASA room to project how long it expects to renew a device Voucher. Revision 36 also makes the later gates clearer. The projected date is still not a replacement artifact, a service-availability receipt or proof that the device completed…
Number Resource Society
The nomination funnel behind RIPE NCC's Executive Board election: what the May 2025 record actually shows
Every three years, the RIPE NCC membership nominates, supports and elects the people who sit on the body that governs the world's largest regional internet registry by membership count. The May 2025 election left a complete public record: a call for nominations under Article 9.1…
CASE FILE
The Mailbox That Exists Only in the Registry: Svea's Abuse Contact and the Limits of "Valid"
When Svea Ekonomi AB merged into Svea Bank AB on 3 January 2022, the group's abuse-contact surface in the RIPE registry did not follow the merger. Nearly four years later, the routed legacy netblock 193.105.138.0/24 still presents a mailbox on a third party's domain…
IETF
The Draft Removed Two HPKE Modes. Running Code Did Not Disappear.
The proposed HPKE replacement reserves the two mode values that RFC 9180 used for Auth and AuthPSK. That is a clear standards decision; it is not an inventory of libraries, profiles, stored entities or counterparties that may still depend on the older compatibility set.
IETF
The Proxy Authenticated the User. It Did Not Authenticate the Source MAC
A green tunnel indicator can be perfectly accurate and still conceal the most important unresolved question: which Layer 2 identities may the authenticated user introduce into the remote broadcast domain? CONNECT-ETHERNET draws that boundary sharply. HTTP can establish the…
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.