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 Suffix Knew the Grammar, Not the Meaning: RFC 3023
A MIME dispatcher could read the final four characters of `application/foo+xml` and learn something useful: an XML processor might open the representation. It still could not know what `foo` meant, which operations were safe, or whether the document was allowed to cause an…
History
A Complete COUNTER Is Still a Proposal: Authority and State in RFC 2446
*The original iTIP model separated a fully specified alternative event from the authority to change the organizer’s master calendar entry.*
History
The Broadcast Address Became a Router: RFC 3021
On an ordinary IPv4 subnet, an address whose host bits are all ones had long carried broadcast meaning. RFC 3021 made that same bit pattern identify one router—provided the link really had only two ends and both ends understood the exception.
History
The Bundle Turned Green When One Link Survived: RFC 3020
RFC 3020 made several Frame Relay circuits look like one logical interface. It also made “up” a configurable predicate: sometimes one surviving link was enough. The green state was useful, but it was a receipt for a policy threshold—not for full capacity, intact ordering or…
History
The Cache Row Said a Group Had Members. Management Could Have Created It: RFC 3019
RFC 3019 gave operators a table of IPv6 multicast membership. The same table let management create or delete rows and declare the local machine a member. Its most useful historical lesson is therefore not that a row was false, but that its origin and evidentiary limit had to…
History
The Transaction Was Atomic. The Remote Call Was Not Reversible: RFC 3018
RFC 3018 imagined a network in which software could read memory, allocate storage and transfer control across machines as if the distance had disappeared. Its transaction could release a bundle all at once. Once a remote call ran, however, the protocol offered no universal road…
History
The Phone Book Had a New Version. The Traveler Still Had No Freshness Proof: RFC 3017
A roaming dialer could hold a well-formed XML book, see that its counter had increased and still act on the wrong operational state. RFC 3017 standardized the bundle that selected and configured access; it deliberately left delivery, authentication, commit and observed service to…
History
The Codec Survived. The Packetizer Chose What One Loss Could Destroy: RFC 3016
An MPEG-4 encoder could preserve every syntax rule and still hand the network a fragile unit. RFC 3016 made the overlooked decision visible: before redundancy, retransmission or decoding, someone had to decide which pieces would fail together.
History
The Context Was Connected. The Call Was Not Proven: RFC 3015
Megaco gave a decomposed media gateway a precise local model of who could hear or see whom. RFC 3015 also showed why a successful command, a visible Context and a returned statistic were not yet receipts for an end-to-end conversation.
History
The Notification Was Lost. The Backup Log Could Lose It Too: RFC 3014
A trap could disappear on the wire, so RFC 3014 gave the device a second memory. Then it did something rarer: it specified how that memory could be filtered, shortened, overwritten, reset and contested—and how an operator might notice the resulting hole.
History
The Gate Issued a Challenge. Trust Still Had to Arrive: RFC 3012
In a visited network, the first useful question was not yet “Who are you?” It was narrower: “Are you answering something I just said, or replaying an old registration?” RFC 3012 made that distinction visible without pretending it had completed the work of trust.
History
The Packet Came from One Subnet. The Address Was for Another: RFC 3011
DHCP once treated a packet’s arrival path as a practical clue to the address pool it needed. RFC 3011 made that clue overridable—and forced operators to decide who was allowed to point beyond the local pool.
History
The Server Forgot the Lock. Recovery Began by Refusing New Ones: RFC 3010
NFS version 4 turned a crash into an argument over remembered rights. RFC 3010 answered with a bounded order: identify the returning client, let old state be reclaimed, and keep new conflicts outside until that opportunity had passed.
History
The Signature Verified. The Resolver Still Asked Who Was Allowed to Sign: RFC 3008
A correct cryptographic result did not yet make a DNS signature authoritative. RFC 3008 gave resolvers a second question: was this the kind of key that could speak for the zone data it signed?
History
The Sender Promised the Flow Would Shrink. The Router Policed the Promise: RFC 3006
A 48 kbit/s stream could be admitted as 33.6 kbit/s when a link could compress its headers. RFC 3006 made that discount local, conditional and enforceable against the flow that asked for it.
History
The List Was Open. Posting Was Conditional: RFC 3005 and the Moderation Boundary of the IETF
The IETF’s broadest mailing list invited technical and procedural argument from an open community. Its 2000 charter also named who could stop a pattern of abuse—and who could hear the complaint when that power was used.
History
NAT Was a Border Function. RFC 2993 Showed the Work It Sent to Applications
The address translator could leave ordinary web traffic untouched and still change what the Internet meant to an application. In 2000, RFC 2993 mapped the hidden work: address-bearing protocols needed gateways, endpoint updates and local name administration wherever translation…
History
The Namespace Was Global. Resolution Was Not: RFC 3001, RFC 3061, and the Authority Hidden in `urn:oid`
A name can travel everywhere without telling anyone where to look. When the IETF carried entity identifiers into URN syntax in 2000, it preserved a delegated system of authority—and left resolution, validation and trust outside the string.
History
Equal Cost Did Not Make the Paths Interchangeable: RFC 2991 and the Price of Stable Multipath
Two routes can tie in the routing table and still disagree about packet size, delay and what a probe can see. In 2000, RFC 2991 made the router’s choice among those paths a question of how much disruption a network was willing to accept.
History
The Fourth Packet Was Certain to Drop. That Still Wasn’t the Result.
In 1998, a small TCP simulation put an awkward objection on the table: if a modem-facing router can hold only three packets, a four-packet opening flight must lose one. The experiment accepted that loss as certain, then asked a harder question—what happened to the connection when…