As per Relevance of the word contents, we have this rfc below:
NWG/RFC# 695 MCK 5-JUL-75 15:38 32908
Official Change in Host-Host
Mark Krilanovich 1
Official Change in Host-Host Protocol 2
This is an official change to the Host to
protocol, this document should be filed with
protocol specification (nic -- 8246,) in the
Network Protocols Notebook (nic -- 7104,). 3
-- Jon Postel 3
This document corrects an ambiguity in the
host-host protocol, concerning the ERR command
Paragraph "f", page 35, of NIC 8246 defines
meaning of an ERR command with error code of 5 to
"socket (link) not connected". The error code
stated to apply to two cases, one in which a
command other than STR or RTS refers to a socket
is neither fully open nor fully closed, and the
in which a (non-control) message arrives over a
not being used for a connection. 4
The difficulty arises from the fact that the
of the "data" field of the ERR command has
different formats in the two cases. In the first,
is a host-host command, and in the second it is
message header. There is no reliable way for the
in the NCP receiving the ERR command (or a
reviewing an error log) to distinguish between the
cases, and therefore fullest use cannot be made of
ERR command. 5
The two cases are now defined to have different
codes. In addition, a new error code is defined
meaning "invalid host leader received". Therefore
paragraph "f" under "ERR - Error detected" is
replaced by the following: 6
f. Request on a non-open socket (Error code = 5) 7
NWG/RFC# 695 MCK 5-JUL-75 15:38 32908
Official Change in Host-Host
A request other than an STR or RTS was made for
socket (perhaps referenced by link number) that
not party to an fully established connection.
socket's inappropriate state could either be
only one RFC has been sent (not yet open) or
only one CLS has been sent (not yet closed).
"data" field contains the command in error;
value of any fill necessary is zeros. 7
g. Message on an unknown link (Error code = 6) 8
A message was received over a user link which
not currently being used for any connection.
contents of the "data" field are the message
followed by the first eight bits of text, if any
or zeros. 8
h. Invalid host header (Error code = 7) 9
A message was received either over the control
or a valid user link that had a host header
invalid format. Examples of when this subtype
be appropriate are the following: the M1 or M
fields were non-zero, the byte size was
(not 8 for a control link, zero for any link),
the declared length (byte size times byte count
exceeded the actual length. The contents of
"data" field is the message header padded
eight bits of zeros. 9
------- 10
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
