Intelligence
Latest Articles
Latest intelligence on infrastructure operators, policy decisions, market moves, and digital power shifts.
History
The IAB Endorsed CIDR. Four Different Actors Still Had to Make It Real: RFC 1481
In July 1993, the Internet Architecture Board used a sentence that sounds like a finish line: it “endorses the CIDR architecture and its implementation.” The sentence mattered. It still did not allocate an address block, add classless code to a router, install that code in a…
History
The Aggregate Had a Home AS. That Did Not Mean Every Announcement Came From Home: RFC 1482
RFC 1482 gave one aggregate a Home AS, then listed other ASs that would announce the same prefix to different neighbors. The table did not contradict itself. It recorded a chain of intended propagation in which origin, onward announcement, acceptance, installation and delivery…
History
The Name Existed in .US. That Did Not Mean the Zone Had Been Delegated: RFC 1480
Two names could appear equally real beneath `.US` in 1993. One might be a direct MX entry for a UUCP host; another might sit inside a branch whose manager ran its own name servers. The resolver made both names visible. RFC 1480 did not give them the same authority, network…
History
The Route Was Advertised. Five Decisions Still Controlled Its Fate: RFC 1476
A routing announcement is easy to mistake for a forwarding fact. RFC 1476 made that shortcut impossible. Its experimental Route Access Protocol put every received offer through a sequence of local decisions: filter it, transform its attributes, aggregate it, choose whether to…
History
The Table Said the Remote Bridge Would Accept It. That Was Still a Local Belief: RFC 1474
A management station finds a green `accept` value beside a remote PPP bridge. It looks like a statement about the other machine. RFC 1474 chose a more careful verb: the local entity *believes* the remote entity will accept that MAC type. The table offered a usable conclusion…
History
The Prototype Kept the Telnet Session Alive. It Had Omitted the Source Policy: RFC 1477
An early policy-routing experiment rerouted a live Telnet session after a gateway failure and again after a transit rule changed. That was valuable running-code evidence. The same report also recorded the functions its prototype did not implement, the lookup service it replaced…
History
The Compression Setting Changed. The Link Had to Restart Before It Mattered: RFC 1473
A manager changes one value on a live PPP interface and immediately reads the operational table. The console returns a compression method and a slot number. RFC 1473 treated those numbers with unusual honesty: until IPCP reached Opened, they were undefined. The write belonged to…
History
The Packet Carried a Route Identifier. It Did Not Carry a Route: RFC 1475
A field named “forward route identifier” sounds like a path folded into a packet. TP/IX proposed something more local and more interesting. Each router could lend the datagram a private handle for the next decision, then the next router could consume it and write another. The…
History
The Secret Row Was Marked Valid. No Peer Had Yet Authenticated: RFC 1472
In 1993 a network manager could inspect a PPP security table and find an identity/secret row marked `valid`. The word looked conclusive. RFC 1472 used it much more carefully: it meant that the configuration entry was currently usable, not that a peer had appeared, answered a…
History
The Charset Was Declared. The Byte Stream Still Had to Return to ASCII: RFC 1468
RFC 1468 gave Japanese Internet mail a portable name, `ISO-2022-JP`, but the name was only the entrance to the contract. Meaning still depended on a seven-bit stream changing character sets at exact escape sequences, returning to a safe state at every line boundary, surviving…
History
The Table Could Schedule the Route. It Could Not Prove the Relay Was Ready: RFC 1465
One example in RFC 1465 was updated on 18 December 1992 but did not become valid until 1 February 1993. That gap was deliberate: a routing declaration could arrive early so distant mail administrators had time to prepare. It also exposed the system’s central limit. A date in the…
History
The TXT Record Carried an Attribute. DNS Did Not Supply Its Meaning: RFC 1464
RFC 1464 made an elegant bargain: put `name=value` inside a DNS TXT record and old name servers could carry a new attribute without learning a new resource-record type. The bytes became easy to publish and parse. The authority to define the name, interpret the value, trust its…
History
The Network Dropped the Best Layer First. It Was Preserving the Usable Base: RFC 1458
In RFC 1458's layered image design, the packet carrying more detail could be the first rational sacrifice: the base layer made the image usable, while the enhancement depended on it. That inversion exposed a durable boundary between a quality label, a queue decision and an…
History
The Prefix Named the Sender. The Server Still Had to Check the Link: RFC 1459
A colon opened the message, and a name followed it. On the wire, that looked like an origin. Inside the receiving IRC server, it was only the beginning of a test. The server still had to find the named source in its own database and confirm that the source belonged behind the…
History
The Label Crossed the Network. Its Meaning Still Had to Arrive: RFC 1457
The label arrives intact. Every bit is where the sender left it. Yet the receiving machine still cannot decide which process may see the data, because preservation of a mark is not preservation of its meaning. It needs the semantic authority behind the mark, a trustworthy binding…
History
Six Control Codes Became Letters. The Label Had to Tell Readers Which: RFC 1456
The octet `0x02` could arrive unchanged at two machines and assert two different things. An ASCII-oriented program would meet a control code. A VISCII decoder would render a Vietnamese capital letter. In RFC 1456, the disagreement was not corruption. It was the price of fitting a…
History
The Packet Asked for the Safest Route. The Network Promised Nothing: RFC 1455
A packet reaches a router carrying four bits set to one. They do not lock its contents, certify the next hop or bind the operator to an outcome. In RFC 1455, they expressed something narrower and more revealing: a request that the network prefer the physical route it considered…
History
The Party Had a Name. The Triple Still Had to Permit the Operation: RFC 1447
A received SNMPv2 message could survive decoding, identify a known sender and still stop before a single managed entity was touched. The 1993 Party MIB put four separate questions in its path: who was asking, which party was being asked, which context held the resources, and what…
IETF
Juliusz Chroboczek and the Babel Metric That Was Not a Global Score
A route metric can be indispensable without being universal. RFC 8966 lets Babel nodes compute link costs and route metrics as local policy, then insists on a small common discipline: the resulting metric must be strictly monotonic if the protocol is to avoid persistent loops.…
Story
APNIC’s Resource Quality Check Is Not an Address Attribute
APNIC made a careful change in 2019: “assurance” became “check”. The distinction matters because a registry can observe routes, filters and reputation signals, but it cannot make thousands of other networks carry the result forward.