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 Model Could Describe the Rule. It Left the Result to Devices: RFC 3060
RFC 3060 gave policy systems a shared vocabulary of groups, rules, conditions and actions. It did not give every router one shared interpreter. The standard could describe when a rule applied and even mark an action order as mandatory or recommended, while leaving the algorithm…
History
The D-Channel Stayed Put When Call Control Moved to IP: RFC 3057
RFC 3057 did not drag the ISDN line into the Internet. It stopped at the boundary: the Signaling Gateway still terminated Q.921, while IUA carried the upper signaling relationship to a call-control process across SCTP. Its redundancy model could move signaling traffic when an…
History
The Counter Said the Call Succeeded. It Could Not Say Whether a Person Heard It: RFC 3055
In 2001, the PINT working group gave operators a disciplined way to count Internet-triggered telephone services. RFC 3055 could distinguish received, successful and disconnected calls across users, clients and gateways. Its greater lesson lies in the distance it preserved: a…
History
The 14 kHz Upgrade Kept a 16 kHz Door Open: RFC 5577
RFC 5577 widened the G.722.1 audio profile and added a faster sampling clock. Its most revealing migration rule was quieter: keep offering the 16 kHz configuration when older terminals still matter.
History
The Phone Named Its Parts. The Controller Still Had to Ask What Was There: RFC 3054
RFC 3054 gave an Internet telephone a shared vocabulary for its display, keys, handset, speaker and media stream. The IPPhone profile let a remote controller begin with a known model instead of guessing a device from an arbitrary inventory. That shortcut reduced inference. It did…
History
The Root DSE Could Name Its Vendor. RFC 3045 Drew the Line at Capability Discovery.
An LDAP server could tell a client who made its software and which release string it reported. That was useful context for a human—or a narrowly targeted workaround—but it was not a feature list. RFC 3045 made the distinction explicit: a vendor label might help explain an…
History
The ISSN Stayed. The URLs Moved. RFC 3044 Built a Watcher Between Them
In 2001, the ISSN International Centre showed how a familiar serial number could travel inside a URN. The harder part was never printing the number. It was keeping the route from that number to a journal’s changing web address honest. RFC 3044 said the identifier could persist…
History
The Broker Ordered the Tunnel. Another Machine Had to Carry It: RFC 3053
RFC 3053 made an awkward early-IPv6 task look like a service: register, supply an IPv4 endpoint, receive configuration and connect. Its architecture also exposed a boundary that service language can hide. The Tunnel Broker made allocation and configuration decisions; a Tunnel…
History
A Global Name, One Authoritative Resolver: The Promise and Limit of RFC 3043
In January 2001, Network Solutions proposed a durable Internet name for people and organizations. RFC 3043 made the reference portable across applications, but its own registration template placed authoritative interpretation inside the company’s resolver. The distinction still…
History
The Standard Recommended LDP. It Did Not Prove the Protocol Was Running: RFC 3037
RFC 3037 recommended LDP for devices that carried MPLS traffic along normally routed paths. That sentence selected an appropriate protocol function; it did not certify a device, enable a feature, establish a TCP session, install a label or move a packet. The applicability…
History
Two Duplicate ACKs Could Send New Data, but Not Enlarge the Window: RFC 3042
A TCP sender with a three-segment congestion window loses one segment. The receiver can return only two duplicate acknowledgments for the later data, one short of the threshold that would trigger Fast Retransmit. In 2001, RFC 3042 proposed a narrow way to keep the feedback clock…
History
The ATM Label Changed at Every Switch. LDP Needed One Both Ends Could Share
An ATM circuit could keep carrying cells while the number printed in its VPI/VCI field changed at the next switch. LDP peers therefore needed more than the local label: they needed a shared identity for the virtual connection before they could bind it into MPLS.
History
The Switch Could Not Decrement TTL. The Ingress Paid the Hop Count Up Front: RFC 3034
A Frame Relay switch could replace a DLCI at line rate yet lack the operation that routers performed on every packet: subtract one from time to live. RFC 3034 preserved MPLS loop and scope accounting by charging a propagated segment length at the boundary. The control plane…
History
LDP Kept the Full-Length Prefix and Dropped the Host FEC
In 2001, LDP gave routers two distinct ways to describe a destination address, even when both could point at the same host. Six years later, its revised specification removed one of those forms for a precise reason: no implementation used it. The full-length prefix remained.
History
The Identifier Named the Session. It Did Not Move It: RFC 3033
A call-control message could carry the exact IPv4 or IPv6 tuple that named an Internet session, yet the packets could still be travelling over the old virtual circuit. RFC 3033 gave ATM signalling a vocabulary for the intended subject. It deliberately stopped short of claiming…
History
The Server Advertised a Capability. Authentication Changed the Answer: RFC 2449
A POP3 client asks what a server can do before it knows who is asking. The reply may be deliberately cautious. The same server can give a more precise answer once a user is authenticated—and a different answer again after the session gains an integrity-protection layer. RFC 2449…
History
The Server Signed the Verdict. The Object Was Still Invalid: RFC 3029
A signed certificate arrives from a trusted validation server. Its conclusion is not “valid” but “invalid”. There is no contradiction. The signature authenticates who issued the verdict, the request it answers, the time and the policy used. It does not repair the document or…
History
The Network Treated Every Packet Equally. The Codec Did Not: RFC 2448
When a compressed picture loses a few bytes, the size of the loss can be a poor guide to its consequence. A missing fragment of ordinary image data may blemish one region; losing a compact description of how to decode what follows can damage much more. In 1998, RFC 2448 proposed…
History
The Rule Chose an Action, Not an Outcome: RFC 3028
A mail filter reaches the end of its script without choosing a destination. That absence could have meant loss. Sieve instead turned it into a protective decision: keep the message by default. The small rule exposes the larger architecture of RFC 3028—language evaluation could…
History
The Envelope Was Not the Calendar: RFC 2447 Put iTIP Inside MIME
RFC 2447 made familiar Internet email a carrier for structured scheduling without asking the mail envelope to become a calendar protocol. Its binding placed a `text/calendar` entity inside MIME, paired the entity's `METHOD` with the MIME `method` parameter, and allowed a readable…