Lecture 6 Application Layer. Antonio Cianfrani DIET Department Networking Group netlab.uniroma1.it

Transcription

1 Lecture 6 Application Layer Antonio Cianfrani DIET Department Networking Group netlab.uniroma1.it

2 Application-layer protocols Application: communicating, distributed processes running in network hosts in user space exchange messages to implement app e.g., , file transfer, the Web Application-layer protocols one piece of an app define messages exchanged by apps and actions taken user services provided by lower layer protocols application transport network data link physical application transport network data link physical application transport network data link physical

3 Network applications A process is a program that is running within a host. Within the same host, two processes communicate with interprocess communication defined by the OS. Processes running in different hosts communicate with an application-layer protocol A user agent is an interface between the user and the network application. Web:browser mail reader streaming audio/video: media player

4 Client-server paradigm Client: Typical network app has two pieces: client and server initiates contact with server ( speaks first ) typically requests service from server, for Web, client is implemented in browser; for , in mail reader Server: provides requested service to client e.g., Web server sends requested Web page, mail server delivers e- mail application transport network data link physical request reply application transport network data link physical

5 Application-layer protocols API: application programming interface defines interface between application and transport layer socket: Internet API two processes communicate by sending data into socket, reading data out of socket Q: how does a process identify the other process with which it wants to communicate? IP address of host running other process port number - allows receiving host to determine to which local process the message should be delivered

6 The World Wide Web Web page: consists of objects addressed by a URL Most Web pages consist of: base HTML page, and several referenced objects. Example: page and 5 images URL has two components: host name and path name: User agent for Web is called a browser: Chrome Internet Explorer Firefox Server for Web is called Web server: Apache (public domain) MS Internet Information Server

7 The Web: the http protocol http: hypertext transfer protocol Web s application layer protocol client/server model client: browser that requests, receives, displays Web objects server: Web server sends objects in response to requests http1.0: RFC 1945 http1.1: RFC 2068 PC running Explorer Mac running Navigator Server running NCSA Web server

8 The http protocol: more http: TCP transport service client initiates TCP 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 http is stateless server maintains no information about past client requests Protocols that maintain state are complex! aside past history (state) must be maintained if server/client crashes, their views of state may be inconsistent, must be reconciled

9 Non-persistent and persistent connections Non-persistent server parses request, responds, and closes TCP connection 2 RTTs to fetch each object Each object transfer suffers from slow start Parallel TCP connections. Persistent on same TCP connection: server, parses request, responds, parses new request,.. Client sends requests for all referenced objects as soon as it receives base HTML. Fewer RTTs and less slow start.

10 time http example Suppose user enters URL 1a. http client initiates TCP connection to http server (process) at Port 80 is default for http server. 2. http client sends http request message (containing URL) into TCP connection socket (contains text, references to 10 jpeg images) 1b. http server at host waiting for TCP connection at port 80. accepts connection, notifying client 3. http server receives request message, forms response message containing requested object (somedepartment/home.index), sends message into socket

11 http example (cont.) time 5. http client receives response message containing html file, displays html. Parsing html file, finds 10 referenced jpeg objects 6. Steps 1-5 repeated for each of 10 jpeg objects 4. http server closes TCP connection.

12 http message format: request two types of http messages: request, response http request message: ASCII (human-readable format) request line (GET, POST, HEAD commands) Carriage return, line feed indicates end of message header lines GET /somedir/page.html HTTP/1.1 Host: Connection: close User-agent: Mozilla/4.0 Accept: text/html, image/gif,image/jpeg Accept-language:fr (extra carriage return, line feed)

13 http request message: general format

14 http message format: respone status line (protocol status code status phrase) data, e.g., requested html file header lines HTTP/ OK Connection: Close Date: Thu, 06 Aug :00:15 GMT Server: Apache/1.3.0 (Unix) Last-Modified: Mon, 22 Jun Content-Length: 6821 Content-Type: text/html data data data data data...

15 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 requested document not found on this server 505 HTTP Version Not Supported

16 User-server interaction: authentication Authentication goal: control access to server documents stateless: client must present authorization in each request authorization: typically name, password authorization: header line in request if no authorization presented, server refuses access, sends WWW authenticate: header line in response client usual http request msg 401: authorization req. WWW authenticate: usual http request msg + Authorization:line usual http response msg usual http request msg + Authorization:line usual http response msg server time Browser caches name & password so that user does not have to repeatedly enter it.

17 User-server interaction: cookies server sends cookie to client in response msg Set-cookie: client presents cookie in later requests cookie: server matches presented-cookie with server-stored info authentication remembering user preferences, previous choices client usual http request msg usual http response + Set-cookie: # usual http request msg cookie: # usual http response msg usual http request msg cookie: # usual http response msg server cookiespectific action cookiespectific action

18 User-server interaction: conditional GET Goal: don t send object if client has up-to-date stored (cached) version client: specify date of cached copy in http request If-modified-since: <date> server: response contains no object if cached copy upto-date: HTTP/ Not Modified client http request msg If-modified-since: <date> http response HTTP/ Not Modified http request msg If-modified-since: <date> http response HTTP/ OK <data> server object not modified object modified

19 Web Caches (proxy server) Goal: satisfy client request without involving origin server user sets browser: Web accesses via web cache client sends all http requests to web cache client Proxy server origin server if object at web cache, web cache immediately returns object in http response else requests object from origin server, then returns http response to client client origin server

20 Why Web Caching? Assume: cache is close to client (e.g., in same network) smaller response time: cache closer to client decrease traffic to distant servers link out of institutional/local ISP network often bottleneck institutional network public Internet 10 Mbps access link origin servers 100 Mbps LAN institutional cache

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

22 DNS name servers Why not centralize DNS? single point of failure traffic volume distant centralized database maintenance doesn t scale! no server has all nameto-ip address mappings local name servers: each ISP, company has local (default) name server host DNS query first goes to local name server authoritative name server: for a host: stores that host s IP address, name can perform name/address translation for that host s name

23 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 13 designated Root name servers worldwide

24 Simple DNS example root name server host surf.eurecom.fr wants IP address of gaia.cs.umass.edu 1. Contacts its local DNS server, dns.eurecom.fr 2. dns.eurecom.fr contacts root name server, if necessary 3. root name server contacts authoritative name server, dns.umass.edu, if necessary local name server dns.eurecom.fr requesting host surf.eurecom.fr authoritative name server dns.umass.edu gaia.cs.umass.edu

25 DNS example root name server Root name server: may not know authoratiative name server may know intermediate name server: who to contact to find authoritative name server local name server dns.eurecom.fr intermediate name server dns.umass.edu 4 5 requesting host surf.eurecom.fr authoritative name server dns.cs.umass.edu gaia.cs.umass.edu

26 DNS: iterated queries root name server recursive query: puts burden of name resolution on contacted name server heavy load? iterated query iterated query: contacted server replies with name of server to contact I don t know this name, but ask this server local name server dns.eurecom.fr 1 8 requesting host surf.eurecom.fr intermediate name server dns.umass.edu 5 6 authoritative name server dns.cs.umass.edu gaia.cs.umass.edu

27 DNS records DNS: distributed db storing resource records (RR) RR format: (name, value, type,ttl) Type=A name is hostname value is IP address Type=NS name is domain (e.g. foo.com) value is IP address of authoritative name server for this domain Type=CNAME name is an alias name for some canonical (the real) name value is canonical name Type=MX value is hostname of mailserver associated with name

28 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

29 DNS protocol, messages Name, type fields for a query RRs in reponse to query records for authoritative servers additional helpful info that may be used