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
When a YANG Name Survives Revision: RFC 9890 and the Registry Identity Boundary
A revised YANG module keeps the initial module name and XML namespace. That makes a stable registry identity useful for locating the module, but it does not by itself identify the deployed revision or prove semantic compatibility. The operational question is therefore precise…
History
The Clock Moved Only for Useful News: How TCP Tied Its Timer to New Acknowledgment
An acknowledgment can arrive without changing what a TCP sender knows. RFC 6298 made that distinction control the retransmission clock: progress receives a fresh interval, repetition does not.
AFNOG
AfNOG’s Host Call Strongly Prefers Prior Workshop Familiarity Without Publishing an Equivalent Path
AfNOG’s dated host call strongly prefers hosts familiar with its workshop requirements through prior participation. The reviewed page does not publish an equivalent proof route for a first-time host.
IETF
Extended BGP OPEN Removes a 255-Byte Ceiling Without Making Every Peer Ready for More Capabilities
BGP speakers announce capabilities before they exchange routes, but the original OPEN message gives all optional parameters together only one octet of length. RFC 9072 removes that 255-byte aggregate ceiling by defining an extended encoding. The change creates room; it does not…
IETF
When 5G Slice Intent Reaches the Transport Network: RFC 9889 and the Handoff Control Boundary
An S-NSSAI that the transport domain cannot see must cross a handoff through a VLAN, IP or MPLS identifier before it can be bound to a transport service. That identifier is a translation point, not a complete promise of isolation, quality or capacity.
AFNOG
AfNOG’s Host Call Makes Impact a Selection Criterion Without Publishing How It Is Measured
AfNOG’s published hosting page gives preference to locations where a local workshop and meeting would have the greatest impact. The reviewed page does not define that comparative standard or publish how selection reasons are recorded.
History
The Old Mean Had to Move Last: How TCP Kept Its Timeout Variance Honest
A new round-trip measurement does two jobs inside TCP: it changes the expected delay and tests how wrong that expectation was. RFC 6298 fixed the order so the sample could not soften its own surprise before variance was recorded.
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.