TCP/IP协议详解：卷1 - 原理

4星 · 超过85%的资源需积分: 47 50 浏览量更新于2024-07-25 收藏 2.72MB PDF 举报

"TCP/IP Illustrated, Volume 1 The Protocols 是一本深入探讨TCP/IP协议的英文原版书籍，由W. Richard Stevens撰写。本书主要涵盖了网络通信的基础知识，包括分层模型、TCP/IP协议栈的结构、互联网地址、域名系统(DNS)、封装、多路分解、客户端-服务器模型、端口号、标准化过程、RFC文档、标准服务、互联网实现、应用编程接口(API)以及测试网络等核心概念。书中进一步讨论了链路层的内容，如以太网和IEEE 802封装、Trailer封装、SLIP、压缩SLIP、PPP协议、环回接口、最大传输单元(MTU)、路径MTU和串行线路吞吐量计算。此外，还详细解析了IP互联网协议，包括IP头部、IP路由、子网寻址、子网掩码以及具体的子网示例。" 在《TCP/IP Illustrated, Volume 1 The Protocols》中，作者首先介绍了TCP/IP协议的基本概念，例如网络通信的分层模型，这是一种将复杂网络功能分解为不同层次的方法，便于管理和实现。TCP/IP协议栈通常分为四层（在OSI模型中对应五层）：链路层、网络层（IP）、传输层（TCP/UDP）和应用层。书中特别强调了互联网地址的重要性，这些地址是网络设备在全球互联网中的唯一标识。域名系统DNS则是为了便于人类记忆，将易于理解的域名转换为IP地址的系统。链路层部分，作者详细讲解了以太网和IEEE 802标准的封装方式，以及用于远程连接的SLIP（Serial Line IP）和其压缩形式，还有更现代的PPP（Point-to-Point Protocol）。此外，还涉及了环回接口，这是网络设备自我检测的重要工具。MTU（Maximum Transmission Unit）和Path MTU（Path Maximum Transmission Unit）的概念对于数据包在不同网络间的传输至关重要，它们决定了数据包的最大尺寸。在IP协议部分，作者深入探讨了IP头的结构，以及IP如何通过路由器进行路由选择。子网寻址和子网掩码是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页未读，继续阅读

mzwang123

粉丝: 22

TCP/IP协议详解：卷1 - 原理

TCP/IP Illustrated

TCP-IP Illustrated, Vol. 1 The Protocols

tcp/ip illustrated Englist edition

TCP/IP Illustrated,. Volume 1

TCP IP Illustrated (TCP/IP详解.第一卷)

TCP/IP三卷【第一部分：TCP/IP基础】

TCP-IP Illustrated Volume 1 The Protocols

TCP IP Illustrated Volume 1 The Protocols

TCP-IP Illustrated Volume 1 The Protocols Second Edition

TCP-IP Illustrated Volunme 1-The Protocols.pdf

最新资源