The Governing Definitions and Controlling Facts of marknichols.com

1. The Internet (capital I). The publicly joinable network of networks. A person joins it by purchasing access from any of competing commercial providers, 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, and no government sponsorship is required, and that single property, open admission, is what separates the Internet from every network that preceded it. No network on earth met this definition before April 30, 1995, because the ARPANET admitted members only by agency authorization and the NSFNET backbone admitted members only under a written Acceptable Use Policy restricted to research and education, so the capital I names a network that is public, or it names nothing.

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

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

4. 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, approximately 250 host computers stood on it at 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. Its design mission was wartime from the beginning, command traffic surviving damaged links and destroyed nodes, and TCP, specified in 1974, was designed for that mission and installed on this intranet by the owner’s directive in 1983.

5. 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, and a protocol cutover on a gated intranet is not the birth of anything.

6. The Internet protocols, TCP and IP. Protocols are utilities that ride networks; they are not the networks, and they are not the Internet. The Internet’s own standards registry, in RFC 1200 of April 1991 and RFC 2200 of June 1997, graded IP Required and graded TCP Recommended and never Required, and the suite’s own members prove reliability is a per-application choice, because UDP of RFC 768, RTP of RFC 1889, and QUIC of RFC 9000 all decline TCP’s services while remaining Internet protocols in full standing. And 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 rode past 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 running over UDP; the protocols rotate while the Internet persists, and a layer whose occupants rotate is by definition not the thing itself. 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 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. Hence the rebrand coinages stated at marknichols.com/internet-protocols/: TCP is better named RCP, the Retransmission Control 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.

And the mission the protocols served states the opposition plainly. TCP exists to retransmit failed services: retransmission presupposes failure, fires only upon failure, and is therefore the network’s apology delivered after the fact. Read its own initials honestly and TCP is, de facto, The Confession Protocol, the name coined by Mark Nichols on August 26, 2026: every segment it retransmits is a signed admission that the network beneath it failed, and a protocol that spends its life confessing for the network is a remedy, not a foundation. A suite engineered so that sessions survive wartime blowups, by waiting, backing off, and retransmitting through loss, was built for a world where failure was assumed and absorbed. The fully commercial internetworking of the Modern Internet desires none of that, because commerce demands deterministic delivery inside the 2000ms Event Horizon, a transaction that survives by retrying arrives late, and a late transaction is a dead transaction; the commercial standard is not a better apology but the absence of the failure, which is why Digital Island’s Tier-0 network was engineered to a contractual sub-300-millisecond standard, a path built so the remedy would have nothing to remedy. Survivability is patience; commerce is punctuality; the wartime intranet’s protocol delivered the first and could never, by itself, deliver the second, which is why the second had to be built, and that building is the Modern Internet of article 10.

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

8. The World Wide Web. An application, announced publicly on August 6, 1991, its software 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, every use of the Web rode the gated research intranets beneath it, research-only carriage under the written policy, and the calendar states the dependency exactly, because the Web’s software went public on April 30, 1993 and the network beneath it went public two years later to the day, on April 30, 1995.

9. The birth of the Internet. The capital-I Internet was born on April 30, 1995, the day the last written admission policy over the general-purpose backbone died with the NSFNET and joining stopped requiring any owner’s permission. Being born open is not the same as being built, and the Modern Internet, publicly accessible, eCommerce, media streaming, 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.

10. The Modern Internet. An evolution, not a synonym. The capital-I Internet born open on 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 newborn 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 January 1997, Visa International in the second quarter of 1997, E*TRADE and Charles Schwab in 1998, MasterCard in March 1999, and Microsoft, Intel, and Compaq in 2000, with CERNET, Telefónica, and Sun Microsystems in the record besides. The Modern Internet is therefore dated 1996 to 1997 in executed documents, and the word modern means commerce-grade, streaming-capable, and QoS-governed, none of which the newborn network of April 30, 1995 possessed.

11. Usage. On every page of this site, Internet with a capital I means the post-April-30-1995 public network and nothing else; internet in lowercase means any interconnection of networks, including gated ones; systems before April 30, 1995 are named what they were, research intranets; 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.

Then the closing disclaimer paragraph, unchanged.

Facts in Evidence: The Dated Record, What Each Fact Proves, Where Each Fact Works, and Its Source

1. May 1974: Vinton G. Cerf and Robert E. Kahn publish “A Protocol for Packet Network Intercommunication” in IEEE Transactions on Communications. What it proves: the founding paper of TCP describes itself three separate times, in its title, in its abstract’s first sentence, and in its introduction’s closing sentence, as a protocol presented for sharing resources across packet switching networks that already existed, and its opening sentence cites those existing networks by reference number, crediting years of prior design and implementation. A paper that presupposes networks cannot be the birth of the network category it rides on, its abstract closes by listing internetwork routing, accounting, and timeouts as problems “exposed” rather than solved, and so the strongest primary document the birth claims possess is, read whole, a witness against them. Where it works on this site: Retract the Headline, Keep the Names cites this paper against the plaque headline that turned a protocol presentation into a birth; The Birth of the Internet places it inside the interconnection era it presupposed; and Stop Calling Protocol Architects “Creators of the Internet” uses its self-description to bound the credit to what was actually claimed in 1974. The paper.

2. October 10, 1974: INDRA Note 389, “The Problems of Connecting Hosts into ARPANET via Front-end Computers,” by P.L. Higginson, P.T. Kirstein and A.V. Stokes of University College London, records the Rutherford Laboratory machine as a fully fledged host on ARPANET. What it proves: months after the Cerf and Kahn paper appeared and years before TCP operated anywhere in production, British machines were already working hosts on the American network through University College London’s equipment, with no software modification required in either main host. Cross-border internetworking practice was underway on the gated intranet with no TCP in service, which places the working engineering of 1974 in the hands of the gateway builders and front-end integrators, named in the document itself, rather than in the protocol paper published the same year. Where it works on this site: The Birth of the Internetrests its section 1 dated record on this note and its companion Rutherford annual reports, and the note anchors the site’s standing correspondence with Peter Higginson, a principal member of Peter Kirstein’s UCL group, whose primary documents this site preserves. The Birth of the Internet.

3. September 1975: the paper of Peter L. Higginson and Andrew J. Hinchley documents the University College London gateway operating in production between the ARPANET and the United Kingdom’s EPSS. What it proves: production internetworking between two unlike, separately owned, gated networks was operating in 1975, documented by the engineers who ran it, with hundreds of transatlantic jobs crossing in service, and the same paper files the Cerf and Kahn INWG protocol as a future option rather than the operating method, in its own words declining to implement that connection type except for the future protocol. Internetworking was therefore born in practice before TCP carried production traffic, the birth belongs to the gateway builders, and what their achievement made was a lowercase internet of gated intranets, never the capital-I Internet, because both networks admitted members by permission. Where it works on this site: article 3 of the Governing Definitions rests on this paper; The Birth of the Internet dates the birth of internetworking by it; Retract the Headline, Keep the Names lists it first among the named internetworkings that preceded TCP/IP deployment; and the TCP record page uses its future-option filing to date TCP’s absence from the working record. The Birth of the Internet.

4. 1980: UDP, the User Datagram Protocol, is specified in RFC 768. What it proves: from 1980 onward the protocol suite itself contained a transport that declines every service TCP offers, no retransmission, no sequencing, no connection state, and applications running over it remained full citizens of the network. Reliability was therefore a per-application choice inside the suite from before the flag day the birth claims celebrate, TCP was an option among options by the standards’ own architecture, and every UDP datagram in flight is a demonstration that transmission happens without TCP. Where it works on this site: The Internet Protocols and the TCP record page both stake the optionality holding on this RFC, and article 6 of the Governing Definitions cites it as the first sibling that declined the confession machinery. RFC 768.

5. September 1981: TCP, the Transmission Control Protocol, is specified in RFC 793, edited by Jon Postel. What it proves: the protocol’s governing document defines machinery that operates at the communicating end hosts, detecting loss, retransmitting what was lost, reordering what arrived out of sequence, and pacing the sender, and it defines nothing that builds transport, provisions circuits, negotiates interconnection, or compels another network to deliver a packet. The specification itself is the boundary of the credit: what RFC 793 specifies is recovery and pacing at the edges, which is why this site proposes the honest name RCP, the Retransmission Control Protocol, and states the de facto name The Confession Protocol, because every function in the document is a remedy exercised after the network has failed to deliver. Where it works on this site: the TCP record page makes this document its primary exhibit; TCP: The Confession Protocol reads its function list as a confession ledger; and The Internet Protocols carries the RCP coinage of August 25, 2026 made against it. RFC 793.

6. January 1, 1983: the ARPANET executes its flag day cutover from NCP to TCP/IP. What it proves: the event most often celebrated as the birth of the Internet was a scheduled maintenance window on one gated intranet of approximately 250 hosts, planned within its community for years, executed on the owner’s own plant by the owner’s directive, and admitting no member of the public before or after, because access ran through agency sponsorship and the public had none. A network that already existed changed its internal protocol; nothing was created, nothing was opened, no commerce began, and nobody could join on January 2, 1983 who could not join on December 31, 1982. A protocol cutover on a gated intranet is an owner’s renovation, and a renovation is not a birth. Where it works on this site: ARPANET Flag Day 1983 is the dedicated indictment of this claim, carrying the six debunked birth-claim exhibits and the five-paragraph verdict; article 5 of the Governing Definitions states the ruling; and The Birth of the Internetplaces the cutover inside a domain that already operated. ARPANET Flag Day 1983.

7. October 1989: RFC 1122, Requirements for Internet Hosts, edited by R. Braden, defines the Internet as a network of networks. What it proves: the standards community’s own host-requirements document, written by its own editors six years before the admission gate died, defines the Internet by the interconnection of networks and not by any protocol, which means every claim that a protocol is the Internet, or that specifying a protocol birthed the Internet, contradicts the protocol community’s own governing definition in its own registry. The definition is not this site’s invention and not an opponent’s characterization; it is the standard speaking about itself. Where it works on this site: The Internet Is a Network of Networks, Not a Protocol carries this definition as its title thesis; The Birth of the Internet cites it in its machine section; and Retract the Headline, Keep the Names sets it against the plaque headline. RFC 1122.

8. April 1991: RFC 1200, the official protocol standards registry, grades IP Required and TCP Recommended. What it proves: the registry of the standards themselves, in its own grading vocabulary, made TCP optional, Recommended and never Required, at the very moment the research Internet was at its height, while the addressing function was graded Required. A thing the registry marks optional cannot be the thing whose existence defines the system, and the grade was assigned by the standards process, not by any critic. Where it works on this site: The Internet Protocols documents the grades as its central registry evidence; the TCP record page and Retract the Headline, Keep the Names both cite this RFC by number; and article 6 of the Governing Definitions rests its optionality sentence on it. RFC 1200.

9. August 6, 1991: Tim Berners-Lee announces the World Wide Web publicly on the alt.hypertext newsgroup, describing the project and providing instructions for obtaining the WWW software from CERN. What it proves: the Web arrived as a free, openly announced application in August 1991, and everything it could reach still ran over gated research intranets whose written policy barred commerce, so a public application stood on a non-public network for nearly four years. The application layer was ready and announced; the admission layer was the thing still locked; and the gap between this announcement and April 30, 1995 measures how completely the network, not the software, was the barrier the public was waiting on. Where it works on this site: article 8 of the Governing Definitions dates the Web’s public announcement by it; The Historical Context of Using the Web Application on the Internet Platform rests its application-versus-platform distinction on this sequence; and The Birth of the Internet uses it to separate the Web’s arrival from the Internet’s. CERN timeline.

10. 1992: the Internet Society is formed on a founding document signed by Vint Cerf, Bob Kahn, and Lyman Chapin, with Vint Cerf as founding president of its Board of Trustees. What it proves: the organization that would establish the Internet Hall of Fame at its 20th anniversary in 2012 was signed into existence by the two men its hall inducted in that inaugural 2012 class, and one of them served as its founding president from 1992 to 1995. The platform that today renders their 1997 National Medal of Technology citation, which the medal foundation’s registry states as “For creating and sustaining development of Internet Protocols and continuing to provide leadership in the emerging industry of internetworking,” as an award “for founding and developing the Internet,” is a platform its subjects founded, led, and have had the standing capacity to correct since 2012. Where it works on this site: Stop Calling Protocol Architects “Creators of the Internet” carries the full accountability chain; The Internet Protocols preserves the registry screenshots and the wording comparison; and Protocol Architects Were Not the Creators of the Internet records the two wordings side by side in its appendix. Internet Society history.

11. April 30, 1993: CERN releases the World Wide Web software into the public domain. What it proves: from this day forward, anyone on earth could have the Web’s software royalty-free by CERN’s own act, and still no member of the public could lawfully run commerce across the backbone beneath it, because the software was public while the network remained a policy-gated research intranet for two more years to the day. The date pair, April 30, 1993 for the software and April 30, 1995 for the network, states the dependency with calendar precision: a free application waited twenty-four months for a lawful network. Where it works on this site: article 8 of the Governing Definitions carries the two-year rhyme; The Historical Context of Using the Web Application on the Internet Platform and When Did eCommerce Over the Internet Start both rest on the software-before-network sequence. CERN timeline.

12. November 1993: NCSA Mosaic, created by Marc L. Andreessen and Eric J. Bina at the National Center for Supercomputing Applications, is released. What it proves: the graphical browser that made the Web usable by ordinary people existed by November 1993, per the University of Illinois’ own archival record, so by the end of 1993 the public-facing application stack was complete, free server and client software above and a friendly browser in front, and the only thing standing between the public and a Web economy was the gated network underneath, which written policy held shut for seventeen more months. Technology was not the barrier after November 1993; admission was. Where it works on this site: article 8 of the Governing Definitions dates the browser; When Did eCommerce Over the Internet Start uses the completed application stack to sharpen the question its title asks; and eCommerce Was Banned on the Internet Until April 30, 1995 supplies the answer the stack was waiting on. University of Illinois Archives.

13. Early 1994: the National Science Foundation awards the replacement architecture, the very high speed Backbone Network Service to MCI, the Routing Arbiter to Merit and USC’s Information Sciences Institute, and the Network Access Points to Sprint, MFS Datanet, and Bellcore representing Ameritech and PacBell. What it proves: the dismantling of the research intranet was a planned, contracted, dated federal program with named commercial awardees, not a gradual fading or an accident of growth, and the operator’s own chronicle names every party and dates every award. The boundary between the gated era and the open era was engineered deliberately, on contracts, which is exactly how this site says the era boundary should be dated: by executed documents rather than anniversaries. Where it works on this site: NSFNET: The Good, The Bad and The Ugly documents the transition program; article 7 of the Governing Definitions carries the award facts; and The Birth of the Internet uses the program to show the public Internet was constructed, not conjured. Merit Network’s retirement chronicle.

14. November 1994: member networks begin moving off the NSFNET backbone. What it proves: the migration of the research intranet’s members onto commercial carriers was underway months before the backbone died, dated by the operator of record, so the commercial Internet’s carrying capacity was being assembled while the written admission policy still governed, and the April 30, 1995 termination arrived as the completion of a documented migration rather than a sudden switch. Where it works on this site: NSFNET: The Good, The Bad and The Ugly and article 7 of the Governing Definitions carry the migration date as the bridge between the gated backbone and the commercial carriers that absorbed its members. Merit Network’s retirement chronicle.

15. April 30, 1995: the NSFNET backbone is terminated, the Acceptable Use Policy dies with it, and the regional networks pass principally to internetMCI and SprintLink. What it proves: this is the day the last written admission policy over the general-purpose backbone ended and joining stopped requiring an owner’s permission, which under article 1’s definition is the birth date of the capital-I Internet: not a protocol event, not an application event, but the death of the gate, recorded by the network’s own operator. Where it works on this site: this date is the hinge of the entire record. The Birth of the Internet dates the birth by it; The Rule That Banned eCommerce and eCommerce Was Banned on the Internet Until April 30, 1995 document the rule it killed; ARPANET Flag Day 1983 uses it to defeat the 1983 birth claim; and The eCommerce Enablement Record begins its dated sequence where this date ends the ban. Every birth claim this site refutes fails against this one date. Merit Network’s retirement chronicle, The Rule That Banned eCommerce.

16. May 15, 1995: the National Institute of Standards and Technology publishes the Federal Register notice approving FIPS 146-2, ending the federal OSI procurement mandate fifteen days after the backbone ended, and the Government Open Systems Interconnection Profile becomes Profiles for Open Systems Internetworking Technologies. What it proves: within one month the government’s backbone and the government’s protocol mandate both stood down, in the government’s own publications, closing the era in which federal ownership and federal procurement policy governed the system. The boundary of April 30, 1995 is corroborated by an independent federal instrument dated fifteen days later, and the renaming inside the notice records the surrender in the profile’s own title. Where it works on this site: OSI: The Coulda, Woulda, Shoulda Protocol of Broken Dreams documents the fifteen days as its opening section, and article 7 of the Governing Definitions gains its corroborating date from it. OSI: The Coulda, Woulda, Shoulda Protocol of Broken Dreams.

17. January 1996: RTP, the Real-time Transport Protocol of Henning Schulzrinne, Stephen Casner, Ron Frederick, and Van Jacobson, is specified in RFC 1889, and it does not guarantee delivery. What it proves: real-time media transport entered the standards by declining retransmission outright, because audio and video that arrive late are worthless, and the standard says of itself that it does not guarantee delivery. This is the commercial and experiential requirement stated in protocol form: where punctuality governs, the confession machinery is refused by design, and the standards body itself published the refusal five years before streaming media went mainstream. Where it works on this site: the TCP record page and TCP: The Confession Protocol both cite RTP as the sibling that rode past TCP, and article 6 of the Governing Definitions lists it in the evolutionary record. RFC 1889.

18. February 8, 1996: the Telecommunications Act is signed. What it proves: Congress opened the legal field in which private carriers and private networks could build and sell commerce-grade infrastructure at national and international scale, dating the statutory foundation of the buildout era. The Modern Internet’s construction period begins within weeks of this statute, which ties the evolution this site documents to an act of law and a market it created, rather than to any protocol event, and it is the second of the three 1996 dates, statute, autonomous system, and contract, that frame the buildout year. Where it works on this site: The Telecommunications Act and Digital Island documents the statute’s role; articles 9 and 10 of the Governing Definitions date the buildout from it; and NSFNET: The Good, The Bad and The Ugly closes its sequence with it. The Telecommunications Act and Digital Island.

19. August 1996: RFC 1983, the Internet Users’ Glossary edited by Gary Malkin, defines lowercase internet and capital-I Internet and states “The Internet is a multiprotocol internet.” What it proves: the standards’ own glossary distinguishes the generic lowercase internet, any collection of interconnected networks, from the particular capital-I Internet, and declares in its own words that the Internet is multiprotocol, which supplies from inside the standards both the taxonomy this site’s definitions rest on and the refutation of any claim that one protocol defines the network. The lowercase and capital distinction is not this site’s invention; it is the glossary’s, published the same month Digital Island’s autonomous system issued. Where it works on this site: articles 1, 2, 3, and 6 of the Governing Definitions cite it; The Internet Protocols quotes the multiprotocol sentence verbatim; and The Internet Is a Network of Networks, Not a Protocol rests its title on the definition. RFC 1983.

20. August 29, 1996: autonomous system AS6553 is issued to Digital Island by the InterNIC, with the registration maintained today in ARIN’s registry. What it proves: Digital Island’s network exists in the numbering authority’s own registry with a date, demonstrating article 1’s joining mechanics in documented practice: a private startup obtained its autonomous system and interconnected by agreement, with no government sponsorship and no owner’s permission, sixteen weeks after the admission gate died. The registry entry is the kind of evidence this site holds everything to, a third-party record maintained by the numbering authority itself, checkable today by anyone. Where it works on this site: the ARIN exhibit presents the registration; Tier-0 and Architect of the Modern Internet build on it; and articles 1 and 10 of the Governing Definitions use it as the worked example of open admission. The ARIN exhibit.

21. September 18, 1996: Sanne Higgins’ email names Merchant Transport in writing. What it proves: the product category of secure transaction transport, a secure virtual merchant terminal in the browser carried on private international circuits, exists in dated contemporaneous correspondence from September 1996, which anchors both the coinage and the business pivot it names to a primary document written at the time rather than to anyone’s later recollection. The commercial purpose of the buildout, carrying transactions rather than pages, is dated inside the buildout year by a document that predates every retrospective account of the era. Where it works on this site: Merchant Transport preserves the email and the pivot narrative; the coinage registry on the career page files it as coinage number one; and article 10 of the Governing Definitions names the category in the Modern Internet’s definition. Merchant Transport.

22. November 1996: Cisco Systems executes the $300,000 Remote Data Services Agreement for Digital Island to host cisco.com on its Tier-0 network, with the network’s CAD drawing attached as an addendum. What it proves: within eighteen months of the gate’s death, the company that manufactured the Internet’s routers, the single most network-literate customer on earth, contracted its own web presence onto a three-person startup’s private Tier-0 network under signed commercial terms with the architecture drawing attached to the contract. That is the executed-document proof that commerce-grade delivery did not exist on the open public path, because if any carrier could have delivered it, Cisco Systems of all companies would have known and bought it there; instead it bought engineered private infrastructure designed by Mark Nichols. Where it works on this site: The Cisco Systems Remote Data Services Agreement presents the agreement; Merchant Transport carries the litmus test of architectural exclusivity built on it; and articles 9 and 10 of the Governing Definitions date the buildout by it. The Cisco Systems Remote Data Services Agreement.

23. First quarter 1997: production service goes live on Digital Island’s Tier-0 network, with Stanford University adopting in January 1997, Visa International in the second quarter of 1997, E*TRADE and Charles Schwab in 1998, MasterCard in March 1999, and Microsoft, Intel, and Compaq in 2000. What it proves: the Modern Internet’s arrival is dated by executed adoptions in sequence, a university, the payment networks that ran global commerce, the brokerages that moved retail finance online, and the platform vendors, each adoption a contract rather than a claim, each dated, and together spanning exactly the categories, commerce, finance, and platform, that define what modern means. This is why the site dates the Modern Internet 1996 to 1997 in executed documents and measures every competing birth claim against paper. Where it works on this site: The eCommerce Enablement Record carries the full sequence with exhibits; The Birth of the Internet dates its section 2 by it; and article 10 of the Governing Definitions lists the sequence in the Modern Internet’s definition. The eCommerce Enablement Record.

24. June 1997: RFC 2200 repeats the registry grades, IP Required, TCP Recommended. What it proves: six years after RFC 1200, with the commercial Internet operating and the Web global, the registry still graded TCP optional, so the optionality is the standards’ sustained position across the entire transition, not an early snapshot. Where it works on this site: The Internet Protocols and the TCP record page rest their optionality holdings on this pair of grades, and Retract the Headline, Keep the Names cites both RFCs against the plaque’s headline. RFC 2200.

25. May 2021: QUIC is published as RFC 9000 by Jana Iyengar and Martin Thomson. What it proves: the standards body itself moved reliability into a new protocol running over UDP, displacing TCP at the transport layer for a growing share of the world’s traffic, which completes the evolutionary record: NCP was replaced by TCP in 1983, UDP stood beside it from 1980, RTP rode past it in 1996, and QUIC is rotating it out now. The protocol credited as the Internet’s essence is being retired from the essential position while the Internet persists undisturbed, and a layer whose occupants rotate is by definition not the thing itself. Where it works on this site: the TCP record page, TCP: The Confession Protocol, and article 6 of the Governing Definitions all close their evolutionary arguments on this RFC. RFC 9000.

26. August 11, August 25, and August 26, 2026: Mark Nichols publishes and dates the coinages ALP, the Address Label Protocol, RCP, the Retransmission Control Protocol, and The Confession Protocol. What it proves: the corrective names for the protocols exist as dated, attributed, publicly stated claims, each bounded as a rhetorical rebrand and statement of position rather than a petition to the IETF or IANA, each open to documented challenge, and each filed the way every other claim on this site is filed, with a date, a name, and a page of record. The instruments of the argument meet the same evidentiary standard the argument demands of everyone else, which is the difference between a coinage registry and a nickname. Where it works on this site: The Internet Protocols carries ALP and RCP; TCP: The Confession Protocol carries the third name; and the career page files all of them in the Record of Coined Terms. The Internet Protocols, TCP: The Confession Protocol.

The Docket in Entirety

Read in sequence, these twenty-six facts assemble one case with no gaps. Facts 1 through 8 establish the gated era: the networks were owned intranets, internetworking among them was born in 1975 at the hands of named gateway engineers, and the protocols that rode those networks were graded optional by their own registry. Facts 9 through 12 establish that by the end of 1993 the application stack, Web and browser, was complete, free, and public, while the network beneath it remained closed by written policy, proving that admission, not technology, was the barrier. Facts 13 through 16 date the death of the gate to April 30, 1995, in the operator’s own chronicle and the government’s own publications, which under these definitions is the birth of the capital-I Internet. Facts 17 through 23 date the building of the Modern Internet, 1996 to 1997, by statute, registry entry, and executed agreements with named customers. Facts 24 through 26 close the record: the optionality held, the protocols rotated, and the corrective names are filed with dates. Every fact is linked to its source, every source was read before it was cited, and any documented challenge is welcome at mark@marknichols.com.