Wikipedia Timeline of the History of the Internet: Reference Audit | Network, Not Protocol

Of the 26 citations in the Wikipedia article “Timeline of the history of the internet”, 2 carry the sentence that cites them, 18 carry it in part, 1 does not carry it and 5 cannot be checked, and the sources of the timeline’s own early entries contradict three of them: Paul Baran’s first proposal of 1960 was for a teletypewriter network and not for digital voice, the source cited for Tymnet titles it a multiplexed packet network and not a switched-circuit network, and the sources disagree on whether the NPL network carried packets in 1969 or became operational in June 1973.

Preamble: I audit the Wikipedia article “Timeline of the history of the internet” footnote by footnote, opening the source that each footnote cites and reading it against the sentence that cites it. This page is the companion of Disagreement 96 in the standing index of the series, Disagreements of Published Claims | Network, Not Protocol, and the article lines cited on this page are the numbered lines of Exhibit A of Wikipedia Timeline of the History of the Internet: Disagreements | Network, Not Protocol. The method and the five grades are the same as on Wikipedia Robert Cailliau: Reference Audit | Network, Not Protocol.

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 audits, the method of the audit, and the grades it assigns.

0.1 The article audited on this page is “Timeline of the history of the internet” of the English Wikipedia at https://en.wikipedia.org/wiki/Timeline_of_the_history_of_the_internet. Wikipedia’s revision history records revision 1384989135 of November 10, 2026 as the latest revision of the article on November 14, 2026, the day on which Disagreement 96 read the text that Mark Nichols supplied. The article carries 26 numbered footnotes, which it cites 26 times, all at lines 5 through 19 and line 36. This page read the list of footnotes, the links of each footnote and the sentences that cite each footnote in revision 1384989135 through Wikipedia’s own public interface on November 14, 2026.

0.2 This page audited each footnote on November 14, 2026, by opening the source at the link the footnote gives, at the archived copy that the footnote names where the original is gone, and, where the footnote names no copy and the link no longer reaches the source, at an archived copy that this page identifies in the unit that grades it. Six of the sources were read in full. Fifteen were retrieved in full and read at the passages that bear on the sentence they support, after a search of the whole text, and the unit that grades each of them states which part was read. Five could not be read, and the unit that grades each of them states why.

0.3 Each citation receives one of five grades. Supported means that the source carries the sentence in its own words. Partial means that the source carries part of the sentence and not the rest. Not supported means that the source was read and does not carry the sentence. Uncheckable means that the citation cannot be followed to a readable source. Unread means that the source was not read for this page.

0.4 The sources are quoted on this page in short fragments, and the rest of what each source says is stated in the words of this page. The sentences of the article are quoted from Exhibit A of Disagreement 96, where the footnotes stand as lines 147 through 172.

1.0 Each of the 26 footnotes of the article is graded at the sentence that cites it.

1.1 At line 5, the article says that a timeline of the history of the Internet can stretch back as far as the 19th century, as early electrical telecommunications like the telegraph laid the conceptual groundwork for global networking, and it cites footnotes 1 and 2. Footnote 1, at line 147, cites History of the Internet: A Chronology, 1843 to the Present, by Christos J. Moschovitis, Hilary Poole and Theresa M. Senft, of 1999, with no page and with a link to a catalog record, and the only copy online, the one footnote 14 links, is a lending copy of the Internet Archive that cannot be read without borrowing it. Footnote 1 is graded Uncheckable.

1.2 Footnote 2, at line 148, cites “Email Innovation Timeline” by Elizabeth Feinler and John Vittal, dated July 1, 2022, of the Computer History Museum, 134 pages, which this page retrieved in full, searched, and read at its title pages, its table of events and its first section. The timeline traces the beginnings of email to the mid-1800s and to communication over wires, and it opens with Samuel Morse’s line of 1844. At line 5, the citation is graded Partial, because the source speaks of the beginnings of email and not of the history of the Internet or of global networking. The work thanks Vint Cerf for funding the digitization of the materials behind it.

1.3 Footnote 3, at line 149, cites RFC 2235, Hobbes’ Internet Timeline, by R. Zakon of MITRE, November 1997, and the footnote itself says that the RFC “essentially also begins in the 1960s.” This page retrieved the RFC in full and read its opening and its timeline through 1969. The RFC begins with a section headed 1950s and an entry for 1957, the launch of Sputnik, and its first entry of the 1960s is Paul Baran’s work of 1962. At line 6, the citation for the statement that the timeline begins in 1960 is graded Partial.

1.4 At line 9, the article says that from 1960 to 1964 J. C. R. Licklider had ideas about human-computer interaction and networking and became the director of Project MAC, and it cites footnotes 4, 5 and 6. Footnote 4, at line 150, cites the fifth chapter of Netizens by Michael Hauben, which this page read in full: it calls Licklider the founding director of the Information Processing Techniques Office of ARPA, says that he thought of time-sharing as interactive computing, and describes his “Intergalactic Network”. Footnote 5, at line 151, cites “The Evolution of Packet Switching” by Lawrence G. Roberts in the Proceedings of the IEEE of November 1978, which this page retrieved in full and read at its section on the pioneers: it says that ARPA under Licklider furthered time-sharing from 1962 to 1964 and that one of his strong interests was to link time-shared computers through a network. Footnote 6, at line 152, cites “The ARPANET & Computer Networks” by Lawrence G. Roberts of May 1995, in the archived copy that the footnote names, which this page read in full: it says that Licklider ran the ARPA office and pursued the concept of the Intergalactic Computer Network. None of the three sources says that Licklider became the director of Project MAC, and the three citations are graded Partial.

1.5 At line 10, the article says that from 1960 to 1964 Paul Baran developed at RAND distributed networking concepts for digital voice communication, and it cites footnotes 7, 8 and 9. Footnote 7, at line 153, cites the article of Christopher S. Yoo in the Colorado Technology Law Journal of 2018 and 2019, which this page retrieved in full and read at its introduction and its section on Baran’s vision: it dates Baran’s briefing to 1961 and his paper to 1962, explains why the network had to be digital, and never uses the word voice. Footnote 8, at line 154, cites “The beginnings of packet switching: some underlying concepts” by Paul Baran in IEEE Communications Magazine of July 2002. The link no longer reaches the file, the footnote names no archived copy, and this page read the text of the copy archived on February 5, 2026 at its passages on voice and on the years 1960 to 1964: Paul Baran writes that his first distributed network proposal at RAND, in 1960, was for a survivable teletypewriter network, and he lists among his principles a single network handling voice, data and teletypewriter. Footnote 9, at line 155, cites “Paul Baran and the Origins of the Internet” of RAND, of March 22, 2018, which this page read in full: it describes a command and control network made robust with redundancy and digital technology and names no voice. The three citations are graded Partial, because each carries distributed networking by Paul Baran at RAND and none carries a design for digital voice.

1.6 At line 11, the article says that from 1965 to 1967 Donald Davies conceived packet switching concepts for data communication in high-speed computer networks, and it cites footnotes 10, 11 and 12. Footnote 10, at line 156, cites the article of Chris Edmondson-Yurkanan in Communications of the ACM of May 2007, which this page retrieved in full and read at its passages on Davies: it records four drafts of 1965 and 1966, the first dated November 10, 1965, and calls Donald Davies one of the co-inventors of the packet-switched network paradigm. Footnote 11, at line 157, cites “Proposal for a Digital Communication Network” by D. W. Davies of the National Physical Laboratory, June 1966, which this page retrieved in full and read at its introduction and summary: it proposes a national communication network that handles data in small packets stored and forwarded at each node. Footnote 12, at line 158, cites “A Digital Communication Network for Computers Giving Rapid Response at Remote Terminals” by D.W. Davies, K.A. Bartlett, R.A. Scantlebury and P.T. Wilkinson, of October 1967, which this page retrieved in full and read at its introduction, its description of packets and its conclusions: it proposes a common-carrier data network that carries packets. The three citations are graded Partial, because the sources carry packet switching for data conceived by Donald Davies and do not describe high-speed computer networks, and because the paper of 1967 has four authors.

1.7 Footnote 13, at line 159, cites “4.7 Planning the ARPANET: 1967-1968” of The History of Computer Communications by James Pelkey for line 12, which says that ARPANET planning began in 1967 to enable resource sharing over a wide area network. The live address returns a page that is not found, and the copy archived on December 23, 2022 that the footnote names, fully read, dates the decision of Robert W. Taylor to interconnect the ARPA time-sharing systems to February 1966, places the hiring of Larry Roberts late in 1966, and places Roberts’s paper at the symposium in Gatlinburg on October 1-4, 1967. It does not use the words resource sharing or wide area network. The citation is graded Partial.

1.8 At line 13, the article lists the Symposium on Operating Systems Principles in Gatlinburg, Tennessee in 1967, and it cites footnotes 14 and 15. Footnote 14, at line 160, cites pages 58 and 59 of the chronology of Christos J. P. Moschovitis of 1999 in a copy of the Internet Archive that is a lending copy and cannot be read without borrowing it, and footnote 14 is graded Uncheckable. Footnote 15, at line 161, cites page 574 of the Encyclopedia of 20th-Century Technology, edited by C. Hempstead and W. Worthington, Routledge, 2005, whose full text this page searched and whose entry Packet Switching, signed by Roger Scantlebury, it read in full. The entry says that the work of the team of Donald Davies was published at the ACM conference “held in Gatlinburg, U.S. in 1967” and calls it a seminal meeting. The citation is graded Partial, because the entry names neither the Symposium on Operating Systems Principles nor Tennessee.

1.9 At line 14, the article says that in 1969 the NPL network followed by the ARPANET carried their first packets, and it cites footnotes 16 and 17. Footnote 16, at line 162, cites “Notable Computer Networks” by John S. Quarterman and Josiah C. Hoskins in Communications of the ACM of October 1986, a scan of 40 pages with no text layer, which this page read by optical character recognition of every page and at its section History: it says that the first packet-switching network was implemented at the National Physical Laboratories and was quickly followed by the ARPANET in 1969. The citation is graded Partial, because the source gives no year for the NPL network and says nothing of first packets. Footnote 17, at line 163, cites the podcast Computer Freaks of Inc. Magazine at 35 minutes and 55 seconds, an audio source whose page carries no transcript, and footnote 17 is graded Uncheckable.

1.10 Footnote 18, at line 164, cites “The Network Information Center and its Archives” by Elizabeth Feinler in the IEEE Annals of the History of Computing of 2010 for line 15, the entry of 1970 for the Network Information Center. The article is offered by IEEE Xplore only by purchase or institutional sign-in, and footnote 18 is graded Uncheckable.

1.11 Footnote 19, at line 165, cites “TYMNET as a multiplexed packet network” by John Kopf of Tymshare, Inc., in the proceedings of the National Computer Conference of June 1977, for line 16, which calls Tymnet a switched-circuit network of 1971. The paper, retrieved in full and read at its abstract and introduction, says that TYMNET has been in continuous operation since November 1971, that circuit routing is set by a central supervisor, and that packets carry virtual channels between neighboring nodes, and it records that TYMNET has been described as a virtual circuit switching network. The citation is graded Partial, because the source titles TYMNET a multiplexed packet network.

1.12 At line 17, the article says that in 1972 Merit Network, founded in 1966, began operation of a packet-switched network, and it cites footnotes 20 and 21. Footnote 20, at line 166, cites the page About of Merit, which this page read in full as served: it says that Merit was founded in 1966 and gives no year 1972 and no packet switching, and the citation is graded Partial. Footnote 21, at line 167, cites the page 1990s of the site The History of Domain Names, which this page read in full: it carries two entries dated 1990 and names neither Merit nor 1966 nor 1972, and the citation is graded Not supported.

1.13 Footnote 22, at line 168, cites “The History of IANA” of the Internet Society, of 9 May 2016, by Joel Snyder, Konstantinos Komaitis and Andrei Robachevsky, for line 18, which says that the Internet Assigned Numbers Authority was established in 1972. This page retrieved the timeline in full and read its introduction and its entries from May 30, 1972 through January 1983. The timeline describes the history of IANA “from its birth in 1972”, and the citation is graded Supported. The same timeline records that in 1972 Jon Postel became the de facto authority for assigning identifiers and that the name IANA first appears in an RFC in RFC 1083.

1.14 At line 19, the article says that in 1973 the CYCLADES network was demonstrated by Louis Pouzin and Hubert Zimmerman, and it cites footnotes 23 and 24. Footnote 23, at line 169, cites the article of Andrew L. Russell and Valérie Schafer in Technology and Culture of 2014, whose identifier opens a page of Project MUSE that demands human verification, and footnote 23 is graded Uncheckable. Footnote 24, at line 170, cites “Presentation and Major Design Aspects of the CYCLADES Computer Network” by Louis Pouzin of IRIA, of 1973, which this page retrieved in full and read at its summary, introduction, planning section and acknowledgments: it says that the project was launched at the beginning of 1972, that the first host-to-host communications were to be tested in May 1973, and it thanks H. Zimmermann for an outstanding contribution on host protocols. The citation is graded Partial, because the paper states a plan and reports no demonstration.

1.15 At line 36, the article says that the JANET network came online in 1984, and it cites footnotes 25 and 26. Footnote 25, at line 171, cites “JANET - the United Kingdom Joint Academic Network” by Mike Wells in Serials of November 1988, which this page retrieved in full and read at its sections on history and objectives: it says that the Computer Board agreed in the winter of 1982 to fund a single network and that its author became Director of Networking in April 1983, and it gives no date on which JANET came online, so the citation is graded Partial. Footnote 26, at line 172, cites the thesis of Dorian Rutter at the University of Warwick of 2005, whose text this page extracted in full and searched: it refers to “the launch of JANET during 1984”, and the citation is graded Supported.

2.0 The sources of the early entries correct the entries on Paul Baran, on Tymnet, on the NPL network and on CYCLADES, and three of the sources were written by persons who took part in the work they describe.

2.1 The entry at line 10 gives Paul Baran’s concepts the purpose of digital voice communication. Paul Baran himself, at footnote 8, writes that his first RAND proposal, of 1960, was for a survivable teletypewriter network carrying minimum essential communications, Lawrence G. Roberts, at footnote 5, says that Baran’s study proposed a system for all military communications, data and voice, and RAND, at footnote 9, describes a survivable command and control network. None of the three sources gives the work a purpose of voice alone.

2.2 The entry at line 16 calls Tymnet a switched-circuit network. Its own source, at footnote 19, titles TYMNET a multiplexed packet network, Lawrence G. Roberts, at footnote 5, describes TYMNET as a network of minicomputer switches that store and forward data from node to node, installed from 1969.

2.3 The entry at line 14 dates the first packets of the NPL network to 1969. The sources of the article disagree with one another on that date. Roger Scantlebury, at footnote 15, cited at line 13 and not at line 14, writes that elements of the pilot NPL network first operated in 1969. James Pelkey, at footnote 13, records in his note 20 that the NPL Data Communication Network would not become operational until June 1973, and Lawrence G. Roberts, at footnote 5, describes a local network at NPL with a single packet switch. The words that footnote 17 quotes from Leonard Kleinrock also speak of a single node packet switch, and that source could not be checked.

2.4 The entry at line 19 says that CYCLADES was demonstrated in 1973 by Louis Pouzin and Hubert Zimmerman. The paper of Louis Pouzin at footnote 24 plans tests for May and June 1973 and reports none, and it spells the name Zimmermann. Lawrence G. Roberts, at footnotes 5 and 6, says that the first hosts were connected to CYCLADES in 1973 and names Louis Pouzin alone as its designer.

2.5 The entry at line 9 gives Licklider the directorship of Project MAC, and none of the three sources cited there says so. The words come closest in the source of footnote 13, cited at line 12, where Licklider is quoted, speaking of the planning of 1967, as saying that he believed he was director of Project MAC at that time.

2.6 Three of the sources were written by persons who took part in the work they describe, and one was funded in part by a person the article credits elsewhere. Roger Scantlebury, the author of the entry at footnote 15, is a co-author of the NPL paper of October 1967 at footnote 12 and presented that paper at Gatlinburg, as footnotes 6 and 13 record. Mike Wells, the author of the article at footnote 25, was the Director of Networking of the network his article describes. Lawrence G. Roberts, the author of footnotes 5 and 6, was the program manager of the ARPANET, as footnote 13 records. The authors of footnote 2 thank Vint Cerf for funding the digitization of the materials behind their timeline.

3.0 Line 7 and 123 entries and headings of the timeline carry no footnote, and the article’s own banner says that it needs more citations.

3.1 Line 7 and lines 20 through 35 and 37 through 143 carry no footnote. The article’s own banner, at line 3, says that it needs more citations and dates that notice to December 2025.

3.2 At line 7, the article says “These events led to the Internet as we know it today.” and cites nothing. The words follow the introduction of RFC 2235 at footnote 3, which presents events and technologies that helped shape the Internet as we know it today.

3.3 The headings at line 8 and line 29 carry no footnote, and the heading at line 29, “Merging the networks and creating the Internet (1981-1994)”, is answered by Disagreement 96 under D1 and D9 of the Definitions Addendum.

4.0 Of the 26 citations, 2 carry the sentence that cites them, 18 carry it in part, 1 does not carry it, and 5 cannot be checked.

4.1 Counted by footnote, footnotes 22 and 26 are graded Supported, footnotes 2 through 13, 15, 16, 19, 20, 24 and 25 are graded Partial, footnote 21 is graded Not supported, and footnotes 1, 14, 17, 18 and 23 are graded Uncheckable.

4.2 The two citations graded Supported carry the entry of 1972 for the Internet Assigned Numbers Authority at line 18 and the entry of 1984 for JANET at line 36. No other footnoted entry of the timeline is carried whole by any of its sources.

5.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.

5.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.

5.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.

6.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.

6.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.

6.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.