EBSCO Robert Kahn Research Starter: Disagreements | Network, Not Protocol

The EBSCO Research Starter Robert Kahn by Robert N. Stacy credits Robert Kahn and Vinton Cerf with developing TCP/IP “in the early 1970s,” calls the ARPANET “the precursor to the Internet,” and credits their protocols with making it possible for networks to connect, while Jon Postel proposed the separate IP in 1977, under D1 the ARPANET never met the definition of the Internet, and under D6 the networks carry the messages of the protocols.

Preamble: I examine the EBSCO Research Starter Robert Kahn, sentence by sentence, against the paper of Vinton G. Cerf and Robert E. Kahn of May 1974, RFC 675 of December 1974, IEN 2 of August 15, 1977, RFC 760 of January 1980, RFC 791 and RFC 793 of September 1981, the “Innovation Timeline” of the Defense Advanced Research Projects Agency, the Official Biography: Robert Kahn of the Internet Hall of Fame, and the Governing Definitions of marknichols.com. Exhibit A at section 9.0 reproduces the eighty-one sentences of the article, numbered and anchored, and every finding on this page cites those numbers. This page is Disagreement 89 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 89, 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 article this page examines, the way its sentences are numbered, and the definitions on which the findings depend.

0.1 The source examined on this page is the EBSCO Research Starter Robert Kahn at https://www.ebsco.com/research-starters/biography/robert-kahn/, which states “Authored by: Stacy, Robert N.” and “Published in: 2013.” Mark Nichols supplied the text of the article to this record on November 13, 2026, as copied from the page. The article reports events of 2024, 2025 and 2026, and its bibliography gives the access date “25 Sept. 2026” for its sources.

0.2 Exhibit A at section 9.0 reproduces the eighty-one sentences of the article in the order of the page: sentences 1 through 9 are the Overview, and sentences 10 through 81 are the Full article. The bibliography, the menus and the list of related topics are not reproduced.

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.

1.0 Sentence 12 states that Robert Kahn and Vinton Cerf developed TCP/IP “in the early 1970s,” which is false as written under F56, because the separate internetwork protocol was first proposed by Jon Postel in IEN 2 of August 15, 1977 and the DoD Standard Internet Protocol was first published in RFC 760 of January 1980, and sentence 57 credits the IP layer to Vinton Cerf and Robert Kahn while the documents give its separation and specification to Jon Postel.

1.1 Sentence 12 of the article states: “Along with Vinton Cerf, Kahn developed the transmission-control protocol/Internet protocol (TCP/IP) in the early 1970s, establishing a means whereby computers on a network (such as ARPANET or the Internet) could communicate with computers on different networks.” Sentence 57 states: “The next is the Internet protocol (IP) layer, developed by Cerf and Kahn, which makes it possible for different local networks to connect and communicate.”

1.2 IEN 2, “Comments on Internet Protocol and TCP,” written by Jon Postel of the Information Sciences Institute and dated 15 August 1977, proposes “that a new distinct internetwork protocol is needed, and that TCP be used strictly as a host level end to end protocol,” and RFC 760 of January 1980, “DOD STANDARD INTERNET PROTOCOL,” is signed by Jon Postel as editor, as 4.4 and 4.5 of Wikipedia Describes Vint Cerf: Disagreements | Network, Not Protocol, Disagreement 11, record.

1.3 The documents date four stages of the protocols: Vinton G. Cerf and Robert E. Kahn published the protocol proposal in May 1974; Vinton G. Cerf, Yogen Dalal and Carl Sunshine wrote RFC 675, the specification of the combined Internet Transmission Control Program, in December 1974; Jon Postel proposed the separation of the relaying of packets from the end-to-end control of the conversation in Internet Experiment Note 2 (IEN 2) on August 15, 1977; and RFC 791 and RFC 793, both of September 1981 and edited by Jon Postel, specified IP and TCP as separate protocols, as 3.2 of Internet Hall of Fame Robert Kahn: Disagreements | Network, Not Protocol, Disagreement 78, records.

1.4 The kind is false as written under F56 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking, which states that “a sentence whose predicate is false as written is false, whether the falsity arose from compression, from shorthand, or from intent”: the suite of two separate protocols that sentence 12 names did not exist in the early 1970s, because the separate internetwork protocol was first proposed on August 15, 1977 and first specified in January 1980. The words “developed by Cerf and Kahn” of sentence 57 are a documentary finding, because the documents give the proposal and the specification of the separate IP to Jon Postel.

1.5 The consequence for the historical record is that the design of May 1974 is credited to Vinton G. Cerf and Robert E. Kahn, the combined specification of December 1974 to Vinton G. Cerf, Yogen Dalal and Carl Sunshine, and the separation of IP from TCP and its first specification to Jon Postel of the Information Sciences Institute.

2.0 Sentences 4, 64, 65 and 66 call the ARPANET “the precursor to the Internet,” place the Internet after the ARPANET in one line of descent, and say the Internet began to evolve in the 1960s and 1970s, while under D1 the ARPANET never met the definition of the Internet and the Internet was born in 1991.

2.1 Sentence 4 of the article states: “In 1968, he joined Bolt, Beranek, and Newman (BBN), where he played a vital role in the early ARPANET project, the precursor to the Internet.” Sentence 64 states: “Kahn and Cerf’s solution ensured that similar problems would not exist within ARPANET and subsequently the Internet.” Sentence 65 states: “In January 1983, ARPANET switched to TCP/IP, a key step in the development of the Internet.” Sentence 66 states: “IP networking represents a synthesis of several developments that began to evolve in the 1960s and 1970s, namely the Internet and local area networks, or LANs (which emerged in the mid- to late-1970s), together with the advent of the World Wide Web in the early 1990s.”

2.2 D1 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking states: “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”. D1 also states that the 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)”.

2.3 The kind is a definitional finding: the words “the precursor to the Internet,” “ARPANET and subsequently the Internet” and “a key step in the development of the Internet” set the ARPANET in the lineage of the Internet, and the words “developments that began to evolve in the 1960s and 1970s, namely the Internet” date the Internet to those decades, while under D1 the ARPANET admitted members only by agency authorization and never met the definition of the Internet, and the Internet was born in 1991. The soft words “played a vital role in,” “ensured that,” “a key step in” and “began to evolve” of the four sentences are recorded in Soft Verbs: A Running Register | Network, Not Protocol.

2.4 The consequence for the historical record is that the ARPANET is recorded as an intranet that admitted members only by agency authorization, and the birth of the Internet in 1991 is credited to the interconnection of PSINet, AlterNet under UUNET, and CERFnet as the Commercial Internet eXchange.

3.0 Sentences 1 and 14 say that Robert Kahn is “recognized as one of its fathers” and that his contributions “have been recognized as among the most important to the creation of the Internet,” while the passive words name no one who gives the recognition, and under D1 the Internet was born in 1991 on the interconnection of three commercial networks.

3.1 Sentence 1 of the article states: “Robert Kahn is a prominent figure in the development of the Internet, recognized as one of its fathers alongside Vinton Cerf.” Sentence 14 states: “Kahn’s contributions have been recognized as among the most important to the creation of the Internet, earning him credit, along with Cerf, as one of the fathers of the Internet.”

3.2 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 D1 states that the 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)”.

3.3 The kind is a definitional finding: the passive words “recognized as” and “have been recognized as” name no person, no body and no document that gives the recognition, and the nouns “fathers” and “the creation of the Internet” credit Robert E. Kahn with the making of an Internet that under D1 was born in 1991 on the interconnection of PSINet, AlterNet under UUNET, and CERFnet, none of which the article names. Sentences 1 and 14 are recorded in Soft Verbs: A Running Register | Network, Not Protocol.

3.4 The consequence for the historical record is that the title of father of the Internet is recorded as an honorific given by unnamed persons, and the birth of the Internet in 1991 is credited to the networks of the Commercial Internet eXchange.

4.0 Sentences 6, 55, 57, 58 and 60 credit TCP/IP, its layers and the work of Robert Kahn and Vinton Cerf with enabling communication between networks and making it possible for networks and individuals to connect and communicate, while under D6 protocols are utilities whose messages the networks carry, under RFC 793 the datagram is embedded in a local network packet, and under D3 the credit for internetworking belongs to the engineers who built and operated the gateways.

4.1 Sentence 6 of the article states: “Together with Cerf, he developed the Transmission Control Protocol/Internet Protocol (TCP/IP), a foundational technology that enables communication between different networks.” Sentence 55 states: “These two layers form the middle of a four-layer structure that makes communication on the Internet possible.” sentence 57 states: “The next is the Internet protocol (IP) layer, developed by Cerf and Kahn, which makes it possible for different local networks to connect and communicate.” Sentence 58 states: “Once a connection is established, the transport layer (Kahn and Cerf’s TCP) allows the host in each network to connect and communicate with the host in another network.” Sentence 60 states: “Kahn and Cerf made it possible for individuals on different networks to communicate with one another.”

4.2 D6 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking states: “Protocols are utilities whose messages the networks carry; they are not the networks, and they are not the Internet.” RFC 793 of September 1981, Section 2.2, states that “This internet module packages TCP segments inside internet datagrams and routes these datagrams to a destination internet module or intermediate gateway. To transmit the datagram through the local network, it is embedded in a local network packet,” as F50.9 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking quotes it.

4.3 D3 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking states: “The credit for internetworking belongs to the engineers who built and operated the gateways”.

4.4 The kind is a definitional finding: the soft words “a foundational technology that enables communication between different networks,” “makes communication on the Internet possible,” “makes it possible for different local networks to connect and communicate,” “allows the host in each network to connect and communicate” and “made it possible for individuals on different networks to communicate” credit protocols, and the two persons who designed them, with the connection of networks, while under D6 the networks carry the messages of the protocols, under RFC 793 the datagram travels embedded in the packet of the network, and under D3 the joining of networks is credited to the engineers who built and operated the gateways. The five sentences are recorded in Soft Verbs: A Running Register | Network, Not Protocol.

4.5 The consequence for the historical record is that the connection of networks is credited to the networks and to the engineers who built and operated the gateways between them, and TCP and IP are recorded as utilities whose messages the networks carry.

5.0 Sentence 11 dates the arrival of Robert Kahn at DARPA to 1973 and sentence 31 says he was offered the head of the Information Processing Techniques Office in 1972, while the article contradicts itself on the year, the agency’s own timeline says he joined that office “as a program manager in 1972,” and the Internet Hall of Fame says he moved to DARPA in 1972 and “subsequently” became its director.

5.1 Sentence 11 of the article states: “Eventually joining the Defense Advanced Research Projects Agency (DARPA) in 1973, Kahn headed what was the largest government computer research and development program at that time.” Sentence 31 states: “In 1972, Kahn was offered a position as head of ARPA’s Information Processing Techniques Office (IPTO).”

5.2 Line 358 of the “Innovation Timeline” of the Defense Advanced Research Projects Agency says that Robert Kahn “joined the Information Processing Techniques Office as a program manager in 1972,” as 2.1 of DARPA's Innovation Timeline: Disagreements | Network, Not Protocol, Disagreement 73, records, and sentence 6 of the Official Biography: Robert Kahn of the Internet Hall of Fame states: “In 1972 he moved to DARPA and subsequently became Director of DARPA’s Information Processing Techniques Office (IPTO),” as Exhibit A of Internet Hall of Fame Robert Kahn: Disagreements | Network, Not Protocol, Disagreement 78, reproduces it.

5.3 The kind is a documentary finding: sentence 11 gives the year 1973 that sentence 31 of the same article, the agency's own timeline and the Internet Hall of Fame give as 1972, and sentence 31 places Robert E. Kahn at the head of the office in 1972, while the agency's own timeline says he joined it as a program manager in that year and the Internet Hall of Fame says he became its director afterward.

5.4 The consequence for the historical record is that Robert E. Kahn joined the Information Processing Techniques Office of the agency in 1972 as a program manager, as the agency's own timeline records, and became its director afterward.

6.0 Sentence 48 calls TCP “the standard protocol used on the Internet,” and sentence 51 says the first version of TCP was “formally documented in RFC 675” without naming its authors, while under D6 TCP is an optional protocol and RFC 675 of December 1974 names Vinton G. Cerf, Yogen Dalal and Carl Sunshine as its authors.

6.1 Sentence 48 of the article states: “They started by conducting research on reliable data communications across packet radio networks, factored in lessons learned from the networking control protocol, and then created the next-generation transmission-control protocol (TCP), the standard protocol used on the Internet.” Sentence 51 states: “The first version of this predecessor of TCP was written in 1973, then revised and formally documented in RFC 675, “Specification of Internet Transmission Control Program” (December 1974; RFC is a standard designation in computer and Internet engineering meaning “request for comments”).”

6.2 D6 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking states that “Under these Governing Definitions, TCP and IP are optional protocols,” and RFC 675 of December 1974, the specification of the combined Internet Transmission Control Program, names Vinton G. Cerf, Yogen Dalal and Carl Sunshine as its authors, as 3.2 of Internet Hall of Fame Robert Kahn: Disagreements | Network, Not Protocol, Disagreement 78, records.

6.3 The kind is a definitional finding for sentence 48, whose words “the standard protocol used on the Internet” give an optional protocol the place of the one standard of the Internet, and a documentary finding for sentence 51, whose words “formally documented in RFC 675” leave unnamed the three authors of that specification. The consequence for the historical record is that TCP is recorded as an optional protocol, and the specification of December 1974 is credited to Vinton G. Cerf, Yogen Dalal and Carl Sunshine.

7.0 Sixty-five sentences of the article were examined and are not disputed on this page, and this section records which sentences and why.

7.1 Sentences 2, 3, 5, 7, 8, 9, 10, 13, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 49, 50, 52, 53, 54, 56, 59, 61, 62, 63, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80 and 81 state a birth, schooling, employment, programs, demonstrations, awards, a relative and the work of the Corporation for National Research Initiatives that no dated document on this page contradicts, and a disagreement without a document has no place on this page.

7.2 The soft words of sentences 7, 8, 9, 13, 27, 33 and 62, which are “allowing for,” “helped shape,” “continues to influence,” “was instrumental in creating,” “contribute to the development,” “important in defining and developing networks” and “ensured that these protocols could be made to work anywhere,” credit Robert E. Kahn, and with him Vinton G. Cerf, with networks and protocols without naming an act or a document, and the seven sentences are recorded in Soft Verbs: A Running Register | Network, Not Protocol as untested.

7.3 Sentence 69 credits Robert E. Kahn and Vinton G. Cerf, by the words “helped form,” with the forming of the Internet Society in 1992, an organization and not a network, an internet or a protocol, so the sentence is outside Soft Verbs: A Running Register | Network, Not Protocol under its unit 0.4.

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 eighty-one sentences of the EBSCO Research Starter Robert Kahn by Robert N. Stacy, numbered in the order of the page and anchored for citation.

9.1 Exhibit A. EBSCO Research Starter, Robert Kahn, authored by Robert N. Stacy, published in 2013, as supplied by Mark Nichols on November 13, 2026 from https://www.ebsco.com/research-starters/biography/robert-kahn/. Sentences 1 through 9 are the Overview and sentences 10 through 81 are the Full article.

1. Robert Kahn is a prominent figure in the development of the Internet, recognized as one of its fathers alongside Vinton Cerf.

2. Born on December 23, 1938, in New York City, Kahn earned degrees in electrical engineering from the City College of New York and Princeton University.

3. His career began at Bell Laboratories and later included a position as an assistant professor at MIT.

4. In 1968, he joined Bolt, Beranek, and Newman (BBN), where he played a vital role in the early ARPANET project, the precursor to the Internet.

5. Kahn's most significant contributions emerged during his tenure at the Advanced Research Projects Agency (ARPA), where he directed the Information Processing Techniques Office.

6. Together with Cerf, he developed the Transmission Control Protocol/Internet Protocol (TCP/IP), a foundational technology that enables communication between different networks.

7. Their work emphasized an open architecture, allowing for widespread accessibility and preventing the proprietary restrictions that could limit network functionality.

8. Kahn's innovations helped shape modern networking and have earned him numerous accolades, including the National Medal of Technology and the Presidential Medal of Freedom.

9. His legacy in fostering open communication systems continues to influence the Internet today.

10. Robert Kahn’s involvement with ARPANET and eventually the Internet began at the very start of the ARPANET program in 1968, when he was part of the team at Bolt, Beranek, and Newman that developed the network for the Department of Defense.

11. Eventually joining the Defense Advanced Research Projects Agency (DARPA) in 1973, Kahn headed what was the largest government computer research and development program at that time.

12. Along with Vinton Cerf, Kahn developed the transmission-control protocol/Internet protocol (TCP/IP) in the early 1970s, establishing a means whereby computers on a network (such as ARPANET or the Internet) could communicate with computers on different networks.

13. In addition, he was instrumental in creating open architecture, meaning that dissimilar computer networks could interconnect and communicate openly rather than through programs that were protected as proprietary intellectual property.

14. Kahn’s contributions have been recognized as among the most important to the creation of the Internet, earning him credit, along with Cerf, as one of the fathers of the Internet.

15. Robert Elliot Kahn was born in New York City on December 23, 1938.

16. He attended the City College of New York, where he earned a bachelor’s degree in electrical engineering.

17. Two years later, he received a master’s degree from Princeton University, and two years after that, he earned his doctorate from the same institution.

18. Kahn’s first job upon completing his education was at Bell Laboratories.

19. He then became an assistant professor of electrical engineering at the Massachusetts Institute of Technology (MIT).

20. In the late 1960s, he joined the staff at Bolt, Beranek, and Newman (BBN) in Cambridge, Massachusetts.

21. In late 1968, Larry Roberts, chief scientist and newly selected program manager at ARPA, released a request for proposal (RFP) in search of contractors to build a computer network for the agency, eventually to be known as ARPANET.

22. BBN received the RFP and began to prepare a response in the form of a technical proposal.

23. Kahn was assigned to the team that prepared this response.

24. In early 1969, BBN was announced as the winner and thus began to develop the network that would eventually result in computers (referred to as interface message processors, or IMPs) at four different sites: the University of California at Los Angeles, the University of California at Santa Barbara, Stanford University, and the University of Utah.

25. In 1970, Kahn coauthored The Interface Message Processor for the ARPA Computer Network with four other BBN engineers.

26. Kahn’s involvement, which began with developing the proposal, would continue into 1971.

27. He would not only contribute to the development but also influence the approach that would be taken to design the network’s architecture.

28. His view, which would be incorporated into the overall development, was that, however the network was to be configured, it ought to be planned in such a way that its basic organization would remain the same even as the network expanded.

29. In that way, costly changes in the future could be avoided.

30. As time went on, Kahn’s involvement in the project was accompanied by a growing conviction that the network was increasingly important, a feeling that he did not believe was being shared by BBN, which tended to develop solutions and then move on to the next problem.

31. In 1972, Kahn was offered a position as head of ARPA’s Information Processing Techniques Office (IPTO).

32. Later that year, Kahn gave a demonstration at an international computing conference of ARPANET’s capabilities, linking forty computers simultaneously.

33. While Kahn’s work up to 1972 was important in defining and developing networks, his major contributions would be made in the later 1970s.

34. First, as IPTO director, he started and managed the largest computer development program to that time, the Strategic Computing Program.

35. Second, he and Vinton Cerf developed a solution to the problem of how networks might communicate with one another despite differences in equipment and architecture.

36. The computers connected to ARPANET had all been brought in as integral parts of the DARPA network.

37. There was no problem with their ability to communicate among themselves.

38. What would happen, however, if there was a need (and there certainly would be at some point) for ARPANET to communicate with computers on other networks?

39. For the time being, there was no commonality in hardware or software, and consequently, none in the ability of networks to contact and understand one another.

40. That was the problem that Kahn and Cerf would solve.

41. Their eventual solution was to develop network protocols.

42. A protocol is software or hardware that defines how communications are conducted so that dissimilar networks can communicate with each other.

43. Protocols handle communications and the rules at different levels.

44. One protocol will handle how different hardware items will interact.

45. Another will establish how messages will be passed back and forth (the packet-switching method that was analyzed by Leonard Kleinrock was the means of conveying messages on ARPANET and later the Internet).

46. Another may govern how browsers will receive messages, while yet another may resolve lost packet issues or authentication.

47. In the spring of 1973, Cerf joined Kahn on the project.

48. They started by conducting research on reliable data communications across packet radio networks, factored in lessons learned from the networking control protocol, and then created the next-generation transmission-control protocol (TCP), the standard protocol used on the Internet.

49. In the early versions of this technology, there was only one core protocol, which was named TCP.

50. At the time, these letters did not stand for transmission-control protocol, but instead stood for the transmission-control program.

51. The first version of this predecessor of TCP was written in 1973, then revised and formally documented in RFC 675, “Specification of Internet Transmission Control Program” (December 1974; RFC is a standard designation in computer and Internet engineering meaning “request for comments”).

52. In 1974, Kahn and Vinton Cerf coauthored A Protocol for Packet Network Intercommunication, a foundational paper on internetwork communication.

53. In 1977, Kahn and Cerf demonstrated internetworking by transmitting data among ARPANET, a packet-radio network, and a satellite network.

54. What Kahn and Cerf developed, then, was to be known as the transmission-control protocol/Internet protocol (TCP/IP).

55. These two layers form the middle of a four-layer structure that makes communication on the Internet possible.

56. The first is known as the link layer and provides the means and the rules for communications within a specific network.

57. The next is the Internet protocol (IP) layer, developed by Cerf and Kahn, which makes it possible for different local networks to connect and communicate.

58. Once a connection is established, the transport layer (Kahn and Cerf’s TCP) allows the host in each network to connect and communicate with the host in another network.

59. Finally, there is an application layer, which governs how data service processes are run (for example, a web browser interacting with a machine with a web server located elsewhere).

60. Kahn and Cerf made it possible for individuals on different networks to communicate with one another.

61. While this was extremely important in resolving an immediate need, its importance went beyond a technical solution.

62. By insisting that the architecture and the protocols be open to everyone, they ensured that these protocols could be made to work anywhere by anyone and not be subjected to the restrictions that would occur when using proprietary systems.

63. The Department of Defense, even at this early stage, was making decisions regarding programs such as the Worldwide Military Command and Control System (in which proprietary solutions would hinder open communications).

64. Kahn and Cerf’s solution ensured that similar problems would not exist within ARPANET and subsequently the Internet.

65. In January 1983, ARPANET switched to TCP/IP, a key step in the development of the Internet.

66. IP networking represents a synthesis of several developments that began to evolve in the 1960s and 1970s, namely the Internet and local area networks, or LANs (which emerged in the mid- to late-1970s), together with the advent of the World Wide Web in the early 1990s.

67. Kahn left DARPA in 1985, and in 1986 founded and served as chief executive officer (CEO) and president of the Corporation for National Research Initiatives (CNRI), a nonprofit organization that seeks to find solutions to developing a national Information infrastructure.

68. At CNRI, Kahn also developed the Digital Object Architecture, a framework for identifying, managing, and locating digital information in networked environments.

69. Kahn and Vinton Cerf were among the Internet pioneers who helped form the Internet Society in 1992.

70. Kahn has received many awards, including the Association for Computing Machinery‘s Alan M. Turing Award and its President’s Award.

71. In conjunction with his collaborator, Cerf, Kahn received the US National Medal of Technology, the Marconi Award, and the Presidential Medal of Freedom.

72. He shared the Charles Stark Draper Prize for 2001 with Cerf, Leonard Kleinrock, and Larry Roberts for their work on the ARPANET and Internet.

73. Kahn and Cerf shared the 2008 Japan Prize in the specific category of “Information Communication Theory and Technology.”

74. In 2012, he became one of the first people to be inducted into the Internet Hall of Fame.

75. In 2013, Kahn shared the inaugural Queen Elizabeth Prize for Engineering with four others.

76. In 2024, he received the Institute of Electrical and Electronics Engineers (IEEE) Medal of Honor.

77. In addition, Kahn received many honorary degrees.

78. In 2025, Kahn received the World Internet Conference Distinguished Contribution Award and became chair emeritus of the DONA Foundation.

79. In 2026, CNRI released the open-source DOIP–MCP Connector, which connects digital objects with artificial intelligence systems.

80. Kahn’s relative, Herman Kahn (1922–83), was a military analyst and theorist who made a specialty of studying the possibilities of atomic warfare and its results, publishing two books on the subject, On Thermonuclear War (1960) and On Escalation (1965).

81. Herman Kahn is said by some to have been one of the models for the titular character in the film Dr. Strangelove.

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.