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.

IETF

An MPLS Pipe Model Hides Transit Hops Without Erasing Hop-Limit Control

An MPLS operator chooses Uniform, Pipe or Short Pipe TTL treatment, while ingress, transit and egress LSRs apply model-specific push, swap and pop rules. The choice changes what an observer can see across a tunnel; it does not create the tunnel, authorize traffic or provide…

Sep 6, 2026
Two paired calendar tiles and one separate tile depict a two-day preference and an undefined one-day possibility.

AFNOG

AfNOG’s Two-Day Tutorial Preference Leaves One-Day Consideration Undefined

AfNOG’s 2007 call preferred two full days for tutorials and said one-day requests might be considered.

Sep 6, 2026
A variable TCP header of option blocks ends at a highlighted Data Offset boundary where the application-data region begins.

History

The Number That Told TCP Where Data Began: Data Offset

TCP's header can grow when options are present, so the first application byte cannot live at one fixed position. A four-bit field solves the ambiguity: Data Offset counts the complete header in 32-bit words. Options may end early and padding may remain, but the encoded…

Sep 6, 2026
Cyan and amber packet signals return through a validated feedback loop while multiple anonymous network junctions leave the congestion source unresolved.

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.

Sep 6, 2026

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…

Sep 6, 2026
A detailed checklist and a simpler suggestion card meet at an unresolved next-step junction.

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.

Sep 6, 2026
A TCP segment between two endpoints with a translucent pseudo-header feeding address, protocol and length context into its checksum.

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…

Sep 6, 2026
A cyan QUIC stream direction dissolves at a transport boundary while the opposite amber direction and remote application work continue.

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.

Sep 6, 2026
Learning-history paths pass through a transparent decision junction toward limited workshop seats and support.

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.

Sep 6, 2026

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…

Sep 6, 2026
Two control positions bracket a continuous TCP data sequence, placing SYN before the bytes and FIN after them.

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…

Sep 5, 2026
Learning-history paths pass through a transparent decision junction toward limited workshop seats and support.

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.

Sep 5, 2026
A protected close frame crosses a dark transport boundary while unfinished application work remains suspended above it.

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.

Sep 5, 2026

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…

Sep 5, 2026
A continuous TCP byte stream moves between two endpoint buffers as a PSH impulse encourages progress without creating a message boundary.

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…

Sep 5, 2026
Learning-history paths pass through a transparent decision junction toward limited workshop seats and support.

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.

Sep 5, 2026

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…

Sep 5, 2026
One TCP endpoint has lost its state while the other retains a connection, and a reset clears the mismatch.

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…

Sep 5, 2026
A bounded amber message crosses separate QUIC transport stages while faded drop paths remain apart from the receiver application.

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…

Sep 5, 2026
Learning-history paths pass through a transparent decision junction toward limited workshop seats and support.

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.

Sep 5, 2026