Escolar Documentos
Profissional Documentos
Cultura Documentos
Chapter 2
Application Layer
2.1 Principles of
network applications
2.2 Web and HTTP
2.3 FTP
2.4 Electronic Mail
Computer Networking:
A Top Down Approach,
4th edition.
diti
Jim Kurose, Keith Ross
Addison-Wesley, July
2007.
with TCP
2.8 Socket programming
with UDP
2.5 DNS
2: Application Layer
by examining popular
application-level
li i l
l
protocols
voice over IP
web
real-time video
instant messaging
HTTP
FTP
SMTP / POP3 / IMAP
DNS
conferencing
remote login
grid computing
multi-user network
games
g
programming
i network
t
k
applications
socket API
2: Application Layer
2: Application Layer
clips
2: Application Layer
2.1 Principles of
network applications
2.2 Web and HTTP
2.3 FTP
2.4 Electronic Mail
s st ms
systems
application
transport
network
data link
physical
application
transport
network
data link
physical
application
transport
p
network
data link
physical
2: Application Layer
2.5 DNS
with TCP
2.8 Socket programming
with UDP
2.9 Building a Web
server
2: Application Layer
Application architectures
Client-server architecture
server:
always-on host
permanent IP address
server farms for
scaling
clients:
Client-server
Peer-to-peer
P
t
(P2P)
Hybrid of client-server and P2P
client/server
2: Application Layer
no always-on server
Processes communicating
Process: program running
within a host.
within same host, two
processes communicate
using inter-process
communication (defined
by OS).
processes in different
hosts communicate by
exchanging messages
2: Application Layer
10
Sockets
process sends/receives
g to/from
f
its
messages
socket
socket analogous to door
Note
Note: applications with
host or
server
host or
server
process
controlled by
app developer
process
socket
socket
TCP with
buffers,
variables
TCP with
buffers,
variables
Internet
controlled
by OS
2: Application Layer
11
2: Application Layer
12
Addressing processes
Addressing processes
to receive messages,
to receive messages,
identifier
identifier
32-bit IP address
Q: does IP address of
host on which process
runs suffice for
identifying the process?
2: Application Layer
exchanged,
Message syntax:
what fields in messages &
how fields are delineated
Message semantics
meaning of information in
fields
HTTP server: 80
Mail server: 25
to gaia.cs.umass.edu
gaia cs umass edu web
server:
IP address: 128.119.245.12
Port number: 80
more shortly
14
Public-domain protocols:
defined in RFCs
allows for
interoperability
e.g., HTTP, SMTP
Proprietary protocols:
e.g., Skype
Timing
Internet telephony,
interactive games)
require low delay to be
effective
2: Application Layer
2: Application Layer
13
32-bit IP address
Q: does IP address of
host on which process
runs suffice for
identifying the
process?
A: No, many
processes can be
running on same host
15
Bandwidth
some apps (e.g.,
multimedia) require
minimum amount of
bandwidth to be
effective
other apps (elastic
apps) make use of
whatever bandwidth
they get
2: Application Layer
16
Bandwidth
Time Sensitive
file transfer
e-mail
Web documents
real-time audio/video
no loss
no loss
no loss
loss-tolerant
no
no
no
yes, 100s msec
stored audio/video
interactive games
instant messaging
loss-tolerant
loss-tolerant
no loss
elastic
elastic
elastic
audio: 5kbps-1Mbps
video:10kbps-5Mbps
same as above
few kbps up
elastic
Application
TCP service:
2: Application Layer
e-mail
remote terminal access
Web
file transfer
streaming multimedia
Internet telephony
Application
layer protocol
Underlying
transport protocol
TCP
TCP
TCP
TCP
TCP or UDP
2: Application Layer
18
network applications
app architectures
app requirements
with TCP
with UDP
2.5
2 5 DNS
typically UDP
2: Application Layer
17
connection-oriented:
connection
oriented: setup
UDP service:
19
2: Application Layer
20
HTTP overview
HTTP: hypertext
transfer protocol
Webs application layer
protocol
client/server model
client: browser that
requests, receives,
displays Web objects
server: Web server
sends objects in
response to requests
HTTP 1.0: RFC 1945
HTTP 1.1: RFC 2068
www.someschool.edu/someDept/pic.gif
host name
path name
2: Application Layer
Server
running
p
Web
W
Apache
server
Mac running
Navigator
2: Application Layer
21
PC running
Explorer
22
HTTP connections
HTTP is stateless
Nonpersistent HTTP
At most one object is
sent over a TCP
connection.
HTTP/1.0 uses
nonpersistent HTTP
server m
maintains no
information about
past client requests
aside
23
Persistent HTTP
Multiple objects can
be sent over single
TCP connection
between client and
server.
HTTP/1.1 uses
persistent connections
in default mode
2: Application Layer
24
Nonpersistent HTTP
(contains text,
Suppose user enters URL
references to 10
www.someSchool.edu/someDepartment/home.index
jpeg images)
www.someSchool.edu waiting
for TCP connection at port 80.
accepts connection, notifying
client
connection.
time
2: Application Layer
initiate TCP
connection
RTT
request
file
RTT
fil
file
received
time
time to
transmit
file
time
2: Application Layer
2: Application Layer
25
27
26
Persistent HTTP
Nonpersistent HTTP issues:
requires 2 RTTs per object
OS overhead
h d for
f each
h TCP
connection
browsers often open parallel
TCP connections to fetch
referenced objects
Persistent HTTP
server leaves connection
open after
f
sending
di response
subsequent HTTP messages
between same client/server
sent over open connection
2: Application Layer
28
request, response
Carriage return,
line feed
indicates end
of message
2: Application Layer
2: Application Layer
29
Method types
Post method:
Web page often
includes form input
Input is uploaded to
server in entity body
HTTP/1.0
GET
POST
HEAD
URL method:
Uses GET method
Input is uploaded in
www.somesite.com/animalsearch?monkeys&banana
2: Application Layer
31
30
HTTP/1.1
GET,
GET POST,
POST HEAD
PUT
DELETE
deletes file specified in
the URL field
2: Application Layer
32
data, e
data
e.g.,
g
requested
HTML file
HTTP/1.1
/
200 OK
Connection close
Date: Thu, 06 Aug 1998 12:00:15 GMT
Server: Apache/1.3.0 (Unix)
Last-Modified: Mon, 22 Jun 1998 ...
Content-Length: 6821
Content-Type: text/html
d t d
data
data
t d
data
t d
data
t d
data
t ...
2: Application Layer
33
34
Ethereal
Eth
l example
l
35
2: Application Layer
36
client
Example:
Susan always access
Internet always from PC
visits specific e1) cookie header line of
HTTP response message
commerce site for first
2) cookie header line in
time
HTTP request message
2: Application Layer
ebay 8734
cookie file
Set-cookie: 1678
ebay 8734
amazon 1678
cookie: 1678
one w
on
week later:
at r
ebay 8734
amazon 1678
usual http
p response
p
msg
g
usual http request msg
cookie: 1678
usual http response msg
Amazon server
creates ID
1678 for user create
entry
cookiespecific
action
access
access
backend
database
cookiespectific
action
2: Application Layer
37
Cookies (continued)
What cookies can bring:
authorization
shopping carts
recommendations
user session state
(Web e-mail)
server
38
2: Application Layer
39
object in cache
cache: cache
returns object
else cache requests
object from origin
server, then returns
object to client
origin
g
server
client
client
Proxy
server
origin
server
2: Application Layer
40
10
Caching example
bits
avg. request rate from
institutions browsers to origin
servers = 15/sec
delay from institutional router
to any origin server and back
to router = 2 sec
C
Consequences
consequence
institutional
network
p LAN
10 Mbps
institutional
cache
total delay
= Internet delay +
access delay + LAN delay
= 2 sec + sec + milliseconds
2: Application Layer
41
origin
servers
public
p
Internet
consequence
42
origin
servers
public
p
Internet
= Internet delay +
access delay + LAN delay
= 2 sec + msecs + msecs
often a costly upgrade
1.5 Mbps
access link
possible solution
link to,
to say
say, 10 Mbps
public
p
Internet
origin
servers
Assumptions
10 Mbps
access link
Total delay
institutional
network
origin server
utilization of access link
reduced to 60%, resulting in
negligible
li ibl d
delays
l
((say 10
msec)
total avg delay = Internet
delay + access delay + LAN
delay = .6*(2.01) secs +
.4*milliseconds < 1.4 secs
p LAN
10 Mbps
institutional
cache
2: Application Layer
1.5 Mbps
access link
43
institutional
network
p LAN
10 Mbps
institutional
cache
2: Application Layer
44
11
Conditional GET
Goal: dont send object if
server
cache
2.1 Principles of
HTTP request
q
msg
g
If-modified-since:
<date>
HTTP response
If-modified-since:
<date>
object
not
modified
HTTP/1.0
304 Not Modified
HTTP response
2.5 DNS
network applications
2.2 Web and HTTP
2.3 FTP
2.4 Electronic Mail
with TCP
2.8 Socket programming
with UDP
2.9 Building a Web
server
object
modified
HTTP/1.0 200 OK
<data>
2: Application Layer
user
at host
FTP
FTP
user
client
interface
file transfer
local file
system
2: Application Layer
45
FTP
server
remote file
system
46
client:
li t side
id th
thatt iinitiates
iti t ttransfer
f ((either
ith tto/from
/f
remote)
server: remote host
ftp: RFC 959
ftp server: port 21
2: Application Layer
47
48
12
Sample commands:
2.1 Principles of
control channel
USER username
PASS password
current directory
(gets) file
network applications
2.2 Web and HTTP
2.3 FTP
2.4 Electronic Mail
in HTTP)
331 Username OK,
password required
125 data connection
already open;
transfer starting
425 Cant
Can t open data
connection
452 Error writing
file
2: Application Layer
Electronic Mail
2.5 DNS
with TCP
2.8 Socket programming
with UDP
2.9 Building a Web
server
2: Application Layer
49
outgoing
message queue
50
user mailbox
user
agent
mail
server
SMTP
protocol: SMTP
User Agent
a.k.a. mail reader
composing,
composing editing,
editing reading
mail messages
e.g., Eudora, Outlook, elm,
Mozilla Thunderbird
outgoing, incoming messages
stored on server
SMTP
mail
server
user
agent
user
agent
Mail Servers
SMTP
user
agent
mail
server
user
agent
user
agent
user
agent
mail
il
server
SMTP
SMTP
mail
server
user
agent
2: Application Layer
51
SMTP
user
agent
mail
server
user
agent
userr
us
agent
user
agent
2: Application Layer
52
13
2) Alice
Ali ss UA sends
s nds message
m ss
to her mail server; message
placed in message queue
3) Client side of SMTP opens
TCP connection with Bobs
mail server
handshaking (greeting)
transfer of messages
closure
command/response interaction
commands:
d ASCII text
response: status code and phrase
1
user
agent
2: Application Layer
mail
server
3
mail
server
4
user
agent
2: Application Layer
53
54
220 hamburger.edu
HELO crepes.fr
250 Hello crepes.fr, pleased to meet you
MAIL FROM: <alice@crepes.fr>
250 alice@crepes.fr... Sender ok
RCPT TO: <bob@hamburger.edu>
250 bob@hamburger.edu ... Recipient ok
DATA
354 Enter mail, end with "." on a line by itself
Do you like ketchup?
How about pickles?
.
250 Message accepted for delivery
QUIT
221 hamburger.edu closing connection
2: Application Layer
55
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)
2: Application Layer
56
14
connections
SMTP requires message
(header & body) to be in 7bit ASCII
SMTP server uses
CRLF.CRLF to determine
end of message
HTTP: pull
SMTP: push
both have ASCII
command/response
interaction, status codes
To:
From:
Subject:
user
agent
g
type
multimedia data
type, subtype,
parameter declaration
encoded data
From: alice@crepes.fr
To: bob@hamburger.edu
Subject: Picture of yummy crepe.
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Type: image/jpeg
SMTP
access
protocol
user
agent
receivers mail
server
59
SMTP
senders mail
server
2: Application Layer
58
method used
to encode data
body
57
MIME version
blank
line
encapsulated
l t d iin it
its own
response msg
SMTP: multiple objects
sent in multipart msg
2: Application Layer
header
60
15
POP3 protocol
authorization phase
client commands:
list: list
l
message numbers
retr: retrieve message by
number
dele: delete
quit
S:
C:
S:
C:
S:
C:
S:
S:
S:
C:
S:
S:
C:
:
C:
S:
S:
C:
C:
S:
list
1 498
2 912
.
retr 1
<message 1 contents>
.
dele 1
retr 2
<message 1 contents>
.
dele 2
quit
+OK POP3 server signing off
2: Application Layer
IMAP
Keep all messages in
l
the
h server
one place:
Allows user to
organize messages in
folders
IMAP keeps user state
across sessions:
61
2.1 Principles of
network applications
2.2 Web and HTTP
2.3 FTP
2.4 Electronic Mail
2.5 DNS
with TCP
2.8 Socket programming
with UDP
2.9 Building a Web
server
SSN name
SSN,
name, passport #
Q: map between IP
addresses and name ?
2: Application Layer
distributed database
application-layer protocol
63
62
implemented in hierarchy of
many name servers
host, routers, name servers to
communicate to resolve names
(address/name translation)
note
note: core Internet
function, implemented as
application-layer protocol
complexity at networks
edge
2: Application Layer
64
16
DNS
DNS services
hostname
m to IP
address translation
host aliasing
65
e NASA Mt View, CA
f Internet
I t
t Software
S ft
C.
C Palo
P l Alto,
Alt
poly.edu
umass.edu
DNS serversDNS servers
2: Application Layer
66
pbs.org
DNS servers
d
doesnt
t scale!
l !
2: Application Layer
13 root name
servers worldwide
b USC-ISI Marina del Rey, CA
l ICANN Los Angeles, CA
2: Application Layer
67
2: Application Layer
68
17
DNS name
resolution example
iterated query:
contacted server
Host at cis.poly.edu
each
h ISP ((residential
id ti l ISP
ISP, company,
acts
t as proxy, forwards
f
d query iinto
t hi
hierarchy
h
requesting host
cis.poly.edu
gaia.cs.umass.edu
2: Application Layer
DNS name
resolution example
recursive query:
resolution on
contacted name
server
heavy load?
3
7
6
TLD DNS server
caches
mapping
cache entries timeout (disappear) after some
time
TLD servers typically cached in local name
servers
Thus root name servers not often visited
requesting host
70
2: Application Layer
69
update/notify
p
fy mechanisms under design
g by
y IETF
RFC 2136
http://www.ietf.org/html.charters/dnsind-charter.html
cis.poly.edu
gaia.cs.umass.edu
2: Application Layer
71
2: Application Layer
72
18
DNS records
RR format: (name,
Type=A
name is hostname
value is IP address
Type=NS
name is domain (e.g.
(e g
foo.com)
value is hostname of
authoritative name
server for this domain
value, type,
yp
ttl)
msg header
Type=CNAME
name is alias name for some
canonical (the real) name
www.ibm.com is really
identification: 16 bit #
servereast.backup2.ibm.com
Type=MX
value is name of mailserver
associated with name
2: Application Layer
2: Application Layer
73
74
(
(e.g.,
Network
k Solutions)
l
)
RRs in response
to query
records for
authoritative servers
registrar
g
additional helpful
info that may be used
75
2: Application Layer
76
19
2.1 Principles of
Example
Alice runs P2P client
application on her
notebook computer
intermittently
connects to Internet;
gets new IP address
for each connection
asks for Hey Jude
application displays
other peers that have
copy of Hey Jude.
network applications
app architectures
app requirements
with TCP
2.8 Socket programming
with UDP
2.9 Building a Web
server
2: Application Layer
copyright infringement:
peers
IP address
content
target of lawsuit is
obvious
1
3
1
2
Bobs PC to Alices
notebook: HTTP
while Alice downloads,
other users uploading
from Alice.
Alice
Alicess peer is both a
Web client and a
transient Web server.
All peers are servers =
highly scalable!
78
centralized
directory
y server
file is copied
p
from
2: Application Layer
77
file transfer is
decentralized, but
locating content is
highly centralized
Alice
2: Application Layer
79
2: Application Layer
80
20
Gnutella: protocol
implementing protocol
Query message
Q
Query
QueryHit
QueryHit
Scalability:
limited scope
flooding
2: Application Layer
81
Hierarchical Overlay
between centralized
1.
2: Application Layer
File transfer:
HTTP
82
83
ordinary peer
group-leader peer
neighoring relationships
in overlay network
2: Application Layer
84
21
u1
us
File, size F
dN
d1
u2
di: client/peer i
download bandwidth
NF/us time
dN
d2
Network (with
abundant bandwidth)
uN
time to download
Time to distribute F
to N clients using = dcs = max { NF/us, F/min(di) }
i
client/server approach
2: Application Layer
increases linearly in N
(for large N) 2: Application Layer
85
u1 d1 u2
us
Network (with
abundant bandwidth)
uN
sends N copies:
ui: client/peer i
upload bandwidth
d2
Server
server sequentially
Server
86
Server
3.5
d u2
1
1
d2
copy: F/us time
us
client i takes F/di time
Network (with
dN
to download
abundant bandwidth)
uN
NF bits must be
downloaded (aggregate)
fastest possible upload rate (assuming
all nodes sending
g file chunks to same
peer): us + ui
i=1,N
P2P
Client-Server
3
2.5
2
1.5
1
05
0.5
0
0
10
15
20
25
30
35
i=1,N
2: Application Layer
87
2: Application Layer
88
22
BitTorrent (1)
torrent: g
group
p of
file
fil di
divided
id d iinto
t 256KB
peers exchanging
chunks of a file
participating in torrent
chunks
h k .
obtain list
of peers
trading
chunks
peer
2: Application Layer
BitTorrent (2)
Pulling Chunks
at any
y given
g
time,
different peers have
different subsets of
file chunks
periodically, a peer
(Alice) asks each
neighbor for list of
chunks that they have.
Alice issues requests
for her missing chunks
rarest first
2: Application Layer
89
90
highest rate
re-evaluate top 4
every 10 secs
every
y 30 secs: randomly
y
select another peer,
starts sending chunks
newly chosen peer may
join top 4
2: Application Layer
91
phone, phone
phone-to-pc)
to pc)
Voice-Over-IP (VoIP)
Skype
application
login server
also IM
proprietary
application-layer
protocol (inferred via
reverse engineering)
hierarchical overlay
Supernode
(SN)
2: Application Layer
92
23
2.1 Principles of
network applications
2.2 Web and HTTP
2.3 FTP
2.4 Electronic Mail
Skype
login server
(authenticate)
2.7
2 7 Socket programming
with TCP
2.8 Socket programming
with UDP
2.5 DNS
callee ID
Socket programming
1981
explicitly created, used,
released by apps
client/server paradigm
two
t ttypes of
f ttransportt
service via socket API:
unreliable datagram
reliable, byte streamoriented
94
2: Application Layer
93
Socket: a door between application process and endend-transport protocol (UCP or TCP)
TCP service: reliable transfer of bytes from one
process to another
socket
a host-local,
application-created,
OS-controlled interface
controlled by
application
developer
2: Application Layer
controlled by
operating
system
socket
TCP with
buffers,
variables
host or
server
95
process
process
internet
socket
TCP with
buffers,
variables
controlled by
application
developer
controlled by
operating
system
host or
server
2: Application Layer
96
24
TCP
setup
application viewpoint
write reply to
connectionSocket
close
connectionSocket
create socket,
connect to hostid, port=x
clientSocket =
Socket()
send request using
clientSocket
li tS k t
97
98
Stream jargon
keyboard
monitor
A stream is a sequence of
inFromS
Server
output
stream
inFromUse
er
Client
Process
process
input
stream
outToSe
erver
Client
create socket,
port=x,
port
x, for
incoming request:
welcomeSocket =
ServerSocket()
input
stream
client
TCP
clientSocket
socket
to network
TCP
socket
from network
2: Application Layer
99
2: Application Layer
100
25
import java.io.*;
import java.net.*;
class TCPClient {
Create
input stream
attached to socket
sentence = inFromUser.readLine();
Send line
to server
BufferedReader inFromUser =
new BufferedReader(new InputStreamReader(System.in));
modifiedSentence = inFromServer.readLine();
System.out.println("FROM SERVER: " + modifiedSentence);
clientSocket.close();
}
}
2: Application Layer
101
102
import java.io.*;
import java.net.*;
Create output
stream,
m, attached
to socket
class TCPServer {
Create input
stream, attached
to socket
Read line
from server
DataOutputStream outToServer =
new DataOutputStream(clientSocket.getOutputStream());
Wait, on welcoming
g
socket for contact
by client
outToServer.writeBytes(sentence + '\n');
2: Application Layer
Create
welcoming socket
at port 6789
BufferedReader inFromServer =
new BufferedReader(new
B ff dR d (
InputStreamReader(clientSocket.getInputStream()));
Read in line
from socket
clientSentence = inFromClient.readLine();
capitalizedSentence = clientSentence.toUpperCase() + '\n';
while(true) {
outToClient.writeBytes(capitalizedSentence);
}
}
}
BufferedReader inFromClient =
new BufferedReader(new
InputStreamReader(connectionSocket.getInputStream()));
2: Application Layer
DataOutputStream outToClient =
new DataOutputStream(connectionSocket.getOutputStream());
103
2: Application Layer
104
26
2.1 Principles of
network applications
with TCP
2.8 Socket programming
with UDP
2.9 Building a Web
server
application viewpoint
input
stream
create socket,
socket
clientSocket =
DatagramSocket()
Client
process
Process
Input: receives
close
clientSocket
packet (recall
that TCP sent
byte
y stream))
UDP
packet
to network
107
packet (recall
thatTCP received
byte stream)
Output: sends
client
UDP
clientSocket
socket
2: Application Layer
monitor
inFrom
mUser
keyboard
Client
sendPacket
create socket,
port=x, for
incoming request:
serverSocket =
DatagramSocket()
106
2: Application Layer
105
re
eceivePacket
2: Application Layer
UDP
packet
UDP
socket
from network
2: Application Layer
108
27
import java.io.*;
import java.net.*;
Create
input stream
class UDPClient {
public static void main(String args[]) throws Exception
{
Create
client socket
Translate
hostname to IP
address using DNS
BufferedReader inFromUser =
new BufferedReader(new InputStreamReader(System.in));
DatagramSocket clientSocket = new DatagramSocket();
DatagramPacket sendPacket =
new DatagramPacket(sendData,
g
(
sendData.length,
g IPAddress, 9876);
)
Send datagram
to server
clientSocket.send(sendPacket);
Read datagram
from server
clientSocket.receive(receivePacket);
DatagramPacket receivePacket =
new DatagramPacket(receiveData, receiveData.length);
String modifiedSentence =
new String(receivePacket.getData());
St i (
i P k t tD t ())
sendData = sentence.getBytes();
2: Application Layer
Get IP addr
port #,, of
p
f
sender
class UDPServer {
public static void main(String args[]) throws Exception
{
Create datagram
to send to client
while(true)
hil (
)
{
Receive
datagram
110
import java.io.*;
import java.net.*;
Create
datagram socket
at port 9876
2: Application Layer
109
DatagramPacket receivePacket =
new DatagramPacket(receiveData, receiveData.length);
2: Application Layer
Write out
datagram
to socket
111
serverSocket.send(sendPacket);
}
}
serverSocket.receive(receivePacket);
DatagramPacket sendPacket =
new DatagramPacket(sendData, sendData.length, IPAddress,
port);
2: Application Layer
112
28
Chapter 2: Summary
Chapter 2: Summary
requirements:
reliability, bandwidth,
delay
specific protocols:
HTTP
FTP
SMTP, POP, IMAP
DNS
P2P: BitTorrent, Skype
socket programming
service model
connection-oriented,
reliable: TCP
unreliable, datagrams: UDP
typical
i l request/reply
/
l
message exchange:
message formats:
headers: fields giving
info about data
data: info being
communicated
Internet transport
2: Application Layer
113
Important themes:
h
control vs. data msgs
in-band, out-of-band
centralized vs.
decentralized
stateless vs.
vs stateful
reliable vs. unreliable
msg transfer
complexity at network
edge
2: Application Layer
114
29