ACM Turing Award Robert E. Kahn: Disagreements | Network, Not Protocol

The A.M. Turing Award profile of Robert E. Kahn that the Association for Computing Machinery publishes, written by Janet Abbate, says that TCP/IP is “the basis for the current internet” and that the connection of ARPANET, PRNET and SATNET in 1977 “became the first incarnation of the Internet”, while Robert E. Kahn said in his oral history of February 17, 2004 that “What’s transformed society was the rapid propagation of networking, the creation of commercial Internet service providers”.

Preamble: I examine the profile of Robert E. Kahn on the A.M. Turing Award site of the Association for Computing Machinery, the biography signed “Author: Janet Abbate” under the award citation of 2004 that Robert E. Kahn shares with Vinton G. Cerf. I test six statements of the profile against Robert E. Kahn's own words in his oral history of February 17, 2004, the dated documents that other pages of marknichols.com reproduce, the profile's own lines, and the Governing Definitions of marknichols.com. Exhibit A at section 9.0 reproduces the profile line by line, numbered and anchored, and every finding on this page cites those line numbers. This page is Disagreement 92 in the standing index of the series, Disagreements of Published Claims | Network, Not Protocol, and a finding on this page is cited by that number followed by the finding's locus, as Disagreement 92, 1.1.

Opinion Rules: You are visiting my record, and I am the subject matter expert on it. If you are a subject matter expert too, I want to hear from you: bring your document and I will answer it on the record. If you are not, you are welcome here to read and to learn. The documented-challenge terms of marknichols.com and the condition on opinion are stated at F40 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking, and they govern this page.

Conditional on the Governing Definitions: Every finding on this page is conditional on the Governing Definitions D1 through D13 of marknichols.com, which are reproduced in full in the Definitions Addendum at the bottom of this page.

0.0 This section records the profile this page examines, its author, the reading of it, and the definitions on which the findings depend.

0.1 The source examined on this page is the page “Robert E Kahn - A.M. Turing Award Laureate” of the Association for Computing Machinery at https://amturing.acm.org/award_winners/kahn_4598637.cfm. The page carries the birth, education, experience, honors and awards of Robert E. Kahn, the heading “ROBERT (“BOB”) ELLIOT KAHN” with “United States – 2004”, the award citation, and a biography that ends with the line “Author: Janet Abbate”. This page read the biography view of the profile in full in a browser on November 13, 2026, all of its text from “BIRTH:” through “Author: Janet Abbate”, and did not read the separate views of the profile headed Short Annotated Bibliography, ACM Turing Award Lecture Video, Research Subjects and Additional Materials.

0.2 The profile carries no date of publication or revision, so the date of the biography is unknown on this page. The award citation is the text of the Association for Computing Machinery, the biography is signed by Janet Abbate, and the author of the lists of birth, education, experience, honors and awards is not named, so the author of those lists is unknown on this page. Exhibit A reproduces the text as the page displays it, with each non-breaking space of the page given as an ordinary space, and divides it into sixty-six lines: each field label, heading and caption is a line of its own, and each paragraph is divided into its sentences.

0.3 D1 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking defines the Internet as “The publicly joinable network of networks of the registry lineage”, and D6 states: “Protocols are utilities whose messages the networks carry; they are not the networks, and they are not the Internet.” The Definitions Addendum at section 10.0 reproduces D1 through D13 in full.

0.4 The citation and the opening of the biography are shared with the profile of Vinton G. Cerf on the same site, which ACM Turing Award Vinton G. Cerf: Disagreements | Network, Not Protocol, Disagreement 16, examines. This page cites Disagreement 16 where it has read a document that this page relies on, and names that page as the reader of the document each time.

1.0 The profile says that Vinton G. Cerf and Robert E. Kahn “led the design and implementation of the Transmission Control Protocol and Internet Protocol (TCP/IP) that are the basis for the current internet”, while under D6 protocols are not the networks and are not the Internet.

1.1 Line 15, the first sentence of the biography, says: “Vinton G. Cerf and Robert E. Kahn led the design and implementation of the Transmission Control Protocol and Internet Protocol (TCP/IP) that are the basis for the current internet.”

1.2 The award citation at line 14 credits the two men “for pioneering work on internetworking, including the design and implementation of the Internet's basic communications protocols, TCP/IP, and for inspired leadership in networking.” The citation credits the design of protocols, and this page does not dispute it. Line 15 goes further and makes the protocols “the basis for” the Internet.

1.3 The profile's own lines describe the networks as existing before the protocols that joined them. Line 41 says that “By 1973 Kahn was already thinking about connecting ARPA’s packet radio and satellite networks to the ARPANET,” and line 52 describes “a set of gateways or routers that would sit between networks, passing traffic between them”. In excerpt 16 of ETHW Robert Kahn Oral History: Disagreements | Network, Not Protocol, Robert E. Kahn says: “The Internet was sort of a lot of LANs connected to the Arpanet with linkages to satellite nets.”

1.4 The kind is a definitional finding. Under D6 the protocols are utilities whose messages the networks carry, and under D1 the Internet is the publicly joinable network of networks of the registry lineage, so a protocol is not the basis of the Internet. The words “that are the basis for” are recorded in Soft Verbs: A Running Register | Network, Not Protocol. Governing Definitions, D1 and D6.

1.5 Corrected statement: Vinton G. Cerf and Robert E. Kahn led the design of the Transmission Control Protocol, first published in “A Protocol for Packet Network Intercommunication” in May 1974, and the protocol suite that followed it is carried by the networks of the Internet and is not their basis.

2.0 The profile says that the experimental connection of ARPANET, PRNET and SATNET in 1977 “became the first incarnation of the Internet”, while Robert E. Kahn called the same three networks “a little research experiment, three nets that DARPA had been building”, and under D1 the Internet was born in 1991.

2.1 Line 59 says: “Cerf and Kahn oversaw the implementation of TCP and the experimental connection of ARPANET, PRNET and SATNET in 1977; this became the first incarnation of the Internet.”

2.2 The profile names the three networks as research networks of the Defense Advanced Research Projects Agency. Line 37 says that Robert E. Kahn “initiated a ground-based packet-radio project, called PRNET, which started experimental operation in 1975”, and line 39 calls SATNET “an experimental transatlantic network operated in conjunction with the British Post Office and Norwegian Telecommunications Authority.” In excerpt 24 of ETHW Robert Kahn Oral History: Disagreements | Network, Not Protocol, Robert E. Kahn says that “we started it out as a little research experiment, three nets that DARPA had been building”.

2.3 The kind is a definitional finding. Under D1 the Internet is the publicly joinable network of networks of the registry lineage born in 1991, and the connection of 1977 joined three experimental networks of one research program, which no buyer could join. The words “this became the first incarnation of” are recorded in Soft Verbs: A Running Register | Network, Not Protocol. Governing Definitions, D1.

2.4 Corrected statement: In 1977 the Defense Advanced Research Projects Agency connected three of its experimental networks, the ARPANET, the packet radio network PRNET and the Atlantic Packet Satellite Network SATNET, using the Transmission Control Protocol, in an experiment that Robert E. Kahn described on February 17, 2004 as “a little research experiment”.

3.0 The profile credits the seminar of June 1973 with laying “the groundwork for the global spread of the Internet” and credits the Internet architecture with features “that would facilitate the Internet’s rapid expansion in the 1990s”, while Robert E. Kahn and Vinton G. Cerf credited the growth of the 1990s to the commercialization that the National Science Foundation facilitated, and Robert E. Kahn credited it to “the creation of commercial Internet service providers”.

3.1 Line 46 says: “In addition, Kahn and Cerf demonstrated farsighted leadership by inviting networking experts from around the world to weigh in on the Internet design at a seminar in June 1973.” Line 47 says: “This move not only led to more robust protocols, but also laid the groundwork for the global spread of the Internet.” Line 54 says: “The Internet architecture was designed to make minimal demands on participating networks, to provide a seamless user experience, and to scale up gracefully, key features that would facilitate the Internet’s rapid expansion in the 1990s.”

3.2 In "Ask the White House" of November 9, 2005, on the archive of the White House of George W. Bush, Vinton G. Cerf and Robert E. Kahn answered the question “Did you ever expect the internet to get so big?” with the words: “Their actions taken in the early 1990s to facilitate commercialization, supported by the US Congress, led to explosive Internet growth.” The word “Their” in that sentence refers to the National Science Foundation, which the sentence before it names.

3.3 In excerpt 22 of ETHW Robert Kahn Oral History: Disagreements | Network, Not Protocol, Robert E. Kahn says: “What’s transformed society was the rapid propagation of networking, the creation of commercial Internet service providers, which really started in the late 1980s with places like UUnet and PSInet and a variety of others, both in the US and around the world. That’s what made it an international phenomenon.”

3.4 The kind is a definitional finding. Under D6 the growth of the Internet is credited to the networks and not to the protocols, and the two dated statements of Robert E. Kahn in 3.2 and 3.3 credit the growth to commercialization and to commercial Internet service providers, not to a seminar of 1973 or to the design of a protocol architecture. The words “laid the groundwork for” and “would facilitate” are recorded in Soft Verbs: A Running Register | Network, Not Protocol. Governing Definitions, D6.

3.5 Corrected statement: The seminar of June 1973 improved the design of the protocols, and the global spread of the Internet in the 1990s came from the commercial networks and Internet service providers that the commercialization of the early 1990s admitted, as Vinton G. Cerf and Robert E. Kahn wrote on November 9, 2005.

4.0 The profile says Robert E. Kahn “began experimenting with using the Intelsat I satellite to link the Arpanet to sites in Britain and Norway”, while the satellite compendium of NASA of June 1973 records Intelsat I retired on August 21, 1969 and RFC 829 of November 1982 identifies an INTELSAT-IV satellite for the Atlantic Packet Satellite experiment.

4.1 Line 38 says: “Kahn also began experimenting with using the Intelsat I satellite to link the Arpanet to sites in Britain and Norway (where ARPA conducted seismic monitoring to detect Soviet underground nuclear tests).” The line follows line 36, which places Robert E. Kahn at the Information Processing Techniques Office “In late 1972,” and line 37, which begins “In 1973,” and line 39 says that “In 1975 this effort grew into the Atlantic Packet Satellite Network (SATNET)”.

4.2 Section 4.0 of ACM Turing Award Vinton G. Cerf: Disagreements | Network, Not Protocol, Disagreement 16, examines the same words in the profile of Vinton G. Cerf and records two documents. The Compendium of Satellite Communications Programs of NASA, published in June 1973, records in its Table 10-1 that Intelsat I was retired into reserve on January 20, 1969, reactivated on June 29 and retired on August 21, 1969. RFC 829 of November 1982 by Vinton Cerf identifies an INTELSAT-IV satellite for the Atlantic Packet Satellite experiment and dates the development of the experiment to 1973.

4.3 The kind is a documentary finding. Line 38 is false as written under F56, because Intelsat I was retired in 1969, three years before Robert E. Kahn joined the Information Processing Techniques Office, and the Atlantic Packet Satellite experiment used an INTELSAT-IV satellite, as the documents that Disagreement 16 records at its 4.0 show. Governing Definitions, F56.

4.4 Corrected statement: The Atlantic Packet Satellite experiment of the Defense Advanced Research Projects Agency, whose development began in 1973 and which the profile says became the Atlantic Packet Satellite Network, SATNET, in 1975, used an INTELSAT-IV satellite, as RFC 829 of November 1982 records.

5.0 The profile says that in 1978 Vinton G. Cerf “collaborated with Jon Postel and Danny Cohen” to “reformulate TCP as a set of two protocols”, while Jon Postel's IEN 2 of August 15, 1977 had already proposed “a new distinct internetwork protocol” separated from the Transmission Control Program.

5.1 Line 56 says: “In 1978 he collaborated with Jon Postel and Danny Cohen, both at the University of Southern California Information Sciences Institute, to reformulate TCP as a set of two protocols: a host protocol (TCP) and a separate internetwork protocol (IP).”

5.2 Wikipedia Defines the Internet Protocol: Disagreements | Network, Not Protocol records Jon Postel's IEN 2 of August 15, 1977, which proposes “a new distinct internetwork protocol” separated from the Transmission Control Program, and records Jon Postel as the author of that proposal and of every specification of IP from 1978 through 1981.

5.3 The kind is a scope overstatement. Line 56 makes Vinton G. Cerf the subject of the separation of TCP and IP and dates it to 1978, while the dated proposal of the separation is Jon Postel's IEN 2 of August 15, 1977. This page does not dispute that Vinton G. Cerf, Jon Postel and Danny Cohen worked together on the protocols in 1978, and it records that the line leaves out the author and the date of the proposal.

5.4 Corrected statement: Jon Postel of the University of Southern California Information Sciences Institute proposed the separation of a distinct internetwork protocol from the Transmission Control Program in IEN 2 of August 15, 1977, and the separate Internet Protocol was specified by Jon Postel from 1978 through RFC 791 of September 1981.

6.0 The profile dates the start of Robert E. Kahn's work at Bolt Beranek and Newman to 1966 in its list of experience and to 1967 in its biography.

6.1 Line 6, the list of experience, gives “Bolt, Beranek and Newman (BBN) (on leave from MIT) (1966-72)”. Line 20 says that Robert E. Kahn “joined the electrical engineering department at MIT as an assistant professor in 1966”, and line 21 says that “in 1967 Kahn arranged a leave of absence from MIT in to work at the firm of Bolt, Beranek and Newman”.

6.2 The kind is a documentary finding. The profile gives two different years for the same event, 1966 in its list of experience and 1967 in its biography, and this page has read no dated document that decides between them, so the year in which Robert E. Kahn began work at Bolt Beranek and Newman is unknown on this page.

7.0 Fifty-eight lines of the profile are examined and not disputed on this page, and several of them record in the profile's own words the findings that marknichols.com makes.

7.1 Line 36 and line 60 record that Robert E. Kahn joined the Information Processing Techniques Office of the Defense Advanced Research Projects Agency in late 1972 as a program manager and “became Director of IPTO in 1979, serving until 1985.” The profile names the office that Robert E. Kahn directed and not the agency, as section 1.0 of ETHW Robert Kahn Oral History: Disagreements | Network, Not Protocol, Disagreement 91, finds.

7.2 Line 44 says that “In the spring of 1973, Kahn approached Cerf with the idea of developing a system for interconnecting networks—what would eventually be called an “internet.”” The profile dates the idea to 1973, as Robert E. Kahn's own account does in section 4.0 of Disagreement 91 and as section 11.0 of Internet Society Brief History of the Internet: Disagreements | Network, Not Protocol, Disagreement 6, records, and it gives the word internet in lowercase for a system for interconnecting networks, which is the lowercase sense that the Governing Definitions give the word.

7.3 Line 23 records that in 1968 Lawrence Roberts of the Defense Advanced Research Projects Agency issued the request for proposals for the ARPANET, and line 28 says that “Kahn played a key role in system design for the proposal that ultimately won BBN the contract”. Robert E. Kahn says in excerpt 6 of Disagreement 91 that “I actually wrote the technical part of the proposal”, and in excerpt 23 that Larry Roberts “really architected the whole thing”, and the profile does not claim more than that. The words “played a key role in system design for” are recorded in Soft Verbs: A Running Register | Network, Not Protocol.

7.4 Line 51, line 52 and line 53 describe the architecture of 1974 as a host protocol and “a set of gateways or routers that would sit between networks,” which places the protocol in the hosts and the gateways between networks that already existed, as section 11.0 of Disagreement 6, at its 11.10, records.

7.5 The remaining fifty lines, 1 through 5, 7 through 14, 16 through 20, 22, 24 through 27, 29 through 35, 37, 39 through 43, 45, 46, 48 through 50, 55, 57, 58 and 61 through 66, state headings, field labels, dates of birth and education, honors, captions of video, the award citation, the designs of the protocols and the later work of Robert E. Kahn at CNRI, and no dated document on this page contradicts them. The soft verbs of lines 14, 17, 37, 39, 40, 58 and 61 are recorded in Soft Verbs: A Running Register | Network, Not Protocol as untested.

8.0 The claims on this page are open to documented challenge on the standing terms of marknichols.com, and the terms are stated here in full.

8.1 The claims on this page are open to challenge on the same terms as every claim on marknichols.com. A challenger who holds that a claim on this page is wrong, or that the Internet is something other than the publicly joinable network of networks of the registry lineage defined at The Governing Definitions and Controlling Facts of Telecommunications Internetworking, states the competing claim or definition in one sentence, names the document that carries it and the document’s date, and sends both to mark@marknichols.com. A challenge submitted with its document is answered on this page, and a competing definition submitted with its document is added to this page as an exhibit with attribution to the person who submitted it; a challenge submitted without a document is an opinion and is heard as one.

8.2 The distinction the site’s definition rests on, that protocols enable interoperability and are not the Internet, is stated in the IETF’s own words, RFC 2026 and STD 1, in the Internet-Draft draft-mnichols-protocols-not-the-internet-01, posted by Mark Nichols to the IETF Datatracker on September 25, 2026 at https://datatracker.ietf.org/doc/draft-mnichols-protocols-not-the-internet/ and stated on this site at Protocols Are Not the Internet: The IETF Internet-Draft by Mark Nichols, so a challenger may also address the definition in the venue that publishes the protocol standards themselves. Any person who holds expertise in telecommunications and a competing claim or definition is invited to bring both, in writing, with the document.

9.0 Exhibit A reproduces the A.M. Turing Award profile of Robert E. Kahn line by line, numbered in the order of the page and anchored for citation.

9.1 Exhibit A. Association for Computing Machinery, A.M. Turing Award, “Robert E Kahn - A.M. Turing Award Laureate”, biography by Janet Abbate, undated, read for this record on November 13, 2026 at https://amturing.acm.org/award_winners/kahn_4598637.cfm. Lines 1 through 10 are the lists of birth, education, experience, honors and awards, lines 11 through 14 are the heading and the award citation, and lines 15 through 66 are the biography with its section headings and the captions of its videos, in the order of the page.

1. BIRTH:

2. 23 December 1938, Brooklyn, New York.

3. EDUCATION:

4. B.E.E. (City College of New York, 1960); M.A. (Electrical Engineering, Princeton, 1962); Ph.D. (Electrical Engineering, Princeton, 1964).

5. EXPERIENCE:

6. Technical Staff, AT&T Bell labs (1964-66); Bolt, Beranek and Newman (BBN) (on leave from MIT) (1966-72); Program Manager / Director, Information Processing Techniques Office, Defense Advanced Research Projects Agency (DARPA) (1972-1985); Chairman, CEO and President of the Corporation for National Research Initiatives (CNRI) (from 1986).

7. HONORS AND AWARDS:

8. SIGCOMM Award, 1993; Marconi Award, 1994; US National Medal of Technology, 1997; IEEE Alexander Graham Bell Medal, 1997; National Academy of Engineering Charles Stark Draper Prize, 2001; ACM Turing Award, 2004; Inductee, National Inventors Hall of Fame, 2006; US Presidential Medal of Freedom, 2005; Fellow of the Computer History Museum, 2006; Japan Prize, 2008; Harold Pender Award, 2010; Queen Elizabeth Prize for Engineering, 2013; AFIPS Harry Goode Memorial Award; President's Award from ACM; ASIS Special Award; Secretary of Defense Civilian Service Award (twice).

9. Kahn has also been named a Fellow of the following organizations: National Academy of Engineering; American Academy of Arts & Sciences; New York Academy of Sciences, IEEE, ACM, AAAI, and an Honorary Fellow of the University College London.

10. He holds honorary doctorates from several institutions.

11. ROBERT (“BOB”) ELLIOT KAHN

12. United States – 2004

13. CITATION

14. With Vinton Cerf, for pioneering work on internetworking, including the design and implementation of the Internet's basic communications protocols, TCP/IP, and for inspired leadership in networking.

15. Vinton G. Cerf and Robert E. Kahn led the design and implementation of the Transmission Control Protocol and Internet Protocol (TCP/IP) that are the basis for the current internet.

16. They formulated fundamental design principles of networking, specified TCP/IP to meet these requirements, prototyped TCP/IP, and coordinated several early TCP/IP implementations.

17. Since then, they have continued to provide leadership in the networking research community and in the emerging industries of the internet and telecommunications.

18. Robert Kahn was born 23 December 1938, in Brooklyn, New York.

19. He earned his B.E.E. in electrical engineering at the City College of New York in 1960 and went on to earn his M.A. (1962) and Ph.D. (1964) in electrical engineering from Princeton.

20. He took a job at AT&T Bell Labs in 1964 and then joined the electrical engineering department at MIT as an assistant professor in 1966.

21. Wishing to do more applied research, in 1967 Kahn arranged a leave of absence from MIT in to work at the firm of Bolt, Beranek and Newman (now known as BBN), where he began developing his own ideas for computer networking.

22. ARPANET Development

23. In 1968, Lawrence Roberts of the US Department of Defense Advanced Research Projects Agency issued a request for proposals for an experimental large-scale network.

24. The ARPANET project proposed using emerging techniques such as packet switching and distributed communications, along with an unheard-of diversity of computer hardware and operating systems.

25. Kahn and Cerf discuss the original motivations for the APRANET project.

26. The ARPANET’s backbone was to consist of a set of long-distance telephone lines connected by packet switches.

27. BBN’s role was to provide the hardware and software for these switches, called Interface Message Processors or IMPs.

28. Kahn played a key role in system design for the proposal that ultimately won BBN the contract, and he subsequently joined the ARPANET development team led by Frank Heart.

29. Kahn describes his work to write the ARPANET proposal for BBN.

30. In 1972, Kahn took the lead in organizing the first public demonstration of the ARPANET at the October International Computer Communication Conference in Washington, D.C.

31. Prior to that demonstration the ARPANET had been an interesting but underused experimental system but, with Kahn’s encouragement, people at the various sites began to bring new applications online, making the network more attractive to users.

32. This effort brought the ARPANET to maturity and dramatically introduced the network to the larger computer science world.

33. Work with Cerf on Internetworking

34. Cerf and Kahn first met when Kahn came to UCLA in 1969 to help test the nascent ARPANET.

35. The two formed an effective working relationship to generate test data and predict and diagnose problems in the network.

36. In late 1972, Kahn joined the Information Processing Techniques Office (part of the US Defense Advanced Research Projects Agency – usually known as “IPTO”) as a program manager and initiated projects in network security, digital speech transmission, and packet radio.

37. In 1973, building on a previous ARPA-funded project called Alohanet, Kahn initiated a ground-based packet-radio project, called PRNET, which started experimental operation in 1975.

38. Kahn also began experimenting with using the Intelsat I satellite to link the Arpanet to sites in Britain and Norway (where ARPA conducted seismic monitoring to detect Soviet underground nuclear tests).

39. In 1975 this effort grew into the Atlantic Packet Satellite Network (SATNET), an experimental transatlantic network operated in conjunction with the British Post Office and Norwegian Telecommunications Authority.

40. Kahn tells how the network gateway concept emerged from his work on satellite ARPANET links.

41. By 1973 Kahn was already thinking about connecting ARPA’s packet radio and satellite networks to the ARPANET, but he faced formidable challenges, since the three networks were technologically incompatible.

42. ARPANET used point-to-point transmission, while the radio networks used broadcast; ARPANET tried to guarantee reliable transmission of packets, while PRNET did not; and SATNET had longer transmission delays because of the great distance the packets had to travel.

43. Successfully connecting such diverse networks would require a new approach.

44. In the spring of 1973, Kahn approached Cerf with the idea of developing a system for interconnecting networks—what would eventually be called an “internet.”

45. Kahn felt that his own knowledge of the problem of connecting dissimilar networks, combined with Cerf’s expertise in writing host software, would create a strong partnership.

46. In addition, Kahn and Cerf demonstrated farsighted leadership by inviting networking experts from around the world to weigh in on the Internet design at a seminar in June 1973.

47. This move not only led to more robust protocols, but also laid the groundwork for the global spread of the Internet.

48. Cerf and Kahn outlined the resulting Internet architecture in a seminal 1974 paper, A Protocol for Packet Network Intercommunication [2].

49. Kahn describes writing the classic 1974 paper that introduced TCP and the hierarchical numbering of network addresses.

50. There were two key elements.

51. First was a host protocol called the Transmission Control Protocol (TCP), which was intended to provide reliable, ordered, flow-controlled transmission of packets over the interlinked networks.

52. Second was a set of gateways or routers that would sit between networks, passing traffic between them and handling inter-network addressing and routing.

53. There was also a hierarchical address system, whereby packets were first sent by the gateways to a network address and then directed internally to a host address within that network.

54. The Internet architecture was designed to make minimal demands on participating networks, to provide a seamless user experience, and to scale up gracefully, key features that would facilitate the Internet’s rapid expansion in the 1990s.

55. Cerf initially worked on developing the Internet protocols as an ARPA contractor at UCLA, then moved to IPTO as program manager for networking in 1976, staying at the agency until 1982.

56. In 1978 he collaborated with Jon Postel and Danny Cohen, both at the University of Southern California Information Sciences Institute, to reformulate TCP as a set of two protocols: a host protocol (TCP) and a separate internetwork protocol (IP).

57. IP would be a stripped-down protocol for passing packets within or between networks; it would run on both hosts and gateways, while the more complex TCP would run only on hosts and provide reliable end-to-end service.

58. The new TCP/IP architecture, described in Cerf’s 1980 article “Protocols for Interconnected Packet Networks” [3], simplified the operation of internet gateways and helped increase the number and diversity of the networks connected to the Internet.

59. Cerf and Kahn oversaw the implementation of TCP and the experimental connection of ARPANET, PRNET and SATNET in 1977; this became the first incarnation of the Internet.

60. Kahn became Director of IPTO in 1979, serving until 1985.

61. He helped guide the changeover of ARPANET sites from the original NCP protocol to TCP/IP in 1983.

62. Also in 1983, Kahn initiated ARPA’s Strategic Computing Initiative, a billion-dollar research program that included chip design, parallel computer architectures, and artificial intelligence.

63. Later activities

64. In 1986 Kahn founded the Corporation for National Research Initiatives (CNRI), where he remains Chairman, CEO, and President.

65. CNRI is a not-for-profit organization that provides technical leadership and funds research and development of emerging information infrastructure components, such as digital object identifiers and “knowbots,” mobile software agents that operate across networked environments.

66. Author: Janet Abbate

10.0 The Definitions Addendum reproduces the Governing Definitions D1 through D13 of marknichols.com word for word, and every finding on this page is made under them.

10.1 Every finding on this page is made under the Governing Definitions of marknichols.com, D1 through D13, which are reproduced in this addendum word for word from The Governing Definitions and Controlling Facts of Telecommunications Internetworking. A reader of this page either accepts these definitions or disputes them. A reader who disputes a definition states the competing definition in one sentence and names the dated document that carries it before opining on any finding of this page. A reader who opines on the findings without disputing a definition has read the findings under these definitions by default.

10.2 The definitions below are copied word for word from the section “These definitions are employed throughout marknichols.com” of The Governing Definitions and Controlling Facts of Telecommunications Internetworking, as that page read on November 13, 2026, and that page controls wherever a copy differs from it.

D1. The Internet (capital I). The publicly joinable network of networks of the registry lineage: the fabric whose addresses and autonomous system numbers were issued by the InterNIC and are maintained today by ARIN. A person joins it by purchasing access from any of competing commercial providers, for any lawful purpose, and a network joins it by obtaining addresses and an autonomous system number from the numbering registry and then interconnecting by agreement with any willing network, the way Digital Island joined under autonomous system AS6553, issued August 29, 1996 by the InterNIC, with the registration maintained today in ARIN’s registry. No owner grants admission, no written policy screens members or their purposes, and no government sponsorship is required, and that single property, open admission, is what separates the Internet from every gated network that existed before it. The capital-I Internet was born in 1991, when independently operated commercial networks of this lineage, PSINet, AlterNet under UUNET, and CERFnet, interconnected by their own agreement as the Commercial Internet eXchange (CIX), settlement-free and free of any purpose-screening policy, and it was born small: the gated research world stood beside it until April 30, 1995, upon the decommission of NSFNET folded into internetMCI, per orders of Congress. Neither the ARPANET intranet, which admitted members only by agency authorization, nor the NSFNET intranet, which admitted members only under a written Acceptable Use Policy restricted to research and education, met this definition on any day of either existence, so the capital I names an Internet network that is public, or it names nothing. Paragraphs D1.1 through D1.7 state why the ARPANET and the NSFNET are not in the lineage of the Internet, each on its document.

D1.1 A network stands in the lineage of the Internet only if it carried the trait that defines the Internet, and D1 names that trait as one property, open admission; a network that never carried open admission had no such trait to pass on, and the ARPANET and the NSFNET never carried it, so neither the ARPANET nor the NSFNET is the grandfather, the ancestor, the parent, or the precursor of the Internet, and neither the ARPANET nor the NSFNET became the Internet.

D1.2 The ARPANET admitted members by its owner’s authorization from its procurement to its end: Request for Quotations No. DAHC15 69 Q 0002, issued July 29, 1968 for the Advanced Research Projects Agency of the United States Department of Defense, states the network’s purpose as “making these advanced research computer systems available to users outside their own design circle,” a purpose among the owner’s research contractors, as F37 of this page records; admission ran through agency authorization, as D4 of this page records; and the ARPANET ran from 1969 to 1990, as F38 of this page records, so the ARPANET was an intranet under D2 on every day of its existence and never carried open admission.

D1.3 The NSFNET admitted members only under a written Acceptable Use Policy restricted to research and education, as D7 of this page records, and its backbone was terminated on April 30, 1995, when its regional networks passed principally to internetMCI and SprintLink, which, in the words of Merit Network, the operator of record, absorbed the NSFNET regionals as their customers, so the NSFNET’s member networks joined the Internet as customers on terms the NSFNET never offered, and the NSFNET itself ended and did not become the Internet.

D1.4 The trait that defines the Internet has a documented origin outside the gated networks: the release of March 25, 1991 by General Atomics, Performance Systems International, Inc., and UUNET Technologies, Inc., seated at F52 of this page, states that the three networks “are not subject to government mandated “acceptable use” restrictions on their traffic,” states that the agreement can be expanded “to include any commercial service which has no restrictions on traffic use,” and states that the exchange allows firms to communicate “without traversing the government restricted backbones, such as the NSFNET (National Science Foundation Network),” so the Internet was built by agreement among commercial networks to carry traffic around the gated backbone, and the Internet did not grow out of the gated backbone.

D1.5 The ARPANET, the NSFNET, and the Internet each performed internetworking under D3, and a shared function is not a shared lineage: RFC 2026, The Internet Standards Process, Revision 3, by Scott O. Bradner of Harvard University, published October 1996, states at its section 1.1 that “There are also many isolated interconnected networks, which are not connected to the global Internet but use the Internet Standards,” so a network that uses the same protocols as the Internet is a user of the same tools and is not thereby the Internet or its ancestor. A redwood and a palm are both called trees, and a redwood did not grow from a palm, and a palm cannot become a redwood; the gated internets of the ARPANET and the NSFNET and the capital-I Internet are both called internets, and the shared word names a shared function and not a shared tree. The shared word was applied to the gated networks in error, and this record documents the error by document and date: the Stanford University bronze dedicated July 28, 2005 casts the headline “BIRTH OF THE INTERNET” above an inscription that records protocol work, as Stanford University Is Petitioned to Retract the Headline of Its BIRTH OF THE INTERNET Plaque records; RFC 1208, A Glossary of Networking Terms, by Ole J. Jacobsen and Daniel C. Lynch of Interop, Inc., published March 1991 as a document that in its own words “does not specify an Internet standard,” calls the ARPANET the “grandfather” of today’s Internet with no document for the descent it asserts; and IEEE Milestone 94 of October 29, 2009 is titled “Birthplace of the Internet, 1969,” as F46.1 of this page records.

D1.6 The registry lineage named in D1 is a continuity of numbering administration, the assignment of network addresses and autonomous system numbers by the Network Information Center at SRI, then by the InterNIC, and today by ARIN, and the registry lineage is not a lineage of networks: the Network Information Center at SRI kept the Official Host Table of the ARPANET’s era, as D4 of this page records, and a number assigned by a registry admits no one to any network, so the continuity of the numbering places no gated network in the lineage of the Internet.

D1.7 On every page of marknichols.com, the ARPANET and the NSFNET are named earlier gated networks, networks that also performed internetworking, or intranets under D2, and no page of marknichols.com calls either network the grandfather, the ancestor, the parent, the precursor, or the forerunner of the Internet, places either network in the lineage of the Internet, or states that either network became, evolved into, or grew into the Internet, under the ruling of Mark Nichols of November 7, 2026 that the ARPANET and the NSFNET belong to the history of internetworking and not to the lineage of the Internet, and that the Internet is a separate species.

D1.8 The plain statements of D1.1 through D1.7 are these. The ARPANET is not the Internet. The NSFNET is not the Internet. The ARPANET did not become the Internet. The NSFNET did not become the Internet. The ARPANET is not the grandfather, the ancestor, the parent, or the precursor of the Internet. The NSFNET is not the grandfather, the ancestor, the parent, or the precursor of the Internet. The ARPANET was an intranet, because the Advanced Research Projects Agency of the United States Department of Defense owned the ARPANET and admitted the ARPANET’s members by permission. The NSFNET was an intranet, because the NSFNET backbone admitted members only under a written Acceptable Use Policy restricted to research and education. The Internet admits anyone, and open admission is the one property that defines the Internet. Open admission came to the Internet from the commercial networks PSINet, AlterNet, and CERFnet at the Commercial Internet eXchange announced on March 25, 1991, and open admission did not come from the ARPANET or from the NSFNET. The ARPANET ended in 1990. The NSFNET backbone ended on April 30, 1995. The ARPANET, the NSFNET, and the Internet share the function of internetworking and share the word internet, and a shared function and a shared word are not a shared lineage. The Internet was born in 1991, and the Internet was not born from the ARPANET or from the NSFNET.

D2. intranet. A network, at any scale, in any geography, and under any protocol, whose members join by an owner’s permission. The word carries its own definition: intra means within, and an intranet is a network within a bounded and credentialed community, whether that community is one company’s offices or one government’s contractors spread across two continents. Scale does not convert an intranet into the Internet, geography does not, and protocol does not, because a gated network that adopts the optional protocols TCP/IP has changed its plumbing and not its admission policy; only open admission makes the Internet, and a research intranet is not the Internet. NSFNET and ARPANET are historical examples of intranets under this definition. Neither was the Internet, and neither became the Internet merely by being technically interconnected with other networks.

D3. internetworking. The technique of interconnecting distinct networks through gateways so that traffic originating on one can reach hosts on another. Internetworking among gated intranets was operating in production by 1975, when the gateway at University College London, developed and operated by Peter Kirstein’s group, of which Peter Higginson was a principal member, joined the ARPANET to the United Kingdom’s EPSS, an operation documented in the September 1975 paper of Peter L. Higginson and Andrew J. Hinchley, which recorded the working gateway while filing the Cerf and Kahn protocol as a future option rather than the operating method. Internetworking among gated intranets makes a lowercase internet, in the exact lowercase vocabulary of RFC 1983, and it never makes the capital-I Internet, because interconnecting two gated networks produces a larger gated system, not a public one. The credit for internetworking belongs to the engineers who built and operated the gateways; that credit does not extend to the birth of the Internet, which did not yet exist.

D4. ARPANET, also rendered DARPANET. The ARPA Network: one organization’s intranet, built, funded, owned, and access-controlled by the Advanced Research Projects Agency of the United States Department of Defense, later renamed DARPA, from its commissioning in 1969 until its decommissioning in 1990. Its very name is a possessive, the agency’s initials welded onto the agency’s property, and the network’s renamings followed the owner’s renamings, as only an owned network’s can. Admission was by the owner’s authorization for the owner’s purposes, the Official Host Table of the Network Information Center at SRI, the register of the era’s hosts that preceded the optional protocol DNS, listed 235 hosts in May 1982 and 562 hosts in August 1983, the two counts in RFC 1296 of January 1992 that bracket the 1983 protocol cutover, and no member of the public could join it, buy from it, or sell across it on any day of its twenty-one years. The owner stated the network’s purpose in its own procurement instrument before the network existed: Request for Quotations No. DAHC15 69 Q 0002, issued July 29, 1968 by the Defense Supply Service-Washington of the Department of the Army for the Advanced Research Projects Agency under ARPA Order No. 1260, and signed by Thomas J. Scheblik, Deputy Director for Procurement, solicited the Interface Message Processors for the ARPA computer network, and its Statement of Work, Specifications of Interface Message Processors for the ARPA Computer Network, states that the Agency was forming the network “with the cooperation of its research contractors,” that the network’s potential lay in “making these advanced research computer systems available to users outside their own design circle,” and that the network itself was “a subject of study and experimentation,” while the Statement of Work’s nineteen pages and seven appendices contain no reference to war, to survivability, to attack, to command and control, or to any military mission. The design mission of the ARPANET was therefore resource sharing among the owner’s research contractors, stated by the owner in 1968, and the later recollections agree with the instrument: Charles Herzfeld, Director of ARPA from 1965 to 1967, stated that the ARPANET was not started to create a command and control system that would survive a nuclear attack; Vint Cerf recorded on the Internet Society’s internet-history list on September 1, 2009 that Larry Roberts confirmed the purpose of the ARPANET was resource sharing and that the nuclear resilience story came from Paul Baran’s earlier work; and the Internet Society’s own history, A Brief History of the Internet, calls that story a false rumor that arose from the unrelated RAND study. The wartime mission, command traffic surviving damaged links and destroyed nodes, belonged to the owner’s later internetting project, which Vint Cerf managed at DARPA and demonstrated by putting packet radios in Strategic Air Command aircraft, and the optional protocol TCP, specified in 1974 with military computer communication requirements as the stated primary focus of RFC 793 of September 1981, was designed for that mission and installed on this intranet by the owner’s directive in 1983. The ARPANET is not the Internet, and DARPANET is not the Internet: one organization’s intranet is not the publicly joinable network of networks. The ARPANET intranet was procured under Request for Quotations No. DAHC15 69 Q 0002 of July 29, 1968, ran from 1969, and carried its traffic for fourteen years, under the Network Control Program, an optional protocol first specified in RFC 33 of February 1970, before TCP was added to it on January 1, 1983; a protocol added to a working network fourteen years after the network was procured is an add-on to that network, not its birth.

D5. Flag day, January 1, 1983. A scheduled protocol cutover, from NCP to TCP/IP, planned within the ARPANET community for years and executed on the owner’s own plant: an intranet’s internal maintenance event, touching no member of the public because no member of the public was on the network before the cutover or after it. The protocol installed that day was commissioned by the same owner to weld its own three networks together, the terrestrial ARPANET, its mobile packet radio network, and its satellite network, crossing dissimilar media under a single owner without ever crossing an owner, so that traffic could survive battlefield destruction. The Internet’s own standards registry graded TCP “Recommended” and never “Required,” in RFC 1200 of April 1991 and RFC 2200 of June 1997, grades that bind only systems electing to implement the standard suite, and a protocol cutover on a gated intranet is not the birth of anything. The network the protocol was cut over onto had been procured on July 29, 1968 and running since 1969, fourteen years before that day, so the cutover added a protocol to an existing intranet and created no network.

D6. The Internet protocols, the optional protocols TCP and IP. Protocols are utilities whose messages the networks carry; they are not the networks, and they are not the Internet. Under these Governing Definitions, TCP and IP are optional protocols, and paragraphs D6.1 through D6.13 state the documents on which that definition rests and the judgment of Mark Nichols that completes it.

D6.1 The Internet’s own standards registry, issued first by the Internet Activities Board and later by the Internet Architecture Board, under the title IAB Official Protocol Standards and from RFC 1500 of August 1993 under the title Internet Official Protocol Standards, assigned a status to each listed protocol in twenty-two editions, from RFC 1083 of December 1988 through RFC 2400 of September 1998.

D6.2 Every one of those twenty-two editions lists TCP, the Transmission Control Protocol of RFC 793, at the status “Recommended”, printed “Rec” from RFC 1280 of March 1992 onward, and lists IP, the Internet Protocol of RFC 791, at the status “Required”, printed “Req” from RFC 1280 onward, and not one of the twenty-two editions lists TCP at the status “Required” in any of its tables.

D6.3 RFC 1200 of April 1991, issued by the Internet Activities Board with Jon Postel as editor, and RFC 2200 of June 1997, issued by the Internet Architecture Board with Jon Postel as editor, each define the status “Required” at section 4.2.1 in the words “A system must implement the required protocols”, define the status “Recommended” at section 4.2.2 in the words “A system should implement the recommended protocols”, and define the status “Elective” at section 4.2.3 in the words “A system may or may not implement an elective protocol”, so that by the registry’s own definitions TCP is a protocol that a system should implement and is not a protocol that a system must implement.

D6.4 RFC 1200 of April 1991 and RFC 2200 of June 1997 each open by stating that the edition “describes the state of standardization of protocols used in the Internet” as determined by its board, and each states that “Few protocols are required to be implemented in all systems” because of the variety of possible systems, gateways, terminal servers, workstations and multi-user hosts among them.

D6.5 RFC 1122, Requirements for Internet Hosts -- Communication Layers, edited by Robert Braden for the Internet Engineering Task Force in October 1989 and listed at the status “Required” in RFC 2200 of June 1997, states at its section 1.1.3 that “To communicate using the Internet system, a host must implement the layered set of protocols comprising the Internet protocol suite” and, in the next sentence, that “A host typically must implement at least one protocol from each layer”, so RFC 1122 binds a host that has chosen to communicate using the Internet system, and RFC 1122 requires of that host at least one transport protocol, not TCP.

D6.6 RFC 1122 of October 1989 states at its section 1.1.3 that “There are two primary transport layer protocols at present”, naming TCP and UDP, and that “the set of official Internet transport protocols may be expanded in the future”, states at its section 4.2.1 that “TCP is used by those applications needing reliable, connection-oriented transport service”, and states at its section 4.1.1 that “UDP is used by applications that do not require the level of service of TCP”, so RFC 1122 itself assigns TCP by the needs of the application.

D6.7 RFC 1200 of April 1991 and RFC 2200 of June 1997 each list, at section 6.3, Network-Specific Standard Protocols, the transmission of IP over each type of physical network, ARPANET, X.25, Ethernet, IEEE 802, FDDI and serial lines among them, at the status “Elective”, and each states that “it is elective to support any particular type of physical network” on which IP is transmitted.

D6.8 RFC 2500 of June 1999 prints no status for TCP or for IP, RFC 5000 of May 2008, the last edition of the registry, prints no status for TCP or for IP, and RFC 7100 of December 2013, written by Pete Resnick of Qualcomm Technologies, Inc., obsoletes RFC 5000 and requests that RFC 5000, and therefore STD 1, be moved to Historic status, so the last status that the Internet’s own standards registry ever assigned to TCP is “Recommended”, in RFC 2400 of September 1998.

D6.9 The IP that the registry listed at the status “Required” is version 4 of the Internet Protocol, RFC 791, and the Internet Engineering Task Force standardized a second and separate Internet Protocol, version 6, in RFC 8200 of July 2017, STD 86, by S. Deering and R. Hinden. RFC 6540 of April 2012, BCP 177, titled IPv6 Support Required for All IP-Capable Nodes and written by W. George of Time Warner Cable, C. Donley of CableLabs, C. Liljenstolpe of Big Switch Networks and L. Howard of Time Warner Cable, advises that “IPv6 support is no longer considered optional”, cautions that the term “IP” has become “a generic that can mean IPv4 + IPv6, IPv6-only, or IPv4-only, depending on context and application”, and states that new and updated IP networking implementations “must not require IPv4 for proper and complete function”, so the Internet Engineering Task Force itself used the word optional for an Internet Protocol until April 2012, and the IP version that the registry listed at the status “Required” is, under the Best Current Practice of April 2012, a version that no new or updated implementation may require.

D6.10 The suite’s own members prove reliability is a per-application choice, because the optional protocols UDP of RFC 768, RTP of RFC 1889 of January 1996, which RFC 3550 of July 2003 obsoletes, and QUIC of RFC 9000 all decline TCP’s services while each remains a protocol of the Internet standards track.

D6.11 TCP is an evolutionary option, not a permanent fixture: it replaced NCP on the owner’s intranet in the 1983 cutover, UDP stood beside it from 1980 for applications that declined its services, RTP went around it in 1996 for media that could not wait for retransmission, and QUIC, published in May 2021, is displacing it now by moving reliability into a new protocol carried inside UDP datagrams; the protocols rotate while the Internet persists, and a layer whose occupants rotate is by definition not the thing itself.

D6.12 It is the stated judgment of Mark Nichols that both are optional utilities: TCP optional on the registry’s own grade, and IP optional as a specific protocol, because the registry’s “Required” grade is conditional conformance language that binds only systems electing to implement the standard suite, the election being made before the grade applies, as the words “To communicate using the Internet system” of RFC 1122 and the word optional that RFC 6540 applies to IPv6 both record, and because what internetworking requires is the addressing function, the label that says where a packet should go, while IP is one implementation of that function and not the function itself.

D6.13 Hence the rebrand coinages stated at marknichols.com/internet-protocols/: TCP is better named ESFRP, the Endpoint Segment Failure Retry Protocol, and IP is better named ALP, the Address Label Protocol. The postmen are not the post office, and the protocols are not the Internet.

D7. NSFNET. The National Science Foundation’s backbone, 1986 to 1995: a federation of research intranets joined into a lowercase internet under a written Acceptable Use Policy that restricted carriage to research and education and barred commercial traffic. The dismantling is dated by the operator of record, Merit Network: the replacement architecture was awarded early in 1994, the very high speed Backbone Network Service to MCI and the Network Access Points to Sprint, MFS Datanet, and Bellcore representing Ameritech and PacBell; member networks began moving off in November 1994; the backbone was terminated on April 30, 1995; and the regional networks passed principally to the commercial carriers internetMCI and SprintLink, which, in Merit’s own words, absorbed the NSFNET regionals as their customers. The NSFNET is not the Internet: a backbone admission-screened under a written Acceptable Use Policy restricted to research and education is a gated network, and a gated network is not the publicly joinable network of networks.

D8. The World Wide Web. An application design made by many persons inside and outside CERN, announced publicly on August 6, 1991, three programs of CERN's World Wide Web software, the line-mode client, the basic server and the library of common code, released into the public domain by CERN on April 30, 1993, with NCSA Mosaic released in 1993 putting a graphical browser in front of it. A free application is not an open network: until April 30, 1995, the Web’s principal carriage was the gated research intranets beneath it, research-only carriage under the written policy, and the calendar states the dependency exactly, because CERN's three programs of Web software went public on April 30, 1993, and the gated research fabric beneath most of its hosts was absorbed into the public Internet two years later to the day, on April 30, 1995. The name World Wide Web is a label for a large body of technology in the public domain, made by many persons and bodies inside and outside CERN, as F32.4 of this page states. The World Wide Web is not the Internet: the Web is an application using the Internet platform, and the application is not the platform.

D9. The birth of the Internet, and the absorption. The capital-I Internet was born in 1991, when PSINet, AlterNet under UUNET, and CERFnet, independently operated commercial networks of the registry lineage, established the Commercial Internet eXchange, a settlement-free router interconnection with open admission and no purpose-screening policy, as recorded in the Federal Communications Commission working paper The Digital Handshake by Michael Kende and as announced by the three networks’ operators themselves, General Atomics, Performance Systems International, Inc., and UUNET Technologies, Inc., in their release of March 25, 1991, which states that “The CIX agreement provides for all customers of AlterNet, CERFnet and PSINet to exchange Internet traffic directly, regardless of which network the customer obtains service from, and at no additional cost” and that the three “are not subject to government mandated “acceptable use” restrictions on their traffic,” the release being preserved as message 441 of the com-priv archive at the Massachusetts Institute of Technology and seated at F52 of this page; the agreement’s own text and its execution date are still sought, and the ruling stands on the dated announcement, the year, the parties, and the terms until a dated earlier instrument of the same lineage is produced. April 30, 1995 is not the Internet’s birthday; it is the absorption: the day the last written admission policy over the general-purpose research backbone died with the NSFNET, the regional networks passed principally to internetMCI and SprintLink, and the populations that had lived behind the gate joined the Internet that had existed without them since 1991. Being born is not the same as being built, and the Modern Internet, publicly accessible, eCommerce native, media streaming native, and QoS native, was built from 1996 to 1997 on executed documents: the Telecommunications Act signed February 8, 1996, autonomous system AS6553 issued August 29, 1996 by the InterNIC, the $300,000 Cisco Systems agreement of November 1996 to host cisco.com on Digital Island’s Tier-0 network, and production service in the first quarter of 1997, with Cisco Systems, Stanford University, and Visa International as the first customers in sequence.

D10. The Modern Internet. The Internet changed from the legacy Internet to the Modern Internet on the day its internetworking changed from best effort to deterministic, and that day is November 1, 1996, the Effective Date of the Cisco Systems Remote Data Services Agreement, signed for Digital Island, Inc. by Mark Nichols, Director, Global Networks, on November 7, 1996 and for Cisco Systems, Inc. by Hervé Goguely, Director, Global Service Management, on November 8, 1996, under which Cisco Systems became the first customer to buy a contractually guaranteed global service, a network segment exclusively its own with secure transaction services and sub-300 milliseconds round trip, on the architecture Mark Nichols hand-drew in June 1996, redrew as DIGITAL ISLAND DRAFT.1 in July 1996 and DRAFT.2 in October 1996, and registered as AS6553, issued to Digital Island, Inc. on August 29, 1996. An evolution, not a synonym. The capital-I Internet born in 1991 and made general-purpose by the absorption of April 30, 1995 was public but bare: a network anyone could join, and nothing commerce-grade could yet depend on, because open admission supplies members and does not supply performance. The Modern Internet is what that public network evolved into when global commerce was engineered onto it: the enabling of the globalization of eCommerce, of streaming media, and of Quality of Service under signed and enforceable terms, built on Digital Island’s Tier-0 network under autonomous system AS6553 with contractually enforced sub-300-millisecond round-trip performance across major markets, carrying the Merchant Transport product category coined in September 1996, on the architecture designed by Mark Nichols as co-founder and chief architect, the record standing at marknichols.com/architect-of-the-modern-internet/, marknichols.com/merchant-transport/, and marknichols.com/tier-0/. The evolution is dated by the executed record and by the customers who ran on AS6553 in sequence: Cisco Systems in November 1996, Stanford University in 1997, Visa International in the second quarter of 1997, E*TRADE under its global data distribution agreement with Digital Island dated August 1, 1997, as Digital Island’s S-1 records it, Charles Schwab in 1998, and MasterCard in March 1999; Telefónica Data formed a global IP alliance with Digital Island on April 26, 1999, Sun Microsystems and Inktomi invested in Digital Island in December 1999, Microsoft, Intel, and Compaq invested in Digital Island in June 2000, and CERNET, the China Education and Research Network, peered with Digital Island under the contract signed in Beijing on February 25, 1998 and was never a customer. The Modern Internet is therefore dated 1996 to 1997 in executed documents, and the word modern means publicly accessible, commerce-grade, streaming-capable, and QoS-governed, none of which the newborn network possessed.

D11. Usage. On every page of this site, Internet with a capital I means the publicly joinable network of the registry lineage born in 1991 and nothing else; internet in lowercase means any interconnection of networks, including gated ones; gated systems are named what they were, research intranets, whatever their date; and any page, headline, plaque, or biography that assigns the birth of the Internet to 1969, 1974, or 1983 is measured against these definitions and fails, because on each of those dates every network in the claim admitted its members by permission, and any account that assigns the birth to April 30, 1995 is measured against these definitions and fails as well, because on that date the Internet already existed and what died was the gate beside it. And on every page of this site, “Required” as a registry grade appears only in quotation marks with its condition stated in the same sentence, that it binds only systems electing to implement the standard suite, except within D6 of this page, where D6.12 states that condition once for every quotation of the registry in D6.1 through D6.11; this site’s own prose never calls any Internet protocol required, because at the level of Internet membership there are no required protocols, only elected ones, and an unconditional “required” applied to an Internet protocol is the registry’s conditional conformance label promoted into a membership law that no document states.

D12. Contemporary primary-source documents control over retrospective accounts, institutional narratives, biographies, media summaries, machine-generated responses, and personal recollections.

D13. Any finding in this record may be amended upon production of contemporaneous documentary evidence demonstrating a materially earlier, later, or contrary fact.