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 Resource Named Its Authorization Server. It Did Not Grant a Right: RFC 9728’s Discovery Boundary
A resource can accurately publish where a client should look next and still have made no decision to let that client do anything. RFC 9728 gives protected resources a disciplined way to publish OAuth metadata. Its value is coordination: it narrows a discovery problem. It is not…
CASE FILE
The Authorization Conversation Was Still Pending. It Was Not an API Right: GNAP’s Continuation Boundary
A client can be entitled to continue an authorization conversation without being entitled to call the API it asked about. RFC 9635 makes the distinction unusually explicit: a continuation credential advances one grant request at the authorization server; a resource right appears…
CASE FILE
Internet Society Added ‘Obedience’ to Its Policy Opening. The Duty Runs to Mission, Not Management
One word can make a governance document look more authoritarian just as the underlying rule becomes easier to read. Internet Society’s Board added the duty of obedience to the opening paragraph of its Trustee fiduciary policy in July 2026. Yet the Board’s own resolution says the…
History
A Bridge Port Was Not Necessarily an Interface. Its Counters Did Not Describe the Whole Line: RFC 1286
A network operator can be handed three reassuringly familiar facts: a port number, an interface index and a counter. RFC 1286, the 1991 Bridge MIB, is valuable because it refused to let those facts collapse into one picture. A bridge port could correspond to an interface without…
History
An Optional Attribute Could Extend a Class. A Mandatory One Had to Start Another: RFC 1274
An early directory needed a common vocabulary without turning every local requirement into a universal decree. RFC 1274’s answer for COSINE and Internet X.500 pilots was neither a frozen list nor permission for every site to reuse the same name privately. It made a more careful…
Story
RIPE NCC Fixed a Cross-Service Vulnerability. The Remediation Needs a Chain Receipt.
“Fixed” is a useful word only when a reader can tell what changed its meaning. RIPE NCC’s June account of a multi-service vulnerability disclosure makes that distinction unusually visible. It describes several issue categories across more than one service, and it also says that…
History
The Measurement Needed Permission Before It Became a Result: RFC 1262
In 1991, the Internet Activities Board gave researchers a deliberately unromantic answer to a worthy ambition. Measuring the network was critical to its development, evolution and deployment planning; it could also disturb the very operation it hoped to understand. RFC 1262 kept…
IETF
IETF Declined the AUDIT BoF. Its New List Is a Venue, Not a Working Group
On 31 August, the IETF opened a mailing list for a possible effort to make AI-agent actions auditable. That was a useful institutional step. It was not approval of the effort that proponents had requested: the public BoF record remains Declined, the list is explicitly non-WG, and…
CASE FILE
The Packet Carried a Mark. It Did Not Deliver an Operations Verdict: RFC 9947 and SRv6 Measurement Authority
A marked packet is compelling because it seems to turn an invisible path into a fact. A loss bit, a delay bit, an identifier, a timestamp and a sequence value can all travel inside the same Segment Routing Header that tells the packet which segment endpoint to visit next. That is…
ICANN
ICANN’s .TEXAS Consent Gate Is Exact. Texas’s Letter Adds “Any Derivative”
Six words enlarge a clear objection into an undefined perimeter. Texas told ICANN that it opposed `.texas` “and any derivative thereof.” The 2026 Applicant Guidebook gives the state a consequential voice over the exact ISO 3166-2 match, but it also says strings that include…
CASE FILE
The Receipt Put a Statement on the Ledger. It Did Not Decide to Trust It: RFC 9943 and SCITT
A software-supply-chain record can look like a conclusion when its machinery is working well. A statement is signed. A transparency service accepts it. A receipt carries a verifiable proof. An auditor can replay a sequence and a dashboard can show a reassuring green line. The…
CASE FILE
W3C's 2026 XML Namespace Points to a Moving Draft Without a Change Policy
W3C dated a new XML Security namespace on 19 August 2026. The first archived Internet-Draft revision to use it appeared two days later, replacing a placeholder while the document was still adding material. Early allocation is useful; the unresolved governance question is what…
CASE FILE
The Forum Could Suspend a Post. It Could Not Claim the Network: RFC 9945 and the Boundary of IETF Moderation
A forum needs a way to stop disruption without mistaking that housekeeping power for a title over everything discussed there. RFC 9945 makes that distinction unusually visible: it gives the IETF a shared procedure for its public online spaces, while repeatedly locating the…
CASE FILE
The Multicast Request Reached the Group. It Did Not Authorize the Action: RFC 10020 and CoAP Evidence
One protected request can look wonderfully decisive. A controller addresses a CoAP group, the network fans it out, several endpoints answer, and the panel records a quiet burst of acknowledgements. In a constrained environment, that economy matters. It is also exactly where an…
IETF
IETF Marks Two Capture Controls Incomplete. Their Q4 Proof Needs a Public Map
One line in the IETF Administration LLC’s 2026 Risk Register names the institutional failure that open technical organizations are often least comfortable naming: “The IETF, or a key part of it, is captured.” The same line says two controls are complete and two remain unfinished…
CASE FILE
What the Aggregate Report Actually Knows: RFC 9990 and the Boundary Before Enforcement
A DMARC dashboard can make a narrow observation look like a verdict. One receiver reports a large count from a source range, records an evaluated policy and shows a disposition. That is valuable operational evidence. It is not a global traffic census, proof of a sender's intent…
IETF
IETF Tools Kept Every-Line Review for AI Code. Its Next Boundary Is Still Unwritten
The IETF Tools Team has named a genuine capacity problem: AI can produce ambitious pull requests faster than maintainers can safely absorb them. Yet the contribution guide it actually adopted in August still puts every submitted line in front of a human maintainer. That is a…
ICANN
ICANN’s $1 Million IGF Offer Draws an Advocacy Firewall
ICANN’s Board did more than authorize a large contribution to the Internet Governance Forum. Its published rationale drew a boundary around what the money was for, what it was not for, who would have to consent to a different use and how much institutional overhead should be…
JPNOG
JANOG Gives Officers a Separate Route to Rewrite Its Rules
JANOG’s public rules make mailing-list subscribers members, but they also let an officer supermajority amend the rules—or dissolve the voluntary association—without using the separate membership-approval route.
ICANN
ICANN Changed ‘Five-Year’ to ‘Periodic’—the Audit Clock Still Runs
One word disappeared from ICANN’s Board Risk Committee charter, but the obligation behind it did not necessarily disappear. The adopted text now promises external assessment “periodically” under professional standards. Those standards still contain a five-year outer limit. The…