Wikipedia Internet Protocol Suite: Reference Audit | Network, Not Protocol

Of the 91 citations in the Wikipedia article Internet protocol suite, 19 carry the sentence that cites them, 35 carry it in part, 7 do not carry it, 26 cannot be checked and 4 were not read, and the sources the article cites date the first IMP's arrival at UCLA to August 30, 1969 and the Department of Defense directive on TCP/IP to December 23, 1978, while one footnote cites a 2012 printout of the article itself.

Preamble: I audit the Wikipedia article Internet protocol suite 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 15 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 Defines the Internet Protocol Suite: 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 Internet protocol suite of the English Wikipedia at revision 1381049376 of October 19, 2026, the revision that Exhibit A of Disagreement 15 reproduces. Wikipedia's revision history records that revision 1381049376 was saved by the account La Qinglü with the edit summary "spacing", which unit 0.1 of Disagreement 15 records as unknown. Wikipedia's revision history also records three later revisions, all of November 11, 2026: revision 1384980386 by the account Popcornfud with the summary "MOS:INTERNET", revision 1384980469 by the same account, and revision 1384998760 by the account Autoinvective, the latest revision on November 14, 2026, whose summary reads in part "Internet Protocol et. al. are capitalized (both words) even if Internet and Internet protocol suite are not". This page audits revision 1381049376.

0.2 Revision 1381049376 carries 76 numbered footnotes and 2 lettered notes. The numbered footnotes are cited 90 times, once of them inside note a, and note b is a pointer to the index of Internet Experiment Notes, so this page grades 91 citations. Eight of the citations sit in the table of layering models, which Exhibit A does not reproduce, and units 1.50 through 1.53 grade them against the table's column headings. This page read the list of footnotes, the links of each footnote and the position of each citation in revision 1381049376 through Wikipedia's own public interface on November 14, 2026.

0.3 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, or, where the live page could not be read, at the latest archived copy of the same address, which the unit that grades it identifies. Of the 76 numbered footnotes, 43 were read in full or retrieved in full and read at the passages that bear on the sentence they support after a search of the whole text, 5 were read at the cited page or in part, and 28 could not be read, and note b was read in full; the unit that grades each states which. Several sources had been read for Wikipedia Internet Protocol: Reference Audit | Network, Not Protocol or for Wikipedia Leonard Kleinrock: Reference Audit | Network, Not Protocol, and the units that grade them say so.

0.4 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, and the four citations so graded point to books that the Internet Archive lends and does not show.

0.5 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 15. Where a site asked this page for a sign-in or stopped it at a check for automated visitors, this page stopped there and did not go around the check, and the unit says so.

1.0 Each of the 76 footnotes and 2 notes of the article is graded at each sentence that cites it.

1.1 Footnote 1 cites RFC 1122, "Requirements for Internet Hosts -- Communication Layers", October 1989, edited by R. Braden, and footnote 2 cites its companion RFC 1123, "Requirements for Internet Hosts -- Application and Support". Both were retrieved in full from rfc-editor.org and searched. RFC 1122 names four layers, Application, Transport, Internet and Link, says that a host "typically must implement at least one protocol from each layer", and says of itself that it "incorporates by reference, amends, corrects, and supplements the primary protocol standards documents relating to hosts". RFC 1123 says that it covers "the applications layer and support protocols" and that its companion covers the transport, IP and link layers.

1.2 At line 5, both RFCs carry the four layers, and neither carries the words that the layers "classify all related protocols according to each protocol's scope of networking", so both citations are graded Partial. At line 75, both RFCs carry the four layers and the support protocols, and RFC 1122 calls itself a set of host requirements that supplements the primary protocol standards, not the defining specification of the suite, so both citations are graded Partial. At line 95, both RFCs name the layers and number none of them, and both citations are graded Supported.

1.3 At line 88, footnote 1 with the page locator 13 cites RFC 1122, whose page 13 carries the quotation word for word, and the citation is graded Supported. At line 179, footnote 1 with the locator §1.1.3 cites the section that says "We distinguish two categories of application layer protocols: user protocols that provide service directly to users, and support protocols that provide common system functions", and the citation is graded Supported.

1.4 Footnote 3 cites Hafner and Lyon (1998), page 91, for line 12; footnotes 6 and 7 cite the same book at page 103 and at pages 103 and 151 for line 14 and line 15; and footnote 9 cites page 153 for line 16. The four footnotes give no link, and Wikipedia's own reference template marks each "harvnb error: no target", because the article lists no edition of 1998. The four citations are graded Uncheckable.

1.5 Note a, which revision 1381049376 places after line 12, says that the same idea "had earlier been independently developed by Donald Davies who was the first to implement packet switching in the local area NPL network" and cites footnote 4, Lawrence G. Roberts, "The ARPANET & Computer Networks", May 1995, in the copy archived on March 24, 2016 that the footnote names. The page, retrieved in full and searched, says that the development of packet switching "happened independently at Rand, NPL and ARPA" and does not say that Davies was the first to implement it or name a local area NPL network, so the citation is graded Partial.

1.6 Footnote 5 cites Dave Walden, "Looking back at the ARPANET effort, 34 years later", at livinginternet.com, read in the copy archived on October 9, 2026. Walden names Frank Heart as team leader and Robert Kahn on the team, and writes that "on August 30, 1969, the first IMP was delivered to UCLA" and that the first four IMPs had been delivered by the end of 1969. The page gives no cost of nearly $1 million, so the citation at line 14 is graded Partial.

1.7 Footnote 8 cites Leo Beranek, "BBN's earliest days: founding a culture of engineering creativity", IEEE Annals of the History of Computing, 2005, for the LO message at line 16. The DOI resolves to IEEE Xplore, whose abstract and section outline describe the founding of BBN and whose full text is behind a sign-in, so the citation is graded Uncheckable.

1.8 Footnote 10 cites RFC 1000 of August 1987 by J. Reynolds and J. Postel, which carries Stephen D. Crocker's "The Origins of RFCs", retrieved in full. Crocker describes the meetings from the summer of 1968, says that "the Network Working Group began to take shape", and says that the host-host protocol and "an abstract implementation of the protocol known as the Network Control Program" were designed in the months after December 1969. He also writes that "ARPA" did not become "DARPA" until 1972 and does not say that he established the group. At line 17, the citation is graded Partial.

1.9 Footnote 11 cites Hafner and Lyon (1996), page 263, at the Internet Archive item wherewizardsstay00haf_vgj, which the Internet Archive marks access-restricted for lending, so the citation at line 20 is graded Unread. Footnote 12 cites Andrew L. Russell, Open Standards and the Digital Age (2014), page 196, whose page image at Google Books was read in full. The page quotes Cerf that "the DARPA effort had been under way since 1973" and does not carry the spring of 1973 or Stanford, so the citation at line 20 is graded Partial. The page also records what Russell calls "the bitter strategic battle within INWG".

1.10 Footnote 13 cites Janet Abbate, Inventing the Internet (1999), page 3, whose page image at Google Books was read in full. The page says that "Cerf and Kahn also enlisted the help of computer experts from England, France, and the United States" and does not name INWG or Xerox PARC, so the citation at line 21 is graded Partial. The footnote's own quotation of the page reads "computer scientists" where the page reads "computer experts".

1.11 Footnote 14 cites the oral history of Robert (Bob) Taylor, Computer History Museum reference X5059.2009, at page 28. The transcript of 74 pages, conducted by Paul McJones and dated by the transcript October 10, 2008, was retrieved in full and page 28 was read in full. The page describes Xerox researchers at a design meeting with the Stanford group, and Taylor says that "TCP/IP designs were based a lot on PUP". The page names neither INWG nor the United Kingdom or France, so the citation at line 21 is graded Partial.

1.12 Footnote 15 cites Walter Isaacson, The Innovators (2014), at the Internet Archive item innovatorshowgro0000isaa_p2p3, which the Internet Archive marks access-restricted for lending, so the citations at line 21 and line 22 are graded Unread.

1.13 Footnote 16 cites Vinton Cerf and Robert Kahn, "A Protocol for Packet Network Intercommunication", IEEE Transactions on Communications, May 1974, in the copy at cs.princeton.edu that this page read in full by optical character recognition for Wikipedia Internet Protocol: Reference Audit | Network, Not Protocol. The paper thanks colleagues "for helpful comments during early discussions of international network protocols" and names Metcalfe, Scantlebury, Walden, Zimmerman, Davies, Pouzin and Crocker. It does not call them members of INWG or call their comments important influences on the design, so the citation at line 23 is graded Partial.

1.14 Footnote 17 cites RFC 675, "Specification of Internet Transmission Control Program", December 1974, whose header names Vinton Cerf, Yogen Dalal and Carl Sunshine and no institution. The RFC carries the authors and the date and not Stanford University, so the citation at line 24 is graded Partial.

1.15 Footnote 18 cites Vinton Cerf, as told to Bernard Aboba, "How the Internet Came to Be" (1993), in the copy archived on September 26, 2017 that the footnote names. The essay, retrieved in full, says "We began doing concurrent implementations at Stanford, BBN, and University College London" and does not say that DARPA contracted the three or give the year 1975, so the citation at line 25 is graded Partial. The essay also says that BBN delivered the IMP to UCLA "Around Labor Day in 1969", that the last of four iterations of TCP came out in 1978, and that "The earliest demonstration of the triple network Internet was in July 1977".

1.16 Footnote 19 cites Vinton Cerf, "Final Report of the Stanford University TCP Project", IEN 151, April 1, 1980, fully read. The report lists the versions of TCP of December 1974 and March 1977 and versions 3 and 4 "in January 1978 and February 1979, respectively", and says that the internetwork functions "were separated into a distinct protocol layer in early 1979 with the publication of version 4 of TCP". At line 26, the versions are carried and the IEN series as the forum of discussion is not, so the citation is graded Partial. At line 44, the report lists implementations at several centers through 1980 and cannot speak to 1983, so the citation is graded Partial.

1.17 Footnote 20 cites Cerf, "Specification of Internet Transmission Control Protocol TCP (Version 2)", March 1977, IEN 5, a scan of 106 pages, of which this page read pages 1 through 5 by optical character recognition. The introduction says that processes "exchange finite length LETTERS" and that "letter boundaries are significant", with a byte stream as one way of using a connection. The pages read do not say that the program provided only a byte stream and not datagrams, so the citation at line 27 is graded Partial.

1.18 Footnote 21 cites Georgios Panzaris, Machines and Romances (2008), page 128, at Google Books, which shows the book in snippet view and no page text, so the citation at line 29 is graded Uncheckable. Footnote 24 reads "Internet Hall of Fame" with no link and no title, and the citation at line 29 is graded Uncheckable.

1.19 Footnote 22 cites James Pelkey's interview page "Yogen Dalal", read in the copy archived on October 20, 2026. The page says that Dalal, John Shoch and David Boggs at Xerox PARC "did what they could to convince Cerf and his team of the need for both a datagram and a session protocol". It does not name Metcalfe as an advocate or name Cohen or Postel, so the citation at line 29 is graded Partial.

1.20 Footnote 23 cites "On the design of TCP/IP" at nethistory.info, an exchange of email among Vinton Cerf, Bob Frankston and David Reed, read in full on the live site after the archived copy returned a check page. Cerf recalls "Danny Cohen's argument" for a fast service for voice, and Reed writes that "John Schoch, Danny Cohen and I each presented arguments" for datagrams. The source names Reed among the advocates and does not name Metcalfe, Dalal or Postel, so the citation at line 29 is graded Partial.

1.21 Footnote 25 cites Jon Postel, "Comments on Internet Protocol and TCP", IEN 2, August 15, 1977, fully read. The IEN carries the sentence that the article quotes at line 30, and it prints the word Internet with a lowercase initial where the article's quotation prints a capital, unmarked, so the citation is graded Partial.

1.22 Footnote 26 cites Abbate, Inventing the Internet, pages 129 and 130, with no link, and footnote 27 cites Cerf, "Protocols for Interconnected Packet Networks", ACM SIGCOMM Computer Communication Review, October 1980, with no link, so both citations at line 33 are graded Uncheckable.

1.23 Footnote 28 cites Andrew L. Russell's doctoral thesis of 2007 at Johns Hopkins, a PDF of 391 pages whose text was extracted in full and searched. Russell writes that "In 1978, Cerf and two other ARPA-funded researchers, Danny Cohen and Jon Postel, split the functions of TCP into two protocols". The thesis carries the split of 1978 and credits three researchers, not Postel alone, and does not name version 4, so the citation at line 33 is graded Partial. Note b points to the index of Internet Experiment Notes at rfc-editor.org, which was read in full and lists the notes, and the note at line 33 is graded Supported.

1.24 Footnote 29 cites Marc Weber, "Born in a Van: Happy 40th Birthday to the Internet!", Computer History Museum blog, November 22, 2017, read in the copy archived on July 18, 2026. The post carries the route, the three networks and the date, and reads "On a rainy Wednesday, November 22, 1977". line 35 reads Tuesday, and November 22, 1977 fell on a Tuesday, so the article departs from its source without saying so, and the citation is graded Partial.

1.25 Four footnotes cite line 37 for the end-to-end principle as pioneered by Louis Pouzin and Hubert Zimmermann in CYCLADES on the ideas of Donald Davies. Footnote 30, the article of The Economist on Louis Pouzin, dated on the page November 30, 2013, read in the copy archived on April 19, 2020 that the footnote names, says that on CYCLADES "The receiving computer, not the network, would then juggle the packets back into order". Footnote 31, Richard Bennett, "Designed for Change", ITIF, September 2009, extracted in full, says that CYCLADES, "designed by Louis Pouzin, pioneered the use of the datagram, functional layering, and the end-to-end strategy". Footnote 32, Pelkey's section 8.3, in the copy archived on June 17, 2021 that the footnote names, quotes Pouzin that one inspiration for datagrams "was Donald Davies' studies". Footnote 33, the paper of Davies, Bartlett, Scantlebury and Wilkinson of October 1967, says that users "will provide themselves with some kind of error control". None of the four names Zimmermann as a pioneer of the principle, and each carries only part of the sentence, so the four citations are graded Partial.

1.26 Footnote 34 cites the Internet Hall of Fame article "Virginia Travers: Technology Does Not Develop Along a Linear Path" of February 3, 2023, read in the copy archived on May 18, 2026. The article says that Travers installed the first gateway at University College London, worked on the Packet Radio Net, and went to Oslo for the Atlantic Satellite Network connection at the Norwegian Defense Research Establishment. It does not say that she had written the first gateway software for TCP or spent months traveling, which are the words of footnote 29, so the citation at line 39 is graded Partial.

1.27 Footnote 35 cites Vinton Cerf and Edward Cain, "The DoD Internet Architecture Model", Computer Networks, October 1983. The DOI resolves to ScienceDirect, which served an error page, so the citation at line 41 is graded Uncheckable.

1.28 Footnote 36 cites RFC 1812, "Requirements for IP Version 4 Routers", June 1995, edited by F. Baker, retrieved in full and searched. The RFC describes routers as devices that "perform the network layer forwarding function", and its chapter 7 is titled "APPLICATION LAYER - ROUTING PROTOCOLS", so the citations at line 46 and line 215 are graded Supported. The RFC also says that older documents call routers gateways, "a name which more recently has largely passed out of favor to avoid confusion with application gateways", which carries line 47. line 47 cites only footnote 37, Crowell, Contos and DeRodeff (2011), page 99, which gives no link, and that citation is graded Uncheckable.

1.29 Three footnotes cite line 48 for the declaration of March 1982. Footnote 39, IEN 207, is a memorandum of March 1982 signed by Richard D. DeLauer which says "The policy cited in reference (a) is reaffirmed" and makes TCP and IP mandatory for DoD packet networks "which have a potential for host-to-host connectivity across network or subnetwork boundaries", with case-by-case exceptions. Footnote 40, IEN 152 of July 1, 1980, carries the memorandum of December 23, 1978 signed by Gerald P. Dinneen, "directing the adoption of a set of DoD standard host-to-host protocols based on the Transmission Control and Internet Protocols", and the memorandum of April 3, 1980 by which the specifications "are hereby ratified". Footnote 38, Ronda Hauben, "From the ARPANET to the Internet", in the copy archived on July 21, 2009 that the footnote names, reports the memorandum of March 1982. IEN 152 and IEN 207 limit the mandate to networks with a potential for connectivity across network boundaries, Hauben quotes the same words, and IEN 152 dates the directive to 1978, so the three citations are graded Partial.

1.30 Footnote 41 cites Ronda Hauben, "The Internet: On its International Origins and Collaborative Vision", Amateur Computerist 12(2), read in the copy archived on September 18, 2026. Its chronology reads "Mar '82 - Norway leaves the ARPANET and become an Internet connection via TCP/IP over SATNET" and "Nov '82 - UCL leaves the ARPANET and becomes an Internet connection", and the citation at line 49 is graded Supported.

1.31 At line 50, footnote 38 reports that "The cutover happened on January 1, 1983 as scheduled", and footnote 42, the Living Internet page "TCP/IP Internet Protocol", in the copy archived on January 1, 2018 that the footnote names, says that "The full switchover to TCP/IP was performed on January 1, 1983", and both citations are graded Supported. The Living Internet page also says that "Between 1978 and 1983, several TCP/IP research prototypes were developed", which carries line 44, and that in 1984 the Department of Defense made TCP/IP the standard for all military computer networking, against the date of line 48.

1.32 Footnote 43 cites "A Brief History of the Internet" of the Internet Society, by Leiner, Cerf, Clark, Kahn, Kleinrock, Lynch, Postel, Roberts and Wolff, at page 15, which this page read in full for Wikipedia Leonard Kleinrock: Reference Audit | Network, Not Protocol and searched again. Page 15 says that in 1985 "Dan Lynch in cooperation with the IAB arranged to hold a three day workshop for ALL vendors", that "About 250 vendor personnel came", and that "In September of 1988 the first Interop trade show was born". The paper does not name IBM or DEC as attendees, so the citation at line 54 is graded Not supported. Footnote 44 cites the oral history of Vinton G. Cerf at exhibits.stanford.edu, which redirected to a Stanford sign-in page, and the citation at line 54 is graded Uncheckable.

1.33 Footnote 45 cites Microsoft Knowledge Base article 108007, "Using Wollongong TCP/IP with Windows for Workgroups 3.11", in the copy archived on January 12, 2012 that the footnote names. The article describes the Wollongong Group's TCP/IP stack for DOS and does not name FTP Software, so the citation at line 58 is graded Partial. Footnote 46 cites Ben Segal, "A Short History of Internet Protocols at CERN" (1995), in the copy archived on November 10, 2016 that the footnote names, which describes TCP/IP on IBM VM/CMS "from the first University of Wisconsin version (WISCNET)", and the citation at line 59 is graded Supported.

1.34 Footnote 47 cites "An Introduction to Computer Networks, Stanford Univ CS144 Fall 2012", a PDF of 127 pages at kirils.org whose text was extracted in full. The PDF states that it was "generated using the open source mwlib toolkit" on October 9, 2012, and it is a book of Wikipedia articles whose list of sources names the article Internet protocol suite at revision 515653549. Its page 22, which is that article, reads "Jay Elinsky and Oleg Vishnepolsky of IBM Research wrote TCP/IP stacks for VM/CMS and OS/2, respectively." The citation at line 61 is graded Supported as printed, and section 2.0 records that the source is the article itself.

1.35 Footnote 48 cites Steven Baker and Donald W. Gillies, "Desktop TCP/IP at middle age", in the copy archived on August 21, 2015 that the footnote names. It says that one early task of FTP Software was "to port all the higher layers to use the multi-channel TCP from Donald Gillies" and that PC/IP was abandoned at MIT in January 1986 when Romkey and Dave Bridgam left "and FTP Software was incorporated", and the citation at line 63 is graded Supported. Footnote 49 cites John Romkey's page "About", in the copy archived on November 5, 2011 that the footnote names, which says that he co-founded FTP Software and gives no year and no TCP of Gillies, and the citation at line 63 is graded Partial.

1.36 Footnote 50 reads "Phil Karn, KA9Q TCP Download Website" with no link, and the citation at line 64 is graded Uncheckable.

1.37 Three footnotes cite line 72 for the period of polarization between OSI and the suite. Footnote 51, Andrew L. Russell, "OSI: The Internet That Wasn't", IEEE Spectrum, July 30, 2013, read in the copy archived on October 24, 2026, names "the Internet-OSI standards wars". Footnote 52, Russell's "'Rough Consensus and Running Code' and the Internet-OSI Standards War", in the PDF archived on November 17, 2019 that the footnote names, extracted in full, describes "A spirited rivalry between respective advocates of OSI and TCP/IP networks". Footnote 53, Howard Davies and Beatrice Bressan, A History of International Research Networking (2010), page 106, whose page image was read in full, begins "The Protocol Wars" with "The protocol wars were undeclared and no peace treaty was ever signed". The three citations are graded Supported. At line 77, footnote 53 again cites page 106, which says nothing of the suite predating OSI, and the citation is graded Not supported.

1.38 Footnote 54 cites the IETF page "Introduction to the IETF", read in the copy archived on November 11, 2026 and in the copy archived on February 27, 2024, the date on which the footnote says it was retrieved. Both copies call the IETF "the premier standards development organization (SDO) for the Internet", and neither says that standards were delegated to it or names TCP/IP or OSI. At line 73, the citation is graded Partial, and at line 206, which Wikipedia itself tags "failed verification", the citation is graded Not supported. Footnote 55 cites Roberto Morabito and Jaime Jiménez, "IETF Protocol Suite for the Internet of Things" (2020), whose abstract at arXiv, in the copy archived on December 13, 2025, was read and calls the IETF one of the most active standards bodies for the Internet of Things, and the citation at line 73 is graded Partial.

1.39 Footnote 56 cites RFC 6214 of April 1, 2011 by B. Carpenter and R. Hinden, "Adaptation of RFC 1149 for IPv6", an April Fools' RFC on carrying IPv6 datagrams by the medium of RFC 1149. Its introduction says that providers plan "to deploy IPv6 to alleviate the imminent shortage of IPv4 addresses", and the citation at line 78 is graded Partial.

1.40 Footnote 57 cites Marjory S. Blumenthal and David D. Clark, "Rethinking the design of the Internet: The end to end arguments vs. the brave new world" (2001), extracted in full, which names firewalls, Network Address Translation boxes and content caches among the departures from the end to end design, and the citation at line 86 is graded Supported.

1.41 Footnote 58 cites RFC 791, "Internet Protocol", September 1981, with the page locator 23. Section 3.2 on page 23 carries the quotation of line 87 word for word, and the citation is graded Supported. RFC 791 says that an implementation "must be robust" and does not use the name robustness principle.

1.42 Footnote 59 cites RFC 1958, "Architectural Principles of the Internet", June 1996, edited by B. Carpenter, fully read, which names neither RFC 1122 nor RFC 1123, so the citation at line 93 is graded Not supported.

1.43 Footnote 60 cites Craig Hunt, TCP/IP Network Administration (2002), pages 9 and 10, with no link, and the citation at line 101 is graded Uncheckable.

1.44 Footnote 61 cites E. Guttman, "Service location protocol", IEEE Internet Computing, 1999, and footnote 62 cites Kai Zheng, "Enabling Protocol Routing", IEEE Internet Computing, 2017. Both DOIs resolve to IEEE Xplore, whose abstracts describe a service discovery protocol and a transport framework and whose full texts are behind a sign-in. The citations at line 110 and line 111, which Wikipedia itself tags "failed verification", are graded Uncheckable. Footnote 63 cites Jing-lian Huang (2009), whose DOI the reference itself marks inactive, and the citation at line 113 is graded Uncheckable.

1.45 Footnote 64 cites W. Richard Stevens, TCP/IP Illustrated, Volume 1 (1994), at the book's page on kohala.com in the copy archived on April 22, 2012 that the footnote names. The page, fully read, lists the book's ISBN, errata and source code and carries none of its text, so the citation at line 171 is graded Uncheckable.

1.46 Footnote 65 cites "A Breakdown of Deep Packet Inspection & How It Works" at ir.com, read in the copy archived on July 13, 2026 and searched in full. The guide does not mention RSVP or the Resource Reservation Protocol, so the citation at line 187 is graded Not supported.

1.47 Footnote 74 cites RFC 3439, "Some Internet Architectural Guidelines and Philosophy", December 2002, by R. Bush and D. Meyer, retrieved in full. Its section 3 is titled "Layering Considered Harmful", and the citation at line 207 is graded Supported. The RFC says nothing of textbooks or of RFC 1122, and the citation at line 196 is graded Not supported.

1.48 Footnote 75 cites "Network Layers Explained: OSI & TCP/IP Models [with examples]" at plixer.com, fully read on the live site, which shows no author or date. The page describes the TCP/IP model "with only 4 layers" and no model of five layers, so the citation at line 203 is graded Not supported. The page also says "While TCP/IP is the newer model".

1.49 Footnote 76 cites RFC 1122, which says that "The Internet layer of host software MUST implement both IP and ICMP" and that "implementation of IGMP is OPTIONAL". At line 223, the RFC carries IP, ICMP, TCP and UDP as required and contradicts the inclusion of IGMP, and the citation is graded Partial.

1.50 The table credits the Internet model of Cisco Academy to footnote 66, Dye, McDonald and Rufi, Network Fundamentals (Cisco Press, 2007); the TCP/IP 5-layer reference model to footnote 67, Charles M. Kozierok, The TCP/IP Guide (2005), and footnote 68, Douglas Comer, Internetworking with TCP/IP (2006); the TCP/IP protocol suite or five-layer Internet model to footnote 70, Forouzan and Fegan, Data Communications and Networking (2003); and the TCP/IP model to footnote 72, William Stallings, Data and Computer Communications (2007). Each footnote links a Google Books record with no page, and a search inside each book returns page numbers and no page text, so the five citations are graded Uncheckable.

1.51 The table credits the TCP/IP 5-layer reference model of Tanenbaum to footnote 69, Computer Networks (2003), page 42, at the Internet Archive item computernetworks00tane_2, which the Internet Archive marks access-restricted for lending, so the citation is graded Unread.

1.52 The table credits the five-layer Internet model of Kurose to footnote 71, Kurose and Ross, Computer Networking: A Top-Down Approach (2008), at the publisher's catalog page in the copy archived on January 23, 2016 that the footnote names. The page lists the table of contents and gives no count of layers, and the citation is graded Uncheckable.

1.53 The table credits the OSI model to footnote 73, ISO/IEC 7498-1:1994, at the catalog page of the International Organization for Standardization, read in the copy archived on November 4, 2026. The page gives the title and edition and sells the text, and the citation is graded Uncheckable.

2.0 The sources the article cites contradict its dates for the selection of BBN, the first IMP, the Department of Defense mandate, the split of TCP and the first Interop, and one footnote cites the article itself.

2.1 At line 12, the article says that ARPA selected BBN in August 1968, and RFC 1000 at footnote 10, cited at line 17, says that "BBN won the procurement in December 1968". At line 15, the article says that the first IMP was shipped to UCLA in September 1969, and three sources it cites at other lines date the arrival earlier: Walden at footnote 5 writes "on August 30, 1969", Crocker in RFC 1000 writes that the IMP "arrived on our loading dock on Saturday, August 30", and Cerf at footnote 18 writes "Around Labor Day in 1969". Section 2.0 of Disagreement 15 answers the same two lines.

2.2 At line 48, the article says that the Department of Defense declared TCP/IP the standard for all military computer networking in March 1982. IEN 152 at footnote 40 carries the directive of December 23, 1978 signed by Gerald P. Dinneen and the ratification of April 3, 1980, IEN 207 at footnote 39 reaffirms that policy in March 1982 over the signature of Richard D. DeLauer, and each limits the mandate to networks with a potential for connectivity across network or subnetwork boundaries. The Living Internet page at footnote 42, cited at line 50, gives 1984.

2.3 At line 33, the article says that Postel split the Transmission Control Program in version 4, written in 1978. IEN 151 at footnote 19, Cerf's report of April 1, 1980, dates version 4 to February 1979 and the separation of IP into its own protocol layer to early 1979. Russell's thesis at footnote 28 dates the split to 1978 and credits Cerf, Danny Cohen and Jon Postel together, and Cerf's essay at footnote 18 says that the last of four iterations came out in 1978.

2.4 Footnote 47, cited at line 61, is a book of Wikipedia articles generated by the mwlib toolkit on October 9, 2012, and the page it cites is the article Internet protocol suite at revision 515653549. The article cites a printout of itself. The same printout credits AT&T with the release of June 1989 that line 65, which carries no footnote, credits to the University of California, Berkeley.

2.5 At line 52, which carries no footnote, the article dates the first Interop conference to 1985. The Internet Society paper at footnote 43, cited at line 54, says "In September of 1988 the first Interop trade show was born". The same page carries the workshop of 1985 that line 51 describes without a footnote, and credits it to Dan Lynch "in cooperation with the IAB", where line 51 says that the Internet Advisory Board held it. Daniel C. Lynch, the subject of line 53, is one of the nine authors of the paper. Section 6.0 of Disagreement 15 dates the TCP/IP Vendors Workshop to August 25 through 27, 1986.

2.6 RFC 1122 describes itself as host requirements that incorporate and supplement "the primary protocol standards documents", which bears on the words "defining specifications" at line 75. RFC 1122 makes IGMP optional, which bears on line 223. RFC 1958, cited at line 93, does not name RFC 1122 or 1123, and RFC 3439, cited at line 196, does not mention textbooks. The source of line 78 is an April Fools' RFC on the medium of RFC 1149.

2.7 Four sources the article cites for the design of TCP and IP record contributions and conflicts that the article's lines 20 through 33 do not carry. Robert Taylor at footnote 14 says that "TCP/IP designs were based a lot on PUP", the protocol of Xerox PARC. Russell's thesis at footnote 28 records that in January 1978 INWG, the group that line 21 says Cerf chaired, "chose a protocol developed within the Cyclades network" over TCP, and Russell's book at footnote 12 records "the bitter strategic battle within INWG". The exchange at footnote 23 names David Reed among the three advocates of the split, and line 29 does not name him.

2.8 Three lines carry the words of a source other than the one they cite. line 39 carries the words of the Computer History Museum post at footnote 29, "had written the first gateway software for TCP" and "spent months traveling to US and European sites to install the software at the points that would be needed for the big test", and cites the Internet Hall of Fame article at footnote 34. line 44 follows the Living Internet page at footnote 42 and cites footnote 19. line 47 follows RFC 1812 at footnote 36 and cites footnote 37.

2.9 The Plixer page at footnote 75 says "While TCP/IP is the newer model", and the article says at line 9 and line 77 that the suite predates the OSI model. The deep packet inspection guide at footnote 65, cited for RSVP at line 187, does not mention RSVP, and the IETF page at footnote 54, cited at line 206, does not mention OSI.

3.0 Most lines of the article carry no footnote, and the sources of other footnotes bear on some of them.

3.1 Of the 224 lines of Exhibit A, 56 lines carry footnotes or notes: lines 5, 12, 14 through 17, 20 through 27, 29, 30, 33, 35, 37, 39, 41, 44, 46 through 50, 54, 58, 59, 61, 63, 64, 72, 73, 75, 77, 78, 86 through 88, 93, 95, 101, 110, 111, 113, 171, 179, 187, 196, 203, 206, 207, 215 and 223. Every other line carries none, including the lead at lines 1 through 4 and 6 through 9, the Interop lines 51 through 53, the release of June 1989 at line 65, and the address lines 134 through 138.

3.2 The Internet Society paper at footnote 43 carries the workshop of line 51 and dates the first Interop of line 52 to 1988. The 2012 printout at footnote 47 credits AT&T with the release of line 65. Section 8.0 and section 9.0 of Disagreement 15 answer lines 135 through 138.

4.0 Of the 91 citations, 19 carry the sentence that cites them, 35 carry it in part, 7 do not carry it, 26 cannot be checked and 4 were not read.

4.1 The 19 citations graded Supported are footnote 1 at line 88, footnote 1 at line 95, footnote 1 at line 179, footnote 2 at line 95, note b at line 33, footnote 36 at line 46, footnote 41 at line 49, footnote 38 at line 50, footnote 42 at line 50, footnote 46 at line 59, footnote 47 at line 61, footnote 48 at line 63, footnote 51 at line 72, footnote 52 at line 72, footnote 53 at line 72, footnote 57 at line 86, footnote 58 at line 87, footnote 74 at line 207 and footnote 36 at line 215.

4.2 The 7 citations graded Not supported are footnote 43 at line 54, footnote 53 at line 77, footnote 59 at line 93, footnote 65 at line 187, footnote 74 at line 196, footnote 75 at line 203 and footnote 54 at line 206.

4.3 The 26 citations graded Uncheckable are footnote 3 at line 12, footnote 6 at line 14, footnote 7 at line 15, footnote 8 at line 16, footnote 9 at line 16, footnote 21 at line 29, footnote 24 at line 29, footnote 26 at line 33, footnote 27 at line 33, footnote 35 at line 41, footnote 37 at line 47, footnote 44 at line 54, footnote 50 at line 64, footnote 60 at line 101, footnote 61 at line 110, footnote 62 at line 110, footnote 62 at line 111, footnote 63 at line 113, footnote 64 at line 171, footnote 66 in the table, footnote 67 in the table, footnote 68 in the table, footnote 70 in the table, footnote 71 in the table, footnote 72 in the table and footnote 73 in the table. The 4 citations graded Unread are footnote 11 at line 20, footnote 15 at line 21, footnote 15 at line 22 and footnote 69 in the table, whose copies at the Internet Archive are lending-only.

4.4 The 35 citations graded Partial are footnote 1 at line 5, footnote 1 at line 75, footnote 2 at line 5, footnote 2 at line 75, footnote 4 at line 12, footnote 5 at line 14, footnote 10 at line 17, footnote 12 at line 20, footnote 13 at line 21, footnote 14 at line 21, footnote 16 at line 23, footnote 17 at line 24, footnote 18 at line 25, footnote 19 at line 26, footnote 20 at line 27, footnote 22 at line 29, footnote 23 at line 29, footnote 25 at line 30, footnote 28 at line 33, footnote 29 at line 35, footnote 30 at line 37, footnote 31 at line 37, footnote 32 at line 37, footnote 33 at line 37, footnote 34 at line 39, footnote 19 at line 44, footnote 38 at line 48, footnote 39 at line 48, footnote 40 at line 48, footnote 45 at line 58, footnote 49 at line 63, footnote 54 at line 73, footnote 55 at line 73, footnote 56 at line 78 and footnote 76 at line 223, and units 1.1 through 1.53 state for each which part of the sentence its source carries.

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.