X.25

X.25
Name	X.25
Caption	Packet-switched network standard
Developer	CCITT
Introduced	1976
Influenced	SNA (computer architecture), OSI model, Frame Relay
Superseded by	Frame Relay, X.75, Integrated Services Digital Network

X.25 is a suite of standards for packet-switched data communication originally developed by CCITT and adopted in the 1970s. It defined layered protocols and network interfaces that enabled interconnection among telecommunication providers such as British Telecom, AT&T, PTT (France), and corporate networks like IBM installations. Widely deployed for applications including telex gateways, bank card transactions, and early ARPANET interworking, it influenced later protocols in the OSI model and commercial services such as Frame Relay and ISDN.

History

The development emerged from collaboration among CCITT, national administrations such as British Post Office, and equipment makers including General Electric, Siemens, Northern Telecom, and Bell Labs. Early milestones included experimental packet-switching work at RAND Corporation, theoretical foundations by Paul Baran and Donald Davies, and the ARPANET project sponsored by DARPA, which popularized packet concepts. Formalization into specifications occurred through CCITT Study Groups and sets of Recommendations in the 1970s, culminating in versions widely used by public data networks run by Telefónica, Deutsche Bundespost, Nippon Telegraph and Telephone, and Western Union. The standard was harmonized with related efforts like ITU-T work and influenced national standards bodies such as ANSI and ETSI.

Architecture and Protocols

The design followed layered principles akin to the OSI model, specifying a physical layer interfacing to circuits like X.21 and RS-232, a data link layer implementing LAPB (a variant of HDLC), and a network layer offering virtual circuits and packet delivery. Protocol primitives supported switched virtual circuits (SVCs) and permanent virtual circuits (PVCs), flow control, and error recovery across hops operated by carriers such as BT and MCI. Important protocol elements were call setup/clearing, packet sequencing, windowing, and retransmission, interoperating with systems from DEC, Hewlett-Packard, Fujitsu, and Motorola. Extensions and related Recommendations permitted interworking via gateways with systems like X.75 for inter-provider links and provided addressing compatible with TALI and other numbering plans.

Addressing and Routing

Addressing used DTE and DCE concepts where customer premises equipment from vendors such as Siemens and NCR Corporation connected to public data networks operated by carriers such as BT and British Telecom International. Addresses were numeric, hierarchical, and sometimes mirrored national numbering schemes used by administrations like France Télécom and Deutsche Telekom. Routing in packet switches—implemented in equipment from GTE, Alcatel-Lucent, and Cable & Wireless—relied on virtual circuit tables, call control signaling, and administrative routing policies similar in spirit to routing registries and hop-by-hop control used later by Internet backbones like Sprint and UUNET. Inter-network exchange used gateway agreements comparable to peering among modern carriers such as Verizon and Comcast.

Implementations and Equipment

Commercial deployments used routers and packet switches from manufacturers including Xerox, IBM, Fujitsu, Nokia, and Northern Telecom. Customer premise equipment ranged from terminal adapters sold by AT&T and Bell System companies to mainframe interfaces for IBM System/370, DEC PDP-11, and Honeywell systems. Network-facing switches—branded as PADs and PSUs—were provided by CISCO Systems early entrants as well as legacy suppliers like Tandem Computers and Unisys. Vendors offered management systems integrating with operations centers run by national carriers such as Telstra, CPR and multinational operators like British Airways for reservation systems and Visa for transaction processing.

Performance, Reliability, and Security

Designed for reliable long-distance links, the protocol emphasized error correction, sequencing, and retransmission suited to analog trunks operated by entities like ITT and GTE. Throughput and latency characteristics depended on link speeds (e.g., 1200 bit/s, 2400 bit/s, 64 kbit/s) available from providers such as BT and NTT; as circuit speeds rose, designs from Cisco and Juniper Networks offered more efficient packet handling. Reliability was high for financial and telemetry applications used by institutions like SWIFT and Bloomberg Terminal services. Security relied on physical isolation, carrier controls, and call authentication; later concerns prompted gateways and overlays integrating cryptographic services influenced by standards from NIST and work by RSA Laboratories and GCHQ.

Decline and Legacy

Use declined as protocol stacks based on TCP/IP grew in academic and commercial adoption via ARPANET, NSFNET, and later commercial Internet service providers like AOL and EarthLink. Economic and technical pressures favored lower-overhead services such as Frame Relay and then MPLS; vendors including Cisco Systems and Alcatel shifted product lines. Nevertheless, the architecture influenced OSI networking pedagogy, service models used by SWIFT and airline reservation systems like Sabre, and protocol engineering practices adopted by researchers at University College London and Stanford University. Remnants persisted in niche banking, legacy telemetry, and inter-carrier signaling where vendors such as Siemens and Fujitsu maintained support.

Category:Telecommunications standards