1. Computer Networks: Internet Introduction 1 Internet Introduction and HTTP and DNS Examples

2. Computer Networks: Internet Introduction 2 Layering and Abstraction Abstractions can be used to hide complexity.Abstractions can be used to hide complexity. Abstraction naturally leads to layering.Abstraction naturally leads to layering. Layering provides an abstraction for functional locality.Layering provides an abstraction for functional locality. Layering simplifies the design process and adds flexibility when modifying and developing the network.Layering simplifies the design process and adds flexibility when modifying and developing the network.

3. Computer Networks: Internet Introduction 3 Layering and Abstraction Layering accommodates incremental changes.Layering accommodates incremental changes. It is possible to have alternative abstractions at each layer.It is possible to have alternative abstractions at each layer. P&D slide

4. Computer Networks: Internet Introduction 4 Applications and Layered Architectures [LG&W pp.43-49] Applications and Layered Architectures [LG&W pp.43-49] In the 1970’s vendor companies (IBM and DEC) developed proprietary networks with the common feature of grouping communication functions into related and manageable sets called layers. network architecture :: a set of protocols that specify how every layer is to function and well-defined interfaces between the layers.

5. Computer Networks: Internet Introduction 5 The Internet and an internet [LG&W pp.26-28] [LG&W pp.26-28] An internet :: involves the interconnection of multiple networks into a single large networks. The “Internet” :: refers to the successor to ARPANET. IP (the Internet Protocol) :: provides connectionless transfer of packets across an internet.

6. Computer Networks: Internet Introduction 6 G G G G G net 1 net 2 net 3 net 4 net 5 G = gateway G Figure 1.18 Leon-Garcia & Widjaja: Communication Networks Copyright ©2000 The McGraw Hill Companies An internet

7. Computer Networks: Internet Introduction 7 IP Currently provides best-effort serviceCurrently provides best-effort service –packets may be lost (i.e., IP is unreliable). General design philosophyGeneral design philosophy –Keep internal operations simple by relegating complex functions to the edge of the subnet. –IP can operate over any network. –allow IP to scale!!! –The end-to-end mechanisms are responsible for recovery of packet losses and congestion control.

8. Computer Networks: Internet Introduction 8 IPv4 Network IDHost ID 4 bytes Uses hierarchical address space with location information embedded in the structure.Uses hierarchical address space with location information embedded in the structure. IP address is usually expressed in dotted- decimal notation (e.g., 128.100.11.56).IP address is usually expressed in dotted- decimal notation (e.g., 128.100.11.56).

9. Computer Networks: Internet Introduction 9 The Internet Provides a name space to refer to machines connected to the Internet (e.g. chablis.cs.wpi.edu).Provides a name space to refer to machines connected to the Internet (e.g. chablis.cs.wpi.edu). The name space is hierarchical, but it is only administrative. The name space is not used in network routing operations.The name space is hierarchical, but it is only administrative. The name space is not used in network routing operations. DNS (Domain Name Service) provides automatic translation of names to IP addresses.DNS (Domain Name Service) provides automatic translation of names to IP addresses.

10. Computer Networks: Internet Introduction 10 Internet Architecture Defined by the Internet Engineering Task Force (IETF).Defined by the Internet Engineering Task Force (IETF). Referred to as an “Hourglass” design.Referred to as an “Hourglass” design. Application vs Application Protocol (FTP, HTTP)Application vs Application Protocol (FTP, HTTP) ■ ■ ■ FTP TCP UDP IP NET 1 2 n HTTPNVTFTP P&D slide

11. Computer Networks: Internet Introduction 11 TCP/IP Architecture Model DCC 6 th Ed., W. Stallings Figure 1.9

12. Computer Networks: Internet Introduction 12 HTTP SMTP RTP TCP UDP IP Network Interface 1 Network Interface 3 Network Interface 2 DNS Figure 2.1 2 Leon-Garcia & Widjaja: Communication NetworksCopyright ©2000 The McGraw Hill Companies

13. Computer Networks: Internet Introduction 13 Interfaces P&D slide

14. 14 Protocol Machinery Protocol GraphProtocol Graph –most peer-to-peer communication is indirect –peer-to-peer is direct only at hardware level Host 1Host 2 File application Digital library application Video application File application Digital library application Video application P&D slide Computer Networks: Internet Introduction

15. 15 ISO Architecture P&D slide

16. Computer Networks: Internet Introduction 16 Layering Example Client/server relationship –Server process waits for incoming requests by listening to a port. –Client process makes requests as required. –Server process provides responses to these requests. –The server process usually runs in the background as a daemon (e.g. httpd is the server daemon for HTTP).

17. Computer Networks: Internet Introduction 17 HTTP Example HTTP (HyperText Transfer Protocol) specifies rules by which the client and the server interact so as to retrieve a document.HTTP (HyperText Transfer Protocol) specifies rules by which the client and the server interact so as to retrieve a document. The protocol assumes the client and the server can exchange messages directlyThe protocol assumes the client and the server can exchange messages directly The client software needs to set up a two-way connection prior to the HTTP request.The client software needs to set up a two-way connection prior to the HTTP request.

18. Computer Networks: Internet Introduction 18 HTTP server HTTP client Request Response Figure 2.1 HTTP client/server interaction Leon-Garcia & Widjaja: Communication NetworksCopyright ©2000 The McGraw Hill Companies

19. Computer Networks: Internet Introduction 19 HTTP server HTTP client TCP GET 80, # #, 80 STATUS Port 80 Ephemeral Port # Figure 2.2 Leon-Garcia & Widjaja: Communication Networks Copyright ©2000 The McGraw Hill Companies

20. The user clicks on a link to indicate which document is to be retrieved. The browser must determine the address that contains the document. It does this by sending a query to its local name server. Once the address is known the browser establishes a connection to the specified machine, usually a TCP connection. In order for the connection to be successful, the specified machine must be ready to accept TCP connections. The browser runs a client version of HTTP, which issues a request specifying both the name of the document and the possible document formats it can handle. The machine that contains the requested document runs a server version of HTTP. It reacts to the HTTP request by sending an HTTP response which contains the desired document in the appropriate format. The TCP connection is then closed and the user may view the document. 1. 2. 3. 4. 5. 6. Figure 1.4 Copyright ©2000 The McGraw Hill Companies Leon-Garcia & Widjaja: Communication Networks Retrieving a Web Page

21. Computer Networks: Internet Introduction 21 Retrieving a document from the Web 1.User selects document 2.Network software of client locates the server host and establishes a two- way connection. 3.HTTP client sends message requesting document. 4.HTTP daemon listening on TCP port 80 interprets a message. 5.HTTP daemon send a result code and a description of the information that the client will receive GET /infocom/index.html HTTP 1.0 HTTP/1.1 200 OK Server: Apache/1.3.23 (Unix) Content-Length: 414 Content-Type: text-html

22. Computer Networks: Internet Introduction 22 Retrieving a document from the Web 6.HTTP daemon reads the file and sends the requested file through the TCP port. 7. Text is displayed by client browser, which interprets the HTML format. 8. HTTP daemon disconnects the connection after the connection is idle for some timeout period. Infocom ’99 The Future Now …

23. Computer Networks: Internet Introduction 23 DNS query and response 1. Application requests name to address translation. 2. Resolver composes query message. 3. Resolver send UDP datagram encapsulating the query message. 4. DNS server looks up address and prepares response. 5. DNS sends UDP datagram encapsulating the response message. Header: OPCODE=SQUERY Question: QNAME= tesla.comm.toronto.edu., QCLASS=IN, QTYPE=A HEADER: OPCODE=SQUERY, RESPONSE AA Question: QNAME= Tesla.comm.toronto.edu., QCLASS=IN, QTYPE=A Answer: telsa.cmm.toronto.edu. 86400 IN A 128.100.11.56