Letter to TIP users-2
RFC 386

Document Type RFC - Unknown (August 1972; No errata)
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 386 (Unknown)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                    Bernard P. Cosell
Request For Comments # 386               David C. Walden
NIC # 11358                              Bolt Beranek and Newman Inc.
Categories:                              August 16, 1972
Updates:
Obsoletes:

                        LETTER TO TIP USERS -- 2

     This is the second letter to TIP users.  The first was RFC #365.
There will be more letters to TIP users as they seem to us to be a
good way to keep you informed about what's going on.  We suggest you
keep these letters with your TIP User's Guide (TUG) as we will use the
letters to provide documentation of TIP system changes which are made
before we can get TUG revisions printed and distributed. (It is almost
inevitable that the TUG revisions follow actual system changes.
Further- more, these letters will allow us more discussion of new
commands than in TUG.)

     Some of the changes we will be making to the TIP have been
suggested by TIP users. We won't bother with acknowledg- ments.

     The @PROTOCOL TO LOGIN and @PROTOCOL TO CLOSE BOTH commands will
be removed very soon. We presume no one uses these commands any more
since they have been replaced by @LOGIN and @CLOSE.

     As we warned in TIP Letter 1, the @LOGIN command will be given a
parameter soon, the Host number up to now given with the @HOST
command.  At the same time, @HOST will be changed so it does a
simultaneous @RECEIVE FROM HOST and @SEND TO HOST.  Presently, @HOST
is the same as @SEND TO HOST.

     Several changes will be made to the @TRANSMIT commands very soon.
First @TRANSMIT ON NO CHARACTERS and @TRANSMIT ON EVERY CHARACTER will
be removed. Their functions will be covered by the other @TRANSMIT
commands. @TRANSMIT NOW will continue to function as at present; it
will cause the one message presently being accumulated to be sent as
soon as possible.  @TRANSMIT ON LINEFEED and @TRANSMIT ON MESSAGE-END
will continue to cause the message being accumulated to be sent on
linefeed and CONTROL-S. However, they will additionally cause the
message being accumulated to be sent when the character buffer is
almost full. Thus, it will no longer be necessary to give a @TRANSMIT
EVERY <big number> with @TRANSMIT ON LINEFEED and @TRANSMIT ON
MESSAGE-END.  @TRANSMIT EVERY # will continue to cause the message
being accumulated to be sent as near as possible to every #th
character.  However, values of # which are bigger than the size of the

                                                                [Page 1]
RFC # 386                                                     NIC #11358

input buffer will cause transmission when the buffer is almost full;
and a value of 0 for # will reset the terminal to its initial setting
-- TRANSMIT-ON-LINEFEED mode off, TRANSMIT ON MESSAGE- END mode off,
and transmitting every character. Thus, TRANSMIT EVERY 0 has the
effect of the removed @TRANSMIT ON NO CHARACTER command, and @TRANSMIT
EVERY 1 has the effect of the removed @TRANSMIT ON EVERY CHARACTER
command.

     There are two ways outside of letters and the telephone to
communicate your suggestions and complaints to us: log into BBN-TENEX
and SNDMSG to WALDEN or use the NIC Journal system to send a message
to DCW3. Dave likes letters best, incidentally.

     We are going to remove the "NEWS" herald from the TIP's HELLO
message. The problem is that we don't know when everybody has read the
latest news so that we can turn off the herald.  Therefore, we can't
turn it off. Therefore, it is useless.  Check the NEWS every time you
use the TIP. If once the news begins printing you discover you have
already seen it, you can stop it by typing @CLOSE _LF_ (on a 2741 hit
"attention" first).

     A new TIP message will have been added by the time you get this
letter, the message TIP GOING DOWN. This message will be printed on
every TIP terminal shortly before the TIP is taken down for preventive
maintenance, new software releases, etc. (see RFC #381 for further
discussion of this topic). When this message is printed, all TIP users
should cleanly stop what they are doing with a Host. Eventually, this
message will include information on how long until the TIP will go
down, for how long it will be down, and why.

     While we are on the subject of TIP messages, let us mention that
we will be adding a number of new messages which we believe will
remove some of the present confusion about what the TIP is doing.
Unfortunately, we don't have the space to store the message text
strings, so, we will use numbers for the new messages. The format of
these messages will probably be something like M46 for message 46.
Perhaps when the TIPs get more core we can replace the number-messages
by text-messages.

     We are thinking of changing all the TIP LOGIN commands to OPEN
commands which would be more opposite to the CLOSE commands and not so
liable to confusion with Host LOGIN.

     On page 12 of the TUG is a description of how Hosts can send
commands to a TIP terminal. Be warned, if you decide to use this
Show full document text