Content Type
Analysis
Within the Content Type facet, Analysis intelligence gathers BTW.MEDIA articles that share the same editorial format, helping readers compare briefings, profiles, risk notes, market analysis, and event coverage without mixing different kinds of evidence. The page explains how this content type frames internet infrastructure events, company movements, governance decisions, operational signals, and public evidence across the site. Readers can compare which actors or infrastructure systems appear most often, how source quality changes interpretation, and whether the material is a durable profile, a time-sensitive event, a strategic market signal, or a governance development. The result is a useful search page for operators, investors, customers, analysts, and policy stakeholders who need to understand the consequence, timing, and evidence behind similar article formats.
History
The Address Changed. The References Did Not: RFC 1900 and the Hidden Cost of Renumbering
In 1996, the Internet Architecture Board described a task that sounded almost clerical: replace one set of IP addresses with another. Then RFC 1900 followed the old numbers out of the router and into configuration files, applications, licences and human-maintained lists. The…
History
The Old Address Fit Inside IPv6. Its Routing Model Did Not: RFC 1888
A twenty-octet address can be placed beside a sixteen-octet one, sliced, tagged and reconstructed. That arithmetic says nothing about whether the route hierarchy survives the move. RFC 1888 recorded this distinction in 1996: its encodings could preserve address bits, while the…
Story
ARIN Adopted an Amended IPv6 Task Force Charter. The Public Index Does Not Show It
ARIN’s Board minutes record the creation of an IPv6 Task Force, an amendment that shortened its planned life, and three people who volunteered to do the work. What the public record does not yet supply is the operative text that joins those facts into a mandate. The missing…
History
The Test Address Came With Its Eviction Notice: RFC 1897 and the 6bone
In 1996, an IPv6 address could be useful, globally coordinated and routable across an experimental backbone while still carrying no promise of permanence. RFC 1897 made that distinction explicit: its addresses were for prototype testing, would be reclaimed and required their…
History
The Peer Returned a DNS Address. It Had Not Proved Names Would Resolve: RFC 1877
The useful answer in a 1995 dial-up exchange could begin with a deliberately useless address. A PPP client placed zero in an IPCP name-server option precisely so the remote peer would reject the value and suggest another. That suggestion could become negotiated configuration only…
History
Readable Without a Parser Did Not Mean Safe to Parse: RFC 1874
In 1995, one MIME label tried to preserve two truths about the same structured document. A person without SGML software might still read its general meaning; a machine with SGML software might interpret far more than the visible lines. RFC 1874 called the first case `text/sgml`…
Global Datacenter Trends
Equinix unveils Fabric One for managed multicloud networking
Fabric One will let customers specify connectivity requirements while Equinix manages routing, cloud links, encryption and failover.
History
The Departure Packet Asked Everyone to Forget. It Could Not Prove They Did: RFC 1868
In 1995, a dial-in user could leave one communications server and return through another while the local network kept sending packets to the first. RFC 1868 proposed a sixteen-byte correction: broadcast an unusual ARP Reply that told every peer to delete the departed address from…
Story
APNIC’s Registry API Returns Batch Results Without a Request-Item Field
APNIC’s Registry API can accept several creates, updates and deletes in one batch. Its public schema then reduces each result item to `status` and `message`, without declaring which request item the row answers. That is not evidence of a failed API. It is a small contract gap…
History
The Message Reached the Partner’s System. The Transaction Had Not Been Accepted: RFC 1865
A purchase order can cross the Internet without crossing the final boundary that matters. In 1996, RFC 1865 described a dedicated SMTP connection delivering EDI directly to a trading partner’s system and called that delivery assured. The phrase was useful at the transport layer…
History
The Shortest Timer Usually Won. The Client Still Had to Absorb the Race: RFC 1863
Redundancy sounds decisive only from a distance. Put two route servers beside the same clients, and it appears that either can replace the other. RFC 1863 described the harder machinery: each server kept its own picture of who was already being informed, waited for a load-ranked…
Story
AFRINIC Reports 3,927,253 Learning Behaviours. Its Academy Signup Does Not Explain the Record
AFRINIC has published an unusually precise measure of its online teaching: 3,927,253 learning behaviours tracked after xAPI was integrated into every lesson. Precision makes the Academy look measurable. It also makes the missing join between the public measurement claim and the…
History
The Page Was Delivered. The Person Had Not Read It: RFC 1861
In 1995, a pager protocol confronted a problem that still defeats much newer systems: the word “delivered” can end an inquiry too early. RFC 1861 made a gateway report not one success but a sequence of bounded states. A request could be accepted, held in a queue, transmitted to a…
History
The Etiquette RFC Assigned Responsibility. It Did Not Create a Global Referee
The Internet wrote down its manners in 1995 and immediately limited what the document could mean. RFC 1855 was Informational, not an Internet Standard. It offered a minimum that organizations could adapt, not a universal code that the IETF would enforce. That restraint was more…
History
The Permission That Survived Deletion: How IMAP Separated ACL Entries from Effective Rights
The administrator removed Fred from the mailbox list. Fred could still write to it. Nothing supernatural had happened, and the server did not need to be broken: Fred might also belong to a group, or receive the same authority through `anyone`. In the access-control language that…
History
The Address That Had to Be Empty: How SMTP Stopped Errors from Mailing Errors
The most important address in SMTP is sometimes no address at all. A delivery failure has to travel back to the system responsible for the original message, yet a failure to deliver that failure must not produce another failure notice, and another after that. `MAIL FROM:<>`…
History
The Number That Stopped Naming Every Packet: How IPv4 Narrowed the Identification Field
IPv4 put a 16-bit Identification value in every header so a receiver could reunite fragments of one datagram. Over time, the value was treated as a more general packet identity—even when fragmentation was impossible. Link speeds then outran the number space, implementations…
History
The Address That Recruited a Subnet: Why Routers Stopped Forwarding Directed Broadcasts
One IPv4 datagram could cross the Internet as an ordinary routed packet, reach the router responsible for a remote network and become a local broadcast there. With a victim's address forged as the source, that last-hop conversion could turn willing hosts on someone else's subnet…
History
The Link That Borrowed Its Address: How Relative URLs Made Documents Movable
A short hyperlink is not a small absolute address. It is an instruction to borrow missing components from a base. That dependency let authors omit repeated schemes, hosts and path prefixes, and it let a collection of pages move while preserving its internal edges. The economy…
Story
RIPE NCC’s Fibre Returned in Minutes. Access Recovery Took About Thirty Minutes
On 27 May, a supplier’s work in a manhole disconnected RIPE NCC’s fibre for only a couple of minutes. The connection came back and recovery was automatic. Yet RIPE NCC says it took about thirty minutes for everything to recover. The useful question is not whether automation…