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 Diagram Had a Bit. The Registry Did Not: RFC 9927’s C-Flag Repair
RFC 8928 drew a C-flag into a compact wire field without registering its position. A later standard properly allocated that same position to another field. RFC 9927 repairs the collision before known deployment made compatibility expensive—but publication cannot update a parser…
History
The Analysis Could Not Stand In for the Test Network: RFC 1245 and RFC 1246
In July 1991, OSPF arrived with more than a protocol specification. Its supporting case was deliberately divided into an analysis and an experience report. That division preserved a distinction Internet engineering still needs: a model can bound expected behaviour, but only…
IETF
BBF Needs the BGP Model. IDR’s WGLC Is Still Not a Publication Date
The Broadband Forum has a practical dependency: its WT-477i2 work refers to the IETF BGP YANG model. That dependency is neither trivial nor improper. The public error would begin only if a dependency notice were retold as a delivery promise. The IETF IDR Working Group’s August…
IETF
Joseph Touch and the UDP Options That Leave the Application in Charge
An extra field at the end of a UDP packet can make a protocol more useful without becoming a permission slip. RFC 9868, co-authored by Joseph D. Touch, draws that line unusually clearly: transport options can be carried after the user’s declared datagram, while the application…
Story
APNIC Logged 57,088 Addresses as M&A Transfers. Its Daily File Still Shows 2007.
One APNIC file says that nine IPv4 prefixes changed hands on 1 September 2026. The next daily statistics file gives every resulting row the date 3 December 2007. This is not a contradiction or a stale update. It is what happens when an event clock and an origin clock share the…
History
The NIC Owned the Question. It Did Not Own the Network: RFC 1302
A help desk can keep faith with a user without pretending to control every system behind the problem. RFC 1302 made that distinction unusually clear in 1992. A Network Information Center was expected to take responsibility for an inquiry until it was resolved in some way. Yet…
IETF
Loa Andersson and the MPLS Decision That Stopped at the Charter
An institutional decision can narrow a future work programme without configuring the network that later uses its protocols. RFC 3468 records an MPLS Working Group consensus, documented by Loa Andersson and George Swallow, to focus traffic-engineering signalling work on RSVP-TE…
Global Institutional
ARTEMIS and the minute between a BGP alert and a safe response
ARTEMIS compares public BGP observations with an operator’s own model of permitted routing to classify suspicious announcements and respond faster. Its history exposes the harder problem: when visibility is incomplete and a counter-announcement can itself cause harm, speed helps…
IETF
Deborah Brungard and the Transport Profile That Did Not Choose a Network
A standards requirement can make a capability available without dictating the network that will use it. RFC 5654, edited by Deborah Brungard and four colleagues, describes requirements for an MPLS Transport Profile. Its most important restraint is plain: the requirements concern…
History
The MIB Had to Redraw Who Could Change AppleTalk: RFC 1243 and RFC 1742
A management model is also a map of responsibility. In 1991, the first AppleTalk MIB let an SNMP manager write route fields and zone mappings while reporting how port settings had been obtained. Four years later, its replacement moved several of those lines. The revision matters…
CASE FILE
The Cache Header Said Fresh. RFC 9919 Says the Signed Response Decides
A cached OCSP response can arrive without the client ever touching the responder. Its HTTP envelope can announce that the entity is fresh, public and reusable. RFC 9919 permits that efficiency at immense scale, then draws a hard evidentiary line: those headers guide the cache…
CASE FILE
The Response Was Signed. Its “Good” Status Had Expired: RFC 9919
A cached OCSP response can remain perfectly signed after it has stopped being evidence of current certificate status. RFC 9919 makes that distinction the centre of scalable revocation checking: distribution may be shared, but the authority of “good” ends at a signed time boundary…
IETF
Alia Atlas and the TE Metric That Did Not Promise a Path
An advertised performance number can be useful without being a promise. RFC 7471, co-authored by Alia Atlas, gives OSPF entities a way to distribute selected link-performance information for traffic engineering. It does not prescribe how the information is measured or what a…
History
The Box Dropped No Frames. It Had Not Passed the Other Tests: RFC 1242
A clean throughput trial is seductive because it ends in one number. RFC 1242 gave that number a strict meaning, then surrounded it with other terms that refused to disappear. Zero loss at one offered rate did not answer latency, burst tolerance, overload, restart, filtering or…
History
The Counter Was Total. Subscription Discards Were Somewhere Else: RFC 1304
A number labelled total looks like the end of an investigation. In RFC 1304, it was the beginning of one. The 1992 MIB could count SIP packets discarded for protocol or bit errors, list other address-related failures and remember the latest disagreement of each syntactic type.…
CASE FILE
The CA Was Trusted. Its Other Certificates Entered the Control Plane: RFC 9918
A NETCONF server can trust the right certification authority for the wrong breadth of purpose. RFC 9918 warns that if the listed CA also issues certificates for unrelated uses, those certificates can be accepted into the management channel. The TLS chain may validate perfectly…
History
The Tunnel Carried the Packet. The Error Lost the Question: RFC 1241
A tunnel can look transparent in the forward direction and become opaque the moment something fails. RFC 1241 drew that asymmetry with unusual precision. Its outer packet could carry an untouched IP datagram through a separate routing space. But an ICMP error from inside that…
CASE FILE
The Error Was Seen in Reverse. The Forward Link Was Removed: RFC 9917
A router at the far end records receive-side errors. Policy turns that observation into a colour on the reverse directed edge. Another router can then remove the forward edge from a Flex-Algorithm topology. RFC 9917 makes this chain computable; it does not make the colour a…
IETF
Lars Eggert and the UDP Datagram That Did Not Escape Shared Costs
UDP gives an application a small transport contract. It does not give it a private network. Lars Eggert's work on RFC 8085 makes that distinction operational: the freedom to choose datagrams leaves congestion responsibility with the traffic that actually shares a path.
History
The MIB Arc Changed. Vendors Still Had to Revise: RFC 1239
Nothing in a management console announces that a number has become architecture. RFC 1239 did. Five MIBs kept describing familiar interfaces, yet their entity identifiers moved from an experimental branch to standard branches. The standards record changed in two pages; every…