Chapter 2

Application Layer

A note on the use of these ppt slides:

Were making these slides freely available to all (faculty, students, readers).
Theyre in PowerPoint form so you can add, modify, and delete slides
(including this one) and slide content to suit your needs. They obviously
Computer Networking:
represent a lot of work on our part. In return for use, we only ask the A Top Down Approach,
following:
If you use these slides (e.g., in a class) in substantially unaltered form,
4th edition.
that you mention their source (after all, wed like people to use our book!) Jim Kurose, Keith Ross
If you post any slides in substantially unaltered form on a www site, that
Addison-Wesley, July

al
you note that they are adapted from (or perhaps identical to) our slides, and
note our copyright of this material. 2007.

ep
Thanks and enjoy! JFK/KWR

itn
All material copyright 1996-2007
J.F Kurose and K.W. Ross, All Rights Reserved

cs
2: Application Layer 1
Chapter 2: Application layer
2.1 Principles of 2.6 P2P applications
network applications 2.7 Socket programming
2.2 Web and HTTP with TCP
2.3 FTP 2.8 Socket programming
2.4 Electronic Mail with UDP
SMTP, POP3, IMAP
2.5 DNS

al
ep
itn
cs
2: Application Layer 2
Chapter 2: Application Layer
Our goals: learn about protocols
conceptual, by examining popular
implementation application-level
aspects of network protocols
application protocols HTTP
transport-layer FTP
service models SMTP / POP3 / IMAP
DNS
client-server

paradigm programming network

peer-to-peer
applications

al
paradigm socket API

ep
itn
cs
2: Application Layer 3
Some network apps
e-mail voice over IP
web real-time video
instant messaging conferencing
remote login grid computing

P2P file sharing

multi-user network
games
streaming stored video
clips

al
ep
itn
cs
2: Application Layer 4
Creating a network app application
transport
network
data link

write programs that physical

run on (different) end

systems
communicate over network
e.g., web server software
communicates with browser
software application

No need to write software

transport
network
data link
for network-core devices
application
physical
transport
network
Network-core devices do data link
physical
not run user applications

al
applications on end systems

ep
allows for rapid app
development, propagation

itn
cs
2: Application Layer 5
Chapter 2: Application layer
2.1 Principles of 2.6 P2P applications
network applications 2.7 Socket programming
2.2 Web and HTTP with TCP
2.3 FTP 2.8 Socket programming
2.4 Electronic Mail with UDP
SMTP, POP3, IMAP 2.9 Building a Web
2.5 DNS server

al
ep
itn
cs
2: Application Layer 6
Application architectures
Client-server
Peer-to-peer (P2P)
Hybrid of client-server and P2P

al
ep
itn
cs
2: Application Layer 7
Client-server architecture
server:
always-on host
permanent IP address
server farms for
scaling
clients:
client/server communicate with server
may be intermittently
connected
may have dynamic IP

al
addresses

ep
do not communicate

itn
directly with each other

cs
2: Application Layer 8
Pure P2P architecture
no always-on server
arbitrary end systems
directly communicate peer-peer
peers are intermittently
connected and change IP
addresses

Highly scalable but

al
difficult to manage

ep
itn
cs
2: Application Layer 9
Hybrid of client-server and P2P
Skype
voice-over-IP P2P application
centralized server: finding address of remote
party:
client-client connection: direct (not through
server)
Instant messaging
chatting between two users is P2P
centralized service: client presence
detection/location
user registers its IP address with central
server when it comes online

al
user contacts central server to find IP

ep
addresses of buddies

itn
cs
2: Application Layer 10
Processes communicating
Process: program running Client process: process
within a host. that initiates
within same host, two
communication
processes communicate Server process: process
using inter-process that waits to be
communication (defined contacted
by OS).
processes in different Note: applications with
hosts communicate by P2P architectures have
exchanging messages client processes &

al
server processes

ep
itn
cs
2: Application Layer 11
 Sockets
host or host or
process sends/receives server server
messages to/from its
socket controlled by
app developer
socket analogous to door process process

sending process shoves socket socket

message out door TCP with TCP with
buffers, Internet buffers,
sending process relies on variables variables
transport infrastructure
on other side of door which
controlled
brings message to socket by OS
at receiving process

al
ep
API: (1) choice of transport protocol; (2) ability to fix
a few parameters (lots more on this later)

itn
cs
2: Application Layer 12
Addressing processes
to receive messages,
process must have
identifier
host device has unique
32-bit IP address
Q: does IP address of
host suffice for
identifying the process?

al
ep
itn
cs
2: Application Layer 13
Addressing processes
to receive messages, identifier includes both
process must have IP address and port
identifier numbers associated with
host device has unique process on host.
32-bit IP address Example port numbers:
Q: does IP address of HTTP server: 80
host on which process Mail server: 25
runs suffice for to send HTTP message
identifying the to gaia.cs.umass.edu web
process? server:
A: No, many IP address: 128.119.245.12

al

processes can be Port number: 80

ep

running on same host more shortly

itn

cs
2: Application Layer 14
App-layer protocol defines
Types of messages Public-domain protocols:
exchanged, defined in RFCs
e.g., request, response allows for
Message syntax: interoperability
what fields in messages & e.g., HTTP, SMTP
how fields are delineated
Proprietary protocols:
Message semantics
meaning of information in e.g., Skype
fields
Rules for when and how

al
processes send &

ep
respond to messages

itn
cs
2: Application Layer 15
 What transport service does an app need?
Data loss
some apps (e.g., audio) can
tolerate some loss
other apps (e.g., file
transfer, telnet) require
100% reliable data
transfer
Timing
some apps (e.g.,
Internet telephony,
interactive games)
require low delay to be
Throughput
some apps (e.g.,
multimedia) require
minimum amount of
throughput to be
effective
other apps (elastic apps)
make use of whatever
throughput they get
Security
Encryption, data

al
effective integrity,

ep
itn
cs
2: Application Layer 16
 Transport service requirements of common apps

Application Data loss Throughput Time Sensitive

file transfer no loss elastic no

e-mail no loss elastic no
Web documents no loss elastic no
real-time audio/video loss-tolerant audio: 5kbps-1Mbps yes, 100s msec
video:10kbps-5Mbps
stored audio/video loss-tolerant same as above yes, few secs
interactive games loss-tolerant few kbps up yes, 100s msec
instant messaging no loss elastic yes and no

al
ep
itn
cs
2: Application Layer 17
Internet transport protocols services
TCP service:
connection-oriented: setup
required between client and
server processes
reliable transport between
sending and receiving process
flow control: sender wont
overwhelm receiver
congestion control: throttle
sender when network
overloaded
does not provide: timing,
minimum throughput
guarantees, security
UDP service:
unreliable data transfer
between sending and
receiving process
does not provide:
connection setup,
reliability, flow control,
congestion control, timing,
throughput guarantee, or
security
al
Q: why bother? Why is
ep
there a UDP?
itn
cs
2: Application Layer 18
Internet apps: application, transport protocols

Application Underlying
Application layer protocol transport protocol

e-mail SMTP [RFC 2821] TCP

remote terminal access Telnet [RFC 854] TCP
Web HTTP [RFC 2616] TCP
file transfer FTP [RFC 959] TCP
streaming multimedia HTTP (eg Youtube), TCP or UDP
RTP [RFC 1889]
Internet telephony SIP, RTP, proprietary
(e.g., Skype) typically UDP

al
ep
itn
cs
2: Application Layer 19
Chapter 2: Application layer
2.1 Principles of 2.6 P2P applications
network applications 2.7 Socket programming
app architectures with TCP
app requirements
2.8 Socket programming

2.2 Web and HTTP with UDP

2.4 Electronic Mail
SMTP, POP3, IMAP
2.5 DNS

al
ep
itn
cs
2: Application Layer 20
Web and HTTP
First some jargon
Web page consists of objects
Object can be HTML file, JPEG image, Java
applet, audio file,
Web page consists of base HTML-file which
includes several referenced objects
Each object is addressable by a URL
Example URL:
www.someschool.edu/someDept/pic.gif

al
ep
host name path name

itn
cs
2: Application Layer 21
HTTP overview

HTTP: hypertext
transfer protocol HT
TP
r
equ
Webs application layer PC running HT est
TP
protocol Explorer res
pon
se
client/server model
client: browser that st
q ue
requests, receives, P re se Server
T o n
displays Web objects HT r esp running
TP Apache Web
server: Web server H T
server
sends objects in
response to requests

al
Mac running
Navigator

ep
itn
cs
2: Application Layer 22
HTTP overview (continued)
Uses TCP:
client initiates TCP
connection (creates socket)
to server, port 80
server accepts TCP
connection from client
Protocols that maintain
HTTP messages (application-
layer protocol messages)
exchanged between browser
(HTTP client) and Web
server (HTTP server)
TCP connection closed
HTTP is stateless
server maintains no
information about
past client requests
aside
state are complex!
past history (state) must
be maintained
if server/client crashes,
their views of state may
al
be inconsistent, must be
ep
reconciled
itn
cs
2: Application Layer 23
HTTP connections
Nonpersistent HTTP Persistent HTTP
At most one object is Multiple objects can
sent over a TCP be sent over single
connection. TCP connection
between client and
server.

al
ep
itn
cs
2: Application Layer 24
 Nonpersistent HTTP
Suppose user enters URL
www.someSchool.edu/someDepartment/home.index
1a. HTTP client initiates TCP
connection to HTTP server
(process) at
www.someSchool.edu on port 80
2. HTTP client sends HTTP
request message (containing
URL) into TCP connection
socket. Message indicates
that client wants object
someDepartment/home.index
time
(contains text,
references to 10
jpeg images)
1b. HTTP server at host
www.someSchool.edu waiting
for TCP connection at port 80.
accepts connection, notifying
client
3. HTTP server receives request
message, forms response
message containing requested
al
object, and sends message
ep
into its socket
itn
cs
2: Application Layer 25
 Nonpersistent HTTP (cont.)

4. HTTP server closes TCP

connection.
5. HTTP client receives response
message containing html file,
displays html. Parsing html
file, finds 10 referenced jpeg
objects
time 6. Steps 1-5 repeated for each
of 10 jpeg objects

al
ep
itn
cs
2: Application Layer 26
Non-Persistent HTTP: Response time
Definition of RTT: time for
a small packet to travel
from client to server
and back. initiate TCP
connection
Response time: RTT
one RTT to initiate TCP request
file
connection time to
RTT
transmit
one RTT for HTTP file
request and first few file
received
bytes of HTTP response
to return

al
time time

ep
file transmission time

itn
total = 2RTT+transmit time

cs
2: Application Layer 27
Persistent HTTP
Nonpersistent HTTP issues:
requires 2 RTTs per object
OS overhead for each TCP
connection
browsers often open parallel
TCP connections to fetch
referenced objects
Persistent HTTP
server leaves connection
open after sending
response
subsequent HTTP messages
between same
client/server sent over
open connection
client sends requests as
soon as it encounters a
referenced object
as little as one RTT for all
al
the referenced objects
ep
itn
cs
2: Application Layer 28
 HTTP request message

two types of HTTP messages: request, response

HTTP request message:
ASCII (human-readable format)

request line
(GET, POST, GET /somedir/page.html HTTP/1.1
HEAD commands) Host: www.someschool.edu
User-agent: Mozilla/4.0
header Connection: close
lines Accept-language:fr

al
Carriage return,
(extra carriage return, line feed)

ep
line feed
indicates end

itn
of message

cs
2: Application Layer 29
HTTP request message: general format

al
ep
itn
cs
2: Application Layer 30
Uploading form input
Post method:
Web page often
includes form input URL method:
Input is uploaded to Uses GET method
server in entity body Input is uploaded in
URL field of request
line:

www.somesite.com/animalsearch?monkeys&banana

al
ep
itn
cs
2: Application Layer 31
Method types
HTTP/1.0 HTTP/1.1
GET GET, POST, HEAD
POST PUT
HEAD uploads file in entity
body to path specified
asks server to leave
in URL field
requested object out of
response DELETE
deletes file specified in
the URL field

al
ep
itn
cs
2: Application Layer 32
HTTP response message
status line
(protocol
status code HTTP/1.1 200 OK
status phrase) Connection close
Date: Thu, 06 Aug 1998 12:00:15 GMT
Server: Apache/1.3.0 (Unix)
header
Last-Modified: Mon, 22 Jun 1998 ...
lines
Content-Length: 6821
Content-Type: text/html

data, e.g., data data data data data ...

requested
HTML file

al
ep
itn
cs
2: Application Layer 33
HTTP response status codes
In first line in server->client response message.
A few sample codes:
200 OK
request succeeded, requested object later in this message
301 Moved Permanently
requested object moved, new location specified later in
this message (Location:)
400 Bad Request
request message not understood by server
404 Not Found

al
requested document not found on this server

ep

505 HTTP Version Not Supported

itn
cs
2: Application Layer 34
 Trying out HTTP (client side) for yourself

1. Telnet to your favorite Web server:

telnet cis.poly.edu 80 Opens TCP connection to port 80
(default HTTP server port) at cis.poly.edu.
Anything typed in sent
to port 80 at cis.poly.edu

2. Type in a GET HTTP request:

GET /~ross/ HTTP/1.1 By typing this in (hit carriage
Host: cis.poly.edu return twice), you send
this minimal (but complete)
GET request to HTTP server

al
3. Look at response message sent by HTTP server!

ep
itn
cs
2: Application Layer 35
User-server state: cookies
Example:
Many major Web sites
use cookies Susan always access
Four components: Internet always from PC
1) cookie header line of visits specific e-
HTTP response message commerce site for first
2) cookie header line in time
HTTP request message
3) cookie file kept on when initial HTTP
users host, managed by requests arrives at site,
users browser site creates:
4) back-end database at
Web site unique ID

al
entry in backend

ep
database for ID

itn
cs
2: Application Layer 36
 Cookies: keeping state (cont.)
client server
ebay 8734
usual http request msg
Amazon server
cookie file usual http response creates ID
Set-cookie: 1678 1678 for user create
ebay 8734 entry
amazon 1678
usual http request msg
cookie: 1678 cookie- access
specific
one week later: usual http response msg action backend
database
access
ebay 8734 usual http request msg

al
amazon 1678 cookie: 1678 cookie-

ep
spectific
usual http response msg action

itn
cs
2: Application Layer 37
Cookies (continued)
aside
What cookies can bring: Cookies and privacy:
authorization cookies permit sites to
shopping carts
learn a lot about you
you may supply name
recommendations
and e-mail to sites
user session state
(Web e-mail)
How to keep state:
protocol endpoints: maintain state
at sender/receiver over multiple

al
transactions

ep
cookies: http messages carry state

itn
cs
2: Application Layer 38
 Web caches (proxy server)
Goal: satisfy client request without involving origin server

user sets browser: origin

server
Web accesses via
cache HT Proxy
TP e st
browser sends all req server req
u
H u P
client TTP e st H TT po nse
HTTP requests to res
pon P res
se H TT
cache ue st
eq
object in cache: cache T P r
o nse
HT r esp
returns object TP
H T
else cache requests

al
object from origin client
origin

ep
server, then returns server
object to client

itn
cs
2: Application Layer 39
More about Web caching
cache acts as both Why Web caching?
client and server reduce response time
typically cache is for client request
installed by ISP reduce traffic on an
(university, company, institutions access
residential ISP) link.
Internet dense with
caches: enables poor
content providers to
effectively deliver

al
content (but so does

ep
P2P file sharing)

itn
cs
2: Application Layer 40
Caching example
origin
Assumptions servers
average object size = 100,000
public
bits Internet
avg. request rate from
institutions browsers to origin
servers = 15/sec
1.5 Mbps
delay from institutional router access link
to any origin server and back
institutional
to router = 2 sec network
10 Mbps LAN
Consequences
utilization on LAN = 15%

al
utilization on access link = 100%
institutional

ep
total delay = Internet delay +
cache
access delay + LAN delay

itn
= 2 sec + minutes + milliseconds

cs
2: Application Layer 41
Caching example (cont)
origin
possible solution servers
increase bandwidth of access
public
link to, say, 10 Mbps Internet
consequence
utilization on LAN = 15%
utilization on access link = 15% 10 Mbps
Total delay = Internet delay + access link
access delay + LAN delay institutional
= 2 sec + msecs + msecs network
10 Mbps LAN
often a costly upgrade

al
institutional

ep
cache

itn
cs
2: Application Layer 42
Caching example (cont)
origin
possible solution: install servers
cache public
suppose hit rate is 0.4 Internet
consequence
40% requests will be
satisfied almost immediately
1.5 Mbps
60% requests satisfied by access link
origin server
utilization of access link institutional
reduced to 60%, resulting in network
10 Mbps LAN
negligible delays (say 10
msec)
total avg delay = Internet

al
delay + access delay + LAN institutional

ep
delay = .6*(2.01) secs +
cache
.4*milliseconds < 1.4 secs

itn
cs
2: Application Layer 43
 Conditional GET

Goal: dont send object if cache server

cache has up-to-date cached HTTP request msg
version If-modified-since:
object
cache: specify date of <date>
not
cached copy in HTTP request modified
If-modified-since: HTTP response
HTTP/1.0
<date> 304 Not Modified
server: response contains no
object if cached copy is up-
HTTP request msg
to-date: If-modified-since:
HTTP/1.0 304 Not <date> object
Modified modified

al
HTTP response

ep
HTTP/1.0 200 OK

itn
<data>

cs
2: Application Layer 44
Chapter 2: Application layer
2.1 Principles of 2.6 P2P applications
network applications 2.7 Socket programming
2.2 Web and HTTP with TCP
2.3 FTP 2.8 Socket programming
2.4 Electronic Mail with UDP
SMTP, POP3, IMAP 2.9 Building a Web
2.5 DNS server

al
ep
itn
cs
2: Application Layer 45
FTP: the file transfer protocol

FTP file transfer

FTP FTP
user client server
interface
user
at host remote file
local file system
system

transfer file to/from remote host

client/server model
client: side that initiates transfer (either to/from
remote)
server: remote host

al
ftp: RFC 959

ep
ftp server: port 21

itn
cs
2: Application Layer 46
FTP: separate control, data connections
TCP control connection
FTP client contacts FTP server port 21
at port 21, TCP is transport
protocol TCP data connection
client authorized over control FTP port 20 FTP
connection client server
client browses remote
server opens another TCP
directory by sending commands
data connection to transfer
over control connection.
another file.
when server receives file
control connection: out of
transfer command, server
band
opens 2nd TCP connection (for
FTP server maintains state:

al
file) to client
current directory, earlier

ep
after transferring one file,
authentication
server closes data connection.

itn
cs
2: Application Layer 47
FTP commands, responses

Sample commands: Sample return codes

sent as ASCII text over
control channel
USER username
PASS password
LIST return list of file in
current directory
RETR filename retrieves
(gets) file
STOR filename stores
status code and phrase (as
in HTTP)
331 Username OK,
password required
125 data connection
already open;
transfer starting
425 Cant open data
connection
452 Error writing

al
(puts) file onto remote file

ep
host

itn
cs
2: Application Layer 48
Chapter 2: Application layer
2.1 Principles of 2.6 P2P applications
network applications 2.7 Socket programming
2.2 Web and HTTP with TCP
2.3 FTP 2.8 Socket programming
2.4 Electronic Mail with UDP
SMTP, POP3, IMAP
2.5 DNS

al
ep
itn
cs
2: Application Layer 49
Electronic Mail outgoing
message queue
user mailbox
user
Three major components: agent
user agents mail
user
server
mail servers agent
simple mail transfer SMTP mail
protocol: SMTP server user
SMTP agent
User Agent
a.k.a. mail reader SMTP
mail user
composing, editing, reading agent
server
mail messages
e.g., Eudora, Outlook, elm, user

al
Mozilla Thunderbird agent

ep
user
outgoing, incoming messages agent

itn
stored on server

cs
2: Application Layer 50
Electronic Mail: mail servers
user
Mail Servers agent
mailbox contains incoming mail
user
messages for user server
agent
message queue of outgoing
SMTP
(to be sent) mail messages mail
server user
SMTP protocol between mail
servers to send email SMTP agent

messages SMTP
client: sending mail mail user
agent
server server
server: receiving mail

al
user
server agent

ep
user

itn
agent

cs
2: Application Layer 51
Electronic Mail: SMTP [RFC 2821]

uses TCP to reliably transfer email message from client

to server, port 25
direct transfer: sending server to receiving server
three phases of transfer
handshaking (greeting)
transfer of messages
closure
command/response interaction
commands: ASCII text
response: status code and phrase

al
messages must be in 7-bit ASCII

ep
itn
cs
2: Application Layer 52
Scenario: Alice sends message to Bob
1) Alice uses UA to compose
message and to
bob@someschool.edu
2) Alices UA sends message
to her mail server; message
placed in message queue
3) Client side of SMTP opens
TCP connection with Bobs
mail server
4) SMTP client sends Alices
message over the TCP
connection
5) Bobs mail server places the
message in Bobs mailbox
6) Bob invokes his user agent
to read message

1 mail
mail
server user

al
user server
2 agent
agent 3 6

ep
4 5

itn
cs
2: Application Layer 53
Sample SMTP interaction
S: 220 hamburger.edu
C: HELO crepes.fr
S: 250 Hello crepes.fr, pleased to meet you
C: MAIL FROM: <alice@crepes.fr>
S: 250 alice@crepes.fr... Sender ok
C: RCPT TO: <bob@hamburger.edu>
S: 250 bob@hamburger.edu ... Recipient ok
C: DATA
S: 354 Enter mail, end with "." on a line by itself
C: Do you like ketchup?
C: How about pickles?
C: .
S: 250 Message accepted for delivery

al
C: QUIT

ep
S: 221 hamburger.edu closing connection

itn
cs
2: Application Layer 54
Try SMTP interaction for yourself:

telnet servername 25
see 220 reply from server
enter HELO, MAIL FROM, RCPT TO, DATA, QUIT
commands
above lets you send email without using email client
(reader)

al
ep
itn
cs
2: Application Layer 55
SMTP: final words
SMTP uses persistent Comparison with HTTP:
connections
SMTP requires message
(header & body) to be in 7-
bit ASCII
SMTP server uses
CRLF.CRLF to determine
end of message
HTTP: pull
SMTP: push
both have ASCII
command/response
interaction, status codes
HTTP: each object
encapsulated in its own
response msg
SMTP: multiple objects

al
sent in multipart msg

ep
itn
cs
2: Application Layer 56
Mail message format

SMTP: protocol for

exchanging email msgs header
blank
RFC 822: standard for text
line
message format:
header lines, e.g.,
To:

body
From:
Subject:
different from SMTP
commands!
body

al
the message, ASCII

ep
characters only

itn
cs
2: Application Layer 57
 Message format: multimedia extensions
MIME: multimedia mail extension, RFC 2045, 2056
additional lines in msg header declare MIME content
type

From: alice@crepes.fr
MIME version To: bob@hamburger.edu
Subject: Picture of yummy crepe.
method used MIME-Version: 1.0
to encode data Content-Transfer-Encoding: base64
Content-Type: image/jpeg
multimedia data
type, subtype, base64 encoded data .....
parameter declaration .........................

al
......base64 encoded data

ep
encoded data

itn
cs
2: Application Layer 58
Mail access protocols
SMTP SMTP access user
user
agent protocol agent

senders mail receivers mail

server server

SMTP: delivery/storage to receivers server

Mail access protocol: retrieval from server
POP: Post Office Protocol [RFC 1939]
authorization (agent <-->server) and download
IMAP: Internet Mail Access Protocol [RFC 1730]
more features (more complex)

al
manipulation of stored msgs on server

ep
HTTP: gmail, Hotmail, Yahoo! Mail, etc.

itn
cs
2: Application Layer 59
POP3 protocol S: +OK POP3 server ready
C: user bob
authorization phase S: +OK
C: pass hungry
client commands: S: +OK user successfully logged on
user: declare username
C: list
pass: password S: 1 498
server responses S: 2 912
S: .
+OK
C: retr 1
-ERR S: <message 1 contents>
transaction phase, client: S: .
C: dele 1
list: list message numbers C: retr 2
retr: retrieve message by S: <message 1 contents>
number

al
S: .
C: dele 2

ep
dele: delete
C: quit

itn
quit S: +OK POP3 server signing off

cs
2: Application Layer 60
POP3 (more) and IMAP
More about POP3 IMAP
Previous example uses Keep all messages in
download and delete one place: the server
mode. Allows user to
Bob cannot re-read e- organize messages in
mail if he changes folders
client IMAP keeps user state
Download-and-keep: across sessions:
copies of messages on names of folders and
different clients mappings between

al
message IDs and folder
POP3 is stateless

ep
name
across sessions

itn
cs
2: Application Layer 61
Chapter 2: Application layer
2.1 Principles of 2.6 P2P applications
network applications 2.7 Socket programming
2.2 Web and HTTP with TCP
2.3 FTP 2.8 Socket programming
2.4 Electronic Mail with UDP
SMTP, POP3, IMAP 2.9 Building a Web
2.5 DNS server

al
ep
itn
cs
2: Application Layer 62
DNS: Domain Name System

People: many identifiers: Domain Name System:

SSN, name, passport # distributed database
Internet hosts, routers: implemented in hierarchy of
many name servers
IP address (32 bit) -
used for addressing
application-layer protocol
host, routers, name servers to
datagrams
communicate to resolve names
name, e.g., (address/name translation)
ww.yahoo.com - used by
note: core Internet
humans
function, implemented as
Q: map between IP application-layer protocol
addresses and name ?

al
complexity at networks

ep
edge

itn
cs
2: Application Layer 63
 DNS
DNS services Why not centralize DNS?
hostname to IP single point of failure
address translation traffic volume
host aliasing distant centralized
Canonical, alias names database
mail server aliasing maintenance
load distribution
replicated Web doesnt scale!
servers: set of IP
addresses for one

al
canonical name

ep
itn
cs
2: Application Layer 64
Distributed, Hierarchical Database
Root DNS Servers

com DNS servers org DNS servers edu DNS servers

pbs.org poly.edu umass.edu

yahoo.com amazon.com
DNS servers DNS serversDNS servers
DNS servers DNS 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

al
client queries amazon.com DNS server to get IP

ep
address for www.amazon.com

itn
cs
2: Application Layer 65
 DNS: Root name servers
contacted by local name server that can not resolve name
root name server:
contacts authoritative name server if name mapping not known
gets mapping
returns mapping to local name server
a Verisign, Dulles, VA
c Cogent, Herndon, VA (also LA)
d U Maryland College Park, MD k RIPE London (also 16 other locations)
g US DoD Vienna, VA
h ARL Aberdeen, MD i Autonomica, Stockholm (plus
j Verisign, ( 21 locations) 28 other locations)
e NASA Mt View, CA m WIDE Tokyo (also Seoul,
f Internet Software C. Palo Alto, Paris, SF)
CA (and 36 other locations)

13 root name

al
servers worldwide

ep
b USC-ISI Marina del Rey, CA
l ICANN Los Angeles, CA

itn
cs
2: Application Layer 66
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

al
provider

ep
itn
cs
2: Application Layer 67
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

al
ep
itn
cs
2: Application Layer 68
DNS name root DNS server

resolution example
2
Host at cis.poly.edu 3
TLD DNS server
wants IP address for 4
gaia.cs.umass.edu 5

iterated query: local DNS server

dns.poly.edu
contacted server 7 6
replies with name of 1 8
server to contact
authoritative DNS server
I dont know this
dns.cs.umass.edu
name, but ask this requesting host
server

al
cis.poly.edu

ep
gaia.cs.umass.edu

itn
cs
2: Application Layer 69
DNS name
resolution example root DNS server

recursive query: 2 3
puts burden of name 6
7
resolution on
TLD DNS server
contacted name
server
heavy load? local DNS server
dns.poly.edu 5 4

1 8

authoritative DNS server

dns.cs.umass.edu

al
requesting host

ep
cis.poly.edu

itn
gaia.cs.umass.edu

cs
2: Application Layer 70
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

al
ep
itn
cs
2: Application Layer 71
DNS records
DNS: distributed db storing resource records (RR)
RR format: (name, value, type, ttl)

Type=A Type=CNAME
name is hostname name is alias name for some
value is IP address canonical (the real) name
www.ibm.com is really
Type=NS
servereast.backup2.ibm.com
name is domain (e.g.
value is canonical name
foo.com)
value is hostname of Type=MX

al
authoritative name
value is name of mailserver

ep

server for this domain
associated with name

itn
cs
2: Application Layer 72
DNS protocol, messages
DNS protocol : query and reply messages, both with
same message format

msg header
identification: 16 bit #
for query, reply to query
uses same #
flags:
query or reply
recursion desired
recursion available

al
reply is authoritative

ep
itn
cs
2: Application Layer 73
DNS protocol, messages

Name, type fields

for a query

RRs in response
to query

records for
authoritative servers

additional helpful
info that may be used

al
ep
itn
cs
2: Application Layer 74
Inserting records into DNS
example: new startup Network Utopia
register name networkuptopia.com at DNS registrar
(e.g., Network Solutions)
provide names, IP addresses of authoritative name server
(primary and secondary)
registrar inserts two RRs into com TLD server:

(networkutopia.com, dns1.networkutopia.com, NS)

(dns1.networkutopia.com, 212.212.212.1, A)

create authoritative server Type A record for

www.networkuptopia.com; Type MX record for
networkutopia.com

al
How do people get IP address of your Web site?

ep
itn
cs
2: Application Layer 75
Chapter 2: Application layer
2.1 Principles of 2.6 P2P applications
network applications 2.7 Socket programming
app architectures with TCP
app requirements
2.8 Socket programming

2.2 Web and HTTP with UDP

2.4 Electronic Mail
SMTP, POP3, IMAP
2.5 DNS

al
ep
itn
cs
2: Application Layer 76
Pure P2P architecture
no always-on server
arbitrary end systems
directly communicate peer-peer
peers are intermittently
connected and change IP
addresses

Three topics:
File distribution

al
Searching for information

ep
Case Study: Skype

itn
cs
2: Application Layer 77
File Distribution: Server-Client vs P2P
Question : How much time to distribute file
from one server to N peers?
us: server upload
bandwidth
Server
ui: peer i upload
u1 d1 u2 bandwidth
us d2
di: peer i download
File, size F bandwidth
dN
Network (with
uN abundant bandwidth)

al
ep
itn
cs
2: Application Layer 78
File distribution time: server-client
Server
server sequentially F u1 d1 u2
sends N copies: us d2

NF/us time dN Network (with

abundant bandwidth)
client i takes F/di uN
time to download

Time to distribute F
to N clients using = dcs = max { NF/us, F/min(di) }
i

al
client/server approach

ep
increases linearly in N

itn
(for large N) 2: Application Layer

cs
79
File distribution time: P2P
Server
server must send one F u1 d1 u2
copy: F/us time us d2

client i takes F/di time

dN Network (with
to download abundant bandwidth)
uN
NF bits must be
downloaded (aggregate)
fastest possible upload rate: us + ui

al
ep
dP2P = max { F/us, F/min(di) , NF/(us + ui) }
i

itn
cs
2: Application Layer 80
Server-client vs. P2P: example
Client upload rate = u, F/u = 1 hour, us = 10u, dmin us

3.5
P2P
Minimum Distribution Time

3
Client-Server
2.5

1.5

0.5

al
0

ep
0 5 10 15 20 25 30 35

itn
N

cs
2: Application Layer 81
File distribution: BitTorrent
P2P file distribution
tracker: tracks peers torrent: group of
participating in torrent peers exchanging
chunks of a file

obtain list
of peers

trading
chunks

al
ep
peer

itn
cs
2: Application Layer 82
BitTorrent (1)
file divided into 256KB chunks.
peer joining torrent:
has no chunks, but will accumulate them over time
registers with tracker to get list of peers,
connects to subset of peers (neighbors)
while downloading, peer uploads chunks to other
peers.
peers may come and go

al
once peer has entire file, it may (selfishly) leave or

ep

(altruistically) remain

itn
cs
2: Application Layer 83
BitTorrent (2) Sending Chunks: tit-for-tat
Alice sends chunks to four
Pulling Chunks
neighbors currently
at any given time,
sending her chunks at the
different peers have highest rate
different subsets of
file chunks re-evaluate top 4 every
10 secs
periodically, a peer
every 30 secs: randomly
(Alice) asks each
neighbor for list of select another peer,
chunks that they have. starts sending chunks
newly chosen peer may
Alice sends requests
join top 4

al
for her missing chunks

ep
optimistically unchoke
rarest first

itn
cs
2: Application Layer 84
BitTorrent: Tit-for-tat
(1) Alice optimistically unchokes Bob
(2) Alice becomes one of Bobs top-four providers; Bob reciprocates
(3) Bob becomes one of Alices top-four providers

al
With higher upload rate,

ep
can find better trading

itn
partners & get file faster!

cs
2: Application Layer 85
P2P: searching for information
Index in P2P system: maps information to peer location
(location = IP address & port number)
. Instant messaging
File sharing (eg e-mule)
Index dynamically Index maps user
tracks the locations of names to locations.
files that peers share. When user starts IM
Peers need to tell application, it needs to
index what they have. inform index of its
Peers search index to
location
determine where files Peers search index to
can be found determine IP address

al
of user.

ep
itn
cs
2: Application Layer 86
P2P: centralized index
Bob
original Napster design centralized
1) when peer connects, it directory server
1
informs central server: peers

IP address 1

content
1 3
2) Alice queries for Hey
2
Jude 1

3) Alice requests file from

Bob

al
ep
Alice

itn
cs
2: Application Layer 87
P2P: problems with centralized directory

single point of failure file transfer is

performance bottleneck decentralized, but
copyright infringement:
locating content is
target of lawsuit is highly centralized
obvious

al
ep
itn
cs
2: Application Layer 88
Query flooding
fully distributed overlay network: graph
no central server edge between peer X
used by Gnutella and Y if theres a TCP
Each peer indexes the connection
files it makes available all active peers and
for sharing (and no edges form overlay net
other files)
edge: virtual (not
physical) link
given peer typically
connected with < 10

al
overlay neighbors

ep
itn
cs
2: Application Layer 89
Query flooding
File transfer:
Query message HTTP
sent over existing TCP
connections
Query
peers forward
QueryHit
Query message
ry Qu
QueryHit e e
Qu H it ry
sent over e ry
Qu
reverse
Query
path
QueryHit

al
Scalability: Qu
er

ep
y
limited scope

itn
flooding

cs
2: Application Layer 90
Gnutella: Peer joining
1. joining peer Alice must find another peer in
Gnutella network: use list of candidate peers
2. Alice sequentially attempts TCP connections with
candidate peers until connection setup with Bob
3. Flooding: Alice sends Ping message to Bob; Bob
forwards Ping message to his overlay neighbors
(who then forward to their neighbors.)
peers receiving Ping message respond to Alice
with Pong message
4. Alice receives many Pong messages, and can then
setup additional TCP connections

al
ep
Peer leaving: see homework problem!

itn
cs
2: Application Layer 91
Hierarchical Overlay
between centralized
index, query flooding
approaches
each peer is either a
super node or assigned to
a super node
TCP connection between
peer and its super node.
TCP connections between
some pairs of super nodes. ordinary peer

al
Super node tracks content group-leader peer

ep
in its children neighoring relationships
in overlay network

itn
cs
2: Application Layer 92
P2P Case study: Skype
Skype clients (SC)
inherently P2P: pairs
of users communicate.
proprietary Skype
application-layer login server Supernode
protocol (inferred via (SN)
reverse engineering)
hierarchical overlay
with SNs
Index maps usernames
to IP addresses;

al
distributed over SNs

ep
itn
cs
2: Application Layer 93
Peers as relays
Problem when both
Alice and Bob are
behind NATs.
NAT prevents an outside
peer from initiating a call
to insider peer
Solution:
Using Alices and Bobs
SNs, Relay is chosen
Each peer initiates
session with relay.
Peers can now

al

communicate through

ep
NATs via relay

itn
cs
2: Application Layer 94
Chapter 2: Application layer
2.1 Principles of 2.6 P2P applications
network applications 2.7 Socket programming
2.2 Web and HTTP with TCP
2.3 FTP 2.8 Socket programming
2.4 Electronic Mail with UDP
SMTP, POP3, IMAP
2.5 DNS

al
ep
itn
cs
2: Application Layer 95
Socket programming
Goal: learn how to build client/server application that
communicate using sockets

Socket API socket

introduced in BSD4.1 UNIX,
1981
explicitly created, used,
released by apps
client/server paradigm
two types of transport
service via socket API:
unreliable datagram
a host-local,
application-created,
OS-controlled interface
(a door) into which
application process can
both send and
receive messages to/from
another application

al
process
reliable, byte stream-

ep
oriented

itn
cs
2: Application Layer 96
Socket-programming using TCP
Socket: a door between application process and end-
end-transport protocol (UCP or TCP)
TCP service: reliable transfer of bytes from one
process to another

controlled by
controlled by process application
application process
developer
developer socket socket
controlled by TCP with TCP with controlled by
buffers, operating
operating buffers, internet system
system variables variables

al
ep
host or host or
server server

itn
cs
2: Application Layer 97
Socket programming with TCP
Client must contact server
server process must first
be running
server must have created
socket (door) that
welcomes clients contact
Client contacts server by:
creating client-local TCP
socket
specifying IP address, port
number of server process
When client creates
socket: client TCP
establishes connection to
server TCP
When contacted by client,
server TCP creates new
socket for server process to
communicate with client
allows server to talk with
multiple clients
source port numbers
used to distinguish
clients (more in Chap 3)
application viewpoint
TCP provides reliable, in-order
al
transfer of bytes (pipe)
ep
between client and server
itn
cs
2: Application Layer 98
Client/server socket interaction: TCP
Server (running on hostid) Client
create socket,
port=x, for
incoming request:
welcomeSocket =
ServerSocket()

TCP create socket,

wait for incoming
connection request connection setup connect to hostid, port=x
connectionSocket = clientSocket =
welcomeSocket.accept() Socket()

send request using

read request from clientSocket
connectionSocket

write reply to

al
connectionSocket read reply from

ep
clientSocket
close

itn
connectionSocket close
clientSocket

cs
2: Application Layer 99
 Stream jargon
keyboard monitor

A stream is a sequence of
characters that flow into

inFromUser
or out of a process. input
stream

An input stream is Client

attached to some input Process
process
source for the process,
e.g., keyboard or socket.
An output stream is
attached to an output

inFromServer
outToServer
output input
source, e.g., monitor or stream stream

socket.
client TCP

al
clientSocket
socket

ep
TCP
socket

itn
to network from network

cs
2: Application Layer 100
Socket programming with TCP
Example client-server app:
1) client reads line from
standard input (inFromUser
stream) , sends to server via
socket (outToServer
stream)
2) server reads line from socket
3) server converts line to
uppercase, sends back to
client
4) client reads, prints modified
line from socket

al
(inFromServer stream)

ep
itn
cs
2: Application Layer 101
 Example: Java client (TCP)
import java.io.*;
import java.net.*;
class TCPClient {

public static void main(String argv[]) throws Exception

{
String sentence;
String modifiedSentence;
Create
input stream BufferedReader inFromUser =
new BufferedReader(new InputStreamReader(System.in));
Create
client socket, Socket clientSocket = new Socket("hostname", 6789);
connect to server

al
Create DataOutputStream outToServer =

ep
output stream new DataOutputStream(clientSocket.getOutputStream());

itn
attached to socket

cs
2: Application Layer 102
 Example: Java client (TCP), cont.

Create BufferedReader inFromServer =

input stream new BufferedReader(new
attached to socket InputStreamReader(clientSocket.getInputStream()));

sentence = inFromUser.readLine();
Send line
to server outToServer.writeBytes(sentence + '\n');

Read line modifiedSentence = inFromServer.readLine();

from server
System.out.println("FROM SERVER: " + modifiedSentence);

al
clientSocket.close();

ep
}

itn
}

cs
2: Application Layer 103
 Example: Java server (TCP)
import java.io.*;
import java.net.*;

class TCPServer {

public static void main(String argv[]) throws Exception

{
String clientSentence;
Create String capitalizedSentence;
welcoming socket
ServerSocket welcomeSocket = new ServerSocket(6789);
at port 6789
while(true) {
Wait, on welcoming
socket for contact Socket connectionSocket = welcomeSocket.accept();
by client

al
BufferedReader inFromClient =
Create input new BufferedReader(new

ep
stream, attached InputStreamReader(connectionSocket.getInputStream()));
to socket

itn
cs
2: Application Layer 104
 Example: Java server (TCP), cont

Create output
stream, attached DataOutputStream outToClient =
to socket new DataOutputStream(connectionSocket.getOutputStream());
Read in line
from socket clientSentence = inFromClient.readLine();

capitalizedSentence = clientSentence.toUpperCase() + '\n';

Write out line
outToClient.writeBytes(capitalizedSentence);
to socket
}
}
} End of while loop,

al
loop back and wait for
another client connection

ep
itn
cs
2: Application Layer 105
Chapter 2: Application layer
2.1 Principles of 2.6 P2P applications
network applications 2.7 Socket programming
2.2 Web and HTTP with TCP
2.3 FTP 2.8 Socket programming
2.4 Electronic Mail with UDP
SMTP, POP3, IMAP
2.5 DNS

al
ep
itn
cs
2: Application Layer 106
Socket programming with UDP

UDP: no connection between

client and server
no handshaking
sender explicitly attaches application viewpoint
IP address and port of
destination to each packet UDP provides unreliable transfer
of groups of bytes (datagrams)
server must extract IP
between client and server
address, port of sender
from received packet
UDP: transmitted data may be
received out of order, or

al
lost

ep
itn
cs
2: Application Layer 107
Client/server socket interaction: UDP
Server (running on hostid) Client

create socket, create socket,

port= x. clientSocket =
serverSocket = DatagramSocket()
DatagramSocket()
Create datagram with server IP and
port=x; send datagram via
read datagram from clientSocket
serverSocket

write reply to
serverSocket
specifying read datagram from
client address, clientSocket

al
port number close

ep
clientSocket

itn
cs
2: Application Layer 108
Example: Java client (UDP)
keyboard monitor

inFromUser
input
stream

Client
Process
Input: receives
process
packet (recall
Output: sends thatTCP received
packet (recall byte stream)

receivePacket
sendPacket
that TCP sent UDP
packet
UDP
packet
byte stream)
client UDP
clientSocket
socket UDP

al
socket

ep
to network from network

itn
cs
2: Application Layer 109
 Example: Java client (UDP)
import java.io.*;
import java.net.*;

class UDPClient {
public static void main(String args[]) throws Exception
{
Create
input stream BufferedReader inFromUser =
new BufferedReader(new InputStreamReader(System.in));
Create
client socket DatagramSocket clientSocket = new DatagramSocket();
Translate
InetAddress IPAddress = InetAddress.getByName("hostname");
hostname to IP
address using DNS byte[] sendData = new byte[1024];

al
byte[] receiveData = new byte[1024];

ep
String sentence = inFromUser.readLine();

itn
sendData = sentence.getBytes();

cs
2: Application Layer 110
 Example: Java client (UDP), cont.
Create datagram
with data-to-send, DatagramPacket sendPacket =
length, IP addr, port new DatagramPacket(sendData, sendData.length, IPAddress, 9876);

Send datagram clientSocket.send(sendPacket);

to server
DatagramPacket receivePacket =
new DatagramPacket(receiveData, receiveData.length);
Read datagram
clientSocket.receive(receivePacket);
from server
String modifiedSentence =
new String(receivePacket.getData());

System.out.println("FROM SERVER:" + modifiedSentence);

al
clientSocket.close();
}

ep
}

itn
cs
2: Application Layer 111
 Example: Java server (UDP)
import java.io.*;
import java.net.*;

class UDPServer {
public static void main(String args[]) throws Exception
Create {
datagram socket
DatagramSocket serverSocket = new DatagramSocket(9876);
at port 9876
byte[] receiveData = new byte[1024];
byte[] sendData = new byte[1024];

while(true)
{
Create space for

al
DatagramPacket receivePacket =
received datagram

ep
new DatagramPacket(receiveData, receiveData.length);
Receive serverSocket.receive(receivePacket);

itn
datagram

cs
2: Application Layer 112
 Example: Java server (UDP), cont
String sentence = new String(receivePacket.getData());
Get IP addr
InetAddress IPAddress = receivePacket.getAddress();
port #, of
sender int port = receivePacket.getPort();

String capitalizedSentence = sentence.toUpperCase();

sendData = capitalizedSentence.getBytes();
Create datagram
DatagramPacket sendPacket =
to send to client new DatagramPacket(sendData, sendData.length, IPAddress,
port);
Write out
datagram serverSocket.send(sendPacket);
to socket }

al
}

ep
} End of while loop,
loop back and wait for

itn
another datagram

cs
2: Application Layer 113
Chapter 2: Summary
our study of network apps now complete!
application architectures specific protocols:
client-server HTTP
P2P FTP
hybrid SMTP, POP, IMAP
DNS
application service
P2P: BitTorrent, Skype
requirements:

reliability, bandwidth, socket programming

delay
Internet transport
service model

al
connection-oriented,

ep

reliable: TCP

itn
unreliable, datagrams: UDP

cs
2: Application Layer 114
Chapter 2: Summary
Most importantly: learned about protocols

typical request/reply Important themes:

message exchange: control vs. data msgs
client requests info or
in-band, out-of-band

service
server responds with centralized vs.
data, status code decentralized
message formats: stateless vs. stateful
headers: fields giving reliable vs. unreliable
info about data msg transfer

al
data: info being

ep

communicated complexity at network
edge

itn
cs
2: Application Layer 115