Index Journeys
RFC 432 UNKNOWN NETWORK · OPERATIONS · TOPOLOGY

Network logical map

A request to review the ARPANET logical map

On rfc-editor.org ↗
PUBLISHED
December 1972
AUTHORS
N. Neigus
STREAM
Legacy
DOI
10.17487/RFC0432

RFC text

Original text · RFC Editor View on rfc-editor.org ↗

This text was converted from the RFC Editor's PDF edition and may contain conversion errors; the layout is approximate. The PDF is the reference copy.

Network Working Group                                          N. Neigus
Request for Comment: 432                                         BBN-NET
NIC: 13490                                                 December 1972


                           Network Logical Map

  Attached is the logical map of the network as of December 30, 1972.
  The ovals indicate the host computers that we think are connected to
  each IMP, with the double oval implying an interface. If there are
  any errors in the map or if your status vis-a-vis connected hosts, is
  going to change within the next few months, please contact:


            Nancy J. Neigus

            Bolt Beranek and Newman Inc.
            50 Moulton Street

            Cambridge, Ma. 02138

            617-491-1850      X511

  or leave a message for NJN at the NIC. In the future we would
  appreciate being notified any time there is such a change.


  NJN/jm

  Attach.


Attached is a figure of the ARPA NETWORK, LOGICAL MAP, JANUARY 1973


          [This RFC was put into machine readable form for entry]
      [into the online RFC archives by Helene Morin, Via Genie 12/99]

ISO Plain Language

On this page
PROBLEMNetwork sites needed a shared view of which host computers were connected to each IMP.
MECHANISMThe RFC attaches a logical map dated December 30, 1972, and explains what its oval symbols represent.
PURPOSE OF THE MAPSites were asked to report errors and planned connection changes to BBN or the NIC.

§1A Snapshot of Network Connections

Nancy Neigus at BBN says the attached logical map represents the ARPANET as of December 30, 1972. The map uses ovals for host computers believed to be connected to each IMP. A double oval indicates an interface.

The accompanying drawing is not included in the plain-text version of this RFC.

The map was intended to show which hosts were connected to each IMP at the end of December 1972. Its symbols distinguish hosts and interfaces.

§2Checking and Updating the Map

The notice asks sites to contact Nancy Neigus if the map contains errors or if their connections to hosts are expected to change in the next few months. It also asks sites to report such changes in the future.

Users could contact BBN by telephone or leave a message for NJN at the NIC.

Sites were asked to check their connections on the map and report mistakes or planned changes. The notice gives phone and NIC message options for contacting BBN.

§3Keeping Network Information Current

The RFC treats the map as a maintained record: sites should report changes when they occur, not only while reviewing this copy. The note contains no protocol specification; it is a coordination request tied to the attached network diagram.

The map could remain useful only if sites reported changes to their connections. This RFC asks for those updates rather than defining a network protocol.