Organization: China Interactive Publishing Network (http://www.china-pub.com/)
RFC Document Chinese Translation Program (http://www.china-pub.com/compters/emook/aboutemook.htm)
E-mail: Ouyang@china-pub.com
Translator: Shao Yi (EPL shaoyi@163.net)
Translation time: 2001-11-7
Copyright: This Chinese translation copyright belongs to China Interactive Publishing Network. Can be used for non-commercial use free reprint, but must
Keep the translation and copyright information of this document.
Network Working Group
REQUEST for Comments $ 107
NIC # 5806
Host - Description of the Host Protocol Fault Clear Committee
(RFC107 - OUTPUT OF THE HOST-Host Protocol)
table of Contents
Introduction 3
Modify 3
1 byte 3
2 packet format 3
3 Message Message Data Type 5
4 reset and reset answer 5
5 flow control 5
6 control signal 6
7 connection assign 6
8 fixed length control command 6
9 Control command format 6
Discussion on byte stream 8
University of California Los Angeles
March 23, 1971
Robert BRESSLER
Steve crocker
William Crowter
Gary grossman
Ray Tomlinson
James withe
Introduction
After the network community, the Transfer Protocol Failure Clear Committee on March 8 to 9, 1971
The second meeting was held in Los Angeles, California, California. The committee expands slightly
The results of the meeting were filed in the form of RFC102 documents. The Committee agreed to the agreement in document No. 1
Individual modifications, the changes involved are as follows.
At each meeting, the Committee quickly deals with all the themes other than a highlighting. First
In a meeting, most of the time is used to consider the interrupt mechanism, and the results of the discussion are summarized as RFC102.
Document. At the second meeting, the committee spent almost all time discussion bytes, this
The discussion results summarize after the list of modifications.
This RFC document will all replace the RFC102 file and as the official revision of the 1 document. 1
The revision of the file will be simply described and merged with the modifications listed here.
The formula of the network control program will merge these changes as soon as possible. The formula of the network control program will also
It is estimated that these network control programs will be ready and put the above estive crocker or him.
Secretary ByRNA Kristel.
modify
1 byte
So far, a connection has always been a bitstream. From now on, it will be a byte stream, with
There is byte length S, given in each message packet's Str command. This byte length satisfies the constraint:
1 <= s = 255.
The choice of a coupling byte length is a question of a third level agreement, but byte length is connected here.
It is a constant within the time limit. Each message message must contain an integer item byte (see below).
2 packet format
The packet format is converted to the format shown in Figure 1.
Fields S and C represent the number of bytes and bytes, respectively.
Fields S has 8 bits, which must match the byte length declared in the creative STR. Field C is 16
The bit length, it illustrates the number of partial bytes in the message packet. The zero value in the field c allows existence,
But no use.
Both M1 and M2 field must be 8 bits, and zero must be included. Field M3 must be existing, and must
Part is zero. Field M3 can be used to fill in message packets to the boundary of a word. And then fill the completion.
32 BITS
| <---------------------------------> ---------- -----------------------
| | |
| Leader |
| | |
------ -------------------------
| | | | | |
| M1 | s | c |
| | | | | |
------ -------------------------
| | ^ |
| M2 | | | | |
| | | | | |
------ | |
| | | | |
| | | | |
| | |
| Text |
///
| | | | |
| | | | |
| | | | |
| | | | |
| | --------
| | | | | |
| | | | M3 |
| V | |
-------------- ------ --------
| | |
| 10 --------- 0 | <- Padding
| | |
---------------
Typical Message
figure 1
The text field consists of C bytes, each byte long S bit. The text field begins in the beginning of the message packet
After 72 bits.
The subnet must be able to divide the byte stream into message packets. Do not add anything on the boundaries of the message packet
Yiyi. In particular:
1. For C, although a message message with zero value is legal, it exhausted resources
Distribution and meaningless. (See the flow control of the text)
2. The receiver does not expect the third level of control information synchronized with the message packet boundary. Special, if
Record is declared to define the join, then the receiver must wait for multiple records or a message.
Record fragment in the article. (However, control information complies with special rules, see below)
3 Message Packet Data Type
The data type is not defined as part of the second level protocol.
The third level protocol may include this definition. The data type cannot be synchronized in the message packet boundary.
4 reset and reset response
A pair of new one control signal RST (RESET) and RRP (Reset Reply) have been added. The RST signal is interpreted as a network control for all existing portions generated by the owner sent to RST.
The signal of the preface table. The host receives the RRP signal representation to the RST signal. Host sending an RST signal
Continue to join after receiving an RST signal or a response RRP signal. If in the first master
After the machine, the second host will return, returns an RST signal.
5 flow control
The flow control method changes from two aspects. First, the stop mechanism is deactivated. 10hi and 11hi
Message packets will no longer be identified as IMPS, and the IMPS will not be regenerated into 10hi, 11hi or 12Hi messages.
Packet.
Second, the distribution mechanism handles two quantities: bits and message packets. The receiver gives these amounts
Each is assigned separately. The transmitter and receiver must keep a 16-bit unsigned count for message packets.
And hold a 32-bit non-symbolic calculator for a bit.
When sending message packets, the transmitter is subtracted from the message packet counter, and the body of the bit counter
The length is also reduced. The receiver then decrements its counter in the same manner when it receives the message packet. If any
A counter will be reduced to less than zero, then the sender will continue to be sent. Similarly, it is also prohibited from receiving
The distribution of greater than 2 ** 16-1 in the production of current message packets, and the allocation of the current bit of 2 ** 32-1.
The text length of the message packet is the product of the S (byte length) and C (number of bytes). Message format
Inly, these values always appear in the first part of the message packet.
The all, gvb and return commands will be corrected to handle the above two values.
As described below, their format is given by the control command. The GVB command is further modified to make it request
Return to empty allocation. The new GVB command has 4 8-bit fields. As mentioned earlier, the beginning two fields are this operation.
Code and connection.
The next two fields contain numbers FM and FB, which is used to control how much the return message packets and assignments. in case
These numbers are interpreted as follows: "The currently allocated 128th". If these numbers
The code is within the scope of 128 to 255, is explained as: "all currently allocated".
6 control signal
Control connection is changed to link 0; connection 1 is no longer used. Therefore, the new and old protocol can coexist.
According to the above description of the packet format, the message packet sent in the link is reported to other regular messages.
Wen has the same format. The byte length field must contain a value of 8.
The control signal cannot contain more than 120 bytes of body. Therefore, the value of the byte number is up to 120.
These restrictions are helpful for small hosts.
The control signal must contain integer control commands.
Therefore, the control command cannot be separated by the control signal.
7 connection assignment
The current connection is assigned as follows:
0 control connection
1 Old protocol control connection will be gradually eliminated
2 - 31 connection connection
32 - 190 Reserved
191 Use only network measurement center for the University of California Los Angeles
192 - 255 is effective for any independent experiment
8 fixed length control command
The ECO, ERP and ERR commands have a fixed length. The length of the ECO and ERP commands are 16 digits, including 8 digits.
The operation code and 8 are data. Err command is currently 96, including 8-bit opcode, 8-bit error, and
80 copies. 80 points are also sufficient for the longest non-ERR control command.
9 Control command format
As mentioned above, STR, ALL, GVB, RET, ECO, ERP, and ERR commands have changed. ; and
Added RST and RRP commands.
The format of these commands is as follows:
| 8 | 32 | 32 | 8 |
--- ------------------------------------------- ---- ----- | | | | | |
1. | STR | Send Socket | Receive Socket | |
| | | | | ^ |
--- ------------------------------------------- ---- - | -
|
| 8 | 8 | 16 | 32 | - Byte Size
--- ----- --------- ---------------------
| | | | | | |
2. | All | LINK | MSG Space | Bit Space |
| | | | | | |
--- ----- --------- ---------------------
| 8 | 8 | 16 | 32 |
--- ----- --------- ---------------------
| | | | | | |
3. | RET | LINK | MSG Space | Bit Space |
| | | | | | |
--- ----- --------- ---------------------
| 8 | 8 | 8 | 8 |
--- ----- --- -----
| | | | | | |
4. | GVB | LINK | FM | FB |
| | | ^ | ^ |
--- ----- - | - - | -
| | |
| - Bit Fraction
------ Message Fraction
| 8 | 8 |
--- -----
| | | | |
5. | Eco | Data |
| | | | |
--- -----
| 8 | 8 |
--- -----
| | | | |
6. | ERP | DATA |
| | | | |
--- -----
| 8 | 8 | 80 |
---- ----- -------------------- // ------------- ---------- | | | | |
7. | Err | | TEXT |
| | ^ | |
--- - | - ----------------------- // ------------- ----------
|
- Error Code
| 8 |
---
| | |
8. | RST |
| | |
---
| 8 |
---
| | |
9. | RRP |
| | |
---
The value of the operation code is:
NOP = 0
RTS = 1
Str = 2
CLS = 3
ALL = 4
Gvb = 5
Ret = 6
INR = 7
INS = 8
ECO = 9
ERP = 10
Err = 11
RST = 12
RRP = 13
Discussion on byte stream
Previously about the pipeline of the joint should become a bit stream has the most widely universal, but the efficiency is the most
low. Here, the pressure from improving efficiency and its related problems are considered.
The bit stream has two types of low efficiency.
1. The receiver host is requested to carry out the expense of a huge transformation, so that the successive message packet is
The text is connected. The sender host has to change the texture from us to change the words.
The boundary matches.
2. If possible, even if you only send one, it is also prohibited from sending an ANY article.
This is stored in uncertain time. These conditions are necessary to prevent any possible pauses
of. For example: Assume that processes A and B are performing sessions on a pair of coupling, one for each process
direction. At the same time, it is also assumed that each of these processes is just one output.
Then, if the network control program of the process A is desired to wait a waiting bit and after it
The calculation output packages from the process A, but can not send this waiting bit in time, then process B
The output will not be output, and B is also. Therefore, it is clear that unless the sender network control program
The buffer has a certain amount of data that is not necessary to receive, the sender network control
The order must assume another way and send data in time.
These considerations have led to the concept of "transmission unit" and must be known for the network control program. This question
The problem is the problem of typical and possible transmission units. For characters, 8 bits
The transfer unit of the transmission unit seems reasonable. For link-oriented interactions, the transmission unit is best
The link itself, and the length varies. In other words, it is best to think that the transmission unit is a character. Correct
For file transfer, the transmission unit is preferably a multiple of the two machine words length. However, if the transmission unit is too large
In the case of the last part of the document, it may not be from the entire transfer unit. At this time, if you want to make it,
The transmission unit should be arbitrarily, and it should be small enough. Therefore, the concept of the transmission unit seems to be byte, etc.
The amount, and the transmission unit is reduced.
Subsequent discussions about pauses and wakeups, there may be two bytes to associate with a single connection:
1. The length of the transmission from the sender process to the sender network control program is S. Sender network
The network control program must send a message packet when the connection is unlocked. Message packet counter
Less one. The bit counter is at least s, and the minimum S bit of the body is ready. Message message
Integer number of bytes must be included.
2. On the receiving end, there may be one for the transmission of the receiver network control program to the receiver process.
Different bytes length r. An example of r <> s is given by UCSB, which is transparently stored in binary
The file provides a file system. The host in use is reasonable with 36-bit bytes.
Although the UCSB file system wants to receive more than 32 bits.
Obviously, from the viewpoint of the network protocol, only byte s is related and is reported to each message.
The amount of communication in the STR command in the article. The selection of byte length R depends on the recipient user, and its meaning
Refers to the recipient network control program to wake up the frequency of the recipient processing. This may also happen:
That is, a recipient process is more complex between the recipient process and the receiver network control program.
Agreement. For example: Network Control Programs can scan and capture change characters before waking up the recipient process.
In the new protocol, the receiver can determine whether a connection is rejected according to the byte length provided.
begging.
From the concept, we can imagine the network control program to handle all bytes length, and this
Select can be maintained until the third level program (user program, log recorder, remote login, etc.). One
Some hosts, especially small hosts, can master enough knowledge about their three-level procedures to limit
The type of byte, and which one can be sent, which can be received. Although it is a local policy
The problem, the committee still strongly recommends that the network control program can process all bytes. In addition,
One of our committees strongly felt that the network control program should be written into a user process.
The output provides different byte length R, and the program that can receive all bytes s.
[This RFC document is from Enrico Bertone in April 1997]
[Component as a machine readable form to entered RFC online file]
RFC107 - OUTPUT OF THE HOST-Host Protocol Glitch Cleaning COMMITTEE
Host - Description of the Host Protocol Fault Clear Committee
1
RFC Document Chinese Translation Program
