Scheduling IMP/TIP down time
A change to how the Network Control Center notifies sites about IMP or TIP downtime.
McKenzie, A.M., "Scheduling IMP/TIP down time", RFC 622, DOI 10.17487/RFC0622, March 1974, <https://www.rfc-editor.org/info/rfc622>.
@misc{rfc622,
series = {Request for Comments},
number = 622,
howpublished = {RFC 622},
publisher = {RFC Editor},
doi = {10.17487/RFC0622},
url = {https://www.rfc-editor.org/info/rfc622},
author = {A.M. McKenzie},
title = {{Scheduling IMP/TIP down time}},
pagetotal = 3,
year = 1974,
month = mar,
} RFC text
Network Working Group Alex McKenzie
RFC # 622 BBN-NET
NIC # 21995 March 13, 1974
Scheduling IMP/TIP Down Time
From time to time it is necessary for an IMP or TIP to be taken down
other than during its scheduled Preventive Maintenance period. Examples
of such cases are retrofit programs and the off-line diagnosis and
repair of intermittent problems. In the past we have scheduled these
downs with our "primary site contact" at the affected site; in our view
this individual was responsible for representing all of the hosts (and
TIP users) connected to that IMP/TIP. Although this policy has worked
well in the past, the recent proliferation of Very Distant Hosts,
together with complaints from representatives of other (local or
distant) Hosts, has caused us to review our procedures.
This note announces a modification of the previous policy. We will
continue to schedule IMP/TIP downs with our "primary site contact." We
will continue to consider this individual a representative of all Hosts
connected to that IMP/TIP, with the following exception. Any Host
organization wishing to be notified by telephone that down time has been
scheduled for their IMP/TIP may nominate some individual as a "secondary
contact." The name of the secondary contact, together with a telephone
number where he/she can be reached, should be submitted to me by any of
the following methods:
US mail
Network Control Center
Bolt, Beranek and Newman Inc.
50 Moulton Street
Cambridge, Mass. 02138
ATTN: Alexander McKenzie
Journal system
Ident = AAM
Network mail
MCKENZIE at BBN-TENEX
The NCC operators will notify the secondary contact by telephone after
scheduling down time with the primary contact.
Following is the current list of "primary site contacts" (and backup
"primary" contacts):
UCLA - Anita Coley (Dave Crocker, Lou Nelson)
SRI - Jim White (Don Wallace)
UCSB - Ron Stoughton (Bob Ploger)
Utah - Dennis Ting
BBN (IMP) - Steve Chipman
MIT-MAC - Al Vezza (Abhay Bhushan)
RAND - Roy Yashimura
SDC - Ken Brandon (Doug Pintar)
Harvard - Bob Nickerson
Lincoln - John Laynor
Stanford - Ted Panofsky (Lester Earnest)
Illinois - Jack Bouknight (Gary Grossman)
Case - Dave Reide (Alan Rosenfeld)
Carnegie - Bill Broadley
AMES IMP - John McConnell (Paul Zima, Dick Brown)
AMES TIP - Bob Linebarger (Toby Gonzales, Glen Holtzer)
MITRE - Jean Iseli (Susan Poh)
RADC - Tom Lawrence (Grant Strength)
NBS - Tom Pyke (Bob Rosenthal)
ETAC - Capt. Petregal (John Smith)
LLL - Robert Abbott (Bob Sherwood)
ISI - Tom Boynton (Jerry Pipes)
USC - James Pepin
GWC - Capt. Goldsmith (Peggy Irving)
DOCB - Dave Lillie (Sky Stevenson)
SDAC - Buz Owen (Vernon Bruffey, Rick Perez, Bill Whyte)
Belvoir - Ken Gibson (Larry Wright)
ARPA - Steve Crocker (Pam Cutler)
Aberdeen - Melvin Wrublewski
CCA - Phil Peterson (Hal Murray)
Xerox - Robert Taylor (Bob Metcalfe)
FNWC - R. Mottencamper (Merrill Peterson)
LBL - Bob Fink (Jose Alvarez)
UCSD - Jim Madden (Grant Rostad)
Hawaii - John Davidson
RML - Mike Young
NORSAR - Per Tveitane (Oddnund Hansen)
London - Peter Kirstein (Hugh Gamble)
Tymshare - Mike Marrah (Robert Martinez)
MIT-IPG - Leo J. Ryan (Mike Padlipsky)
Moffett - Ed Mortenson (Gene Lichner)
Rutgers - Tom Webb (Jeff Broido)
Wright-Patterson - Capt. Woodward (Fred Pitts)
Please let me know if the "primary" contact for your site should be
changed.
[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Alex McKenzie with ]
[ support from GTE, formerly BBN Corp. 10/99 ]
ISO Plain Language
On this page
§1Scheduling IMP and TIP Downtime
An IMP or TIP may need to be taken out of service outside its scheduled preventive-maintenance period, for example for retrofit work or diagnosis and repair of intermittent problems. The Network Control Center had scheduled these periods with the affected site's primary contact, who was treated as representing all connected Hosts and TIP users.
McKenzie says that the growing number of Very Distant Hosts and complaints from other host representatives prompted a review of the procedure. The primary contact arrangement remains in place.
The Network Control Center continues to arrange equipment downtime with a site's primary contact. The note adds a way for another organization to request a separate phone notification.
§2Nominating a Secondary Contact
Any Host organization that wants a telephone notice when its IMP or TIP downtime is scheduled may nominate a secondary contact. The organization must provide that person's name and a telephone number where they can be reached.
Details may be sent by US mail to the Network Control Center at BBN, through the Journal system using Ident AAM, or by network mail to MCKENZIE at BBN-TENEX. NCC operators telephone the secondary contact after they schedule the downtime with the primary contact.
An organization can name someone else for the NCC to call about scheduled downtime. It sends the person's name and phone number by mail, the Journal system or network mail.
§3Primary Site Contacts
The RFC lists the current primary site contacts and, where supplied, backup primary contacts for network locations. The list includes the named representatives for sites such as UCLA, SRI, UCSB, BBN, MIT-MAC, Harvard, Stanford, Hawaii and London.
The memo asks sites to report if their primary contact should be changed. The contact list supports the scheduling process described in the note.
The note publishes the people currently listed as each site's primary contact. Sites are asked to report changes to those contact details.