
66, 11, pp 1386-1408, November 1978. This is a special issue devoted to packet
internetworking issues.)
Kirstein adds: “In fact the original grant I had from ARPA was to connect in two
computers, the large IBM Computer at the Rutherford Laboratory near Oxford and the
CDC in London. Both were the centre of centralised proprietary interactive and remote
job entry networks. This connection was made as one between two networks from the
beginning. It looked to ARPAnet as if IBM was directly connected as a Host, and any
ARPAnet Host looked like a remote IBM device.” (Higginson, PL, PT Kirstein and AV
Stokes: “The Problems Connecting Hosts into ARPAnet via Front-end Computers,”
Workshop on Distributed Computer Systems, Darmstadt (1974). Lloyd, D and PT
Kirstein: “Alternative Approaches to the Interconnection of Computer Networks,”
London, Proc European Comp. Conf. on Communications Networks, London, Online,
499-515 (1975))
Kirstein continues: “This was not an Internet design; this was connections at an
application level, and hence not very rugged. However, this mechanism continued for
the next 15 years, while the British NREN became quite sophisticated, including packet
switching, their version of the Domain Name Service (Name Registration Scheme),
FTP, Telnet, mail, etc. By 1990, while the links to the Internet had long gone IP, the
hosts on the British networks were running a totally different set of protocols. While
history (and the analysis we made at the time) showed this was not the best, rugged or
fast way to go, it allowed both interconnectivity and independent development of
protocol structures to co-exist until all the bugs had been resolved in the Internet
protocols, and also commercial products to be produced by new firms such as Cisco.”
(Kirstein, E-mail, Oct 3, 2002)
16. The Brighton INWG meeting took place just after the NATO Advanced Institute.
Though the original protocol was called TCP, it later was split into two parts and from
then on called TCP/IP. When the paper describing the philosophy and design for TCP
was officially published in May, 1974, the authors, Vint Cerf and Bob Kahn, wrote:
“The authors wish to thank a number of colleagues for helpful comments during early
discussions of international network protocols especially R. Metcalfe, R. Scantlebury,
D. Walden, H. Zimmerman. D. Davies and L. Pouzin who constructively commented
on the fragmentation and accounting issues, and S. Crocker who commented on the
creative destruction of associations.”(p. 643) (See also, Ronda Hauben, “A Protocol for
Packet Network Intercommunication,” in The Encyclopedia of Computers and
Computer History. Raul Rojas, Editor, Fitzroy Dearborn, Chicago, 2001, vol 2, pp.
652-653.)
16a. Describing the process of creating a protocol specification, or Request for
Comment (RFC), Mills writes, “One of the principal drivers in the standardization
effort was the published TCP and IP standards, which were issues both as RFCs and
Military Specifications (MILSPEC). Bob considered this a major coup. Later, DoD
policy saluted COTS (Commercial Off the Shelf) and told the agencies to avoid
Page 46