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.
History
The Header Described an Archive. It Did Not Authorize the Decoder to Run It: RFC 1505
The line counts agree. The archive expands. The checksum closes. A shell command now waits in a directory created from an email message. In 1993, RFC 1505 drew the most important boundary at exactly this point: successful decoding was not permission to execute.
Leaders
Karthick Thangavel and the Network Work Hidden Beneath India’s Broadband Growth
Every AI answer, streamed match and digital payment begins with a less glamorous event: somebody surveyed a route, joined a fibre, configured an access device and stayed available when the link failed. Karthick Thangavel’s public record is useful because it keeps that operating…
CASE FILE
The Challenge Released the Message. It Still Had Not Reached the List
The IETF plans to replace the machinery behind its email services on 11 September. The design usefully separates challenges, list handling, identity rewriting, signing and outbound transport. It also makes the central operating question unavoidable: when one component reports…
IETF
When 255 Octets Stop Being Enough: RFC 9885 and Multi-Part IS-IS TLVs
A syntactically valid IS-IS LSP can leave a receiver with an incomplete entity when information crosses the 255-octet limit and the receiver processes only one TLV occurrence. RFC 9885 defines how to recognize and process those related occurrences without changing the underlying…
CASE FILE
The CRL Number Was Higher. RPKI Still Had to Ignore It: RFC 9829
A relying party retrieves two signed revocation lists from one publication point. The first carries the larger CRL Number. The second is the file named by the certificate and hashed on the issuer’s current manifest. A generic PKI instinct says to trust the larger counter. RFC…
AFNOG
AfNOG Publishes Fellowship Criteria, Not the Procedure That Applies Them
AfNOG’s published Abha Ahuja Bursary application page tells candidates what the fellowship is looking for. It identifies a selecting committee, lists eligibility criteria and says incomplete applications will not be considered. The reviewed page does not set out how those…
CASE FILE
The Trace Linked the Action. It Did Not Prove the Authority
A new IETF discussion list asks how an agent’s intent, delegation, changing permissions and external actions can be followed across services. The hard part is not inventing a universal trace identifier. It is preventing that identifier—and the agent’s own account of events—from…
History
The Router Saw a New Network. It Was a Shadow of Its Own Mapping: RFC 1504
The route looked newly learned and the number was locally valid. The awkward fact was that no second network had appeared. A number invented at one translation boundary had travelled around a redundant path, lost its lineage and returned as if it belonged to a stranger.
History
The Key That Could Change Mid-Connection: TCP-AO's Rollover Signal
Long-lived routing sessions made a simple operational question unusually dangerous: how can two endpoints replace an authentication key without dropping the TCP connection or guessing the same switching instant? TCP-AO answered with visible key identifiers and directional…
IETF
A Local Root Makes DNS Resilience an Operator-Controlled Failover Decision
RFC 8806 lets a recursive resolver answer root-zone questions from a complete local copy. The design can reduce dependence on a reachable remote root server and keep root queries off intervening networks. It also moves a consequential decision inside the operator’s own system…
CASE FILE
The Tag List Kept Its Order. It Still Lost Part of the Policy: RFC 9825
Four administrative tags left an OSPF area in the intended order. The next router supported only two. Its log said the list had been preserved; its policy engine therefore looked healthy. Yet the action-bearing tag had occupied the third position. No field was reordered, no…
IETF
The Label Arrived, but Did It Reach the Right Path? RFC 9884 and PSID Validation
A label can arrive at the intended egress and be popped there, yet still be associated with the wrong SR Policy, candidate path, or segment list. RFC 9884 makes that control-plane correlation testable with LSP Ping instead of treating reachability as proof of path identity.
CASE FILE
The Token Authorized the Tool. It Did Not Authorize These Arguments
OAuth can establish that an agent may call a payment, messaging or infrastructure tool. The dangerous decision comes one layer later: whether the exact destination, amount, command and live form state produced by the model are the act a principal or governed policy approved. An…
CASE FILE
The Header Said NOERROR. The Signed Body Said the Name Did Not Exist: RFC 9824
A security pipeline closed a nonexistent-domain alert because the DNS header said `NOERROR`. The validating resolver had reached the opposite conclusion from the signed NSEC evidence: the queried name did not exist. Neither observation was fabricated. One component had read the…
CASE FILE
The Older Service Record Won. The Service Had Already Moved
A name collision is supposed to stop a newcomer from impersonating an established local service. Put two registration proxies between the service and that local link, however, and the same safeguard can protect yesterday’s address from today’s legitimate update. DNSSD’s proposed…
CASE FILE
The EAP Method Succeeded. The Protected Session Still Needed a Second Witness: RFC 9820
The access controller displayed three green facts: the EAP method had succeeded, the Master Session Key had been exported, and the constrained device had been placed in the security domain. Only the first two facts could be reconstructed. No one could produce the protected…
CASE FILE
The IESG Approved Three ML-KEM Groups. The Registry Recommended None
An approved IETF document can define exactly how three post-quantum groups travel through TLS while leaving the deployment verdict deliberately unresolved. That is not bureaucratic ambiguity. It is a precise boundary between an interoperable mechanism, a registry coordinate and…
CASE FILE
The Switch Executed the Program. It Did Not Inherit the Right to Read, Rewrite or Decide: RFC 9817
A program that runs inside a switch or network interface card is no longer merely near the traffic. It can become part of the path by which traffic is classified, transformed, delayed, replicated or converted into a control action. RFC 9817 catalogs the opportunity and, more…
CASE FILE
All Three Attestations Were True. They Still Did Not Belong to the CSR Key
A certification request can arrive with one valid statement about an HSM, another about corporate ownership and a third about platform health. The dangerous moment comes when a certificate authority treats three successful checks as one joined fact. Revision 29 of an IETF draft…
CASE FILE
One Timer Drove Three IPv6 Decisions. The Counters Could Not Explain Which One
A network team changes one millisecond value on an IPv6 interface. Address resolution, reachability probing and duplicate-address detection all inherit it. The edit receipt is precise; the operational meaning is not, until the team joins the change to an interface, an epoch and…