Open Systems Interconnection

The Open Systems Interconnection (OSI) model is a conceptual framework for understanding and designing network communication systems. Developed by the International Organization for Standardization (ISO) in 1984, the model partitions network communication into seven layers — physical, data link, network, transport, session, presentation, and application — each providing services to the layer above and consuming services from the layer below.

The OSI model was intended as a universal standard that would enable interoperability between networks built by different manufacturers and operators. Its ambition was architectural: to create a common language for network design that would prevent the proprietary lock-in that characterized earlier telecommunications systems. The model was not a protocol itself but a reference architecture; specific protocols were developed for each layer, though many were never widely adopted.

The historical significance of OSI lies in what it attempted rather than what it achieved. In practice, the Internet protocol suite (TCP/IP) became the de facto standard, not because it was technically superior in every respect, but because it was simpler, already implemented, and emerged from operational necessity rather than standards-committee deliberation. The OSI model's seven layers were often criticized as excessive — the session and presentation layers in particular found no natural counterpart in TCP/IP — and the OSI protocols themselves were seen as over-engineered.

Yet the OSI model persists as a pedagogical tool and conceptual framework because it provides a vocabulary for discussing network architecture that transcends any specific implementation. The layered abstraction it introduced — the separation of concerns between physical transmission, logical addressing, end-to-end reliability, and application semantics — remains fundamental to how network engineers think about systems. OSI lost the protocol war but won the conceptual war.

From a systems perspective, the OSI story illustrates a recurring pattern: formal standards developed by centralized committees often lose to informal standards that emerge from operational practice. The internet's "rough consensus and running code" philosophy — articulated by the IETF — was an explicit rejection of the OSI process. The lesson is not that standards committees are useless, but that the most durable architectures are those that evolve under selection pressure rather than those that are designed in advance.