Content Type
Research
Within the Content Type facet, Research intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
CASE FILE
The Card Was Removed. Its Configuration Stayed: RFC 10016 and the Authority of System State
RFC 10016 gives device-supplied configuration a standard place to be seen. It also exposes a harder operational truth: the device can withdraw a system node while client intent remains, and a client can withdraw an override only to uncover the system value beneath it. The four…
MENOG
MENOG’s Local Host Can Sign Contracts, but the Secretariat Holds Approval
MENOG gives a local host substantial work and visible benefits. Its host requirements also draw a precise line: the host may sign service contracts on the Secretariat’s behalf, but only subject to the Secretariat’s approval.
CASE FILE
The Tree Was Active. One Leaf Still Had No Packet: RFC 10018 and the P2MP Closeout Boundary
The Tree Was Active. One Leaf Still Had No Packet: RFC 10018 and the P2MP Closeout Boundary intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
CASE FILE
The Endpoint Still Spoke TLS 1.2. Its Old Handshake Had to Go: RFC 10015 and the Retirement Boundary
RFC 10015 does not switch TLS 1.2 off. It makes a more exacting intervention: keep the protocol version where it is still needed, but remove the finite-field Diffie-Hellman and RSA key-exchange paths whose risk can no longer be justified. The hard part begins after that sentence…
CASE FILE
W3C Resolved to Change WCAG 3. It Did Not Freeze the Text
On 25 August, the Accessibility Guidelines Working Group adopted three resolutions that pointed editors to a conformance draft and told them to resolve the document's remaining comments before updating WCAG 3. That was a real group decision. It was not approval of every word that…
CASE FILE
The Handshake Combined Two Secrets. The Random Generator Was Still One
RFC 10024 gives TLS 1.3 a precise way to combine a traditional exchange with ML-KEM. The construction protects against the failure of one cryptographic assumption; it does not certify that the two components were executed inside independent operational failure domains.
CASE FILE
The Name Matched. The Key Had No Right to Revoke: RFC 10007 and the Missing `cRLSign` Proof
One certification authority gave the same named subject two different keys. Only one was meant to sign revocation lists. For years, the validation text could let the other key cross that boundary precisely because its certificate said nothing about permitted use.
IETF
IETF LLC Needs More Financial Signers. A Signer Still Is Not the Decision
IETF Administration LLC has identified a real resilience problem: a Treasurer's departure left one authorised signatory for both its bank and investment adviser. The proposed staff signer could help execute Board decisions. It should not blur who made them. The durable control is…
CASE FILE
The JSON Was Valid. The Trunk Still Needed an Owner: RFC 10006 and the Apply Boundary
A service provider can now describe a SIP trunk in a form an enterprise edge can discover, authenticate for and parse. The consequential question begins one step later: who is entitled to turn that description into running configuration?
CASE FILE
The Boot Loader Identified Itself. The Relying Party Still Had to Decide
RFC 10013 gives a measured component a portable identity and sampled value inside an Entity Attestation Token. That evidence can be fresh, signed and correctly encoded while the final question — what this device may do — remains unanswered.
CASE FILE
The Route Advertised 70. The Local Link Could Carry 50: RFC 10005 and Bandwidth Authority
One upstream says it has 70 units of capacity. The receiving router can reach that upstream only across a 50-unit local link, yet policy assigns it 70% of the traffic. The BGP UPDATE is valid, every session remains established, and congestion is still the expected result. RFC…
Story
RIPE NCC’s Two Voting Codes Need a Credential Map
RIPE NCC tells October’s voters to expect two codes in two emails. That is a useful instruction, but it is not yet an account of the control. The names “Code 1” and “Code 2” describe a user journey; they do not show what each credential proves, who can recreate it, or when a…
ICANN
ICANN Tests Two-Character gTLDs Against Two-Letter ASCII Codes. What Does That Gate Actually Protect?
A two-character label can be valid enough to enter the 2026 Round and still be stopped because it resembles a two-letter ASCII code. The important question is not simply whether ICANN says no. It is which gate said no, which label or variant caused the comparison, and whether the…
CASE FILE
The DNS Said the Domain Was for Sale. It Did Not Have Authority to Close the Deal
RFC 10023 makes a registered domain’s availability visible in DNS. Its compact signal can open a negotiation while the domain remains in use; it cannot identify the rightful seller, bind a price or complete the transfer.
CASE FILE
The Zone Was Online. One Address Family Could Not Reach Its Authority: RFC 10001 and DNS Partition
The dashboard stayed green because its resolver quietly used IPv4. An IPv6-only resolver followed the same published delegation, reached a missing dependency and stopped. The name had not disappeared; its authority existed on one transport path and not the other. RFC 10001 turns…
CASE FILE
The Route Tree Remembered Every Target It Saw. It Did Not Authorize the Detour
SIP History-Info can show how a request moved from one target to another. That makes it valuable evidence. It does not make the resulting route complete, truthful, permitted or successful.
CASE FILE
The Packet Came Back Complete. The Evidence Set Didn't: RFC 10029 and Authority Across DNS Types
A resolver asks once for an address, an IPv6 address and an HTTPS service binding. One successful packet returns. That packet can still leave one of the three questions unfinished. RFC 10029 makes the missing distinction operational: a shared envelope can reduce transactions, but…
CASE FILE
The Dialog Was Found. The Transfer Was Not Yet Earned: SIP Replaces and the Authority to Move a Conversation
A help-desk console can show “transfer accepted” while the target has refused the new call and the original caller is still hearing hold music. The messages may all be correct. The failure lies in treating a reference, a dialog match and a completed handoff as one event.
ICANN
ICANN Can Stop a String Without a Competing Applicant. What Does a Blocked Name Actually Do?
In the 2026 new gTLD round, a protected or reserved label can stop an application without becoming a rival applicant. The decisive governance question is whether the public record shows the exact exclusion boundary, comparison and challenge clock.
CASE FILE
The Login Was Real. The Request Context Wasn't: RFC 10027 and Authority Across Devices
A television asks for an account, a phone displays the authentic service, and strong authentication succeeds. Yet the token can still return to an attacker's device. RFC 10027 makes the missing control visible: the ceremony proved the user, but the unauthenticated path between…