Index Journeys
RFC 266 UNKNOWN MONITORING · STATUS

Network host status

A BBN table of ARPANET host test results from October 26 to November 5, 1971

On rfc-editor.org ↗
PUBLISHED
November 1971
AUTHORS
E. Westheimer
STREAM
Legacy
BUILDS ON
RFC 255 — Status of network hosts
OBSOLETED BY
RFC 267 — Network Host Status
REPORT PERIOD
October 26 to November 5
STATUS CODES
O, D, R, T, H
DOI
10.17487/RFC0266
LINEAGE · FROM THE RFC INDEXOpen full graph →
'71RFC 255Status of network hosts'71RFC 266Network host status'71RFC 267Network Host Status

RFC text

Original text · RFC Editor View on rfc-editor.org ↗ 
Network Working Group                      Ellen Westheimer
RFC #266                                   Bolt Beranek and Newman Inc.
NIC #7814                                  8 November 1971
Categories:  F, G, 3
Updates:  RFC 255
Obsoletes:  None










                          NETWORK HOST STATUS











   This RFC reports on the status of most.Network Hosts from October 26
   to November 5.  (Massachusetts celebrated Armistice day on Monday,
   October 25.) During these two weeks the general status of these hosts
   remained as it had been previously.

   The table on the following page summarizes the daily information on
   host status for this period.

NETWORK
ADDRESS  SITE       COMPUTER            DAY, DATE AND TIME (EASTERN)
-------  ----       --------            ----------------------------
                                T     W    Th     F    M    T    W    Th   F
                              10/26 10/27 10/28 10/29 11/1 11/2 11/3 11/4 11/5
                              1430  1200  1300  1300  1630 1330 1330 1330 1330
   1     UCLA       SIGMA-7     O     O     O     T    O    T    O    O    O
 *65     UCLA       IBM-360/91  O     D     O     O    O    O    O    O    O
   2     SRI(NIC)   PDP-10      O     O     O     O    D    O    D    O    O
  66     SRI(AI)    PDP-10      D     D     D     D    D    D    D    D    D
   3     UCSB       IBM-360/75  D     O     O     O    O    D    D    O    O
   4     UTAH       PDP-10      T     T     T     D    D    D    D    D    T
  69     BBN(TENEX) PDP-10      D     O     D     D    O    O    O    O    O
   6     MIT(MULTICS) H-645     O     D     D     O    O    O    O    T    O
  70     MIT(DM)    PDP-10      D     H     T     O    O    O    O    O    T
   8     SDC        IBM-360/67  D     D     D     D    D    D    D    D    D
   9     HARVARD    PDP-10      D     D     T     D    D    D    D    D    D
  10     LINCOLN    IBM-360/67  H     D     H     T    T    H    H    D    H

where

D=  Dead (Destination Host either dead or inaccessible [due to network
    partitioning or local IMP failure] from the BBN Terminal IMP.)

R=  Refused (Destination Host returned a CLS to the initial RFC.)

T=  Timed out (Destination Host did not respond in any way to the
    initial RFC, although not dead.)

H=  1/2 Open (Destination Host opened a connection but then either
    immediately closed it, or did not respond any further.)

O=  Open (Destination Host opened a connection and was accessible to
    users.)

* The UCLA IBM-360/91 currently has Remote Job Service (NETRJS), but
  has not implemented a full server Telnet System.  The BBN Terminal
  IMP is not equipped to test NETRJS;  however, we are assuming that
  receipt of the UCLA explanatory message indicates that NETRJS is also
  functioning.


       [ This RFC was put into machine readable form for entry ]
       [ into the online RFC archives by BBN Corp. under the   ]
       [ direction of Alex McKenzie.                   12/96   ]

ISO Plain Language

On this page
PROBLEMNetwork users needed to know whether most ARPANET hosts could be reached during the reporting period.
MECHANISMThe report lists daily connection-test outcomes from the BBN Terminal IMP using codes for open, dead, timed out, half-open and refused.
WHAT THE REPORT SHOWEDThe report says overall host status remained as before and was later replaced by RFC 267.

§1The Host Status Report

RFC 266 reports the status of most Network Hosts from October 26 through November 5. The author says the general status remained as it had been previously.

The table records results of tests from the BBN Terminal IMP and shows the day, date and Eastern time of each observation.

This report records what happened when most network hosts were tested during the listed period. It says the overall status had not changed from the previous report.

§2Reading the Test Results

O means the host opened a connection and was accessible to users. D means it was dead or inaccessible from the BBN Terminal IMP; T means it did not respond, although it was not dead. R means it refused the initial request, and H means it opened a connection but immediately closed it or stopped responding.

The report notes that UCLA's IBM-360/91 offered Remote Job Service but did not have a full Telnet server, so the BBN IMP's response was used as an indication that the service was functioning.

The letters summarize each test: open, inaccessible, timed out, refused, or only partly opened. The report also explains how it interpreted the UCLA system's Remote Job Service response.

§3Scope and Successor

The RFC presents the table as a status snapshot for the reporting period, with individual observations rather than a promise of continuous availability.

The unit metadata records RFC 267 as the document that later obsoleted RFC 266.

Each table entry is one test result at the time shown. RFC 267 later replaced this report.