The OSI model: seven layers of communication

Seven layers, different responsibilities

OSI is a reference model, not an exact implementation of the internet stack. Its lower layers explain transmission and transport; the upper layers describe sessions, representation and applications. Real stacks do not always draw the upper boundaries as neatly as a teaching diagram.

• 7 Application: network functions used by applications, such as HTTP, SMTP and FTP; data.
• 6 Presentation: data representation, formatting and encryption concepts, illustrated by JPEG, ASCII and TLS; data.
• 5 Session: coordination of communication sessions between hosts; data.
• 4 Transport: end-to-end communication, using TCP segments or UDP datagrams.
• 3 Network: logical addressing and routing, including IP and ICMP; packets.
• 2 Data Link: local frames, MAC addressing and media access, including Ethernet switching; frames.
• 1 Physical: signals, media and binary transmission through cables, hubs or radio; bits.

A shared language narrows the problem

Saying that Layer 1 is up but Layer 3 is missing narrows diagnosis more than 'the network is broken'. A device may work across several layers: a firewall can inspect network, transport and application information. A multilayer switch can route as well as switch Ethernet frames.

The model helps separate physical signalling, local delivery, IP routing and end-to-end transport from the behaviour of the application itself. A problem at one layer can produce symptoms higher up without making every layer faulty.

Encapsulation links the layers

During sending, each participating protocol adds control information. Application data becomes a segment or datagram, then an IP packet, an Ethernet frame and finally signals. Conceptually this is data with a TCP header, the resulting segment with an IP header, and the packet with an Ethernet header.

The receiver removes the corresponding information in reverse order. This explains where MTU, fragmentation, ports and checksums belong. The TCP/IP model groups several OSI layers differently and often describes the implemented internet architecture more directly; the models serve complementary teaching and diagnostic purposes.

Work bottom-up or top-down, but consistently

For a completely failed connection, start with power, link, error counters, VLAN, address, route, transport and application. For a clear application error, working downward may be faster. Gather observations for each layer instead of changing unrelated settings.

A successful ping demonstrates only parts of Layers 1–3 and ICMP handling. It does not prove an open TCP port, successful TLS session or correct application. State explicitly what each test does and does not establish.