
1).” Date: Nov. 27, 1993.
24. Vinton G. Cerf, private e-mail correspondence, dated Nov.
27, 1993. Subject: “Re: Early Days of the ARPANET and
the NWG.”
25. “The Origins of RFCs” by Stephen D. Crocker is contained
in J. Reynolds and J. Postal, RFC-1000, 1.
26. The following quotes show some of the reasoning that went
into the choice of the initial ARPANET sites:
CCN’s [The Campus Computing Network of UCLA]
chance to obtain a connection to the ARPANET was
a result of the presence at UCLA of Professor L.
Kleinrock and his students, including S. Crocker, J.
Postel, and V. Cerf. This group was not only involved
in the original design of the network and the Host
protocols, but also was to operate the Network
Measurement Center (NMC). For these reasons the
first delivered IMP was installed at UCLA, and ARPA
was thus able to easily offer CCN the opportunity for
connection. (Completion Report Draft, III-689).
UCLA was specifically asked to take on the task of a
“Network Measurement Center” with the objective of
studying the performance of the network as it was
built, grown, and modified; SRI was specifically asked
to take on the task of a “Network Information Center”
with the objective of collecting information about the
network, about host resources, and at the same time
generating computer based tools for storing and
accessing that collected information (Completion
Report Draft, II-16).
The accessibility of distributed resources carries with
it the need for an information service (either
centralized or distributed) that enables users to learn
about those resources. This was recognized at the PI
[ed. Primary Instigators] meeting in Michigan in the
spring of 1967. At the time, Doug Engelbart and his
group at the Stanford Research Institute were already
involved in research and development to provide a
computer-based facility to augment human interaction.
Thus, it was decided that Stanford Research Institute
would be a suitable place for a “Network Information
Center” (NIC) to be established for the ARPANET.
With the beginning of implementation of the network
in 1969, construction also began on the NIC at SRI
(Completion Report Draft, III-60).
27. Completion Report Draft, III-67.
28. E-mail message to Con-Priv mailing list. Subject: “Re:
RFC-1000 (End of response to part 1).” Date: Nov. 27,
1993.
29. RFC-1000.
30. Completion Report Draft, III-67.
31. E-mail message to Con-Priv mailing list. Subject: “Re:
RFC-1000 (Response to part 2),” Date: Nov. 27, 1993.
32. Completion Report, III-30.
33. RFC-1000, 3.
34. ibid.
35. In RFC-1000, Stephen Crocker reports on the process of the
installation of the first IMP:
[T]ime was pressing: The first IMP was due to be
delivered to UCLA September 1, 1969, and the rest
were scheduled at monthly intervals.
At UCLA we scrambled to build a host-IMP
interface. SDS, the builder of the Sigma 7, wanted
many months and many dollars to do the job.
Mike Wingfield, another grad student at UCLA,
stepped in and offered to get interface built in six
weeks for a few thousand dollars. He had a gorgeous,
fully instrumented interface working in five and one
half weeks. I was in charge of the software, and we
were naturally running a bit late. September 1 was
Labor Day, so I knew I had a couple of extra days to
debug the software. Moreover, I had heard BBN was
having some timing troubles with the software, so I
had some hope they’d miss the ship date. And I
figured that first some Honeywell people would
install the hardware – IMPs were built out of
Honeywell 516s in those days – and then BBN people
would come in a few days later to shake down the
software. An easy couple of weeks of grace.
BBN fixed their timing trouble, air shipped the
IMP, and it arrived on our loading dock on Saturday,
August 30. They arrived with the IMP, wheeled it
into our computer room, plugged it in and the
software restarted from where it had been when the
plug was pulled in Cambridge. Still Saturday, August
30. Panic time at UCLA.
The second IMP was delivered to SRI at the
beginning of October, and ARPA’s interest was
intense. Larry Roberts and Barry Wessler came by for
a visit on November 21, and we actually managed to
demonstrate a Telnet-like connection to SRI.
36. RFC-1000, 4.
37. ibid.
38. Completion Report Draft, II-24.
39. ibid., III-69.
40. RFC-3, “Documentation Conventions,” Stephen Crocker,
April 1969, 1.
41. ibid.
42. ibid.
43. RFC-1336, 5.
44. This democratic community is in danger of being
fundamentally altered. This study of the history of the
development of the ARPANET in conjunction with
Chapter 3, “The Social Forces Behind the Development of
Usenet” is meant to help people understand where the Net
has come from, in order to defend it, and try to fight to
keep it open and democratic - “the eighth wonder of the
world,” as some call the Internet.
45. Some examples of comments upon comments include:
RFC-1 Crocker, S. Host software, 1969 April 7
RFC-65 Walden, D. Comments on Host/Host Protocol
document #1
RFC-36 Crocker, S. Protocol notes, 1970 March 16
RFC-38 Wolfe, S. Comments on network protocol from
NWG/RFC #36
RFC-39 Harslem, E.; Heafner, J. Comments on protocol
Page 35