Application 1 - Networking

CMPT 371 Data Communications and Networking
Chapter 2 Application Layer
2: Application Layer
Chapter 2: Application Layer

Our goals: conceptual, implementation aspects of network application protocols transport-layer service models client-server paradigm
learn about protocols
by examining popular application-level protocols
HTTP FTP SMTP / POP3 / IMAP DNS
programming network
peer-to-peer paradigm
applications
socket API
Chapter 2 outline
2.1 Principles of app layer protocols
2.2 Web and HTTP

2.3 FTP 2.4 Electronic Mail SMTP, POP3, IMAP 2.5 DNS 2.6 Content distribution Network Web caching Content distribution networks P2P file sharing
Network applications
Applications -> Software What exactly running in a computer ?
Network applications: some jargon

Process: program running within a host.
implements user within same host, two
interface & application-level protocol

Web: browser E-mail: mail reader streaming audio/video: media player
processes communicate using interprocess communication (defined by OS). processes running in different hosts communicate with an application-layer protocol
Applications and application-layer protocols

Application: communicating, distributed processes

application transport network data link physical
Application-layer protocols

e.g., e-mail, Web, P2P file sharing, instant messaging running in end systems (hosts) exchange messages to implement application
one piece of an app define messages exchanged by apps and actions taken use communication services provided by lower layer protocols (TCP, UDP)
App-layer protocol defines

Types of messages
exchanged, e.g., request & response messages Syntax of message types: what fields in messages & how fields are delineated Semantics of the fields, i.e., meaning of information in fields Rules for when and how processes send & respond to messages
Public-domain protocols: defined in RFCs allows for interoperability eg, HTTP, SMTP Proprietary protocols: eg, Skype BitTorrent (?)
Client-server paradigm
Typical network app has two pieces: client and server Client:
initiates contact with server
request
(speaks first) typically requests service from server, Web: client implemented in browser; e-mail: in mail reader
reply
Server:
provides requested service to client e.g., Web server sends requested Web
page, mail server delivers e-mail
Programming - Socket
process sends/receives
messages to/from its socket socket analogous to door
host or server controlled by app developer
host or server
process
process
socket socket sending process shoves TCP/UDP TCP/UDP message out door Internet with with buffers, buffers, sending process assumes variables variables transport infrastructure on other side of door which controlled brings message to socket by OS at receiving process API: Application Programmers Interface (1) choose transport protocol; (2) set parameters (You might have learnt it; or you can study it in 471)
2: Application Layer 9
Outside of the door Transport Layer Service

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 effective
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
10
Transport service requirements of common apps

Application file transfer e-mail Web documents real-time audio/video Data loss no loss no loss no loss loss-tolerant loss-tolerant loss-tolerant no loss Bandwidth Time Sensitive no no no yes, 100s msec
stored audio/video interactive games instant messaging
elastic elastic elastic audio: 5kbps-1Mbps video:10kbps-5Mbps same as above few kbps up elastic
yes, few secs yes, 100s msec yes and no
11
Internet apps: application, transport protocols

Application Application layer protocol SMTP [RFC 2821] Telnet [RFC 854] HTTP [RFC 2616] FTP [RFC 959] proprietary (e.g. RealNetworks) proprietary (e.g., Dialpad) Underlying transport protocol TCP TCP TCP TCP TCP or UDP
e-mail remote terminal access Web file transfer streaming multimedia

Internet telephony
typically UDP
12
Chapter 2 outline
2.2 Web and HTTP

13
Web and HTTP

First some jargon Web page consists of objects Object can be HTML file, JPEG image, Java applet, audio file, Most Web sites have a base HTML-file which includes several referenced objects Each object is addressable by a URL Example URL: http://www.cs.sfu.ca/~jcliu/cmpt371/index.htm
host name
path name
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
PC running Explorer
Server running Apache Web server
Mac running Navigator
15
Is it difficult to write a Browser ?

MS Internet Explorer Safari Opera http://www.opera.com/ (15.3MB) Mozilla http://www.mozilla.org/ (11.7MB) FireFox http://www.mozilla.com/en-US/firefox/ Chrome
16
Trying out HTTP (client side) for yourself

1. Telnet to your favorite Web server:
telnet www.cs.sfu.ca 80
Opens TCP connection to port 80 (default HTTP server port) at www.cs.sfu.ca

Anything typed in sent to port 80
2. Type in a GET HTTP request:

GET or GET /~jcliu/index.htm
You have sent this minimal (but complete) GET request to HTTP server And you have received HTML objects !
Is it difficult to write a Browser ?

Internet Explorer Chrome FireFox
Implement HTTP - network Implement a GUI - local
Anymore ?
Efficiency, fault-tolerant, compatibility, security, Javasupport, multi-language
18
HTTP overview (continued)

Uses TCP:
client initiates TCP
HTTP is stateless
server maintains no
connection (creates socket) to server, port 80 server accepts TCP connection from client HTTP messages (applicationlayer protocol messages) exchanged between browser (HTTP client) and Web server (HTTP server) TCP connection closed
information about past client requests
Protocols that maintain state are complex! past history (state) must be maintained if server/client crashes, their views of state may be inconsistent, must be reconciled
aside
19
HTTP request message

two types of HTTP messages:
request, response
HTTP request message: ASCII (human-readable format)

request line (GET, POST, HEAD commands)
GET /somedir/page.html HTTP/1.1 Host: www.someschool.edu User-agent: Mozilla/4.0 header Connection: close lines Accept-language:fr (extra carriage return, line feed)
Carriage return, line feed indicates end of message
20
HTTP request message: general format
21
Uploading form input

Post method: Web page often includes form input Input is uploaded to server in entity body URL method: Uses GET method Input is uploaded in URL field of request line:
www.somesite.com/animalsearch?monkeys&banana
22
Method types
HTTP/1.0 GET POST HEAD
HTTP/1.1 GET, POST, HEAD PUT
asks server to leave requested object out of response debugging
uploads file in entity body to path specified in URL field
DELETE deletes file specified in the URL field
23
HTTP response message

status line (protocol status code status phrase) header lines 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 data data data data data ...
data, e.g., requested HTML file
24
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 requested object moved, new location specified later in this message (Location:) request message not understood by server requested document not found on this server
301 Moved Permanently
400 Bad Request
404 Not Found
505 HTTP Version Not Supported

25
HTTP connections
Nonpersistent HTTP At most one object is sent over a TCP connection. HTTP/1.0 uses nonpersistent HTTP Persistent HTTP Multiple objects can be sent over single TCP connection between client and server. HTTP/1.1 uses persistent connections in default mode
26
Nonpersistent HTTP
(contains text, Suppose user enters URL references to 10 www.someSchool.edu/someDepartment/home.index jpeg images)
1a. HTTP client initiates TCP
connection to HTTP server (process) at www.someSchool.edu on port 80
1b. HTTP server at host
2. HTTP client sends HTTP
www.someSchool.edu waiting for TCP connection at port 80. accepts connection, notifying client
request message (containing

URL) into TCP connection socket. Message indicates that client wants object someDepartment/home.index
3. HTTP server receives request

message, forms response message containing requested object, and sends message into its socket
time
Nonpersistent HTTP (cont.)

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

of 10 jpeg objects
28
Response time modeling

Definition of RTT: time to send a small packet to travel from client to server and back. Response time: one RTT to initiate TCP connection one RTT for HTTP request and first few bytes of HTTP response to return file transmission time total = 2RTT+transmit time
initiate TCP connection RTT request file RTT file received time time time to transmit file
29
Nonpersistent HTTP issues

requires at least 2 RTTs per object so browsers often open parallel TCP connections
to fetch referenced objects but OS must work and allocate host resources for each TCP connection
30
Persistent HTTP
response subsequent HTTP messages between same client/server are sent over connection Persistent without pipelining: client issues new request only when previous response has been received one RTT for each referenced object Persistent with pipelining: default in HTTP/1.1 client sends requests as soon as it encounters a referenced object as little as one RTT for all the referenced objects
server leaves connection open after sending
User-server interaction: authorization

Authorization : control access to server client server content usual http request msg authorization credentials: typically name, password 401: authorization req. WWW authenticate: stateless: client must present authorization in each request authorization: header line in usual http request msg + Authorization: <cred> each request if no authorization: header, usual http response msg server refuses access, sends
WWW authenticate:
header line in response
usual http request msg + Authorization: <cred>
usual http response msg
time
32
Cookies: keeping state

Many Web sites use cookies Example:
You access Internet always from same PC You visit a specific ecommerce site for first time When initial HTTP requests arrives at site, site creates a unique ID and creates an entry in backend database for ID
33
Cookies: keeping state

Many major Web sites use cookies Four components:
1) cookie header line in the HTTP response message 2) cookie header line in HTTP request message 3) cookie file kept on users host and managed by users browser 4) back-end database at Web site
Cookies: keeping state (cont.)

client
Cookie file ebay: 8734 Cookie file amazon: 1678 ebay: 8734
server
server creates ID 1678 for user cookiespecific action cookiespectific action
usual http request msg usual http response +
Set-cookie: 1678
usual http request msg
cookie: 1678
one week later:

Cookie file amazon: 1678 ebay: 8734
usual http request msg
cookie: 1678
Cookies (continued)
What cookies can bring: authorization shopping carts recommendations user session state (Web e-mail) Cookies and privacy: cookies permit sites to learn a lot about you you may supply name and e-mail to sites search engines use redirection & cookies to learn yet more advertising companies obtain info across sites
aside
Cookies: Enable/Disable
37
Cookies: Delelte
38
Chapter 2 outline
2.2 Web and HTTP

39
FTP: the file transfer protocol

FTP FTP user client interface local file system
file transfer
FTP server
remote file system
user at host
transfer file to/from remote host client/server model
remote) server: remote host ftp: RFC 959 ftp server: port 21
client: side that initiates transfer (either to/from
40
FTP: separate control, data connections

FTP client contacts FTP
server at port 21, specifying TCP as transport protocol Client obtains authorization over control connection Client browses remote directory by sending commands over control connection. When server receives a command for a file transfer, the server opens a TCP data connection to client After transferring one file, server closes connection.
TCP control connection port 21
FTP client
TCP data connection port 20
FTP server
Server opens a second TCP
data connection to transfer another file. Control connection: out of band FTP server maintains state: current directory, earlier authentication
FTP commands, responses

Sample commands:
sent as ASCII text over
Sample return codes

status code and phrase (as

control channel USER username PASS password
LIST return list of file in
current directory (gets) file
RETR filename retrieves
STOR filename stores
(puts) file onto remote host
in HTTP) 331 Username OK, password required 125 data connection already open; transfer starting 425 Cant open data connection 452 Error writing file
42
FTP Client Software
43
Port 21 ?
44
Secure FTP (http://www.ssh.com/)
ssh never trusts the net; somebody hostile who has taken over the network can only force ssh to disconnect, but cannot decrypted or play back the traffic, or hijack the connection.
SSH
46
Key differences between HTTP & FTP

Stateless vs. stateful
Inband control vs. outband control

Why ?
47
Chapter 2 outline
2.2 Web and HTTP

48
Electronic Mail
Three major components:
user agents
mail servers mail transfer protocol
mail server user agent
outgoing message queue user mailbox
user agent mail server
User Agent a.k.a. mail reader composing, editing, reading mail messages e.g., Eudora, Outlook, elm, Netscape Messenger outgoing, incoming messages stored on server
user agent
mail server user agent
user agent
user agent
49
Electronic Mail: mail servers

Mail Servers
mailbox contains incoming
?
mail server
user agent
messages for user message queue of outgoing (to be sent) mail messages SMTP protocol between mail servers to send email messages client: sending mail server server: receiving mail server
SMTP SMTP
mail server
user agent mail server user agent
SMTP
user agent
user agent
user agent
50
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
messages must be in 7-bit ASCII
51
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 user agent 2
mail server 3
mail server 4 5 6
user agent
52
Sample SMTP interaction

S: C: S: C: S: C: S: C: S: C: C: C: S: C: S: 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
Try SMTP interaction for yourself:

telnet servername 25
54
Try SMTP interaction for yourself:

telnet smtp.sfu.ca 25
(mailgate.sfu.ca 465
info.html
http://www.sfu.ca/itservices/sfuconnect/getstarted/accessmethods/ssl_background_
SSLv2
) see 220 reply from server enter HELO, MAIL FROM, RCPT TO, DATA, QUIT commands above lets you send email without using email client (reader) -- note: SFU IT service has upgraded their system and now supports only SSL connections
Message format: multimedia extensions

ASCII: http://www.asciitable.com/ MIME: multimedia mail extension, RFC 2045, 2056 additional lines in msg header declare MIME content type
MIME version method used to encode data multimedia data type, subtype, parameter declaration
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 base64 encoded data ..... ......................... ......base64 encoded data
encoded data
56
MIME types
Content-Type: type/subtype; parameters Text Video
example subtypes: plain,
html
example subtypes: mpeg,
quicktime
Image
gif
example subtypes: jpeg,
Application
other data that must be
Audio
example subtypes: basic
(8-bit mu-law encoded), 32kadpcm (32 kbps coding)
processed by reader before viewable example subtypes: msword, octet-stream
57
Multipart Type
From: alice@crepes.fr To: bob@hamburger.edu Subject: Picture of yummy crepe. MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=StartOfNextPart --StartOfNextPart Dear Bob, Please find a picture of a crepe. --StartOfNextPart Content-Transfer-Encoding: base64 Content-Type: image/jpeg base64 encoded data ..... ......................... ......base64 encoded data --StartOfNextPart Do you want the recipe?
58
MIME types
Content-Type: type/subtype; parameters
An Example: MailEncodingExample.txt
------=_NextPart_000_0010_8CEC7DC6.92E25D8C Content-Type: application/octet-stream; name="readme.scr" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="readme.scr"
TVqQAAMAAAAEAAAA//8AALgAAAAAAAAAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAqAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAUEUA AEwBAwAAAAAAAAAAAAAAAADgAA8BCwEHAABQAAAAEAAAAGAAAGC+AAAAcAAAAMAAAAAASgAAEAAA AAIAAAQAAAAAAAAABAAAAAAAAAAA0AAAABAAAAAAAAACAAAAAAAQAAAQAAAAABAAABAAAAAAAAAQ AAAAAAAAAAAAAADowQAAMAEAAADAAADoAQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAABVUFgwAAAAAABgAAAAEAAAAAAAAAAEAAAAAAAAAAAAAAAAAACAAADg VVBYMQAAAAAAUAAAAHAAAABQAAAABAAAAAAAAAAAAAAAAAAAQAAA4C5yc3JjAAAAABAAAADAAAAA BAAAAFQAAAAAAAAAAAAAAAAAAEAAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
59
Coding for MIME

Key issue: Binary data (bit string) to plain text (SMTP message)
Simple solution: 8 bit -> one plain text symbol (?)
60
ASCII Table
Beyond 7 bit?

Extended ASCII Never well defined
61
Base 64 coding more info (RFC1521)

A 65-character subset of US-ASCII is used, enabling 6 bits to be represented per printable character. (The extra 65th character, "=", is used to signify a special processing function.)
NOTE: This subset has the important property that it is represented identically in all versions of ISO 646, including US ASCII, and all characters in the subset are also represented identically in all versions of EBCDIC. Other popular encodings, such as the encoding used by the uuencode utility and the base85 encoding specified as part of Level 2 PostScript, do not share these properties, and thus do not fulfill the portability requirements a binary transport encoding for mail must meet.
62
Base 64 coding more info (RFC1521)

The 64 characters
A-Z a-z 0-9 + / =
63
Mail access protocols

user agent
SMTP
user agent
senders mail server
receivers mail server
64
Mail access protocols

user agent
SMTP
SMTP
access protocol
user agent
senders mail server
receivers mail 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) manipulation of stored msgs on server HTTP: Hotmail , Yahoo! Mail, etc.
WebMail
Hotmail/Gmail
SFU Webmail:
webmail.sfu.ca (old)/connect.sfu.ca
66
POP3 protocol
authorization phase
client commands:
user: declare username pass: password server responses +OK -ERR
S: C: S: C: S: C: S: S: S: C: S: S: C: C: S: S: C: C: S:
+OK POP3 server ready user bob +OK pass hungry +OK user successfully logged 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
on
transaction phase, client:

number dele: delete quit
list: list message numbers retr: retrieve message by
67
POP3 (more) and IMAP

More about POP3 Previous example uses download and delete mode. Bob cannot re-read email if he changes client Download-and-keep: copies of messages on different clients POP3 is stateless across sessions newpop.sfu.ca 995 SSLv2 IMAP IMAP keeps user state across sessions:
names of folders and mappings between message IDs and folder name
Allows user to
organize messages in folders Partial retrieving header

Chapter 2 outline
2.2 Web and HTTP

69
Name vs. ID
People: many identifiers: name, passport #, driving license ID, SIN Example:
I want to talk to J.C. Liu. -- from Friend
Please tell me you driving license ID. -- from Visa card service
70
DNS: Domain Name System

People: many identifiers:
Domain Name System:
SIN, name, passport #

IP address (32 bit) used for addressing datagrams name, e.g., gaia.cs.umass.edu - used by humans
distributed database
Internet hosts, routers:
implemented in hierarchy of many name servers
application-layer protocol
Q: map between IP addresses and name ?
host, routers, name servers to communicate to resolve names (address/name translation) note: core Internet function, implemented as application-layer protocol complexity at networks edge
DNS name servers

Centralize DNS? No single point of failure traffic volume distant centralized database maintenance doesnt scale!
no server has all name-
to-IP address mappings local name servers:
each ISP, company has
local (default) name server

host DNS query first goes to local name server for a host: stores that hosts IP address, name can perform name/address translation for that hosts name
authoritative name server:

DNS: Client Settings
73
DNS name servers

local name servers:
each ISP, company has local (default) name server host DNS query first goes to local name server for a host: stores that hosts IP address, name can perform name/address translation for that hosts name
authoritative name server:
no server has all name-to-IP address mappings
74
DNS: Root name servers

contacted by local name server that can not resolve name root DNS server:
contacts authoritative name server if name mapping not known gets mapping returns mapping to local name server
a NSI Herndon, VA c PSInet Herndon, VA d U Maryland College Park, MD g DISA Vienna, VA h ARL Aberdeen, MD
j NSI (TBD) Herndon, VA
k RIPE London i NORDUnet Stockholm m WIDE Tokyo
e NASA Mt View, CA f Internet Software C. Palo Alto,

CA
b USC-ISI Marina del Rey, CA l ICANN Marina del Rey, CA
13 root name servers worldwide
75
Simple DNS example

host surf.eurecom.fr wants IP address of gaia.cs.umass.edu
2
root name server
4 5 3
1. contacts its local DNS server, dns.eurecom.fr 2. dns.eurecom.fr contacts local name server dns.eurecom.fr root name server, if necessary 1 6 3. root name server contacts authoritative name server, dns.umass.edu, if requesting host necessary
surf.eurecom.fr
authorititive name server dns.umass.edu
gaia.cs.umass.edu
76
DNS example
Root name server:
may not know
root name server
2 7 3
authoritative name server may know
intermediate name server: who to
local name server

dns.eurecom.fr
contact to find authoritative name server
intermediate name server dns.umass.edu
requesting host
surf.eurecom.fr
authoritative name server dns.cs.umass.edu
gaia.cs.umass.edu
DNS: iterated queries

recursive query:
puts burden of name
root name server iterated query 3 4 7
resolution on contacted name server heavy load?
local name server

dns.eurecom.fr
iterated query:
contacted server
intermediate name server dns.umass.edu
replies with name of server to contact I dont know this name, but ask this server
requesting host
surf.eurecom.fr
authoritative name server dns.cs.umass.edu
gaia.cs.umass.edu
DNS: caching and updating records

once (any) name server learns mapping, it
mapping cache entries timeout (disappear) after some time update/notify mechanisms under design by IETF
caches
RFC 2136
http://www.ietf.org/html.charters/dnsind-charter.html
79
DNS records
DNS: distributed db storing resource records (RR) RR format: (name,
Type=A name is hostname value is IP address
value, type,ttl)
Type=NS servereast.backup2.ibm.com name is domain (e.g. value is canonical name foo.com) value is IP address of Type=MX authoritative name value is name of mailserver server for this domain associated with name
Type=CNAME name is alias name for some canonical (the real) name www.ibm.com is really
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 reply is authoritative
81
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
82

Application 1 - Networking

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Application 1 - Networking

Hochgeladen von

Copyright:

Verfügbare Formate

CMPT 371 Data Communications and Networking

Chapter 2 Application Layer

Chapter 2: Application Layer

learn about protocols

by examining popular application-level protocols

HTTP FTP SMTP / POP3 / IMAP DNS

2.2 Web and HTTP

Network applications: some jargon

interface & application-level protocol

Web: browser E-mail: mail reader streaming audio/video: media player

Applications and application-layer protocols

application transport network data link physical

application transport network data link physical

App-layer protocol defines

page, mail server delivers e-mail

messages to/from its socket socket analogous to door

host or server controlled by app developer

Outside of the door Transport Layer Service

Transport service requirements of common apps

stored audio/video interactive games instant messaging

yes, few secs yes, 100s msec yes and no

Internet apps: application, transport protocols

e-mail remote terminal access Web file transfer streaming multimedia

2.2 Web and HTTP

Web and HTTP

Server running Apache Web server

Mac running Navigator

Is it difficult to write a Browser ?

Trying out HTTP (client side) for yourself

Opens TCP connection to port 80 (default HTTP server port) at www.cs.sfu.ca

2. Type in a GET HTTP request:

Is it difficult to write a Browser ?

Efficiency, fault-tolerant, compatibility, security, Javasupport, multi-language

HTTP overview (continued)

information about past client requests

HTTP request message

HTTP request message: ASCII (human-readable format)

Carriage return, line feed indicates end of message

HTTP request message: general format

Uploading form input

HTTP/1.1 GET, POST, HEAD PUT

asks server to leave requested object out of response debugging

uploads file in entity body to path specified in URL field

DELETE deletes file specified in the URL field

HTTP response message

data, e.g., requested HTML file

HTTP response status codes

301 Moved Permanently

400 Bad Request

404 Not Found

505 HTTP Version Not Supported

1a. HTTP client initiates TCP

connection to HTTP server (process) at www.someSchool.edu on port 80

1b. HTTP server at host

2. HTTP client sends HTTP

request message (containing

3. HTTP server receives request

Nonpersistent HTTP (cont.)

time 6. Steps 1-5 repeated for each

Response time modeling

Nonpersistent HTTP issues

server leaves connection open after sending

User-server interaction: authorization

header line in response