Oxford Internet Institute Lifetime Achievement Award: Disagreements | Network, Not Protocol

Design Chronology, Architectural Importance, and Award Attribution

Preamble. I examine the Oxford Internet Institute’s 2011 announcement of Vinton G. Cerf’s Lifetime Achievement Award. Five findings address the timing of design work, protocol terminology, the scope of an importance claim, the wording of a federal award’s rationale, and an IAB service date. The review identifies each disputed phrase, explains what the dated documents establish, and states the consequence for the historical record. The exact Oxford excerpts are quoted in the findings of section 1.0, and the exhibit section at the bottom of the page holds the complete federal citation and an institutional chronology comparison. This page is Disagreement 35 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 35, 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 Release, publisher, and speakers. The examined source is OII’s press release of July 21, 2011. Oxford Internet Institute is the institutional publisher. The displayed release identifies no individual writer. William Dutton and Cerf are named as speakers of their respective quotations. Attribute Dutton’s statement to Dutton and the surrounding institutional narrative to OII.

0.2 Dates and source references. The July release announces presentation planned for September 22 in its 2011 context. Announcement and presentation are separate events. References 1 through 4 identify the Oxford passages by the exact excerpts quoted at 1.1 through 1.4, and the linked OII release carries the full passages. Reference 2 identifies the opening summary; the body repeats its recognition with slightly expanded wording. Reference 5 identifies the IAB-service claim by its date excerpt and accompanying comparison records. The federal citation is a separate source.

0.3 Definitions and their application. The following definitions state this record’s framework and the evidence needed to apply it. Governing Definitions, D1 through D3 and D6.

Term Meaning used here Application to the release
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 public-founding attribution needs records identifying the service, interconnection terms, responsible organizations, and operating dates. A protocol-design attribution does not establish those particulars by itself.
Intranet, D2 A network whose owner controls admission. Size, geography, and protocol choice do not determine whether participation is public. A network’s protocol requirement identifies an operating condition. It does not, by itself, change restricted admission into public access.
Internetworking, D3 Connecting distinct networks through gateways so traffic from one can reach hosts on another. Designing an interconnection method, implementing it, building facilities, and operating the resulting service are separately attributable acts.
Protocol scope, D6 This record treats TCP and IP as optional protocol selections. TCP supplies endpoint transport; IP specifies datagram addressing and forwarding. Implementations execute those functions, and a deployment can require its selected protocols for compatible operation. Elective architectural selection, a deployment’s implementation requirements, and historical importance within that deployment are different questions. Calling a protocol optional among architectures does not make it optional while performing that protocol’s specified function.

0.4 Standard of finding. Chronology requires dated records of the particular role or document. Protocol terminology requires the applicable function and technical stage. A scope disagreement identifies the additional inference being challenged. A formal award citation and another institution’s paraphrase retain their separate authorship. Conflicting records are stated explicitly rather than silently resolved in favor of one date.

1.0 Disagreements

1.1 Disagreement. Initial design at Stanford must be distinguished from Cerf’s later DARPA appointment

Source. The biographical account, reference 1.

Timing words contested, exact excerpt: during his tenure. The sentence places Cerf’s co-design in his DARPA tenure.

Finding and disagreement. The sentence compresses initial and later development into one employment period. Cerf and Kahn’s May 1974 paper identifies Cerf with Stanford. The CV accompanying Cerf’s February 8, 2001 congressional testimony lists Stanford employment from November 1972 through August 1976 and DARPA/IPTO employment from September 1976 through September 1982. The original published design therefore belongs to his Stanford period. Vinton G. Cerf and Robert E. Kahn, May 1974 · Cerf, 2001 testimony and appended CV.

Sponsorship and employment. Cerf’s April 1, 1980 IEN 151 documents the DARPA-supported Stanford TCP project from 1973 through 1976 and subsequent work at other centers. DARPA sponsorship of Stanford research does not make Cerf’s Stanford appointment the same employment period as his later DARPA position. Development and refinement continued during the DARPA period. Identify both phases when crediting the work. Cerf, IEN 151, printed pp. 1 and 2.

Corrected historical statement. Cerf began the collaboration with Kahn while at Stanford, and their design paper appeared in May 1974. Development continued during Cerf’s DARPA appointment from 1976 through 1982, including later refinement and separation of the early combined protocol design.

Consequence for the Historical Record. Attribute each phase to the correct people, institution, and period. DARPA funding, Stanford design work, later DARPA program management, subsequent specifications, and operating deployment must not become one undated accomplishment.

1.2 Disagreement. The TCP/IP label needs precision while protocol design and technical oversight retain their separate meaning

Source. The opening summary, reference 2.

Words contested, exact excerpt: designing the TCP/IP protocol.

Finding and disagreement. The singular label compresses distinct TCP and IP functions into one protocol name. TCP/IP commonly identifies a suite or architecture. TCP endpoint service and IP datagram processing should be identified separately when the subject is precise engineering attribution. Oxford’s sentence also credits broader technical-architecture contributions. Its conjunction identifies those as additional work; it does not logically equate protocol design with all architecture or physical construction.

How D1, D3, and D6 apply. The May 1974 paper describes a gateway-based interconnection design. Cerf’s May 1990 RFC 1160 documents his IAB chairmanship and the board’s standards and coordination responsibilities. Those records support architectural and institutional contributions at identified scopes. Under D3, the design addresses communication across networks. Under D6, implementations perform the specified functions. Under D1, construction and public participation additionally require records identifying facilities, operating interconnections, and admission terms. Cerf and Kahn, May 1974 · Vinton Cerf, RFC 1160, §2.

Corrected historical statement. OII recognized Cerf’s role in developing the TCP/IP protocols and his broader contributions to architecture and technical coordination. Identify the particular functions and periods of that work separately from construction and operation of constituent networks.

Consequence for the Historical Record. Name the protocol functions accurately and preserve supported architectural and institutional work. Use construction, deployment, and admission records to attribute the additional acts required to establish the operating public network.

1.3 Disagreement. Historical importance must not silently become universal protocol necessity

Source. OII Director William Dutton’s attributed quotation, reference 3.

Words contested, exact excerpt: one of its fundamental protocols.

Finding and disagreement. Dutton describes importance and institutional leadership. The scope objection concerns interpreting the adjective as a claim that every Internet communication must use the same transport. His quotation does not identify TCP/IP by name or expressly make that universal-use claim. State the technical subject and deployment before inferring necessity from an importance attribution.

Applicable counterexample. Jon Postel’s August 1980 RFC 768 specifies UDP communication over IP. A communication using UDP without TCP demonstrates that TCP is not used in every IP communication. It does not demonstrate communication without IP. John Lazzaro’s July 2006 RFC 4571 specifies RTP/RTCP carriage over connection-oriented transports, including TCP, so naming RTP alone does not establish TCP’s absence. Postel, RFC 768 · Lazzaro, RFC 4571.

How D6 applies. A method can be elective among architectures and historically central in a deployment that selected it. Those propositions can coexist. Evidence of an alternative function limits a universal-use assertion at that function; it does not erase the selected method’s historical contribution.

Corrected historical statement. Dutton credited protocol work of historical and architectural importance and leadership in Internet institutions. That attribution does not establish TCP’s use in every IP communication or impose TCP/IP on every possible internetwork architecture.

Consequence for the Historical Record. Preserve the distinction between importance and necessity. Identify the claimed protocol and the function an alternative actually replaces. An adjective does not establish a universal requirement, and elective selection does not establish historical irrelevance.

1.4 Disagreement. Oxford’s founding paraphrase must retain its separate authorship from the federal medal citation

Source. The National Medal of Technology account, reference 4.

Words contested, exact excerpt: for founding and developing the Internet.

Finding and disagreement. Oxford gives a broader historical characterization than the formal rationale. The contemporaneous White House record of December 16, 1997 and the USPTO laureates page identify Internet-protocol development and continuing leadership in the internetworking industry. Oxford’s paraphrase is not presented as a verbatim quotation. The disagreement concerns substituting that paraphrase for the federal award’s actual wording. White House, December 16, 1997 · USPTO, 1997 laureates.

Full comparison wording. The complete formal citation appears in Exhibit B, §4.5. It credits a defined contribution to protocol development and industry leadership. Under D1, a broader public-founding attribution requires additional records of the networks, operators, terms, and operating dates. Oxford’s characterization cannot supply those particulars by being repeated as the federal citation.

Corrected historical statement. President Clinton presented the National Medal of Technology to Cerf and Kahn on December 16, 1997. The formal rationale recognized protocol development and continued industry leadership. Oxford’s founding description is its own broader historical paraphrase and must remain attributed to Oxford.

Consequence for the Historical Record. Report the federal citation in its own words and identify Oxford’s paraphrase as Oxford’s. A later institution’s broader characterization must not replace the award’s documentary rationale or establish all construction and public-founding acts by implication.

1.5 Disagreement. Oxford’s IAB start year conflicts with the examined membership records

Source. The institutional biography’s IAB service interval. Its excerpt and comparison records appear at reference 5.

Interval contested, exact excerpt: 1983-1993.

Finding and disagreement. The IAB’s own historical roster lists Cerf’s membership from 1986 to 1993. The biography he supplied for Gary Malkin’s May 1992 RFC 1336 distinguishes an ex officio ICCB role during 1979 through 1982 from IAB membership beginning in 1986 and chairmanship during 1989 through 1991. These records do not support Oxford’s 1983 IAB start. Creating or serving on an earlier body and joining the later IAB are different roles. IAB historical roster · Cerf biography compiled by Malkin, RFC 1336, §4.5, printed p. 11.

Conflicting start-date record. Cerf’s 2001 CV instead gives IAB membership from 1985 to 1993 and chairmanship from 1989 to 1992. This variation must remain visible. None of these three records supplies Oxford’s 1983 membership start. The exact entry date and the inconsistent chairmanship end years require appointment or meeting records to settle them. Cerf, 2001 testimony and CV.

Corrected historical statement. Identify Cerf’s earlier ICCB role separately from his IAB service. The IAB roster records membership during 1986 through 1993 and chairmanship from July 1989 to July 1991. His 1992 biography supports a 1986 membership start; his 2001 CV gives 1985. Attribute each date to its record rather than presenting Oxford’s 1983 start as settled.

Consequence for the Historical Record. Date the individual’s actual institutional role, rather than extending it backward by association with a predecessor body. Preserve the documented leadership contribution and the unresolved differences among records. An institution’s organizational history does not, by itself, establish when a particular person joined it.

2.0 Protocol Choice and Functional Separation

2.1 Implementation grades have a stated scope. Within its Internet-suite conformance framework for applicable hosts and gateways, RFC 1200 of April 1991, issued by the Internet Activities Board and edited by Jon Postel, classifies TCP as “Recommended” and IP as “Required” in §6.2. These are implementation grades for that architecture. A network operator can impose applicable requirements within its selected service. The classifications do not allocate historical construction credit or impose one architecture on every possible form of internetworking. RFC 1200, §6.2.

2.2 Counterexamples must identify their technical layer and date. UDP over IP, specified by Postel in 1980, demonstrates transport without TCP. RTP can use a TCP carriage method documented by Lazzaro in 2006. Jana Iyengar and Martin Thomson’s May 2021 RFC 9000 specifies QUIC over UDP. That later standard is a present-day illustration, not evidence of Dutton’s intended 2011 reference. Each example establishes a particular function and dependency. RFC 768 · RFC 4571 · Iyengar and Thomson, eds., RFC 9000.

2.3 Name the equipment and function. TCP connection, sequencing, acknowledgment, retransmission, and flow control execute at communicating endpoints. IP hosts and forwarding routers perform IP datagram processing. An underlying ATM switch can carry encapsulated IP traffic by switching cells without performing IP forwarding. A router can also act as an endpoint for its own communication. Naming the actual function on the actual path distinguishes endpoint service, IP forwarding, and carrier carriage. Jon Postel, ed., RFC 793, September 1981 · Postel, ed., RFC 791, September 1981 · Dan Grossman and Juha Heinanen, RFC 2684, September 1999.

3.0 Evidence and Institutional Attribution

3.1 Preserve authorship and technical stage. The May 1974 intercommunication paper is by Vinton G. Cerf and Robert E. Kahn. The December 1974 RFC 675 specification is by Vinton Cerf, Yogen Dalal, and Carl Sunshine. The early combined program predates the later separate TCP and IP specifications. Keep the author lists and technical stages distinct when attributing the design. Cerf and Kahn, May 1974 · Cerf, Dalal, and Sunshine, RFC 675.

3.2 Institutional attribution and record conflicts. OII is responsible for its release, and Dutton is the identified speaker of his quotation. The White House and USPTO are responsible for their federal award records; their individual citation drafter is unknown here. The IAB is responsible for its historical roster, whose individual compiler is unidentified. Gary Malkin compiled RFC 1336 from supplied biographies, including Cerf’s. These distinctions identify who said what. They also preserve the difference between an institutional record, a participant’s biography, and a later press-release paraphrase.

4.0 Exhibits: Oxford Passages and Comparison Records

The Oxford passages examined in findings 1.1 through 1.4 are identified by the exact excerpts quoted at those findings, and the linked OII release carries the full passages. The complete federal citation in §4.5 is comparison evidence from a different institutional source. §4.6 identifies Oxford’s IAB-service date and records the conflicting chronology. These are selected passages and verification records, rather than a reproduction of the entire OII release. The source labels, anchors, and yellow highlights are editorial additions. OII press release, July 21, 2011.

4.5 Exhibit B. Complete formal National Medal of Technology citation. The White House’s December 16, 1997 record and USPTO’s 1997 laureates page give the following rationale for Cerf and Kahn. The institutional sources are identified; the individual drafter is unknown here.

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

White House, December 16, 1997, National Medal of Technology recipients · USPTO, 1997 laureates.

4.6 Exhibit C. IAB-service chronology, source reference 5. Oxford’s institutional biography assigns Cerf IAB service from 1983 to 1993. This is a source paraphrase. The records below identify different dates and roles. Their discrepancies remain stated rather than silently merged.

Record and attribution Earlier ICCB role IAB membership and chairmanship as recorded
Cerf’s supplied biography in Gary Malkin’s May 1992 RFC 1336, §4.5 Ex officio member, 1979 through 1982 Member, 1986 through 1989; chairman, 1989 through 1991. The biography distinguishes the roles.
IAB’s historical roster, individual compiler unidentified No individual ICCB term supplied in Cerf’s roster entry Member, 1986 through 1993; chairman, July 1989 through July 1991
Cerf’s CV appended to his February 8, 2001 congressional testimony No individual ICCB interval in the cited entry Member, 1985 through 1993; chairman, 1989 through 1992

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.