Page Navigation:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56
Printable Version: RFC929.PDF
RFC 929 December 1984
Proposed Host-Front End Protocol
7XX Reserved for Future Expansion
8XX Reserved for Future Expansion
9XX Protocol Idiosyncratic Errors: Some error occurred that is
idiosyncratic to the particular off-loaded protocol being
used. The response code indicates the error.
Description of the Commands
As stated above, communication between the Host and the OPE at the
Command Level is accomplished using commands and responses. Commands
may be issued by either the Host or the OPE, and are used to
stimulate activity in the other entity. Some commands may only have a
meaningful interpretation in one direction, however. A response
indicates that the activity started by the command was completed, and
a code indicates success or failure of the command, and perhaps other
information related to the command as well.
Associated with each command is a set of parameters. The order in
which the parameters appear is significant to the correct operation
of the protocols. More information on the syntax of command
parameters can be found in the syntax descriptions.
The commands are:
- Begin: initiate communication between a process in the Host and
an off-loaded protocol interpreter in the OPE. (A Channel level
stream/connection will typically have been opened as a prior step.
All other commands, except No-op, apply to a stream on which a
successful Begin has been done.)
- Transmit: transmit data between a process in the Host and an
off-loaded protocol interpreter in the OPE.
- Signal: cause an out-of-band signal to be sent by the
off-loaded protocol interpreter to its peer, or indicate the
arrival of such a signal from the remote side.
- Condition: alter the off-loaded protocol interpreter's
operational characteristics.
- Status: transfer status requests or information between a
process in the Host and an off-loaded protocol interpreter in the
OPE.
Lilienkamp & Mandell & Padlipsky [Page 11]