Theory
Every layer has its own protocols
Now that you know the seven OSI layers, here is the next piece: each layer has its own protocols, the agreed rules for doing that layer's job, and even its own name for a chunk of data. A message is not the same 'thing' at every layer; it is wrapped and renamed as it moves.
This lesson looks at the important protocols around the network layer, the idea of packets and datagrams, and how encryption (SSL) and the familiar application protocols (HTTP, FTP, Telnet) sit in the upper layers. Getting protocols matched to their correct layer is the key skill here.
Theory
The network layer: IP, packets, and datagrams
The star protocol of the network layer (3) is IP (Internet Protocol). IP provides logical addressing (IP addresses) and handles routing, getting data from one network to another. (ICMP, used for error and status messages like ping, also lives here.)
At this layer, a chunk of data is called a packet, and often a datagram. The words overlap: 'packet' is the general term for the network-layer unit, while datagram emphasises that the unit is self-contained and connectionless, each one is routed independently, carrying its own address, with no pre-established connection. IP datagrams are routed hop by hop, each finding its own way.
At a glance
| Protocol | Job | OSI layer |
|---|---|---|
| IP | Logical addressing and routing between networks | Network (3) |
| TCP / UDP | End-to-end delivery; reliable (TCP) or fast/connectionless (UDP) | Transport (4) |
| SSL / TLS | Encryption and secure formatting of data | Presentation role (6) |
| HTTP | Transfer web pages | Application (7) |
| FTP | Transfer files | Application (7) |
| Telnet | Remote text login to another machine | Application (7) |
Formula
SSL secures; HTTP, FTP, Telnet carry
Be precise about these upper-layer protocols. SSL/TLS provides encryption, converting data into a secure form, which is the job of the presentation layer (translation and encryption). HTTP, FTP, and Telnet are application-layer protocols that carry the actual user work: web pages, file transfers, remote logins.
They combine: when HTTP runs secured over SSL/TLS, you get HTTPS. So think of SSL/TLS as the security wrapper (presentation-layer role) and HTTP/FTP/Telnet as the application-layer protocols doing the visible work. Matching each protocol to its true layer is exactly what exam questions test.
Quiz
At which OSI layer does the IP protocol operate, and what is its data unit called?
- The Application layer; the unit is a web page
- The Network layer (3); the unit is a packet, also called a datagram
- The Physical layer; the unit is a bit
- The Transport layer; the unit is a frame
Show the answer
The Network layer (3); the unit is a packet, also called a datagram
IP (Internet Protocol) operates at the Network layer (layer 3), providing logical addressing and routing, and its data unit is a packet, also called a datagram (a self-contained, connectionless unit). Option A is wrong: the Application layer hosts protocols like HTTP, not IP; and a 'web page' is not IP's data unit. Option C is wrong: the Physical layer deals in raw bits, but IP is not a physical-layer protocol. Option D makes two errors: IP is not a Transport-layer protocol (that is TCP/UDP), and a 'frame' is the Data Link layer's unit, not the Network layer's. Anchor the units to layers: bits (Physical), frames (Data Link), packets/datagrams (Network, IP), segments (Transport).
Think first
What exactly is the difference between a packet and a datagram?
The words packet and datagram are often used together for network-layer data. Is there a real distinction? Then tap.
Show the answer
They largely refer to the SAME thing, the network-layer unit of data, but 'datagram' carries an extra emphasis: that the unit is SELF-CONTAINED and CONNECTIONLESS. 'Packet' is the general, everyday word for a formatted chunk of data at the network layer. 'Datagram' stresses a particular style of delivery: each datagram travels INDEPENDENTLY, carrying everything it needs (like its full destination address) to be routed on its own, with NO pre-arranged connection between sender and receiver and no guarantee about order or arrival. This is exactly how IP works, IP datagrams are launched into the network and each one may take its own path, arriving possibly out of order or not at all, which is why IP is called a connectionless, best-effort service. (UDP at the transport layer is likewise called a datagram protocol for the same reason.) So when someone says 'IP packet' or 'IP datagram', they usually mean the same object; 'datagram' just highlights the independent, connectionless nature of its journey. Contrast this with a connection-oriented approach like TCP, which first establishes a connection and then delivers an ordered, reliable stream, a different philosophy layered on top. The takeaway: packet is the general term, datagram emphasises 'independent and connectionless', and IP's units are both.
Summary
Key takeaways
- Each OSI layer has its own protocols and its own name for a unit of data.
- The network layer's main protocol is IP, which does logical addressing (IP addresses) and routing; ICMP also lives here.
- The network-layer data unit is a packet, also called a datagram: self-contained and connectionless, routed independently.
- 'Packet' is the general term; 'datagram' emphasises independent, connectionless delivery (as in IP and UDP datagrams).
- SSL/TLS provides encryption, the presentation layer's role (6); it secures data rather than carrying user work.
- HTTP, FTP, and Telnet are application-layer protocols (7) carrying web pages, files, and remote logins; HTTP over SSL/TLS is HTTPS.
- Memory hook: IP and packets/datagrams at layer 3; SSL secures (presentation), HTTP/FTP/Telnet carry (application).