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.
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.
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…
IETF
QUIC Migration Can Fail Before the Connection Does
A QUIC connection can remain cryptographically alive while becoming unable to use a new path. The missing resource may be neither keys nor congestion window, but an unused connection ID supplied by the peer.
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.
IETF
QUIC's Three-Times Limit Is an Address-Validation Budget, Not DDoS Protection
A QUIC server can have the next handshake bytes ready and still be forbidden to send them. Before it knows that a client can receive packets at its claimed address, every received byte grants only a bounded amount of transmission credit.
AFNOG
AIS 2026 Promises Selected Recordings Without Naming the Selector
AIS 2026 is presented as a hybrid summit whose virtual entities will receive live-streamed sessions, interactive discussions and access to selected recordings. The word “selected” creates a governance question: who decides which sessions become part of the accessible record…
IETF
When a Drone ID Becomes a DNS Delegation: RFC 9886 and the Registry Chain Behind Remote ID
A Broadcast Remote ID can carry a compact DRIP Entity Tag (DET), while the public evidence needed to authenticate registry inclusion is distributed across reverse-DNS delegations, HHIT and BRID records, and a certificate chain. The practical question is therefore not only whether…
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.
IETF
The QUIC Spin Bit Is a Sample, Not a Latency SLA
A passive latency graph can go blank while a QUIC service remains healthy. The signal may have disappeared because an endpoint did not participate, traffic paused, or connection context changed—not because round-trip time became infinite.