Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

TIP/Tenex reliability improvements (RFC0636)

IP.com Disclosure Number: IPCOM000003708D
Original Publication Date: 1974-Jun-10
Included in the Prior Art Database: 2000-Sep-13
Document File: 7 page(s) / 20K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J.D. Burchfiel: AUTHOR [+4]

Abstract

RFC 636 J. Burchfiel - BBN-TENEX B. Cosell - BBN-NET NIC 30490 R. Tomlinson - BBN-TENEX D. Walden - BBN-NET 10 June 1974 TIP/TENEX Reliability Improvements

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

NWG/RFC# 636 JDB BPC RST DCW3 MLK 23-OCT-75 22:27 30490

TIP/TENEX Reliability Improvements

RFC 636 J. Burchfiel - BBN-TENEX

B. Cosell - BBN-NET

NIC 30490 R. Tomlinson - BBN-TENEX

D. Walden - BBN-NET

10 June 1974

TIP/TENEX Reliability Improvements

During the past months we have felt strong pressure to improve the

reliability of TIP/TENEX network connection as improvement in the

reliability of users' connections between TENEXs and TIPs would have

major impact on the appearance of overall network reliability due to the

large number and high visibility of TENEXs and TIPs. Despite the

emphasis on TIP/TENEX interaction, all work done applies equally well to

interactions between Hosts of any type.

The remainder of this RFC gives a sketch of our plan for improving the

reliability of connections bettween TIPs and TENEXs. Major portions of

this plan have already been implemented (TIP version 322; TENEX version

1.32) and are now undergoing final test prior to release throughout the

network. Completion of the implementation of the plan is expected in

the next quarter.

Our plan for improving the reliability of TIP/TENEX connections is

concerned with obtaining and maintaining TIP/TENEX connections,

gracefully recovering from lost connections, and providing clear

messages to the user whenever the state of his connection changes.

When a TIP user attempts to open a connection to any Host, the Host may

be down. In this case it would be helpful to provide the user with

information about the extent of the Host's unavailability. To facilitate

this, we modified the IMP program to accept and utilize information from

a Host about when the Host will be back up and for what reason it is

down. TENEX is to be modified to supply such information before it goes

down, or through manual means, after it has gone down. When the TIP

user then attempts to connect to the down TENEX, the IMP local to the

TENEX returns the information about why and for how long TENEX will be

down. The TIP is to be modified to report this sort of information to

the user; e.g., "Host unavailable because of hardware maintenance --

expected available Tuesday at 16:30 GMT".

The TIP's logger is presently not reentrant. Thus, no single TIP user

can be allowed to tie up the logger for too long at a time; and the TIP

NWG/RFC# 636 JDB BPC RST DC...