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.
AFNOG
AfNOG’s Proposal-Type Field Names Formats Without Defining Their Evidence
AfNOG’s 2007 call named three proposal formats without publishing format-specific evidence fields.
IETF
QUIC 0-RTT Acceptance Is Replay Exposure, Not Commit
A latency dashboard can record accepted early data while the application is still deciding whether a repeated request may create a second side effect.
IETF
Every Cell Says Stop: RFC 9906 Completes ECC-GOST’s DNSSEC Retirement
Every affected ECC-GOST registry cell now says **MUST NOT**: RFC 9906 closes both the production and validation lanes, unlike RFC 9905’s SHA-1 compatibility transition. The result is not merely a recommendation to stop signing; it is a coordinated retirement covering signing…
AFNOG
AfNOG’s 200-Word Abstract Cap Leaves the Required Signal Unspecified
AfNOG’s 2007 call capped abstracts at 200 words without stating what those words had to establish.
Europe and Middle East Regional ISP Trends
Ray-Svyaz's 500 Mbit/s promotion leaves the post-promotion price unverified
MyCentra’s Sheregesh offer puts a 500 Mbit/s headline beside a 50% discount. The same official page says the discount lasts three months and then gives way to the main tariff agreed at connection. That makes the post-promotion price—not the launch price—the first economic fact a…
History
When IPv4 Identification Stopped Identifying Every Datagram
IPv4 still carries a 16-bit field called Identification in every header. Yet the current standard says that field has no meaning in an atomic datagram. The apparent contradiction records a deliberate narrowing: an identifier created to reunite fragments no longer has to pretend…
IETF
Stop Signing, Keep Reading: RFC 9905 Makes SHA-1 Retirement Asymmetric
RFC 9905 changes the DNSSEC operating rule at the algorithm-row level: the affected SHA-1 algorithms MUST NOT be used to create new material, while validator implementations MUST continue to support validation during the remaining installed-base transition. The result is…
IETF
MPLS Linear Protection Coordinates the Switch—but Priority Rules Decide Which Request Wins
A protection-domain endpoint receives local and remote requests, orders them by explicit priority, and moves selectors between a pre-provisioned working path and protection path. The leadership decision is therefore not whether PSC can invent a recovery route: it is whether both…
History
The Attachment Named Its Type. The Local Machine Chose the Command: RFC 1524
A multimedia message could say what it carried, but it could not legitimately appoint the program that would open it. RFC 1524 placed that decision in a local `mailcap` policy—a small indirection that made new formats portable across mail readers while exposing exactly where…
IETF
QUIC Payload Ceilings Are Not Path MTU
A peer's QUIC declaration describes what it is willing to receive. It does not describe what the network path can carry.
IETF
Four Cells, One Trust Chain: RFC 9904 Moves DNSSEC Algorithm Policy into the Registry
A DNSSEC algorithm number has four separately governed recommendation cells: validator implementation, signer implementation, validation use, and signing use. RFC 9904 changes where that guidance is maintained, not the recommendation status inherited on day one.
History
The Message Arrived Intact. Its Reading Order Still Had Three Owners: RFC 1556
A mixed Hebrew-and-English line could survive every mail relay with its characters unchanged and still arrive as a different sentence on two screens. RFC 1556 named the missing contract: transport had delivered the sequence, but somebody still had to own its order.
History
Why TCP Options Needed Both an End Marker and a No-Operation
TCP made room for future capabilities inside a header whose total extent still had to be known before payload could begin. Two deliberately small option codes—End of Option List and No-Operation—helped keep that variable space parseable without making every sender lay it out the…
History
The Repeater Had to Reply Before It Reset: RFC 1516
The management reply was designed to leave while the Ethernet repeater was still able to send it. Only then could the disruptive reset begin. RFC 1516 turned that small ordering rule into a durable warning: acknowledgement, action, completion and restored service do not share one…
History
The Internet Asked Who Would Have to Live With Its Next Protocol: RFC 1550
A utility meter and a wireless link appeared before any packet diagram. In RFC 1550, the search for a successor to IPv4 began by asking future users what the new protocol would have to endure—and by keeping the candidates temporarily out of the room.
History
The Alarm Had to Wait Five Seconds; the Counter Did Not: RFC 1515
Two bursts of an Ethernet fault could enter the same five-second window. A manager might receive one alarm, poll a normal state a moment later, and still find that the transition counter had advanced twice. In 1993, RFC 1515 made those answers coexist because an alert, a present…
History
The Standard Had to Work With the Feature Off: RFC 1547
On a metered line, a packet sent only to ask whether the other end is still alive can appear on the bill. RFC 1547 used that small operational conflict to establish a large design rule: if one site needs a feature and another must disable it, the common protocol still has to…
History
The Table Measured What an Application Could Use, Not the Disk: RFC 1514
A host can report a perfectly accurate disk capacity and a smaller, equally accurate amount of usable storage. The disagreement begins only when a manager strips away which layer each number describes. In 1993, RFC 1514 built that distinction into the Host Resources MIB: physical…
History
The Address Stayed the Same. The Server Did Not Have To: RFC 1546
In 1993, one ordinary-looking destination field was asked to do an unusual job: name a service offered by several machines while declining to name any particular machine. RFC 1546 called that experimental service anycasting. Its enduring lesson is less about shortening a path…
History
The Probe Counted Shortages, Not Missing Frames: RFC 1513
The counter moved from 41 to 42. How many frames had vanished? RFC 1513 gave the only responsible answer: the number did not say. It recorded one more occasion on which a monitoring probe ran short of resources, not the size of the unseen traffic behind that shortage.