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 Registry and the RFC Disagreed. Running Code Chose the Registry: RFC 3115
In 2001, a standards-track RFC and the IANA registry assigned different numbers to the same Mobile IP extensions. The replacement RFC settled the conflict with an unusually direct fact: implementations were already using the registry values.
History
The Prefix That Could Not Return Traffic: RFC 5220
An IPv6 host could hold two valid addresses, send a packet through the wrong provider, and leave the reply aimed at a prefix with no public return route. RFC 5220 named this a host-selection problem; it did not report a measured outage or prove how often it occurred.
History
The Password Matched. The User Was Not Yet Authenticated: RFC 3112
RFC 3112 gave LDAP a way to test a password against a derived value in the directory. It also drew a hard line around the answer: a match could be true while no directory association had authenticated the client.
Story
The frozen stack: what DFINFRA's address footprint can and cannot prove
The frozen stack: what DFINFRA's address footprint can and cannot prove 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.…
History
Both Layers Said Forward. They Meant Opposite Directions: RFC 3108
RFC 3108 exposed a problem more dangerous than a missing field: two legitimate control systems used the word “forward” from different origins. A media gateway could receive a perfectly valid traffic descriptor and still have to reverse its direction before using it.
History
The New RFC Fixed the Session Label, Not the Payload Design: RFC 5219
In 2008, RFC 5219 replaced an MP3-over-RTP specification whose example already named the right format while its prose told session descriptions to use the wrong one. The revision corrected that split and clarified implementation pseudocode; its own change note did not claim a new…
History
The Gateway Lent the Address. Locality Became a Protocol: RFC 3102
Realm Specific IP offered a striking alternative to invisible address translation: let the private host borrow public addressing parameters and place them in its own packets. The address moved into the host, but allocation, lease, policy and return-path control remained at the…
History
DHCP Authentication Stayed Inside the Trust Domain: RFC 3118
RFC 3118 added authentication to DHCP, but not a network-wide identity service. Its delayed exchange assumed that a client and server could receive a shared secret out of band inside one administrative domain—and left the decision to accept an unauthenticated offer to local…
History
Before Consent Became a Checkbox: RFC 3098
RFC 3098 did more than ask Internet advertisers to behave. It turned responsibility into an operating design: do not preselect the audience, tell people how their data will be used, confirm the request with provenance, make removal possible, and keep the cost of maintaining a…
Story
The company behind the dormant network: what the Hamburg register can prove that AS210860's registry layer cannot
The company behind the dormant network: what the Hamburg register can prove that AS210860's registry layer cannot intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
IETF
The Channel Stayed Secure. Its Attested State Did Not Stay Current
Binding fresh attestation evidence to a TLS connection closes a dangerous substitution gap at the handshake. It does not freeze the endpoint’s software, policy or authorization state for the lifetime of that connection.
IETF
One Packet per Second Is Not Idle
PowerBench revision 03 turns a tiny traffic trace into a large warning for buyers of network equipment: a watt figure cannot be compared until the useful work, device state, configuration, meter and time window have been made part of the same result.
History
ROHC Began Without a Return Channel: RFC 3095
Before ROHC could trust an acknowledgment, it had to work where no acknowledgment could come back. RFC 3095 therefore made every compression context begin in unidirectional mode, then let the decompressor—not the compressor's optimism alone—request the move to feedback-driven…
IETF
The Peak Had a Timestamp. The Fifteen Minutes Still Had No Sequence
A new BMP statistics format can expose the peak that disappeared between two identical snapshots. It still cannot say whether the route surge lasted seconds, dominated the window or arrived before the collapse.
Europe and Middle East Cloud Services
The Routing-Policy Swap Behind AS210328: What the August 2026 Registry Edit Changed — and What It Did Not
The Routing-Policy Swap Behind AS210328: What the August 2026 Registry Edit Changed — and What It Did Not intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…
Story
The contractual tail: how African LIRs stayed RIPE NCC members while AFRINIC served them
The handover of Africa's internet number registry is usually told as a single act of recognition. The dated instruments tell a more layered story: for over ten months after AFRINIC began operating, African members were legally RIPE NCC members under the RIPE NCC Standard Service…
CASE FILE
The Draft Had Eight Numbers. The Registry Still Had None
On 1 October 2026, an OpenPGP implementer could place two official-looking documents side by side and receive two different answers. Revision 05 of a working-group draft called eight composite algorithms 37 through 44. The live IANA registry still called the entire range from 37…
History
Foo Entered the RFCs Before the RFCs Explained It: RFC 3092
In December 1971, RFC 269 told a user to rename `FOO` as `BAR` and assumed the example needed no cultural translation. Three decades later, RFC 3092 counted roughly seven per cent of the RFC Series carrying the same private vocabulary. The explanation arrived after the convention…
IETF
The Site Reported Zero. Its Routes Could Still Remain in BGP
A revised edge-metadata draft turns one zero-value update into a site-wide forwarding decision. The control is compact; proving which routes, routers and live flows actually obeyed it is not.
History
The Firewall Allowed HTTP. It Had Not Approved the Packet Inside: RFC 3093
RFC 3093 proposed putting a complete IP datagram inside an HTTP message, passing it through the ordinary web opening, and reinserting it behind the firewall. Published on 1 April 2001, the comic design exposed a serious limit: a policy decision about an outer envelope says…