TCP协议详解：从基础到实现

需积分: 47 39 浏览量更新于2024-07-26 收藏 2.72MB PDF 举报

TCP/IP详解是一本由W.Richard Stevens编写的经典著作，全称为TCP/IPIllustrated，该书深入浅出地介绍了互联网协议的核心原理和技术。这本书共分为两卷，主要关注TCP（Transmission Control Protocol）和IP（Internet Protocol）这两个关键协议，适合对网络通信和编程感兴趣的读者深入学习。 **第1章：介绍** 本章涵盖了TCP/IP体系结构的基础知识，包括网络层和传输控制层的分层理论，互联网地址的使用，域名系统（DNS）的工作方式，数据封装的过程，以及客户端-服务器模型的概念。此外，还讨论了端口号的作用、标准化过程中的RFC（Request for Comments）文档，以及一些基本的互联网服务和接口。这一章概述了TCP/IP在实际应用中的实现和接口设计，最后介绍了如何构建一个测试网络来验证理论知识。 **第2章：链路层** 这部分深入探讨了物理层与网络层之间的连接技术。讲解了Ethernet和IEEE 802标准的封装，以及不同类型的串口通信协议如SLIP（Serial Line IP）和Compressed SLIP的使用。PPP（Point-to-Point Protocol）作为点对点链接的常见协议也被详细介绍。章节还包括处理最大传输单元（MTU）、路径MTU以及通过计算来优化串行线路的吞吐量。这部分内容对于理解网络通信的底层实现至关重要。 **第3章：IP协议** 本章重点在于IP协议本身，首先介绍了IP协议的基本概念，包括IP头的构成，路由选择机制，以及子网地址和子网掩码的应用。特殊类型的IP地址，如环回地址，也在这一章有所涉及。同时，通过ifconfig等工具的使用，展示了如何配置和管理IP地址和网络接口。 TCP/IP详解提供了丰富的实践经验和理论知识，对于理解网络通信的核心技术和协议工作原理有着重要的参考价值。无论是网络管理员、系统开发者还是对网络感兴趣的学习者，都能从这本书中获得深入的理解和宝贵的经验。通过阅读和实践，读者可以掌握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页未读，继续阅读

hubi

粉丝: 104
资源: 21

TCP协议详解：从基础到实现

tcp/ip详解英文版123

TCP.IP详解 英文版

TCP/IP 详解 卷二 英文版 压缩包2（共2包）

tcp/ip协议详解卷1英文版

tcp ip英文版 电子版

modbus tcp 协议详解

labview的tcp通信详解

tcp/ip详解卷二第二版

tcp ip详解 卷1 协议

tcp/ip详解 卷二 下载

最新资源

TCP.IP详解英文版

TCP/IP 详解卷二英文版压缩包2（共2包）

tcp ip英文版电子版

tcp ip详解卷1 协议

tcp/ip详解卷二下载