Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
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…
Creators
Jakub Kicinski: How Linux Turns Networking Features into Sustainable Infrastructure
A new network card may arrive with an impressive capability and a pressing commercial deadline. Linux must ask a slower question: can that capability be expressed in a form other devices can understand, operators can observe, tests can reproduce and maintainers can support years…
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…
North America Institutional Trends
Consenting holders’ 8.6m Hornbeck Jones Act warrants map to 88.5m shares—but citizenship controls issuance
Hornbeck Offshore Services inherited a block of Jones Act warrants whose gross arithmetic is large enough to look like immediate dilution. The 8,617,903 warrants held by consenting stockholders map, at 10.27167 shares each, to about 88.5 million common shares. Yet the filed…
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.…
IETF
Jari Arkko and the Registry Field That the Protocol Did Not Need
A protocol registry is often read as a durable record, which makes every old column look like a permanent requirement. RFC 8602 takes the opposite discipline: an inherited postal-address field in two TRIP registration procedures had no identified use, so IANA stopped collecting…
North America Institutional Trends
Public Storage’s Canada Deal Has Two Unit Prices and a $500m Debt Draw
Public Storage closed its PS Canada acquisition with an upfront value of about $1.2 billion. The filed mechanics are more revealing than the rounded headline: 2,762,108 operating-partnership units valued at $321.98 each, about $310 million in cash, a possible second unit issue…
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…
ICANN
ICANN’s Specific Reviews Are Paused. The Pause Needs a State Record
ICANN has not erased its Specific Reviews. It has put a temporary rule beside the old duty, with a known effective date, a first expiry, two possible routes to a further pause, a maximum outer limit and a prescribed route back into the reviews. That is a more disciplined response…
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…
North America Institutional Trends
Keurig Dr Pepper’s $925m Chobani Exit Starts with $400m Cash
Keurig Dr Pepper describes its Chobani transactions as producing $925 million of pre-tax proceeds. The filing divides that total into instruments with different clocks: $400 million of cash at closing, a $400 million note due on 26 December and $125 million of asset consideration…
IETF
VELOCE’s Call Chose an IANA Pointer. The WG Draft Still Says No IANA Actions
On 25 August, an attributed VELOCE project-call summary said that an IANA indirection model had been confirmed: a registry would point to the repository rather than place the module itself inside an RFC. The Working Group revision issued the same day ends with a contrary-looking…
IETF
Heather Flanagan and the RFC Archive That Cannot Freeze
An RFC can look unchanged to a reader while its publication machinery has changed underneath it. It can also acquire a cleaner HTML rendering, repaired XML or a regenerated PDF without acquiring a new protocol meaning. The two statements are easy to say and hard to govern.…
History
The Master Said Accepted. The Applications Had Not Reported an Outcome: RFC 1301
Twelve small verdicts travelled inside every Multicast Transport Protocol packet. One could say accepted, another pending, a third rejected. They looked like receipts, but they were not votes from twelve receivers. RFC 1301 gave one master the right to set those values after…
CASE FILE
The Link Named the Parent. It Had Not Frozen the Hierarchy: RFC 9910
RFC 9910 gives RDAP clients typed paths through number-resource hierarchies. Those paths are useful navigation, but they are not sealed records of what the registry would have returned at an earlier time.
History
The Agent Spoke with One Voice. The Subtree Had Another Owner: RFC 1227
To a management station, an SNMP agent looked like one speaker. RFC 1227 placed a switchboard behind that voice: local processes registered branches of the MIB, priorities chose which process answered, and a broader branch could hide a narrower one. The reply was real, but its…