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
Both Slices Were Admitted. Only One Queue Was Real
An IP/MPLS slice can pass every control-plane admission check and still lose its service promise when packets meet a shared scheduler. The missing proof sits between the reservation ledger and the live queue.
History
The IPv4 Address Was Only a Local Handle: RFC 3338
The old application believed it had received an IPv4 address. On the wire, no such destination needed to exist. RFC 3338's Bump-in-the-API mechanism intercepted name and socket calls, assigned a temporary IPv4-shaped value from a private local pool, and used that value to recover…
IETF
The Preview Passed. The Dangerous Bytes Had Not Arrived.
The adaptation service saw the headers and the opening body segment, then returned a decision. The decisive bytes were still in the unseen tail. RFC 3507 makes that observation boundary measurable instead of magical.
History
A Class Identifier Was Not a Latency Guarantee: RFC 3337
The network had recognized the voice packet. That did not mean it would move first. RFC 3337 gave PPP over AAL2 a way to assign fragments from different traffic classes to separate Channel Identifiers, but it deliberately left the scheduler to the implementation and the service…
IETF
The Signature Survived Preprocessing. The Provenance Trail Did Not
A valid COSE signature can preserve the origin and integrity of one YANG dataset while saying nothing about the unsigned transformation that produced the data now driving a controller.
History
One Lost ATM Cell No Longer Had to Destroy the Whole Bundle: RFC 3336
A packet can fail because its bits were lost. It can also fail because an engineer chose to bind it to other packets before deciding whether any of them survived. RFC 3336, published in December 2002, addressed that second kind of failure. By carrying PPP through AAL2's Common…
History
The Meter Counted Only What the Policy Asked It to See: RFC 3334
An accounting record looks retrospective: a statement of what a customer used. RFC 3334 exposed the prior decision hidden inside it. Before a byte became a record, policy could decide which flows existed for accounting purposes, which attributes survived, how often the meter…
History
The Routing Key Chose the Traffic. Network Appearance Named the SS7 Context: RFC 3332
M3UA moved MTP3-user messages across IP, but it did not give every identifier the same job. A Routing Key described which SS7 traffic an Application Server should receive; a Routing Context named that key; and Network Appearance supplied a locally coordinated view of which SS7…
History
The Gateway Turned the Route Into a Key: RFC 3332
RFC 3332 described a gateway that did more than carry signalling from one network to another. It terminated the SS7 network layer, inspected the coordinates of each message and used a configured Routing Key to decide which remote application should receive it. That key made…
IETF
The Download Link Was Fast. The ACK Path Set the Pace.
A wide downstream pipe advertised the headline rate. TCP advanced only when small acknowledgments crossed a narrow return path. RFC 3449 shows why capacity in one direction is not a receipt for useful delivery in the other.
IETF
The Link Loaded. The Filtering Incident Never Happened
A resolver can point to a real database page and still lie about why a name failed; DNS filtering transparency begins only when the application keeps routing, trust and proof apart.
History
The SS7 Link Stayed at the Gateway. Its User Moved Across IP: RFC 3331
In M2UA, “user” did not mean the person making a call. It meant MTP3, the layer immediately above an SS7 signalling link. RFC 3331 kept the wire and MTP2 machinery at a gateway, then carried that upper boundary across SCTP to a remote controller. The resulting system could show a…
History
The Address Looked Ordinary. The Packet Was Not Allowed to Behave Ordinarily: RFC 3330
Every IPv4 address fits into the same 32 bits. Its operational meaning does not. A destination can describe this host, one link, a private interior, an example, a laboratory or a public endpoint. RFC 3330 gathered those exceptions into one catalog—and exposed why the catalog…
IETF
The Reflector Returned an Address. It Did Not Return an Exit Plan.
RFC 3424 treated self-address discovery across NAT as a temporary heuristic, not a new identity system. The harder question was never whether a reflector could report a mapping. It was who would retire the dependency after applications learned to need it.
IETF
The Grease Range Passed. Every Other Unknown Value Still Failed
A middlebox can learn to permit the values reserved for anti-ossification tests while continuing to reject every genuinely unfamiliar DNS extension, turning the test itself into a new fossil.
History
The Stronger Lock Was Offered. The Attacker Removed It Before Selection: RFC 3329
The first security offer traveled before there was any agreed security to protect it. That circular problem made a one-line deletion powerful: erase the stronger mechanism, and two capable SIP peers might settle for less. RFC 3329 answered with a receipt delivered later, after…
History
A REGISTER Was Temporary. Its Route Was for Later: RFC 3327
A registrar could know which contact to call without knowing every proxy that a future call had to cross. RFC 3327 attached an ordered Path to a contact binding so the home proxy could reuse those route references after REGISTER had finished. That Path prescribed later routing…
History
The Registrar Knew the Contact. It Still Did Not Know How to Reach It: RFC 3327
A successful registration can answer the wrong question perfectly. SIP could tell a registrar which Contact belonged to a public address, yet still leave the home network unable to reproduce the route required to reach that Contact. RFC 3327 turned that missing route into state…
IETF
The Answer Arrived. The Resolver Never Accepted the Limit
A proposed DNS option lets a client cap how much address information a recursive resolver may disclose, but a normal answer can conceal the most important fact: an older resolver may have ignored the request completely.
IETF
The Server Never Rejected the Connection. The Firewall Rejected Two New Bits.
A TCP reset looked like the remote endpoint had refused the connection. RFC 3360 showed why that conclusion could be false: an on-path box might have generated RST merely because an ECN setup SYN used two formerly reserved flags.