HISTORY.com “The Invention of the Internet”: Disagreements | Network, Not Protocol

Research Networks, Protocol Development, the Web, and Commercial Access

Preamble. I examine eight disputed claims or attribution gaps in the supplied copy of HISTORY.com’s The Invention of the Internet. The disagreements identify the relevant system and event before assigning credit or failure. Defense sponsorship, packet-switching design, host operation, protocol development, worldwide service, Web invention, browser development, and commercial access each require evidence of the work actually performed. Every disagreement below states what the source says, what the dated documents establish, and the consequence for the historical record. This page is Disagreement 12 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 12, 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 Source and Scope

0.1 Source. The examined article is credited to HISTORY.com Editors and published by A&E Television Networks. Its stated publication date is June 11, 2024, and its stated update date is May 28, 2025. The citation panel in the supplied copy records access on October 29, 2026. HISTORY identifies an editorial team but does not assign an individual author to each disputed sentence. The individual authors of those sentences are unknown to this record. HISTORY.com article.

0.2 Passage references. Exhibit A retains the supplied text and its 45 numbered article-body sentence units. Headings, advertisements, promotional material, and the separate fact box are excluded from that numbering. The source links below identify the complete passages on this published page. Yellow identifies the disputed claim in an expressly labeled paraphrase; the complete source wording remains in Exhibit A.

0.3 Network definitions and their application. This page applies the following definitions from The Governing Definitions, D1 through D3. A source’s historical use of a term and this site’s classification of the system must both remain visible.

Term Definition used here Application to this article
The Internet, D1 The publicly joinable network of networks in the InterNIC-to-ARIN registry lineage. People can buy lawful access from competing providers, and independent networks can interconnect by agreement with willing networks without admission approval from a central owner or government sponsor. A claim about establishing this public system needs evidence of service availability and interconnection terms. A research-network installation or protocol publication does not, by itself, establish those admission conditions.
Intranet, D2 A network whose owner controls admission. Size, geography, and protocol choice do not determine whether admission is public. Defense sponsorship and international reach do not establish public admission. The access rules of the particular network must be examined.
Internetworking, D3 Communication between distinct networks through gateways so traffic from one can reach hosts on another. Connecting separate research networks establishes internetworking. An exchange between two hosts on ARPANET establishes communication within that network. Neither event alone establishes D1’s public-admission conditions.

0.4 Protocol, Web, and performance boundaries. Under D6, a protocol is a specified method of communication implemented by equipment and software. TCP’s endpoint transport functions and IP’s datagram functions must be identified separately from the facilities carrying their traffic. Under D8, the Web is a linked information system implemented through clients, servers, and retrieval methods. The Internet is the underlying network service used by that system. Under D10, Modern Internet names this site’s further distinction between best-effort service and engineered delivery against specified performance conditions. Public access, Web availability, and a specified delivery commitment are separate claims. Governing Definitions, D6, D8, and D10.

0.5 Finding standard. An unsupported origin story, an omitted contributor, a host failure, a misidentified application, and an incomplete policy explanation require different corrections. HISTORY’s opening rejects a single inventor. The findings below address the later passages as written and identify the particular contribution, component, or causal inference in dispute.

1.0 Disagreements

Disagreement Subject Finding
1.1 Defense sponsorship and nuclear survivability A funding context does not establish the specific telephone-backup mission or an attack-survival guarantee.
1.2 Packet-switching attribution Davies’s documented work belongs beside Baran’s independently developed message-block design.
1.3 The October 1969 login attempt The receiving host’s software failed; successful character echo and whole-network failure are different events.
1.4 TCP/IP authorship and chronology The records identify multiple contributors and a separation of previously combined functions.
1.5 Worldwide network operation A protocol contribution does not document the construction and operation of all facilities carrying it.
1.6 Web invention A linked information system and its underlying network are different systems.
1.7 Mosaic and Netscape Personnel continuity does not make separate browser projects the same product.
1.8 NSF authority and commercialization Conditional agency authority, backbone policy, commercial interconnection, and Web adoption require separate evidence.

1.1 Disagreement. The telephone-backup origin story requires evidence of the stated mission

Source. Lead and The Birth of the ARPAnet, sentence 3, sentences 15 and 16, and sentence 20.

Disputed claim, paraphrased. Licklider’s network proposal would preserve leadership communications after telephone-system destruction, and packet switching would reduce ARPANET’s attack vulnerability.

Finding. The article combines a documented defense setting with a specific mission and a survivability comparison that the cited record does not establish.

Disagreement. J. C. R. Licklider’s April 23, 1963 memorandum discusses shared computing resources and conventions among research groups. Frank Heart, Alex McKenzie, John McQuillan, and David Walden’s ARPANET completion report, prepared January 4, 1978 and reproduced with an April 1981 cover, describes computer interconnection and resource sharing on printed page II-2. Neither document substantiates the article’s specific telephone-backup explanation. The 1963 memorandum also cannot, by itself, prove what was or was not discussed in 1962. Licklider memorandum · BBN completion report.

Defense rationale and operating capability. Stephen J. Lukasik’s 2011 first-person account explicitly describes military command and nuclear-threat motivations. Those motivations belong in the record. Paul Baran’s 1964 distributed-communications design separately examines surviving stations, connectivity, and routing. These sources support distinguishing the funding rationale from a demonstrated capability to survive a specified attack. Packet division does not establish that usable links, equipment, power, and alternate paths remain available. Lukasik, 2011 · Baran, RM-3420-PR, 1964.

Corrected statement. ARPA sponsored research into computer interconnection and resource sharing within a defense program. Claims about a telephone-backup mission or survival of a particular attack require evidence identifying that mission and the facilities and operating conditions needed to sustain it.

Consequence for the Historical Record. Record defense sponsorship, research objectives, proposed military uses, and demonstrated survivability separately. A funding rationale does not establish an undocumented operational guarantee.

1.2 Disagreement. Packet-switching history includes independently developed contributions

Source. The Birth of the ARPAnet, sentence 17.

Disputed presentation, paraphrased. The article presents Davies’s work as its entire account of packet-switching development and omits Baran’s independent message-block design.

Finding. Incomplete attribution. The article’s recognition of Davies is supported. The disagreement concerns missing parallel work rather than a sole-inventor claim that the sentence does not make.

Disagreement. Paul Baran’s 1964 RAND memorandum describes standardized message blocks and adaptive store-and-forward routing in distributed networks. Donald W. Davies’s June 1966 NPL proposal describes a digital communications network using packets, interfaces, queues, and error control. These are separate authored records of related developments. The article’s 1965 date for Davies is not the disputed point here. Baran, 1964 · Davies, June 1966.

Corrected statement. Davies developed his packet-switching proposal at NPL. Baran independently developed and published a distributed-communications design using message blocks at RAND. A history of the technique should identify both contributions and distinguish their designs from later implementations.

Consequence for the Historical Record. Restore the omitted independent work while retaining Davies’s contribution. Assign each design and implementation to its documented authors and date.

1.3 Disagreement. The 1969 login failure was in SRI’s receiving host software

Source. LOGIN, sentences 21 through 23.

Disputed claim, paraphrased. The destination is identified simply as Stanford, only two letters are said to have arrived, and the failed login is described as a crash of ARPANET.

Finding. The institution, evidence of receipt, and failed component need correction.

Disagreement. Charley Kline and Bill Duvall’s 2009 interview with Marc Weber, reproduced in the Computer History Museum’s CORE 2019, printed page 56, describes communication from UCLA’s Sigma 7 to Stanford Research Institute’s SDS 940 in Menlo Park. Kline received echoes of L and O. Processing G triggered a bug in the receiving system. Duvall describes changing the buffer size, rebuilding the operating system, and rebooting the host. Those observations identify a host-software failure. They do not establish a crash of the IMP communications subnet. Kline and Duvall interview, printed p. 56.

Why the distinction matters. The two successfully echoed characters establish an observed return exchange. The account of processing G gives evidence beyond those two echoes, so an echo count must not be substituted for a literal count of all characters received. SRI’s institutional history records independence in 1970. Calling the 1969 destination Stanford Research Institute is more precise while preserving its affiliation with Stanford at that time. SRI institutional history, individual author and publication date unknown.

Corrected statement. On October 29, 1969, Kline attempted a login from UCLA to the SDS 940 at Stanford Research Institute. L and O were echoed successfully before processing G triggered a receiving-host software bug. Duvall repaired and rebooted that host before a successful attempt.

Consequence for the Historical Record. Assign the failure to the receiving host software identified by the participants. Network transport, host processing, returned character echo, and completed login are distinct events.

1.4 Disagreement. TCP/IP development was collaborative and separated previously combined functions

Source. The Network Grows, sentences 27 through 30.

Disputed claim, paraphrased. TCP is presented as Cerf’s individual invention, followed by his personal addition of IP.

Finding. The account compresses multiple authors and an architectural separation into one individual’s sequence of inventions.

Disagreement. Vinton G. Cerf and Robert E. Kahn jointly authored the May 1974 paper. Vinton Cerf, Yogen Dalal, and Carl Sunshine authored RFC 675 in December 1974. Their paper and specification record different contributions and authorship. The early transmission-control design combined endpoint and internetwork functions. Cerf and Kahn, May 1974 · Cerf, Dalal, and Sunshine, RFC 675.

The documented design transition. Jon Postel’s IEN 2 of August 15, 1977 proposes separating endpoint conversation control from internetwork packaging and relaying. The IEN index lists Postel’s separate TCP and Internet Protocol version 4 specifications as IEN 40 and IEN 41 in June 1978. This record identifies a separation of functions through continuing development, not merely another protocol appended to an unchanged personal invention. Postel, IEN 2 · IEN 40 and IEN 41 index entries.

Corrected statement. Cerf and Kahn published an internetwork protocol design in May 1974. Cerf, Dalal, and Sunshine published the transmission-control specification that December. Subsequent collaborative work separated endpoint transport control into TCP and datagram handling and forwarding into IP.

Consequence for the Historical Record. Preserve the named contributors and design stages. Authorship of a protocol document establishes a contribution to that design; it does not assign construction of every participating network to its authors.

1.5 Disagreement. Worldwide service required deployed networks as well as implemented protocols

Source. The World Wide Web, sentence 32.

Disputed claim, paraphrased. Worldwide network reach is attributed to Cerf’s protocol, with deployment and operations left unexplained.

Finding. The causal explanation is incomplete and its attribution is too compressed.

Disagreement. Jon Postel’s RFC 801 of November 1981 describes an already operating ARPANET, the wider ARPA Internet, protocol implementations, application services, and a planned January 1983 transition. Its account separates the existing networks from the work of changing their selected host protocols. Interoperability required running implementations. Geographic reach required usable paths, connected equipment, routing, and sustained operations. Postel, RFC 801.

How the definitions apply. Under D3, functioning gateways and paths establish communication across networks. Under D1, public service availability and interconnection terms establish the additional public-admission condition. Under D10, a specified performance commitment requires evidence of the engineered service delivering it. A protocol design can contribute to the first operation while its authorship alone establishes neither the later admission terms nor the installed facilities and service commitments.

Corrected statement. Collaborative TCP/IP development and deployment contributed to communication among networks that implemented it. Worldwide reach also required the construction, interconnection, and operation of networks and facilities. Credit for protocol design and credit for those operating accomplishments must identify their respective participants and evidence.

Consequence for the Historical Record. Separate protocol development, deployment, geographic reach, public admission, and service performance. Explain which work produced each result instead of assigning the entire operating system to a protocol attribution.

1.6 Disagreement. Berners-Lee’s documented work is three programs of CERN’s Web software and the first specifications, and the World Wide Web is a label for the work of many

Source. The World Wide Web, sentences 35 and 36.

Disputed identification, paraphrased. The World Wide Web is described as an internet, and Web invention is carried over into a claim that Berners-Lee created today’s Internet.

Finding. The passage conflates a linked information system with the networks that carry it.

Disagreement. Tim Berners-Lee’s March 1989 proposal concerns distributed hypertext. His November 12, 1990 proposal with Robert Cailliau describes clients, servers, and use of existing computing resources. Berners-Lee’s August 6, 1991 announcement describes prototype browsers and retrieval using existing networking and protocols. These documents establish Web proposal and implementation milestones. Berners-Lee, March 1989 · Berners-Lee and Cailliau, November 12, 1990 · Berners-Lee, August 6, 1991.

How D1 and D8 apply. Under D8, the World Wide Web application design is the linked information system that browsers and servers provide, made by many persons inside and outside CERN. Under D1, the Internet is the underlying network of networks with public admission. Software for linking and retrieving information does not supply evidence that its author constructed the underlying network. Berners-Lee’s own explanation distinguishes the Web from the existing Internet. Berners-Lee’s FAQ, General questions 1998.

Corrected statement. Tim Berners-Lee started the WorldWideWeb project at CERN in 1989, led it, wrote its first application on the NeXT, and wrote the first specifications for URLs, HTTP and HTML, and the World Wide Web application design, a linked information system that the existing networks carry, was made by many persons and bodies inside and outside CERN, as the project's own list of contributors of November 3, 1992 records. Its 1989 proposal, 1990 implementation, and 1991 public announcement are milestones of that work. The influence of the World Wide Web application design on Internet use is a separate subject from creation of the underlying network.

Consequence for the Historical Record. Credit Berners-Lee’s documented work at the scope the documents establish, and credit the World Wide Web application design to the many persons and bodies who made it. Keep network construction and public interconnection attribution attached to evidence of those activities.

1.7 Disagreement. Mosaic and Netscape were separate browser projects

Source. The World Wide Web, sentences 37 and 38.

Disputed identification, paraphrased. NCSA Mosaic is presented as the same browser that later became Netscape.

Finding. Personnel and business continuity are substituted for product identity.

Disagreement. Marc Andreessen’s October 13, 1994 announcement introduces Mosaic Netscape 0.9 Beta from Mosaic Communications Corporation as a separately built browser. That contemporary release account distinguishes the new software from NCSA Mosaic. Participation by former Mosaic developers does not make the two projects identical. Andreessen, October 13, 1994.

Date distinction. Sharita Forrest’s University of Illinois account, dated April 17, 2003, places Mosaic prototype development in 1992 and its public debut in 1993. Development and public release are different milestones, so the 1993 release does not contradict a 1992 development date. Forrest, University of Illinois, April 17, 2003.

Corrected statement. NCSA Mosaic development began in 1992, followed by public releases in 1993. Some developers later worked on the separately developed Netscape browser. Personnel continuity should be described without turning one browser project into a renamed version of the other.

Consequence for the Historical Record. Distinguish project identity, developers’ employment, company names, and release dates. Preserve continuity where documented without inventing product identity.

1.8 Disagreement. The 1992 NSF authority had conditions and did not establish the start of commercial networking

Source. The World Wide Web, sentences 40 and 41.

Disputed explanation, paraphrased. A broad description of Congress authorizing connections to commercial networks is used as the direct explanation for companies’ Web adoption and online selling.

Finding. The statutory conditions are omitted, and the causal claim needs evidence of the events it connects.

What Congress authorized. Congress enacted the conditional NSF access provision in Public Law 102-476, section 4, on October 23, 1992, at 106 Stat. 2300. Public Law 102-588, section 217, enacted the same wording on November 4, 1992, at 106 Stat. 5117. It authorized NSF to support research and education access to networks substantially used for additional purposes when those additional uses tended to improve the networks’ ability to support research and education. That condition is part of the authorization and must appear in its description. 102d Congress, October 23 enactment · 102d Congress, November 4 enactment.

What the earlier commercial record establishes. General Atomics, Performance Systems International, and UUNET’s joint March 25, 1991 CIX announcement records commercial exchange terms for CERFnet, PSINet, and AlterNet customers outside government-restricted backbones. Its 60-day expectation appears in the sentence about Network Operations Center support; it is not a verified first-traffic date. Mark Fedor’s October 1991 CIX-WEST report supplies traffic measurements among those providers. The agreement and the operating report establish different milestones, both preceding the 1992 provisions. The announcement’s individual writer is unknown. Joint CIX announcement · Fedor, October 1991 report, pp. 14 and 15.

Policy and causation. The ACM SIGUCCS Networking Taskforce’s RFC 1359, August 1992, Appendix B, reproduces an acceptable-use policy scoped to the NSFNET backbone. A backbone restriction and NSF’s statutory authority govern different things. Neither enactment, by itself, proves that this policy was revoked, that commercial internetworking began in 1992, or how much later Web and commerce growth the enactment caused. RFC 1359, Appendix B.

Corrected statement. In 1992, Congress authorized conditional NSF support for research and education access to networks with substantial additional uses. Commercial providers and commercial interconnection already existed. The statutes, backbone policies, browser releases, and operating services belong in a dated account of commercialization with evidence for any causal relationship claimed.

Consequence for the Historical Record. Keep agency authority, backbone policy, commercial exchange agreements, production traffic, Web adoption, and online commerce separate. Their sequence must be documented before one is presented as the cause or beginning of another.

2.0 The Functional and Attribution Record

2.1 Functions require their own operating evidence. This table describes the separated TCP/IP architecture. The early combined transmission-control program must be read against its own specification.

Function Equipment or participants Evidence needed for the historical claim
TCP connection and byte-stream control TCP endpoints Implementation and observed sequencing, acknowledgments, retransmission, flow control, and connection behavior.
IP datagram processing and forwarding IP hosts and forwarding routers Implemented datagram handling, forwarding, and usable routes.
Underlying carriage Installed links, carrier switches, and facilities Provisioned capacity, available paths, protection, and service performance.
Public service and network interconnection Providers and interconnected networks Service terms, admission conditions, agreements, and operating exchanges.
Web information services Browsers, servers, and application software Retrieval and presentation of linked information over available network service.

Jon Postel’s September 1981 specifications describe IP datagram processing and TCP endpoint service. An IP router performs IP forwarding; a carrier’s underlying switching fabric performs its selected carriage functions. These activities must be identified at their actual equipment and service boundaries. RFC 791 · RFC 793.

2.2 Architectural selection and scoped requirements. D6 treats protocols as selectable communication methods. A deployment can require the selected components for participation in that deployment. Jon Postel’s edited standards registers, RFC 1200 of April 1991 and RFC 2200 of June 1997, grade TCP Recommended and IP Required within their listed suite frameworks. Those grades concern implementation requirements within that framework. They do not assign authorship of the networks using it, and architectural optionality does not erase a selected protocol’s contribution to a deployment. RFC 1200 · RFC 2200 · Governing Definitions, D6.

2.3 Credit the documented role. Baran’s distributed message-block design, Davies’s NPL proposal, BBN’s communications subnet, the Cerf and Kahn paper, RFC 675’s three authors, Postel’s separation proposal, and Berners-Lee’s hypertext work are distinct contributions. Cailliau’s coauthorship of the November 1990 proposal establishes his role in that document. None of these attributions assigns another participant’s design, installation, or operating work by implication.

2.4 Public reach and performance. A protocol specification establishes proposed behavior. A release announcement establishes an announced software release. An exchange agreement establishes stated interconnection terms. Traffic measurements establish observed operation at the measured point and period. A service agreement establishes the parties’ commitments, while measurements are needed to establish performance delivered. Claims of worldwide capacity, public admission, or specified transaction performance must identify the corresponding evidence.

3.0 Supported Milestones and Evidentiary Limits

3.1 The source’s opening. HISTORY’s first two sentences reject a single inventor and describe development over time. The eight findings address particular claims or omissions later in the article. A correction must preserve that distinction between the article’s opening position and its later wording.

3.2 The 1972 ALOHA connection. Norman Abramson’s March 1985 paper records delivery and installation on December 17, 1972, of an IMP connecting the ALOHA system to ARPANET by satellite. This supports the 1972 connection milestone. The satellite link and ALOHA’s local radio packet-broadcasting operation are distinct parts of the system. Abramson, Development of the ALOHANET, printed p. 121.

3.3 Proposal, implementation, announcement, and operation. A proposal’s date does not automatically date an implementation. An announcement’s date does not automatically date first production traffic. A successfully transported character does not establish completed login or application processing. A later successful exchange does not identify or repair every cause of an earlier failure. Each conclusion must follow from evidence of the event it names.

3.4 Historical correction. Describe each network, protocol, application, policy, and operating service at its documented scope. Attribute the design to its authors, the implementation to its developers, and construction and operation to the participants who performed those tasks. Explain a causal link with evidence of the connected events rather than letting adjacency in a narrative supply the connection.

4.0 Exhibits

4.1 Exhibit A. Supplied HISTORY.com text. Keep the existing source block below. It preserves the supplied plain-text copy, including its byline, dates, citation information, copyright notice, navigation, advertisements, and promotional material. Sentence numbers, anchors, and yellow highlights are editorial additions. The supplied citation panel records access on October 29, 2026. This is a text exhibit, not a capture of the publisher’s original layout. Promotional material remains source content, and the publisher’s copyright notice remains attached to it.

Skip to main content HomeShowsThis Day in HistoryVideos U.S. World Eras & Ages Culture Science & Innovation Halloween Haunted History Stream HISTORY TryHISTORY Vault Advertisement Inventions & Science The Invention of the Internet HISTORY.com Editors Silas Stein/picture alliance via Getty Images Published: June 11, 2024 Last Updated: May 28, 2025 TABLE OF CONTENTS 1 The Sputnik Scare 2 The Birth of the ARPAnet 3 'LOGIN' 4 The Network Grows 5 The World Wide Web [1] Unlike technologies such as the phonograph or the safety pin, the internet has no single “inventor.” [2] Instead, it has evolved over time. [3] The internet got its start in the United States in the late 1960s as a military defense system in the Cold War. [4] For years, scientists and researchers used it to communicate and share data with one another. [5] Today, we use the internet for almost everything, and for many people it would be impossible to imagine life without it. The Sputnik Scare [6] On October 4, 1957, the Soviet Union launched the world’s first artificial satellite into orbit. [7] The satellite, known as Sputnik, did not do much: It relayed blips and bleeps from its radio transmitters as it circled the Earth. [8] Still, to many Americans, the beach ball-sized Sputnik was proof of something alarming: While the U.S. economy was booming and its consumer technologies were advancing, the Soviets had been focusing on training scientists—and were positioned to win the Space Race, and possibly the Cold War, because of it. Did you know? Nearly two-thirds of the world’s 8 billion people used the internet in 2023. [9] After Sputnik’s launch, many Americans began to think more seriously about science and technology. [10] Schools added courses on subjects like chemistry, physics and calculus. [11] Universities and corporations took government grants and invested them in scientific research and development. [12] And the federal government itself formed new agencies, such as the National Aeronautics and Space Administration (NASA) and the Department of Defense’s Advanced Research Projects Agency (ARPA), to develop space-age technologies such as rockets, weapons and computers. Advertisement How the Census Led to Modern Computing The census has been around since the beginning of the United States, which meant the entire population had to be counted by hand. Until one inventor saw a better way forward. 1:00m watch The Birth of the ARPAnet [13] Scientists and military experts were especially concerned about what might happen in the event of a Soviet attack on the nation’s telephone system. [14] Just one missile, they feared, could destroy the whole network of lines and wires that made efficient long-distance communication possible. [15] In 1962, a scientist from ARPA named J.C.R. Licklider proposed a solution to this problem: a “intergalactic network” of computers that could talk to one another. [16] Such a network would enable government leaders to communicate even if the Soviets destroyed the telephone system. [17] In 1965, Donald Davies, a scientist at Britain’s National Physical Laboratory developed a way of sending information from one computer to another that he called “packet switching.” [18] Packet switching breaks data down into blocks, or packets, before sending it to its destination. [19] That way, each packet can take its own route from place to place. [20] Without packet switching, the government’s computer network—now known as the Arpanet—would have been just as vulnerable to enemy attacks as the phone system. 'LOGIN' [21] On October 29, 1969, Arpanet delivered its first message: a “node-to-node” communication from one computer to another. [22] (The first computer was located in a research lab at UCLA and the second was at Stanford; each one was the size of a large room.) [23] The message—“LOGIN”—was short and simple, but it crashed the fledgling Arpanet anyway: The Stanford computer only received the note’s first two letters. The Network Grows [24] By the end of 1969, just four computers were connected to the Arpanet, but the network grew steadily during the 1970s. [25] In 1972, it added the University of Hawaii’s ALOHAnet, and a year later it added networks at London’s University College and the Norwegian Seismic Array. [26] As packet-switched computer networks multiplied, however, it became more difficult for them to integrate into a single worldwide “internet.” [27] By the mid-1970s, a computer scientist named Vinton Cerf had begun to solve this problem by developing a way for all of the computers on all of the world’s mini-networks to communicate with one another. [28] He called his invention “Transmission Control Protocol,” or TCP. [29] (Later, he added an additional protocol, known as “Internet Protocol.” [30] The acronym we use to refer to these today is TCP/IP.) [31] One writer describes Cerf’s protocol as “the ‘handshake’ that introduces distant and different computers to each other in a virtual space.” Advertisement The World Wide Web [32] Cerf’s protocol transformed the internet into a worldwide network. [33] Throughout the 1980s, researchers and scientists used it to send files and data from one computer to another. [34] However, in 1991 the internet changed again. [35] That year, a computer programmer working at the CERN research center on the Swiss-French border named Tim Berners-Lee introduced the World Wide Web: an internet that was not simply a way to send files from one place to another but was itself a “web” of linked information that anyone on the Internet could retrieve. [36] Berners-Lee created the Internet that we know today. [37] In 1992, a group of students and researchers at the University of Illinois developed a sophisticated browser that they called Mosaic. [38] (It later became Netscape.) [39] Mosaic offered a user-friendly way to search the Web: It allowed users to see words and pictures on the same page for the first time and to navigate using scrollbars and clickable links. [40] That same year, Congress authorized the National Science Foundation to connect the country’s research- and education-focused internet services to commercial networks. [41] As a result, companies of all kinds hurried to set up websites of their own, and e-commerce entrepreneurs began to use the internet to sell goods directly to customers. [42] By the 2000s, companies including Amazon and eBay emerged as dominant players in the online retail space. [43] In the first decade of the 2000s, social media platforms such as Facebook, Twitter and Instagram emerged, changing the way people connected, created and shared content. [44] By around 2015, more people accessed the internet from smartphones than from other kinds of computers. [45] By the early 2020s, companies, including OpenAI, Google, Microsoft and others starting rolling out advanced artificial intelligence systems to the public. Advertisement RELATED STORIES Inventions & Science Who Invented Television? Multiple inventors deserve credit for the technology, which had its origins in the 19th century. Inventions & Science 5 Inventions Influenced by ‘Star Trek’ These inventions boldly go where “Star Trek” went before. Take a closer look at the inventions that have transformed our lives far beyond our homes (the steam engine), our planet (the telescope), and our wildest dreams (the Internet). 7-DAY FREE TRIAL Commercial-free, Cancel anytime 101 Inventions That Changed the World Exclusions & terms apply RELATED Inventions & Science 97 videos Inventions & Science How an Anonymous Parisian Became the First Person Ever Photographed An 1838 photo that accidentally captured a man getting a shoe shine on a Paris street was almost lost to history. Twice. Inventions & Science Why Coca-Cola’s ‘New Coke’ Flopped Coca-Cola’s disastrous attempt at rebranding Coke in 1985 delivered a painful lesson: Don't mess with a classic. Inventions & Science Who Invented Television? Multiple inventors deserve credit for the technology, which had its origins in the 19th century. See More ABOUT THE AUTHOR HISTORY.com Editors HISTORY.com works with a wide range of writers and editors to create accurate and informative content. All articles are regularly reviewed and updated by the HISTORY.com team. Articles with the “HISTORY.com Editors” byline have been written or edited by the HISTORY.com editors, including Amanda Onion, Christian Zapata, Cristiana Lombardo and Adrienne Donica. FACT CHECK We strive for accuracy and fairness. But if you see something that doesn't look right, click here to contact us! HISTORY reviews and updates its content regularly to ensure it is complete and accurate. CITATION INFORMATION Article Title The Invention of the Internet Author HISTORY.com Editors Website Name History URL https://www.history.com/articles/invention-of-the-internet Date Accessed October 29, 2026 Publisher A&E Television Networks Last Updated May 28, 2025 Original Published Date June 11, 2024 Around the Web The Supportive Bra Women Over 50 Are Loving The Supportive Bra Women Over 50 Are Loving imgainting Electricians: The Mistake That Doubles Your Electricity Bill Electricians: The Mistake That Doubles Your Electricity Bill Gadgethome Protein Isn't Enough - Here's What Really Builds Muscle After 60 Protein Isn't Enough - Here's What Really Builds Muscle After 60 ApexLabs Give Your Senior Dog a Spoon of Honey Tonight, Here’s What Happens Give Your Senior Dog a Spoon of Honey Tonight, Here’s What Happens Pets Daily Health Feet Keeping You Up at Night? Take a Look at This Simple Drawing Feet Keeping You Up at Night? Take a Look at This Simple Drawing The Nerve Health Report Flip This One Switch Before Bed. Your Next Power Bill Could Be Shockingly Lower Flip This One Switch Before Bed. Your Next Power Bill Could Be Shockingly Lower Daily Hack Digest Surgeons: This Simple Trick Will End Knee Pain & Arthritis Quickly (Try It) Surgeons: This Simple Trick Will End Knee Pain & Arthritis Quickly (Try It) Health Weekly Seniors Born 1939-1969 Get 11 Benefits This Month (If They Ask) Seniors Born 1939-1969 Get 11 Benefits This Month (If They Ask) Plentyside & Seniors This Stunning Stained Glass Hummingbird Lamp is Being Snapped Up in California This Stunning Stained Glass Hummingbird Lamp is Being Snapped Up in California Peoasis Revcontent Advertisement A+E Global Media History HISTORY Education HISTORY Vault™ HISTORY Apps HISTORY en Español® Military HISTORY® Newsletter Sign Up Share Your Opinions FAQ / Contact Us A&E Lifetime LMN FYI VICE TV Biography Crime+Investigation LRW Advertise with Us A+E Factual Studios™ A+E Studios® Employment Opportunities Accessibility Support TV Parental Guidelines © 2026, A&E Television Networks, LLC. All Rights Reserved. Terms of Use Privacy Policy Copyright Policy Cookie Notice Ad Choices Legal Terms and Privacy By clicking "Accept & Close", you have read and agree to our Terms of Use and agree to the collection and use of your information by cookies and similar technologies, as set forth in our Privacy Policy. Accept & Close

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

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

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

D11.1 Definitions govern meaning. Documents govern facts. Findings govern conclusions.

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.