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.
Story
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity
RIPEstat Wants Better AS Names—and a Map of Which ASNs Are One Entity 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.…
History
One Call-ID, Several Dialogs: How SIP Tags Named a Fork
An invitation sent to one address could ring at several endpoints and return several answers. SIP's durable solution was not to give each answer a new call number, but to let each peer complete a two-sided name for the state that would outlive the invitation.
CASE FILE
The Session Grouped Four Streams. It Did Not Reconstruct the Scene: RFC 10034 and Authority over a V3C Representation
Volumetric video does not travel as one self-sufficient picture. It can arrive as an atlas plus occupancy, geometry and attribute streams, each with its own packets and failure state. RFC 10034 gives those parts a shared transport grammar. It does not appoint any one green…
IETF
Erik Nordmark and the Neighbor That Became Stale Before It Became Unreachable
An IPv6 neighbor can become `STALE` while it is still carrying traffic, and it can enter `UNREACHABLE` while packets are still sent to its cached link-layer address. The apparent contradiction disappears once the cache is read as a record of expiring evidence rather than a…
History
The Connection Died. The Session Did Not: How RTSP Put State Beyond TCP
A media server could lose the socket that carried PLAY and still remember what the client had set up. RTSP made that possible by giving server state its own expiring identifier—then carefully refusing to treat the identifier as the resource, the media path or the user's…
CASE FILE
The Header Asked for a Stream. The Proxy Still Owned the Flush: RFC 10036 and the Authority to Release an HTTP Message
A sender can place `Incremental: ?1` at the front of an HTTP message and begin producing useful content immediately. That does not make the path a pipe. Every intermediary still controls a parser, a security decision, a capacity limit and a buffer. RFC 10036 turns the sender's…
Story
LACNIC's Delegation File Declares 49,894 Records. It Contains 48,214
A daily file built for machines fails the counting rule printed in its own specification, while its automatic alias and its dated signature offer two different paths to trust. The discrepancy is not evidence of missing Internet resources. It is a test of whether a registry…
Story
LACNIC’s Revocation List Shows a /23 in 2023 and a Nested /24 in 2026
The same first address appears twice in LACNIC’s public revoked-resources table, first as a 512-address block and three years later as its lower 256-address half. That visual repetition invites the wrong question: was the same resource revoked twice? Six official daily snapshots…
History
The Number That Said Goodbye So the Stream Could Continue: How RTP Resolved SSRC Collisions
Two live sources could enter one RTP session carrying the same 32-bit number. The protocol did not ask a central registry to decide who owned it. The source that found its own number in conflict sent goodbye for that label, selected an unused replacement and kept the media…
CASE FILE
The Server Issued a Locator. The Network Had Not Yet Accepted the Route: RFC 10038 and the Authority to Allocate SRv6 Reachability
A DHCPv6 Reply can make an SRv6 locator administratively real in a few fields: who received it, how it is divided and when it expires. The packet path is harder. A route still has to be installed, advertised, selected, programmed, filtered and joined to a local SID behavior. RFC…
History
One XID, Two Executions: Why RPC Needed Memory Beyond the Reply Number
A remote call can be repeated with exactly the same number and still perform its work twice. ONC RPC made replies attributable; the harder task was preserving enough server-side history to say whether a retry was new.
CASE FILE
The Token Matched. Permission Still Had to Be Checked: WebDAV Lock Tokens and Write Authority
A WebDAV client can present the exact token for a live lock and still be correctly refused. That is not a contradiction in the protocol. It is the point at which a coordination marker stops and authority begins.
CASE FILE
The Registry Published the TTL. The Resolver Kept Its Own Clock: RFC 10037 and the Authority to Describe a DNS Change Window
A registry can now place a delegation TTL in an RDAP response, where an operator can read it without querying the DNS. The number is useful precisely because its authority is narrow. It describes what the registry database has provisioned; it does not reveal how many seconds…
History
The Answer That Supplied the Next Question: How SNMP Walked the MIB
An early network manager could know the name of a routing-table column without knowing a single row index. SNMP solved that ignorance with an unusual answer: return not the requested name, but the next accessible one. The reply became the next question, and an unknown inventory…
Story
ARIN Accepts Non-Human Service Accounts. Its Guide Still Says to Use an Individual Email
ARIN closed a four-year request on 29 July after removing the account-creation restriction on non-human service accounts. The implementation gives network operators a proper principal for automation. The public instructions have not yet made the same transition: the account guide…
CASE FILE
The Cache Told You It Was a Hit: Cache-Status and the Authority to Explain a Response
Cache-Status gives every cache in an HTTP path a common way to describe its part in delivering a response. That makes incidents easier to investigate, but it also creates a tempting mistake: treating the system's own explanation as if it were independent proof.
CASE FILE
The Message Was Accepted Before It Was Released: IETF's Mail Transition and the Authority to Hold, Rewrite and Relay
On 11 September, a first-time sender may hand a message to the IETF's mail system and receive an apparently ordinary SMTP outcome while the operational copy waits elsewhere for a challenge response. That gap between acceptance and release is the real story in the IETF's new email…
Story
ARIN’s ROA Alerts Follow Deletion, Not the Change in Routing Authority
ARIN can commit several routing authorizations in one transaction, yet its documented alert boundary still follows a single verb: delete. Two public suggestions expose the resulting choice between inbox noise and silence. A safer design would report the net change once.
History
The Option Nobody Understood Still Said What to Do: How IPv6 Bounded Unknown Options
IPv6 gave future options a way to meet old software without leaving the consequence to guesswork. Three leading bits did not explain the new feature; they told an unknowing processor how far ignorance was allowed to travel.
IETF
Jen Linkova and the Five-Minute Clock That Kept IPv4 on Call
The most revealing part of RFC 8925 is not that a device can decline an IPv4 address. It is that the refusal expires. A client asks for DHCPv4 option 108, a configured server returns a waiting time, and the client pauses DHCPv4 only until that clock runs out or the network…