Browse Prior Art Database

Letter to TIP users-2 (RFC0386)

IP.com Disclosure Number: IPCOM000003565D
Original Publication Date: 1972-Aug-16
Included in the Prior Art Database: 2000-Sep-13
Document File: 4 page(s) / 12K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

B. Cosell: AUTHOR [+2]

Abstract

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.)

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 25% of the total text.

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 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

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...