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.
Europe and Middle East Datacenter
AZUR DATACENTER SAS: what a RIPE NCC membership listing actually proves
A French company named AZUR DATACENTER SAS appears in the RIPE NCC public member directory. That single record is the entire verified signal behind the company's presence in BTW's directory — and it is a narrower signal than its name suggests.
History
The Service Had a Name. The Name Proved Almost Nothing: RFC 2216
In 1997, the Internet engineering community gave quality-of-service offerings a namespace. But RFC 2216 made the harder point first: a service number was only an address into a specification. The proof began after the name—with the caller, the traffic contract, the element’s…
ICANN
4.3 Million IDNs Are a Registration Count, Not a Universal Acceptance Result
A name can exist in the DNS, appear in a registry total and still be rejected by the first sign-up form that asks for its email address. ICANN’s new annual report makes both sides visible: multilingual identifiers are widely available, while the software path that must use them…
History
One Clean Match Hid the Hard Questions: RFC 2345 and the Company-Name Lookup
A company name went in; a name and a URL came back. RFC 2345 made that exchange intentionally small enough for a 1998 browser add-in and a port-43 server. The economy was the point. Yet the response line carried no proof of who registered the domain, which legal entity the name…
History
The Error Terms That Made a Promise Calculable: RFC 2212
Guaranteed Service did not promise that a network would behave like a perfect wire. RFC 2212 did something more useful: it required every participating element to put a maximum price on its departure from that ideal, then showed how those prices could be added into a delay bound…
IETF
The Reply Address Was Not the Router
The IETF Last Call has closed on an ICMP extension that could make an ambiguous traceroute hop more intelligible by attaching a node address or name. The same fields can disclose internal topology, and the draft provides no way to authenticate them. That makes node identification…
History
The Map Was Not the Road: What RFC 2333 Let NHRP Resolve—and What It Could Never Prove
A clean NHRP cache row could look like the end of a problem. It joined an IP destination to an NBMA address, carried an authority class and retained a holding time. Yet RFC 2333 placed that row in a much longer chain. Routing had to choose a path first. NHRP could then resolve a…
History
The Request Reached the Coffee Pot. The Cup Was Still Empty: RFC 2324
RFC 2324 made a networked coffee pot answer HTTP-like commands, then quietly exposed how little a successful exchange can say about the physical world. A valid `BREW` request is evidence about a message and a controller. It is not a receipt for hot coffee, a filled cup, a safe…
History
The Bit That Invalidated a Path: What RFC 2210's ADSPEC Could Actually Prove
RFC 2210 gave an RSVP receiver a compact account of the path in front of it. The account could include hop count, bandwidth, latency, MTU and service-specific terms. Yet the most important field was not a large number or a precise bound. It was a break bit: a one-bit warning that…
IETF
The Product Says Internet Access. The Receipt Should Say What It Can Carry: RFC 4084
“Internet access” is a product name broad enough to conceal the operational facts a buyer will later depend on. RFC 4084 offers a better starting point: name the capability, disclose the restriction, and never promote a workaround into a promise.
History
The Alias Reached the Child Zone. Nothing Else Was Proven: RFC 2317
A reverse query for one address can cross two administrative boundaries before it returns a name. RFC 2317 made that path possible for IPv4 blocks smaller than a /24, but the records along the path remain narrow receipts: they show how DNS reached a PTR answer, not who owns the…
History
The Association Was Mature. The Security Result Was Not: RFC 2367
A diagnostic console shows an IPsec Security Association in the `MATURE` state. Its SPI, algorithms, addresses and lifetime are all present. That is useful evidence—but only of what one local Key Engine reported. RFC 2367 drew the interface boundary clearly enough to show why the…
CASE FILE
The Packet With No Payload That Can Move TCP State Backward
Presto’s pseudo-segment solves a hard pipeline problem by turning a backward state correction into another forward pass. That synthetic record can be authoritative inside the transport without being user traffic, a completed socket operation or proof that an application received…
History
The Address Said “Stay Here.” Only the Router Could Enforce It: RFC 2365
An IPv4 multicast packet can carry a destination inside 239/8 and still escape the region its operator intended. RFC 2365 made that uncomfortable distinction explicit: the address describes an administrative scope, while containment is performed by boundary routers whose…
CASE FILE
The resolver address was not the resolver
APNIC Labs added a second dual-stack authoritative nameserver and watched average queries per test fall from 3.43 to 2.57. The experiment did not reveal a cause. It revealed something more operationally awkward: a public recursive-resolver address is often a routing handle, not a…
History
When a Successful ESRO Result Still Ends in Failure
In ESRO, a performer could finish an operation, send a successful result, and later receive a failure indication even though the invoker had already accepted that result. RFC 2188 made room for both observations to be true. Its most durable lesson is not about a forgotten 1990s…
Leaders
Adrian Farrel and the Path That Exists Only on the Controller
A positive PCEP reply can put a clean route on an operator's screen before any router has accepted it. Adrian Farrel's PCE architecture matters because it lets us say exactly what has happened—and what has not.
IETF
When One Bad Route Becomes Everyone Else’s Risk: The Authority Question in BGP DRIP
A router sees one suspect announcement. Minutes later, routes that were never themselves invalid have lost preference because they share an origin, a neighbour or an AS-path pattern. That is the consequential idea inside the first BGP DRIP draft: not simply faster warning, but a…
IETF
The Drop Rate Was Historical. The Control Boundary Still Matters: RFC 7872
RFC 7872 recorded substantial loss for several IPv6 extension-header probes in 2014–15. Its enduring value is not a percentage that can be carried into 2026; it is the disciplined separation between what a probe observed, where a path might have discarded it, who could change…
History
The Backup Route’s Invoice
A second Internet provider promised resilience, but the extra route appeared only after the first path failed. RFC 2260’s enduring insight was that multihoming never removed the bill for reachability; it decided whether that bill would be paid in global routing state, provider…