Internet protocol stack.pptVIP

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 2: Application Layer * 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) 2: Application Layer * Mail access protocols SMTP: delivery/storage to receiver’s 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: gmail, Hotmail, Yahoo! Mail, etc. user agent sender’s mail server user agent SMTP SMTP access protocol receiver’s mail server 2: Application Layer * DNS: Domain Name System People: many identifiers: SSN, name, passport # Internet hosts, routers: IP address (32 bit) - used for addressing datagrams “name”, e.g., - 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” 2: Application Layer * DNS Why not centralize DNS? single point of failure traffic volume distant centralized database maintenance doesn’t scale! DNS services hostname to IP address translation host aliasing Canonical, alias names mail server aliasing load distribution replicated Web servers: set of IP addresses for one canonical name 2: Application Layer * Domain Name Hierarchy com edu net gov int mil org ae us za ... ... rutgers yale cs www yahoo cnn Generic Domains Country Domains 2: Application Layer * Root DNS Servers com DNS servers org DNS servers edu DNS servers DNS servers DNS servers DNS servers DNS servers DNS servers Distributed, Hierarchical Datab