Primary Domain
Infrastructure
Within the Primary Domain facet, Infrastructure intelligence groups reporting by primary domain so readers can follow a focused area of internet infrastructure, governance, connectivity markets, or digital capital. The page brings together related articles, public evidence, institutions, companies, people, regional exposure, operating dependencies, and market context that may otherwise sit across separate category pages. It explains the domain, the likely actor class, the market or governance context, and the source material readers should use when comparing signals. Operators, analysts, and governance readers can see how the same domain appears across events, profiles, market shifts, public-source evidence, regional dependencies, and longer-cycle infrastructure decisions over time.
IETF
A Valid QUIC Retry Tag Does Not Authenticate the Server
The Retry integrity check binds a packet to an observed Initial, but identity, token acceptance and client-address validation remain separate facts.
IETF
Enhanced Route Refresh Draws a Reconciliation Boundary Without Resetting the BGP Session
Enhanced Route Refresh Draws a Reconciliation Boundary Without Resetting the BGP Session intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
IETF
When Caller Identity Leaves SIP: RFC 9888 and the Control Plane Behind Out-of-Band STIR
A call can cross a gateway that cannot preserve an SIP Identity header while the PASSporT moves separately over HTTPS to a destination service provider’s Call Placement Service (CPS). RFC 9888 therefore treats caller-identity delivery as a control-plane problem: discover the…
AFNOG
AIS 2026 Invokes Decades of Collaboration Without Publishing an Institutional Memory Trail
AfNOG describes AIS as a long-standing community of practice in which each edition builds on decades of collaboration. The current first-party page reviewed here does not publish the cross-edition trail that would make that institutional memory inspectable.
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…
IETF
A QUIC Key-Phase Change Proves New Keys Worked, Not Why They Changed
A successful transition to the next packet-protection keys confirms protocol progress on one connection; it does not explain the policy, incident or deployment that caused the change.
Story
RIPE Database Now Composes Unicode. The Text Chain Needs a Normalisation Receipt
One visible name can arrive as two different code-point sequences. RIPE Database release 1.123 deliberately makes those sequences converge before the value passes through its remaining UTF-8 controls. That is good interoperability. It is also the moment when an evidentiary chain…
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…
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.
IETF
A QUIC Stateless Reset Proves a Token Match, Not Why State Was Lost
A client can recognize that its peer no longer has usable QUIC connection state without learning which machine, deployment or routing decision made that state disappear.
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.