Beruflich Dokumente
Kultur Dokumente
Chapter 1:Introduction
Computer Networking: A Top Down Approach ,
4th edition. Jim Kurose, Keith Ross
Chapter 1: Introduction
Our goal:
get feel and
Overview:
whats the Internet? whats a protocol? network edge; hosts, access
terminology more depth, detail later in course approach: use Internet as example
net, physical media network core: packet/circuit switching, Internet structure performance: loss, delay, throughput Protocol layers, service models History of Internet
Throughput
The rate (bits/sec) at which bits are transferred
between sender/receiver Difference between Bandwidth and Throughput? ISPs sell bandwidth In computer networks, the throughput is less than the bandwidth for several reasons The channel may be shared by other users Packet loss due to congestion Packet loss due to bit errors Noise in the channel Transmission rates of the link over which the data flows.
Throughput
Rs
Rs
B packets queueing (delay) free (available) buffers: arriving packets dropped (loss) if no free buffers
Time waiting at output link for transmission depends on congestion level of router If queue empty no delay Microseconds to milliseconds
propagation
B processing
queueing
4. Propagation Delay: Time to propagate from the beginning of the link to the other router (node) propagation delay = d/s d = length of physical link s = propagation speed in medium (~3x108 m/sec)
propagation B
nodal processing
queueing
Queuing Delay
When is Queuing Delay large and
when it is insignificant?
L=packet length(bits)
rate(packets/sec) Traffic Intensity = (Average rate at which bits arrive at the queue) =La Transmission Rate R La/R ~ 0: average queuing delay small La/R -> 1: delays become large (queue begins to get larger) La/R > 1: average rate at which bits arrive at the queue exceeds the rate at which the bits can be transmitted from the queue. more work arriving than can be serviced Packet Loss will occur
Queuing Delay
Consider the case La/R1 Nature of arriving traffic impacts queuing delay in such a case
In reality the arrival process to a queue is random and arrivals do not follow any pattern.
(Find about Queuing Theory?)
Protocol Layers
Networks are complex! many pieces: hosts routers links of various media applications protocols hardware, software
Question:
Is there any way of organizing network architecture?
Answer:
Why layering?
Dealing with complex systems: Discuss a well defined, specific part of a large and complex system Modularization eases maintenance, updating of system Change of implementation of layers service transparent to rest of system e.g. change in gate procedure doesnt affect rest of system
FTP, HTTP
Application Transport
Network
Link Physical
Standardization proposed a seven layered model called Open Systems Interconnection (OSI) model. Presentation Layer: Provide services such as data encryption, compression. Session Layer: Synchronization points (checkpointing) and recovery of data exchange. Internet stack missing these layers! these services, if needed, must be implemented in the application by the application developer.
source
message segment
Ht M M M M
frame Hl Hn Ht
datagram Hn Ht
Encapsulation
destination
M
Ht
Hn Ht Hl Hn Ht
M M M
Hn Ht Hl Hn Ht
M
M
Hn Ht
router
network applications 2.2 Web and HTTP 2.3 FTP 2.4 Electronic Mail
2.5 DNS
programming network
Web
Instant messaging Remote login P2P file sharing Multi-user network games Streaming stored video clips Voice over IP Real-time video conferencing Many more interesting applications
Application Architectures
Application Architecture is
Designed
by the application developer Dictates how the application is structured over various end systems
Two architectures used in modern day
Network Applications:
Client-Server
Client-Server Architecture
Server: Always-on host permanent well defined IP address A single server is incapable of keeping up with all the requests of the clients. A cluster of hosts referred as server farm is often used. Clients: Communicate with server May have dynamic IP addresses Do not communicate directly with each other Client/Server architecture is infrastructure intensive Require service providers to install and maintain servers.
Client/Server
P2P Architecture
Direct communication
between pairs of intermittently connected hosts called peers Peers are not owned by any peer-peer service provider P2P
Highly Distributive
chapter
Some apps (e.g., audio, VoIP) can tolerate some loss 2% tolerable for VoIP
email) require 100% reliable data transfer Timing Application may require timing guarantee Tight timing constraints
multiplayer games, VoIP, teleconferencing. In Non-real time lower delays are preferred but no tight constraint on end-to-end delays.
Throughput Bandwidth sensitive applications (e.g., multimedia) require minimum amount of throughput Other apps (elastic apps) make use of whatever throughput they get e.g .Email, file transfer Security Encryption and decryption
elastic elastic elastic audio: 5kbps-1Mbps video:10kbps-5Mbps same as above few kbps -10kbps