Summary

  • RFC 1261 scheduled the 1991 transfer of Network Information Center services from SRI International to Government Systems Inc. It preserved familiar user-facing paths where it could, but it explicitly suspended all registration actions from 26 to 30 September so the WHOIS master database could move.
  • A hostname, mailbox, archive or Help Desk can make a service feel continuous. They are not evidence that the authority to write the registry is active, that a submitted change has entered the master record, or that a handoff succeeded without loss.

A service is more than its front door

The old Internet depended on institutions whose work was easy to mistake for a single machine. The Network Information Center answered questions, distributed RFCs and Internet-Drafts, helped users, maintained online services and handled registration. Some of those functions were visible to anyone who could connect. Others were the less visible authority to change a network number, assign a top-level domain name or alter a record held in the system of record.

RFC 1261, published in September 1991, announced a particular move: the NIC would transition from SRI International in Menlo Park to Government Systems Inc. in Chantilly on 1 October. The notice did not describe a new Internet or a new namespace. It described continuity work. SRI would continue responding to calls and requests through 30 September. GSI would carry forward registration, online information, Help Desk operations and RFC and Internet-Draft archive and distribution services.

That is why the notice is more useful than a simple before-and-after date. It separates functions that can be made familiar from functions that must be handed over carefully. Online services would, with a few exceptions, appear the same when a user connected to the new NIC host. The exceptions were attributed to a change from TOPS-20 to SunOS; the new host was identified as a Sun 470 SPARCserver running SunOS 4.1. An interface can preserve a habit even when the operating environment beneath it has changed.

The public surface therefore carried a limited meaning. It said a user might continue to find an online service in a recognisable place. It did not say that every stateful administrative operation was continuously available, that every old process was identical, or that the new operator had already completed every internal transfer needed to make a change authoritative.

The five-day interval that explains the handoff

RFC 1261 did not hide the harder part. Between 26 and 30 September, the WHOIS database would not be changed. All registration actions would be suspended. The stated reason was to transfer the master database to GSI. Registration was to resume on 1 October.

This is a small operational sentence with a large conceptual consequence. A registry is not merely a page that displays records. It is also a controlled process that decides whether a requested mutation becomes part of the master state. During the announced interval, users could still have reasons to look at a service, ask a question or send email. But an attempted registration was deliberately outside the active write path. The system had chosen consistency of the transferred master record over the appearance of uninterrupted change acceptance.

That choice creates several events that should not be collapsed. A person can compose a request. A mailbox can receive it. SRI can redirect it to GSI as appropriate. A Help Desk can answer a call. None of those events is itself a registry mutation. The event that matters for an assignment or change is a later, accountable act against the master database once the responsible system is able to accept it again.

The notice made this distinction concrete through its channels. From 26 September, postal and fax requests were to be directed to GSI. Electronic-mail requests were to continue to the HOSTMASTER and REGISTRAR mailboxes at NIC.DDN.MIL, with SRI redirecting mail to GSI as appropriate. The familiar address was an intake and continuity mechanism; it was not a proof that the master database remained writable. Forwarding can preserve a request’s route without deciding its disposition.

Compatibility is not custody

The language of continuity often invites an accidental overclaim. If services look the same, a reader may imagine that custody of every relevant state changed instantaneously and perfectly. RFC 1261 instead gives the careful reader a sequence: an announced future transition, continued service through a stated date, a pause on WHOIS changes, a transfer of the master database, redirected request channels and a planned resumption of registrations.

Each step has its own evidentiary scope. “We will make every effort” is a commitment, not an audit. “Users should be minimally impacted” is an expectation, not a measurement of experienced impact. “All registration activities will resume” names the intended control point; it does not certify any particular request as completed. A migration notice cannot retroactively prove that no record was lost, no queue was delayed, no user was confused or no policy decision changed. Those would require distinct records from the relevant operation.

This is not pedantry. Registry-like services often combine a low-friction public surface with a high-consequence state transition. The first benefits from familiarity. The second needs a precise ledger: which requests arrived, which were held, which authority applied the change, which version of the master record accepted it, and which result was communicated. If the public surface is allowed to stand in for that ledger, accountability becomes performative. Everyone can see that a door is open; nobody can say whether a particular change crossed the threshold.

A migration changes several kinds of time

RFC 1261 also teaches that “the transition date” is not one time. There was a scheduled effective date, 1 October. There was a five-day no-change interval. There was an earlier date when physical-mail and fax routing changed. There was a continuing electronic-mail address with possible redirection. There was the point at which a user reached the new online host. And there was the later point at which an individual registration action actually resumed and was processed.

Those clocks belong to different owners. A systems team can make a host reachable. A service desk can answer. A mail system can forward. A registry authority can reopen a write path. The RFC’s strength is not that it makes those tasks disappear into one word—“migration”—but that it leaves their seams visible.

For a historian, this prevents a false binary. The NIC did not simply exist at SRI on one day and exist at GSI on the next. Its public contact surfaces, operating environment, request-routing arrangements and mutation authority had related but distinct transitions. For an operator, the same distinction turns into a practical audit question: when a change was requested during a handoff, what evidence proves not only receipt, but admission to the authoritative state after the handoff?