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.
ICANN
Who Controls the .jp Registry? The Instrument Chain Above JPRS
Japan Registry Services Co., Ltd. (JPRS) sits at the center of a layered control surface for the .jp country-code top-level domain: IANA and ICANN grant its international authority, JPNIC and Japan's government can challenge it, and a 2025–2026 evaluation cycle plus a second…
Europe and Middle East Regional ISP
AS210837: a registry record without a network, read only through its mirrors
AS210837: a registry record without a network, read only through its mirrors 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…
Story
RIPE NCC’s Geneva Briefing Invoked Measurable Progress, Without Naming a Measure
At a 17 September session co-hosted with the ITU and the Permanent Mission of Lebanon in Geneva, the RIPE NCC placed the RIR function between digital-policy goals and operational delivery. Its post-event account describes partnerships, capability and capacity building as routes…
IETF
The Byte Was the Same. The Timeout Was Not: RFC 9510
A one-byte CCNx lifetime can mean a fraction of a second to one forwarder and years to the next. RFC 9510 buys a wide time range without buying a new TLV—and makes software-version identity part of the evidence.
CASE FILE
The Runtime Said It Supported BPF. The Program Never Reached the Hook
A compiler selected an atomic instruction from a capability label, the loader returned a program identifier, and the release dashboard called the policy active. None of those facts proved that the intended hook had accepted that program generation.
CASE FILE
NIST’s Multi-Cloud Draft Exposes the Boundary a Service Bundle Cannot Prove
A managed bridge between cloud providers can move integration work away from a customer. It cannot, by itself, establish which system, control and evidence an authorizing decision actually covers. NIST’s draft asks readers to confront that distinction.
CASE FILE
One Packet Finished the Handshake and Carried the Command. Silence Could Mean Eight Different Things
RFC 9668 lets a constrained client append EDHOC message_3 to its first OSCORE request, reducing key establishment plus one protected transaction to two round trips. The optimization saves airtime. It does not make handshake completion, request verification and application…
IETF
The Locator Was Visible. The Route Was Not: RFC 9514
A controller can receive a valid BGP-LS Prefix NLRI, see an SRv6 Locator, and still lack the field that lets it call the prefix reachable. RFC 9514 draws that line in one companion TLV—and a verified erratum corrects the number operators must use.
ICANN
Challenging a .jp Registration Just Got Easier: What the 2026 JP-DRP Rules Revision Actually Changed
Japan's procedure for disputing ownership of a .jp domain name was quietly modernised this spring — but its most consequential limits were left exactly where they were.
CASE FILE
NIST’s Final Token Guide Puts Revocation Limits at the Cloud Handoff
A provider can stop issuing fresh credentials without instantly extinguishing every access token already accepted elsewhere. NIST’s final IR 8587 asks cloud providers and agencies to make that boundary knowable.
IETF
The number was free. The meaning was still unreviewed: RFC 9515
A vendor can now reserve a high-range BMP value through a well-formed request, without first producing the stable public specification that `Specification Required` demanded. RFC 9515 makes collision avoidance cheaper. It also makes it dangerous to mistake an available number for…
CASE FILE
The Outside Network Saw One Perfect Router. The Fabric Behind It Had Already Split
RFC 9666 lets an IS-IS area appear to Level 2 as one proxy node. That compression can save a network from carrying an entire leaf-spine topology twice, but it also hides the machinery that must honor the advertised transit. A clean Proxy LSP is a control-plane promise, not a…
CASE FILE
A SPARQL Graph Store Draft Makes Two Client Defaults Visible
W3C’s September revision widens the RDF format a server may return when a client omits `Accept`, and spells out UTF-8 decoding for an indirectly named graph. Neither change gives a client permission to write.
Europe and Middle East Cloud Services
Poyraz Hosting AS210574: live routes, lagging public records
Poyraz Hosting AS210574: live routes, lagging public records 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. The Europe…
CASE FILE
The Printer Kept Its Name After the Reset. The Key That Owned It Did Not
RFC 9665 makes automatic service registration workable by letting the first accepted device key defend a DNS-SD name. That useful continuity is narrower than identity: a valid signature can preserve a name while the owner, registrar, published answer or service behind it has…
IETF
The registry opened faster. The ecosystem had not yet agreed: RFC 9519
An SSH parameter can now receive a public name without waiting for a full IETF-stream RFC. That is useful coordination, not a declaration that software ships it, peers negotiate it or operators should enable it. RFC 9519 shortens one governance path and makes the missing receipts…
CASE FILE
A Quantum Source Is Not a Randomness Receipt
ETSI has drawn attention to a gap between the origin of random bits and the assurance a cryptographic service can actually use. A quantum label describes the source; it does not account for every step that follows.
CASE FILE
The Handshake Was Modern. The Incident Log Was Still Missing: RFC 9662’s Delivery Boundary
RFC 9662 repairs the cryptographic floor for secure syslog, but a preferred cipher suite is only one state in a longer evidence chain. Leadership needs to know what was offered, negotiated, authenticated, transmitted, accepted and retained for each event—not infer delivery from a…
IETF
The tunnel was up. The tenant path was still unproven: RFC 9521
A green BFD session can be exactly right and still answer a smaller question than the dashboard suggests. RFC 9521 gives Geneve operators a precise continuity test between two virtual access points; the harder operational task is preserving the scope of that result when…
Story
AFRINIC’s New IPv6 Tally Is 120 Below Its 2023 Figure. The Bases Differ.
AFRINIC’s September invitation reports 257 deployment milestones. A 2023 blog reported 377 across Deployathons and DO Helpdesk. The numerical gap is real; a like-for-like decline is not established.