Wikipedia WorldWideWeb: Disagreements | Network, Not Protocol

Wikipedia’s article WorldWideWeb says that the source code of the WorldWideWeb browser “was released into the public domain on 30 April 1993” and that Tim Berners-Lee “eventually opted to release it into the public domain”, while CERN’s statement of 30 April 1993, signed by W. Hoogland, Director of Research, and H. Weber, Director of Administration, put into the public domain three other programs, the W3 basic line-mode client, the W3 basic server and the W3 library of common code, and names neither the WorldWideWeb browser nor Tim Berners-Lee.

Preamble: I examine the Wikipedia article WorldWideWeb, the article on the browser and editor that Tim Berners-Lee wrote at CERN in 1990, line by line, against CERN's statement of 30 April 1993 releasing the CERN W3 software into the public domain, against Tim Berners-Lee's own announcement of that statement of May 7, 1993, and against the Governing Definitions of marknichols.com. Exhibit A at section 5.0 reproduces the article line by line, numbered and anchored, and every finding on this page cites those line numbers. This page is Disagreement 99 in the standing index of the series, Disagreements of Published Claims | Network, Not Protocol, and a finding on this page is cited by that number followed by the finding's locus, as Disagreement 99, 1.1.

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

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

0.0 This section records the article this page examines, the documents it is read against, and the definitions on which the findings depend.

0.1 The source examined on this page is the article WorldWideWeb of the English Wikipedia at https://en.wikipedia.org/wiki/WorldWideWeb. Mark Nichols supplied the text of the article as it read on November 14, 2026, and this page read the supplied text in full on November 14, 2026 and did not compare it with the live page. The supplied text does not carry the number of its revision, and the revision number is unknown on this page. The article names no author, and its authors are the editors of Wikipedia, whose names are unknown on this page.

0.2 CERN's statement of 30 April 1993 is CERN's statement concerning the release of the CERN W3 software into the public domain, two pages, page 1 and page 2, held on marknichols.com as L-028 of Exhibit Library | Network, Not Protocol, which this page read in full on November 14, 2026. Tim Berners-Lee's announcement of the statement is “PUBLIC DOMAIN CERN WWW SOFTWARE,” sent to the mailing lists www-talk and www-announce on May 7, 1993, as 1.3 and 2.2 of The Guardian, Why I Gave the World Wide Web Away for Free: Disagreements | Network, Not Protocol, Disagreement 75, record it, and this page relies on that record of it.

0.3 Exhibit A reproduces the article from its title through its list of references, without the menus of the site, its external links and its navigation boxes, and divides it into 67 lines: each notice, line of the infobox, heading, item of a list and reference is a line of its own, each paragraph is divided into its sentences, and the label and value of an infobox line are separated by a vertical bar. D8 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking defines the World Wide Web as “An application design made by many persons inside and outside CERN”. The Definitions Addendum at section 6.0 reproduces D1 through D13 in full.

1.0 The article says that the source code of the WorldWideWeb browser was released into the public domain on 30 April 1993 and gives the browser the license “Public-domain software”, while CERN’s statement of that date lists three other programs, the W3 basic line-mode client, the W3 basic server and the W3 library of common code, and states that it “does not constitute a precedent to be applied to any other CERN copyright software.”

1.1 Line 21 says: “The source code was released into the public domain on 30 April 1993.[2][4]” Line 32 says: “On 30 April 1993, the CERN directorate released the source code of WorldWideWeb into the public domain.” Line 14, in the infobox, reads: “License | Public-domain software[2]” Line 55, the reference that line 21 and line 14 cite as their citation 2, reads: “"The document that officially put the World Wide Web into the public domain on 30 April 1993". CERN. 1993. Retrieved 26 September 2013.”

1.2 CERN's statement concerning the release of the CERN W3 software into the public domain, headed “STATEMENT CONCERNING CERN W3 SOFTWARE RELEASE INTO PUBLIC DOMAIN” and dated Geneva, 30 April 1993, states on page 2: “The following CERN software is hereby put into the public domain:”, and lists “W 3 basic ("line-mode") client”, “W 3 basic server” and “W 3 library of common code.” It continues: “This does not constitute a precedent to be applied to any other CERN copyright software.”

1.3 Tim Berners-Lee's announcement of May 7, 1993 says, as 1.3 of The Guardian, Why I Gave the World Wide Web Away for Free: Disagreements | Network, Not Protocol records it, that the declaration covers the “libwww” common code library, “the line mode browser (www) and the W3 server (httpd),” and that “The declaration, signed on 30 April 1993, makes it clear that this is not a precedent for CERN software.” The article's own line 23 says that the WorldWideWeb browser was written “on a NeXT Computer”, and its own line 26 names “the Line Mode Browser” as a separate program, written later by Nicola Pellow.

1.4 The kind is a documentary finding. The statement of 30 April 1993 names three programs, and the WorldWideWeb browser for the NeXT computer is not one of them, as the statement and the announcement of May 7, 1993 both list them, so the words of lines 21 and 32 and the infobox license at line 14 give to the WorldWideWeb browser a release that CERN made for three other programs, and the statement's own words say that it is not a precedent for any other CERN copyright software.

1.5 Corrected statement: On 30 April 1993, CERN put three programs of its W3 software, the basic line-mode client, the basic server and the library of common code, into the public domain by a statement signed by W. Hoogland, Director of Research, and H. Weber, Director of Administration, and the statement does not name the WorldWideWeb browser that Tim Berners-Lee wrote on a NeXT computer in 1990.

2.0 The article says that Tim Berners-Lee “eventually opted to release it into the public domain”, while the release of 30 April 1993 is an act of CERN signed by two of its directors, its two pages name Tim Berners-Lee nowhere, and the programs it released do not include the WorldWideWeb browser.

2.1 Line 34 says: “Berners-Lee initially considered releasing it under the GNU General Public License, but after hearing rumors that companies might balk at the concept if any licensing issues were involved, he eventually opted to release it into the public domain.[12]”

2.2 CERN's statement concerning the release of the CERN W3 software into the public domain is signed by “W. Hoogland, Director of Research” and “H. Weber, Director of Administration”, and its two pages name Tim Berners-Lee nowhere. Tim Berners-Lee's announcement of May 7, 1993 says that the declaration “has been signed by H. Weber, CERN's Director for Administration and W. Hoogland, Director for Computing,” as 1.3 of The Guardian, Why I Gave the World Wide Web Away for Free: Disagreements | Network, Not Protocol records it, and that paragraph records that the announcement does not name Tim Berners-Lee as a signer.

2.3 The kind is a documentary finding. The choice of the public domain was made in an instrument of CERN signed by its Director of Research and its Director of Administration, and the word “it” at line 34 refers to the WorldWideWeb browser, which that instrument does not name, so the line gives to Tim Berners-Lee an act of release that the documents record as CERN's and for programs other than the one the article describes. 2.6 of The Guardian, Why I Gave the World Wide Web Away for Free: Disagreements | Network, Not Protocol records that Tim Berners-Lee convinced his managers at CERN to put the three programs in the public domain.

2.4 Corrected statement: Tim Berners-Lee convinced his managers at CERN to put three programs of CERN's W3 software in the public domain, and on 30 April 1993 W. Hoogland, Director of Research of CERN, and H. Weber, Director of Administration of CERN, signed the statement that did so, which names neither Tim Berners-Lee nor the WorldWideWeb browser.

3.0 62 lines of the article are examined and not disputed on this page, and several of them keep the software apart from the World Wide Web and name the team that worked on it.

3.1 Line 4 and line 18 keep the browser apart from the World Wide Web, and line 28 says that the browser was renamed Nexus Browser in 1994 “in order to differentiate between the software (WorldWideWeb) and the World Wide Web”, which agrees with D8. Line 40 says that the browser could use “FTP, HTTP, NNTP, and local files”.

3.2 Line 23 and line 6 give the browser to Tim Berners-Lee at CERN in the second half of 1990. Line 26 names Bernd Pollermann, Robert Cailliau, Jean-François Groff and Nicola Pellow as involved in the project by August 1991, and line 31 credits Tim Berners-Lee and Jean-François Groff with the libwww API, which agrees with D8's record of an application design made by many persons. Line 25 says that the browser became available to the general public in August 1991, which agrees with D8's date of August 6, 1991 for the public announcement of the World Wide Web, as 3.2 of Wikipedia World Wide Web: Disagreements | Network, Not Protocol records.

3.3 Line 35 records the auction of 2021 of an NFT of the WorldWideWeb source code, and this page does not test the line.

3.4 The remaining 52 lines, 1 through 3, 5, 7 through 13, 15 through 17, 19, 20, 22, 24, 27, 29, 30, 33, 36 through 39, 41 through 54 and 56 through 67, state the title, the notices, the infobox, the headings, the account of the browser's names and porting, its features, the list of related articles and the references, and this page makes no finding on them.

3.5 Tim Berners-Lee's own page about the browser, “The WorldWideWeb browser” at www.w3.org/People/Berners-Lee/WorldWideWeb.html, read in full on November 14, 2026, says that the program “was renamed Nexus in order to save confusion between the program and the abstract information space (which is now spelled World Wide Web with spaces)”. The page also says that he wrote the program “using a NeXT computer” and that “WorldWideWeb was written in Objective-C”. The page describes the program's menus, linking, style sheets and editing, and it says nothing about the program being released into the public domain.

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

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

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

5.0 Exhibit A reproduces the Wikipedia article WorldWideWeb line by line, numbered in the order of the page and anchored for citation.

5.1 Exhibit A. Wikipedia, WorldWideWeb, at https://en.wikipedia.org/wiki/WorldWideWeb, as supplied by Mark Nichols on November 14, 2026. Line 1 is the title, lines 2 through 4 are the notices, lines 5 through 17 are the infobox, lines 18 through 48 are the article, lines 49 through 52 are its list of related articles, and lines 53 through 67 are its heading of references and its references, in the order of the page.

1. WorldWideWeb

2. From Wikipedia, the free encyclopedia

3. This article is about the web browser.

4. For the distributed hypertext system, see World Wide Web.

5. WorldWideWeb

6. Developer | Tim Berners-Lee for CERN

7. Release | 25 December 1990; 35 years ago[1]

8. Final release

9. 0.17 Edit this on Wikidata / 1994; 32 years ago

10. Written in | Objective-C[1]

11. Operating system | NeXTSTEP[1]

12. Available in | English

13. Type | Web browser, Web authoring tool

14. License | Public-domain software[2]

15. Website | w3.org/People/Berners-Lee/WorldWideWeb.html

16. Repository

17. www.w3.org/History/1991-WWW-NeXT/Implementation/ Edit this at Wikidata

18. WorldWideWeb (later renamed Nexus to avoid confusion between the software and the World Wide Web) is the first web browser[1] and web page editor.[3]

19. It was discontinued in 1994.

20. It was the first WYSIWYG HTML editor.

21. The source code was released into the public domain on 30 April 1993.[2][4]

22. History

23. Tim Berners-Lee wrote what would become known as WorldWideWeb on a NeXT Computer[4] during the second half of 1990, while working for CERN, a European nuclear research agency.

24. The first edition was completed "some time before" 25 December 1990, according to Berners-Lee, after two months of development.[5]

25. The browser was announced on the newsgroups and became available to the general public in August 1991.[5][6]

26. By this time, several others, including Bernd Pollermann, Robert Cailliau, Jean-François Groff,[7] and visiting undergraduate student Nicola Pellow – who later wrote the Line Mode Browser – were involved in the project.[5]

27. Berners-Lee considered different names for his new application, including The Mine of Information and The Information Mesh, before publicly launching the WorldWideWeb browser in 1991.[8]

28. When a new version was released in 1994, it was renamed Nexus Browser, in order to differentiate between the software (WorldWideWeb) and the World Wide Web.[9]

29. The team created so called "passive browsers" which do not have the ability to edit because it was hard to port this feature from the NeXT system to other operating systems.

30. Porting to the X Window System was not possible as nobody on the team had experience with the X Window System.[3]

31. Berners-Lee and Groff later adapted many of WorldWideWeb's components into a C programming language version, creating the libwww API.[10]

32. On 30 April 1993, the CERN directorate released the source code of WorldWideWeb into the public domain.

33. Several versions of the software are still available on the web in various states.[11]

34. Berners-Lee initially considered releasing it under the GNU General Public License, but after hearing rumors that companies might balk at the concept if any licensing issues were involved, he eventually opted to release it into the public domain.[12]

35. In 2021, Sotheby's held an auction for an NFT of the WorldWideWeb source code.[13][14]

36. Features

37. Since WorldWideWeb was developed on and for the NeXTSTEP platform, the program uses many of NeXTSTEP's components – WorldWideWeb's layout engine was built around NeXTSTEP's Text class.[1]

38. WorldWideWeb is capable of displaying basic style sheets,[4] downloading and opening any file type with a MIME type that is also supported by the NeXT system (PostScript,[3][4] movies, and sounds[4]), browsing newsgroups, and spellchecking.

39. In earlier versions, images are displayed in separate windows, until NeXTSTEP's Text class gained support for Image objects.[4]

40. WorldWideWeb is able to use different protocols: FTP, HTTP, NNTP, and local files.

41. Later versions are able to display inline images.[1]

42. The browser is also a WYSIWYG editor.[1][3]

43. It allows the simultaneous editing and linking of many pages in different windows.

44. The functions "Mark Selection", which creates an anchor, and "Link to Marked", which makes the selected text an anchor linking to the last marked anchor, allow the creation of links.

45. Editing pages remotely is not possible, as the HTTP PUT method had not yet been implemented during the period of the application's active development.[1]

46. WorldWideWeb's navigation panel contains Next and Previous buttons that automatically navigate to the next or previous link on the last page visited, similar to Opera's Rewind and Fast Forward buttons, or HyperCard; i.e., if one navigated to a page from a table of links, the Previous button would cause the browser to load the previous page linked in the table.[1]

47. WorldWideWeb does not have bookmarks as they exist in later browsers, but a similar feature was provided: to save a link for later use, users could link to it from their own home page (start page).

48. Users could create multiple home pages, similar to folders in modern web browsers' bookmarks.[3]

49. See also

50. Free and open-source software portal

51. History of the World Wide Web

52. Wiki

53. References

54. Berners-Lee, Tim. "The WorldWideWeb browser". World Wide Web Consortium. Retrieved 23 July 2010.

55. "The document that officially put the World Wide Web into the public domain on 30 April 1993". CERN. 1993. Retrieved 26 September 2013.

56. Petrie, Charles; Cailliau, Robert (November 1997). "Interview Robert Cailliau on the WWW Proposal: "How It Really Happened."". Institute of Electrical and Electronics Engineers. Archived from the original on 6 January 2011. Retrieved 18 August 2010.

57. Berners-Lee, Tim. "Frequently asked questions – What were the first WWW browsers?". World Wide Web Consortium. Retrieved 22 July 2010.

58. Berners-Lee, Tim (1993). "A Brief History of the Web". World Wide Web Consortium. Retrieved 17 August 2010.

59. "A Little History of the World Wide Web". www.w3.org. Retrieved 2020-02-03.

60. Jean-François Groff. "NeXT editor upgrade proposal". World Wide Web Consortium. Retrieved 21 June 2010.

61. "Welcome to info.cern.ch". CERN. Retrieved 25 July 2010.

62. Boulton, Jim. "The Nexus Browser | Digital Archaeology". Retrieved 2021-06-15.

63. Stewart, Bill. "Web Browser History". Living Internet. Retrieved 2 June 2010.

64. "browsers.evolt.org". browsers.evolt.org.

65. "History of Libwww" (PDF). p. 3. Archived from the original (PDF) on 2009-09-16. Retrieved 2007-02-14.

66. "Source Code for the WWW | This Changed Everything: Source Code for WWW x Tim Berners-Lee, an NFT | 2021".

67. "Tim Berners-Lee sells web source code NFT for $5.4m". 30 June 2021.

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.