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: McSewang Mcsewang@21cn.com)
Translation time: 2001-5-24
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 Note Steve Crocker, UCLA
RFC-6 10 April 1969
Session with Bob Kahn
Conversation with bob kahn
Yesterday I was talking to Bob Kahn in BB & N. We talked about IMP, Imp-Host communication, and
Code conversion in Host software.
BB & N is ready to convert 6,7,8,9-bit character code to 8-bit ASCII code to transfer and in target IMP
Convert it again on the collection. BB & N has developed a unique "one-to-one" plan form for each host. I
It is proposed that the area that uses 6-bit code may need to perform character switching, BOB said that it may switch when you need too much.
Leading overflow, I think the probability of this situation is small, and we should can endure this possible overflow,
In fact, overflow is almost inevitable.
For the considering of Host-IMP communication, we now use a 5-bit connection field, and use 1 bit to mark
Conversion. It may also be two-digit conversion marker, one for conversion before sending, one for transmission. This will make another
A handle can detect or control the system.
Host (Host) can send information or part of the information to its IMP to specify:
1, track
2, conversion
3, information is target IMP or Host (host)
4, send RFNM information
5, Host (host) is active or downtime
6, synchronize
7, format the error message
8, palm connection clearance
9, status request
IMP can send the following related information to its host:
1, conversion
2, RFNM has arrived
3, IMP activation or downtime
4, synchronize
5, host call no response
6, formatted error
7. State in IMP
I also introduced the contents of network documentation 1, 2, and 3 for BOB.
RFC 6 Conversation with Bob Kahn and Bob Kahn Session
1
