RFC 22 (rfc22) - Page 1 of 2
Host-host control message formats
Alternative Format: Original Text Document
Network Working Group Vint Cerf
Request for Comments: 22 UCLA
October 17, 1969
Host-Host Control Message Formats
NWG/RFC 11 has been modified at UCLA; and will be republished. In
the meantime, it seems important to report a new control message
format which does not use 7-bit ASCII character mode of transmission.
All Host-Host control messages consist of sequences of 8-bit bytes of
the form:
...
It is reasonable to transmit more than one control message in any
given packet, although this is not mandatory.
Presently, 9 control messages have been defined by UCLA these are
given in the table below along with their parameters. The
interpretation is given from the point of view of the transmitting
host. ("L" or "Li" mean Link#, and are binary values.)
Control byte Parameter Interpretation
Please establish primary connection;
our output link # is L
Please establish auxiliary connection
parallel to our primary output link L.
The auxiliary output link is L2.
DK primary. Your primary output link
to us was L; our primary output link
to you is L2.
OK auxiliary. Your auxiliary output
link is Li, our auxiliary output link
is L2.
Not OK primary. We cannot establish a
primary connection. Your primary
output link number was L.
- Not OK auxiliary. We cannot establish an auxiliary connection. Your primary output link no was L2. Cerf