Topic
Network-resource Evidence
Within the Topic facet, Network-resource Evidence topic intelligence connects articles that share a specific subject, signal focus, or monitoring theme. The page gives readers a richer path through related reporting, source evidence, market actors, and infrastructure implications, with enough context to understand why the topic matters across company movements, governance decisions, regional exposure, and operational risk. Readers can compare recurring signals, affected organisations, public evidence, market context, service continuity, procurement, competition, compliance, and strategic planning questions behind the subject instead of stopping at a thin list of matching articles. It explains what the topic covers, which infrastructure actors or policies are involved, what evidence supports the coverage, and why the subject may matter for operators, customers, investors, and policy readers.
Global Regional ISP
The Customer Ledger Is the Weakest Layer: What AS17494's Own Records Prove About Its ISP Claim
The Customer Ledger Is the Weakest Layer: What AS17494's Own Records Prove About Its ISP Claim intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
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…
IETF
Silence Is Not Availability: The Multicast Address That Survives Until the Partition Heals
Two senders can each complete a clean probe, retain the same multicast group ID and continue without an alarm. The contradiction appears only when the switch comes back and the network becomes whole again. An IETF draft now makes that delayed failure unusually legible: its…
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…
Global Cloud Services
AS210328 After the August 2026 Registry Edit: What Changed, and What Still Cannot Be Verified
AS210328 After the August 2026 Registry Edit: What Changed, and What Still Cannot Be Verified intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Global Institutional
DFINFRA/AS210860: The Routing Table Says Zero, the Directory Says Ten
DFINFRA/AS210860: The Routing Table Says Zero, the Directory Says Ten intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow.…
Story
AS210328 Today: What the Live Record Shows — and Fails to Show — About AO ALMAZ's Cloud Network
AS210328 Today: What the Live Record Shows — and Fails to Show — About AO ALMAZ's Cloud Network intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
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…
IETF
The Draft Promised 0-RTT. Its Normative Rule Turns It Off.
The router returned after a failure with an old RPKI cache view and a valid QUIC session ticket. The draft's introduction offered a tempting picture: put the session request in the first packet and almost instantly close the blank interval. Five pages later, the protocol did…
IETF
The Incident Named a Cause. The Confidence Stayed Upstream
An incident record can be exact about the node, resource and class of a probable cause while remaining silent about how strongly the diagnosis is believed. Revision 17 of the IETF NMOP incident model makes that silence deliberate: confidence belongs outside the common incident…
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…
Asia-Pacific National Telecom
AS17494: Declared Transit Policy Versus Observed Routing
AS17494: Declared Transit Policy Versus Observed Routing intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
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…
IETF
The Claim Was Encrypted. It Still Did Not Own the Multicast Address.
GAAP-25 hardens the packet that carries a multicast-address claim. That is useful engineering. It is not a deed, a mandate, or evidence that the claimant may control what it names. The operational mistake would be to let a cryptographic success answer a question it was never…
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…