BITS ZC481 Computer Networks

Vikas Singh

Lecture no. 1

Introduction, History and Development of Computer Networks, Concept of Layered Architecture (e.g. OSI Model and TCP/IP Model), Application Layer: Basic Communication Applications and Protocols, Transport Layer: Services and Protocols, Reliable Protocol Design Concepts, Network Layer: Services, Routing Algorithms and Protocols, Inter domain and Intra domain Routing, Multicasting, IP Addressing, Concept of Sub Networks, Link Layer: Services, Channel Access Protocols, Link layer Addressing, Interconnection devices (e.g. Hub, Bridge, Switch, Routers), ATM and MPLS networks, Concept of LAN, LAN Implementations, Physical Layer: Physical Media, Data Communication Basics, Line Encoding Techniques
We will closely follow the top down approach to computer networking as given in the textbook, which will enable you to understand the most visible part i.e. the applications, and then seeing, progressively, how each layer is supported by the next layer down. Most of the time, our example network will be Internet. Also, some time examples will be from wireless and mobile networks will be covered as currently users access the Internet from offices, from homes, while on move, and from public places wirelessly

Prescribed Text Book

Kurose James F and Keith W. Ross: Computer Networking: A Top-Down Approach Featuring the Internet, Pearson Education, 3rd Edition, 2005.

Reference Books
Andrew S. Tanenbaum, Computer Networks, Fourth Edition, Pearson Education, 2006. William Stallings, Computer Networking with Internet Protocols and Technology, Pearson Education, 2004. L. Peterson and B. Davie, Computer Networks: A Systems Approach, Fourth Edition, Elsevier, 2007 (Book From 24x7 Online Book)

Overview
whats the Internet whats a protocol? network edge network core access net, physical media Internet/ISP structure performance: loss, delay protocol layers, service models history

router

millions of connected computing devices: hosts, endsystems

PCs workstations, servers PDAs phones, toasters running network apps

workstation mobile

server

local ISP

communication links
fiber, copper, radio, satellite transmission rate = bandwidth

regional ISP

routers: forward packets (chunks of data)

company network

communication infrastructure enables distributed applications:

Web, email, games, ecommerce, database., voting, file (MP3) sharing

communication services provided to apps:

connectionless Connection-oriented Currently, no gurantees about performance (Best Effort).

protocols control sending, receiving of msgs

e.g., TCP, IP, HTTP, FTP, PPP

Internet: network of networks

loosely hierarchical public Internet versus private intranet

Internet standards
RFC: Request for comments IETF: Internet Engineering Task Force

A human protocol and a computer network protocol:

Hi Hi

TCP connection req TCP connection response

Get http://www.awl.com/kurose-ross

Got the time?

2:00 Time

<file>

All activity in the Internet that involves two or more communicating remote entities is governed by a protocol. (Routing protocols, Congestion Control protocols, media access protocols, etc.)

network edge: applications and hosts network core:

routers network of networks

access networks, physical media: communication links

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. Gnutella, KaZaA

Goal: data transfer between end

systems handshaking: setup (prepare for) data transfer ahead of time
Exchange control packets set up state in two communicating hosts (e.g. Sequence number of next packet)

TCP service [RFC 793]

reliable, in-order bytestream data transfer
loss: acknowledgements, time-outs and, retransmissions

flow control:
sender wont overwhelm receiver (receiver may be slower/busier than sender)

TCP - Transmission Control Protocol

Internets connectionoriented service

congestion control:
senders slow down sending rate when network congested

Goal: data transfer between end

systems
same as before!

Apps using TCP:

HTTP (Web), FTP (file transfer), Telnet (remote login), SMTP (email)

Connection-less:

No hand shaking.
UDP - User Datagram Protocol [RFC 768]: Internets connectionless service

Apps using UDP:

streaming media, teleconferencing, DNS, Internet telephony

unreliable data transfer no flow control no congestion control

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

End-end resources reserved for call

link bandwidth, switch capacity dedicated resources: no sharing circuit-like (guaranteed) performance call setup required
dividing link bandwidth into pieces

frequency division

time division

Example:
FDMA 4 users

frequency

time TDMA

frequency

time

each end-end data stream divided into packets Different users' packets share network resources each packet uses full link bandwidth resources used as needed

resource contention:
aggregate resource demand

can exceed amount available

for link use

congestion: packets queue, wait store and forward: packets

move one hop at a time transmit over link

wait turn at next link

Bandwidth division into pieces Dedicated allocation Resource reservation