RFC40 more annotations about future agreements

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-6-10

Copyright: This Chinese translation copyright belongs to China Interactive Publishing Network. Can be used for non-commercial use free reprint, but the translation and copyright information of this document must be retained.

Network Working Group E. HARSLM

Request for Comments: 40 J.heafner

Rand

March 1970

More annotations about future agreement

(RFC40 More Comments on the fortcoming protocol)

We have recently discussed NWG / RFC # 36 and # 39 documentation with UCLA's Steve Crocker. Steve has explained our detailed explanation of errors, queries, and host conditions mentioned in NWG / RFC # 39 documentation.

Please make your point of view as soon as possible to correct future agreements.

Error message

is an 8-bit field that indicates the type of error. The predefined error code is listed below. is a 16-bit binary integer, which specifies how many binary bits (BIT), is a pseudo command.

The range of is expressed as follows:

00 unspecified error Types (not specified error type)

01-0F Resource Errors (Resource Error)

10-1f status errors (state error)

20-2f Content ErrorS (Content Error)

30-3F unused (unused, reserved)

Specific field value and its meaning are listed below:

Interpretation

00 Unexpected error

01 invalid resource request

02 Application resources are being occupied, then try again

03-0F Not used

Interpretation

10 Invalid , that is, connected but cannot communicate

11 Invalid .

12 Invalid , that is, no after the connection

13 blocking link message

14-1f is not used

20 Unknown command code

21 Disconnect link message

22 Invalid .

23 Invalid .

24 Invalid , that is, the link is not available

25 Invalid .

26 Invalid .

27 Invalid .

28 Invalid , ie not connected

29-2f is not used

30-ff is not used

Inquire

Or

is the query command specified in NWG / RFC # 39, and is the response information. The format of is shown below, refer to page 3 of NWG / RFC # 36.

:: = <16 Bit Count of Relevant Connection Table Entries>

:: =

Host Status

The status of an NCP process can be run, hang, wait, and so on. When an NCP changes its status as run, it will send a to each remote NCP that specifies its available. Then send the NCP can create a vector in the RFNM it receives. A NCP that receives can correct the validity of the sender NCP in its host status vector.

[This RFC WAS PUT INTO MACHINE READABLE FORM for Entry]

[INTO THE ONLINE RFC Archives By Richard Ames 6/97]

RFC40 More Comments on The Forthcoming Protocol More annotations for future agreements

1

RFC Document Chinese Translation Program