第三章TCP-IP协议栈.pptVIP

Purpose: This graphic explains the format of UDP. Emphasize: UDP is simple and efficient but not reliable. The UDP segment format includes a source port, a destination port, a length field, and an optional checksum field. It has no sequencing, acknowledgments, or windowing. Example: TFTP uses a checksum. At the end of the transfer if the checksum does not match then the file did not make it. The user is notified and must type in the command again. As a result, the user has become the reliability mechanism. Transition: The next section discusses the network layer of the OSI model and how it corresponds to the TCP/IP internet layer. Purpose: This figure explains how TCP uses port numbers to connect applications. Emphasize: These port numbers were standardized in RFC 1340. This RFC has been obsoleted by RFC 1700. However, many of the port numbers outlined in RFC 1340 are still being used as standards. It is possible to filter on TCP port numbers. The TCP port number, combined with other information, is what UNIX C language developers call a socket. However, work sockets have different meanings in XNS and Novell, where they are service access point abstractions or programming interfaces rather than service access point identifiers. Purpose: This figure continues to explain how TCP uses port numbers. Emphasize: In most cases the TCP port number on one side of a conversation is the same on the other side. For example, when a file transfer takes place, the software on one host is communicating with a peer application on another host. In this example we see a Telnet (TCP port 23) session. It is possible to have multiple Telnet sessions running simultaneously on a host or router. Telnet selects an unused port number above 1023 to represent the source port for each independent session. Notice that the destination port is still 23. Port numbering is important to understand in order to configure IP extended access lists. The lack of symmetry in port number use is a