TCP/IP卷1：从入门到网络协议详解

4星 · 超过85%的资源需积分: 9 121 浏览量更新于2024-07-21 收藏 2.47MB PDF 举报

《TCP/IP详解卷1：协议》（TCP/IP Illustrated, Volume 1: The Protocols）是由W. Richard Stevens撰写的一本经典著作，它全面而深入地介绍了网络通信的基础知识。这本书对于理解计算机网络通信的核心原理至关重要，特别适合那些想要掌握TCP/IP协议栈、互联网架构以及底层通信机制的学习者。在第一部分的介绍章节中，作者首先定义了TCP/IP的基本概念。章节1.1阐述了网络通信的总体概念，强调了层状模型在设计和理解网络结构中的关键作用。1.2至1.16部分分别探讨了网络层（Layering）、互联网地址（Internet Addresses）、域名系统（DNS）、封装与解封装（Encapsulation and Demultiplexing）、客户端-服务器模型（Client-Server Model）、端口号（Port Numbers）、标准化过程（Standardization Process）以及RFC（Request for Comments，互联网工程任务组的标准文档）的重要性。此外，书中还讨论了标准服务、互联网的工作原理、不同实现方式以及应用编程接口（Application Programming Interfaces），并提供了测试网络环境进行实践学习。第二章专门讲解了链路层（Link Layer）技术，包括常见的局域网技术如以太网（Ethernet）和IEEE 802标准，以及如何通过Trailer Encapsulation进行数据封装。接着介绍了串行线路IP（SLIP）、压缩SLIP（Compressed SLIP）和点到点协议（PPP）等用于连接不同类型网络的通信协议。此外，还讨论了loopback接口、最大传输单元（MTU）、路径MTU（Path MTU）以及计算串行线路的吞吐量的方法。第三章深入剖析了互联网协议（Internet Protocol, IP）本身，从IP头的结构开始，解释了路由选择（IP Routing）、子网寻址（Subnet Addressing）和子网掩码（Subnet Mask）的概念。书中通过具体的例子说明了特殊情况下IP地址的处理，并提到了命令`ifconfig`的使用，这些都是理解和配置IP网络的关键操作。《TCP/IP Illustrated, Volume 1: The Protocols》不仅覆盖了理论知识，还提供了丰富的实践案例和实用工具，对于网络管理员、开发人员和对网络技术感兴趣的读者来说，是一本不可或缺的参考书。通过阅读和实践书中的内容，读者可以建立起扎实的TCP/IP基础，为后续在网络技术领域的进一步发展打下坚实基础。

Chapter 1. Introduction

Introduction

1.1 Introduction

The TCP/IP protocol suite allows computers of all sizes, from many different computer vendors,

running totally different operating systems, to communicate with each other. It is quite amazing

because its use has far exceeded its original estimates. What started in the late 1960s as a

government-financed research project into packet switching networks has, in the 1990s, turned

into the most widely used form of networking between computerrs. It is truly an open system in

that the definition of the protocol suite and many of its implementations are publicly available at

little or no charge. It forms the basis for what is called the worldwide Internet, or the Internet, a

wide area network (WAN) of more than one million computers that literally spans the globe.

This chapter provides an overview of the TCP/IP protocol suite, to establish an adequate

background for the remaining chapters. For a historical perspective on the early development of

TCP/IP see [Lynch 1993].

1.2 Layering

Networking protocols are normally developed in layers, with each layer responsible for a

different facet of the communications. A protocol suite, such as TCP/IP, is the combination of

different protocols at various layers. TCP/IP is normally considered to be a 4-layer system, as

shown in Figure 1.1.

Application Telnet, FTP, e-mail, etc.

Transport TCP, UDP

Network IP, ICMP, IGMP

Link device driver and interface card

Figure 1.1 The four layers of the TCP/IP protocol suite.

Each layer has a different responsibility.

1. The link layer, sometimes called the data-link layer or network interface layer, normally

includes the device driver in the operating system and the corresponding network

interface card in the computer. Together they handle all the hardware details of physically

interfacing with the cable (or whatever type of media is being used).

2. The network layer (sometimes called the internet layer) handles the movement of packets

around the network. Routing of packets, for example, takes place here. IP (Internet

Protocol), ICMP (Internet Control Message Protocol), and IGMP (Internet Group

Management Protocol) provide the network layer in the TCP/IP protocol suite.

3. The transport layer provides a flow of data between two hosts, for the application layer

above. In the TCP/IP protocol suite there are two vastly different transport protocols:

TCP (Transmission Control Protocol) and UDP (User Datagram Protocol).

file:///D|/Documents%20and%20Settings/bigini/Docu...homenet2run/tcpip/tcp-ip-illustrated/introduc.htm (1 of 20) [12/09/2001 14.46.31]

Chapter 1. Introduction

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 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

file:///D|/Documents%20and%20Settings/bigini/Docu...homenet2run/tcpip/tcp-ip-illustrated/introduc.htm (3 of 20) [12/09/2001 14.46.31]

Chapter 1. Introduction

(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.

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

file:///D|/Documents%20and%20Settings/bigini/Docu...homenet2run/tcpip/tcp-ip-illustrated/introduc.htm (4 of 20) [12/09/2001 14.46.31]

剩余589页未读，继续阅读

qq_32138667

粉丝: 0
资源: 1

TCP/IP卷1：从入门到网络协议详解

TCP/IP Illustrated, Volume 1, 2nd Edition

TCP/IP Illustrated 2nd Edition

TCP/IP Illustrated,. Volume 1

Addison.Wesley.TCP.IP.Illustrated.Volume.1.The.Protocols.chm

Addison Wesley.TCP.IP.Illustrated.Volume.1.The.Protocols.chm

TCP.IP.Illustrated.Volume.1.The.Protocols

The.Protocols.(TCP-IP.Illustrated,.Volume.1)

The.Protocols.(TCP-IP.Illustrated,.Volume.1).7z.002

The.Protocols.(TCP-IP.Illustrated,.Volume.1).7z.003

The.Protocols.(TCP-IP.Illustrated,.Volume.1).7z.001

最新资源