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.
CASE FILE
The Network Named a Provisioning Domain. It Did Not Choose the Path.
A Provisioning Domain can keep one network's addresses, resolvers and routes from contaminating another. It names a coherent context; it does not convert a Router Advertisement into a command that chooses a connection.
CASE FILE
The bridge was gone. The topology still crossed it
Two BGP-LS producers can each retain one stale half of a failed link. A consumer that merges their disclosures may reconstruct a plausible connection that no longer exists, and a controller may compute straight across it. The failure is not simply “bad telemetry.” It exposes who…
Story
APNIC’s First IPv6 PI Request Has No Previous Assignment
APNIC’s `prop-175-v001` offers to remove a peculiar round trip: issue a `/48`, wait for deployment, invite the applicant back, receive much the same network plan and assess the larger need a second time. Reusing the later-stage test is economical. It is also a change of state…
History
A Reservation Could Survive Without Being Rechecked
RSVP learned to keep previously advertised state alive by naming it instead of repeating its description. That reduced routine work, but changed what the routine could discover. A missing record could ask for repair; a recognisable record with the wrong contents was a different…
History
The Reply SMTP Could Not Divide: How LMTP Made Local Delivery Per-Recipient
One message reaches the local-delivery boundary with two accepted recipients. One mailbox can take it; the other is temporarily over quota. SMTP has one final answer for that transaction, so the receiver must own what happens next. LMTP changed the shape of the answer: one…
Story
Two Numbers on One Proposal: APNIC Must Correct Identity Without Rewriting History
`prop-174: Align implementation of Prop-125 in APNIC Policy (APNIC-127)` `prop-173: Align implementation of Prop-125 in APNIC Policy (APNIC-127)`
History
The Knock That Brought the Client Back
A DHCP server could know that a setting should change while its client had no reason to ask again. FORCERENEW gave the server an opening in that quiet interval. It did not give the opening message the power to complete the change.
CASE FILE
The route existed. The subscription did not
A VPN route can be valid, selected and available at its source while a remote PE correctly receives nothing. RFC 4684 lets Route Target interest travel toward the route and matching reachability travel back. That inverse graph saves state, but it also makes an absent or stale…
CASE FILE
The Child Has Spoken. Who Makes the DS Record Real?
A child zone can publish a perfectly signed request for its next DNSSEC trust state and still be rightfully refused. CDS/CDNSKEY automation works only when signal, acceptance, parent publication and validator observation remain separate facts.
History
Philip F. Smith and the Routing Report That Could Observe, Not Command
A daily BGP report begun in 1999 made routing behaviour public at a moment when registry records and operator claims could not show what the network was actually announcing. Philip F. Smith’s long-running instrument matters because it also exposes its own limits: a selected path…
Story
One Portal, Four Unfinished Clocks
MyAFRINIC v2 has become more than a software project: AFRINIC's own records place four materially different policy paths behind the same portal milestone, making it necessary to prove each implementation separately rather than letting one launch announcement stand for all four.
History
The Link the Origin Asked to Remove: Why HTTP 410 Was Not 404
Two dead-looking links can lead to the same empty browser view while making very different claims. HTTP 404 leaves the reason and duration unresolved. HTTP 410 lets an origin say that access ended deliberately, is likely to stay ended, and should change how the rest of the Web…
History
The Message That Expired at Only One End
A sender could stop pursuing a message whose usefulness had run out. It could not make the receiver infer that decision from silence, or recall a copy already on its way. SCTP’s partial-reliability extension made abandonment a shared procedure without disguising it as delivery.
CASE FILE
Zero is not a diagnosis
An alert that says only “BGP saw zero” has thrown away the fact that decides the response. Zero is a valid ORIGIN code, a prohibited autonomous-system identity, and an RPKI disavowal value in three different protocol entities. RFC 7607 makes the distinction operational: refuse…
CASE FILE
Who Owns the Renewal Clock? ACME ARI and the Last Mile of Certificate Replacement
A certification authority can spread renewal work across a day, yet a fleet can still compress that day into one frantic minute. ACME Renewal Information supplies a window; the client, deployment system and live service decide whether that window becomes a safe replacement.
Story
The Prefix Must Keep Its History: AFRINIC’s Proposed Pool Decision
Under `AFPUB-2026-IPv4-003-DRAFT01`, one recovered IPv4 block would first enter the temporary `Recovered Pool`. AFRINIC staff would trace its original source-pool category, return it there, classify a partial block proportionally, or send an uncertain origin to the…
CASE FILE
The Reply Said Success. No Client Had Changed: DHCPv6 Reconfigure and the Authority of a Trigger
A relay can report that configuration changed, a server can answer `Success`, and an authenticated packet can reach a client without any of those events proving that the client now runs different addresses, prefixes or service parameters. DHCPv6 Reconfigure is useful precisely…
CASE FILE
The route outlived the speaker
BGP Long-Lived Graceful Restart can keep a failed peer’s routes for hours or days after ordinary restart protection ends. That buys time, but it also turns stale state into a temporary operating promise whose timer, forwarding basis and exit must be proved.
History
The Packet That Had to Go Home Before Going On
A mobile computer could carry its address to another network, but not necessarily the right to emit that address from there. Mobile IPv4's reverse tunnel sent an outgoing packet home before letting it continue to its correspondent. The detour was less an admission that the…
History
The Report That Had to Wait for the Crowd
An RTCP report timer reaches its appointment, and the source still does not send. The report is ready. The correct next action may still be to send nothing. In the control protocol accompanying real-time media, an appointment made with an incomplete picture of the group is not an…