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.
IETF
Treat-as-withdraw Contains a Malformed BGP Route Without Letting One UPDATE Reset the Session
A malformed BGP UPDATE once carried authority far beyond the routes it described: under the base error response, it could bring down the receiving session and remove every otherwise valid path learned across that adjacency. RFC 7606 narrows that blast radius. Where the receiver…
History
The One-Second Bet: How TCP Shortened Its Initial Retransmission Timer
Before TCP has measured a path, its first loss recovery rests on a guess. In 2011, the IETF cut that recommended guess from three seconds to one—and required the RTO to return to three seconds before data transmission if a shorter timer expired while the sender awaited…
AFNOG
AIS 2026 Names the People Shaping Africa’s Digital Future Without Publishing a Representation Method
AfNOG names five constituencies as the people shaping Africa’s digital future at AIS 2026. The current first-party page reviewed here does not publish how those constituencies are represented, selected or balanced.
IETF
A BLACKHOLE Community Requests Discard Without Granting a Neighbor Unlimited Routing Authority
A DDoS victim may need traffic discarded before it reaches a congested interconnection, but asking a neighboring network to destroy reachability is an unusually powerful request. RFC 7999 standardizes that request while surrounding it with prior agreement, prefix authorization…
Leaders
Prasanna Premachandra and the School Network That Turned Mobility Into Learning Time
A dropped wireless connection between classrooms looks like a small technical fault. Multiplied across a school day, it becomes lost teaching time, unequal access and a recurring demand on support staff. Prasanna Premachandra’s public record offers a tightly bounded case of how…
CASE FILE
The Two Letters Were Not the Whole Case: Virtual Works v Volkswagen and the Call About `vw.net`
A two-letter domain can look like a conclusion. `vw.net` resembled Volkswagen's famous mark, and short addresses were scarce. But the Fourth Circuit refused to make resemblance do all the work. Its judgment followed a sequence: what Virtual Works' principals discussed when they…
History
The Standard That Required Two Answers: TCP-AO's Cryptographic Baseline
Algorithm agility sounds like freedom of choice. For TCP-AO, RFC 5926 exposed the harder half of that promise: two endpoints could each support sound cryptography and still fail to authenticate a single segment unless they shared one precise MAC-and-key-derivation pair.
AFNOG
AIS 2026 Says Conversations Become Progress Without Publishing an Outcome Ledger
AfNOG presents AIS as a place where conversations translate into real progress. The current first-party page reviewed here does not publish the outcome ledger that would separate discussion from commitment and show follow-through.
IETF
A Graceful Shutdown Community Declares Maintenance Without Taking the Neighbor's Routing Authority
Planned maintenance is a local decision, but the traffic it moves belongs to an interconnection. RFC 8326 gives one network a standard way to say that an EBGP path is about to disappear while leaving the neighboring network in control of its own route preference. That…
History
The Translator That Changed the Authenticated Connection: TCP-AO and NAT
A middlebox can change a packet without changing its route. TCP-AO made the consequences depend on what changed: rewriting a TCP option could be accommodated by authenticating fewer fields, but rewriting an address or port changed the identity of the protected connection itself.
AFNOG
AIS 2026 Names Its Organisers and Host but Not Their Decision Boundaries
AIS 2026 publicly names AfNOG and AFRINIC as joint organisers and TESPOK as host. The current first-party page reviewed here does not say which institution decides what when their roles meet.
AFNOG
AIS 2026 Calls Distance No Barrier Without Publishing a Hybrid Participation Standard
AIS 2026 promises live streams and interactive discussions and says distance is not a barrier. The current first-party page reviewed here does not publish the service and remedy standard behind that commitment.
History
The Reset That Could Not Be Trusted: TCP-AO After a Peer Reboot
TCP normally has a blunt way to tell a peer that an old connection no longer exists: send a reset. TCP-AO makes that answer harder to trust on purpose. When a protected peer reboots and forgets its connection state, the reset it can still send may be precisely the reset the…
AFNOG
AIS 2026 Names the Power to Exclude but Not a Meeting Appeal Route
AIS 2026 makes one end of its conduct system clear: AFRINIC may exclude a registrant from the meeting, including chat or other communication channels. The public pages reviewed for this article do not make the full meeting-specific decision and review chain equally visible.
IETF
An Extended DNS Error Explains Failure Without Authorizing a Different Answer
A DNS failure can be technically correct and operationally opaque. RFC 8914 lets a responder attach a more precise explanation to the result, but it deliberately leaves the result itself unchanged. That separation gives operators a useful observability channel—and creates a…
AFNOG
AIS 2026 Can Change Its Attendance Terms Without Publishing a Notice Rule
AIS 2026 says its attendance terms may be amended and become valid upon publication. It also treats attendance after a change as confirmation that a registrant has accepted it. The reviewed terms do not say how a consequential change will be brought to each registrant's attention…
AFNOG
AIS 2026 Requires an ID Upload Without Publishing Its Handling Rule
AIS 2026 asks every registrant to upload a passport or other government-issued identity document. The public registration and terms pages explain several uses of attendee information, but the reviewed text does not explain the specific lifecycle of that required file.
IETF
The Insecure Middle of a Secure TACACS+ Migration: RFC 9887 and the Cost of Dual-Stack Authentication
A TACACS+ client using TLS must not fall back to non-TLS when TLS negotiation fails. Yet a migration can temporarily keep separate non-TLS TACACS+ servers for devices that cannot move at once. That coexistence is not a secure dual stack: RFC 9887 considers the mixed phase…
History
The Segment That Returned to the Same Number: TCP-AO's Sequence Number Extension
A TCP sequence number can come back during one long-lived connection. TCP-AO had to ensure that the repeated 32-bit value did not also repeat the evidence presented to its authenticator.
CASE FILE
The Notification Arrived. One Backend Still Had Nothing to Serve
The IETF is asking for final comments on a proposed operating guide for RPKI publication services. Its sharpest rule is also the easiest to violate during a routine rollout: do not expose the new notification until every snapshot and delta it names is already available. An index…