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.
CASE FILE
A Delegated LSP Was Not a Delegated Network
RFC 9504 makes a stateful PCE more useful in GMPLS networks. It does not turn a protocol exchange into an institutional transfer of authority, or a desired LSP into an operating service.
CASE FILE
The Recipient Key Was Named. The Message Had Not Been Opened: RFC 9936
CMS can now carry an ML-KEM recipient path under RFC 9936. An inspectable recipient record can identify a certificate or public key and the ciphertext made for it; it cannot, by itself, certify private-key custody, successful local processing or an organizational decision.
History
The Agent Said It Supported the Module. It Had Not Authorized the Change: RFC 1303
An operator can learn a great deal from a device that describes its management surface. It may tell a station which MIB groups it implements, which entities are unavailable, which values it can read, and which values it will accept in a write. That knowledge prevents a management…
History
The Ticket Was Not the Outage: RFC 1297's Memory Boundary
An outage does not pause at a shift change. It does not become one event merely because several people call about it, and it does not become repaired because somebody has recorded an escalation. In 1992, RFC 1297 treated the trouble ticket as something more modest and more…
CASE FILE
The Schedule Was Enabled. It Had Not Executed the Change: RFC 9922
An `enabled` schedule with a credible next window and a recent `last-occurrence` can be useful management evidence. It is not proof that a controlled change was authorized, invoked, completed, rolled back safely, or produced the effect a dashboard now reports.
History
The DNS Walk Counted Records, Not Reachability: RFC 1296's Lower Bound
The Internet acquired a number before it acquired a census. In January 1992, RFC 1296 reported 727,000 hosts from a DNS collection run. The point of Mark Lottor's memo is not that the number settled what the Internet was. Its more durable lesson is that a careful collector can…
History
The Public Directory Needed a Right to Refuse: RFC 1295's Boundary
An electronic directory can make a name easier to find long before it makes that name legitimate to publish. RFC 1295, the North American Directory Forum's 1992 *User Bill of Rights for entries and listings in the Public Directory*, put that distinction in an unusually plain…
History
A Frame Label Was Not a Virtual-Circuit Configuration: RFC 1294’s Multiprotocol Boundary
A Frame Relay receiver could be given enough bytes to identify the protocol inside a frame and still have no authority to treat the virtual circuit as available for every encapsulation it could recognise. RFC 1294 made that separation unusually explicit. NLPID and SNAP told a…
CASE FILE
The UDP Payload Was Protected. The Option Was Not: RFC 9868
RFC 9868 gives UDP a place for transport options. It does not place that option area inside the UDP user data that DTLS protects, turn an option checksum into a security decision, or prove that an endpoint, path or application acted on an option.
CASE FILE
The Cursor Continued the List. It Did Not Continue the Right: RFC 9865
RFC 9865 gives SCIM a cleaner way to traverse a long result set. It does not convert a continuation value into a portable permission, a complete inventory, or a decision already made.
SANOG
SANOG’s Six-NOG Committee Does Not Cover Its Eight-Country Map
SANOG describes a region of eight countries. Its published future governance strategy, however, routes local-NOG representation through six named forums. That leaves Afghanistan and Maldives without the same visible institutional path into the Core Committee.
History
A Local Service Was Not Control of the Network: RFC 1291’s Mid-Level Boundary
In 1991, a mid-level network could make the Internet more usable without becoming the Internet's owner. RFC 1291 proposed local DNS capacity, software-discovery pointers, time servers, news feeds, mailing-list relays, testbeds, information services and NOC contacts. Its design…
Story
AFRINIC Says It Added JSContact. Its RDAP Guide Does Not Say Which One.
AFRINIC’s public record contains a useful sentence and an unfinished question. The current release entry for WHOIS 2.10.7 says that an RDAP feature called JSContact was added. The current RDAP guide tells a reader where the service is, which resources may be queried, which…
CASE FILE
The Color Reached PCEP. It Did Not Reach the Service: RFC 9863
RFC 9863 lets PCEP carry a color for a TE path. That is useful coordination data. It is not a guarantee that a service was mapped, a latency objective was met, or a customer received a result.
History
A Pointer Was Not the Information: RFC 1290 Had Not Made the Route Invisible
In 1991, the problem was not a lack of material on the network. RFC 1290 described the opposite: information and file repositories so abundant that browsing could consume a lifetime. The problem was how a person crossed from abundance to something usable. The document separated…
CASE FILE
The Router Repaired the Path. It Did Not Restore the Service: RFC 9855 and TI-LFA’s Local Boundary
A router can react to a directly attached failure in milliseconds and still know nothing about whether a customer service has recovered. RFC 9855 gives Segment Routing deployments a disciplined way to precompute and activate a loop-free repair path at the Point of Local Repair.…
History
The Architecture Retreat Named Five Problems. It Did Not Pick the Next Internet: RFC 1287
In 1991, a group of Internet architects looked at growth, address exhaustion, multiple protocol suites, security, real-time traffic and the next generation of applications. RFC 1287 is the record they left behind. It is tempting to read such a record backwards: it discusses…
History
A Bridge Port Was Not Necessarily an Interface. Its Counters Did Not Describe the Whole Line: RFC 1286
A network operator can be handed three reassuringly familiar facts: a port number, an interface index and a counter. RFC 1286, the 1991 Bridge MIB, is valuable because it refused to let those facts collapse into one picture. A bridge port could correspond to an interface without…
CASE FILE
After a Reboot, “Secure” Must Not Mean “Resume”: RFC 10021 and Group OSCORE Recovery
A controller can regain a safe cryptographic footing after a power loss without regaining permission to continue the process it interrupted. RFC 10021 makes that distinction operational: restore the security context first; decide separately whether anything should resume.
Europe and Middle East National Telecom Trends
Slow broadband deters UK home movers, survey finds
Hyperoptic’s survey suggests broadband is being checked before a move, raising the value of clear availability and fast activation.