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.
IETF
RFC 9812: A Stricter Review Gate Does Not Allocate IPv6 Space
Most of the IPv6 address space remains marked “Reserved by IETF.” RFC 9812 changed the rule for any major future release of that reserve from IESG Approval to IETF Review. That is a consequential transfer from an exceptional gate to a public, documented process. It is not an…
Asia-Pacific National Telecom Trends
U Mobile's three-day 5G site starts a longer continuity test
A portable mast can shorten the wait for first coverage. It cannot shorten every obligation that begins when people rely on it. U Mobile and ZTE have shown how to start one kind of rural site in three days; the market question is how the site behaves through the weeks, weather…
IETF
Nick Hilliard and the IPv6 Prefix That Works Only When It Goes Nowhere
`100::/64` is globally unique, forwardable inside a network and deliberately not globally reachable. That apparent contradiction is the point. The prefix gives IPv6 remote-triggered blackholing a clean internal next hop, but its success cannot be read from an IANA row or a green…
Story
Stork’s DNS Serial Comparison Begins With the Zones It Could Fetch
APNIC 62 showed a useful cross-server mismatch signal. Its meaning begins one step earlier: which daemons, views and zone configurations entered the cache, when they were fetched, and what the fetch could not observe.
Leaders
Nick McKeown and the Barrier Reply That Never Saw a Packet
A controller can receive a perfectly valid OpenFlow Barrier Reply while the customer’s packet is still being discarded. That is not a contradiction. The reply certifies order on one control connection; delivery belongs to a longer chain of evidence that starts after the fence.
Story
ARIN’s IPv6 CSV Has a Spelling Problem, Not a New Address
An uppercase letter in an IPv6 export does not allocate a second network. It can still give a spreadsheet, log search or text-based join a second name for the same one. An ARIN customer asked for lowercase in the Manage Networks CSV; ARIN agreed that the change would be more…
Leaders
Remco van Mook and the IPv4 Gateway That Has No IPv4 Neighbour
An IPv4 default gateway normally looks like an address that a host can find with ARP. Remco van Mook's current IETF proposal turns that expectation inside out: `192.0.0.11` is not a neighbour to discover, but an instruction to reuse a neighbour that IPv6 has already discovered.…
Story
AFRINIC’s IPv6 Draft Changed What 95% Means
Draft 3 keeps the comfort of a familiar percentage while changing the thing being counted. A future result can be comparable only if it travels with the policy version, denominator and measurement method that produced it.
IETF
The Hash Looked Expensive. The Login Fleet Had Not Been Measured
RFC 9106 makes Argon2id's memory, passes and lanes explicit. That is the start of an engineering decision, not evidence that a verifier can carry its real login load or that a stolen hash will cost an attacker what the defender imagines.
History
The Interface Published a Delay Budget. It Did Not Publish a Guarantee: RFC 2214
RFC 2214 turned a router’s departure from ideal fluid service into four manageable interface fields. The precision mattered, but it was precision about configuration—not proof that a particular flow received the promised result.
IETF
The Link Colour Arrived. The Policy Decision Did Not: RFC 9104
A controller can receive a perfectly formed Extended Administrative Group through BGP-LS and still lack the evidence needed to say what the bits mean, which policy used them, which path won or what happened to traffic. RFC 9104 standardises carriage across that boundary—not the…
History
The Green Tunnel Light Is Not a Service Receipt: Reading RFC 2341 Precisely
An operations screen can show a tunnel as open while the user's application is still waiting. RFC 2341 makes that gap unusually easy to see. Its Layer Two Forwarding protocol coordinates a tunnel between an access provider's Network Access Server and a Home Gateway, then carries…
History
The Row Was Active. The Reservation Was Still Unproven: RFC 2213
RFC 2213 gave Integrated Services a management surface detailed enough to inspect and, in some implementations, alter. Its precision was useful precisely because every field stopped short of proving the whole reservation.
IETF
SIMAP Can Trace a Service to Its Hardware. That Does Not Make the Map the Network
Revision 13 gives network software a common way to walk from a service through logical layers to physical resources and back again. The result can be operationally valuable without being a certificate that the graph is complete, current or authorised to act.
IETF
The Transfer Was Encrypted. The Zone Still Needed a Custodian: RFC 9103
Encrypting AXFR or IXFR removes a powerful observer from the path: anyone who could read the transfer in cleartext. RFC 9103 makes that result precise—and, just as importantly, leaves authorization, replica custody and the rest of the DNS exposure surface as separate questions.
History
The Server Drew Three Mail Maps. It Did Not Prove a Mailbox Was There: RFC 2342
RFC 2342 let an IMAP server disclose the naming conventions for personal, other-users and shared mailboxes. A prefix and hierarchy delimiter could tell a client how to ask the next question. They could not answer whether a particular mailbox existed, appeared in a list, accepted…
History
One Path, Four Algebras, and One Contagious Unknown: RFC 2215
A network path can be described by many numbers, but those numbers do not obey one law. RFC 2215 made that distinction operational: a break propagates by logical OR, aware hops are counted, bandwidth and packet size are narrowed by minima, and latency accumulates. More…
IETF
The Proxy Said Yes. The Destination Had Not Yet Proved Anything
CONNECT-TCP revision 14 gives a TCP proxy a normal HTTP origin, a URI-template address and a capsule protocol that works across HTTP/1.1, HTTP/2 and HTTP/3. That makes the proxy easier to authenticate, route and govern. It also creates a tempting analytical error: treating a…
IETF
The Backup Nameserver Answered. The Cached Key Did Not Fit: RFC 8901
A second authoritative DNS provider can keep answering after the first one fails and still leave validating resolvers without an acceptable answer. RFC 8901 shows why DNSSEC redundancy is a synchronization contract across signers, not a count of nameservers.
History
The Packet Contained Picture and Sound. It Did Not Prove a Programme Played: RFC 2343
RFC 2343 put MPEG-2 video slices and audio frames into one RTP payload so that a stored programme could travel as one coordinated stream. The packet carried useful timing and boundary evidence. It still could not testify for the network, decoder, renderer, loudspeaker, screen or…