Protocol “Layers”
Networks are
complex!
many “pieces”:
Question:
hosts
Is there any hope of
routers organizing structure of
links of various network?
media
applications
Or at least our discussion
of networks?
protocols
hardware,
software
1: Introduction 1
Organization of air travel
ticket (purchase) ticket (complain)
baggage (check) baggage (claim)
gates (load) gates (unload)
runway takeoff runway landing
airplane routing airplane routing
airplane routing
a series of steps
1: Introduction 2
Organization of air travel: a different view
ticket (purchase) ticket (complain)
baggage (check) baggage (claim)
gates (load) gates (unload)
runway takeoff runway landing
airplane routing airplane routing
airplane routing
Layers: each layer implements a service
via its own internal-layer actions
relying on services provided by layer below
1: Introduction 3
Layered air travel: services
Counter-to-counter delivery of person+bags
baggage-claim-to-baggage-claim delivery
people transfer: loading gate to arrival gate
runway-to-runway delivery of plane
airplane routing from source to
destination
1: Introduction 4
Distributed implementation of layer
functionality
ticket (purchase) ticket (complain)
baggage (check) baggage (claim)
Departing
gates (load) gates (unload)
arriving
airport
airport
runway takeoff runway landing
airplane routing airplane routing
intermediate air traffic sites
airplane routing airplane routing
airplane routing
1: Introduction 5
Next example
Luton,
Anh
Trại quốc
Chuyển thông điệp giam Mai Thị
T16 Phương HuyềnTiến
thứ trưởng gửi cô
“I lov u” cho TH thông điệp “I lov u”
From : Tiến thứ trưởng,
Trại giam T16
To : Hoa hậu MP, Luton
“I lov u”
Bưu cục Hà Tây Bưu cục Luton
Bưu cục Hà Nội Bưu cục London
1: Introduction 6
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?
1: Introduction 7
Internet protocol stack
application: supporting network
applications
application
ftp, smtp, http
transport: process-to-process data
transport
transfer
tcp, udp
network: routing of datagrams from
network
source to destination
ip, routing protocols
link
link: data transfer between
neighboring network elements
physical
ppp, ethernet
physical: bits “on the wire”
1: Introduction 8
Layering: logical communication
Each layer: application
transport
distributed network
“entities” link
physical
implement
network
layer functions application link
at each node transport physical
entities network
link
perform physical
application application
actions, transport transport
exchange network network
messages link link
physical physical
with peers
1: Introduction 9
Layering: logical communication
data
E.g.: transport application
take data from
transport
transport
network
app link
add addressing, physical
reliability check ack network
info to form application link
“datagram” transport data physical
network
send datagram to
link
peer data
physical
application application
wait for peer to
transport transport
transport
ack receipt network
network
analogy: post link link
office physical physical
1: Introduction 10
Layering: physical communication
data
application
transport
network
link
physical
network
application link
transport physical
network
link
physical data
application application
transport transport
network network
link link
physical physical
1: Introduction 11
Protocol layering and data
Each layer takes data from above
adds header information to create new data unit
passes new data unit to layer below
source destination
M application application M message
Ht M transport transport Ht M segment
Hn Ht M network network Hn Ht M datagram
Hl Hn Ht M link link Hl Hn Ht M frame
physical physical
1: Introduction 12
Internet structure: network of
networks
roughly hierarchical
national/international
local
backbone providers (NBPs) ISP
e.g. BBN/GTE, Sprint, AT&T,
regional ISP
IBM, UUNet
interconnect (peer) with NBP B
each other privately, or at
public Network Access Point NAP NAP
(NAPs)
regional ISPs NBP A
connect into NBPs regional ISP
local ISP, company local
ISP
connect into regional ISPs
1: Introduction 13
National Backbone Provider
e.g. BBN/GTE US backbone network
1: Introduction 14
Internet History
1961-1972: Early packet-switching principles
1961: Kleinrock - 1972:
queueing theory shows ARPAnet
effectiveness of packet- demonstrated publicly
switching NCP (Network Control
1964: Baran - packet-
Protocol) first host-
switching in military host protocol
nets first e-mail program
1967: ARPAnet
ARPAnet has 15 nodes
conceived by Advanced
Reearch Projects Agency
1969: first ARPAnet
node operational
1: Introduction 15
Internet History
1972-1980: Internetworking, new and proprietary
nets
1970: ALOHAnet satellite
Cerf and Kahn’s
network in Hawaii internetworking
1973: Metcalfe’s PhD thesis principles:
proposes Ethernet minimalism, autonomy
1974: Cerf and Kahn - - no internal changes
architecture for required to
interconnecting networks interconnect networks
late70’s: proprietary best effort service
architectures: DECnet, SNA, model
XNA
stateless routers
late 70’s: switching fixed
decentralized control
length packets (ATM
precursor) define today’s Internet
1979: ARPAnet has 200 nodes architecture
1: Introduction 16
Internet History
1980-1990: new protocols, a proliferation of
networks
1983: deployment of new national
TCP/IP networks: Csnet,
1982: smtp e-mail BITnet, NSFnet,
protocol defined Minitel
1983: DNS defined 100,000 hosts
for name-to-IP- connected to
address translation confederation of
1985: ftp protocol networks
defined
1988: TCP
congestion control
1: Introduction 17
Internet History
1990’s: commercialization, the WWW
Early 1990’s: ARPAnet
Late 1990’s:
decomissioned est. 50 million
1991: NSF lifts restrictions on
computers on Internet
commercial use of NSFnet
est. 100 million+
(decommissioned, 1995)
early 1990s: WWW users
hypertext [Bush 1945,
backbone links
Nelson 1960’s] runnning at 1 Gbps
HTML, http: Berners-Lee
1994: Mosaic, later
Netscape
late 1990’s:
commercialization of the
WWW
1: Introduction 18
Chapter 1: Summary
Covered a “ton” of You now hopefully
material! have:
Internet overview context, overview,
what’s a protocol?
“feel” of networking
network edge, core,
more depth, detail
access network
later in course
performance: loss,
delay
layering and service
models
backbones, NAPs, ISPs
history
ATM network
1: Introduction 19
