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: Li Jing (WaterCloud Watercloud@263.net)
Translation time: 2001-7-16
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 Stephen Wolfe
RFC # 692 UCLA CCN
NIC # 32734 June 20, 1975
Note for changes in Imp / Host protocol (RFCS 687 and 690)
(Comments On Imp / Host Protocol Changes, (RFCS 687 and 690))
This article RFC is mainly a collection of opinions that seems to be realistic for RFC 687, and can also be used as
Note for RFC 690.
The main problem now is as indicated by Postel, before the changed IMP and HOST transmission
The total length of the guide character is just 120, which is not an integer multiple of 8 or 36.
A solution that can be thought of is to increase the length of the leading character of Host to Host protocol, making it
The total length reaches 144 bits. But there is still a problem here, that is, after making such a change, the IMP must
Can be inserted or removed 24 bits to perform conversion between 144-bit preamble characters and 120-bit leading characters.
This problem exists in the above solution is quite obvious.
A better solution is to change the length of the IMP preamble character. I propose to use 104-bit length instead of the original 80-bit long.
degree. However, 104-bit length is not an integer multiple of an IMP word, which is indeed a problem. But if I
If you use the following rules, solve this problem is not a difficult thing.
1. Never use the last 8-bit delivery information.
2. The network is not required to pass them from the data source to the destination, or return them to the data source
3. When sending a message different from zero type (ie irregular message), IMP is allowed to send 96 bits, 104
Bit, 112-bit data, the specific choice to see the convenience of IMP at that time.
4. Similarly, if desired, 96-bit and 112 bits can also be used as the length of the leading character of the irregular message.
In this way, compare all HOST for modification to adapt to new standard protocols, modify the IMP program, so they can
It is a faster, and it is also a cheaper choice.
Another suggestion is to define a new type of IMP to Host messages. This news should have one including
Host's name (People Type Character String) and the table of Host's network address.
This message should be sent when each interface is reset, or when Host sends a new request to IMP,
When the above information is requested, this message can be sent as a response.
[THIS RFC WAS PUT INTO MACHINE READABLE FORM for Entry] [INTO THE ONLINE RFC Archives BY Alex Mckenzie with]
[Support from Gte, Formerly BBN Corp. 10/99]
RFC692-Comments On Imp / Host Protocol Changes, (RFCS 687 and 690)
Note for changes in Imp / Host protocol (RFCS 687 and 690)
1
RFC Document Chinese Translation Program
