1 / 22

Chapter 13

Chapter 13. The Internet. O BJECTIVES. Understand the architecture of today’s Internet and its relation- ship with ISPs. Understand the importance of the TCP/IP protocol suite. Understand the role of IP, UDP, and TCP in the Internet.

chiquita-valdez
Download Presentation

Chapter 13

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 13 The Internet

  2. OBJECTIVES Understand the architecture of today’s Internet and its relation- ship with ISPs. Understand the importance of the TCP/IP protocol suite. Understand the role of IP, UDP, and TCP in the Internet. Understand the difference between the Internet, an intranet, and an extranet. Know how the Internet began. After reading this chapter, the reader should be able to:

  3. 13.1 HISTORY AND ADMINISTRATION

  4. Note: RFCs can be found athttp://www.rfc-editor.org

  5. Figure 13-1 Internet today

  6. Technical Focus:Maturity Levels of an RFC An RFC, during its lifetime, falls into one of six maturity levels: proposed standard, draft standard, Internet standard, historic, experimental, and informational.

  7. Figure 13-2 Internet administration

  8. 13.2 TCP/IP PROTOCOL SUITE

  9. Figure 13-3 TCP/IP protocol suite

  10. Figure 13-4 IP datagram

  11. Technical Focus:Inside the Header of an IP Datagram An IP datagram contains several fields. The most important are the source and destination addresses of the datagram (IP addresses). The header also contains fields related to fragmentation. The size of a datagram may be too large for some LAN or WAN protocols. In this case, the datagram is divided into fragments; each fragment carries the same identification number as well as other information to help the receiver assemble the datagram. The header also has two length fields; one defines the length of the header, the other defines the length of the entire packet. One field that can decrease traffic on the Internet holds the number of routers a packet can visit before it is discarded. The header also contains a checksum field to determine the validity of the packet.

  12. Figure 13-5 Internet address

  13. Technical Focus:Classful versus Classless Addressing With more and more organizations wanting to use the Internet, the Internet authorities are running out of IP addresses. Internet addresses were originally designed as classful addresses. By this, we mean that the total number of 32-bit addresses was divided unevenly into five classes: A, B, C, D, and E. Class A and B contain blocks of addresses with a very large range. Each block is granted to one organization, but most of these organizations never use their allotted number of addresses. This is a tremendous waste of addresses. Recently, a new design called classless addressing has been implemented. In this design, all available addresses are put into a big pool; each organization is granted a range of addresses according to its need.

  14. A part of the Internet Figure 13-6

  15. Figure 13-7 UDP user datagram

  16. Technical Focus:Inside a UDP header The header of the UDP datagram is very simple: it contains only four fields. One field defines the application program that has sent the packet (the source), and another defines the application program that is to receive the packet (the destination). Another field defines the length of the entire packet. The last field carries a checksum for error detection.

  17. Figure 13-8 TCP segment format

  18. Technical Focus:Inside a TCP Segment Header The header of a segment is very complicated and contains optional as well as mandatory fields. We briefly discuss just the required fields. One pair of fields defines the source and destination application programs. Another pair is used for error and flow control; one holds the unique sequence number, and the other holds the acknowledgment number. One field defines the size of the sliding window in the transport layer. The sliding window in the transport layer uses the same concept as the one in the data link layer (see Chapter 5). There are also flags that define the purpose of the segment (for connection establishment, for termination, for acknowledgment, and so on). The last required field carries a checksum for error detection.

  19. 13.3 NEXT GENERATION

  20. 13.3 ACCESS TO THE INTERNET

  21. 13.5 PRIVATE NETWORKS: INTRANET AND EXTRANET

  22. Technical Focus:Network Address Translation (NAT) A technology that is related to private networks is network address translation (NAT). The technology allows a site to use a set of private addresses for internal communication and a set of (at least one) global Internet addresses for communication with other sites.

More Related