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
The Tag Survived the Mask. The Node Still Proved Nothing
Revision 11 of an expired NETMOD draft turns node classification into a composed operational view: automatic tags, intended user choices, and exact-match masks meet in one visible set. That set is useful for discovery. It is not a certificate of what the node is, does, or…
History
The Bytes Kept Their Delimiters. Meaning Still Needed Another Contract: RFC 2044
UTF-8's first Internet-era promise was not that software had learned every language. It was that multilingual characters could enter systems built around ASCII without hiding an ASCII delimiter inside a multibyte character. RFC 2044 made that promise inspectable at the byte…
Story
ARIN Waited for a Geofeed Standard. Its RDAP Help Still Does Not Claim It.
Two years ago ARIN tied a community request to a visible trigger: once the common RDAP geofeed standard was accepted, three named product surfaces would change. The standard is now RFC 9877. The useful question is no longer whether the IETF will finish the vocabulary, but how an…
History
One PPP Link, Two SNA Permissions: What RFC 2043's Open State Could Not Prove
A line can be up while the thing an operator cares about is still down. RFC 2043 made that distinction unusually concrete: on one PPP link, SNA with LLC 802.2 and HPR SNA without LLC were admitted by different control protocols. Each could open without speaking for the other, and…
CASE FILE
The Private Number Was Valid. The Instruction Was Still Unowned: RFC 9752
A vendor payload can cross a stateful PCEP session with a real enterprise number and perfect framing while leaving the decisive questions unanswered: who published its meaning, what the PCC was allowed to do, what the device installed, and what the traffic experienced.
IETF
ACTN’s Abstract Topology Is a Policy View, Not a Physical Inventory
An optical controller may show a coordinator that two packet edges could be connected while withholding the fibres, wavelengths and vendor-specific constraints underneath. That abstraction is not a defective inventory. It is a deliberately governed view. The evidentiary mistake…
History
The Next Macroblock Could Start Cleanly. The Picture Was Still Damaged: RFC 2032
RFC 2032 gave an H.261 receiver a deliberate place to resume after packet loss and a compact way to ask for corrective action. Neither mechanism certified that the missing picture returned, that prediction state was right, or that a viewer saw an uninterrupted frame.
History
255 Was a Workshop Tag, Not a Private BGP Namespace: RFC 2042
Two unfinished BGP attributes could both wear the number 255 and still mean entirely different things. That was the point. In RFC 2042, the value marked work under development; public identity began only when an attribute was documented and IANA assigned it a unique code.
Story
APNIC's ASPA Interface Checks Observed Paths. A Standby Provider Leaves No Path to Check.
APNIC has built a sensible safety rail into its new ASPA interface: suggest providers from visible routing data, then show how an edit would affect paths that BGP observers can see. The awkward provider is the one hired precisely not to be visible yet. A standby link turns the…
CASE FILE
The Message Continued. The Constraint Went Missing: RFC 9753
RFC 9753 lets stateful PCEP peers keep working when selected entities are optional. That is a useful availability mechanism. It is not evidence that the ignored meaning survived, that the replacement LSP is equivalent, or that forwarding remained safe.
IETF
The Template List Was Present. The Intended Configuration Was Not Yet Proven
Revision 03 of the YANG configuration-templates draft turns list order and ancestor depth into configuration semantics. Reconstructing the intended tree is therefore possible only from a complete, same-version evidence bundle—and even a perfect reconstruction stops before…
Story
AFRINIC’s ccTLD Map Counts 27. Three Require an Address Join.
AFRINIC’s new DNS surface gets the total right, but it does not show the work behind the number. Twenty-four of its 27 ccTLD rows name the registry in a delegated hostname. Somalia, Nigeria and Mali become legible only when their nameserver addresses are joined to AFRINIC’s…
History
The Clock at the Edge: RFC 2030 and the Evidence Lost When One Reply Becomes Time
RFC 2030 made Internet time small enough for simple devices by preserving the NTP packet while discarding most of the machinery around it. Its warning was architectural: an SNTP client belonged at a leaf, not in the middle of a dependency chain, because one usable reply could set…
History
The Server Was Up. The Website Was Not: RFC 2039’s Missing Layer
In 1996, one short RFC identified a management error that survives every change of tooling: a machine can be measurable, orderly and alive while the service it is meant to provide is failing somewhere else.
Creators
David S. Miller and the shared authority behind Linux networking
A Linux networking change may begin on a public mailing list, then reach servers, routers, phones and industrial equipment worldwide. David S. Miller has spent decades where such changes are tested, debated and accepted as long-term commitments. His public record runs from the…
Story
LACNIC’s BGP Case Counts 368 Route Peers. The Vendor Could Not Produce a Definitive Installation List.
LACNIC’s latest routing-security case is unusually rich in network evidence and unusually poor in application evidence. The route, certificate and attack window can be reconstructed in detail; the vendor still cannot say which installations accepted the malicious update. That gap…
Story
AFRINIC's Prefix Checker Can Supply the ASN From BGP. The Verdict Keeps Only the RPKI Time.
AFRINIC's Prefix Checker Can Supply the ASN From BGP. The Verdict Keeps Only the RPKI Time. intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
CASE FILE
The Controller Said Done. The Packets Had Not Testified: RFC 9757
RFC 9757 gives a PCE an experimental vocabulary for coordinating Native IP paths, but its acknowledgements end inside the controller–client conversation. Leadership still needs independent proof that BGP, routing policy, forwarding hardware and live traffic enacted the same…
History
Eight Bytes Drew a Recovery Boundary: RFC 2029 and CellB After Packet Loss
RFC 2029 gave every CellB packet its own spatial address: the first 4×4 cell’s coordinates and the image dimensions. That small repeated header let a receiver resume at a known place after loss, but it did not replace the missing cells or prove that the resulting frame was…
IETF
One MAC Address, Four Spellings: A YANG Draft Redraws the Duplicate Boundary
The proposed rule is easy to miss because nothing on screen has to change. A value can keep the colon, hyphen and letter case that arrived over the wire, while a second, invisible form decides whether another configuration entry is a duplicate.