Primary Domain
Internet Infrastructure
Within the Primary Domain facet, Internet 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 Unknown Attachment Was Not Text: RFC 2049’s Minimum Promise
MIME conformance did not mean that a mail program understood every format. In 1996 it meant something smaller and more useful: decode the common transfer forms, preserve the distinction between text and opaque bytes, and retreat predictably when a type was unknown.
History
The Packet Knew Its Place. It Did Not Prove the Picture: RFC 2035’s Reconstruction Boundary
RFC 2035 made Motion-JPEG economical on RTP by omitting stable JPEG syntax and repeating only the context needed to rebuild it. Fragment offsets and restart boundaries made damaged frames more tractable, but their evidence ended before decoded integrity, timely playout or a…
IETF
The Server Accepted the View. It Did Not Authorize the Write
An expired 2020 NETMOD proposal tried to let each NETCONF session or RESTCONF request select a versioned YANG view. The useful question is not whether a schema-set name was accepted, but which authority—and which evidence—survives after that acceptance.
History
The Server Said Why. It Did Not Prove It: RFC 2034 and SMTP’s Diagnostic Boundary
RFC 2034 gave mail systems a finer vocabulary without asking them to surrender human explanation. Its three-part status token made replies easier to classify across software and languages, but the evidence still stopped at what one server declared during one exchange.
IETF
The Tag Survived the Mask. The Node Still Proved Nothing
Revision 11 of an expired NETMOD draft turns node classification into a composed operational view: automatic tags, intended user choices, and exact-match masks meet in one visible set. That set is useful for discovery. It is not a certificate of what the node is, does, or…
History
The Bytes Kept Their Delimiters. Meaning Still Needed Another Contract: RFC 2044
UTF-8's first Internet-era promise was not that software had learned every language. It was that multilingual characters could enter systems built around ASCII without hiding an ASCII delimiter inside a multibyte character. RFC 2044 made that promise inspectable at the byte…
History
Demi Getschko and the Country Code That Arrived Before Brazil Spoke TCP/IP
On 18 April 1989, `.br` entered the DNS root while Brazilian academic networks were still speaking BITNET, HEPnet and other protocols. Demi Getschko's part in that sequence reveals a neglected infrastructure skill: securing a durable name, accepting responsibility for it and…
IETF
A Green Check Without Its Schema Is Not Evidence
Revision 00 of an expired NETMOD draft proposed two ways to validate YANG `anydata`. The interesting divide is not pass versus fail, but whether the receipt preserves the schema context and whether constraint checks ran at all.
History
One PPP Link, Two SNA Permissions: What RFC 2043's Open State Could Not Prove
A line can be up while the thing an operator cares about is still down. RFC 2043 made that distinction unusually concrete: on one PPP link, SNA with LLC 802.2 and HPR SNA without LLC were admitted by different control protocols. Each could open without speaking for the other, and…
CASE FILE
The Private Number Was Valid. The Instruction Was Still Unowned: RFC 9752
A vendor payload can cross a stateful PCEP session with a real enterprise number and perfect framing while leaving the decisive questions unanswered: who published its meaning, what the PCC was allowed to do, what the device installed, and what the traffic experienced.
History
The Next Macroblock Could Start Cleanly. The Picture Was Still Damaged: RFC 2032
RFC 2032 gave an H.261 receiver a deliberate place to resume after packet loss and a compact way to ask for corrective action. Neither mechanism certified that the missing picture returned, that prediction state was right, or that a viewer saw an uninterrupted frame.
History
255 Was a Workshop Tag, Not a Private BGP Namespace: RFC 2042
Two unfinished BGP attributes could both wear the number 255 and still mean entirely different things. That was the point. In RFC 2042, the value marked work under development; public identity began only when an attribute was documented and IANA assigned it a unique code.
CASE FILE
The Message Continued. The Constraint Went Missing: RFC 9753
RFC 9753 lets stateful PCEP peers keep working when selected entities are optional. That is a useful availability mechanism. It is not evidence that the ignored meaning survived, that the replacement LSP is equivalent, or that forwarding remained safe.
IETF
The Template List Was Present. The Intended Configuration Was Not Yet Proven
Revision 03 of the YANG configuration-templates draft turns list order and ancestor depth into configuration semantics. Reconstructing the intended tree is therefore possible only from a complete, same-version evidence bundle—and even a perfect reconstruction stops before…
Story
AFRINIC’s ccTLD Map Counts 27. Three Require an Address Join.
AFRINIC’s new DNS surface gets the total right, but it does not show the work behind the number. Twenty-four of its 27 ccTLD rows name the registry in a delegated hostname. Somalia, Nigeria and Mali become legible only when their nameserver addresses are joined to AFRINIC’s…
History
Ginny Strazisar and the Gateway Code That Traveled Before the Packets Did
The celebrated packet path began with a less cinematic journey: an engineer arriving at a site where the machine for her software was not yet ready. Virginia “Ginny” Strazisar Travers helped turn internetworking from a protocol idea into installed boundary equipment at BBN…
History
The Clock at the Edge: RFC 2030 and the Evidence Lost When One Reply Becomes Time
RFC 2030 made Internet time small enough for simple devices by preserving the NTP packet while discarding most of the machinery around it. Its warning was architectural: an SNTP client belonged at a leaf, not in the middle of a dependency chain, because one usable reply could set…
IETF
A Green YANG Validator Cannot Recover the Requirement NAIM Never Received
NAIM proposes a disciplined relay from natural language to canonical JSON, human review, model context and generated YANG. Its strongest contribution may be showing exactly where confidence must stop: a successful conversion is evidence about one representation chain, not proof…
History
Karen Sollins and the Delayed ACK That Made Every Packet Appear Twice
TFTP could deliver a file correctly and still damage the network carrying it. In the failure later called the Sorcerer’s Apprentice syndrome, one delayed acknowledgement could start a feedback loop in which every remaining data block and acknowledgement travelled twice. Karen…
CASE FILE
The Controller Said Done. The Packets Had Not Testified: RFC 9757
RFC 9757 gives a PCE an experimental vocabulary for coordinating Native IP paths, but its acknowledgements end inside the controller–client conversation. Leadership still needs independent proof that BGP, routing policy, forwarding hardware and live traffic enacted the same…