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
QUIC ECN validation confirms a signal path, not the cause
A validated ECN feedback loop can guide congestion control on one path. It cannot identify the queue, hop, carrier or business impact behind a mark.
IETF
An MPLS Entropy Label Balances Flows Without Authorizing a New Path
The ingress LSR extracts selected flow keys, computes a load-balancing hash, and encodes that result as an entropy label (EL). Transit LSRs can then balance from the label stack without deep payload inspection. The mechanism changes the available load-balancing input; it does not…
AFNOG
AfNOG’s Parallel Invitation for Suggestions Makes Next-Step Discretion Visible
AfNOG’s 2007 call listed a detailed proposal package, then welcomed suggestions and expressions of interest even without all the requested information.
History
The Header That Was Never Sent: Why TCP Checksums IP Addresses
TCP validates more than the bytes in its own segment. Before calculating or checking the mandatory checksum, each endpoint conceptually places selected IP fields in front of the TCP header: the source and destination addresses, protocol identity and TCP length. This pseudo-header…
IETF
QUIC STOP_SENDING Ends a Stream Direction, Not the Remote Operation
A transport signal can stop incoming bytes without proving that the work behind those bytes was never started, accepted, or completed.
AFNOG
AfNOG’s Contradictory 2007 Deadline Turns Calendar Accuracy Into a Governance Control
AfNOG’s archived 2007 call published a proposal deadline after the event while placing notification and programme publication months before that deadline.
IETF
BFD Shortens Failure Detection Without Deciding Which Route Should Survive
Bidirectional Forwarding Detection can tell a routing or service application that a forwarding path has stopped working with far less delay than many protocol-native timers. That speed is useful precisely because BFD does not own the larger decision. Operators still determine…
History
The Two Flags That Took Up Space: Why TCP Counts SYN and FIN
TCP numbers bytes, yet two control events also advance its sequence space. SYN stands before the first data octet and FIN stands after the last, giving connection opening and closing the same acknowledgment and retransmission protection as the stream without turning either flag…
AFNOG
AfNOG’s Speaker-Cost Rule Separates Programme Access From Travel Support
AfNOG’s 2007 call waived registration for presenters and instructors but expected them to fund their own travel because organisational funds were limited.
IETF
QUIC CONNECTION_CLOSE Ends Transport State, Not the Business Process
A transport shutdown is a precise network event, but it is not a receipt for every business action still moving through the connection.
IETF
A BGP Confederation Hides Internal Topology Without Erasing Internal Policy Authority
A large network can divide itself into smaller BGP policy domains while still presenting one autonomous-system number to the outside world. RFC 5065 makes that boundary operationally useful, but not costless. The Member-AS structure hidden from external peers still decides how…
History
The Push That Was Never a Message Boundary: TCP's PSH Flag
An application asks TCP to push a buffer because waiting for later data could stall the exchange. TCP marks the last segment it creates from that buffer with PSH. Yet the mark does not turn that segment into a message: the sender's write, the packets on the wire, the receiver's…
AFNOG
AfNOG’s Reproduction-Permission Rule Turns a Talk Into a Commons Asset
AfNOG’s 2007 call asked contributors not only for a proposal, but also for permission to reproduce and publish the resulting presentation.
IETF
An Origin Validation Community Carries a Trust Decision Without Delegating Import Policy
An Origin Validation Community Carries a Trust Decision Without Delegating Import Policy intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
History
The Connection One Side Forgot: TCP's Half-Open Reset
A TCP connection can look alive from one endpoint and already be gone from the other. The classic specifications called that split a half-open connection. Their recovery examples turn the next packet into a test of shared memory: sequence expectations collide, a reset makes the…
IETF
QUIC DATAGRAM Keeps Message Boundaries, Not Delivery Guarantees
A QUIC DATAGRAM frame can carry a complete application datagram without retransmission or ordering relative to other DATAGRAM messages. That makes it useful for time-sensitive information, but it does not turn local submission or packet acknowledgment into a receipt for the…
AFNOG
AfNOG’s Repeat-Attendance Rule Turns Training History Into Access Authority
AfNOG’s 2005 workshop notice made prior training, subsequent use, available space and financial support part of a single access decision.
IETF
A 65,535-Octet BGP Message Is a Negotiated Capacity, Not Network-Wide Permission
A router can accept a 65,535-octet UPDATE from one peer and still be unable to carry that announcement across the next session. RFC 8654 expands the BGP envelope only after a bilateral capability signal. At mixed-support boundaries, the operator inherits a harder decision…
History
When Both Sides Knocked at Once: TCP's Simultaneous Open
The standard picture of TCP begins with a client knocking and a server listening. The protocol itself has never required that casting. Its original 1981 specification described what happens when two endpoints knock at once: their SYN segments cross, each side becomes both…
AFNOG
AIS’s Shortlist Rule Turns Agenda Time Into Editorial Authority
The AIS 2025 presentation call invited a wide technical community, then made clear that limited programme time would place only shortlisted abstracts on the agenda.