TCP/IP详解：卷一 - Internet协议与链接层解析

需积分: 48 71 浏览量更新于2024-07-27 收藏 2.61MB PDF 举报

"TCP/IP详解卷一英文版" 本书是网络领域的经典之作，深入讲解了TCP/IP协议栈的各个层面。作者W.Richard Stevens详细阐述了TCP/IP协议族的基本概念、工作原理和实现细节。在第一部分，作者介绍了TCP/IP的基础知识。第1章"Introduction"涵盖了一系列关键概念，如分层模型（Layering）以及TCP/IP的四层模型（应用层、传输层、网络层和链路层）。讨论了互联网地址（Internet Addresses），包括IP地址和域名系统（DNS）的作用，它是如何实现域名到IP地址的映射。此外，还讲解了封装（Encapsulation）、多路复用与解复用（Demultiplexing）的概念，以及客户端-服务器模型（Client-Server Model）的工作方式。端口号（Port Numbers）在服务识别中的作用，标准化过程（Standardization Process）和RFC（Request for Comments）文档的重要地位，以及标准和简单服务（Standard, Simple Services）的定义。书中还介绍了互联网的架构和不同实现（Implementations），以及应用程序编程接口（APIs）的应用。为了便于学习，书中提到了测试网络的搭建，并在每章末尾都进行了总结。第二部分，作者开始探讨底层通信协议。第2章"Link Layer"主要关注链路层，讨论了以太网和IEEE 802封装（Ethernet and IEEE 802 Encapsulation），以及Trailer Encapsulation的使用。此外，还详细介绍了串行线路IP协议SLIP（Serial Line IP）和压缩SLIP（Compressed SLIP），以及点对点协议PPP（Point-to-Point Protocol）。同时，提到了回环接口（Loopback Interface）、最大传输单元MTU（Maximum Transmission Unit）以及路径MTU发现（Path MTU Discovery）。最后，分析了串行线路的吞吐量计算。第三部分深入到网络层，第3章"IP: Internet Protocol"讨论了IP协议的核心内容。这包括IP头部结构（IP Header）、IP路由（IP Routing）以及子网寻址（Subnet Addressing）。书中解释了子网掩码（Subnet Mask）的重要性，并通过实例展示了特殊IP地址（Special Case IPAddress）的处理。介绍了命令行工具ifconfig和netstat在查看网络状态和配置IP参数方面的应用，同时展望了IP的未来发展方向。第四部分，作者在第4章"ARP: Address Resolution Protocol"中探讨了地址解析协议ARP，它是如何解决IP地址到物理地址的转换问题。这一章将介绍ARP的工作机制、请求与响应流程，以及缓存管理等方面的内容。这本书详尽地剖析了TCP/IP协议的各个方面，不仅适合网络专业人士阅读，也对学习计算机网络的初学者提供了宝贵的参考资料。

application layer can ignore all these details.

UDP, on the other hand, provides a much simpler service to the application layer. It just sends packets

of data called datagrams from one host to the other, but there is no guarantee that the datagrams reach

the other end. Any desired reliability must be added by the application layer.

There is a use for each type of transport protocol, which we'll see when we look at the different

applications that use TCP and UDP.

The application layer handles the details of the particular application. There are many common

TCP/IP applications that almost every implementation provides:

Telnet for remote login,

❍

FTP, the File Transfer Protocol,❍

SMTP, the Simple Mail Transfer protocol, for electronic mail,❍

SNMP, the Simple Network Management Protocol,❍

and many more, some of which we cover in later chapters.

If we have two hosts on a local area network (LAN) such as an Ethernet, both running FTP, Figure 1.2

shows the protocols involved.

Figure 1.2 Two hosts on a LAN running FTP.

We have labeled one application box the FTP client and the other the FTP server. Most network applications

are designed so that one end is the client and the other side the server. The server provides some type of

service to clients, in this case access to files on the server host. In the remote login application, Telnet, the

service provided to the client is the ability to login to the server's host.

Each layer has one or more protocols for communicating with its peer at the same layer. One protocol, for

example, allows the two TCP layers to communicate, and another protocol lets the two IP layers

Chapter 1. Introduction

file:///F|/USER/DonahuJ/tcpip/tcpip_ill/introduc.htm (2 of 17) [1/23/2002 10:11:22 AM]

communicate.

On the right side of Figure 1.2 we have noted that normally the application layer is a user process while the

lower three layers are usually implemented in the kernel (the operating system). Although this isn't a

requirement, it's typical and this is the way it's done under Unix.

There is another critical difference between the top layer in Figure 1.2 and the lower three layers. The

application layer is concerned with the details of the application and not with the movement of data across

the network. The lower three layers know nothing about the application but handle all the communication

details.

We show four protocols in Figure 1.2, each at a different layer. FTP is an application layer protocol, TCP is

a transport layer protocol, IP is a network layer protocol, and the Ethernet protocols operate at the link layer.

The TCP/IP protocol suite is a combination of many protocols. Although the commonly used name for the

entire protocol suite is TCP/IP, TCP and IP are only two of the protocols. (An alternative name is the

Internet Protocol Suite.)

The purpose of the network interface layer and the application layer are obvious-the former handles the

details of the communication media (Ethernet, token ring, etc.) while the latter handles one specific user

application (FTP, Telnet, etc.). But on first glance the difference between the network layer and the transport

layer is somewhat hazy. Why is there a distinction between the two? To understand the reason, we have to

expand our perspective from a single network to a collection of networks.

One of the reasons for the phenomenal growth in networking during the 1980s was the realization that an

island consisting of a stand-alone computer made little sense. A few stand-alone systems were collected

together into a network. While this was progress, during the 1990s we have come to realize that this new,

bigger island consisting of a single network doesn't make sense either. People are combining multiple

networks together into an internetwork, or an internet. An internet is a collection of networks that all use the

same protocol suite.

The easiest way to build an internet is to connect two or more networks with a router. This is often a

special-purpose hardware box for connecting networks. The nice thing about routers is that they provide

connections to many different types of physical networks: Ethernet, token ring, point-to-point links, FDDI

(Fiber Distributed Data Interface), and so on.

These boxes are also called IP routers, but we'll use the term router.

Historically these boxes were called gateways, and this term is used throughout much of the TCP/IP literature. Today the term

gateway is used for an application gateway: a process that connects two different protocol suites (say, TCP/IP and IBM's SNA)

for one particular application (often electronic mail or file transfer).

Figure 1.3 shows an internet consisting of two networks: an Ethernet and a token ring, connected with a

router. Although we show only two hosts communicating, with the router connecting the two networks, any

host on the Ethernet can communicate with any host on the token ring.

In Figure 1.3 we can differentiate between an end system (the two hosts on either side) and an intermediate

system (the router in the middle). The application layer and the transport layer use end-to-end protocols. In

our picture these two layers are needed only on the end systems. The network layer, however, provides a

hop-by-hop protocol and is used on the two end systems and every intermediate system.

Chapter 1. Introduction

file:///F|/USER/DonahuJ/tcpip/tcpip_ill/introduc.htm (3 of 17) [1/23/2002 10:11:22 AM]

Figure 1.3 Two networks connected with a router.

In the TCP/IP protocol suite the network layer, IP, provides an unreliable service. That is, it does its best job

of moving a packet from its source to its final destination, but there are no guarantees. TCP, on the other

hand, provides a reliable transport layer using the unreliable service of IP To provide this service, TCP

performs timeout and retransmission, sends and receives end-to-end acknowledgments, and so on. The

transport layer and the network layer have distinct responsibilities.

A router, by definition, has two or more network interface layers (since it connects two or more networks).

Any system with multiple interfaces is called multihomed. A host can also be multihomed but unless it

specifically forwards packets from one interface to another, it is not called a router. Also, routers need not be

special hardware boxes that only move packets around an internet. Most TCP/IP implementations allow a

multihomed host to act as a router also, but the host needs to be specifically configured for this to happen. In

this case we can call the system either a host (when an application such as FTP or Telnet is being used) or a

router (when it's forwarding packets from one network to another). We'll use whichever term makes sense

given the context.

One of the goals of an internet is to hide all the details of the physical layout of the internet from the

applications. Although this isn't obvious from our two-network internet in Figure 1.3, the application layers

can't care (and don't care) that one host is on an Ethernet, the other on a token ring, with a router between.

There could be 20 routers between, with additional types of physical interconnections, and the applications

would run the same. This hiding of the details is what makes the concept of an internet so powerful and

useful.

Another way to connect networks is with a bridge. These connect networks at the link layer, while routers

connect networks at the network layer. Bridges makes multiple LANs appear to the upper layers as a single

LAN.

Chapter 1. Introduction

file:///F|/USER/DonahuJ/tcpip/tcpip_ill/introduc.htm (4 of 17) [1/23/2002 10:11:22 AM]

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.

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.

Chapter 1. Introduction

file:///F|/USER/DonahuJ/tcpip/tcpip_ill/introduc.htm (6 of 17) [1/23/2002 10:11:23 AM]

剩余481页未读，继续阅读

xxx134617

粉丝: 3
资源: 22

TCP/IP详解：卷一 - Internet协议与链接层解析

一个C-S模版，该模版由三部分的程序组成

Android -「安卓端」 广告配音工具用于语音合成助手/自媒体配音/广告配音/文本朗读

基于java的网络教学平台设计与实现.docx

Go 语言开发的web系统脚手架, 前后端分离, 仅包含项目开发的必需部分, 基于角色的访问控制(RBAC), 分包合理, 精简易于扩展 后端Go包含了gin、 gorm、 jwt和casb.zip

IBM发布2024年AI实际应用报告: 探讨AI引领者成功之道

基于python+PyQt+MySQL的酒店管理系统资料齐全+详细文档.zip

本库将会整理我在学习go语言过程中在阅读好文，博客，开源项目代码时遇到的好的易于复用的并发模式代码.zip

102舒靓宇202404416085(1).docx

基于java的小区物业智能卡管理的开题报告.docx

基于python实现的各种小爬虫详细文档+资料齐全.zip

最新资源

Android -「安卓端」广告配音工具用于语音合成助手/自媒体配音/广告配音/文本朗读

Go 语言开发的web系统脚手架, 前后端分离, 仅包含项目开发的必需部分, 基于角色的访问控制(RBAC), 分包合理, 精简易于扩展后端Go包含了gin、 gorm、 jwt和casb.zip