COMP30023 · Computer Systems
Network Protocols and the OSI Model
Week 6 opens the networking half: why protocols are layered, the seven-layer OSI reference model against the Internet's layers, encapsulation as headers are added down the stack, and connection-oriented versus connectionless service. Listing the OSI layers with their data units, distinguishing a service from a protocol, and reasoning about which layers a change or a cut link affects are common exam questions (this half is examined in the final exam, not the MST).
What this chapter covers
- 01Why layer: the Internet is an aggregation of many networks; modularity manages complexity
- 02Service vs protocol: a service is the interface a layer offers upward; a protocol is the peer-to-peer rules at one layer
- 03The seven OSI layers top-to-bottom and their data units (Application, Presentation, Session, Transport/Segment, Network/Packet, Data link/Frame, Physical/Bit)
- 04The TCP/IP model: Application (subsumes OSI 5-7), Transport, Internet (= Network), Link (= Data link + Physical)
- 05Encapsulation/decapsulation: each layer prepends its header (message → segment → packet → frame → bits)
- 06Connection-oriented (TCP, like a phone call) vs connectionless (UDP, like the postal service) service models
- 07The IP 'narrow waist' (hourglass): many apps and links, one network protocol (IP over everything)
- 08Point-to-point (adjacent nodes) vs end-to-end (the two hosts); routers implement only layers 1-3
Which OSI layers a cut cable affects
- +1Physical layer: definitely affected — with the medium severed no signal (bits/symbols) can cross that hop at all.
- +1Data-link layer: definitely affected — it cannot frame or transfer data over a dead physical link on that hop, since it relies on the physical layer beneath it.
- +1Network layer: definitely affected — the topology has changed, so the routing/forwarding tables must be recomputed to route traffic around the break; existing paths through that link fail.
- +1Transport layer: may be affected — if packets are rerouted or lost, a connection-oriented transport (TCP) will see reordering, timeouts and retransmissions while it recovers, whereas a connectionless flow (UDP) or a clean reroute might show no transport-visible effect. Layers above transport are not directly affected by a single link.
Key terms
- Service vs protocol
- A service is the set of primitives (the interface/API) a layer offers to the layer above it. A protocol is the set of rules governing the format and meaning of packets exchanged between peer entities at the same layer. Services define what; protocols define how.
- OSI reference model
- A seven-layer model (top to bottom): Application, Presentation, Session, Transport (Segment), Network (Packet), Data link (Frame), Physical (Bit). It is an idealised reference for design and diagnosis; routers implement only the bottom three layers.
- TCP/IP model
- The Internet's four-layer model: Application (subsuming OSI's Session and Presentation), Transport, Internet (= OSI Network), and Link (= OSI Data link + Physical). It reflects what actually runs on the Internet.
- Encapsulation
- As data descends the stack, each layer prepends its own header (the link layer may add a trailer): application message → transport segment → network packet/datagram → link frame → physical bits. The receiver reverses this (decapsulation), stripping headers on the way up.
- Connection-oriented vs connectionless
- Connection-oriented service (TCP, MPLS) sets up, uses and tears down a connection with negotiation, like a phone call. Connectionless service (UDP, IP) treats each message as self-contained, like the postal service — no setup, no per-connection state.
- IP narrow waist
- The hourglass shape of the Internet stack: many application protocols on top and many link technologies below, but a single network protocol (IP) in the middle — 'IP over everything, and everything over IP' — which is what makes the Internet interoperable.
Network Protocols and the OSI Model FAQ
What is the difference between a service and a protocol?
A service is the interface a layer provides to the layer above — the set of operations (primitives) that layer can request, defining what the layer does. A protocol is the agreement between peer entities at the same layer on both sides of the connection about the format and meaning of the messages they exchange, defining how it is done. Layering isolates the two: you can change a layer's protocol without changing the service it offers, and the layer above is unaffected.
What are the OSI layers in order, and their data units?
Top to bottom: Application, Presentation, Session, Transport, Network, Data link, Physical. The examinable data-unit names are Segment at the Transport layer, Packet at the Network layer, Frame at the Data-link layer and Bit (really a symbol) at the Physical layer. The Internet/TCP-IP stack collapses this to Application (covering OSI 5-7), Transport, Internet and Link.
If a layer's service changes, what happens to the layers above and below?
The layer below is unaffected, because it does not depend on the layer above it. The layer above may need to be reimplemented, because it consumes the changed layer's service — if the new service still provides everything the upper layer needed, it keeps working; if not, it breaks. Layering isolates changes downward and exposes them upward. This is the reasoning behind moving HTTP from TCP to QUIC affecting only transport and application.
Why is IP called the narrow waist of the Internet?
Because the protocol stack is hourglass-shaped: many application protocols (HTTP, SMTP, DNS) sit on top and many link/physical technologies (Ethernet, WiFi, DSL) sit below, but they all meet at a single network-layer protocol — IP — in the middle. 'IP over everything, and everything over IP' is what lets any application run over any physical medium, which is a big part of why the Internet interoperates so widely.
Can AI help me with the OSI model and layering in COMP30023?
Yes. Sia can drill you on the OSI layers and their data units, explain service versus protocol, and reason through which layers a change or a fault affects, checking your answers against the way the subject phrases them. It is a study aid for the networking half; it does not complete your graded exam, quizzes or projects, and University of Melbourne academic-integrity rules apply.
Exam move
The networking half is assessed in the final exam (not the mid-semester test), so budget revision accordingly and start the layering vocabulary early because everything downstream — sockets, TCP, routing — is described in it. Memorise the seven OSI layers in order with their data-unit names (Segment/Packet/Frame/Bit) and the TCP/IP mapping, and be able to state the service-vs-protocol distinction in one sentence. Practise the 'which layers are affected' reasoning for both a service change and a cut link, using the definite-vs-may split. Know the encapsulation sequence (message → segment → packet → frame → bits) and the connection-oriented vs connectionless contrast with their everyday analogies. These are quick, high-yield boxed answers; rehearse them under time pressure, confirm the exam date on Canvas, and remember that this foundation compounds toward your WAM across the whole networking half.
Working through Network Protocols and the OSI Model in COMP30023? Sia is AskSia’s AI Computer Science tutor — ask any COMP30023 Network Protocols and the OSI Model question and get a clear, step-by-step explanation grounded in how COMP30023 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
