CN Chp1 (Compatibility Mode)

Computer Networks
Orientation
Jamali@iust.ac.ir Orientation 1 -1
Chapter 1: Orientation
1.0 Why Networking

1.1 What is the Internet?
1.2 Network Structure
Network edge
Network core
Network access and physical media
1.3 Internet structure and ISPs
1.4 Delay & loss in packet-switched networks
1.5 Protocol layers, service models
1.6 History
Why Networking !
Distributed Software
Application (will be discussed): WEB, email, 3-tier appl., …
Database
Directory
Resource Sharing
File, Software, Data, … (Network File System, File
Transfer, …)
CPU, Memory, Peripherals, …
Communication
Email, Chat, TV, Radio, Video Conference, Telephone, .
Virtual Terminal (Remote Login)
Application Software
Platform Services Application Agent

Application Program Interface (API)
Graphics
Platform (OS + Hardware)
Data Interchange
Data Management
User Interface Application Application
process process
Software Engineering
Application Program Interface (API)
Communication Services
Platform (OS + Hardware)
Inter-process Communication
Distributed Applications or Network Application:
Application System Client/Server
Application Software (Client Part) Application Software (Server Part)

Client (user) Agent Server Agent
Application Program Interface (API) Application Program Interface (API)
Networking Software & Hardware Networking Software & Hardware

Platform (OS + Hardware) Platform (OS + Hardware)
Client Agents Examples:

Internet Explorer + http,
Opera + http
MS’s Outlook + SMTP, Communication
Netscape’s Messenger + Network
SMTP, Eudora + SMTP
… next slide
Client/Server Applications
Application Process Application Process

Application
(Client Side)
process (Server Side)
Application Program Interface (API) Application Program Interface (API)
Networking Software & Hardware Networking Software & Hardware

Platform (OS + Hardware) Platform (OS + Hardware)
Server Agents Examples:

Internet Information
Sever + http,
Appachi + http Communication
SQL query engines + http Network
Communication Software
Examples: TCP, UDP; IP…
Layered Application Model
Presentation
Client Part
User Interface
Application
Software Business (Application Logic)
Server Parts
Data (Database Access)
Client Part
Presentation: The client agent remains focused on

presenting information to or receiving input from
the user.
User Interface: User’s access to the application
logic via client agent. It can be dynamic and
configured by user. It is build on the top of the
user interface control.
Dynamic User Interface:
• Customizing the look (example: www.cstore.com
• Customizing the content ( examples: my.yahoo.com ,
www.exite.com )
Server Parts
Business Rules (Application Logic)

Units of processing or algorithms that represents
concept of importance to the organization using
database.
Data (Database Access)

Logic to connect to database; access/manipulate data held
within databases.
Layered Application:
3-Tier Client/Server Model
Runs by Application
Run by Client Agent Server Agent
Business
Presentation (Application Logic)
User Interface
user Application Sever

Runs by Database
Client Workstation Server Agent
Run by Client Agent (rich client) Communication Data
Network (Data Access and
Presentation Storage)
User Interface
Mobile Client Data Server
user Workstation Database
(thin client)
Jamali@iust.ac.ir Orientation 1-10

“Logical Tiers vs Physical Tiers
Application Model
Logical Tiers
Presentation Client
• Presentation
• User Interface User Interface Workstation
• Business Business Application
• Data (Application Logic) Server
Data
Database
Physical Tiers (Database Access)
• Client workstation
• Application server
• Data Base

Chapter 1 Outline
1.0 Why Networking

Network edge
Network core
1.6 History

Local ISP (LAN)
Router
modem Telephone LAN Switch

External Link
Lines Remote Access Server
Modem pools
hub
modem Client
Servers
Client
Server
Client
Client Printer
modem External Link

Router
modem

internet: network of networks
router local ISP regional ISP
modem links
server modem
modem
Base Station
workstation
local ISP
mobile station
company
network

Internet
millions of connected computing devices:

hosts, end-systems
PCs workstations, servers, …
Personal Data Assistances, phones, …
running network apps
communication links
fiber, copper, radio, satellite
transmission rate = bandwidth
routers: forward packets
Networking Hardware and Software
Protocols, Hubs, LAN Switches, Repeaters,

Internet
protocols control sending, receiving of

messages
e.g., TCP, IP, HTTP, FTP, PPP, …
Internet: “network of networks”
loosely hierarchical
public Internet versus private intranet
Internet standards (IAB)
RFC: Request for comments
IETF: Internet Engineering Task Force

Internet Services
Examples?
Search Engines (Google)
Email (Hotmail)
Shopping (Amazon)
Auctions (eBay)
Chat (AOL)
Goals?
Fast service (low latency)
Service all users (scalability)
Always available (fault tolerance)

intranet
router
firewall
intranet
the Internet
Intranet: access is denied from outside

A private corporate network consisting of hosts, routers,
and networks that use TCP/IP technology. An intranet may
or may not connect to the global Internet.

extranet
Company 3
Company 1
Company 2
Extranet: an internet of networks

each of which is belong to
individual company or organization

IP addressing: ICANN
Q: How does an ISP get block of addresses
and Names?
A: ICANN: (Internet Corporation For
Assigned Names and Numbers)
The organization that took over the IANA
duties after Postel’s death.
IANA: (Internet Assigned Number Authority)
Essentially one individual (Jon Postel). IANA
was originally responsible for assigning IP
addresses and the constants used in TCP/IP
protocols. Replaced by ICANN in 1999.

IP addressing: ICANN
ICANN coordinates the assignment of

identifiers that must be globally unique for
the Internet to function.
allocates addresses
manages DNS
assigns domain names, resolves disputes
assigns default port numbers
sets protocol parameter

DNS Root Servers
(a) NSI Herndon, VA

(c) PSInet Herndon, VA
(d) U Maryland College Park, MD (i) NORDUnet Stockholm, Sweden
(g) DISA Vienna, VA
(h) ARL Aberdeen, MD
(j) NSI (TBD) Herndon, VA
(k) RIPE London, UK
(m) WIDE Tokyo, Japan
(e) NASA Mt View, CA

(f) Internet Software C. Palo Alto, CA
(b) USC-ISI Marina del Rey, CA

(l) ICANN Marina del Rey, CA

What’s the Internet: a service view
communication
infrastructure enables local ISP
regional ISP
modem
distributed applications:
Web, email, games, modem
e-commerce, database.,
file (MP3) sharing
communication services
provided to apps:
connectionless company
connection-oriented network

Chapter 1: Outline
1.0 Why Networking

Network edge
Network core
1.6 History

Network Structure
network edge: local ISP

regional ISP
modem
applications and
hosts modem
network core:
routers
access networks,
physical media:
company
communication links network

The network edge:
end systems (hosts):

run application programs
local ISP
e.g. Web, email modem
regional ISP
at “edge of network”
client/server model modem
client host requests, receives

service from always-on server
e.g. Web browser/server;
email client/server
peer-peer model:
company
minimal (or no) use of network
dedicated servers
e.g. Gnutella, KaZaA

Client--Server
Client
Client Side
Software
modem
1. Client-Server
Client Side Software modem
Peer Side
Server Side Software
2. Peer-to-Peer ! (chapter 2)
Server Side
Peer Side Software

Server Types
Web server
File Server (example: Network File System)
Database Server
Application Server
Groupware Server
Software Server
Object Server
Proxy Server
DNS Server

Network edge: connection-
connection-oriented service
Goal: data transfer TCP service [RFC 793]

between end systems reliable, in-order byte-
handshaking: setup stream data transfer
(prepare for) data loss: acknowledgements
transfer ahead of time and retransmissions
set up “state” in two flow control:
communicating hosts sender won’t overwhelm
TCP - Transmission receiver
Control Protocol congestion control:
Internet’s connection- senders “slow down sending
oriented service rate” when network
congested

Network edge: connectionless service
Goal: data transfer App’s using TCP:

between end systems HTTP (Web), FTP (file
same as before! transfer), Telnet
UDP - User Datagram (remote login), SMTP
Protocol [RFC 768]: (email)
Internet’s
connectionless service
App’s using UDP:
unreliable data
transfer streaming media,
teleconferencing, DNS,
no flow control
Internet telephony
no congestion control

Chapter 1 Outline
1.0 Why Networking

Network edge
Network core
1.6 History

The Network Core
mesh of interconnected
local ISP
routers modem
regional ISP
the fundamental
question: how is data modem
transferred through net?

circuit switching:
dedicated circuit per
call: telephone net
packet-switching: data
company
sent thru net in network
discrete “chunks”

Network Core: Circuit Switching
End-end resources local ISP

regional ISP
reserved for “call” modem
link bandwidth, switch modem
capacity
dedicated resources:
no sharing
circuit-like
(guaranteed)
performance company
network
call setup required

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
resource piece idle if

not used by owning call
(no sharing)

Packet Switching: Statistical Multiplexing
10 Mbs
Ethernet statistical multiplexing C
A
1.5 Mbs
empty
B buffer
queue of packets
waiting for output
link
D E
Sequence of A & B packets does not have

fixed pattern statistical multiplexing.
In TDM each host gets same slot in revolving
TDM frame.
Packet switching versus circuit switching
Packet switching allows more users to use network!
User: 1
Switch
1 Mbps link
User: N
Each user:
sends 100 kbps when “active”
is active p=10% of time
Circuit-Switch ≤ 10 simultaneous users

How many Users?
Packet-Switch binomial distribution:

if N=35 users, The probability that k
for active users > 10 users be active
there is: together:
probability < 0.0017
N k
for active users <= 10 P (k ; N , p ) =   p (1 − p ) N − k
there is: k
probability > 0.9983 N N!
in which :   =
 
35  k  k!( N − k )!
P( k f 10 ) = ∑ P( k ;35,0.1 ) = 0.0017
k =11
P( k <= 10 ) = 1 - 0.0017 = 0.9983

Packet Switching Users
Switch supports 35 simultaneous users
(connections)
Up to 10 users be active: no queue, packet
switching has almost the same delay
performance as circuit switching.
More than 10 users be active: output queue
begin to grow and the connections experience
queuing delay.
Because the probability of having 11 or more
simultaneous active users is 0.0017,almost the
same delay performance as circuit switching.
Packet switching allows more than 3 times the
number of users.
Packet switching versus circuit switching
Great for bursty data

resource sharing
simpler
no call setup
Excessive congestion:
packet delay and loss
protocols needed for reliable data transfer,

congestion control
Q: How to provide circuit-like behavior?
bandwidth guarantees needed for audio/video
applications.
still an unsolved problem (chapter 6)

Packet--switching: store
Packet store--and-
and-forward
L
R R R
Takes L/R seconds to Example:

transmit (push out) L = 7.5 Mbits; message
packet of L bits on to size
link or R bps R = 1.5 Mbps; link
Entire packet must bandwidth
arrive at router before message transmission
it can be transmitted time = L/R = 5 sec
on next link: store and
delay = 3L/R = 15 sec
forward
delay = 3L/R
Packet Switching: Message Segmenting
Now break up the message

into 5000 packets
Each packet 1,500 bits

1 msec to transmit
packet on one link
pipelining: each link
works in parallel
Delay reduced from 15
sec to 5.002 sec

Packet--switched networks: forwarding
Packet
Goal: move packets through routers from source to

destination
we’ll study several path selection (i.e. routing)algorithms
(chapter 4)
datagram network:
destination address in packet determines next hop
routes may change during session
virtual circuit network:
each packet carries tag (virtual circuit ID), tag
determines next hop
fixed path determined at call setup time, remains fixed
thru call
routers maintain per-call state

Network Taxonomy
Telecommunication
networks
Circuit-switched Packet-switched
networks networks
Networks Datagram
FDM TDM
with VCs Networks
Datagram network is not either connection-oriented

or connectionless.
Internet provides both connection-oriented (TCP)
and connectionless services (UDP) to applications.

Chapter 1 Outline
1.0 Why Networking

Network edge
Network core
1.6 History

Access networks and physical media
Q: How to connection end

systems to edge router?
local ISP
residential access nets modem
regional ISP
institutional
institutional access modem
networks (school,
company)
mobile access networks
Keep in mind:
bandwidth (bits per
second) of access company
network? network
shared or dedicated?

Residential access: point to point access
Dialup via modem

up to 56Kbps direct access to modem
router (often less)

Can’t surf and phone at same
modem
time: can’t be “always on”
ADSL: asymmetric digital subscriber line

up to 1 Mbps upstream (today typically < 256 kbps)
up to 8 Mbps downstream (today typically < 1 Mbps)
FDM: 50 kHz - 1 MHz for downstream

4 kHz - 50 kHz for upstream
0 kHz - 4 kHz for ordinary telephone

Residential access: cable modems
HFC: hybrid fiber coax

asymmetric: up to 10Mbps upstream, 1 Mbps
downstream
network of cable and fiber attaches homes to
ISP router
shared access to router among home
issues: congestion, dimensioning
deployment: available via cable companies, e.g.,

MediaOne

Residential access: cable modems
Diagram: http://www.cabledatacomnews.com/cmic/diagram.html

Cable Network Architecture: Overview
Typically 500 to 5,000 homes
cable headend
home
cable distribution
network (simplified)

cable headend
home
cable distribution
network (simplified)

server(s)
cable headend
home
cable distribution
network

FDM:
C
O
V V V V V V N
I I I I I I D D T
D D D D D D A A R
E E E E E E T T O
O O O O O O A A L
1 2 3 4 5 6 7 8 9
Channels
cable headend
home
cable distribution
network

Company access: local area networks
company/univ local area

network (LAN) connects
end system to edge router modem
Ethernet:
shared or dedicated link modem
connects end system

and router
10 Mbs, 100Mbps,
Gigabit Ethernet
deployment: institutions,
home LANs happening now
LANs: chapter 5
Wireless access networks
shared wireless access

network connects end
system to router router
via base station “access
point”
wireless LANs: base
802.11b (WiFi): 11 Mbps station
wider-area wireless access
provided by telco operator
3G ~ 384 kbps
• Will it happen?? mobile
WAP/GPRS in Europe stations (hosts)
(IranCell)

Home networks
Typical home network components:
ADSL or cable modem
(Network Address Translation) A technology that
router/firewall/NAT allows hosts with private addresses to communicate
with an outside network such as the global Internet.
Ethernet
wireless access point router/Firewall/NAT
wireless
to/from laptops
Internet
cable modem Ethernet (switched) wireless access point

Physical (Transmission) Media-
Media-Link
Physical Media (link) : what lies between transmitter & receiver.

Twisted Pair
Twisted Pair (TP)
Unshielded/Shielded
UTP/STP
Category 3: traditional
phone wires, 10 Mbps
Ethernet
Category 5 TP: 100Mbps
Ethernet
…

Physical Media: coax, fiber
Coaxial cable: Fiber optic cable:

two concentric copper glass fiber carrying light
conductors pulses, each pulse a bit
bidirectional high-speed operation:
baseband: high-speed point-to-point
transmission (e.g., 5 Gps)
single channel on cable
legacy Ethernet low error rate: repeaters
broadband: spaced far apart ; immune
multiple channel on cable
to electromagnetic noise
HFC

Physical media: radio
signal carried in Radio link types:

electromagnetic terrestrial microwave
spectrum e.g. up to 45 Mbps channels
no physical “wire” LAN (e.g., WaveLAN)
bi-directional 2Mbps, 11Mbps
propagation wide-area (e.g., cellular)
environment effects: e.g. 3G: hundreds of kbps
reflection satellite
obstruction by objects up to 50Mbps channel (or
interference multiple smaller channels)
270 msec end-end delay
geosynchronous versus
LEOS
Links: Delay and Bandwidth
Delay
Latency for propagating data along the link
Corresponds to the “length” of the link
Typically measured in seconds
Bandwidth (Capacity)
Amount of data sent (or received) per unit time
Corresponds to the “capacity” of the link
Typically measured in bits per second
Bandwidth delay x bandwidth

(Bps) (bit)
Delay
(sec)
Chapter 1 Outline
1.0 Why Networking

Network edge
Network core
1.6 History

Tier Definition-
Definition-Tier 1
Tier 1 providers make settlement-free interconnection

arrangements with other Tier 1 providers, in which the two
networks agree to carry each other's traffic (so-called
"peering" with one another) at no cost.
No Tier 1 carriers have to pay for IP transit to any other

Tier 1, and in general all other ISPs directly or indirectly pay
the Tier 1s for access to their networks.
Tier 1 providers own the physical medium over which

information is carried, as well as the network equipment
which manages that information.

Tier 1 IPv4 ISPs
The following are believed to be the only Tier 1 ISPs
worldwide:
1. AOL Transit Data Network (ATDN)-AS 1668
2. AT&T-AS 7018 (not 2685, 2686, 2687, 2688 or 7132)
3. Global Crossing (GX)-AS 3549
4. Level 3-AS 3356
5. Verizon Business (UUnet)-AS 701 (not 702, 703 or 19262)
6. Nippon Telegraph and Telephone Corp. (NTT)-AS 2914
7. Qwest-AS 209
8. SAVVIS (Cable & Wireless America)-AS 3561
9. Sprint Nextel Corporation-AS 1239
• In the Internet, an autonomous system (AS) is a collection of IP
networks and routers under the control of one entity (or sometimes
more) that presents a common routing policy to the Internet. See RFC
1930 for additional detail on this updated definition.

UUNET US backbone network

Tier--1 ISPs Interconnection
Tier
High Speed Link from Telecom Companies NAPs
Topology: Full Mesh ▪▪▪
Data Rates: 622Mbps, 2.5-10Gbps 1
NAPs
1. NSF 1988 ,T1 ▪▪▪
NAPs
2. ANS 1993 ,T3 ▪▪▪
9 2
NAP: Network Access Point
4
3
NAPs
▪▪▪
▪▪▪ NAPs
Tier--2 ISPs
Tier
Tier Definition-
Definition-Tier 2, 3
There is no formal interconnection hierarchy,

lower-tier companies are divided into two
categories:
Tier 2 - A network who peers with other networks, but
still pays for transit to reach some portion of the
Internet.
Tier 3 - A network who solely purchases transit from
other networks to reach the Internet.
Many of Tier 2 and 3 companies are very large Internet

providers, but since they purchase IP transit from other
networks they are not considered Tier 1.

Tier--2 ISPs / Access ISPs
Tier
Tier-1
Tier-
ISP To Tier-1 ISP
▪▪▪
NAPs
▪▪▪▪
Tier-2
Tier-
Tier-2
Tier-
Access ISP
ISP
ISP
Servers modem
Access Remote Clients

3 Com
ISP
RAS modem
Clients +
Modem Pool
Tier--1 ISP: e.g., UUNET
Tier

Internet structure: network of networks
roughly hierarchical
at center: “tier-1” ISPs (e.g., UUNet, BBN/Genuity,
Sprint, AT&T), 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

“Tier-2” ISPs: smaller (often regional) ISPs

Connect to one or more tier-1 ISPs, possibly other tier-2 ISPs
Tier-2 ISPs also

peer privately with
each other,
interconnect at NAP
Tier-2 ISP pays Tier-2 ISP Tier-2 ISP

tier-1 ISP for
connectivity to Tier 1 ISP
rest of Internet NAP
tier-2 ISP is
customer of
tier-1 provider Tier 1 ISP Tier 1 ISP Tier-2 ISP
Tier-2 ISP Tier-2 ISP

“Tier-3” ISPs and local ISPs

last hop (“access”) network (closest to end systems)
local
ISP Tier 3 local
local local
ISP ISP
ISP ISP
Local and tier- Tier-2 ISP Internet
Tier-2 ISP
3 ISPs are Connection
customers of Tier 1 ISP Providers (ICPs)
higher tier NAP For local ISPs
ISPs
connecting
them to rest
Tier 1 ISP Tier 1 ISP Tier-2 ISP
of Internet
local
ISP
local local local
ISP ISP ISP

End to End Communication
a packet passes through many networks!
Access
ISP Tier 3 Access
Access Access
ISP ISP
ISP ISP
Tier 1 ISP
NAP
Tier 1 ISP Tier 1 ISP Tier-2 ISP

Access
ISP
Access Access Access
ISP ISP ISP

Chapter 1 Outline
1.0 Why Networking

Network edge
Network core
1.6 History

How do loss and delay occur?
packets queue in router buffers

packet arrival rate to link exceeds output link capacity
packets queue, wait for turn
packet being transmitted (delay)
B
packets queue (delay)
free (available) buffers: arriving packets
dropped (loss) if no free buffers

Four sources of packet delay
1. nodal processing: 2. queueing

check bit errors time waiting at output
determine output link link for transmission
depends on congestion
level of router
transmission
A propagation
B
nodal
processing queue

Delay in packet-
packet-switched networks
3. Transmission delay: 4. Propagation delay:

R=link bandwidth (bps) d = length of physical link
L=number of bits in s = propagation speed in
packet (bits) medium (~2x108 m/sec)
time to send bits into propagation delay = d/s
link = L/R
Note: s and R are very
different quantities!
transmission
A propagation
B
nodal
processing queue
bit length: s/R [m]
packet length: Ls/R [m]
Caravan analogy
10 3 2 1
car=bit
caravan = packet
cars speed (km/hr) = propagation speed (m/sec)
service rate at toll booth (car/sec) = bandwidth
(bit/sec)

Caravan Analogy (cont.)
10 3 2 1
4km
cars speed = 120 km/hr = 2km/min

1
toll booth takes 12 sec to service a car ( 12 car/sec)
Q: How long until caravan is lined up before 2nd toll booth?

Time to “push” entire caravan through toll booth onto
highway = 12*10 = 120sec = 2min
Time for last car to propagate from 1st to 2nd toll both:
120km/(120km/hr)= 1 hr
A: 62 minutes

Caravan Analogy (cont.)
10 9 8 7 3 2
1
cars speed = 1200 km/hr = 20km/min

toll booth takes 1min to service a car ( 1 car/min)
Q: Will cars arrive to 2nd booth before all cars serviced at 1st
booth?
After (1+6) min, 1st car at 2nd booth and 3 cars still at 1st
booth.
1st bit of packet can arrive at 2nd router before packet is
fully transmitted at 1st router!
Bit Length
bit length = s/R
Packet length = Ls/R
s = propagation speed of energy in the link (medium)
[m/sec]
R = link bandwidth [bps]
L = number of bits in packet [bits]
Example : s= 200m/µs;
R=10Mbps [Tbit =0.1 µs];
L= 500 Byte = 2000 bit
20m
2000
1999
Propagation direction
1
2
4
3
source destination
20×2000 m
link

Nodal delay
d nodal = d proc + d queue + d trans + d prop
dproc = processing delay

typically a few msecs or less
dqueue = queuing delay
depends on congestion
dtrans = transmission delay
= L/R, significant for low-speed links
dprop = propagation delay
a few microsecs to hundreds of msecs

Queuing delay (revisited)
Average queuing delay

R=link bandwidth (bps)
L=packet length (bits)
a=average packet
arrival rate
traffic intensity = La/R

La/R
1
La/R ~ 0: average queuing delay small
La/R —> 1: delays become large
La/R > 1: more “work” arriving than can be
serviced, average delay infinite!
“Real” Internet delays and routes
What do “real” Internet delay & loss look like?

Traceroute program: provides delay
measurement from source to router along end-end
Internet path towards destination. For all i:
sends three packets that will reach router i on path
towards destination
router i will return packets to sender
sender times interval between transmission and reply.
3 probes
3 probes
3 probes
“Real” Internet delays and routes
traceroute: gaia.cs.umass.edu to www.eurecom.fr

Three delay measements from
gaia.cs.umass.edu to cs-gw.cs.umass.edu
1 cs-gw (128.119.240.254) 1 ms 1 ms 2 ms
2 border1-rt-fa5-1-0.gw.umass.edu (128.119.3.145) 1 ms 1 ms 2 ms
3 cht-vbns.gw.umass.edu (128.119.3.130) 6 ms 5 ms 5 ms
4 jn1-at1-0-0-19.wor.vbns.net (204.147.132.129) 16 ms 11 ms 13 ms
5 jn1-so7-0-0-0.wae.vbns.net (204.147.136.136) 21 ms 18 ms 18 ms
6 abilene-vbns.abilene.ucaid.edu (198.32.11.9) 22 ms 18 ms 22 ms
7 nycm-wash.abilene.ucaid.edu (198.32.8.46) 22 ms 22 ms 22 ms trans-oceanic
8 62.40.103.253 (62.40.103.253) 104 ms 109 ms 106 ms
9 de2-1.de1.de.geant.net (62.40.96.129) 109 ms 102 ms 104 ms link
10 de.fr1.fr.geant.net (62.40.96.50) 113 ms 121 ms 114 ms
11 renater-gw.fr1.fr.geant.net (62.40.103.54) 112 ms 114 ms 112 ms
12 nio-n2.cssi.renater.fr (193.51.206.13) 111 ms 114 ms 116 ms
13 nice.cssi.renater.fr (195.220.98.102) 123 ms 125 ms 124 ms
14 r3t2-nice.cssi.renater.fr (195.220.98.110) 126 ms 126 ms 124 ms
15 eurecom-valbonne.r3t2.ft.net (193.48.50.54) 135 ms 128 ms 133 ms
16 194.214.211.25 (194.214.211.25) 126 ms 128 ms 126 ms
17 * * *
18 * * * * means no reponse (probe lost, router not replying)
19 fantasia.eurecom.fr (193.55.113.142) 132 ms 128 ms 136 ms

Packet Loss
queue (aka buffer) preceding link in buffer has

finite capacity
when packet arrives to full queue, packet is
dropped (aka lost)
lost packet may be retransmitted by previous
node, by source end system, or not retransmitted
at all

Chapter 1 Outline
1.0 Why Networking

Network edge
Network core
1.6 History

Network Models
The network model is

defined in 3-D space.
App.
App.Software
Software(User)
(User)Plane:
Plane: We study this part only!
Data
DataCommunication.
Communication.
Control Plane:
Connection setup and
connection Maintenance,
Resources access control and App. Software
access level control. (User)
Management Plane: Plane
Measurement and
management of network
Figure: Network Model.
performance.

Layering: A hierarchical Partitioning
of Networks
Networks are complex!
many “elements”: Question:
Hosts, Is there any hope of
Routers, organizing structure of
Links of various media,
network?
Application Software,
Control and
Or at least our discussion
Management Software, of networks?
Communication,
Hardware.

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?

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 defines:
when msgs received, format,
or other events order of msgs sent and
received among
network entities, and
actions taken on msg
transmission,
reception.
Protocols (stack)
Distributed Systems relies on communicating

elements.
Communicating elements follow a set of rules,
syntax and semantics, i.e. Protocol.
In other words:
A protocol governs the co-operation of two remote
parties (elements), or
Two elements, remote to each other, do together a task
using a predefined rules, syntax, and semantics.
Protocol Stack: It is a set of protocols, designed
to govern entire network.

Internet Layering Model and Protocols
Application: supporting network

applications
FTP, SMTP, HTTP application
Transport: host-host data transfer
TCP, UDP transport
Network: routing of datagrams
from source to destination network
IP, routing protocols
Link: data transfer between link
neighboring network elements
PPP, Ethernet physical
Physical: Putting bits “on the wire”

Layers and Addresses
Application Layer
domain name
e.g. www.iust.ac.ir
Transport Layer application
the identity of the application in the
destination host
Port number: 2 bytes transport
e.g. 80
Network Layer network
the network identity of the destination host
IP address: 4 bytes for IPv4
e.g. 202.156.1.78 link
Link Layer
the identity of network interface card

MAC address (physical address): 6 bytes
physical
e.g. 00-04-23-5E-6A-93

OSI model vs TCP/IP model
application
presentation application application
Session
transport transport transport
network network network
Link network link

interface
physical physical
Open Systems Interconnection model
(International Standard Organization-ISO, UN)

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 process Destination process
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 Tl link link Hl Hn Ht M Tl frame
physical physical
PDUs: frame, datagram (packet), segment, message

Layering and Protocol
Appl. Soft. Appl. Soft.
App. Layer Protocols application

application (ftp, http, SMTP, …)
Transport Layer
transport Protocol (TCP, UDP) transport
network NETWORK Network Layer

Protocols (IP, OSPF, RSVP) network
Link Layer
link Protocols (Ethernet, FDDI, …) link
Physical Layer
physical Protocols (Ethernet, FDDI, …) physical
Physical Communication Channel

Protocol layering and data
App. Process decides to send

a message to its counterpart
Message App. Process
App. Layer adds its header,
sends the message to transport layer
Ha Message application
Transport layer breaks down
the message into several parts, transport
add its header to each part
Ht Ht Ht Ht
And makes segments.
It sends one-by-one segments
to network layer
network

Protocol Data Units
Appl. Soft. [tps], [HTTPops/s] Appl. Soft.

,[NFS IOPS]
application message application
[mes/sec]
Segment
transport transport
Baud = changes in signal/sec
[seg/sec]
Datagram
network [Packet/sec] network
Frame
link [frame/sec] link
1st layer PDU
physical (physical frame)
[bps]
physical
[Baud], [Hz]
Physical Communication Channel
Network Bandwidth
Bandwidth,, Throughput and Goodput
Application Transport Network Link Physical

Layer Layer Layer Layer layer
Bandwidth Tps, Segmant/s Packet/s Frame/s Bit/s
Throughput HTTPops/s,
Goodput …
Bandwidth: The rate at which the data units can be

transmitted.
Throughput: The rate at which the data units are delivered
(transferred).
It is a function of load.
Its upper-band is Bandwidth.
Goodput: The rate at which the useful data units are
delivered (transferred).
Its upper-band is the Throughput.

Throughput, Goodput vs Load
Throughput
Goodput

Example: Network Layer Goodput
Goodput:
( recieved packets - recieved replica) × payload length per packet [bit]
Goodput [b / s ] =
recieving time duration [sec]
Efficiency:
goodput [bps]
Efficiency = × 100
optimum goodput [bps]
Optimum goodput = goodput in condition of :
no - loss packet, no - corupted packet, and no - congestion link.

Protocols/Services
Application Program
Services
application
End-to-End
protocols
transport
network
Data Transport
Services Hop-to-Hop
link protocols
physical

From Application Viewpoint
App. Software Controlled

Application Software application by App. Soft.
API
Application Program Interface (API) transport
Communication Software & Hardware network Controlled
by OS
Platform (OS + Hardware) link
physical

Layering: Physical Communication
data
application
transport
network Host A
Router R
link
physical network
modem
link
physical
application
transport Host B
network
link modem data
physical
application
application
transport
transport
network
network
link
link
physical
physical
Layering: Logical Communication-
Communication-1
application
Each layer: transport
distributed network
link
“entities” physical network
implement
modem
link
layer functions physical
at each node application

transport
entities network
perform link modem
actions, physical
application
application
exchange transport
transport
messages with network
network
link
peers link
physical
physical

Layering: Logical Communication
data
application
E.g.: transport transport
transport
take data from app network
add addressing,
link
physical network
reliability check modem
info to form link

ack physical
“datagram”
data
send datagram to application
peer transport
network
wait for peer to link
ack receipt
modem
data
physical
application
analogy: post application
transport
transport
office transport
network
network
link
link
physical
physical

TCP/IP protocol stack
icmp: Internet control message protocol
ftp: file transfer protocol
ospf: open shortest path first protocol
http; hypertext transfer protocol rsvp: resource reservation protocol
Smtp: simple mail transfer protocol igmp: Internet group management protocol
Mime: multipurose Internet mail extensions
telnet=virtual terminal simple network trival file
management pr. transfer pr.real time pr.
mime domain name
service
ftp http smtp telnet snmp tftp rtp dns …
Transmission Control Pr. (TCP) User Datagram Pr. (UDP)
arp: address resolution protocol

rarp: reverse address resolution protocol
rsvp igmp Internet Protocol (IP) icmp ospf arp rarp
Ethernet, token ring, FDDI, ATM, Frame relay, SNA, X25

Chapter 1 Outline
1.0 Why Networking

Network edge
Network core
1.6 History

Internet Host Count
Internet Systems Consortium, Inc. (ISC) is a nonprofit

corporation
dedicated to supporting the infrastructure of the universal
connected self-organizing Internet and
has autonomy to participates by developing and maintaining core
production quality software, protocols, and operations.

Internet Standard: RFCs
RFC Numbers
Introduction Year

Internet History
1961-1972: Early packet-switching principles
1961: Kleinrock - queueing 1972:

theory shows ARPAnet
effectiveness of packet- demonstrated publicly
switching NCP (Network Control
1964: Baran - packet- Protocol) first host-
switching in military nets host protocol
1967: ARPAnet conceived first e-mail program
by Advanced Research ARPAnet has 15
Projects Agency nodes
1969: first ARPAnet
node operational

Internet History
1972-1980: Internetworking, new and proprietary nets
1970: ALOHAnet satellite Cerf and Kahn’s

network in Hawaii internetworking principles:
1973: Metcalfe’s PhD thesis minimalism, autonomy -
proposes Ethernet no internal changes
1974: Cerf and Kahn - required to
architecture for interconnect networks
interconnecting networks best effort service
late70’s: proprietary model
architectures: DECnet, SNA, stateless routers
XNA decentralized control
late 70’s: switching fixed define today’s Internet
length packets (ATM architecture
precursor)
1979: ARPAnet has 200 nodes
Internet History
1980-1990: new protocols, a proliferation of networks
1983: deployment of new national networks:

TCP/IP Csnet, BITnet,
1982: SMTP e-mail NSFnet, Minitel
protocol defined 100,000 hosts
1983: DNS defined connected to
for name-to-IP- confederation of
address translation networks
1985: FTP protocol
defined
1988: TCP congestion
control

Internet History
1990, 2000’s: commercialization, the Web, new apps
Early 1990’s: ARPAnet Late 1990’s – 2000’s:

decommissioned
more killer apps: instant
1991: NSF lifts restrictions on
messaging, peer2peer
commercial use of NSFnet
(decommissioned, 1995)
file sharing (e.g.,
Naptser)
early 1990s: Web
hypertext [Bush 1945, Nelson
network security to
1960’s] forefront
HTML, HTTP: Berners-Lee
est. 50 million host, 100
1994: Mosaic, later Netscape
million+ users
late 1990’s:
backbone links running
commercialization of the Web at Gbps

References & Links
Complimentary Hyperlinks
This part provides hyperlinks to interesting
(and hopefully useful) computer-networking
resources. Most of these resources provide
complimentary information to the material in
chapter 1. If you're asked to write a paper
pertaining to a specialized topic in computer
networking, these resources should serve as a
good starting point for your research.
References and Hyperlinks

Complimentary Hyperlinks 1
IEEE History Center

http://www.ieee.org/organizations/history_center/oral_hist
ories/comsoc_oh.html.
Oral Histories that have been collected to commemorate the
50th Anniversary of the IEEE Communications Society. A
number of interesting interviews with pioneers in the field.
International Engineering Consortium: Web ProForum

Tutorials http://www.iec.org/online/tutorials/
More than 150 tutorials on communications and networking
topics, with a focus on cutting edge technology. The tutorials
vary in terms of their technical depth, but many are
outstanding, and all are extremely well-written and very
readable. This is the first place we look when looking for an on-
line survey or tutorial.

Broadband: Bringing home the bits

http://www.nap.edu/html/broadband
Extensive report on the importance and future of
residential broadband access from the Computer Science
And Telecommunications Board, National Research
Council, January 2002
Webopedia http://www.pcwebopaedia.com/
Online dictionary for computer and Internet technology
Internet Economics
http://china.si.umich.edu/telecom/net-
economics.html
Comprehensive index for resources relating to Internet
economics, including regulation and pricing.

traceroute.org http://www.traceroute.org/
As discussed in Section 1.6, Traceroute provides routes and packet
delays between pairs of hosts in the Internet. This site gives you direct
access to hundreds of source hosts from which you can trace routes to
arbitrary destination hosts. Choose a country, a source host in that
country, and any destination host -- then see how the packets weave
their way through the Internet.
Internet Engineering Task Force (IETF) http://www.ietf.org/

The IETF is an open international community concerned with the
development and operation of the Internet and its architecture. The
IETF was formally established by the Internet Architecture Board
(IAB), http://www.isi.edu/iab, in 1986. The IETF meets three times a
year; much of its ongoing work is conducted via mailing lists by working
groups. Typically, based upon previous IETF proceedings, working
groups will convene at meetings to discuss the work of the IETF
working groups. The IETF is administered by the Internet Society,
http://www.isoc.org/, whose Web site contains lots of high-quality,
Internet-related material.

Henning Schulzrinne's Internet Technical

Resources
http://www.cs.columbia.edu/~hgs/internet
Henning Schulzrinne has an extensive - although not
always current - index of online resources for the
Internet.
The Association for Computing Machinery (ACM)

http://www.acm.org/
A major international professional society that has
technical conferences, magazines, and journals in the
networking area. The ACM Special Interest Group in
Data Communications (SIGCOMM),
http://www.acm.org/sigcomm, is the group within this
body whose efforts are most closely related to
networking

The Institute of Electrical and Electronics Engineers (IEEE)

http://www.ieee.org/
The other major international professional society that has technical
conferences, magazines, and journals in the networking area. The IEEE
Communications Society, http://www.comsoc.org/, and the IEEE
Computer Society, http://www.computer.org/, are the groups within
this body whose efforts are most closely related to networking.
The SETI@home Project http://setiathome.ssl.berkeley.edu/

As discussed in Section 1.2, the SETI@home project is a scientific
experiment that uses Internet-connected computers to search for
extraterrestrial intelligence. You can download the SETI program
directly from this site.
Nerds 2.0.1 A Brief History of the Internet

http://www.pbs.org/opb/nerds2.0.1
This is the Web site for the highly entertaining and informative PBS
video on the history of the Internet. The PBS video, Triumph of the
Nerds, about the history of personal computers, is also recommended.

Leonard Kleinrock's Personal History of the Internet

http://www.lk.cs.ucla.edu/LK/Inet/birth.html
Professor Leonard Kleinrock made numerous important contributions to
Internet technology and to the field of computer networking. This page
provides his own interesting and highly entertaining description of the
early history of the Internet.
The DSL Forum http://www.dslforum.org/

DSL Forum is a consortium of nearly 250 leading industry players
covering telecommunications, equipment, computing, networking and
service provider companies. The site is rich in information about
developments in digital subscriber loop and broadband access to the
home.
Cable-modems.org http://www.cable-modems.org/
This site has many tutorials on cable modems, hybrid fiber-coax, and
related topics. Also includes reviews of cable modem products.

A note on Internet Request for Comments (RFCs): Copies

of Internet RFCs are maintained at multiple sites. The RFC
URLs below all point into the RFC archive at the Information
Sciences Institute (ISI), maintained the the RFC Editor of
the Internet Society (the body that oversees the RFCs).
Other RFC sites include http://www.faqs.org/rfc,
http://www.pasteur.fr/other/computer/RFC (located in
France), and http://www.csl.sony.co.jp/rfc/ (located in
Japan).
Internet RFCs can be updated or obsoleted by later RFCs.
We encourage you to check the sites listed above for the
most up-to-date information. The RFC search facility at ISI,
http://www.rfc-editor.org/rfcsearch.html, will allow you to
search for an RFC and show updates to that RFC.

References and Hyperlinks 1
[@Home 1998] @Home, "Frequently Asked

Questions," http://www.home.com/qa.html.
[Abramson 1970] N. Abramson, "The Aloha
System--Another Alternative for Computer
Communications," Proceedings of Fall Joint
Computer Conference, AFIPS Conference, p. 37,
1970.
[ADSL 1998] ADSL Forum, "ADSL Tutorial,"
http://www.adsl.com/adsl_tutorial.html
[Almanac 1998] Computer Industry Almanac,
http://www.c-i-a.com/

[AT&T Apps 1998] AT&T, "Killer Apps,"

http://www.att.com/technology/forstudents/brainspin/netw
orks/killerapps.html
[AT&T Bandwidth 1999] AT&T, "Bandwidth: The Need for
Speed,"
http://www.att.com/technology/forstudents/brainspin/netw
orks/bandwidth/game.html
[AT&T Optics 1999] AT&T, "What are fiber optics?,"
http://www.att.com/technology/forstudents/brainspin/fiber
optics/
[Baran 1964] P. Baran, "On Distributed Communication
Networks," IEEE Transactions on Communication Systems,
Mar. 1964. Rand Corporation Technical report with the same
title (Memorandum RM-3420-PR, 1964).
http://www.rand.org/publications/RM/RM3420/

[Berners-Lee 1989] T. Berners-Lee, CERN, "Information

Management: A Proposal," Mar. 1989, May 1990.
http://www.w3.org/History/1989/proposal.html
[Bertsekas 1991] D. Bertsekas and R. Gallagher, Data
Networks, 2nd Ed. , Prentice Hall, Englewood Cliffs, NJ,
1991.
[Bush 1945] V. Bush, "As We May Think," The Atlantic
Monthly, July 1945.
http://www.theatlantic.com/unbound/flashbks/computer/bu
shf.htm
[Cable 1998] Cable Data News, "Overview of Cable Modem
Technology and Services," 1998.
http://www.cabledatacomnews.com/cmic/cmic1.html

[Cerf 1974] V. Cerf and R. Kahn, "A Protocol for Packet

Network Interconnection," IEEE Transactions on
Communications Technology, Vol. COM-22, No. 5, pp. 627-
641.
[Cisco LAN 1998] Cisco Systems Inc., "Designing Switched
LAN Internetworks,"
http://www.cisco.com/univercd/cc/td/doc/cisintwk/idg4/nd
2012.htm
[Clark 1988] D. Clark, " The Design Philosophy of the
DARPA Internet Protocols, Proceedings of ACM
SIGCOMM'88, (Stanford, CA), Aug. 1988, Vol. 18, No. 4,
http://www.acm.org/sigcomm/ccr/archive/1995/jan95/ccr-
9501-clark.html
[Cusumano 1998] M.A. Cusumano and D.B. Toffle, Competing
on Internet Time: Lessons from Netscape and its Battle
with Microsoft, Free Press, 1998

[Daigle 1991] J. N. Daigle, Queuing Theory for

Telecommunications, Addison-Wesley, Reading, MA, 1991.
[DEC 1990] Digital Equipment Corporation, "In Memoriam: J.
C. R. Licklider 1915-1990," SRC Research Report 61, Aug.
1990. http://gatekeeper.dec.com/pub/DEC/SRC/research-
reports/abstracts/src-rr-061.html
[Dertouzos 1999] M. Dertouzos, "The Future of Computing,"
Scientific American, August 1999, pp.52-55.
[Fraser 1983] A. G. Fraser, "Towards a Universal Data
Transport System," IEEE Journal on Selected Areas in
Communications, Vol. SAC-1, No 5, pp. 803-816.

[Fraser 1993] A. G. Fraser (1993). "Early Experiments with

Asynchronous Time Division Networks," IEEE Network
Magazine, Vol. 7, No. 1, pp. 12-27.
[Goodman 1997] D. Goodman (Chair), The Evolution of
Untethered Communications, National Academy Press,
Washington DC, Dec. 1997.
http://www.nap.edu/readingroom/books/evolution/index.htm
l
[Green 1992] P. Green, Fiber Optics Networks, Prentice
Hall, 1992
[Greenberg 1997] I. Greenberg, "The Future of the Living
Room."
http://www.cnet.com/Content/Features/Dlife/Living/index.
html

[Haynal 1999] R. Haynal, "Internet Backbones,"

http://navigators.com/isp.html
[Huston 1999a] G. Huston, "Interconnection, Peering, and
Settlements - Part I," The Internet Protocol Journal, Vol. 2, No. 1,
(June 1999). http://www.cisco.com/warp/public/759/ipj_2-
1/ipj_2-1_ps1.html
[Huston 1999b] G. Huston, "Interconnecting, Peering, and
Settlements - Part II," The Internet Protocol Journal, Vol. 2, No. 2
(June 1999). http://www.cisco.com/warp/public/759/ipj_2-
2/ipj_2-2_ps1.html
[Iren 1999] S. Iren, P. Amer, P. Conrad, "The Transport Layer:
Tutorial and Survey," ACM Computing Surveys, Vol 31, No 4, (Dec
1999). http://www.cis.udel.edu/~amer/PEL/survey/
[Jacobson 1988] V. Jacobson, "Congestion Avoidance and Control,"
Proceedings of ACM SIGCOMM '88, pp. (Stanford, CA, Aug. 1988),
314-329, ftp://ftp.ee.lbl.gov/papers/congavoid.ps.Z

[Kegel 1999] Dan Kegel's ISDN Page,

http://alumni.caltech.edu/~dank/isdn/
[Kleinrock 1961] L. Kleinrock, "Information Flow in Large
Communication Networks," RLE Quarterly Progress Report, July
1961.
[Kleinrock 1964] L. Kleinrock, 1964 Communication Nets:
Stochastic Message Flow and Delay, McGraw-Hill, NY, NY, 1964.
[Kleinrock 1975] L. Kleinrock, Queuing Systems, Vol. 1, John Wiley,
New York, 1975.
[Kleinrock 1976] L. Kleinrock, Queuing Systems, Vol. 2, John Wiley,
New York, 1976.
[Kleinrock 1998] L. Kleinrock, "The Birth of the Internet,"
http://www.lk.cs.ucla.edu/LK/Inet/birth.html
[Leiner 1998] B. Leiner, V. Cerf, D. Clark, R. Kahn, L. Kleinrock, D.
Lynch, J. Postel, L. Roberts, and S. Woolf, "A Brief History of the
Internet," http://www.isoc.org/internet/history/brief.html
[List 1999] "The List: The Definitive ISP Buyer's Guide,"
http://thelist.internet.com/

[Lucky 1997] R. Lucky, "New Communication Services -

What Do People Want?", Proceedings of the IEEE, Oct.
1997, pp 1536-1543.
[Metcalfe 1976] R. M. Metcalfe and D. R. Boggs. "Ethernet:
Distributed Packet Switching for Local Computer Networks,"
Communications of the Association for Computing Machinery,
Vol. 19, No. 7, (July 1976), pp. 395 - 404.
http://www.acm.org/classics/apr96/
[Mills 1998] S. Mills, "TV set-tops set to take off," CNET
News.com, Oct. 1998. http://news.cnet.com/news/0-1006-
200-334433.html
[NAS 1995] National Academy of Sciences, The
Unpredictable Certainty: Information Infrastructure
Through 2000, National Academy of Sciences Press, 1995.
http://www.nap.edu/readingroom/books/unpredictable/chap
4.html

[Network 1996] Network Wizards, "Internet Domain

Survey", July 1996, http://www.nw.com/zone/WWW-
9607/report.html
[Network 1999] Network Wizards, "Internet Domain
Survey," Jan. 1999, http://www.isc.org/ds/
[Pacific Bell 1998] Pacific Bell, "ISDN Users Guide,"
http://www.pacbell.com/Products_Services/Residential/ISD
Nuserguide/0,1078,20,00.html
[Perkins 1994] A. Perkins, "Networking with Bob Metcalfe,"
The Red Herring Magazine, Nov. 1994.
http://www.herring.com/mag/issue15/bob.html
[Quittner 1998] J. Quittner, M. Slatalla, Speeding the Net:
The Inside Story of Netscape and How it Challenged
Microsoft, Atlantic Monthly Press, 1998.

[Ramaswami 1998] R. Ramaswami, K. Sivarajan, Optical Networks:

A Practical Perspective, Morgan Kaufman Publishers, 1998
[RFC 001] S. Crocker, "Host Software," RFC 001 (the very first
RFC!).
[RFC 793] J. Postel, "Transmission Control Protocol," RFC 793,
Sept. 1981. http://www.rfc-editor.org/rfc/rfc793.txt
[RFC 801] J. Postel, "NCP/TCP Transition Plan," RFC 801 Nov. 1981.
http://www.rfc-editor.org/rfc/rfc801.txt
[RFC 1034] P. V. Mockapetris, "Domain Names--Concepts and
Facilities," RFC 1034, Nov. 1987. http://www.rfc-
editor.org/rfc/rfc1034.txt
[Roberts 1967] L. Roberts, T. Merril, "Toward a Cooperative
Network of Time-Shared Computers," AFIPS Fall Conference, Oct.
1966.
[Ross 1995] K. W. Ross, Multiservice Loss Models for Broadband
Telecommunication Networks, Springer, Berlin, 1995.
[Segaller 1998] S. Segaller, Nerds 2.0.1, A Brief History of the
Internet, TV Books, New York, 1998.

[Thinplanet 2000] Thinplanet homepage,

http://www.thinplanet.com/
[Turner 1986] J. Turner, "New Directions in Communications
(or Which Way to the Information Age?)," Proceedings of
the Zürich Seminar on Digital Communication, (Zurich,
Switzerland, Mar. 1986), pp. 25-32,.
[W3C 1995] The World Wide Web Consortium, "A Little
History of the World Wide Web," 1995.
http://www.w3.org/History.html
[Wakeman 1992] Ian Wakeman, Jon Crowcroft, Zheng
Wang, and Dejan Sirovica, "Layering Considered Harmful,"
IEEE Network, Jan. 1992, p. 20-24.

[Waung 1998] W. Waung, "Wireless Mobile Data

Networking The CDPD Approach," Wireless Data Forum,
1998.
http://www2.wirelessdata.org/public/whatis/whatis.html
[Wireless 1998] Wireless Data Forum, "CDPD System
Specification Release 1.1," 1998.
http://www2.wirelessdata.org/public/specification/index.ht
ml
[Wood 1999] L. Wood, "Lloyds Satellites Constellations,"
http://www.ee.surrey.ac.uk/Personal/L.Wood/constellations/
iridium.html
[Ziff-Davis 1998] Ziff-Davis Publishing, "Ted Nelson:
Hypertext pioneer," 1998.
http://www.zdnet.com/zdtv/screensavers_story/0,3656,212
7396-2102293,00.html© 2000-2001 by Addison Wesley
Longman
A division of Pearson Education.

Home Work-
Work- Chapters1
Computer Networking ‫ ز از اول ب‬

. ‫ را‬3edition
16 - 15 - 14 - 6 - 5 - 3 - 2
., jamali@iust.ac.ir ‫ "درس‬#$ ‫درا‬%& '()*+

Subject: HW1,”Name; Student ID Number”

CN Chp1 (Compatibility Mode)

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CN Chp1 (Compatibility Mode)

Hochgeladen von

Copyright:

Verfügbare Formate

Computer Networks

1.0 Why Networking

Platform Services Application Agent

Application Software (Client Part) Application Software (Server Part)

Application Program Interface (API) Application Program Interface (API)

Networking Software & Hardware Networking Software & Hardware

Client Agents Examples:

Application Process Application Process

Application Program Interface (API) Application Program Interface (API)

Networking Software & Hardware Networking Software & Hardware

Server Agents Examples:

Presentation: The client agent remains focused on

Business Rules (Application Logic)

Data (Database Access)

user Application Sever

Jamali@iust.ac.ir Orientation 1-10

Jamali@iust.ac.ir Orientation 1-11

1.0 Why Networking

Jamali@iust.ac.ir Orientation 1-12

modem Telephone LAN Switch

modem External Link

Jamali@iust.ac.ir Orientation 1-13

router local ISP regional ISP

Jamali@iust.ac.ir Orientation 1-14

millions of connected computing devices:

Jamali@iust.ac.ir Orientation 1-15

protocols control sending, receiving of

Jamali@iust.ac.ir Orientation 1-16

Jamali@iust.ac.ir Orientation 1-17

Intranet: access is denied from outside

Jamali@iust.ac.ir Orientation 1-18

Extranet: an internet of networks

Jamali@iust.ac.ir Orientation 1-19

Jamali@iust.ac.ir Orientation 1-20

ICANN coordinates the assignment of

Jamali@iust.ac.ir Orientation 1-21

(a) NSI Herndon, VA

(m) WIDE Tokyo, Japan

(e) NASA Mt View, CA

(b) USC-ISI Marina del Rey, CA

Jamali@iust.ac.ir Orientation 1-22

Jamali@iust.ac.ir Orientation 1-23

1.0 Why Networking

Jamali@iust.ac.ir Orientation 1-24

network edge: local ISP

Jamali@iust.ac.ir Orientation 1-25

end systems (hosts):

client host requests, receives

Jamali@iust.ac.ir Orientation 1-26

Jamali@iust.ac.ir Orientation 1-27

Jamali@iust.ac.ir Orientation 1-28

Goal: data transfer TCP service [RFC 793]

Jamali@iust.ac.ir Orientation 1-29

Goal: data transfer App’s using TCP:

Jamali@iust.ac.ir Orientation 1-30

1.0 Why Networking

Jamali@iust.ac.ir Orientation 1-31

transferred through net?

Jamali@iust.ac.ir Orientation 1-32

End-end resources local ISP

link bandwidth, switch modem

Jamali@iust.ac.ir Orientation 1-33