前几天期末考试了，都没咋看了。。。
几天开始暑假，继续开始自己的学习！
RFC: 793
TRANSMISSION CONTROL PROTOCOL
DARPA INTERNET PROGRAM
PROTOCOL SPECIFICATION
September 1981
prepared for
Defense Advanced Research Projects Agency
Information Processing Techniques Office
1400 Wilson Boulevard
Arlington, Virginia22209
by
Information Sciences Institute
University of Southern California
4676 Admiralty Way
MarinadelRey, California90291
September 1981
Transmission Control Protocol
TABLE OF CONTENTS
PREFACE ........................................................ iii
1. INTRODUCTION ..................................................... 1
1.1 Motivation .................................................... 1
1.2 Scope ......................................................... 2
1.3 About This Document ........................................... 2
1.4 Interfaces .................................................... 3
1.5 Operation ..................................................... 3
2. PHILOSOPHY ....................................................... 7 //体系结构
2.1 Elements of the Internetwork System ........................... 7 //Elements:基础
2.2 Model of Operation ............................................ 7
2.3 The Host Environment .......................................... 8
2.4 Interfaces .................................................... 9
2.5 Relation to Other Protocols ................................... 9
2.6 Reliable Communication ........................................ 9
2.7 Connection Establishment and Clearing ........................ 10
2.8 Data Communication ........................................... 12
2.9 Precedence and Security ...................................... 13
2.10 Robustness Principle ......................................... 13 //Robustness:鲁棒性
3. FUNCTIONAL SPECIFICATION ........................................ 15
3.1 Header Format ................................................ 15
3.2 Terminology .................................................. 19 //术语
3.3 Sequence Numbers ............................................. 24
3.4 Establishing a connection .................................... 30
3.5 Closing a Connection ......................................... 37
3.6 Precedence and Security ...................................... 40
3.7 Data Communication ........................................... 40
3.8 Interfaces ................................................... 44
3.9 Event Processing ............................................. 52
GLOSSARY ............................................................ 79
REFERENCES .......................................................... 85
[Page i]
September 1981
Transmission Control Protocol
[Page ii]
September 1981
Transmission Control Protocol
PREFACE //序言
This document describes the DoD Standard Transmission Control Protocol //based on 9 erlier editions
(TCP). There have been nine earlier editions of the ARPA TCP
specification on which this standard is based, and the present text
draws heavily from them. There have been many contributors to this work
both in terms of concepts and in terms of text. This edition clarifies //clarifies：阐明
several details and removes the end-of-letter buffer-size adjustments,
and redescribes the letter mechanism as a push function. //pay some attention to the push function
Jon Postel
Editor
RFC: 793
Replaces: RFC761
IENs: 129, 124, 112, 81,
55, 44, 40, 27, 21, 5
TRANSMISSION CONTROL PROTOCOL
DARPA INTERNET PROGRAM
PROTOCOL SPECIFICATION
1. INTRODUCTION
The Transmission Control Protocol (TCP) is intended for use as a highly //intend for highly reliable host-to-host protcol
reliable host-to-host protocol between hosts in packet-switched computer
communication networks, and in interconnected systems of such networks.
This document describes the functions to be performed by the //function,program and interface
Transmission Control Protocol, the program that implements it, and its
interface to programs or users that require its services.
1.1. Motivation
Computer communication systems are playing an increasingly important //the history of TCP
role in military, government, and civilian environments. This
document focuses its attention primarily on military computer
communication requirements, especially robustness in the presence of //robustness in unreliability and availabity(when congestion)
communication unreliability and availability in the presence of
congestion, but many of these problems are found in the civilian and
government sector as well.
As strategic and tactical computer communication networks are //motivation:interconnecting computer communication networks
developed and deployed, it is essential to provide means of
interconnecting them and to provide standard interprocess
communication protocols which can support a broad range of
applications. In anticipation of the need for such standards, the
Deputy Undersecretary of Defense for Research and Engineering has
declared the Transmission Control Protocol (TCP) described herein to
be a basis for DoD-wide inter-process communication protocol
standardization.
TCP is a connection-oriented, end-to-end reliable protocol designed to //TCP is connection-oriented and end-to-end reliable
fit into a layered hierarchy of protocols which support multi-network
applications. The TCP provides for reliable inter-process
communication between pairs of processes in host computers attached to
distinct but interconnected computer communication networks. Very few
assumptions are made as to the reliability of the communication //TCP enable that the lower layer provide unreliable connection
protocols below the TCP layer. TCP assumes it can obtain a simple,
potentially unreliable datagram service from the lower level
protocols. In principle, the TCP should be able to operate above a
wide spectrum of communication systems ranging from hard-wired
connections to packet-switched or circuit-switched networks. //TCP can operate on hard-wired connections,packet-switched
//and circuit-switched networks,hard-wired connections:电线直连
[Page 1]
September 1981
Transmission Control Protocol
Introduction
TCP is based on concepts first described by Cerf and Kahn in [1]. The
TCP fits into a layered protocol architecture just above a basic //TCP is just above the internet module
Internet Protocol [2] which provides a way for the TCP to send and
receive variable-length segments of information enclosed in internet//TCP transmitte the "envolopes"--a block of data,
datagram "envelopes". The internet datagram provides a means for //and the fragment is made by the internet module
addressing source and destination TCPs in different networks. The
internet protocol also deals with any fragmentation or reassembly of
the TCP segments required to achieve transport and delivery through
multiple networks and interconnecting gateways. The internet protocol //to operate on multiple networks,TCP doesn't care
also carries information on the precedence, security classification //the local nerwork and the lower protocol
and compartmentation of the TCP segments, so this information can be
communicated end-to-end across multiple networks.
Protocol Layering
+---------------------+
| higher-level |
+---------------------+
| TCP |
+---------------------+
| internet protocol |
+---------------------+
|communication network|
+---------------------+
Figure 1
Much of this document is written in the context of TCP implementations //TCP is closely related with the end system
which are co-resident with higher level protocols in the host
computer. Some computer systems will be connected to networks via
front-end computers which house the TCP and internet protocol layers,
as well as network specific software. The TCP specification describes
an interface to the higher level protocols which appears to be
implementable even for the front-end case, as long as a suitable
host-to-front end protocol is implemented.
1.2. Scope
The TCP is intended to provide a reliable process-to-process //TCP provide a reliable process-to-process communiction service
communication service in a multinetwork environment. The TCP is
intended to be a host-to-host protocol in common use in multiple//进程间的通信
networks.
1.3. About this Document
This document represents a specification of the behavior required of //this document represents the behavior，format and the
any TCP implementation, both in its interactions with higher level //philosophical(设计思想)
protocols and in its interactions with other TCPs. The rest of this
[Page 2]
September 1981
Transmission Control Protocol
Introduction
section offers a very brief view of the protocol interfaces and
operation. Section 2 summarizes the philosophical basis for the TCP
design. Section 3 offers both a detailed description of the actions
required of TCP when various events occur (arrival of new segments,
user calls, errors, etc.) and the details of the formats of TCP
segments.
1.4. Interfaces
The TCP interfaces on one side to user or application processes and on//user of TCP:application processes
the other side to a lower level protocol such as Internet Protocol. //TCP using:lower protocol like IP
The interface between an application process and the TCP is //the basic function of the interface between the process and TCP
illustrated in reasonable detail. This interface consists of a set of
calls much like the calls an operating system provides to an //"call"--a important concept,provides information
application process for manipulating files. For example, there are
calls to open and close connections and to send and receive data on
established connections. It is also expected that the TCP can
asynchronously communicate with application programs. Although //asynchronously--异步,support asynchronously communication
considerable freedom is permitted to TCP implementors to design
interfaces which are appropriate to a particular operating system
environment, a minimum functionality is required at the TCP/user //the interface
interface for any valid implementation.
The interface between TCP and lower level protocol is essentially //the basic function between TCP and the lower layer
unspecified except that it is assumed there is a mechanism whereby the //only required the asynchronously communication
two levels can asynchronously pass information to each other. //and the ability of identify
Typically, one expects the lower level protocol to specify this
interface. TCP is designed to work in a very general environment of
interconnected networks. The lower level protocol which is assumed
throughout this document is the Internet Protocol [2].
1.5. Operation
As noted above, the primary purpose of the TCP is to provide reliable,
securable logical circuit or connection service between pairs of //the primary purpose:reliable,securable logical circuit
processes. To provide this service on top of a less reliable internet //or connection service between the two processes
communication system requires facilities in the following areas:
Basic Data Transfer //the basic abilities
Reliability
Flow Control
Multiplexing
Connections
Precedence and Security
The basic operation of the TCP in each of these areas is described in
the following paragraphs.
[Page 3]
September 1981
Transmission Control Protocol
Introduction
Basic Data Transfer:
The TCP is able to transfer a continuous stream of octets in each //transfer stream of octets base on fragmentation and
direction between its users by packaging some number of octets into//reassembly which are provided by the lower layer
segments for transmission through the internet system. In general,
the TCPs decide when to block and forward data at their own
convenience.
Sometimes users need to be sure that all the data they have
submitted to the TCP has been transmitted. For this purpose a push//push function:postively push the data to TCP
function is defined. To assure that data submitted to a TCP is
actually transmitted the sending user indicates that it should be
pushed through to the receiving user. A push causes the TCPs to
promptly forward and deliver data up to that point to the receiver.
The exact push point might not be visible to the receiving user and
the push function does not supply a record boundary marker.
Reliability:
The TCP must recover from data that is damaged, lost, duplicated, or //using ACK,sequence number,checksum to make sure reliability
delivered out of order by the internet communication system. This //ACK:retransmitted--sender
is achieved by assigning a sequence number to each octet //seqyence number and checksum:recover--receiver
transmitted, and requiring a positive acknowledgment (ACK) from the
receiving TCP. If the ACK is not received within a timeout
interval, the data is retransmitted. At the receiver, the sequence
numbers are used to correctly order segments that may be received
out of order and to eliminate duplicates. Damage is handled by
adding a checksum to each segment transmitted, checking it at the
receiver, and discarding damaged segments.
As long as the TCPs continue to function properly and the internet
system does not become completely partitioned, no transmission //why?require some errors?
errors will affect the correct delivery of data. TCP recovers from
internet communication system errors.
Flow Control:
TCP provides a means for the receiver to govern the amount of data //use "window" for flow control,and it is based on ACK
sent by the sender. This is achieved by returning a "window" with
every ACK indicating a range of acceptable sequence numbers beyond
the last segment successfully received. The window indicates an
allowed number of octets that the sender may transmit before
receiving further permission.
[Page 4]
September 1981
Transmission Control Protocol
Introduction
Multiplexing:
To allow for many processes within a single Host to use TCP //use the port function for multiplexing
communication facilities simultaneously, the TCP provides a set of
addresses or ports within each host. Concatenated with the network
and host addresses from the internet communication layer, this forms
a socket. A pair of sockets uniquely identifies each connection.
That is, a socket may be simultaneously used in multiple
connections.
The binding of ports to processes is handled independently by each //the host(OS) manages the ports
Host. However, it proves useful to attach frequently used processes
(e.g., a "logger" or timesharing service) to fixed sockets which are
made known to the public. These services can then be accessed
through the known addresses. Establishing and learning the port
addresses of other processes may involve more dynamic mechanisms.
Connections:
The reliability and flow control mechanisms described above require //using sockets,sequence number,window sizes to
that TCPs initialize and maintain certain status information for //manage the connection
each data stream. The combination of this information, including
sockets, sequence numbers, and window sizes, is called a connection.
Each connection is uniquely specified by a pair of sockets
identifying its two sides.
When two processes wish to communicate, their TCP's must first //the process of the establishing connection
establish a connection (initialize the status information on each
side). When their communication is complete, the connection is
terminated or closed to free the resources for other uses.
Since connections must be established between unreliable hosts and //using handshake mechanism to ensure the correct
over the unreliable internet communication system, a handshake //initialization
mechanism with clock-based sequence numbers is used to avoid
erroneous initialization of connections.
Precedence and Security:
The users of TCP may indicate the security and precedence of their
communication. Provision is made for default values to be used when
these features are not needed.
498
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
