Professional Documents
Culture Documents
Chapter1 Intro PDF
Chapter1 Intro PDF
Chapter1 Intro PDF
Introduction 1-2
What’s the Internet: “nuts and bolts” view
protocols control sending, router workstation
receiving of msgs server
e.g., TCP, IP, HTTP, FTP, mobile
Internet: “network of local ISP
networks”
loosely hierarchical
public Internet versus regional ISP
private intranet
Internet standards
RFC: Request for comments
IETF: Internet Engineering
Task Force company
network
Introduction 1-3
What’s the Internet: a service view
communication
infrastructure enables
distributed applications:
Web, email, games, e-
commerce, file sharing
communication services
provided to apps:
Connectionless unreliable
connection-oriented
reliable
Introduction 1-4
What’s a protocol?
human protocols: network protocols:
“what’s the time?” machines rather than
“I have a question” humans
introductions all communication
activity in Internet
… specific msgs sent governed by protocols
… specific actions taken protocols define format,
when msgs received, order of msgs sent and
or other events received among network
entities, and actions
taken on msg
transmission, receipt
Introduction 1-5
What’s a protocol?
a human protocol and a computer network protocol:
Hi
TCP connection
request
Hi
TCP connection
Got the response
time? Get http://www.awl.com/kurose-ross
2:00
<file>
time
network edge:
applications and
hosts
network core:
routers
network of
networks
access networks,
physical media:
communication links
Introduction 1-8
The network edge:
end systems (hosts):
run application programs
e.g. Web, email
at “edge of network”
client/server model
client host requests, receives
service from always-on server
e.g. Web browser/server;
email client/server
peer-peer model:
minimal (or no) use of
dedicated servers
e.g. Skype, BitTorrent, KaZaA
Introduction 1-9
Network edge: connection-oriented service
Introduction 1-11
Chapter 1: roadmap
1.1 What is the Internet?
1.2 Network edge
1.3 Network core
Network access and physical media
Internet structure and ISPs
1.4 Delay & loss in packet-switched networks
1.5 Protocol layers, service models
1.6 Networks under attack: security (covered in
Chap. 8)
1.7 History
Introduction 1-12
The Network Core
mesh of interconnected
routers
the fundamental
question: how is data
transferred through net?
circuit switching:
dedicated circuit per
call: telephone net
packet-switching: data
sent thru net in
discrete “chunks”
Introduction 1-13
Network Core: Circuit Switching
End-end resources
reserved for “call”
link bandwidth, switch
capacity
dedicated resources:
no sharing
circuit-like
(guaranteed)
performance
call setup required
Introduction 1-14
Network Core: Circuit Switching
network resources dividing link bandwidth
(e.g., bandwidth) into “pieces”
divided into “pieces” frequency division
pieces allocated to calls time division (TDM)
resource piece idle if code division (CDM)
not used by owning call
(no sharing)
Introduction 1-15
Network Core: Packet Switching
each end-end data stream resource contention:
divided into packets aggregate resource
user A, B packets share demand can exceed
network resources amount available
each packet uses full link congestion: packets
bandwidth (for short time) queue, wait for link use
resources used as needed store and forward:
packets move one hop
at a time
Bandwidth division into “pieces” Node receives complete
Dedicated allocation packet before forwarding
Resource reservation
Introduction 1-16
Packet Switching: Statistical Multiplexing
100 Mb/s
A Ethernet statistical multiplexing C
1.5 Mb/s
B
queue of packets
waiting for output
link
D E
Keep in mind:
Bit rate [bandwidth]
(bits per second) of
access network?
shared or dedicated?
Introduction 1-21
Chapter 1: roadmap
1.1 What is the Internet?
1.2 Network edge
1.3 Network core
Network access and physical media
Internet structure and ISPs
1.4 Delay & loss in packet-switched networks
1.5 Protocol layers, service models
1.6 Networks under attack: security (covered in
Chap. 8)
1.7 History
Introduction 1-22
Internet structure: network of networks
roughly hierarchical
at center: “tier-1” ISPs (e.g., MCI, Sprint, AT&T, Cable
and Wireless), national/international coverage
treat each other as equals
Tier-1 providers
also interconnect
Tier-1 at public network
providers
Tier 1 ISP
NAP access points
interconnect (NAPs)
(peer)
privately
Tier 1 ISP Tier 1 ISP
Introduction 1-23
Tier-1 ISP: e.g., Sprint
Sprint US backbone network
DS3 (45 Mbps)
OC3 (155 Mbps)
OC12 (622 Mbps)
OC48 (2.4 Gbps)
Seattle
Tacoma
POP: point-of-presence
to/from backbone
New York
Stockton Cheyenne Chicago
peering Pennsauken
San Jose
… … Relay
Wash. DC
Roachdale
Kansas City
.
Anaheim
…
…
Atlanta
to/from customers
Fort Worth
Orlando
Introduction 1-24
Internet structure: network of networks
Tier-2 ISPs
Tier-2 ISP pays Tier-2 ISP also peer
Tier-2 ISP privately with
tier-1 ISP for
connectivity to Tier 1 ISP each other,
rest of Internet NAP interconnect
tier-2 ISP is
at NAP*
customer of
tier-1 provider Tier 1 ISP Tier 1 ISP Tier-2 ISP
local
ISP Tier 3 local
local local
ISP ISP
ISP ISP
Local and tier- Tier-2 ISP Tier-2 ISP
3 ISPs are
customers of Tier 1 ISP
higher tier NAP
ISPs
connecting
them to rest
Tier 1 ISP Tier 1 ISP Tier-2 ISP
of Internet
local
Tier-2 ISP Tier-2 ISP
ISP
local local local
ISP ISP ISP Introduction 1-26
Internet structure: network of networks
local
ISP Tier 3 local
local local
ISP ISP
ISP ISP
Tier-2 ISP Tier-2 ISP
Tier 1 ISP
NAP
B
packets queueing (delay)
free (available) buffers: arriving packets
dropped (loss) if no free buffers
Introduction 1-29
Four sources of packet delay
1. nodal processing: 2. queueing (node "i")
check bit errors time waiting at output
determine output link link for transmission
depends on congestion
Small - Neglect level of router
processing delay in all
problems = Qi /Rout
transmission
A propagation
B
nodal
processing queueing Qi =preceding bits in queue
Rout = output link bps
Introduction 1-30
Delay in packet-switched networks
3. Transmission delay: 4. Propagation delay:
R=link bandwidth (bps) d = length of physical link
L=packet length (bits) s = propagation speed in
time to send bits into medium (~2x108 m/sec)
link = L/R propagation delay = d/s
B
nodal
processing queueing
Introduction 1-31
Caravan analogy
100 km 100 km
ten-car toll toll
caravan booth booth
Cars “propagate” at Time to “push” entire
100 km/hr caravan through toll
booth onto highway =
Toll booth takes 12 sec to
12*10 = 120 sec
service a car
(transmission time) Time for last car to
propagate from 1st to
car~bit; caravan ~ packet
2nd toll both:
Q: How long until caravan 100km/(100km/hr)= 1 hr
is lined up before 2nd toll
A: 62 minutes
booth?
Introduction 1-32
Caravan analogy (more)
100 km 100 km
ten-car toll toll
caravan booth booth
Yes! After 7 min, 1st car
Cars now “propagate” at at 2nd booth and 3 cars
1000 km/hr still at 1st booth.
Toll booth now takes 1 1st bit of packet can
min to service a car arrive at 2nd router
Q: Will cars arrive to before packet is fully
2nd booth before all transmitted at 1st router!
cars serviced at 1st
booth?
Introduction 1-33
Multiple links: sum over nodes i (Qi/Ri)
sum over links i (L/Ri)
Nodal delay Xtotal / s
3 probes 3 probes
3 probes
Introduction 1-36
Packet loss due to buffer
overflow
queue (aka "buffer") – each output link of
router has buffer with finite capacity
many input links may be putting packets
into the queue.
when packet arrives to full queue, packet is
dropped (aka "lost" or "dropped")
lost packet may be retransmitted by
previous node, by source end system, or
not retransmitted at all
Introduction 1-39
Organization of air travel
a series of steps
Introduction 1-40
Layering of airline functionality
airplane routing airplane routing airplane routing airplane routing airplane routing
Introduction 1-41
Why layering?
Dealing with complex systems:
explicit structure allows identification,
relationship of complex system’s pieces
layered reference model for discussion
modularization eases maintenance, updating of
system
change of implementation of layer’s service
transparent to rest of system
e.g., change in gate procedure doesn’t affect
rest of system
layering considered harmful?
Introduction 1-42
Internet protocol stack
application: supporting network applications
FTP, SMTP, HTTP
transport: process-process data transfer
application
TCP, UDP
network: routing of datagrams from source transport
to destination
IP, routing protocols network
link: data transfer between neighboring
network elements link
PPP, Ethernet
physical: bits “on the wire” (Ethernet or physical
WiFi adapter)
Introduction 1-43