AppleTalk

In the early 1980s, Apple Computer embarked on an ambitious challenge: creating a network protocol in parallel with the development of the Macintosh. The idea seemed bold, but it addressed a concrete need. Users wanted to share their files and printers without wrestling with complex technical configurations. AppleTalk was born from this desire to simplify network computing.

The protocol concealed its sophistication behind a remarkably transparent interface. Computers communicated with each other without users needing to understand the underlying mechanisms. This philosophy stood in stark contrast to the systems of the era, often intimidating and reserved for experts. Apple bet on the invisibility of technical operations: only the result mattered.

Two main versions emerged. Phase 1 targeted small workgroups but suffered from constraining limitations. It was impossible to exceed 135 machines on a segment, and wide area networks remained out of reach. These restrictions hindered AppleTalk's expansion in enterprises. Phase 2 corrected these flaws by allowing up to 253 machines per segment and managing wide area networks. This evolution paved the way for more ambitious deployments.

AppleTalk's flexibility was expressed through its physical implementations. LocalTalk exploited Apple's proprietary twisted pair cabling, while TokenTalk relied on Token Ring networks. EtherTalk leveraged Ethernet, and FDDITalk exploited FDDI optical fibers. This modularity enabled technological transitions without a complete system overhaul.

The protocol architecture was methodically organized. The DDP (Datagram Delivery Protocol) transported packets from one point to another. The AARP (AppleTalk Address Resolution Protocol) established the correspondence between logical and physical addresses. The RTMP (Routing Table Maintenance Protocol) kept routing information up to date. Each protocol fulfilled its function without encroaching on the others.

Name management relied on ingenious mechanisms. The NBP (Name Binding Protocol) associated understandable names with technical addresses, while the ZIP (Zone Information Protocol) organized networks into logical zones. The AEP (AppleTalk Echo Protocol) verified that machines remained accessible. The ATP (AppleTalk Transaction Protocol) guaranteed exchange reliability for critical applications such as file sharing or printing.

Dynamic addressing constituted one of AppleTalk's innovations. An identifier was automatically assigned to each machine upon connection. This approach prevented address conflicts while simplifying administration. The address combined three elements: a 16-bit network number, an 8-bit node identifier, and an 8-bit socket number to designate the relevant service.

The zone concept revolutionized network organization. Machines could be grouped according to functional rather than geographical criteria. The accounting department could thus gather its resources in a single zone, even if the computers were scattered across different buildings. This flexibility would appeal to many network administrators.

Transmission occurred without prior connection establishment. Packets traveled independently toward their destination. Higher-level protocols then added the necessary reliability mechanisms according to needs. This modular architecture facilitated system evolution and maintenance.

Cisco progressively enriched its AppleTalk integration. It added support for different EtherTalk versions, compatibility with VLANs, integration with WAN protocols like Frame Relay. These extensions pushed the protocol's limits far beyond Apple's initial intentions. The encapsulation of RTMP packets over IP also enabled AppleTalk traffic over the Internet.

Security remained AppleTalk's poor relation, with the protocol delegating it to applications—a questionable choice by current standards but consistent with the philosophy of the 1980s. Cisco attempted to fill this gap with its distribution lists, a rudimentary but useful mechanism for controlling the propagation of routing information.

Cisco's implementation presented a surprising peculiarity: it refused to transmit certain packets with identical local addresses. This restriction, contrary to Apple's specifications, aimed to preserve the integrity of address tables. The manufacturer prioritized network stability over strict standards compliance.

AppleTalk's decline began in the 1990s. TCP/IP progressively established itself as the universal standard for network communications. Its open nature and adoption by the Internet sealed the fate of proprietary protocols. In 2009, Mac OS X v10.6 Snow Leopard definitively abandoned AppleTalk. Apple thus came full circle by turning toward the open standards it had initially shunned.

With the AppleTalk protocol, a sophisticated network remained simple to use. Auto-configuration and automatic service discovery, central concepts of AppleTalk, still inspire current developments. Bonjour, AppleTalk's spiritual successor at Apple, perpetuates this philosophy of simplicity in a TCP/IP world.