TCP/IP详解第一卷：协议解析

3星 · 超过75%的资源需积分: 49 167 浏览量更新于2024-08-01 收藏 2.33MB PDF 举报

"TCP/IP详解第一卷(英文版).pdf" 是一本关于TCP/IP协议的权威著作，由W. Richard Stevens撰写。这本书共423页，内容涵盖了TCP/IP协议的基础知识，包括各层协议、互联网地址、域名系统、封装、多路分解、客户端-服务器模型、端口号、标准化过程、RFC文档、标准服务、互联网实现、应用编程接口、测试网络等。在第一章"Introduction"中，作者介绍了TCP/IP的基本概念，如分层架构，TCP/IP协议栈的层次结构，以及互联网地址的重要性。他还讨论了域名系统（DNS）的工作原理，如何通过封装将不同层的数据包组合在一起，以及如何通过多路分解将数据包发送到正确的目的地。此外，还介绍了客户端-服务器模型，端口号的作用，标准化的过程（如RFC文档），以及一些基本的互联网服务。第二章"Link Layer"专注于链路层，讲解了以太网和IEEE 802封装，以及SLIP（串行线IP）、压缩SLIP和PPP（点对点协议）等串行通信协议。还提到了环回接口、最大传输单元（MTU）和路径MTU的概念，以及如何计算串行线路的吞吐量。第三章"IP: Internet Protocol"深入探讨了互联网协议IP，包括IP头部的结构，IP路由的工作方式，子网寻址的重要性，子网掩码的使用，特殊IP地址的情况，以及一些命令行工具如`ifconfig`和`netstat`的用法。同时展望了IP的未来发展趋势。第四章"ARP: Address Resolution Protocol"则聚焦于地址解析协议ARP，这是一个用于将IP地址转换为物理地址的关键协议，对于理解数据包在网络中的传输至关重要。这本书是学习TCP/IP协议的宝贵资料，不仅适合初学者，也对经验丰富的网络专业人士有所裨益。每一章末尾的总结帮助读者巩固所学知识，并为进一步探索提供指导。

Figure 1.4 Various protocols at the different layers in the TCP/IP protocol suite.

TCP and UDP are the two predominant transport layer protocols. Both use IP as the network layer.

TCP provides a reliable transport layer, even though the service it uses (IP) is unreliable. Chapters 17

through 22 provide a detailed look at the operation of TCP. We then look at some TCP applications:

Telnet and Riogin in Chapter 26, FTP in Chapter 27, and SMTP in Chapter 28. The applications are

normally user processes.

UDP sends and receives datagrams for applications. A datagram is a unit of information (i.e., a certain

number of bytes of information that is specified by the sender) that travels from the sender to the receiver.

Unlike TCP, however, UDP is unreliable. There is no guarantee that the datagram ever gets to its final

destination. Chapter 11 looks at UDP, and then Chapter 14 (the Domain Name System), Chapter 15

(the Trivial File Transfer Protocol), and Chapter 16 (the Bootstrap Protocol) look at some applications

that use UDP. SNMP (the Simple Network Management Protocol) also uses UDP, but since it deals

with many of the other protocols, we save a discussion of it until Chapter 25.

IP is the main protocol at the network layer. It is used by both TCP and UDP. Every piece of TCP and

UDP data that gets transferred around an internet goes through the IP layer at both end systems and at

every intermediate router. In Figure 1.4 we also show an application accessing IP directly. This is rare,

but possible. (Some older routing protocols were implemented this way. Also, it is possible to experiment

with new transport layer protocols using this feature.) Chapter 3 looks at IP, but we save some of the

details for later chapters where their discussion makes more sense. Chapters 9 and 10 look at how IP

performs routing.

ICMP is an adjunct to IP. It is used by the IP layer to exchange error messages and other vital

information with the IP layer in another host or router. Chapter 6 looks at ICMP in more detail. Although

ICMP is used primarily by IP, it is possible for an application to also access it. Indeed we'll see that two

popular diagnostic tools, Ping and Traceroute (Chapters 7 and 8), both use ICMP.

Page 16

ABC Amber CHM Converter Trial version, http://www.processtext.com/abcchm.html

IGMP is the Internet Group Management Protocol. It is used with multicasting: sending a UDP datagram

to multiple hosts. We describe the general properties of broadcasting (sending a UDP datagram to every

host on a specified network) and multicasting in Chapter 12, and then describe IGMP itself in Chapter

13.

ARP (Address Resolution Protocol) and RARP (Reverse Address Resolution Protocol) are specialized

protocols used only with certain types of network interfaces (such as Ethernet and token ring) to convert

between the addresses used by the IP layer and the addresses used by the network interface. We

examine these protocols in Chapters 4 and 5, respectively.

1.4 Internet Addresses

Every interface on an internet must have a unique Internet address (also called an IP address). These

addresses are 32-bit numbers. Instead of using a flat address space such as 1, 2, 3, and so on, there is a

structure to Internet addresses. Figure 1.5 shows the five different classes of Internet addresses.

These 32-bit addresses are normally written as four decimal numbers, one for each byte of the address.

This is called dotted-decimal notation. For example, the class B address of the author's primary system

is 140.252.13.33.

The easiest way to differentiate between the different classes of addresses is to look at the first number of

a dotted-decimal address. Figure 1.6 shows the different classes, with the first number in boldface.

Figure 1.5 The five different classes of Internet addresses.

Class

Range

0.0.0.0 to 127.255.255.255

128.0.0.0 to 191.255.255.255

192.0.0.0 to 223.255.255.255

224.0.0.0 to 239.255.255.255

240.0.0.0 to 247.255.255.255

Figure 1.6 Ranges for different classes of IP addresses.

It is worth reiterating that a multihomed host will have multiple IP addresses: one per interface.

Since every interface on an internet must have a unique IP address, there must be one central authority

for allocating these addresses for networks connected to the worldwide Internet. That authority is the

Internet Network Information Center, called the InterNIC. The InterNIC assigns only network IDs.

The assignment of host IDs is up to the system administrator.

Page 17

ABC Amber CHM Converter Trial version, http://www.processtext.com/abcchm.html

Registration services for the Internet (IP addresses and DNS domain names) used to be handled by the NIC, at

nic.ddn.mil

. On April 1, 1993, the InterNIC was created. Now the NIC handles these requests only for the Defense

Data Network (DDN). All other Internet users now use the InterNIC registration services, at

rs.internic.net

There are actually three parts to the InterNIC: registration services (

rs.internic.net

), directory and database

services (

ds.internic.net

), and information services (

is.internic.net

). See Exercise 1.8 for additional

information on the InterNIC.

There are three types of IP addresses: unicast (destined for a single host), broadcast (destined for all

hosts on a given network), and multicast (destined for a set of hosts that belong to a multicast group).

Chapters 12 and 13 look at broadcasting and multicasting in more detail.

In Section 3.4 we'll extend our description of IP addresses to include subnetting, after describing IP

routing. Figure 3.9 shows the special case IP addresses: host IDs and network IDs of all zero bits or all

one bits.

1.5 The Domain Name System

Although the network interfaces on a host, and therefore the host itself, are known by IP addresses,

humans work best using the name of a host. In the TCP/IP world the Domain Name System (DNS) is a

distributed database that provides the mapping between IP addresses and hostnames. Chapter 14 looks

into the DNS in detail.

For now we must be aware that any application can call a standard library function to look up the IP

address (or addresses) corresponding to a given hostname. Similarly a function is provided to do the

reverse lookup-given an IP address, look up the corresponding hostname.

Most applications that take a hostname as an argument also take an IP address. When we use the Telnet

client in Chapter 4, for example, one time we specify a host-name and another time we specify an IP

address.

1.6 Encapsulation

When an application sends data using TCP, the data is sent down the protocol stack, through each layer,

until it is sent as a stream of bits across the network. Each layer adds information to the data by

prepending headers (and sometimes adding trailer information) to the data that it receives. Figure 1.7

shows this process. The unit of data that TCP sends to IP is called a TCP segment. The unit of data that

IP sends to the network interface is called an IP datagram. The stream of bits that flows across the

Ethernet is called a frame.

The numbers at the bottom of the headers and trailer of the Ethernet frame in Figure 1.7 are the typical

sizes of the headers in bytes. We'll have more to say about each of these headers in later sections.

A physical property of an Ethernet frame is that the size of its data must be between 46 and 1500 bytes.

We'll encounter this minimum in Section 4.5 and we cover the maximum in Section 2.8.

All the Internet standards and most books on TCP/IP use the term octet instead of byte. The use of this cute, but

baroque term is historical, since much of the early work on TCP/IP was done on systems such as the DEC-10, which

did not use 8-bit bytes. Since almost every current computer system uses 8-bit bytes, we'll use the term byte in this

text.

To be completely accurate in Figure 1.7 we should say that the unit of data passed between IP and the network

interface is a packet. This packet can be either an IP datagram or a fragment of an IP datagram. We discuss

fragmentation in detail in Section 11.5.

We could draw a nearly identical picture for UDP data. The only changes are that the unit of information

that UDP passes to IP is called a UDP datagram, and the size of the UDP header is 8 bytes.

Page 18

ABC Amber CHM Converter Trial version, http://www.processtext.com/abcchm.html

剩余422页未读，继续阅读

ysp123ysp

粉丝: 0

TCP/IP详解第一卷：协议解析

tcp/ip详解英文版123

TCP/IP 卷三（英文版）

tcp\ip详解卷1-协议英文第二版及阅读器

tcpip详解卷1第二版 pdf

363、tcpip详解 [卷Ⅰ] 协议(原书第2版\tcpip详解 [卷Ⅰ] 协议(原书第2版.pdf

tcpip协议详解卷一第二版 pdf

tcpip详解卷一百度百科

tcpip详解套装共3册pdf

基于fpga verilog的tcp tcpip_stack_v1_2.zip

tcpip协议详解卷一pdf

最新资源