Network Working Group Alex McKenzie Request for Comments #224 BBN NIC #7623 14 September 1971 Categories: D.7 Updates: none Obsoletes: none Reference: RFC #215, #221
It should be noted that the Terminal IMP will be unable to
a) The Terminal IMP is completely incapable of storing incoming messages for later printing or display.
b) The Terminal IMP is not expected to be able to perform as the "server" portion of any connection.
c) The Terminal IMP cannot provide programs for the
processing of a variety of types of input streams.
It currently supports the TELNET protocol, and is
expected to support at least one mode of Data
Transfer Protocol in the future. It is _not_ likely
to support the File Transfer Protocol. Furthermore,
when using the Data Transfer Protocol it will not
perform any transformations on the data stream
(e.g., interpretation of line printer form-control
"characters," translation from one character set to
another, etc.). It will be up to the "other end"
of the connection to set up and decode messages based
on the terminal type.
Although these limitations preclude Terminal IMPs from
[Page 1]
A technically unattractive alternative to this scheme would
We feel that, in addition to other arguments, it would be
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by BBN Corp. under the ] [ direction of Alex McKenzie. 12/96 ]
[Page 2]