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 Speaker Was in the Session, Not the Path: IXP Route Servers and the Authority to Broker Reachability
The BGP session was established to one system. The route began with another network's AS number. Its next hop named a third address on the exchange fabric, and the packets never crossed the machine that had delivered the UPDATE. Nothing was malformed. The apparent contradiction…
History
The Second Connection Asked Who Owned the First: How IDENT Bounded a Username's Authority
A server has already accepted one TCP connection when it opens another in the opposite direction. On that second connection it sends two port numbers to the first host and asks a narrow question: which local user owns the first connection? IDENT made that answer useful for logs.…
Story
AFRINIC’s bylaws committee can recommend; the Board controls the gate to members
The consultation has ended, but consultation is not authority. AFRINIC’s own rules place the decisive pre-member gate with the institution that appointed the review committee.
History
The Time Packet That Was Not Time: How NTP Kiss-o'-Death Made Refusal Actionable
The reply fits the familiar NTP shape and even belongs to a request the client just sent. Yet its timestamps must not adjust a clock. Stratum 0 and the four letters `RATE` turn the packet into something else: a server's bounded request for less traffic, delivered inside the…
CASE FILE
The Request Said Urgent. The Scheduler Still Decided: HTTP Priorities and the Authority to Allocate Scarce Delivery
A browser can call a hero image urgent, an origin can prefer the font, and a CDN can see both through a different connection map. RFC 9218 lets each express useful information. It does not let any of them annex the scheduler that finally allocates the next byte.
Story
AFRINIC consultation closes; the response ledger is the next test
The endpoint has expired. AFRINIC’s committee rules now point to one accountability test: show what came in and how each item was handled.
Story
AFRINIC's “all legal costs” resolution still lacks closure
A 2022 Board record explains the urgent defence. It does not show how the unlimited-looking undertaking was classified, spent or closed.
History
The Prefix That Tried to Make IPv6 Automatic: 6to4 and 2002::/16
6to4 offered a seductive bargain: turn an existing IPv4 address into an IPv6 network and let relays complete the journey. The address trick worked as specified. The operational responsibility did not assemble itself around it.
Asia-Pacific National Telecom Trends
User-level AI-RAN needs an error ledger, not one average
DOCOMO and Samsung report that simulated user-level optimisation cut throughput-degradation frequency from 13.1% to 7.2%. The result is promising; commercial control depends on who improved, who was incorrectly changed, what other users lost and how the network rolls back.
History
The File Did Not Come From Port 69: How TFTP Bound a Transfer to Chosen Endpoints
A packet trace of a correct TFTP read begins with a small surprise. The request goes to UDP port 69, but the first block of the file comes back from another port. That change is neither drift nor a second service. It is the moment the protocol replaces a public door with a…
Asia-Pacific National Telecom Trends
DOCOMO's 2028 satellite roadmap needs a service envelope
DOCOMO has contracted for a satellite layer intended to add voice, faster browsing and IoT during fiscal 2028. The roadmap is strategically significant; its operating value will depend on published limits for capacity, latency, priority, device certification and fallback.
CASE FILE
The Resolver Named the Failure. It Did Not Prove the Cause: Extended DNS Errors and the Authority of Diagnosis
Extended DNS Errors can turn an opaque DNS failure into a useful account of what one resolver observed. The gain is operational clarity. The danger begins when a dashboard promotes that account into proven cause, assigned blame or permission to weaken the control that produced…
History
The Question SMTP Learned Not to Answer: How VRFY Separated Address Acceptance from Directory Disclosure
In 1982, a remote machine could ask an SMTP server to `VRFY Smith` and receive Fred Smith’s full name and mailbox. The command was useful because it made a mail problem inspectable. It was dangerous for the same reason: a transport service had become a public directory, one…
Story
AFRINIC promises representation before publishing the method
An open, anonymous consultation may find useful priorities. It cannot become evidence of member consent merely because the response count grows.
Asia-Pacific National Telecom Trends
Marunouchi makes real estate the control plane for mmWave
DOCOMO and Mitsubishi Estate want to build a dense 5G cluster across one of Tokyo's busiest business districts. The partnership addresses mmWave's hardest constraint: radios only work where property access, sightlines, fiber, power and streetscape approval meet.
History
The Server Returned the New Name: How UIDPLUS Made IMAP Mutation Verifiable
The upload had succeeded. The message was in the mailbox. Yet the client still lacked the one fact it needed for its offline ledger: which UID had the server assigned? Before UIDPLUS, a positive result could confirm the mutation while withholding the durable local reference…
Story
ARIN's Single-Site `/48` Lived in an Example Before It Reached the Rule
One site filled 100% of the `/48`s inside a `/48`. The sentence therefore pointed to `/44`; the example did not. ARIN-2025-7 repairs that small contradiction, and in doing so reveals a larger rule: examples must never become the hidden execution layer of number policy.
CASE FILE
The Token Knew the Address, Not the Actor: DNS Cookies and the Authority of Weak Authentication
A valid DNS Server Cookie proves something useful and deliberately small: a requester using this Client Cookie at this source address previously received a value derived from a server secret. Trouble begins when an operations system promotes that narrow fact into identity, trust…
Story
APNIC Reprinted a Router Guide That Turns a Private WAN Address into a CGNAT Verdict
A private address on a router's WAN port is an observation, not a diagnosis. APNIC's republication of a home-router guide compresses several different access designs into one confident label, even though the remedy depends on which design is actually present.
History
The Command That Gave Away the Connection: Why SMTP Replaced TURN with ETRN
A mail host called its provider and asked the line to turn around. The server could then send queued messages back over the same connection. The convenience hid an authority transfer: the caller had spoken a host name, but the protocol had not proved that it was entitled to…