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.
CASE FILE
Four Thousand Was a Prefix Claim, Not a Rate-Limit Mandate: RFC 9977 and the Evidence Boundary
A prefix file can make an address range easier to group. It cannot convert a count of end sites into a command to relax a local risk control.
ICANN
ICANN’s Ombuds Workplan Is Public. Its Board Evaluation Map Is Not
ICANN has published what its Ombuds Office plans to do in FY27 and the six kinds of performance evidence it intends to track. The Board has also approved a separate set of specific objectives against which it will evaluate the Ombuds. What the public record does not provide is…
Story
RIPE NCC’s RIS Is Updating Its Peering Policy. The Archive Needs a Selection Receipt
An archive becomes a public institution long before anyone gives it a constitution. A researcher downloads a route dump; an operator compares an incident against a collector feed; a policymaker treats a graph as a picture of the network. Each act lends the archive a little…
CASE FILE
The Certificate Verified the Peer. The External PSK Still Needed a Custodian: RFC 9973 and TLS Authority
A security review can make an unusually comforting statement: the client validated the certificate, the server selected an external pre-shared key, the handshake finished, and the traffic was encrypted. Every clause may be true. None answers the question a security owner…
Story
LACNIC's Board Is Nine Members. Its Public Description Still Says Seven
A public governance page can be right in its detailed account and wrong in the sentence built to travel furthest. LACNIC's current English Board record offers that small but revealing split: its description says the honorary Board has seven directors; the record's body says nine…
CASE FILE
The Flag Said Several Routers Meant This Prefix. It Did Not Name a Working One: RFC 9983 and Anycast Evidence
An OSPF control plane can state that a prefix is meant to be advertised by several routers. That is useful coordination. It is not a statement that any particular replica is reachable, selected, healthy, authorised to serve, or able to complete the transaction a packet…
CASE FILE
A Cookie Matched the Request. It Did Not Prove the Decision: RFC 10025 and Ambient Authority
A browser can attach the right-looking cookie to the right-looking request at the exact moment a consequential button is pressed. That still leaves four questions open: who caused the request, whether the server still accepts the session, whether this action is allowed now, and…
CASE FILE
One Trustee Roster, Two Boards: Internet Society Decisions Need a Capacity Receipt
Internet Society and its Foundation use the same trustees, yet their governing documents create two Boards—and a third capacity when Internet Society acts as the Foundation's sole Member. Back-to-back 2026 agendas show why aligned oversight still needs a record of which legal hat…
CASE FILE
A Ciphertext Reached the Key. It Did Not Name Its Sender: RFC 9180 and the Authority Missing from HPKE Base Mode
A team can receive an HPKE ciphertext, open it with the intended private key and still be unable to say who sent it, what outer request it belonged to, whether it is fresh, or whether anyone was entitled to act on its plaintext. RFC 9180 makes the cryptographic transition…
CASE FILE
An MPLS Action Is Not an Admission Decision: RFC 9994
A packet can arrive with a perfectly formed MPLS Network Action Sub-Stack, an opcode that an engineer can name and ancillary data that a parser can read. That packet has not yet proved that the next node supports the action, that the action belongs on this path, that its data…
History
The Dash That Grew With Every Forwarding: RFC 934 and the Cost of Recursive Quoting
In 1985, a message digest faced an apparently small problem: a line of ordinary mail text could look exactly like the line chosen to separate enclosed messages. RFC 934 answered by adding characters on the way in and removing them on the way out. That made the boundary…
Story
ARIN Kept Five Services Running Without Updates. Its Service-Level Report Has No Freshness Column
A registry can answer a question and still have nothing new to say. ARIN's planned July maintenance made that distinction visible: five reader-facing services remained operational while updates were not being published. The public service-level report measures availability well…
CASE FILE
The Packet Declared a Haptic Effect. The Device Still Had to Decide Whether to Render It: RFC 9993
A remote session marks one haptic unit as high priority. The packet is valid, the stream is negotiated and the receiver can decode it. None of that tells an actuator where on a body it may act, whether the requested amplitude is within the device’s envelope, whether a temperature…
CASE FILE
A Key Could Cross the Fabric. It Could Not Decide the Route: RFC 9992 and RIFT Authority
Two Top-of-Fabric nodes lose contact, each advertises the same RIFT key with a different value, and a leaf sees both. It must select one. A deterministic result is useful; it is not a declaration that the winning value is the current truth, that any receiver may act on it, or…
CASE FILE
The Private Key Never Left. Its Authority Did: RFC 9987 and the Transitive Trust of SSH Agent Forwarding
An engineer forwards a workstation’s SSH agent to a bastion. A process on that bastion cannot copy the private key, yet it may still ask the distant agent to sign a new authentication request. “No key exfiltration” is therefore an incomplete incident verdict: material custody and…
CASE FILE
The Domain Requested the Failure Report. The Receiver Still Had to Authorize Disclosure: RFC 9991 and DMARC Forensics
A mail receiver detects a genuine authentication failure in a forwarded calendar invitation. The author's domain has requested a forensic report at an external address. Sending the report could expose the invitation, its recipients and the forwarding path to a party that never…
CASE FILE
SC100’s Draft Draws DNSSEC’s Boundary at the Primary Perspective. The Receipt Must Name It
SC100 passed its vote by unanimity among the members who participated, but on 31 August 2026 it was still an accepted draft under intellectual-property review. Its most useful clarification is not that “DNSSEC is required.” That duty already exists. It is that the duty belongs to…
Story
APNIC's EC Adopted Topic Shepherds. No Public Charter Says What a Shepherd Can Do
APNIC's Executive Council has chosen a sensible answer to a familiar board problem: give individual members continuing responsibility for important subjects. Its May minutes call them topic “Shepherds” and say they will lead discussions on allocated areas. The missing part is not…
CASE FILE
SC101 Closes a Domain-Control Gap. The Transition Still Permits Two Rulebooks
A certificate authority can now point to one current set of TLS Baseline Requirements while legitimately running one of two different domain-control derivation rules. SC101 made the safer order explicit: choose the validation method, follow a permitted CNAME path, then prune…
CASE FILE
The Label Named the Encoding. It Did Not Name the Schema: RFC 9996 and Authority Behind a Protobuf Payload
A gateway accepts `application/protobuf`, the decoder returns a message value, and the request enters the business system. None of those successes establishes that the receiver used the producer's intended message definition. RFC 9996 gives Protocol Buffers a proper outer label.…