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.
History
The Label Said JPEG. Every Other Identifier Said GIF: RFC 2158
One line in RFC 2158 refused to agree with the record around it. The heading said GIF. The X.400 body-part name said GIF. The entity-identifier branch said `gif-image(4)`. The MIME field alone said `image/jpeg`. That small fracture turns a three-page standard into a useful lesson…
History
The Page Had One Character Universe, Whatever Bytes Carried It: RFC 2070
Two HTML files could carry different octets and still present the parser with the same character. RFC 2070 made that result architectural rather than accidental: `charset` selected the decoder for the concrete resource, while HTML kept one abstract UCS document character set.…
History
One Arrow Was a Mapping. Only the Return Made It Equivalent: RFC 2157
An attachment can cross a gateway, keep its bytes and still arrive under a weaker claim than the word “equivalent” suggests. RFC 2157 made that distinction unusually precise: one transformation was a mapping; equivalence required the outward and return mappings together to…
Story
Rapport Counts Outcomes Only After a Requested Test Path Exists
LACNIC’s revised Rapport runner can expand several category and test selectors into a matrix. Yet a requested cell with no matching directory leaves no row in the result: it returns before a test identity is printed or any outcome counter moves.
History
The Password Left the Wire. Its Equivalent Stayed in the File: RFC 2069
“We do not store passwords,” an administrator might have said in 1997. “We store only their digests.” RFC 2069 made the first half of that reassurance meaningful on the network: a client could prove knowledge of a password without sending it in cleartext. It also made the second…
History
The Software Could Do It. The Gateway Still Had to Prove It: RFC 2156
RFC 2156 drew a line that procurement sheets still blur: a mail product may contain every required MIXER function while the gateway actually carrying traffic is configured for a narrower, non-conforming role. Distribution lists could turn that local corridor into a global…
IETF
EVPN Can Select One Multicast Source. It Cannot Certify Redundancy.
A receiver may show one clean programme while two contribution sources are transmitting. RFC 9856 explains how an EVPN can suppress the extra copy. It does not establish that the surviving source was healthy, equivalent, or switched without loss. Those are separate operational…
Story
APNIC’s Two-Nameserver Run Had Fewer Repeats. The Difference Still Needs a Reproduction Receipt
APNIC measured fewer authoritative DNS queries in a later run using two nameservers than in an earlier run using one. The observation is real in the published aggregates; the cause is not settled. A reproducible decision needs the two treatments to share a clock, cohort and…
CASE FILE
The Registry Marked the Version. It Did Not Supply the Meaning: RFC 9713
RFC 9713 added one small column to an IANA table and, by doing so, exposed a large operating mistake. A code point can be allocated, valid for BPv7 and safely clear of the public assignment pool while still saying nothing about whether this receiver knows its content, shares the…
History
The Version Number Promised the Next Message, Not This One: RFC 2068
In January 1997, an HTTP message that began with `HTTP/1.1` was making a carefully bounded promise. The label described the sender’s message format and the highest HTTP capability it could support in further communication. It did not say which HTTP/1.1 features this particular…
History
The Address Was Easy to Read. It Was Not the Address on the Wire: RFC 2155
RFC 2155 gave an APPN management console a human-readable data-link address while warning that the value was for display only. The actual bytes in the DLC header belonged to another evidence source. That small boundary still matters whenever an operator mistakes a legible label…
IETF
The teardown that must leave a reservation alive
In RFC 9705, receiving a Conditional PathTear can make deleting state the wrong action. The decision depends on an established protection role—and on whether neighbouring routers can honour the same rule.
IETF
The Reply Crossed Three Domains. The Proof Did Not
RFC 9716 gives an SR-MPLS echo reply a route home when ordinary IP reachability ends at a domain boundary. Its label stack can be supplied in advance or assembled border by border. That makes inter-domain diagnosis practical; it does not turn one returned echo into proof that the…
History
The Signature Knew Who Spoke. It Could Not Know Whether the Link Was Real: RFC 2154
RFC 2154 let an OSPF advertisement carry its origin evidence through every flooding hop. That was a remarkable change from trusting only the neighbour that handed over the packet. Yet the RFC drew its own harder boundary: a router could sign a false metric, a dead link or a…
IETF
Where TreeDN’s replication saving stops
A network can send fewer copies of a live programme and still owe the viewer a usable picture. RFC 9706 makes replication easier to buy; it also exposes how much of delivery sits outside the replication contract.
IETF
The Orbit Said the Link Was Ready. The Network Had Not Agreed
RFC 9717 turns orbital predictability into a routing advantage without confusing a forecast with an observation. Its proposed satellite architecture can prepare for scheduled change, but a schedule, a computed SID list and even a successful install receipt remain different claims…
History
The Namespace Arrived. Understanding Did Not: RFC 2153
RFC 2153 gave proprietary PPP extensions a shared outer address: Code or Type 0, an OUI, a Kind and vendor-defined values. That prevented private meanings from colliding in the public fields. It did not make those meanings public, prove that a peer understood them, or turn…
History
The Text Looked Readable. The Gateway Still Had Choices: RFC 2152
UTF-7 let a 1997 mail reader leave much of an ASCII message in plain sight while carrying the rest of Unicode through a seven-bit channel. That readability was useful, but it was never a preservation receipt: punctuation could take more than one legal route, shifted text could…
Story
RIPE’s RDAP Marks a Mixed AS Block Reserved at Either Boundary
RIPE’s RDAP Marks a Mixed AS Block Reserved at Either Boundary 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. The…
History
The Server Stopped Speaking It. The Client Still Had to Understand: RFC 2062
In December 1996, IMAP drew a line that software migrations still struggle to express. A new server could retire an old command without demanding that every client forget how to read it. RFC 2062 made compatibility directional: stop producing obsolete syntax, keep only the…