Internet and Intranet Protocols and Applications Lecture 3: Application Layer 2: , DNS and P2P February 1, 2005 Arthur Goldberg Computer Science Department New York University

2 Chapter 2 Application Layer Computer Networking: A Top Down Approach Featuring the Internet, 3 rd edition. Jim Kurose, Keith Ross Addison-Wesley, July 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 can add, modify, and delete slides (including this one) and slide content to suit your needs. They obviously represent a lot of work on our part. In return for use, we only ask the following:  If you use these slides (e.g., in a class) in substantially unaltered form, that you mention their source (after all, we’d like people to use our book!)  If you post any slides in substantially unaltered form on a www site, that you note that they are adapted from (or perhaps identical to) our slides, and note our copyright of this material. Thanks and enjoy! JFK/KWR All material copyright J.F Kurose and K.W. Ross, All Rights Reserved

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

2: Application Layer4 Electronic Mail Three major components: r user agents r mail servers r simple mail transfer protocol: SMTP User Agent r a.k.a. “mail reader” r composing, editing, reading mail messages r e.g., Eudora, Outlook, elm, Netscape Messenger r outgoing, incoming messages stored on server user mailbox outgoing message queue mail server user agent user agent user agent mail server user agent user agent mail server user agent SMTP

2: Application Layer5 Electronic Mail: mail servers Mail Servers r mailbox contains incoming messages for user r message queue of outgoing (to be sent) mail messages r SMTP protocol between mail servers to send messages m client: sending mail server m “server”: receiving mail server mail server user agent user agent user agent mail server user agent user agent mail server user agent SMTP

2: Application Layer6 Electronic Mail: SMTP [RFC 2821] r uses TCP to reliably transfer message from client to server, port 25 r direct transfer: sending server to receiving server r three phases of transfer m handshaking (greeting) m transfer of messages m closure r command/response interaction m commands: ASCII text m response: status code and phrase r messages must be in 7-bit ASCII

2: Application Layer7 Scenario: Alice sends message to Bob 1) Alice uses UA to compose message and “to” 2) Alice’s UA sends message to her mail server; message placed in message queue 3) Client side of SMTP opens TCP connection with Bob’s mail server 4) SMTP client sends Alice’s message over the TCP connection 5) Bob’s mail server places the message in Bob’s mailbox 6) Bob invokes his user agent to read message user agent mail server mail server user agent

2: Application Layer8 Sample SMTP interaction S: 220 hamburger.edu C: HELO crepes.fr S: 250 Hello crepes.fr, pleased to meet you C: MAIL FROM: S: 250 Sender ok C: RCPT TO: S: 250 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

2: Application Layer9 Try SMTP interaction for yourself:  telnet servername 25 r see 220 reply from server r enter HELO, MAIL FROM, RCPT TO, DATA, QUIT commands above lets you send without using client (reader)

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

2: Application Layer11 Mail message format SMTP: protocol for exchanging msgs RFC 822: standard for text message format: r header lines, e.g., m To: m From: m Subject: different from SMTP commands! r body m the “message”, ASCII characters only header body blank line

2: Application Layer12 Message format: multimedia extensions r MIME: multimedia mail extension, RFC 2045, 2056 r additional lines in msg header declare MIME content type From: To: Subject: Picture of yummy crepe. MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Type: image/jpeg base64 encoded data base64 encoded data multimedia data type, subtype, parameter declaration method used to encode data MIME version encoded data

2: Application Layer13 Mail access protocols r SMTP: delivery/storage to receiver’s server r Mail access protocol: retrieval from server m POP: Post Office Protocol [RFC 1939] authorization (agent server) and download m IMAP: Internet Mail Access Protocol [RFC 3501] more features (more complex) manipulation of stored messages on server m HTTP: Hotmail, Yahoo! Mail, etc. user agent sender’s mail server user agent SMTP access protocol receiver’s mail server

2: Application Layer14 POP3 protocol authorization phase r client commands:  user: declare username  pass: password r server responses m +OK  -ERR transaction phase, client:  list: list message numbers  retr: retrieve message by number  dele: delete r quit C: list S: S: S:. C: retr 1 S: S:. C: dele 1 C: retr 2 S: S:. C: dele 2 C: quit S: +OK POP3 server signing off S: +OK POP3 server ready C: user bob S: +OK C: pass hungry S: +OK user successfully logged on

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

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

2: Application Layer17 DNS: Domain Name System People: many identifiers: m SSN, name, passport # Internet hosts, routers: m IP address (32 bit) - used for addressing datagrams m “name”, e.g., ww.yahoo.com - used by humans Q: map between IP addresses and name ? Domain Name System: r distributed database implemented in hierarchy of many name servers r application-layer protocol host, routers, name servers to communicate to resolve names (address/name translation) m note: core Internet function, implemented as application-layer protocol m complexity at network’s “edge”

2: Application Layer18 DNS Why not centralize DNS? r single point of failure r traffic volume r distant centralized database r maintenance doesn’t scale! DNS services r Hostname to IP address translation r IP address to Hostname translation r Host aliasing m Canonical and alias names r Mail server aliasing r Load distribution m Replicated Web servers: set of IP addresses for one canonical name m But performs poorly – suppose Aol cached one IP address

2: Application Layer19 Root DNS Servers com DNS servers org DNS serversedu DNS servers poly.edu DNS servers umass.edu DNS servers yahoo.com DNS servers amazon.com DNS servers pbs.org DNS servers Distributed, Hierarchical Database Client wants IP for 1 st approx: r Client queries a root server to find com DNS server r Client queries com DNS server to get amazon.com DNS server r Client queries amazon.com DNS server to get IP address for

2: Application Layer20 DNS: Root name servers r contacted by local name server that cannot resolve name r root name server: m contacts authoritative name server if name mapping not known m gets mapping m returns mapping to local name server 84 root name servers worldwide See b USC-ISI Marina del Rey, CA l ICANN Los Angeles, CA e NASA Mt View, CA f Internet Software C. Palo Alto, CA (and 17 other locations) i Autonomica, Stockholm (plus 3 other locations) k RIPE London (also Amsterdam, Frankfurt) m WIDE Tokyo a Verisign, Dulles, VA c Cogent, Herndon, VA (also Los Angeles) d U Maryland College Park, MD g US DoD Vienna, VA h ARL Aberdeen, MD j Verisign, ( 11 locations)

2: Application Layer21 TLD and Authoritative Servers r Top-level domain (TLD) servers: responsible for com, org, net, edu, etc, and all top-level country domains uk, fr, ca, jp m Network solutions maintains servers for com TLD m Educause for edu TLD r Authoritative DNS servers: organization’s DNS servers, providing authoritative hostname to IP mappings for organization’s servers (e.g., Web and mail) m Can be maintained by organization or service provider

2: Application Layer22 Local Name Server r Does not strictly belong to hierarchy r Each ISP (residential ISP, company, university) has one m Also called “default name server” r When a host makes a DNS query, query is sent to its local DNS server m Acts as a proxy, forwards query into hierarchy

2: Application Layer23 requesting host cis.poly.edu gaia.cs.umass.edu root DNS server local DNS server dns.poly.edu authoritative DNS server dns.cs.umass.edu 7 8 TLD DNS server Example r Host at cis.poly.edu wants IP address for gaia.cs.umass.edu 1. Find gaia.cs.umass.edu 2. Find gaia.cs.umass.edu 3. List of IPs for TLD servers for edu 4. Find gaia.cs.umass.edu 5. IP for authoritative server for umass.edu 6. Find gaia.cs.umass.edu 7. IP for gaia.cs.umass.edu 8. IP for gaia.cs.umass.edu

2: Application Layer24 requesting host cis.poly.edu gaia.cs.umass.edu root DNS server local DNS server dns.poly.edu authoritative DNS server dns.cs.umass.edu 7 8 TLD DNS server 3 Recursive queries recursive query: r Name server finds answer r puts burden of name resolution on contacted name server r heavy load? iterated query: r contacted server replies with name of server to contact r “I don’t know this name, but ask this server”

2: Application Layer25 DNS: caching and updating records r When a name server learns a mapping, it caches the mapping m A server discards cached entries after a timeout (typically 2 days) m TLD servers typically cached in local name servers Thus root name servers queried infrequently r update/notify mechanisms under design by IETF m RFC 2136 m

2: Application Layer26 DNS records DNS: distributed db storing resource records (RR) r Type=NS  name is domain (e.g. foo.com)  value is IP address of authoritative name server for this domain RR format: (name, value, type, ttl) r Type=A  name is hostname  value is IP address r Type=CNAME  name is alias name for some “cannonical” (the real) name is really servereast.backup2.ibm.com  value is cannonical name r Type=MX  value is name of mailserver associated with name

2: Application Layer27 DNS protocol, messages DNS protocol : query and reply messages, both with same message format msg header r identification: 16 bit # for query, reply to query uses same # r flags: m query or reply m recursion desired m recursion available m reply is authoritative

2: Application Layer28 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

2: Application Layer29 Inserting records into DNS r Example: just created startup “Network Utopia” r Register name networkuptopia.com at a registrar (e.g., Network Solutions) m Need to provide registrar with names and IP addresses of your authoritative name server (primary and secondary) m Registrar inserts two RRs into the com TLD server: (networkutopia.com, dns1.networkutopia.com, NS) (dns1.networkutopia.com, , A) r Put in authoritative server Type A record for and Type MX record for networkutopia.com r How do people get the IP address of your Web site?

2: Application Layer30 Chapter 2: Application layer r 2.1 Principles of network applications m app architectures m app requirements r 2.2 Web and HTTP r 2.4 Electronic Mail m SMTP, POP3, IMAP r 2.5 DNS r 2.6 P2P file sharing r 2.7 Socket programming with TCP r 2.8 Socket programming with UDP r 2.9 Building a Web server

2: Application Layer31 P2P file sharing Example r Alice runs P2P client application on her notebook computer r Intermittently connects to Internet; gets new IP address for each connection r Asks for “Hey Jude” r Application displays other peers that have copy of Hey Jude. r Alice chooses one of the peers, Bob. r File is copied from Bob’s PC to Alice’s notebook: HTTP r While Alice downloads, other users uploading from Alice. r Alice’s peer is both a Web client and a transient Web server. All peers are servers = highly scalable!

2: Application Layer32 P2P: centralized directory original “Napster” design 1) when peer connects, it informs central server: m IP address m content 2) Alice queries for “Hey Jude” 3) Alice requests file from Bob centralized directory server peers Alice Bob

2: Application Layer33 P2P: problems with centralized directory r Single point of failure r Performance bottleneck r Copyright infringement file transfer is decentralized, but locating content is highly decentralized

2: Application Layer34 Query flooding: Gnutella r fully distributed m no central server r public domain protocol r many Gnutella clients implementing protocol overlay network: graph r edge between peer X and Y if there’s a TCP connection r all active peers and edges is overlay net r Edge is not a physical link r Given peer will typically be connected with < 10 overlay neighbors

2: Application Layer35 Gnutella: protocol Query QueryHit Query QueryHit Query QueryHit File transfer: HTTP r Query message sent over existing TCP connections r peers forward Query message r QueryHit sent over reverse path Scalability: limited scope flooding

2: Application Layer36 Gnutella: Peer joining 1. Joining peer X must find some other peer in Gnutella network: use list of candidate peers 2. X sequentially attempts to make TCP with peers on list until connection setup with Y 3. X sends Ping message to Y; Y forwards Ping message. 4. All peers receiving Ping message respond with Pong message 5. X receives many Pong messages. It can then setup additional TCP connections Peer leaving: see homework problem!

2: Application Layer37 Exploiting heterogeneity: KaZaA r Each peer is either a group leader or assigned to a group leader. m TCP connection between peer and its group leader. m TCP connections between some pairs of group leaders. r Group leader tracks the content in all its children.

2: Application Layer38 Questions about Gnutella, 1 r What are ‘little-endian’ and ‘big-endian’? Why does the protocol have to specify them? r Unique identifiers: How are unique Descriptor IDs and Servent Identifiers generated? r The spec says (p 3, para 2) “if a servent becomes out of synch with its input stream, it should drop the connection”. How would it know?

2: Application Layer39 Questions about Gnutella, 2 r In the section ‘Descriptor Routing’ on page 5, the spec says “Pong descriptors may only be sent along the same path that carried the incoming Ping descriptor” and “Push descriptors may only be sent along the same path that carried the incoming QueryHit descriptor.” How would this be implemented? r In the section ‘Firewalled Servents’ the spec says “A servent can request a file push by routing a Push request back to the servent that sent the QueryHit descriptor describing the target file.” How is this possible? Isn’t the latter servent behind a firewall?

2: Application Layer40 KaZaA: Querying r Each file has a hash and a descriptor r Client sends keyword query to its group leader r Group leader responds with matches: m For each match: metadata, hash, IP address r If group leader forwards query to other group leaders, they respond with matches r Client then selects files for downloading m HTTP requests using hash as identifier sent to peers holding desired file

2: Application Layer41 Kazaa tricks r Limitations on simultaneous uploads r Request queuing r Incentive priorities r Parallel downloading