Marconi Society Vinton Cerf: Disagreements | Network, Not Protocol

The Marconi Society laureate page for Vinton Cerf widens the official rationale of the 1997 National Medal of Technology to “founding and developing,” leaves his ICANN chairmanship of November 2000 to November 2007 open-ended, applies the title “Fellow” to his membership of the National Academy of Engineering, and uses the honorific “Fathers of the Internet” without a defined historical scope.

Preamble. I examine the Marconi Society’s Vinton Cerf laureate page and record four disagreements. They concern the stated rationale for the 1997 National Medal of Technology, an open-ended ICANN chairmanship, the National Academy of Engineering’s membership designation, and the scope of a parental honorific. Each finding identifies the disputed wording, names the controlling evidence, explains its application, and states the consequence for the historical record. The Marconi Prize’s contribution citation is assessed separately. Source excerpts and the complete official medal citation appear in the bottom exhibits. This page is Disagreement 23 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 23, 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 Marconi Society laureate page that this page examines, the publisher of the page, the method and limits of the findings, and the Governing Definitions on which the findings depend.

0.1 Source and date. The source is the Marconi Society’s Cerf laureate page. Its heading names the 1998 prize; separately listed 2023 honors show later additions. No composition or update date is displayed for the biography. This review assesses the currently visible wording.

0.2 Authorship. The Marconi Society is the institutional publisher. No individual biographical writer is identified. Institutional publication and individual sentence authorship are different facts. The comparison documents have their own issuing bodies.

0.3 Method and limits. Findings 1.1 through 1.3 compare biography language with award and institutional records. Finding 1.4 challenges the scope of an origin label while preserving the documented design contribution. A shared-design claim is not a sole-inventor claim. The short excerpts identify the contested terms; their accompanying paraphrases state the complete claim examined. Read the original wording through the direct source links.

0.4 Definitions used here and the evidence they require. These are this site’s declared categories. They identify the scope of its historical disagreement. Dates, service terms, technical documents, and institutional records establish what actually occurred. Governing Definitions, D1 through D3 and D6.

Term Meaning in this record Application to this page
The Internet, D1 The publicly joinable network of networks in the InterNIC-to-ARIN registry lineage. People can buy 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 founding claim needs identified public services, interconnection terms, responsible organizations, and operating dates. Protocol authorship alone supplies none of those particulars.
Intranet, D2 A network whose owner controls admission. Its geographical reach and protocol selection do not determine whether participation is public. A restricted research deployment and a publicly joinable service have different admission conditions. Naming a protocol does not establish either condition.
Internetworking, D3 Connecting distinct networks through gateways so traffic from one can reach hosts on another. Cerf and Kahn’s gateway design is an architectural contribution to interconnection. Building and operating particular networks remain separately attributable activities.
Protocol scope, D6 This record treats TCP and IP as optional architectural selections. A selected deployment can require compatible implementations of its chosen protocols. Selection, implementation conformance, actual traffic use, and historical influence are different questions. The scoped RFC 1200 grades are stated in §2.2.

1.0 The Marconi Society laureate page for Vinton Cerf carries four disagreements, on the rationale of the 1997 National Medal of Technology, the term of his ICANN chairmanship, his designation at the National Academy of Engineering, and the scope of the honorific “Fathers of the Internet.”

1.1 Disagreement. The medal explanation expands the official award rationale

Finding: a broader institutional paraphrase.

Word contested, exact excerpt: founding. Marconi attributes the 1997 medal to Cerf and Kahn’s founding and development of the Internet. That is the first clause of a sentence continuing with a separate 2005 honor. MC-03.

Finding and disagreement. The White House’s December 16, 1997 record and the USPTO’s official recipient record identify development of Internet protocols and continuing industry leadership. The official wording includes development of Internet Protocols; its complete citation is GOV-01 below. Marconi’s sentence is an unquoted paraphrase, not a quotation falsely transcribed. The objection is that its founding attribution exceeds the narrower activities named in the government’s citation. White House, December 16, 1997 · USPTO, 1997 laureates.

How the evidence applies. Under D1, founding a publicly joinable network concerns service admission and operation. The official citation names protocol work and industry leadership. It does not identify a public-service opening, a network-construction project, or terms under which the public could join. The citation therefore does not establish the stronger founding claim by itself.

Corrected statement. President Clinton presented Cerf and Kahn with the National Medal of Technology in 1997 for creating and sustaining Internet protocol development and continuing leadership in the internetworking industry.

Consequence for the Historical Record. Preserve the recipients, award, year, and actual rationale. Identify Marconi’s broader wording as its own paraphrase. Do not circulate that paraphrase as the government’s exact citation or use it as independent proof of founding the whole operating service.

1.2 Disagreement. The displayed ICANN chairmanship is left open-ended

Finding: a stale description of an institutional role.

Word contested, exact excerpt: chaired. The biography describes the chairmanship as continuing from 2000 without an end date. MC-04.

Finding and disagreement. ICANN’s November 2, 2007 adopted resolutions identify November 2000 as the beginning of Cerf’s chairmanship. The same day’s succession announcement identifies Peter Dengate Thrush as the newly elected chair and Cerf as retiring. The current Marconi page contains later honors but leaves this appointment grammatically open-ended. The biography’s unknown composition date prevents a finding about when its wording first became stale. It does not prevent correcting the presently displayed tenure. ICANN adopted resolutions, November 2, 2007 · ICANN succession announcement, November 2, 2007.

Corrected statement. Cerf chaired ICANN’s board from November 2000 until November 2007. Peter Dengate Thrush succeeded him on November 2, 2007.

Consequence for the Historical Record. Trace institutional authority through actual terms of office. Continued display of an outdated biography cannot establish that an expired appointment continued or that the former officeholder exercised later authority in that role.

1.3 Disagreement. A collective fellowship title obscures the NAE membership designation

Finding: an imprecise institutional title.

Word contested, exact excerpt: Fellow. The biography applies a collective fellowship description across an institutional list that includes the National Academy of Engineering. MC-05.

Finding and disagreement. The NAE’s 2008 annual report explicitly identifies Cerf as a member. Its October 4, 2020 publication also includes him among anniversary members. These Academy records establish the designation relevant to this finding. A fellowship title used by another institution should not be carried across the list as though every institution uses the same category. NAE 2008 Annual Report, printed p. 14 · NAE membership publication, October 4, 2020, p. 20.

Corrected statement. Cerf is a member of the National Academy of Engineering. Fellowships at other institutions should be listed under each institution’s own official title.

Consequence for the Historical Record. Preserve the documented affiliation and its proper designation. This terminology correction does not negate Cerf’s Academy membership. A loose collective label does not make different institutional categories interchangeable.

1.4 Disagreement. The parental label needs a defined historical scope

Finding: a definitional and attribution-scope objection.

Word contested, exact excerpt: Fathers. Marconi reports the familiar parental honorific and credits Cerf, together with Kahn, with TCP/IP design and the Internet’s basic architecture. The sentence expressly describes shared design. MC-02.

Finding and disagreement. The dispute is with using the honorific as a literal or unrestricted origin attribution. Cerf and Kahn’s May 1974 paper contains architectural mechanisms for interconnection, including gateways, addressing, fragmentation, and host responsibilities. That work is documented. Its gateway architecture applies to D3’s interconnection of networks. It does not, by itself, establish who constructed every participating network, provisioned the facilities, opened public service under D1, or operated later commercial deployments. Vinton G. Cerf and Robert E. Kahn, May 1974, especially printed pp. 637 through 639.

How D1, D2, D3, and D6 apply. Protocol choice does not determine admission. A D2 restricted network can use the same protocols as a D1 publicly joinable service. A D3 interconnection can join restricted networks without opening them to the public. D6 distinguishes selecting protocols from operating requirements after selection. None of those facts erases the design contribution. They explain why the design credit cannot, on its own, answer separate questions about public admission, facilities, or operation.

Corrected statement. Cerf and Kahn co-designed influential internetworking protocols and architectural mechanisms. The parental description is an honorific. Identify particular networks, deployments, public-service milestones, and their contributors through dated evidence.

Consequence for the Historical Record. Credit the documented design at its actual scope. An honorific supplies no dated birth event, and shared architectural credit assigns neither every network’s construction nor every form of internetworking to the named designers.

2.0 The Marconi Prize citation credits Vinton Cerf among the “major factors” as contribution credit, and this section separates that credit from protocol selection, from implementation requirements, from the technical functions of TCP, IP and the carrier networks, and from the author lists of each design stage.

2.1 The Marconi Prize citation credits contributions. Its operative phrase is major factors. The citation credits technical achievement and ambassadorial leadership. That is evaluative contribution credit, not an assertion that Cerf alone created the system. The existence of an alternative architecture does not disprove the historical influence of the selected design or his leadership. This page does not present that citation as a fifth documentary contradiction. Marconi Prize citation.

2.2 Selection and implementation requirements have different scopes. Under D6, this record treats TCP and IP as optional architectural selections. Once a service selects an architecture, compatible implementation can be an operating requirement. RFC 1200 of April 1991, issued by the Internet Activities Board and edited by Jon Postel, grades TCP “Recommended” and IP “Required” in §6.2 for applicable implementations of its Internet suite. These grades concern implementation conformance. They do not establish that every application uses TCP, that all possible internetworking must select this suite, or that its designers constructed the networks carrying it. RFC 1200, §6.2.

2.3 Name the technical functions. Modern TCP supplies transport services between endpoints. IP modules in participating hosts and IP routers process datagrams. Supporting carrier networks can carry those datagrams through other switching mechanisms. RFC 791 distinguishes IP processing from the supporting networks. An underlying ATM switch can carry encapsulated IP traffic through cell switching without performing IP forwarding. Endpoint transport, IP forwarding, carrier carriage, and network construction therefore require separate descriptions. Jon Postel, ed., RFC 791, September 1981, §1.4 · Dan Grossman and Juha Heinanen, RFC 2684, September 1999.

2.4 Preserve the design stages and author lists. The May 1974 paper is by Vinton G. Cerf and Robert E. Kahn. The December 1974 RFC 675 is by Vinton Cerf, Yogen Dalal, and Carl Sunshine. The early combined transmission-control design is distinct from the later separation into TCP and IP. An account should identify which document, design stage, and contributor list it means. May 1974 paper · RFC 675, December 1974.

3.0 The documentary findings match each institution to its own record, date each asserted fact by its own document, and separate repeated wording from verified events.

3.1 Match the institution to the question. The White House’s December 16, 1997 record and the USPTO’s recipient entry state the government award rationale. ICANN’s November 2, 2007 resolutions and succession announcement establish the chairmanship boundary. NAE’s own 2008 and 2020 publications establish its membership designation. Each institution is an identifiable author or issuing body for its own record. No individual writer of the quoted institutional wording is identified here.

3.2 Date the fact being asserted. The Marconi Prize year does not date every later biographical sentence. A ceremony date, a term of office, a technical document’s publication date, and an undated webpage’s composition date are different facts. State the known date and preserve the uncertainty where the record does not supply one.

3.3 Separate repetition from verification. Similar language in multiple biographies establishes repeated wording. It does not independently establish every underlying event. An honorific establishes usage; an award citation establishes the stated recognition; a design paper establishes its technical proposal. None of those alone proves motive, coordination, universal necessity, or the construction and operation of all later infrastructure.

4.0 Exhibit A reproduces the five short excerpts of the Marconi Society laureate page that the findings contest or assess, and Exhibit B reproduces the complete official citation of the 1997 National Medal of Technology.

4.1 Exhibit A. Marconi source-excerpt ledger. The following are short exact excerpts, not complete sentences or the entire biography. The linked findings above supply the complete claim context. Read the original through its direct source link. Yellow identifies disputed wording; the accepted contribution excerpt is unhighlighted. The publisher is the Marconi Society, and the individual biographical writer is unknown.

MC-01. Marconi Prize citation. Assessment: §2.1. Finding or assessment · Complete original source.

major factors

MC-02. Parental honorific and architecture. Finding and complete claim context: §1.4. Finding or assessment · Complete original source.

Fathers of the Internet

MC-03. The 1997 medal clause. Finding and complete claim context: §1.1. This excerpt belongs to the 1997 clause. Finding or assessment · Complete original source.

founding and developing

MC-04. ICANN chairmanship. Finding and complete claim context: §1.2. Finding or assessment · Complete original source.

Since 2000, Cerf has chaired

MC-05. Institutional title. Finding and complete claim context: §1.3. Finding or assessment · Complete original source.

Fellow

4.2 Exhibit B. GOV-01, complete official 1997 medal citation. The White House’s December 16, 1997 record and the USPTO recipient entry identify Cerf and Kahn together. The citation reads:

For creating and sustaining development of Internet Protocols and continuing to provide leadership in the emerging industry of internetworking.

White House award record · USPTO recipient record · Finding 1.1. The issuing institutions are the source authorities; the individual citation writer is unidentified. This official wording is comparison evidence and is not highlighted as a disputed claim.

This record uses the declared terminology and documented-challenge terms in The Governing Definitions and Controlling Facts. Definitions identify its categories. Dated evidence establishes events, technical functions, and institutional roles.

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.