Protocol layering is the architectural idea of building a communication system as a stack of protocols, where each layer provides a service to the layer above it and relies on the service of the layer below. Rather than solving the entire problem of getting data from one application to another in a single monolithic design, layering breaks it into manageable, independent pieces: one layer worries about pushing bits down a wire, another about routing across networks, another about reliable end-to-end delivery, and so on.
The principle was set out rigorously by Hubert Zimmermann in his 1980 IEEE Transactions on Communications paper on the OSI Reference Model. He describes the core rules of decomposition: a layer should be created where a different level of abstraction is needed, each layer should perform a well-defined function, the boundaries between layers should be chosen to minimize the flow of information across interfaces, and the number of layers should be large enough that distinct functions are not forced together yet small enough that the architecture stays manageable. A key benefit is that any layer can be changed internally without disturbing its neighbors, as long as the service it offers across the interface stays the same.
The Internet community arrived at layering independently and pragmatically. RFC 871, M. A. Padlipsky’s 1982 “A Perspective on the ARPANET Reference Model,” frames layering as a fundamental architectural axiom while criticizing the OSI approach as overly rigid. The ARPANET model used broad functional groupings — roughly a network interface layer, a host-to-host layer, and a process or applications layer — rather than seven prescribed levels. Padlipsky insists that “a given protocol’s control information should be treated strictly as data by a protocol below it,” the encapsulation rule that lets each layer wrap and unwrap the data of its neighbor without interpreting it.
The two great instantiations of the idea are the seven-layer OSI model and the four-layer TCP/IP model. OSI is the more formal and prescriptive; TCP/IP is leaner, collapsing several OSI layers and famously leaving the session and presentation concerns to applications. The contrast between them, and the political and technical fight over which would prevail, became the protocol wars of the 1980s and early 1990s.
Layering’s payoff is modularity at internet scale. Because the network layer (IP) presents the same simple service to everything above it, transport protocols like TCP and UDP, and the thousands of application protocols above them, can evolve independently of the underlying physical media — Ethernet, fiber, or wireless. This separation of concerns is one of the central reasons the Internet could grow and absorb new technologies for decades without being redesigned.