RFC 224 (rfc224) - Page 1 of 2
Comments on Mailbox Protocol
Alternative Format: Original Text Document
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
Comments on Mailbox Protocol
It should be noted that the Terminal IMP will be unable to
directly implement the currently-proposed mailbox protocol for
the following reasons:
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
participating in the currently-proposed mailbox protocol, this
should not be considered an objection to implementation of the
protocol, provided that Terminal IMP installations will be
guaranteed the right to "rent" mailboxes at some larger Host
site [the NIC is probably a good candidate]. With this capability,
a message destined for a Terminal IMP user would be shipped to the
site of the "rented" mailbox according to protocol and stored
there. A terminal IMP user could then periodically log in to that
