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 Octet That Changed Its Contract: From IPv4 Type of Service to DSCP and ECN
The second octet of the IPv4 header did not move, but its contract did. What began as precedence and desired service qualities became a configurable per-hop behavior selector plus an explicit congestion signal—a history of compatibility managed by redefining bits in place.
History
The Name Looked Complete. The Resolver Still Rewrote It: RFC 1535
`UnivHost.University.EDU` looks like an address already supplied. To one 1993 resolver, it was only the beginning of a search. Before asking for the rooted name the user appeared to mean, the software could manufacture three longer candidates, cross from a locally managed suffix…
IETF
RFC 9916 Draws the Line at PCEPS Early Data
A PCE controller can save one handshake round trip and still create a worse incident if path-control data is accepted before replay-safe handshake completion. RFC 9916 therefore treats the PCEPS session boundary as a control-state boundary: negotiate the newest supported TLS…
AFNOG
AfNOG’s Presenter-Cost Rule Waives Registration but Leaves Travel Support Unspecified
AfNOG’s 2007 call said presenters and tutorial instructors were expected to cover travel while being exempt from registration fees, but the cited page did not say beside that rule whether a travel-support exception route existed.
IETF
MPLS-TP Continuity Is Not Connectivity—the Source Identity Decides Whether a Live Session Is the Right Path
A BFD session can remain **UP** while receiving RDI, and recurring packets can arrive from the wrong maintenance endpoint. Continuity therefore proves neither that the intended source is transmitting nor that the live path is the correct connectivity relationship.
History
The Length That Outranked the Frame: Why IPv4 Counts Its Own Header
An IPv4 packet can sit inside a link-layer frame that is longer than the packet itself. The small field that resolves the ambiguity does more than count payload: it declares the complete IP datagram, header included, so the network layer keeps its own boundary when the enclosing…
IETF
A QUIC PADDING Frame Adds Wire Bytes, Not Transport Progress
A full-size Initial datagram can look reassuring on an operations dashboard. Its added bytes may still be only PADDING, with no content that advances the handshake or the application.
IETF
A Lease Is a State Machine: RFC 9915 Tightens DHCPv6 Authority
A client can receive an address successfully and still fail hours later when renewal, rebinding or delegated-prefix continuity crosses a server or relay boundary. DHCPv6 is therefore a state machine, not a one-shot response: the operational question is whether identity, lifetime…
AFNOG
AfNOG’s Reproduction-Permission Request Leaves the Licence Boundary Unstated
AfNOG’s 2007 call asked for permission to reproduce the contributor’s presentation after the event, including permission to post it on the AfNOG website. That sentence names two requested acts, but it does not state how long the permission would last, where it would apply…
IETF
An RSVP-TE Loopback Requires a Locked LSP—and the Target Node Still Controls the Test
A loopback request can reach a specifically addressed LSP node, but that target MUST ignore it unless the ADMIN_STATUS A bit proves that the LSP remains locked. The point is not a sovereign ingress command: it is a distributed authorization sequence.
IETF
The Root Writes the Shortcut: RFC 9914 Projects Routing State into RPL
A leaf-to-leaf packet may climb a stretched RPL DODAG path through the Root even when a shorter directional path exists. RFC 9914 lets the Root project a PCE-computed shortcut as routing state into selected nodes—improving path choice, but also making freshness, precedence…
History
The Number IPv4 Could Not Freeze: How the Protocol Field Became a Live Registry
IPv4 devoted one octet to a deceptively simple question: what protocol should receive the payload next? The answer could not live in the packet format alone. It required a shared assignment system that could change while the eight bits on the wire stayed fixed.
History
The Header Shrunk to One Octet. The Missing Bytes Moved into Shared State: RFC 1553
A packet crosses a slow link with a one-octet compression header. Its ordinary thirty-octet IPX header is absent. Nothing has been lost—if the receiver still holds exactly the right prior header in exactly the right slot. Let one earlier packet vanish, however, and the same…
IETF
Four Radios, One Control Problem: What RFC 9913 Reveals About RAW's Capability Plane
Four radio technologies can each advertise scheduling or redundancy while exposing different clocks, resource units, diversity primitives and failure correlations; their feature names are therefore not interchangeable assurance promises. This briefing by Theo March examines how…
IETF
A QUIC CRYPTO Frame Carries Handshake Bytes, Not a TLS Message Boundary
A protected packet can carry handshake bytes without proving what TLS has understood, accepted, or completed.
AFNOG
AfNOG’s Affiliation Field Names an Institution Without Defining the Relationship
AfNOG’s 2007 call requested a contributor’s affiliation without defining what relationship that label represented.
IETF
An RSVP-TE Hop Attribute Targets One Route Step Without Granting It Path-Wide Authority
An RSVP-TE Path message reaches the route step named immediately before an ERO Hop Attributes subobject. That adjacency fixes which hop the request addresses; the R bit then selects required or optional processing. It does not give the ingress path-wide authority.
History
Why IPv4 Checksums Only Its Header
A packet can carry an undamaged payload and still be dangerous to forward if a bit error changes its destination, length or remaining lifetime. IPv4 therefore checks the control surface routers must trust: its header, and only its header.
IETF
The Fast Path Is a Recovery Graph: RFC 9912 Moves Wireless Reliability Into the Network Plane
Wireless conditions can change faster than a controller can install a new route, so RAW preinstalls a finite recovery graph and lets a Point of Local Repair select protection paths locally. That is the architectural move: reliability becomes a network-plane control problem, not a…
CASE FILE
A RISC-V Profile Is a Compatibility Vocabulary, Not a Hardware Mandate
A RISC-V profile makes a useful promise of language, not a universal promise of hardware. It tells hardware and software communities which bounded instruction-set surface they can discuss together. It does not, by itself, tell a buyer what is on a particular chip, tell a…