RFC 634 UNKNOWN INFRASTRUCTURE · ROUTING

Change in network address for Haskins Lab

Haskins Lab's network address moves from 197 to 201

On rfc-editor.org ↗
PUBLISHED
April 1974
AUTHORS
A.M. McKenzie
STREAM
Legacy
OLD ADDRESS
197
NEW ADDRESS
201
HOST NUMBER (UNCHANGED)
3
NEW IMP CONNECTION
Harvard, IMP #9
DOI
10.17487/RFC0634

RFC text

Original text · RFC Editor View on rfc-editor.org ↗
Network Working Group                                     Alex McKenzie
RFC # 634                                                 BBN-NET
NIC # 30445                                               April 10, 1974


               Change in Network Address for Haskins Lab


Sometime between May 8 and May 22, probably toward the end of that
period, the Haskins Laboratory "Very Distant Host" connection will be
moved from BBN (IMP #5) to Harvard (IMP #9).  The Host Number of the
Haskins machine will remain Host 3 (numbering from zero to three).
Thus, the Network Address of the Haskins Laboratory Host will change
from 197 to 201.  Since the date of the change is dependent on
installation of new circuits by the local telephone company, I am unable
to give the actual date more precisely.










       [ 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.            11/99 ]

AI ELI5

On this page
PROBLEMA research facility's host computer needs to move from BBN's network connection to Harvard's, requiring a network address change.
MECHANISMThe very distant host connection is physically moved from BBN IMP number 5 to Harvard IMP number 9, while the host number stays the same at 3.
ADDRESS UPDATE NEEDEDThe network address changes from 197 to 201 to reflect the new IMP connection, and users must update their routing information.

§1Address Change Notice

RFC 634 announces that the Haskins Laboratory Very Distant Host connection will move between telephone company circuits managed by different network facilities. The host was attached to BBN (the Boston node, IMP #5) and will move to Harvard (IMP #9). The host number—the identifier within that facility—remains 3, but the overall network address changes from 197 to 201 to reflect the new connection point.

The move depends on the local telephone company completing new circuits, so the exact date is uncertain but expected between May 8 and May 22, 1974. Users and network operators will need to update their address tables to route messages to the new location.

A computer is moving to a different box on the network, so its address number changes. The notice says which computers need to know the new address.

§2Network Address Scheme

In the ARPANET, network addresses are assigned based on the IMP (Interface Message Processor) serving the host and the host position within that IMP. The address 197 identified the Haskins Lab host on IMP #5 (BBN), and address 201 identifies the same host on IMP #9 (Harvard). The host number—position 3—is preserved because it remains the same logical resource; only its attachment point changes.

This scheme requires all network nodes to maintain current address tables so that routing decisions correctly locate hosts when they move between IMP connections. The RFC is thus not only an announcement but also an operational requirement: administrators must update their network configuration.

The address is a combination of which network box and which position in that box. When the computer moves to a different box, both parts of the address change even though it's the same computer.

§3Historic Notice

RFC 634 is an infrastructure notice from the earliest days of ARPANET. It documents the administrative process for managing host migrations on the network. The specific address change announced is historical and has no modern relevance, but the RFC demonstrates how early networks required explicit coordination and communication about topology changes.

This is just a note from 1974 telling other computers about a move. It does not affect anything today.