Computer Networks

Chapter 01
(version April 12, 2007)

Maarten van Steen

Vrije Universiteit Amsterdam, Faculty of Sciences
Dept. Computer Science
Room R4.20. Tel: (020) 598 7784
E-mail: [email protected], URL: www.cs.vu.nl/∼steen/

01 Introduction
02 Physical Layer
03 Data Link Layer
04 MAC Sublayer
05 Network Layer
06 Transport Layer
07 Application Layer
08 Network Security

00 – 1 /

Overview
Hardware: Talk just a bit about how you can configure
a bunch of computers into a network:

• Local Area Networks (LAN)

• Metropolitan Area Networks (MAN)
• Wide Area Networks (WAN)
• Internetworks

Software: This is what actually makes computer net-

works – not the hardware!

• Protocols: describe how two communicating par-

ties exchange information.
• Services: describe what a network offers to par-
ties that want to communicate.
• Interfaces: describe how a client can make use
of network services, i.e. how the services can be
accessed.

Reference models: Describe how the OSI and Inter-

net networks are organized.
01 – 1 Introduction/
 Computer Networks
Hardware

Broadcast network: a single communication chan-

nel is shared by all computers ⇒ sending a packet
implies that all others receive it.

Point-to-point network: Computers are connected in

pairs ⇒ sending a packet goes strictly from the
sender to the receiver, possibly having to visit in-
termediate machines (routing).
Interprocessor Processors Example
distance located in same

1m Square meter Personal area network

10 m Room

100 m Building Local area network

1 km Campus

10 km City Metropolitan area network

100 km Country
Wide area network
1000 km Continent

10,000 km Planet The Internet

01 – 2 Introduction/1.2 Hardware

Local Area Networks (LAN) (1/2)

Apart from scale, LANs distinguish themselves from

other networks by (generally) using broadcast tech-
nology, and having simple topologies:

Computer

Cable Computer

(a) (b)

Type (a) (Bus-based): All computers are connected

to the same wire. When one of them starts sending,
the signal is propagated to all others. If two of them
start sending at the same time, packets collide and
rubbish is the result.

01 – 3 Introduction/1.2 Hardware
 Local Area Networks (LAN) (2/2)

Computer

Cable Computer

(a) (b)

Type (b) (Token-based): a token (which is just a small

packet) continuously circulates along the ring. A send-
ing computer

(1) waits until the token passes and removes it

(2) sends its packet along the ring,
(3) waits until the packet returns
(4) reinserts the token.

01 – 4 Introduction/1.2 Hardware

Metropolitan Area Networks

(MAN)
A MAN is intended to cover an entire city. A well-
known example of a MAN is the cable television net-
work:

Junction
box

Antenna

Head end

Internet

In essence, the original network was used only for

broadcasting radio and TV, but it soon became clear
that the infrastructure could be used for two-way data
communication as well.
01 – 5 Introduction/1.2 Hardware
 Wide Area Networks (WAN)
Note: LANs and MANs (traditionally) didn’t have any
switching elements: the wire did all the work. This
makes them extremely efficient, although harder to
scale. Here’s where WANs come in.
Subnet Router

Host

LAN

In a WAN, hosts are connected to a subnet, which

in turn consists of routers (switching elements) and
transmission lines.

Routers generally adhere to a store-and-forward prin-

ciple: incoming packets are first buffered (stored), the
router takes a decision on where the packet has to
go, and forwards the packet across the selected out-
put line.
01 – 6 Introduction/1.2 Hardware

Wireless Networks (1/2)

In wireless networks, the transmission occurs through
unguided media. Distinguish four different categories:

System interconnection: Basically for replacing the

traditional cables that connect local devices to each
other (monitor–keyboard–mouse–..., cordless tele-
phone, stereo components).

Wireless LANs: Computers communicate through a

(wired) base station that is placed at the ceiling,
or directly in a peer-to-peer fashion (e.g., home
networks).

Wireless MANs: Often in the form of access net-

works: parts of a city offer a wireless mesh through
which routing to a Internet access points take place.

Wireless WANs: The digital cellular phone networks

fall into this category. New technology is now
pushing bandwidth to 50 Mbps over several kilo-
meters.

01 – 7 Introduction/1.2 Hardware
 Wireless Networks (2/2)

Important: Make distinction between wireless and

mobile:

Application W M
Office workstations N N
Notebooks N Y
LAN in the jungle Y N
LAN on a ship N Y/N
PDA Y Y

Note: Distinction is sometimes hard to make, espe-

cially when wireless and wired go together:

Flying router

Portable Wired
computer LAN
One telephone
call per computer
(a) (b)

01 – 8 Introduction/1.2 Hardware

Home Networks
Essence: Many devices in the same home will be
connected to a single network and communicate with
each other:
• Computers
• Entertainment (audio equipment, game centers)
• Telecommunications (mobile phones, fax devices,
intercom)
• Appliances (refrigerator, microwave, central heat-
ing, lights)
• Telemetry (alarms, cameras, thermostat)

Different models for home networking exist (completely

decentralized versus centralized). No single one can
be pointed to as the winner, but we’re heading to-
wards centralized solutions (MS media center). Note
the specific requirements:
• 100% robust
• very easy to use
• self-managing
• high bandwidth

01 – 9 Introduction/1.2 Hardware
 Internetworks

The assumption so far is that a network is homoge-

neous: there is hardly any variation in hardware and
software. In practice, large networks can only be con-
structed by interconnecting different kinds of networks
⇒ internet(work).

Examples:

• Connecting a collection of different kinds of LANs

within a department (combine wired/wireless).

• Connecting LANs to each other through a WAN

(think of enterprise networks for multinationals).
The WAN acts as a subnet.

• Connecting WANs to each other (the Internet).

01 – 10 Introduction/1.2 Hardware

Protocol Hierarchy
Fundamental to all software that makes a computer
network run, is the notion of protocol hierarchies:
structuring the services that a network must offer in
terms of layers.

Location A Location B

I like J'aime
Message Philosopher
rabbits bien les
lapins
3 3

Information
L: Dutch for the remote Translator L: Dutch
Ik vind translator Ik vind
konijnen konijnen
2 2
leuk leuk

Information
Fax #--- for the remote Fax #---
L: Dutch secretary Secretary L: Dutch
Ik vind Ik vind
1 1
konijnen konijnen
leuk leuk

01 – 11 Introduction/1.3 Software
 Layering: The Concepts

• Two parties at different sites, but at the same level,

always agree on how they will exchange informa-
tion ⇒ specified in a protocol. Example: we
all agree to speak Dutch (but use English on the
sheets).

• In order for one party to send and receive infor-

mation, it can only make use of the communi-
cation services offered by the layer directly un-
derneath it. Example: The use of interpreters in
negotiations between countries.

• Services offered by a layer are always fully spec-

ified in terms of an interface that makes those
services accessible. Example: phones have but-
tons that allow you to “dial” a number.

01 – 12 Introduction/1.3 Software

Layering: An Example

Layer
Layer 5 protocol
5 M M

Layer 4 protocol
4 H4 M H4 M

Layer 3
protocol
3 H3 H4 M1 H3 M2 H3 H4 M1 H3 M2

Layer 2
protocol
2 H2 H3 H4 M1 T2 H2 H3 M2 T2 H2 H3 H4 M1 T2 H2 H3 M2 T2

Source machine Destination machine

Observation: In a protocol stack, Layer k puts its en-

tire packet as data into a Layer k − 1 packet; the latter
may add a header and/or a trailer.

Note: It may occur that Layer k data has to be split

across several Layer k − 1 packets ⇒ fragmentation
01 – 13 Introduction/1.3 Software
Services: Connections or Not (1/2)

(Most) Network layers offer one or both of the follow-

ing types of services:

Connection-oriented: This is the telephone model:

you first establish a connection, then do a lot
communication, and finally release the connec-
tion.

Connectionless: The postal model: your data is put

into some kind of envelope on which the desti-
nation address has been written. The envelope +
contents is sent to the destination, and that’s it.

01 – 14 Introduction/1.3 Software

Services: Connections or Not (2/2)

Service Example

Reliable message stream Sequence of pages

Connection-
oriented Reliable byte stream Remote login

Unreliable connection Digitized voice

Unreliable datagram Electronic junk mail

Connection-
Acknowledged datagram Registered mail
less
Request-reply Database query

Each service can provide some quality:

• Is data delivered in the order it was sent? With

connections, this is generally the case.

• Is data transmission reliable? Generally offered

with connections, but not always with connection-
less services. Reliability requires sending acknowl-
edgements ⇒ performance may degrade.

01 – 15 Introduction/1.3 Software
 Service Primitives (1/2)

A service is specified by means of a set of primitives,

also called operations, available to clients. Example
of primitives for a simple connection-oriented service:

01 – 16 Introduction/1.3 Software

Service Primitives (2/2)

Server Client
LISTEN
CONNECT
RECEIVE SEND
SEND RECEIVE
DISCONNECT DISCONNECT

Client machine Server machine

(1) Connect request
Client (2) ACK
process Server
(3) Request for data process
System (4) Reply
calls
(5) Disconnect
Operating
Kernel Protocol Drivers (6) Disconnect Kernel Protocol Drivers
system stack stack

01 – 17 Introduction/1.3 Software
 Services vs. Protocols

Service: set of primitives that a layer provides to the

layer above it.

Protocol: set of rules that prescribe the layout and

meaning of packets, and often the order in which
specific packets should be sent.

Note: The same service can be realized by differ-

ent protocols; each protocol can be implemented dif-
ferently (using different data structures, programming
languages, etc.)

Layer k + 1 Layer k + 1

Service provided by layer k

Protocol
Layer k Layer k

Layer k - 1 Layer k - 1

01 – 18 Introduction/1.3 Software

The OSI Model

Layer Name of unit
exchanged
Application protocol
7 Application Application APDU

Interface
Presentation protocol
6 Presentation Presentation PPDU

Session protocol
5 Session Session SPDU

Transport protocol
4 Transport Transport TPDU
Communication subnet boundary
Internal subnet protocol
3 Network Network Network Network Packet

2 Data link Data link Data link Data link Frame

1 Physical Physical Physical Physical Bit

Host A Router Router Host B

Network layer host-router protocol

Data link layer host-router protocol
Physical layer host-router protocol

Note: Knowing the layering by heart is important

01 – 19 Introduction/1.4 Reference Models
 OSI Physical Layer

Essence: Describes the transmission of raw bits in

terms of mechanical and electrical issues:

Example: Connect two computers by means of a wire:

• Setting -3V on the wire corresponds to a binary 1;

+4V is a binary 0
• The wire is not to be longer than 15 meters
• You may change the voltage at most 20,000 times
per second (Question: what’s the transfer rate?)

01 – 20 Introduction/1.4 Reference Models

OSI Data Link Layer (1/2)

Observation: We need to at least detect bit trans-

mission errors ⇒ send bits in frames that add re-
dundancy to detect something went wrong

Bits 8 8 8 >0 16 8

01111110 Address Control Data Checksum 01111110

Examples:

• Add a parity bit to every 7 transmitted bits: 1 says

there were odd number of 1’s; 0 says there were
an even number of 1’s
• Add a checksum (cyclic redundancy check) that
should match the bits before it

Also: Provide the mechanisms so that fast senders

don’t overwhelm slow receivers (flow control)
01 – 21 Introduction/1.4 Reference Models
 OSI Data Link Layer (2/2)

Observation: We also need to specify how a number

of computers can share a common channel (i.e., wire)
⇒ medium access control sublayer (MAC):

• Specifies how one out of several competing senders,

is eventually allowed exclusive access to the wire

• Common approach 1: listen to each other; retreat

when you hear someone else, and try again later

• Common approach 2: wait your turn by passing a

token between all stations

Well-known protocols: Ethernet, token ring, token

bus, FDDI

01 – 22 Introduction/1.4 Reference Models

OSI Network Layer

Essence: Describes how routing (and congestion) is

to be done. Mostly needed in subnets.

• How do we find out which computers/routers are

in the network?

• How do we calculate the best route from A to B?

• What happens when a computer/router goes down?

• Should multicasting/broadcasting be supported?

• What happens if a router becomes overloaded

and starts dropping packets (congestion)?

• Can we detect and avoid “hot spots?”

01 – 23 Introduction/1.4 Reference Models

 OSI Transport Layer

Observation: Generally offers connection-oriented as

well as connectionless services, and varying degrees
of reliability. This layer provides the actual network
interface to applications

• Often provides network interface through sock-

ets (UNIX, Windows)

• Allows to set up a connection to another applica-

tion, and subsequently deliver data reliably, and
in the order that it was sent

• Often also support for secure connections

• Also support for datagrams: unreliable message

passing on a per-message basis

01 – 24 Introduction/1.4 Reference Models

OSI Session and Presentation

Layers

Session: tells how applications can set up long-lasting

communications, for example, allowing a connec-
tion to be re-established when suddenly broken
(think of downloading large files).

Presentation: Describes everything that is needed

to exchange data in a platform-independent way.
Example: think of byte ordering in different com-
puters, or passing binary data through e-mail

01 – 25 Introduction/1.4 Reference Models

 OSI Application Layer

Essence: Contains the rest

Traditional: Name services (DNS), security, e-mail

(SMTP), News (NNTP), Web (HTTP)

Modern: All types of middleware protocols to support

distributed systems:

• New transfer protocols for object systems like

Java (RMI), CORBA (IIOP), DCOM (propriety)
• Special protocols to handle replication, fault
tolerance, caching, data persistence, etc.

High-level protocols: Special application-level proto-

cols for e-commerce, banking, EDI, etc.

01 – 26 Introduction/1.4 Reference Models

The TCP/IP Model

OSI TCP/IP

7 Application Application

6 Presentation Not present

in the model
5 Session

4 Transport Transport

3 Network Internet

2 Data link Host-to-network

1 Physical

The bad thing is that TCP/IP did not make a clear dis-
tinction between services, interfaces, and protocols.
That makes it much harder to re-implement certain
layers.

TCP/IP protocol suite is successful because (1) it was

there when needed (OSI implementations were ter-
rible), (2) freely distributed with the UNIX operating
system.
01 – 27 Introduction/1.4 Reference Models
 Example: The Internet
Regional ISP
Backbone

POP

NAP

Client Telephone
Server farm
system

Corporate
LAN
Router

ISP Internet Service Provider

POP Point Of Presence – interface between telephone
system and ISP’s network
NAP Network Access Point – connection point to differ-
ent backbones

01 – 28 Introduction/1.5 Example Networks