Chapter 1 Computer Networks and The Internet MME
Chapter 1 Computer Networks and The Internet MME
Abstraction
2-4
Chapter 1: introduction
Chapter goal: Overview/roadmap:
Get “feel,” “big picture,” What is the Internet? What is a
introduction to terminology protocol?
• more depth, detail later in Network edge: hosts, access network,
course physical media
Network core: packet/circuit switching,
internet structure
Performance: loss, delay, throughput
Protocol layers, service models
Security
History
Introduction: 1-5
The Internet: a “nuts and bolts”
view
Billions of connected mobile network
computing devices: national or global ISP
hosts = end systems
running network apps at
Internet’s “edge”
bikes
Gaming devices
Others?
Internet phones diapers
Introduction: 1-7
The Internet: a “nuts and bolts”
view
mobile network
4G
Internet: “network of networks” national or global ISP
• Interconnected ISPs
Streaming
protocols are everywhere Skype
IP
video
• control sending, receiving of
local or
messages regional ISP
• e.g., HTTP (Web), streaming video,
home network
Skype, TCP, IP, WiFi, 4/5G, Ethernet content
provider
HTTP network
Internet standards
datacenter
network
Ethernet
• RFC: Request for Comments
• IETF: Internet Engineering Task TCP
enterprise
Force network
WiFi
Introduction: 1-8
The Internet: a “services” view
Infrastructure that provides mobile network
Introduction: 1-9
What’s a protocol?
Human protocols: Network protocols:
“what’s the time?” computers (devices) rather than humans
“I have a question” all communication activity in Internet
introductions governed by protocols
Rules for:
Protocols define the format, order of
… specific messages sent messages sent and received among
… specific actions taken network entities, and actions taken
when message received,
or other events on message transmission, receipt
Introduction: 1-10
What’s a protocol?
A human protocol and a computer network protocol:
Hi TCP connection
request
Hi TCP connection
response
Got the
time? GET http://gaia.cs.umass.edu/kurose_ross
2:00
<file>
time
enterprise
network
Introduction: 1-13
A closer look at Internet structure
mobile network
enterprise
network
Introduction: 1-14
A closer look at Internet structure
mobile network
Network core:
network
interconnected routers
network of networks enterprise
network
Introduction: 1-15
Access networks and physical media
Q: How to connect end systems mobile network
to edge router?
national or global ISP
enterprise
network
Introduction: 1-16
Access networks: home networks
Wireless and wired
devices
to/from headend or
central office
often combined
in single box
to Internet
to Internet
Introduction: 1-18
Access networks: enterprise networks
Enterprise link to
ISP (Internet)
institutional router
Ethernet institutional mail,
switch web servers
Introduction: 1-22
Links: physical media
Wireless radio Radio link types:
signal carried in various Wireless LAN (WiFi)
“bands” in electromagnetic • 10-100’s Mbps; 10’s of meters
spectrum wide-area (e.g., 4G/5G cellular)
no physical “wire” • 10’s Mbps (4G) over ~10 Km
broadcast, “half-duplex” (sender Bluetooth: cable replacement
to receiver) • short distances, limited rates
propagation environment terrestrial microwave
effects: • point-to-point; 45 Mbps channels
• reflection satellite
• obstruction by objects • up to < 100 Mbps (Starlink) downlink
• Interference/noise • 270 msec end-end delay (geostationary)
Introduction: 1-23
Chapter 1: roadmap
What is the Internet?
What is a protocol?
Network edge: hosts, access
network, physical media
Network core: packet/circuit
switching, internet structure
Performance: loss, delay, throughput
Security
Protocol layers, service models
History
Introduction: 1-24
Multiplexing multiple logical flows over a
single physical link
Switching
The network core
mesh of interconnected routers mobile network
national or global ISP
packet-switching: hosts break
application-layer messages into packets
• network forwards packets from one
router to the next, across links on local or
path from source to destination regional ISP
enterprise
network
Introduction: 1-26
Two key network-core functions
Introduction: 1-28
Packet-switching: store-and-
forward
L bits
per packet
3 2 1
source destination
R bps R bps
Introduction: 1-29
Packet-switching: queueing
R = 100 Mb/s
A C
D
B R = 1.5 Mb/s
E
queue of packets
waiting for transmission
over output link
Introduction: 1-30
Packet-switching: queueing
R = 100 Mb/s
A C
D
B R = 1.5 Mb/s
E
queue of packets
waiting for transmission
over output link
Packet queuing and loss: if arrival rate (in bps) to link exceeds
transmission rate (bps) of link for some period of time:
packets will queue, waiting to be transmitted on output link
packets can be dropped (lost) if memory (buffer) in router fills up
Introduction: 1-31
Alternative to packet switching: circuit
switching
end-end resources allocated to,
reserved for “call” between source
and destination
in diagram, each link has four circuits.
• call gets 2nd circuit in top link and 1st
circuit in right link.
dedicated resources: no sharing
• circuit-like (guaranteed) performance
circuit segment idle if not used by call (no
sharing)
commonly used in traditional telephone networks
* Check out the online interactive exercises for more examples: h ttp://gaia.cs.umass.edu/kurose_ross/interactive
Introduction: 1-32
Circuit switching: FDM and TDM
Frequency Division Multiplexing
(FDM) 4 users
frequency
optical, electromagnetic frequencies
divided into (narrow) frequency
bands
each call allocated its own band, can
time
transmit at max rate of that narrow
band
Time Division Multiplexing (TDM)
frequency
time divided into slots
each call allocated periodic slot(s),
can transmit at maximum rate of time
(wider) frequency band (only) during
its time slot(s) Introduction: 1-33
Packet switching versus circuit
switching
example:
1 Gb/s link
…..
N
each user: users 1 Gbps link
• 100 Mb/s when “active”
• active 10% of time
Q: how many users can use this network under circuit-switching and packet switching?
circuit-switching: 10 users
packet switching: with 35 users, Q: how did we get value 0.0004?
probability > 10 active at same time A: HW problem (for those with
is less than .0004 * course in probability only)
* Check out the online interactive exercises for more examples: h ttp://gaia.cs.umass.edu/kurose_ross/interactive
Introduction: 1-34
Packet switching versus circuit
switching
Is packet switching a “slam dunk winner”?
great for “bursty” data – sometimes has data to send, but at other times not
• resource sharing
• simpler, no call setup
excessive congestion possible: packet delay and loss due to buffer overflow
• protocols needed for reliable data transfer, congestion control
Q: How to provide circuit-like behavior with packet-switching?
• “It’s complicated.” We’ll study various techniques that try to make packet
switching as “circuit-like” as possible.
net
access
access net
net
IXP access
access net
net
ISP A
…
…
Content provider network
access
net
IXP ISP B access
net
access
net
ISP C
access
net
access
net
regional ISP access
… net
access access …
net access net
net
Introduction: 1-37
Internet structure: a “network of networks”
B
packets in buffers (queueing delay)
free (available) buffers: arriving packets
dropped (loss) if no free buffers
Introduction: 1-40
Packet delay: four sources
transmission
A propagation
B
nodal
processing queueing
B
nodal
processing queueing
Introduction: 1-43
Caravan analogy
100 km 100 km
Introduction: 1-44
Packet loss
queue (aka buffer) preceding link in buffer has finite capacity
packet arriving to full queue dropped (aka lost)
lost packet may be retransmitted by previous node, by source end
system, or not at all
buffer
(waiting area) packet being transmitted
A
B
packet arriving to
full buffer is lost
* Check out the Java applet for an interactive animation (on publisher’s website) of queuing and loss
Introduction: 1-45
Throughput
throughput: rate (bits/time unit) at which bits are being sent from
sender to receiver
• instantaneous: rate at given point in time
• average: rate over longer period of time
link
pipecapacity
that can carry linkthat
pipe capacity
can carry
serverserver,
sends with
bits Rsfluid at rate
bits/sec Rfluid
c
at rate
bits/sec
(fluid)
fileinto
of Fpipe
bits (Rs bits/sec) (Rc bits/sec)
to send to client
Introduction: 1-46
Throughput
Rs < Rc What is average end-end throughput?
Rs bits/sec Rc bits/sec
Rs bits/sec Rc bits/sec
bottleneck link
link on end-end path that constrains end-end throughput
Introduction: 1-47
Throughput: network scenario
per-connection end-end
Rs throughput:
Rs Rs min(Rc,Rs,R/10)
in practice: Rc or Rs is
R
often bottleneck
Rc Rc
Rc
* Check out the online interactive exercises for more
examples: http://gaia.cs.umass.edu/kurose_ross/
A C
A C
Introduction: 1-53
Bad guys: denial of service
Denial of Service (DoS): attackers make resources (server,
bandwidth) unavailable to legitimate traffic by
overwhelming resource with bogus traffic
1. select target
2. break into hosts
around the network
(see botnet)
target
3. send packets to target
from compromised
hosts
Introduction: 1-54
Lines of defense:
authentication: proving you are who you say you are
• cellular networks provides hardware identity via SIM card; no such
hardware assist in traditional Internet
confidentiality: via encryption
integrity checks: digital signatures prevent/detect tampering
access restrictions: password-protected VPNs
firewalls: specialized “middleboxes” in access and core
networks:
off-by-default: filter incoming packets to restrict senders, receivers,
applications
detecting/reacting to DOS attacks
… lots more on security (throughout, Chapter 8) Introduction: 1-55
Chapter 1: roadmap
What is the Internet?
What is a protocol?
Network edge: hosts, access
network, physical media
Network core: packet/circuit
switching, internet structure
Performance: loss, delay, throughput
Security
Protocol layers, service models
History
Introduction: 1-56
Protocol “layers” and reference models
Introduction: 1-57
Example: organization of air travel
Introduction: 1-60
Layered Internet protocol stack
application: supporting network applications
• HTTP, IMAP, SMTP, DNS
application
application
transport: process-process data transfer
• TCP, UDP transport
transport
network: routing of datagrams from source to
destination network
• IP, routing protocols
link
link: data transfer between neighboring
network elements physical
• Ethernet, 802.11 (WiFi), PPP
physical: bits “on the wire”
Introduction: 1-61
Services, Layering and Encapsulation
M
Application exchanges messages to implement some
application application service using services of transport layer application
Ht M
transport Transport-layer protocol transfers M (e.g., reliably) from transport
one process to another, using services of network layer
source destination
Introduction: 1-62
Services, Layering and Encapsulation
M
application application
Ht M
transport Transport-layer protocol transfers M (e.g., reliably) from transport
one process to another, using services of network layer
Hn Ht M
network Network-layer protocol transfers transport-layer segment
network
[Ht | M] from one host to another, using link layer services
link network-layer protocol encapsulates link
transport-layer segment [Ht | M] with
physical network layer-layer header Hn to create a physical
network-layer datagram
source • Hn used by network layer protocol to destination
implement its service
Introduction: 1-63
Services, Layering and Encapsulation
M
application application
Ht M
transport transport
Hn Ht M
network Network-layer protocol transfers transport-layer segment
network
[Ht | M] from one host to another, using link layer services
Hl Hn Ht
link M
link
Link-layer protocol transfers datagram [Hn| [Ht |M] from
host to neighboring host, using network-layer services
physical link-layer protocol encapsulates network physical
datagram [Hn| [Ht |M], with link-layer header
source Hl to create a link-layer frame destination
Introduction: 1-64
Encapsulation
Matryoshka dolls (stacking dolls)
message M
application M application
segment Ht M
transport Ht M
transport
datagram Hn Ht M Hn Ht M
network network
frame Hl Hn Ht M Hl Hn Ht M
link link
physical physical
source destination
Introduction: 1-67
source Encapsulation:
message
segment Htt
M
M
application
transport
an end-end
datagram Hn Ht M network view
frame Hl Hn Ht M link
physical
link
physical
switch
destination Hn Ht M network
M application Hl Hn Ht M link Hn Ht M
Ht M transport physical
Hn Ht M network
Hl Hn Ht M link router
physical
Introduction: 1-68
The OSI Reference Model (contd.)
7 application network services (email, file transfer)
Introduction 69
The OSI Reference Model (contd.)
Encapsulation
data
5 session SH PH AH data
4 transport TH SH PH AH data
3 network NH TH SH PH AH data
Introduction 70
The TCP/IP Reference Model
The TCP/IP Reference Model (Transmission Control Protocol/Internet
Protocol)
Introduction 71
The TCP/IP Reference Model (contd.)
Introduction 72
Application Layer
Introduction 73
Transport Layer
Five basic services
Segmenting upper-layer application data
Establishing end-to-end operations
Sending segments from one end host to another end host
Ensuring data reliability
Providing flow control
Process A
Process B
Introduction 74
Internet Layer
The purpose of the Internet layer is to select the best path through the network for packets to travel.
IP performs the following operations:
• Defines a packet and an addressing scheme
• Transfers data between the Internet layer and network access layers
• Routes packets to remote hosts
Introduction 75
Network Access
The network access layer is also called the host-to-network layer.
Concerned with all of the issues that an IP packet requires to actually make a physical link to the network
media.
Network access layer functions include mapping IP addresses to physical hardware addresses and
encapsulation of IP packets into frames.
Introduction 76
Comparison: OSI and TCP/IP Model
Similarities of the OSI and TCP/IP models:
• Both have layers
• Both have application layers, though they include different services
• Both have comparable transport and network layers
• Packet-switched, not circuit-switched, technology is assumed
• Networking professionals need to know both models
Differences of the OSI and TCP/IP models:
• TCP/IP combines the presentation and session layer into its application layer
• TCP/IP combines the OSI data link and physical layers into 1 layer
• TCP/IP appears simpler because it has fewer layers
• TCP/IP transport layer using UDP does not always guarantee reliable delivery of packets as
transport layer in the OSI model does
Introduction 77
Comparison: OSI and TCP/IP Model (contd.)
Introduction 78
ISO/OSI reference model
Two layers not found in Internet
application
protocol stack!
presentation
presentation: allow applications to
interpret meaning of data, e.g., encryption, session
compression, machine-specific conventions transport
session: synchronization, checkpointing, network
recovery of data exchange link
Internet stack “missing” these layers!
physical
• these services, if needed, must be
implemented in application The seven layer OSI/ISO
reference model
• needed?
Introduction: 1-79