X.25
In 1976, when the International Telegraph and Telephone Consultative Committee adopted X.25, no one suspected that this protocol would survive for more than thirty years. Yet this technical standard, born from heated debates between French and British engineers, would lastingly shape the architecture of data networks.
The first questions about the future of digital communications were emerging. ARPANET had taken its first steps across the Atlantic since 1969, but in Europe, the situation was radically different. Telecommunications administrations reigned supreme over the infrastructures. In France, the Direction générale des télécommunications held the reins, just as the British Post Office did in the United Kingdom. These public monopolies did not look favorably upon the relative anarchy that characterized American developments.
Packet switching sparked passionate technical debates. This method, which breaks messages into small portions to optimize their circulation, divided the scientific community. On one side, Rémi Després from CNET staunchly defended virtual circuits: each communication follows a predetermined path through the network, which guarantees a certain order. On the other, Louis Pouzin and his team at IRIA advocated for datagrams: packets navigate freely, finding their route according to network availability.
This technical quarrel concealed much broader stakes. Virtual circuits appealed to traditional telephone operators through their predictability. They recalled the familiar world of classic telephone switching, where each call establishes a dedicated circuit. Datagrams, on the other hand, embodied a different philosophy, closer to the libertarian spirit blowing across American campuses.
The adoption process at the CCITT resembled a game of diplomatic chess. Larry Roberts, despite being the father of ARPANET, paradoxically supported virtual circuits from his private company. But without voting rights, his influence was limited. A similar situation existed for the Canadians at Bell Canada, who were nevertheless developing Datapac on this technical basis.
The turning point came with the unexpected rallying of the British Post Office to French positions. Halvor Bothner, the Norwegian rapporteur, then abandoned his initial position. He who had coined the term “datagram” ultimately sided with virtual circuits. This about-face sealed the fate of X.25, adopted in March 1976 and then solemnly confirmed in the fall.
Ironically, this French victory immediately benefited the international community. Spain and the Netherlands built their national networks on X.25. Bell Canada integrated it into Datapac, thus validating European technical choices. IBM, ever pragmatic, adapted its equipment to this standard as early as 1975.
In France, X.25 found its apotheosis with Transpac. This national network would support Minitel traffic for more than three decades, from 1980 to 2012. A remarkable performance for a technology that some had already deemed outdated in the 1990s. Banks, in particular, remained loyal to it: its inherent reliability and security corresponded perfectly to their strict requirements.
The emergence of the Internet could have sounded the death knell for X.25. TCP/IP, a direct heir to Pouzin’s datagrams, gradually established itself as the de facto standard. But X.25 persisted in its specialized niches. Costa Rica was still using it in 1999, France until 2012. This longevity contrasts with the resounding failure of OSI, that pharaonic ISO project that claimed to standardize all computer communications.
X.25 perfectly illustrates the caprices of technical innovation. A standard can be born from a political compromise, flourish in unexpected uses, and survive far beyond its initial predictions. It also testifies to the ability of French engineers to carry weight in international technical debates, when technical quality meets diplomatic skill.
This story above all reveals the complexity of technological ecosystems. Contrary to popular belief, the “best” technical solution does not always prevail. X.25 and TCP/IP coexisted for decades, each meeting specific needs. This peaceful coexistence contrasts with the standards wars that regularly shake the computer world.