Computer Networks
Chan Yeob Yeun
Lecture 6
OSI vs. TCP/IP
OSI
TCP/IP
MODEL
APPLICATION
7 APPLICATION
Worldwide Web: http
PRESENTATION Remote Login: telnet, rlogin
6 Remote Commands: rexec, rsh
File Transfers: ftp, rcp, tftp, UUCP
E-mail: SMTP, POP3, IMAP
SESSION Remote File Systems: NIS/NFS, RPC
5
TRANSPORT
TRANSPORT
4 Tranmission Control Protocol (TCP)
User Datagram Protocol (UDP)
INTERNETWORKING
NETWORK
3 Internet Protocol (IP)
Internet Control Message Protocol (ICMP)
NETWORK INTERFACE
DATA LINK
&
2
HARDWARE
CONNECTIONS
PHYSICAL
LAN: Ethernet, Token Ring, FDDI, ATM...
1
WAN: SLIP/PPP, X.25, Frame Relay...
P2
1
Chapter 2
Application Layer
A note on the use of these ppt slides:
We’re making these slides freely available to all (faculty, students, readers).
They’re in PowerPoint form so you see the animations; and can add, modify,
and delete slides (including this one) and slide content to suit your needs. Computer
They obviously represent a lot of work on our part. In return for use, we only
ask the following: Networking: A Top
If you use these slides (e.g., in a class) that you mention their source
(after all, we’d like people to use our book!) Down Approach
If you post any slides on a www site, that you note that they are adapted
from (or perhaps identical to) our slides, and note our copyright of this
Global edition
material. James Kurose, Keith Ross
Thanks and enjoy! JFK/KWR
Pearson
November 2016
All material copyright 1996-2012
J.F Kurose and K.W. Ross, All Rights Reserved
Application Layer 2-3
Chapter 2: outline
2.1 principles of network 2.6 P2P applications
applications 2.7 socket programming
app architectures with UDP and TCP
app requirements
2.2 Web and HTTP
2.3 FTP
2.4 electronic mail
SMTP, POP3, IMAP
2.5 DNS
Application Layer 2-4
2
Electronic mail outgoing
message queue
user mailbox
Three major components: user
agent
user agents
mail servers mail user
server agent
simple mail transfer
protocol: SMTP SMTP mail user
server agent
User Agent SMTP
a.k.a. “mail reader” SMTP user
agent
composing, editing, reading mail
server
mail messages user
e.g., Outlook, Thunderbird, agent
iPhone mail client user
agent
outgoing, incoming
messages stored on server
Application Layer 2-5
Electronic mail: mail servers
mail servers: user
agent
mailbox contains incoming
messages for user mail user
server
message queue of outgoing agent
(to be sent) mail messages SMTP mail user
SMTP protocol between server agent
mail servers to send email SMTP
messages user
client: sending mail SMTP
agent
mail
server server
“server”: receiving mail user
agent
server
user
agent
Application Layer 2-6
3
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 (like HTTP, FTP)
commands: ASCII text
response: status code and phrase
messages must be in 7-bit ASCI
Application Layer 2-7
Scenario: Alice sends message to Bob
1) Alice uses UA to compose 4) SMTP client sends Alice’s
message “to” message over the TCP
[email protected] connection
2) Alice’s UA sends message 5) Bob’s mail server places the
to her mail server; message message in Bob’s mailbox
placed in message queue 6) Bob invokes his user agent
3) client side of SMTP opens to read message
TCP connection with Bob’s
mail server
1 user mail user
mail agent
agent server server
2 3 6
4
5
Alice’s mail server Bob’s mail server
Application Layer 2-8
4
Sample SMTP interaction
S: 220 hamburger.edu
C: HELO crepes.fr
S: 250 Hello crepes.fr, pleased to meet you
C: MAIL FROM: <[email protected]>
S: 250 [email protected]... Sender ok
C: RCPT TO: <[email protected]>
S: 250 [email protected] ... 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
C: QUIT
S: 221 hamburger.edu closing connection
Application Layer 2-9
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)
Application Layer 2-10
5
SMTP: final words
SMTP uses persistent comparison with HTTP:
connections
HTTP: pull
SMTP requires message
(header & body) to be in SMTP: push
7-bit ASCII both have ASCII
SMTP server uses command/response
CRLF.CRLF to interaction, status codes
determine end of message
HTTP: each object
encapsulated in its own
response msg
SMTP: multiple objects
sent in multipart msg
Application Layer 2-11
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 MAIL
FROM, RCPT TO:
commands!
Body: the “message”
ASCII characters only
Application Layer 2-12
6
Mail access protocols
user
mail access user
SMTP SMTP protocol agent
agent
(e.g., POP,
IMAP)
sender’s mail receiver’s mail
server server
SMTP: delivery/storage to receiver’s server
mail access protocol: retrieval from server
POP: Post Office Protocol [RFC 1939]: authorization,
download
IMAP: Internet Mail Access Protocol [RFC 1730]: more
features, including manipulation of stored msgs on
server
HTTP: gmail, Hotmail, Yahoo! Mail, etc.
Application Layer 2-13
POP3 protocol
S: +OK POP3 server ready
C: user bob
authorization phase S:
C:
+OK
pass hungry
client commands: S: +OK user successfully logged on
user: declare username
pass: password C: list
S: 1 498
server responses
S: 2 912
+OK S: .
-ERR C: retr 1
transaction phase, client: S:
S:
<message 1 contents>
.
list: list message numbers C: dele 1
retr: retrieve message by C: retr 2
number S: <message 1 contents>
dele: delete S: .
quit C: dele 2
C: quit
S: +OK POP3 server signing off
Application Layer 2-14
7
POP3 (more) and IMAP
more about POP3 IMAP
previous example uses keeps all messages in one
POP3 “download and place: at server
delete” mode allows user to organize
Bob cannot re-read e- messages in folders
mail if he changes keeps user state across
client sessions:
POP3 “download-and- names of folders and
keep”: copies of messages mappings between
on different clients message IDs and folder
POP3 is stateless across name
sessions
Application Layer 2-15
Chapter 2: outline
2.1 principles of network 2.6 P2P applications
applications 2.7 socket programming
app architectures with UDP and TCP
app requirements
2.2 Web and HTTP
2.3 FTP
2.4 electronic mail
SMTP, POP3, IMAP
2.5 DNS
Application Layer 2-16
8
DNS: domain name system
people: many identifiers: Domain Name System:
SSN, name, passport # distributed database
Internet hosts, routers: implemented in hierarchy of
IP address (32 bit) - many name servers
used for addressing application-layer protocol: hosts,
datagrams name servers communicate to
“name”, e.g., resolve names (address/name
www.yahoo.com - translation)
used by humans note: core Internet function,
Q: how to map between IP implemented as application-
layer protocol
address and name, and
vice versa ? complexity at network’s
“edge”
Application Layer 2-17
DNS: services, structure
DNS services why not centralize DNS?
hostname to IP address single point of failure
translation traffic volume
host aliasing distant centralized database
canonical, alias names maintenance
mail server aliasing
load distribution A: doesn’t scale!
replicated Web
servers: many IP
addresses correspond
to one name
Application Layer 2-18
9
DNS: a 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 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
Application Layer 2-19
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
c. Cogent, Herndon, VA (5 other sites)
d. U Maryland College Park, MD k. RIPE London (17 other sites)
h. ARL Aberdeen, MD
j. Verisign, Dulles VA (69 other sites ) i. Netnod, Stockholm (37 other sites)
e. NASA Mt View, CA m. WIDE Tokyo
f. Internet Software C. (5 other sites)
Palo Alto, CA (and 48 other
sites)
a. Verisign, Los Angeles CA 13 root name
(5 other sites)
b. USC-ISI Marina del Rey, CA
“servers”
l. ICANN Los Angeles, CA worldwide
(41 other sites)
g. US DoD Columbus,
OH (5 other sites)
Application Layer 2-20
10
TLD, authoritative servers
top-level domain (TLD) servers:
responsible for com, org, net, edu, aero, jobs, museums,
and all top-level country domains, e.g.: uk, fr, ca, jp
Network Solutions maintains servers for .com TLD
Educause for .edu TLD
authoritative DNS servers:
organization’s own DNS server(s), providing
authoritative hostname to IP mappings for organization’s
named hosts
can be maintained by organization or service provider
Application Layer 2-21
Local DNS 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
has local cache of recent name-to-address translation
pairs (but may be out of date!)
acts as proxy, forwards query into hierarchy
Application Layer 2-22
11
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
1 8
replies with name of
server to contact
authoritative DNS server
“I don’t know this dns.cs.umass.edu
name, but ask this requesting host
server” cis.poly.edu
gaia.cs.umass.edu
Application Layer 2-23
DNS name root DNS server
resolution example
2 3
recursive query: 7
6
puts burden of name TLD DNS
server
resolution on
contacted name local DNS server
server dns.poly.edu 5 4
heavy load at upper 1 8
levels of hierarchy?
authoritative DNS server
dns.cs.umass.edu
requesting host
cis.poly.edu
gaia.cs.umass.edu
Application Layer 2-24
12
DNS: caching, updating records
once (any) name server learns mapping, it caches
mapping
cache entries timeout (disappear) after some time (TTL)
TLD servers typically cached in local name servers
• thus root name servers not often visited
cached entries may be out-of-date (best effort
name-to-address translation!)
if name host changes IP address, may not be known
Internet-wide until all TTLs expire
update/notify mechanisms proposed IETF standard
RFC 2136
Application Layer 2-25
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
type=NS www.ibm.com is really
name is domain (e.g., servereast.backup2.ibm.com
foo.com) value is canonical name
value is hostname of
authoritative name type=MX
server for this domain value is name of mailserver
associated with name
Application Layer 2-26
13
DNS protocol, messages
query and reply messages, both with same message
format 2 bytes 2 bytes
msg header identification flags
identification: 16 bit # for # questions # answer RRs
query, reply to query uses
# authority RRs # additional RRs
same #
flags: questions (variable # of questions)
query or reply
recursion desired answers (variable # of RRs)
recursion available
reply is authoritative authority (variable # of RRs)
additional info (variable # of RRs)
Application Layer 2-27
DNS protocol, messages
2 bytes 2 bytes
identification flags
# questions # answer RRs
# authority RRs # additional RRs
name, type fields
questions (variable # of questions)
for a query
RRs in response answers (variable # of RRs)
to query
records for
authority (variable # of RRs)
authoritative servers
additional “helpful” additional info (variable # of RRs)
info that may be used
Application Layer 2-28
14
