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 Tunnel Kept the Packet and Lost the Congestion: RFC 9599
A tunnel can deliver every packet in view and still break congestion control. If its egress removes the only header carrying a congestion mark, the packet emerges apparently clean, the sender keeps its old rate, and a successful decapsulation becomes a false report of spare…
History
PREPARED Survived the Crash. The Proof Had to Survive Too: RFC 2372
RFC 2372 placed a quiet but consequential condition on a transaction manager’s vocabulary. Before a subordinate could say PREPARED, it was supposed to leave behind a recovery record. Before a superior could say COMMIT from that state, it was supposed to preserve another one. The…
History
The Smaller Reservation Succeeded. The Larger Circuit Stayed: RFC 2380
RFC 2380 allowed an RSVP request for fewer resources to be reported as a successful change even when ATM could not build the smaller replacement and the old, larger circuit remained. That 1998 rule was not sloppy accounting. It exposed the price of preserving service when…
Story
APNIC Was 3.0% of One Geofeed Success Sample. That Is Not an Adoption Rate
The smallest bar in an APNIC 62 chart is precise to one decimal place. The footnote does more work than the bar: 200,000 geolocation rows were sampled, publishers were reduced to distinct netnames, and two of the five RIRs were left out. The result is a useful signal about one…
History
David Tennenhouse and the Packet That Asked the Router to Run Code
In the passive Internet, a packet could ask to be forwarded. David Tennenhouse and David Wetherall proposed a more demanding message: a capsule that arrived carrying, or naming, the computation it wanted the next node to perform. That change made service innovation faster in…
History
The Guaranteed Circuit Began with an Unguaranteed Message
In August 1998, RFC 2379 confronted a small architectural embarrassment inside RSVP over ATM: the control message requesting reserved service was supposed to travel first across the ordinary best-effort path. That choice was not a contradiction to be hidden. It was a disciplined…
History
The Envelope Reached the Area. The Application Still Had to Believe It: RFC 2370
RFC 2370 gave OSPF a reusable envelope for information the base routing protocol did not itself define. The envelope could be scoped, flooded, acknowledged and stored with ordinary link-state machinery. That success stopped at a precise boundary: the receiving application still…
IETF
The exporter saw a QUIC field. It did not see the whole connection
IPFIX can give operators a common vocabulary for QUIC observations. It cannot turn one configured vantage point into a complete connection, application or outcome receipt.
Story
APNIC's AS0 Maintenance Window Has a Delegation Clock
Four service names appear in APNIC's notice for 29 September, with no downtime expected. One of them is not merely a page to reach. The AS0 ROA Service makes a security assertion about address space that APNIC has not delegated. If an address moves out of that category, the…
CASE FILE
The Claim Was Visible Before It Was Trusted: RFC 9597
RFC 9597 lets a COSE entity expose selected CWT claims before decryption or without an attached payload. That convenience can guide key discovery and routing, but it creates a dangerous interval in which a claim can influence the system before the system has earned the right to…
History
The Link Wrote the Message. The User Still Had to Send It: RFC 2368
RFC 2368 turned a web-era address link into a compact message template: recipient, selected headers and even a short body could arrive prefilled. Its decisive safeguard was the remaining gap. Resolving `mailto:` created a draft, not a transmission, and the user still owned the…
History
The Identifier Looked Like Email. It Was Not a Mailbox: RFC 2377
RFC 2377 tried to make LDAP naming deployable by borrowing names the Internet already had. Its most revealing warning concerned a value that looked perfectly familiar: `uid=mailbox-shaped-identifier` could name a directory entry without being a working email address. Reuse…
IETF
The window grew. The path did not promise the next burst
A congestion window is a sender’s control state, not capacity booked from the network. That distinction matters most when the application or receiver has left much of the window unused.
CASE FILE
The Header Named the Object. It Did Not Authorize the Action: RFC 9596
A protected type label can stop one COSE entity from masquerading as another. It cannot tell an application that the payload is true, that the signer was entitled to send this class of entity, or that any requested action should occur.
History
Craig Partridge and the Gigabit That Did Not Need a New Internet
In 1989, one gigabit per second sounded large enough to indict an architecture. Craig Partridge answered by refusing to let the unit make the decision. He converted the rate into packets, instructions, memory touches, buffers and round trips, then asked which component actually…
History
The Envelope Overruled the Document: RFC 2376
RFC 2376 gave XML two places to declare its character encoding: the transport envelope and the document itself. In one common case, a missing value outside the document defeated an explicit declaration inside it. The history is a compact lesson in where protocol authority…
History
The Manager Deleted the Row. The Circuit Could Still Exist: RFC 2366
RFC 2366 gave operators a common SNMP view of multicast over ATM. Its most revealing rule was not a counter or an address: a client, server or MCS row could disappear while associated virtual-circuit rows still existed or were in use. The management model could forget a parent…
History
The Group Number Stayed the Same. The Membership Did Not: RFC 2375
RFC 2375 gave early IPv6 multicast services durable names across several scopes. It also drew a line that operations still depends on: the same group number at another scope is another group, and a node has to join it separately. The registry named the destination. It did not…
IETF
BTPU could repeat every segment. It still could not say the bundle arrived
On a one-way link, sending another copy can improve the odds. It cannot manufacture the missing observation at the receiver, or carry that observation back.
CASE FILE
The Token Opened the Door. The KDC Still Had to Admit the Member: RFC 9594
An access token can be authentic, correctly scoped and still prove no group membership at all. RFC 9594 makes that distinction operational: permission is issued at one authority, admission is completed at another, and usable group state exists only after a further exchange.