What Are Networking Layers?

What a Network Is

A computer network is two or more devices that can share information with each other. Your phone and your wireless router form a network. So do a thousand servers in a data center. So does the internet, which is simply an enormous collection of smaller networks that have agreed to pass information along for one another.

The word "share" is doing a lot of work in that sentence. When you send a photo to a friend, nothing physically travels from your phone to theirs. Your phone turns the photo into a very long string of ones and zeros, sends those ones and zeros out as electrical pulses, flashes of light, or radio waves, and a device at the other end rebuilds the photo from them. Everything in this book is about how that trip is organized.

Why Devices Need Rules

Your laptop was built by one company. The wireless router in your home was built by another. The web server holding the page you are reading was built by a third, runs different software, and may sit on another continent.

None of these machines were designed together. They cooperate because they all follow the same published rules about how to format information, how to address it, and what to do when something goes wrong. A rule set like that is called a protocol. Protocols are the reason a fifteen-year-old printer still works with a brand-new phone.

What a Layer Is

Getting information from one device to another involves a lot of separate jobs. Something has to turn data into signals. Something has to get those signals to the right device in the room. Something has to find a path across the world. Something has to hand the data to the right program once it arrives.

A layer is one of those jobs. Each layer is responsible for a single part of the delivery, and it trusts the layers below it to handle the rest. The layer that finds a path across the world does not care whether the signals travel on copper, glass, or radio. The layer that makes the signals does not care whether you are sending email or watching a film.

This is the whole idea. Each layer does one job and hands its work to the next.

Why Splitting the Work Helps

Separating the jobs pays off in four practical ways.

You can learn one piece at a time. Nobody understands all of networking at once. Layers give you seven smaller subjects instead of one impossible one.

You can change one piece without breaking the rest. Wi-Fi replaced a great deal of cabling without anyone rewriting email. The lower layer changed; the upper layers never noticed.

Different makers can build different pieces. A cable manufacturer, a switch maker, and a browser developer can each work to their own layer's rules and still end up with parts that work together.

You can find faults faster. When something breaks, you can ask which job failed. Is the cable dead, or is the address wrong, or is the program not running? Each question belongs to a different layer.

Why Seven Layers

In 1984 the International Organization for Standardization published a reference model that divided network communication into seven layers. It is called the OSI model, short for Open Systems Interconnection. From the bottom up, the layers are Physical, Data Link, Network, Transport, Session, Presentation, and Application.

    Layer 7   Application     What programs ask for
    Layer 6   Presentation    How data is formatted
    Layer 5   Session         Managing the conversation
    Layer 4   Transport       Which program, how carefully
    Layer 3   Network         Which network, which device
    Layer 2   Data Link       Delivery on the local network
    Layer 1   Physical        Signals on cable, glass, or air

Seven is not a magic number. It was a committee's judgment about where the natural boundaries between jobs fall. The internet itself is actually built on a different and simpler model, described in the standards as four layers, which combines the top three OSI layers into one.

So why learn seven? Because the seven-layer vocabulary is what the industry uses. Engineers say "that's a Layer 2 problem" or "we need a Layer 7 firewall" and expect to be understood. The model is a shared language more than a blueprint.

The Most Important Warning in This Book

The seven layers are a model, not seven objects.

If you opened your laptop you would not find seven layers stacked inside it. No component is labeled "Layer 5." No cable carries a sticker saying "Layer 1." Real software often blurs the boundaries, and some protocols sit awkwardly across two layers at once.

The model is a way of thinking, and it earns its place because it makes a complicated process describable. Hold it firmly enough to use it and loosely enough that you are not surprised when reality is untidy.

Remember This

The layers are seven separate jobs in one delivery, described as a model so that people can learn, build, and repair networks one piece at a time.