APPLICATION LAYER

Distributed, Hierarchical Database

Root DNS Servers

com DNS servers yahoo.com amazon.com DNS servers DNS servers

org DNS servers pbs.org DNS servers

edu DNS servers poly.edu umass.edu DNS serversDNS servers

Client wants IP for www.amazon.com; 1st approx: client queries a root server to find com DNS server client queries com DNS server to get amazon.com DNS server client queries amazon.com DNS server to get IP address for www.amazon.com
Adapted from Computer Networking JFK & KWR 3

TLD and Authoritative Servers

Top-level domain (TLD) servers:
responsible for com, org, net, edu, etc, and all top-level country domains uk, fr, ca, jp. Network Solutions maintains servers for com TLD Educause for edu TLD

Authoritative DNS servers:

organizations DNS servers, providing authoritative hostname to IP mappings for organizations servers (e.g., Web, mail). can be maintained by organization or service provider
Adapted from Computer Networking JFK & KWR 4

Local Name Server

does not strictly belong to hierarchy each ISP (residential ISP, company, university) has one.
also called default name server

when host makes DNS query, query is sent to its local DNS server
acts as proxy, forwards query into hierarchy
Adapted from Computer Networking JFK & KWR 5

DNS name resolution example

Host at cis.poly.edu wants IP address for gaia.cs.umass.edu
iterated query: 2

root DNS server

3 4 5 local DNS server

dns.poly.edu

TLD DNS server

contacted server replies with name of server to contact I dont know this name, but ask this server

requesting host
cis.poly.edu

authoritative DNS server dns.cs.umass.edu

gaia.cs.umass.edu
Adapted from Computer Networking JFK & KWR 6

DNS name resolution example

recursive query:

root DNS server

puts burden of name resolution on contacted name server heavy load?

2 7 6

3 TLD DNS server

local DNS server

dns.poly.edu

8
authoritative DNS server dns.cs.umass.edu

requesting host
cis.poly.edu

gaia.cs.umass.edu
Adapted from Computer Networking JFK & KWR 7

DNS: caching and updating records

once (any) name server learns mapping, it caches mapping cache entries timeout (disappear) after some time TLD servers typically cached in local name servers
Thus root name servers not often visited

update/notify mechanisms under design by IETF

RFC 2136
http://www.ietf.org/html.charters/dnsind-charter.html

Adapted from Computer Networking JFK & KWR

Pure P2P architecture

no always-on server arbitrary end systems directly communicate peer-peer peers are intermittently connected and change IP addresses

Adapted from Computer Networking JFK & KWR

Homework Due Next Class

Read about nslookup command. Check and understand the outputs?

Adapted from Computer Networking JFK & KWR

10

File Distribution: Server-Client vs P2P

Question : How much time to distribute file from one server to N peers?
Server u1 d1 u2

us: server upload bandwidth ui: peer i upload bandwidth

d2

File, size F dN uN

us

di: peer i download bandwidth

Network (with abundant bandwidth)

Adapted from Computer Networking JFK & KWR

11

Server-client vs. P2P: example

3.5

Minimum Distribution Time

3 2.5 2 1.5 1 0.5 0 0

P2P Client-Server

10

15

20

25

30

35

Chapter 2: Summary
our study of network apps now complete!
application architectures
client-server P2P hybrid
specific protocols:

application service requirements:

HTTP FTP SMTP, POP, IMAP DNS

Internet transport service model

connection-oriented, reliable: TCP unreliable, datagrams: UDP

reliability, bandwidth, delay

2: Application Layer

13

Chapter 2: Summary
Most importantly: learned about protocols
typical request/reply message exchange:
client requests info or service server responds with data, status code
Important themes: control vs. data msgs in-band, out-of-band centralized vs. decentralized stateless vs. stateful reliable vs. unreliable msg transfer complexity at network edge

2: Application Layer

14

Moving down the protocol stack

Email FTP WWW

TCP

UDP

Transport Layer

IP

Ethernet ireless W

15

Chapter 3: Transport Layer

Our goals: understand principles behind transport layer services:
multiplexing/demultiplexing reliable data transfer flow control congestion control

learn about transport layer protocols in the Internet:

UDP: connectionless transport TCP: connection-oriented transport TCP congestion control

Adapted from Computer Networking JFK & KWR

16

Chapter 3 outline
3.1 Transport-layer services 3.5 Connection-oriented transport: TCP 3.2 Multiplexing and segment structure demultiplexing reliable data transfer 3.3 Connectionless flow control transport: UDP connection management 3.4 Principles of reliable 3.6 Principles of data transfer congestion control 3.7 TCP congestion control

Adapted from Computer Networking JFK & KWR

17

Transport services and protocols

provide logical communication between app processes running on different hosts transport protocols run in end systems send side: breaks app messages into segments, passes to network layer rcv side: reassembles segments into messages, passes to app layer more than one transport protocol available to apps Internet: TCP and UDP
application transport network data link physical

application transport network data link physical

Adapted from Computer Networking JFK & KWR

18

Internet transport-layer protocols

reliable, in-order delivery (TCP)
congestion control flow control connection setup
application transport network data link physical network data link physical network data link physical

unreliable, unordered delivery: UDP

no-frills extension of besteffort IP

network data link physical network network data link physical

data link physical application transport network data link physical

services not available:

delay guarantees bandwidth guarantees
Adapted from Computer Networking JFK & KWR

network data link physical

19