Skip to main content

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.

An abstract African map links several host-readiness nodes to a shared technical summit forum.

AFNOG

AfNOG’s Host-Selection Rules Turn Infrastructure Capacity Into Convening Power

An archived Africa Internet Summit hosting call shows that choosing a host is both an operational-risk decision and a distribution of institutional attention.

Sep 5, 2026
A blue packet path reaches an amber delay chamber inside the receiver before an acknowledgment returns along a separate arc.

IETF

QUIC ACK Delay Is Not Network Latency

ACK Delay is a receiver’s report of intentional waiting for one acknowledged packet. It is useful to RTT estimation, but subtraction alone cannot turn it into a network-only measurement.

Sep 5, 2026

IETF

A Route Reflector Scales IBGP by Centralizing Dissemination, Not Route Authority

The full mesh disappears, but the decision point does not. RFC 4456 lets a route reflector redistribute an IBGP-learned route to selected internal peers, replacing a session-count problem with a governed dissemination hierarchy. The reflector can scale reachability, yet its…

Sep 5, 2026
A protective hourglass around a closed TCP endpoint is fractured by a red reset reflected from a stateless peer, while a separate guarded path preserves evidence for safe connection reuse.

History

The Reset That Ended Waiting Too Soon: TCP's TIME-WAIT Assassination Hazard

TIME-WAIT looks passive: a closed connection remains in a table while a clock runs down. In 1992, RFC 1337 showed that the state could be destroyed by active protocol behavior. One old segment provoked an acknowledgment; that acknowledgment provoked a reset; the reset erased the…

Sep 5, 2026
An abstract glass service award at the centre of connected African technical-community collaboration.

AFNOG

AfNOG’s NII Service Award Turns Recognition Into a Governance Signal

AfNOG’s published award language does more than celebrate individuals. It identifies service, sustained technical contribution and mentorship as conduct the institution wants its community to value.

Sep 5, 2026
Three network connectors lie unplugged beneath preserved empty sockets beside an intact archival card index, showing port bindings retired while registry history remains traceable.

IETF

The Ports That Outlived Their Protocols: RFC 9900 and the Discipline of Giving Numbers Back

Ports 831, 832, and 833 can persist in diagrams, service files, and filters even after the NETCONF transports once attached to them never reached known production deployment. RFC 9900 therefore retires the number bindings without erasing their semantic history.

Sep 5, 2026
Three separately protected QUIC packets leave one translucent UDP datagram envelope on independent processing paths.

IETF

QUIC Coalescing: Efficient Wire Use, Separate Delivery

Putting several complete QUIC packets into one UDP datagram can reduce carriage overhead during the handshake. It does not turn those packets into one protected entity, one acknowledgment event, or one application result.

Sep 5, 2026

IETF

Four-Octet ASNs Expand the Namespace While Compatibility Still Rewrites the Path

Four-Octet ASNs Expand the Namespace While Compatibility Still Rewrites the Path intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that…

Sep 5, 2026
One funded journey reaches a technical meeting node, from which knowledge pathways branch toward local and regional communities.

AFNOG

AfNOG’s Bursary Criteria Turn Travel Funding Into a Knowledge-Sharing Mandate

A dated AfNOG-hosted bursary application ties individual travel support to the ability to reuse and share meeting knowledge within an African country and region.

Sep 5, 2026
A central reusable ACL policy set organizes several match groups and connects to multiple ACL panels and network devices, with an amber change moving through validation to green deployment across a visible dependency map.

IETF

One Name, Many Rules: RFC 9899 and the Control Surface of Reusable ACL Sets

A security team changes one named prefix set once, and every ACL that references it can inherit the change without rewriting each parent rule. That mechanism is the promise—and the control problem—behind RFC 9899’s reusable policy entities.

Sep 5, 2026
A TCP data path passes through an independent middlebox while a small repeating clock drives retransmissions and a larger red deadline arc marks the connection’s final user timeout.

History

The Deadline That Was Not a Retransmission Timer: TCP User Timeout

TCP can decide to retransmit a segment and still decide, on a different clock, that the connection has waited too long. The first decision schedules another attempt. The second ends the connection. RFC 5482 made that persistence preference visible to a peer without turning it…

Sep 5, 2026
An IPv6 router connects three host-isolation arrangements: individual routed host islands, separate logical prefix zones on a shared medium, and partial Layer-2 multicast cells, while three incoming pressure streams are filtered differently.

IETF

Shrink the Trust Domain: RFC 9898 and the IPv6 Neighbor-Discovery Isolation Choice

On one IPv6 access segment, three different root causes can surface together: multicast load, implicit trust of every on-link node, and router Neighbor Cache Entries created on demand. The practical question is therefore not which symptom to patch, but which part of the Neighbor…

Sep 5, 2026
A confirmation pulse retires the middle QUIC Handshake-key chamber while a separate application-readiness console remains incomplete and rejected early data resets.

IETF

QUIC Handshake Confirmation Is Not Application Readiness

A green dashboard can hide an important distinction: HANDSHAKE_DONE marks a transport and cryptographic transition, not a completed application transaction. Confirmation retires Handshake keys, but it does not certify early-data acceptance, backend health, durable storage, or…

Sep 5, 2026

IETF

A BGP Shutdown Message Explains the Decision Without Delegating the Restart

A session can disappear before an email thread catches up. RFC 8203 lets an operator place a short UTF-8 explanation inside an Administrative Shutdown or Administrative Reset notification. The explanation can connect a protocol event to a maintenance record, but it is not an…

Sep 5, 2026
A transparent two-key approval gate allows proportionate sponsor acknowledgement into a technical programme while redirecting exhibition-scale promotion.

AFNOG

AfNOG’s Sponsor-Visibility Gate Is a Governance Firewall, Not a Branding Rule

AfNOG’s hosting rules make sponsor advertising conditional on advance approval and the event’s non-commercial purpose. That gate is an allocation of authority, not a cosmetic branding choice.

Sep 5, 2026
Two endpoints exchange differently colored SYN option envelopes, with later TCP payloads bounded independently in each direction across a separate router path.

History

The Offer That Was Not a Negotiation: How TCP MSS Bounded Each Direction

Each side of a TCP connection can place a four-byte option in its opening SYN. The number does not settle a shared packet size. It says how much TCP data the option's sender is prepared to receive in one segment—a directional boundary that the other endpoint must combine with…

Sep 5, 2026
An established blue transport path runs above an amber advertised address; a second path turns green only after a bidirectional authentication and reachability gateway, while a red private-address branch is rejected.

IETF

Authenticated Is Not Reachable: RFC 9897 and the MP-DCCP Path-Join Boundary

An authenticated `MP_ADDADDR` advertisement is control data, not permission to send traffic on a new path. That path becomes usable only when `MP_JOIN` binds a new subflow to the original connection and completes the nonce/HMAC reachability handshake.

Sep 5, 2026
An archived message moves through visible correction, targeted redaction, attachment replacement and exceptional removal with a retained metadata trace.

AFNOG

AfNOG Treats Its Mailing-List Archive as a Technical Resource Without Publishing a Correction Policy

AfNOG presents its public mailing-list archive as a technical resource, but the reviewed pages do not explain how archived material is corrected, annotated or removed after publication.

Sep 5, 2026

IETF

A BGP Large Community Carries a Policy Signal Without Granting the Sender Authority

A BGP Large Community can carry an operator’s intent across network boundaries in a form that still fits four-octet ASNs. That portability is useful precisely because it is not command authority. The Global Administrator identifies the namespace whose documentation gives a value…

Sep 5, 2026
Two endpoint hourglasses flank a smaller silence boundary as three QUIC probe pulses cross and a middlebox path fades early.

IETF

QUIC Idle Timeout Is a Silence Limit, Not a Session Lifetime Promise

A thirty-minute `max_idle_timeout` can look like a promise that a session will remain usable for thirty minutes. It is narrower: a boundary for how long QUIC endpoint state tolerates qualifying protocol silence.

Sep 5, 2026