ICANN Vinton G. Cerf: Disagreements | Network, Not Protocol

Award Wording, Architectural Credit, and Profile Provenance

Preamble. I examine three claims in the supplied biography of Vinton G. Cerf hosted on ICANN’s website. The disagreements distinguish a reported honorific from evidence of a defined founding event, compare the biography’s medal description with the formal 1997 citation, and correct the titles used for two institutional affiliations. Each finding identifies the source wording, the documentary evidence, and the consequence for the historical record. The page also distinguishes hosting a profile from independently verifying its claims. This page is Disagreement 13 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 13, 1.1.

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

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

0.0 Source and Scope

0.1 Source and authorship. The examined source is the supplied copy of the Vinton G. Cerf biography hosted by ICANN, headed with his name and Google role. No publication or update date appears in that copy. Its individual author and the authors of the disputed sentences are unknown to this record. Present-tense career descriptions must therefore retain their undated context. The date embedded in the URL does not, by itself, establish when a particular sentence was written or updated.

0.2 Passage references. Exhibit A preserves the supplied biography with 38 numbered body sentence units. Navigation, the heading, footer, and cookie notice are retained outside that count. The source links below identify the complete disputed passages on this published page. Yellow identifies the disputed claim in an expressly labeled paraphrase. Exhibit B separately reproduces the official medal citation for comparison. Exhibit A · Exhibit B.

0.3 Definitions and their application. The definitions below state this site’s framework and explain how it applies to the biography. They do not change the historical wording in the source exhibit. The Governing Definitions, D1 through D3.

Term Meaning used here What the claim must establish
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 claim needs a named network, its operators, the participation terms, and a supported operating date. A protocol design or award does not establish these particulars by itself.
Intranet, D2 A network whose owner controls admission. Its protocol, size, and international reach do not determine whether admission is public. A research network’s reach or use of TCP/IP does not establish D1’s public-admission condition. The relevant access rules must be examined.
Internetworking, D3 Connecting distinct networks through gateways so traffic from one can reach hosts on another. A design for communication across networks is architectural work. Its design record must be distinguished from the records of installation, operating interconnection, and public service.

0.4 Protocol scope. D6 treats protocols as specified communication methods implemented by equipment and software. TCP provides endpoint transport control; IP handles datagrams in hosts and in routers performing IP forwarding. A network operator can select an architecture and require its components for that deployment. Such a requirement identifies the deployment’s conditions, while construction, admission, reach, and service performance each require their own evidence. Governing Definitions, D6.

0.5 Finding standard. The biography reports shared recognition and collaborative design credit. Those statements must be evaluated at their stated scope. A disputed award paraphrase, an undefined founding honorific, and an institution’s membership title require different findings. The documented design, engineering, and management contributions remain attributable to the work and participants the evidence identifies.

1.0 Disagreements

Disagreement Subject Finding
1.1 Founding honorific and architectural attribution The design contribution and the public founding event require different evidence.
1.2 1997 medal description The biography’s founding language is broader than the formal citation.
1.3 APS and NAE designations The institutions describe these relationships as membership.

1.1 Disagreement. The honorific leaves the founding event and operating work undefined

Source. Sentence 7.

Disputed attribution, paraphrased. The biography couples a shared Internet-founding honorific with TCP/IP co-design and an unqualified attribution of Internet architecture.

Finding. The reported recognition and design contribution are documented subjects. The disagreement concerns using that combination as a complete historical explanation without identifying the system, founding event, or operating work being credited.

Disagreement. Vinton G. Cerf and Robert E. Kahn’s May 1974 paper describes communication across separately developed packet networks, including gateways, network boundaries, packet handling, and host communication. That is architectural work. The paper establishes a design contribution with named authors. It does not document every subsequent network’s construction, admission rules, or operating service. Cerf and Kahn, May 1974.

How D1 and D3 apply. D3 identifies what the design addresses: communication across networks. D1 adds a distinct public-admission test. To establish that public milestone, the evidence must identify who could obtain service and how independent networks could interconnect. The joint CIX announcement of March 25, 1991 records commercial exchange terms for customers of CERFnet, PSINet, and AlterNet. Mark Fedor’s October 1991 CIX-WEST report records operating traffic among those providers. Those are the kinds of agreement and operating records needed for that separate finding. The announcement’s institutional authors are General Atomics, Performance Systems International, and UUNET; its individual writer is unknown. CIX announcement · Fedor, October 1991 report, pp. 14 and 15.

Corrected statement. Cerf, working with Kahn and other contributors, helped develop internetwork architecture and protocols that evolved into TCP/IP. The biography also reports widespread recognition through a founding honorific. A historical account should identify the particular system and event that honorific is intended to explain, then attribute its construction, operating interconnection, and public access through their own documentary records.

Consequence for the Historical Record. Credit the architectural contribution demonstrated by the design documents. Require separate evidence naming the participants and events behind network construction, operating interconnection, public admission, and commercial service. An honorific cannot supply those missing particulars.

1.2 Disagreement. The medal citation credits protocol development and leadership in internetworking

Source. Sentence 8.

Disputed award description, paraphrased. The biography describes the 1997 National Medal of Technology as recognition for Cerf and Kahn founding and developing the Internet.

Finding. The biographical paraphrase expands the stated scope of the formal award citation. The passage is a paraphrase rather than a purported direct quotation, so the correction must identify the change in scope precisely.

Disagreement. The White House Office of the Press Secretary’s December 16, 1997 ceremony record reproduces the citation for developing Internet protocols and continuing leadership in the internetworking industry. The USPTO’s recipient record repeats that citation. Cerf’s own 2009 witness statement, paragraph 6 on printed page 2, gives the same wording. Exhibit B reproduces it once for direct comparison. These records establish the medal’s stated grounds and confirm the December 1997 presentation. White House, December 16, 1997 · USPTO recipient record · Cerf, 2009 witness statement, paragraph 6.

Why the wording changes the historical claim. Protocol development and leadership in an industry identify contributions. Founding an operating network identifies an establishment event. Under D3, the citation’s internetworking subject concerns communication across networks. Under D1, a public opening additionally requires evidence of the network, operators, participation terms, and operating date. The formal citation does not supply those particulars or make the biography’s broader founding claim. That broader claim requires additional evidence.

Corrected statement. On December 16, 1997, President Clinton presented Cerf and Kahn with the National Medal of Technology for their protocol-development work and continuing leadership in internetworking, as stated in the formal citation. A broader founding claim must be identified as a separate historical assertion and supported separately.

Consequence for the Historical Record. Preserve the award’s stated grounds. Do not allow a broader profile paraphrase to circulate as though the award document itself established a public-network founding event. Keep the citation and the additional historical claim visible as separate propositions.

1.3 Disagreement. APS and NAE membership should retain the institutions’ own titles

Source. Sentence 24.

Disputed designation, paraphrased. The biography’s combined fellowship list applies a single Fellow designation to the American Philosophical Society and the U.S. National Academy of Engineering.

Finding. The affiliations are supported, but their formal designations need correction. This finding addresses these two entries rather than assuming that every institution in the list uses an incorrect title.

Disagreement. The American Philosophical Society’s 2020 member news identifies Cerf with the election year 2008. The National Academy of Engineering’s October 4, 2020 publication lists him among its anniversary members on printed page 20. The National Academy of Sciences’ Cerf profile likewise describes membership in the national academies. These institutional records support describing the APS and NAE relationships as membership. Individual authors of these institutional entries are unknown. APS member news, April 2020 · NAE membership publication, October 4, 2020, p. 20 · NAS Cerf profile.

Corrected statement. Cerf’s affiliations include fellowships in organizations such as IEEE and ACM, and membership in the American Philosophical Society and the National Academy of Engineering. Each institution’s designation should be retained rather than placing every relationship under one fellowship label.

Consequence for the Historical Record. Preserve the relationship each institution actually records. Membership, fellowship, an award, and institutional leadership are different credentials and must remain distinguishable when they are used as historical authority.

2.0 The Engineering and Career Record

2.1 Identify the function and equipment. This table describes the separated TCP/IP architecture. Its final separation must not be projected unchanged onto the early combined transmission-control program.

Function Where performed Evidence of a distinct accomplishment
TCP connection and byte-stream control TCP endpoints Implementation and observed acknowledgments, sequencing, retransmission, flow control, and connection behavior.
IP datagram processing and forwarding IP hosts and forwarding routers Implemented processing, usable routes, and forwarding behavior in the selected architecture.
Underlying switching and carriage Provisioned links, carrier switches, and facilities Installed capacity, available paths, protection, and service performance.
Admission and operating interconnection Providers and interconnected networks Access conditions, agreements, and observed operating exchanges.

Jon Postel’s September 1981 specifications describe IP datagram handling and TCP endpoint service. An IP router actively forwards datagrams. An underlying ATM switch can carry encapsulated traffic through cell switching without performing the carried traffic’s IP forwarding function. The roles belong to different equipment and protocol boundaries. RFC 791 · RFC 793 · Grossman and Heinanen, RFC 2684, September 1999.

2.2 Selection and scoped requirements. An operator can select an architecture and require its applicable components for participation. D6 treats these as selectable methods of communication. The protocol registers edited by Jon Postel grade TCP Recommended and IP Required within their listed suite frameworks. Those grades describe requirements in that framework. They do not assign authorship of the underlying networks or establish a universal requirement for all possible internetworking. RFC 1200, April 1991 · RFC 2200, June 1997 · Governing Definitions, D6.

2.3 Supported engineering and management work. Cerf’s CV accompanying his February 8, 2001 congressional testimony records DARPA service from September 1976 through September 1982, MCI engineering work from October 1982 through May 1986, CNRI service from June 1986 through January 1994, and a return to MCI in February 1994. The CV identifies design and implementation responsibilities for MCI Mail and later MCI data services. These are documented engineering and management roles that require attribution alongside protocol design. Cerf’s CV and congressional testimony.

2.4 Separate product and connection milestones. The biography’s MCI Mail passage describes engineering during the earlier employment interval and separately characterizes the service’s later Internet connection. A product’s design, launch, subsequent gateway connection, and access policy are distinct events. The employment dates alone do not establish the date or priority of the later connection.

3.0 Profile Hosting, Institutional Relationships, and Repeated Claims

3.1 Hosting is not evidence of independent verification. The current ICANN profile, checked on November 4, 2026, includes a notice disclaiming responsibility for profile content and verification of user details. That notice is absent from the supplied copy preserved in Exhibit A. Its current presence is a provenance finding, not a silent amendment to the older exhibit. ICANN hosts and circulates the biography. The hosting alone does not establish who wrote it or that ICANN independently verified every claim. Current ICANN profile, notice following the biography.

3.2 Leadership relationships require their own records. The biography identifies Cerf as a former ICANN chairman, an Internet Society founding president, and a subsequent Society chairman. The Internet Society’s July 21, 1998 board minutes record his election as chair; the June 22, 1999 minutes record Geoff Huston’s election as successor. Those records support service during 1999 and provide a more precise account than an undated profile alone. The institutional minutes are the authority for the recorded elections. Their individual drafter is unknown here. Internet Society, July 21, 1998 minutes · Internet Society, June 22, 1999 minutes.

3.3 Repetition establishes circulation. Matching or similar wording across profiles establishes that a claim circulated. It does not establish independent investigation by every host, the identity of an original author, the direction of copying, or a writer’s motive. Record the matching words and documented relationships, then verify the historical proposition against the evidence addressing it.

3.4 Match the document to the question. The formal citation establishes the stated grounds of the medal. Design documents identify architectural and protocol work. Membership records establish institutional designations. Board minutes establish elections. Construction records, agreements, admission terms, and measurements establish the relevant operating accomplishments. A prominent host or repeated honorific cannot substitute for those records.

4.0 Exhibit A. Supplied ICANN Biography

4.1 Exhibit description. Preserve the existing source block below, including its 38 numbered body sentence units, navigation, heading, footer, copyright text, and cookie notice. Sentence numbers, passage anchors, and yellow highlights are editorial additions. This is the supplied plain-text copy, not a capture of ICANN’s original page layout. Its individual author and publication or update date remain unidentified. The current hosting notice discussed in §3.1 is not inserted into this supplied exhibit.

Skip to main content Log InSign Up GET STARTED About ICANN ICANN for Beginners Fellowship Program NextGen@ICANN Program History NEWS AND MEDIA Announcements Blog Media Resources Press Releases Global Newsletters ICANN News Subscriptions Regional Reports POLICY Develop Policy Operational Design Phase (ODP) Implement Policy Community Participation Guidelines PUBLIC COMMENT Public Comment Home Upcoming Proceedings Open Proceedings Closed Proceedings About Public Comment Other Public Consultations RESOURCES Board Activities and Meetings Accountability Mechanisms Contracted Parties (Registry Operators and Accredited Registrars) Domain Name Registrants Contractual Compliance Domain Name Security Threats Privacy and Proxy Services Government Engagement Careers Complaints Office I Need Help ICANN 25th Anniversary Photo Mosaic COMMUNITY Engagement Calendar Address Supporting Organization (ASO) Country Code Names Supporting Organization (ccNSO) Generic Names Supporting Organization (GNSO) At-Large Advisory Committee (ALAC) Governmental Advisory Committee (GAC) Root Server System Advisory Committee (RSSAC) Security and Stability Advisory Committee (SSAC) QUICKLINKS Board Activities and Meetings Data Protection and Privacy Domain Name Registrants Engagement Calendar IANA Services ICANN Acronyms and Terms ICANN Grant Program New gTLD Program Public Technical Identifiers (PTI) Open Data Question About A Domain Name? Technology @ ICANN WSIS+20 Outreach Network About ICANN Board Activities and Meetings Accountability Governance Groups Business Civil Society Complaints Office Domain Name System Abuse Contractual Compliance Contracted Parties (Registry Operators and Accredited Registrars) Domain Name Registrants GDS Metrics Identifier Systems Security, Stability and Resiliency (OCTO-SSR) ccTLDs Internationalized Domain Names New gTLD Program Universal Acceptance Initiative Policy Operational Design Phase (ODP) Implementation Public Comment Root Zone KSK Rollover Technical Functions ICANN Locations I Need Help Vinton G. Cerf | Vice President and Chief Internet Evangelist [1] Vinton G. Cerf has served as vice president and chief Internet evangelist for Google since October 2005. [2] In this role, he is responsible for identifying new enabling technologies to support the development of advanced, Internet-based products and services from Google. [3] He is also an active public face for Google in the Internet world. [4] Cerf is the former senior vice president of Technology Strategy for MCI. [5] In this role, Cerf was responsible for helping to guide corporate strategy development from the technical perspective. [6] Previously, Cerf served as MCI's senior vice president of Architecture and Technology, leading a team of architects and engineers to design advanced networking frameworks including Internet-based solutions for delivering a combination of data, information, voice and video services for business and consumer use. [7] Widely known as one of the "Fathers of the Internet," Cerf is the co-designer of the TCP/IP protocols and the architecture of the Internet. [8] In December 1997, President Clinton presented the U.S. National Medal of Technology to Cerf and his colleague, Robert E. Kahn, for founding and developing the Internet. [9] Kahn and Cerf were named the recipients of the ACM Alan M. Turing award in 2004 for their work on the Internet protocols. [10] The Turing award is sometimes called the "Nobel Prize of Computer Science." [11] In November 2005, President George Bush awarded Cerf and Kahn the Presidential Medal of Freedom for their work. [12] The medal is the highest civilian award given by the United States to its citizens. [13] In April 2008, Cerf and Kahn received the prestigious Japan Prize. [14] Prior to rejoining MCI in 1994, Cerf was vice president of the Corporation for National Research Initiatives (CNRI). [15] As vice president of MCI Digital Information Services from 1982-1986, he led the engineering of MCI Mail, the first commercial email service to be connected to the Internet. [16] During his tenure from 1976-1982 with the U.S. Department of Defense's Advanced Research Projects Agency (DARPA), Cerf played a key role leading the development of Internet and Internet-related packet data and security technologies. [17] Vint Cerf served as chairman of the board of the Internet Corporation for Assigned Names and Numbers (ICANN) from 2000-2007. [18] Cerf also served as founding president of the Internet Society from 1992-1995 and in 1999 served a term as chairman of the Board. [19] In addition, Cerf is honorary chairman of the IPv6 Forum, dedicated to raising awareness and speeding introduction of the new Internet protocol. [20] Cerf served as a member of the U.S. Presidential Information Technology Advisory Committee (PITAC) from 1997 to 2001 and serves on several national, state and industry committees focused on cyber-security. [21] Cerf sits on the Board of Directors for the Endowment for Excellence in Education, the Broadband for the Deaf and Hard of Hearing Corporation, StopBadWare, the Smart Grid Interoperability Panel governing board and the Intaba Institute (for the Deaf). [22] He serves on the Jet Propulsion Laboratory Advisory Committee and serves as Chair of the Visitors Committee on Advanced Technology of the U.S. National Institute of Standards and Technology. [23] He also serves as 1st Vice President and Treasurer of the National Science & Technology Medals Foundation. [24] Cerf is a Fellow of the IEEE, ACM, and American Association for the Advancement of Science, the American Academy of Arts and Sciences, the International Engineering Consortium, the Computer History Museum, the Annenberg Center for Communications at USC, the Swedish Royal Academy of Engineering, the American Philosophical Society and the US National Academy of Engineering. [25] Cerf is a recipient of numerous awards and commendations in connection with his work on the Internet. [26] These include the Marconi Fellowship, Charles Stark Draper award of the National Academy of Engineering, the Prince of Asturias award for science and technology, the National Medal of Science from Tunisia, the St. Cyril and St. Methodius Order (Grand Cross) of Bulgaria, the Alexander Graham Bell Award presented by the Alexander Graham Bell Association for the Deaf, the NEC Computer and Communications Prize, the Silver Medal of the International Telecommunications Union, the IEEE Alexander Graham Bell Medal, the IEEE Koji Kobayashi Award, the ACM Software and Systems Award, the ACM SIGCOMM Award, the Computer and Communications Industries Association Industry Legend Award, installation in the Inventors Hall of Fame, the Yuri Rubinsky Web Award, the Kilby Award , the Rotary Club International Paul P. Harris Medal, the Joseph Priestley Award from Dickinson College, the Yankee Group/Interop/Network World Lifetime Achievement Award, the George R. Stibitz Award, the Werner Wolter Award, the Andrew Saks Engineering Award, the IEEE Third Millennium Medal, the Computerworld/Smithsonian Leadership Award, the J.D. Edwards Leadership Award for Collaboration, World Institute on Disability Annual award and the Library of Congress Bicentennial Living Legend medal. [27] Cerf was inducted into the National Inventors Hall of Fame in May 2006. [28] He was made an Eminent Member of the IEEE Eta Kappa Nu (HKN) honor society of the IEEE in 2009. [29] In 2010 he received a Lifetime Webby Award. [30] In February 2011 he was named a Stanford Engineering School "Hero" for his work on the Internet. [31] In December, 1994, People magazine identified Cerf as one of that year's "25 Most Intriguing People." [32] In addition to his work on behalf of Google and the Internet, Cerf has served as a technical advisor to production for "Gene Roddenberry's Earth: Final Conflict" and made a special guest appearance on the program in May 1998. [33] Cerf has appeared on television programs NextWave with Leonard Nimoy and often co-hosted World Business Review with Alexander Haig and Caspar Weinberger. [34] Cerf also holds an appointment as distinguished visiting scientist at the Jet Propulsion Laboratory where he is working on the design of an interplanetary Internet. [35] Cerf holds a Bachelor of Science degree in Mathematics from Stanford University and Master of Science and Ph.D. degrees in Computer Science from UCLA. [36] He also holds honorary Doctorate degrees from the Swiss Federal Institute of Technology (ETH), Zurich; Lulea University of Technology, Sweden; University of the Balearic Islands, Palma; Capitol College, Maryland; Gettysburg College, Pennsylvania; George Mason University, Virginia; Rovira i Virgili University, Tarragona, Spain; Rensselaer Polytechnic Institute, Troy, New York; the University of Twente, Enschede, The Netherlands; Brooklyn Polytechnic; Marymount University; the University of Pisa; the Beijing University of Posts and Telecommunications;Tschingua University, Beijing, China; the University of Zaragoza, Spain; the Technical University of Cartagena, Spain; the Polytechnic University of Madrid, Spain; and Bethany College, Kansas. [37] His personal interests include fine wine, gourmet cooking and science fiction. [38] Cerf and his wife, Sigrid, were married in 1966 and have two sons, David and Bennett. YouTube Twitter LinkedIn Flickr Facebook Newsletters Community Wiki ICANN Blog WHO WE ARE ICANN For Beginners ICANN Learn Participate Groups Board Members CEO Corner Staff Careers Public Responsibility CONTACT US Locations Report Security Issues Certificate Authority Registry Liaison Ombuds Complaints Office Media Resources ACCOUNTABILITY AND TRANSPARENCY Accountability Mechanisms Document Disclosure Independent Review Process Request for Reconsideration Empowered Community Employee Anonymous Hotline Policy and Procedures GOVERNANCE Governance Documents Agreements Organizational Reviews Specific Reviews Annual Report Financials Planning RFPs Litigation Correspondence HELP I Need Help Dispute Resolution Domain Name Dispute Resolution Name Collision ICANN Lookup Registration Data Request Service (RDRS) DATA PROTECTION Data Privacy Practices Privacy Policy Terms of Service Cookies Policy © Internet Corporation for Assigned Names and Numbers.Privacy PolicyTerms of ServiceCookies Policy We use cookies to improve your browsing experience, analyze our traffic, and provide you with personalized content as described in our Cookie Policy. By clicking 'Accept All', you consent to our use of cookies. To manage your preferences or disable cookies, click 'Manage Cookies'. To reject non-essential cookies, click ‘Reject Cookies’.Privacy Policy Manage Cookies Reject Cookies Accept All Cookies

5.0 Exhibit B: Official 1997 Medal Citation

5.1 Source. The USPTO's official 1997 recipient record identifies Vinton Gray Cerf and Robert E. Kahn. The passage below is the formal citation quoted in section 1.2. This is a quoted excerpt, not a reproduction of the entire USPTO webpage.

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

5.2 Corroborating records. The USPTO’s official 1997 recipient entry reproduces the same citation. Cerf’s 2009 witness statement, paragraph 6 on printed page 2, also reproduces it. These records corroborate the wording. Their repetition does not expand the award’s stated grounds into a different founding claim. USPTO recipient record · Cerf witness statement, paragraph 6.

6.0 The Definitions Addendum reproduces the Governing Definitions D1 through D13 of marknichols.com word for word, and every finding on this page is made under them.

6.1 Every finding on this page is made under the Governing Definitions of marknichols.com, D1 through D13, which are reproduced in this addendum word for word from The Governing Definitions and Controlling Facts of Telecommunications Internetworking. A reader of this page either accepts these definitions or disputes them. A reader who disputes a definition states the competing definition in one sentence and names the dated document that carries it before opining on any finding of this page. A reader who opines on the findings without disputing a definition has read the findings under these definitions by default.

6.2 The definitions below are copied word for word from the section “These definitions are employed throughout marknichols.com” of The Governing Definitions and Controlling Facts of Telecommunications Internetworking, as that page read on November 13, 2026, and that page controls wherever a copy differs from it.

D1. The Internet (capital I). The publicly joinable network of networks of the registry lineage: the fabric whose addresses and autonomous system numbers were issued by the InterNIC and are maintained today by ARIN. A person joins it by purchasing access from any of competing commercial providers, for any lawful purpose, and a network joins it by obtaining addresses and an autonomous system number from the numbering registry and then interconnecting by agreement with any willing network, the way Digital Island joined under autonomous system AS6553, issued August 29, 1996 by the InterNIC, with the registration maintained today in ARIN’s registry. No owner grants admission, no written policy screens members or their purposes, and no government sponsorship is required, and that single property, open admission, is what separates the Internet from every gated network that existed before it. The capital-I Internet was born in 1991, when independently operated commercial networks of this lineage, PSINet, AlterNet under UUNET, and CERFnet, interconnected by their own agreement as the Commercial Internet eXchange (CIX), settlement-free and free of any purpose-screening policy, and it was born small: the gated research world stood beside it until April 30, 1995, upon the decommission of NSFNET folded into internetMCI, per orders of Congress. Neither the ARPANET intranet, which admitted members only by agency authorization, nor the NSFNET intranet, which admitted members only under a written Acceptable Use Policy restricted to research and education, met this definition on any day of either existence, so the capital I names an Internet network that is public, or it names nothing. Paragraphs D1.1 through D1.7 state why the ARPANET and the NSFNET are not in the lineage of the Internet, each on its document.

D1.1 A network stands in the lineage of the Internet only if it carried the trait that defines the Internet, and D1 names that trait as one property, open admission; a network that never carried open admission had no such trait to pass on, and the ARPANET and the NSFNET never carried it, so neither the ARPANET nor the NSFNET is the grandfather, the ancestor, the parent, or the precursor of the Internet, and neither the ARPANET nor the NSFNET became the Internet.

D1.2 The ARPANET admitted members by its owner’s authorization from its procurement to its end: Request for Quotations No. DAHC15 69 Q 0002, issued July 29, 1968 for the Advanced Research Projects Agency of the United States Department of Defense, states the network’s purpose as “making these advanced research computer systems available to users outside their own design circle,” a purpose among the owner’s research contractors, as F37 of this page records; admission ran through agency authorization, as D4 of this page records; and the ARPANET ran from 1969 to 1990, as F38 of this page records, so the ARPANET was an intranet under D2 on every day of its existence and never carried open admission.

D1.3 The NSFNET admitted members only under a written Acceptable Use Policy restricted to research and education, as D7 of this page records, and its backbone was terminated on April 30, 1995, when its regional networks passed principally to internetMCI and SprintLink, which, in the words of Merit Network, the operator of record, absorbed the NSFNET regionals as their customers, so the NSFNET’s member networks joined the Internet as customers on terms the NSFNET never offered, and the NSFNET itself ended and did not become the Internet.

D1.4 The trait that defines the Internet has a documented origin outside the gated networks: the release of March 25, 1991 by General Atomics, Performance Systems International, Inc., and UUNET Technologies, Inc., seated at F52 of this page, states that the three networks “are not subject to government mandated “acceptable use” restrictions on their traffic,” states that the agreement can be expanded “to include any commercial service which has no restrictions on traffic use,” and states that the exchange allows firms to communicate “without traversing the government restricted backbones, such as the NSFNET (National Science Foundation Network),” so the Internet was built by agreement among commercial networks to carry traffic around the gated backbone, and the Internet did not grow out of the gated backbone.

D1.5 The ARPANET, the NSFNET, and the Internet each performed internetworking under D3, and a shared function is not a shared lineage: RFC 2026, The Internet Standards Process, Revision 3, by Scott O. Bradner of Harvard University, published October 1996, states at its section 1.1 that “There are also many isolated interconnected networks, which are not connected to the global Internet but use the Internet Standards,” so a network that uses the same protocols as the Internet is a user of the same tools and is not thereby the Internet or its ancestor. A redwood and a palm are both called trees, and a redwood did not grow from a palm, and a palm cannot become a redwood; the gated internets of the ARPANET and the NSFNET and the capital-I Internet are both called internets, and the shared word names a shared function and not a shared tree. The shared word was applied to the gated networks in error, and this record documents the error by document and date: the Stanford University bronze dedicated July 28, 2005 casts the headline “BIRTH OF THE INTERNET” above an inscription that records protocol work, as Stanford University Is Petitioned to Retract the Headline of Its BIRTH OF THE INTERNET Plaque records; RFC 1208, A Glossary of Networking Terms, by Ole J. Jacobsen and Daniel C. Lynch of Interop, Inc., published March 1991 as a document that in its own words “does not specify an Internet standard,” calls the ARPANET the “grandfather” of today’s Internet with no document for the descent it asserts; and IEEE Milestone 94 of October 29, 2009 is titled “Birthplace of the Internet, 1969,” as F46.1 of this page records.

D1.6 The registry lineage named in D1 is a continuity of numbering administration, the assignment of network addresses and autonomous system numbers by the Network Information Center at SRI, then by the InterNIC, and today by ARIN, and the registry lineage is not a lineage of networks: the Network Information Center at SRI kept the Official Host Table of the ARPANET’s era, as D4 of this page records, and a number assigned by a registry admits no one to any network, so the continuity of the numbering places no gated network in the lineage of the Internet.

D1.7 On every page of marknichols.com, the ARPANET and the NSFNET are named earlier gated networks, networks that also performed internetworking, or intranets under D2, and no page of marknichols.com calls either network the grandfather, the ancestor, the parent, the precursor, or the forerunner of the Internet, places either network in the lineage of the Internet, or states that either network became, evolved into, or grew into the Internet, under the ruling of Mark Nichols of November 7, 2026 that the ARPANET and the NSFNET belong to the history of internetworking and not to the lineage of the Internet, and that the Internet is a separate species.

D1.8 The plain statements of D1.1 through D1.7 are these. The ARPANET is not the Internet. The NSFNET is not the Internet. The ARPANET did not become the Internet. The NSFNET did not become the Internet. The ARPANET is not the grandfather, the ancestor, the parent, or the precursor of the Internet. The NSFNET is not the grandfather, the ancestor, the parent, or the precursor of the Internet. The ARPANET was an intranet, because the Advanced Research Projects Agency of the United States Department of Defense owned the ARPANET and admitted the ARPANET’s members by permission. The NSFNET was an intranet, because the NSFNET backbone admitted members only under a written Acceptable Use Policy restricted to research and education. The Internet admits anyone, and open admission is the one property that defines the Internet. Open admission came to the Internet from the commercial networks PSINet, AlterNet, and CERFnet at the Commercial Internet eXchange announced on March 25, 1991, and open admission did not come from the ARPANET or from the NSFNET. The ARPANET ended in 1990. The NSFNET backbone ended on April 30, 1995. The ARPANET, the NSFNET, and the Internet share the function of internetworking and share the word internet, and a shared function and a shared word are not a shared lineage. The Internet was born in 1991, and the Internet was not born from the ARPANET or from the NSFNET.

D2. intranet. A network, at any scale, in any geography, and under any protocol, whose members join by an owner’s permission. The word carries its own definition: intra means within, and an intranet is a network within a bounded and credentialed community, whether that community is one company’s offices or one government’s contractors spread across two continents. Scale does not convert an intranet into the Internet, geography does not, and protocol does not, because a gated network that adopts the optional protocols TCP/IP has changed its plumbing and not its admission policy; only open admission makes the Internet, and a research intranet is not the Internet. NSFNET and ARPANET are historical examples of intranets under this definition. Neither was the Internet, and neither became the Internet merely by being technically interconnected with other networks.

D3. internetworking. The technique of interconnecting distinct networks through gateways so that traffic originating on one can reach hosts on another. Internetworking among gated intranets was operating in production by 1975, when the gateway at University College London, developed and operated by Peter Kirstein’s group, of which Peter Higginson was a principal member, joined the ARPANET to the United Kingdom’s EPSS, an operation documented in the September 1975 paper of Peter L. Higginson and Andrew J. Hinchley, which recorded the working gateway while filing the Cerf and Kahn protocol as a future option rather than the operating method. Internetworking among gated intranets makes a lowercase internet, in the exact lowercase vocabulary of RFC 1983, and it never makes the capital-I Internet, because interconnecting two gated networks produces a larger gated system, not a public one. The credit for internetworking belongs to the engineers who built and operated the gateways; that credit does not extend to the birth of the Internet, which did not yet exist.

D4. ARPANET, also rendered DARPANET. The ARPA Network: one organization’s intranet, built, funded, owned, and access-controlled by the Advanced Research Projects Agency of the United States Department of Defense, later renamed DARPA, from its commissioning in 1969 until its decommissioning in 1990. Its very name is a possessive, the agency’s initials welded onto the agency’s property, and the network’s renamings followed the owner’s renamings, as only an owned network’s can. Admission was by the owner’s authorization for the owner’s purposes, the Official Host Table of the Network Information Center at SRI, the register of the era’s hosts that preceded the optional protocol DNS, listed 235 hosts in May 1982 and 562 hosts in August 1983, the two counts in RFC 1296 of January 1992 that bracket the 1983 protocol cutover, and no member of the public could join it, buy from it, or sell across it on any day of its twenty-one years. The owner stated the network’s purpose in its own procurement instrument before the network existed: Request for Quotations No. DAHC15 69 Q 0002, issued July 29, 1968 by the Defense Supply Service-Washington of the Department of the Army for the Advanced Research Projects Agency under ARPA Order No. 1260, and signed by Thomas J. Scheblik, Deputy Director for Procurement, solicited the Interface Message Processors for the ARPA computer network, and its Statement of Work, Specifications of Interface Message Processors for the ARPA Computer Network, states that the Agency was forming the network “with the cooperation of its research contractors,” that the network’s potential lay in “making these advanced research computer systems available to users outside their own design circle,” and that the network itself was “a subject of study and experimentation,” while the Statement of Work’s nineteen pages and seven appendices contain no reference to war, to survivability, to attack, to command and control, or to any military mission. The design mission of the ARPANET was therefore resource sharing among the owner’s research contractors, stated by the owner in 1968, and the later recollections agree with the instrument: Charles Herzfeld, Director of ARPA from 1965 to 1967, stated that the ARPANET was not started to create a command and control system that would survive a nuclear attack; Vint Cerf recorded on the Internet Society’s internet-history list on September 1, 2009 that Larry Roberts confirmed the purpose of the ARPANET was resource sharing and that the nuclear resilience story came from Paul Baran’s earlier work; and the Internet Society’s own history, A Brief History of the Internet, calls that story a false rumor that arose from the unrelated RAND study. The wartime mission, command traffic surviving damaged links and destroyed nodes, belonged to the owner’s later internetting project, which Vint Cerf managed at DARPA and demonstrated by putting packet radios in Strategic Air Command aircraft, and the optional protocol TCP, specified in 1974 with military computer communication requirements as the stated primary focus of RFC 793 of September 1981, was designed for that mission and installed on this intranet by the owner’s directive in 1983. The ARPANET is not the Internet, and DARPANET is not the Internet: one organization’s intranet is not the publicly joinable network of networks. The ARPANET intranet was procured under Request for Quotations No. DAHC15 69 Q 0002 of July 29, 1968, ran from 1969, and carried its traffic for fourteen years, under the Network Control Program, an optional protocol first specified in RFC 33 of February 1970, before TCP was added to it on January 1, 1983; a protocol added to a working network fourteen years after the network was procured is an add-on to that network, not its birth.

D5. Flag day, January 1, 1983. A scheduled protocol cutover, from NCP to TCP/IP, planned within the ARPANET community for years and executed on the owner’s own plant: an intranet’s internal maintenance event, touching no member of the public because no member of the public was on the network before the cutover or after it. The protocol installed that day was commissioned by the same owner to weld its own three networks together, the terrestrial ARPANET, its mobile packet radio network, and its satellite network, crossing dissimilar media under a single owner without ever crossing an owner, so that traffic could survive battlefield destruction. The Internet’s own standards registry graded TCP “Recommended” and never “Required,” in RFC 1200 of April 1991 and RFC 2200 of June 1997, grades that bind only systems electing to implement the standard suite, and a protocol cutover on a gated intranet is not the birth of anything. The network the protocol was cut over onto had been procured on July 29, 1968 and running since 1969, fourteen years before that day, so the cutover added a protocol to an existing intranet and created no network.

D6. The Internet protocols, the optional protocols TCP and IP. Protocols are utilities whose messages the networks carry; they are not the networks, and they are not the Internet. Under these Governing Definitions, TCP and IP are optional protocols, and paragraphs D6.1 through D6.13 state the documents on which that definition rests and the judgment of Mark Nichols that completes it.

D6.1 The Internet’s own standards registry, issued first by the Internet Activities Board and later by the Internet Architecture Board, under the title IAB Official Protocol Standards and from RFC 1500 of August 1993 under the title Internet Official Protocol Standards, assigned a status to each listed protocol in twenty-two editions, from RFC 1083 of December 1988 through RFC 2400 of September 1998.

D6.2 Every one of those twenty-two editions lists TCP, the Transmission Control Protocol of RFC 793, at the status “Recommended”, printed “Rec” from RFC 1280 of March 1992 onward, and lists IP, the Internet Protocol of RFC 791, at the status “Required”, printed “Req” from RFC 1280 onward, and not one of the twenty-two editions lists TCP at the status “Required” in any of its tables.

D6.3 RFC 1200 of April 1991, issued by the Internet Activities Board with Jon Postel as editor, and RFC 2200 of June 1997, issued by the Internet Architecture Board with Jon Postel as editor, each define the status “Required” at section 4.2.1 in the words “A system must implement the required protocols”, define the status “Recommended” at section 4.2.2 in the words “A system should implement the recommended protocols”, and define the status “Elective” at section 4.2.3 in the words “A system may or may not implement an elective protocol”, so that by the registry’s own definitions TCP is a protocol that a system should implement and is not a protocol that a system must implement.

D6.4 RFC 1200 of April 1991 and RFC 2200 of June 1997 each open by stating that the edition “describes the state of standardization of protocols used in the Internet” as determined by its board, and each states that “Few protocols are required to be implemented in all systems” because of the variety of possible systems, gateways, terminal servers, workstations and multi-user hosts among them.

D6.5 RFC 1122, Requirements for Internet Hosts -- Communication Layers, edited by Robert Braden for the Internet Engineering Task Force in October 1989 and listed at the status “Required” in RFC 2200 of June 1997, states at its section 1.1.3 that “To communicate using the Internet system, a host must implement the layered set of protocols comprising the Internet protocol suite” and, in the next sentence, that “A host typically must implement at least one protocol from each layer”, so RFC 1122 binds a host that has chosen to communicate using the Internet system, and RFC 1122 requires of that host at least one transport protocol, not TCP.

D6.6 RFC 1122 of October 1989 states at its section 1.1.3 that “There are two primary transport layer protocols at present”, naming TCP and UDP, and that “the set of official Internet transport protocols may be expanded in the future”, states at its section 4.2.1 that “TCP is used by those applications needing reliable, connection-oriented transport service”, and states at its section 4.1.1 that “UDP is used by applications that do not require the level of service of TCP”, so RFC 1122 itself assigns TCP by the needs of the application.

D6.7 RFC 1200 of April 1991 and RFC 2200 of June 1997 each list, at section 6.3, Network-Specific Standard Protocols, the transmission of IP over each type of physical network, ARPANET, X.25, Ethernet, IEEE 802, FDDI and serial lines among them, at the status “Elective”, and each states that “it is elective to support any particular type of physical network” on which IP is transmitted.

D6.8 RFC 2500 of June 1999 prints no status for TCP or for IP, RFC 5000 of May 2008, the last edition of the registry, prints no status for TCP or for IP, and RFC 7100 of December 2013, written by Pete Resnick of Qualcomm Technologies, Inc., obsoletes RFC 5000 and requests that RFC 5000, and therefore STD 1, be moved to Historic status, so the last status that the Internet’s own standards registry ever assigned to TCP is “Recommended”, in RFC 2400 of September 1998.

D6.9 The IP that the registry listed at the status “Required” is version 4 of the Internet Protocol, RFC 791, and the Internet Engineering Task Force standardized a second and separate Internet Protocol, version 6, in RFC 8200 of July 2017, STD 86, by S. Deering and R. Hinden. RFC 6540 of April 2012, BCP 177, titled IPv6 Support Required for All IP-Capable Nodes and written by W. George of Time Warner Cable, C. Donley of CableLabs, C. Liljenstolpe of Big Switch Networks and L. Howard of Time Warner Cable, advises that “IPv6 support is no longer considered optional”, cautions that the term “IP” has become “a generic that can mean IPv4 + IPv6, IPv6-only, or IPv4-only, depending on context and application”, and states that new and updated IP networking implementations “must not require IPv4 for proper and complete function”, so the Internet Engineering Task Force itself used the word optional for an Internet Protocol until April 2012, and the IP version that the registry listed at the status “Required” is, under the Best Current Practice of April 2012, a version that no new or updated implementation may require.

D6.10 The suite’s own members prove reliability is a per-application choice, because the optional protocols UDP of RFC 768, RTP of RFC 1889 of January 1996, which RFC 3550 of July 2003 obsoletes, and QUIC of RFC 9000 all decline TCP’s services while each remains a protocol of the Internet standards track.

D6.11 TCP is an evolutionary option, not a permanent fixture: it replaced NCP on the owner’s intranet in the 1983 cutover, UDP stood beside it from 1980 for applications that declined its services, RTP went around it in 1996 for media that could not wait for retransmission, and QUIC, published in May 2021, is displacing it now by moving reliability into a new protocol carried inside UDP datagrams; the protocols rotate while the Internet persists, and a layer whose occupants rotate is by definition not the thing itself.

D6.12 It is the stated judgment of Mark Nichols that both are optional utilities: TCP optional on the registry’s own grade, and IP optional as a specific protocol, because the registry’s “Required” grade is conditional conformance language that binds only systems electing to implement the standard suite, the election being made before the grade applies, as the words “To communicate using the Internet system” of RFC 1122 and the word optional that RFC 6540 applies to IPv6 both record, and because what internetworking requires is the addressing function, the label that says where a packet should go, while IP is one implementation of that function and not the function itself.

D6.13 Hence the rebrand coinages stated at marknichols.com/internet-protocols/: TCP is better named ESFRP, the Endpoint Segment Failure Retry Protocol, and IP is better named ALP, the Address Label Protocol. The postmen are not the post office, and the protocols are not the Internet.

D7. NSFNET. The National Science Foundation’s backbone, 1986 to 1995: a federation of research intranets joined into a lowercase internet under a written Acceptable Use Policy that restricted carriage to research and education and barred commercial traffic. The dismantling is dated by the operator of record, Merit Network: the replacement architecture was awarded early in 1994, the very high speed Backbone Network Service to MCI and the Network Access Points to Sprint, MFS Datanet, and Bellcore representing Ameritech and PacBell; member networks began moving off in November 1994; the backbone was terminated on April 30, 1995; and the regional networks passed principally to the commercial carriers internetMCI and SprintLink, which, in Merit’s own words, absorbed the NSFNET regionals as their customers. The NSFNET is not the Internet: a backbone admission-screened under a written Acceptable Use Policy restricted to research and education is a gated network, and a gated network is not the publicly joinable network of networks.

D8. The World Wide Web. An application design made by many persons inside and outside CERN, announced publicly on August 6, 1991, three programs of CERN's World Wide Web software, the line-mode client, the basic server and the library of common code, released into the public domain by CERN on April 30, 1993, with NCSA Mosaic released in 1993 putting a graphical browser in front of it. A free application is not an open network: until April 30, 1995, the Web’s principal carriage was the gated research intranets beneath it, research-only carriage under the written policy, and the calendar states the dependency exactly, because CERN's three programs of Web software went public on April 30, 1993, and the gated research fabric beneath most of its hosts was absorbed into the public Internet two years later to the day, on April 30, 1995. The name World Wide Web is a label for a large body of technology in the public domain, made by many persons and bodies inside and outside CERN, as F32.4 of this page states. The World Wide Web is not the Internet: the Web is an application using the Internet platform, and the application is not the platform.

D9. The birth of the Internet, and the absorption. The capital-I Internet was born in 1991, when PSINet, AlterNet under UUNET, and CERFnet, independently operated commercial networks of the registry lineage, established the Commercial Internet eXchange, a settlement-free router interconnection with open admission and no purpose-screening policy, as recorded in the Federal Communications Commission working paper The Digital Handshake by Michael Kende and as announced by the three networks’ operators themselves, General Atomics, Performance Systems International, Inc., and UUNET Technologies, Inc., in their release of March 25, 1991, which states that “The CIX agreement provides for all customers of AlterNet, CERFnet and PSINet to exchange Internet traffic directly, regardless of which network the customer obtains service from, and at no additional cost” and that the three “are not subject to government mandated “acceptable use” restrictions on their traffic,” the release being preserved as message 441 of the com-priv archive at the Massachusetts Institute of Technology and seated at F52 of this page; the agreement’s own text and its execution date are still sought, and the ruling stands on the dated announcement, the year, the parties, and the terms until a dated earlier instrument of the same lineage is produced. April 30, 1995 is not the Internet’s birthday; it is the absorption: the day the last written admission policy over the general-purpose research backbone died with the NSFNET, the regional networks passed principally to internetMCI and SprintLink, and the populations that had lived behind the gate joined the Internet that had existed without them since 1991. Being born is not the same as being built, and the Modern Internet, publicly accessible, eCommerce native, media streaming native, and QoS native, was built from 1996 to 1997 on executed documents: the Telecommunications Act signed February 8, 1996, autonomous system AS6553 issued August 29, 1996 by the InterNIC, the $300,000 Cisco Systems agreement of November 1996 to host cisco.com on Digital Island’s Tier-0 network, and production service in the first quarter of 1997, with Cisco Systems, Stanford University, and Visa International as the first customers in sequence.

D10. The Modern Internet. The Internet changed from the legacy Internet to the Modern Internet on the day its internetworking changed from best effort to deterministic, and that day is November 1, 1996, the Effective Date of the Cisco Systems Remote Data Services Agreement, signed for Digital Island, Inc. by Mark Nichols, Director, Global Networks, on November 7, 1996 and for Cisco Systems, Inc. by Hervé Goguely, Director, Global Service Management, on November 8, 1996, under which Cisco Systems became the first customer to buy a contractually guaranteed global service, a network segment exclusively its own with secure transaction services and sub-300 milliseconds round trip, on the architecture Mark Nichols hand-drew in June 1996, redrew as DIGITAL ISLAND DRAFT.1 in July 1996 and DRAFT.2 in October 1996, and registered as AS6553, issued to Digital Island, Inc. on August 29, 1996. An evolution, not a synonym. The capital-I Internet born in 1991 and made general-purpose by the absorption of April 30, 1995 was public but bare: a network anyone could join, and nothing commerce-grade could yet depend on, because open admission supplies members and does not supply performance. The Modern Internet is what that public network evolved into when global commerce was engineered onto it: the enabling of the globalization of eCommerce, of streaming media, and of Quality of Service under signed and enforceable terms, built on Digital Island’s Tier-0 network under autonomous system AS6553 with contractually enforced sub-300-millisecond round-trip performance across major markets, carrying the Merchant Transport product category coined in September 1996, on the architecture designed by Mark Nichols as co-founder and chief architect, the record standing at marknichols.com/architect-of-the-modern-internet/, marknichols.com/merchant-transport/, and marknichols.com/tier-0/. The evolution is dated by the executed record and by the customers who ran on AS6553 in sequence: Cisco Systems in November 1996, Stanford University in 1997, Visa International in the second quarter of 1997, E*TRADE under its global data distribution agreement with Digital Island dated August 1, 1997, as Digital Island’s S-1 records it, Charles Schwab in 1998, and MasterCard in March 1999; Telefónica Data formed a global IP alliance with Digital Island on April 26, 1999, Sun Microsystems and Inktomi invested in Digital Island in December 1999, Microsoft, Intel, and Compaq invested in Digital Island in June 2000, and CERNET, the China Education and Research Network, peered with Digital Island under the contract signed in Beijing on February 25, 1998 and was never a customer. The Modern Internet is therefore dated 1996 to 1997 in executed documents, and the word modern means publicly accessible, commerce-grade, streaming-capable, and QoS-governed, none of which the newborn network possessed.

D11. Usage. On every page of this site, Internet with a capital I means the publicly joinable network of the registry lineage born in 1991 and nothing else; internet in lowercase means any interconnection of networks, including gated ones; gated systems are named what they were, research intranets, whatever their date; and any page, headline, plaque, or biography that assigns the birth of the Internet to 1969, 1974, or 1983 is measured against these definitions and fails, because on each of those dates every network in the claim admitted its members by permission, and any account that assigns the birth to April 30, 1995 is measured against these definitions and fails as well, because on that date the Internet already existed and what died was the gate beside it. And on every page of this site, “Required” as a registry grade appears only in quotation marks with its condition stated in the same sentence, that it binds only systems electing to implement the standard suite, except within D6 of this page, where D6.12 states that condition once for every quotation of the registry in D6.1 through D6.11; this site’s own prose never calls any Internet protocol required, because at the level of Internet membership there are no required protocols, only elected ones, and an unconditional “required” applied to an Internet protocol is the registry’s conditional conformance label promoted into a membership law that no document states.

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.