Open Letter to Stanford University:
Retract the Headline, Keep the Names: An Open Letter to Stanford University on the “Birth of the Internet” Plaque
The Claim in One Sentence
The claim that the proposition of TCP/IP birthed the Internet is impossible.
The Claim, Stated Flat
RFC 1122 defines the Internet in seven words: “The Internet is a network of networks.” Every internetworking on the record below meets that definition, on dated records, before January 1, 1983, and most of them met it without TCP/IP at all. The definition the plaque’s own community later canonized was satisfied, repeatedly, in London, in France, across Europe, at Xerox PARC, and across the commercial world, before the protocol the headline credits was formalized. The birth the headline claims had already happened, more than once, and the record below names who did it and when. And the record below supports one sentence that ends the argument by itself: networks connected to networks without TCP/IP, in research and in commerce, before it and alongside it and after it, so networks connecting to networks never needed TCP/IP, and TCP/IP cannot be what gave networks-connecting-to-networks its existence.
Thus, the claim of TCP/IP birthed the Internet is impossible.
The full record follows: the plaque verbatim, the dated primary record, the named internetworkings, the protocol chronology, the logic, and the petition.
1. What This Letter Asks
Stanford University maintains a bronze plaque, dedicated on July 28, 2005, headlined “BIRTH OF THE INTERNET.” This letter asks Stanford to correct the headline and keep everything else. The names on the plaque belong on the plaque, the dates in the body are in the main accurate, and the headline miscategorizes the accurate body beneath it, so the correction is one line of bronze: replace “BIRTH OF THE INTERNET” with “THE CONCEPTION OF AN OPTIONAL INTERNET ARCHITECTURE: TCP/IP.”
That replacement headline is not rhetoric; it is the grade the Internet’s own standards registry assigned. RFC 1200, the IAB Official Protocol Standards of April 1991, lists IP as Standard and Required, and TCP as Standard and Recommended, and RFC 2200, the same registry in June 1997, carries the same two grades unchanged. The full registry record is examined at Internet Protocols. TCP, the protocol the plaque’s body chiefly commemorates, was never graded Required by the registry of the very network it is credited with birthing. If “optional” reads as too plain for bronze, the fallback is plainer still: “THE CONCEPTION OF TCP/IP.” Either headline matches the body. The current headline does not.
2. The Plaque, Verbatim
[PLAQUE TRANSCRIPTION EXHIBIT: the full verbatim text of the bronze is inserted here upon letter-perfect verification against the photographs.]
Pending that exhibit, the load-bearing lines are quoted exactly as they appear on the bronze. The headline reads “BIRTH OF THE INTERNET.” The body states that the Internet architecture and the Transmission Control Protocol were conceived by Vinton G. Cerf and Robert E. Kahn during 1973, Cerf at Stanford’s Digital Systems Laboratory and Kahn at ARPA; that the work became known at a networking conference in England in September 1973; that the seminal paper was published in May 1974; that Cerf, Yogen K. Dalal, and Carl Sunshine wrote the first full TCP specification in December 1974; and that early implementations were tested by BBN, Stanford, and University College London during 1975. The body then states, in its own words: “BBN BUILT THE FIRST INTERNET GATEWAY, NOW KNOWN AS A ROUTER, TO LINK NETWORKS TOGETHER.” The body closes: “ULTIMATELY, THOUSANDS IF NOT TENS TO HUNDREDS OF THOUSANDS HAVE CONTRIBUTED THEIR EXPERTISE TO THE EVOLUTION OF THE INTERNET.”
3. What the Plaque’s Own Text Concedes
Read the bronze strictly and two things follow.
First, the word “birth” appears only in the headline. The body claims conception during 1973, publication in May 1974, specification in December 1974, and testing during 1975, and conception, publication, specification, and testing are the vocabulary of design work, which the body uses with discipline. Nowhere does the body claim that an operational Internet came into existence at Stanford on any date, and the closing line concedes that the Internet is the work of thousands by “EVOLUTION,” not by birth. The headline makes a claim that the body it headlines declines to make.
Second, the plaque’s own gateway line concedes the mechanism. “BBN BUILT THE FIRST INTERNET GATEWAY, NOW KNOWN AS A ROUTER, TO LINK NETWORKS TOGETHER” states, in Stanford’s own bronze, that a built machine links networks together. That is correct, and it decides the category question: networks are interconnected by gateways, which are machines that are built, powered, configured, and operated, and not by protocol specifications, which are documents. A specification can define the envelope a gateway forwards, but the forwarding is done by the gateway. The plaque says so itself.
And the builder has a name, standing in the plaque’s own fine print: Virginia Strazisar, listed under BBN in the roster below the headline. The Internet Hall of Fame, operated by the Internet Society, inducted her in 2021 as Virginia Strazisar Travers, and its own citation states that she “designed and wrote the software that created Internet gateways, the precursor to routers and the core component that allows dissimilar networks to connect.” Read that citation against this headline. The custodians of Internet history have already conceded, in their own published words, that the core component of interconnection is the gateway, and the engineer who built BBN’s stands in the roster while the headline above her credits the conception.
4. What the Dated Record Shows, 1973 to 1976
University College London joined the ARPANET on July 25, 1973. That date is stated by Peter L. Higginson, a principal member of Peter T. Kirstein’s group at University College London, the group that developed and operated the UCL gateway, and Higginson wrote the operational gateway code himself.
INDRA Note 389 of October 10, 1974, “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, documents the front-end architecture of that work on dated paper. The Rutherford Laboratory’s 1974 annual report records a working transatlantic link, the laboratory’s 1975 annual report carries the work forward, and the 1976 report shows the service arriving, all on dated, archived, institutional paper. The full dated record is maintained, with citations, at Birth of the Internet.
In September 1975, Peter L. Higginson and A.J. Hinchley published the gateway problem in one sentence that has not aged: “In the longterm, either all networks must use substantially the same network protocol (tending to one global network), or a gateway of considerable complexity is required.” That sentence, written in 1975 by an engineer whose name is on this plaque, states the whole internetworking problem and its two solutions, in the NCP era, with TCP running nowhere in production.
The interconnection itself happened on that same record. The United Kingdom’s Experimental Packet Switched Service, EPSS, was a packet network distinct from and incompatible with the ARPANET, and the UCL gateway joined them. Peter L. Higginson’s own judgment, given to me in writing in August 2026, reads: “So I think EPSS was a genuine network to network link.” I state this conservatively: Higginson does not recall accessing an EPSS computer from the ARPANET side, so I claim exactly what the documents and the participant state and no more. What remains is a dated, primary-source record of unlike networks joined by an operated gateway in 1975 and 1976, seven years before TCP/IP became the ARPANET’s host protocol on January 1, 1983.
Peter L. Higginson’s name is on the plaque, under University College London, beside Deignan, Galland, Hinchley, Kirstein, and Stokes. Keep the names. The names are the best thing on the bronze.
5. Examples of First Internetworkings: A Network of Networks, Named and Dated
The category the headline claims for one campus was populated on both sides of the Atlantic, on dated records, by named engineers, and several of those engineers stand in this plaque’s own rosters. The category itself is documented at The Internet Is a Network of Networks, Not a Protocol.
London, 1973 to 1976. The record is stated in full in Section 4 and maintained at Birth of the Internet: Peter L. Higginson, Peter T. Kirstein, and A.V. Stokes of University College London, the operated UCL gateway, the Rutherford Laboratory annual reports of 1974, 1975, and 1976, and the EPSS interconnection of 1975 and 1976, a genuine network to network link in the NCP era. That interconnection meets the definition RFC 1122 would later write down, a network of networks, and it ran with no TCP in production anywhere on earth.
France, 1972 to 1976. CYCLADES, designed and directed by Louis Pouzin, began design and staffing in 1972, ran its first demonstration in November 1973 with three hosts and one packet switch, and by 1976 stood in full deployment at twenty nodes with connections to the NPL network in London, to ESA in Rome, and to the European Informatics Network. Pouzin coined “catenet” in 1973, in a note circulated to the International Network Working Group, five years before IEN 48 wrote under the category’s name. CYCLADES interconnected with networks in two other countries by 1976: that meets the definition, a network of networks, and none of it ran on TCP/IP.
Europe, 1976. The European Informatics Network, EIN, built under the European COST 11 project with Derek Barber in the leading role, was operational in 1976 and interconnected national research networks across borders, including the NPL network in London and CYCLADES in France. That meets RFC 1122’s definition, a network of networks, spanning nations, in production, in 1976, thirteen years before RFC 1122 wrote the definition down.
The BBN gateways, 1976 to 1977. By the Internet Hall of Fame’s own published citation, Virginia Strazisar’s gateway software connected the ARPANET with the mobile Packet Radio Network in 1976, and then connected the Atlantic Packet Satellite Network with the ARPANET node at University College London, and the November 1977 demonstration sent a message an estimated 88,000 miles in under three seconds across the three networks. Three unlike networks joined by operated gateways meets the definition, a network of networks, and it was met by the gateway engineer’s software, not by the specification.
Xerox PARC, 1974 to 1979. The PUP internetwork architecture, designed by David R. Boggs, John F. Shoch, Edward A. Taft, and Robert M. Metcalfe, was substantially complete in its fundamental design by 1974, and Xerox PARC report CSL-79-10 of July 1979, “Pup: An Internetwork Architecture,” documents an operational internetwork serving approximately 1,000 computers across 25 networks of five different types through 20 gateways, running on PUP and not on TCP/IP. Robert M. Metcalfe and John F. Shoch stand in this plaque’s own Stanford roster: two of the men the plaque honors built and documented an operational internetwork of twenty-five networks on a protocol family that was not TCP/IP. Twenty-five networks through twenty gateways meets the definition, a network of networks, at scale, in documented operation, and not one byte of it required TCP/IP.
The public X.25 world, 1975 to 1988. Telenet began operation in the United States in 1975, Datapac in Canada in 1976 was the first public data network designed for X.25, Transpac opened in France in December 1978, and the International Packet Switched Service, created in 1978 by Britain’s Post Office Telecommunications with Western Union International and Tymnet, reached Canada, Hong Kong, and Australia by 1981 and listed approximately 800 global sites by 1988. The national public networks were interconnected through X.75 gateways: commercial internetworking around the planet, in production for paying customers, without TCP. A planet of national networks joined through gateways meets the definition, a network of networks, commercially, and TCP was not on the invoice. The optionality that world proves is examined at TCP: The Optional Internet Protocol and at OSI.
Excluded by the same rule, stated for discipline. NORSAR and University College London joined the ARPANET in 1973 as hosts on one network, and ALOHAnet, operational in June 1971 under Norman Abramson at the University of Hawaii, reached the ARPANET in its later versions. Host connections to a single network are not internetworking, and this record excludes them for the same reason the birth claim cannot rest on them.
The claim, stated flat. RFC 1122 defines the Internet in seven words: “The Internet is a network of networks.” Every entry above meets that definition, on dated records, before January 1, 1983, and most of them met it without TCP/IP at all. The definition the plaque’s own community later canonized was satisfied, repeatedly, in London, in France, across Europe, at Xerox PARC, and across the commercial world, before the protocol the headline credits was formalized. The birth the headline claims had already happened, more than once, and the record above names who did it and when.
Sourcing, stated in the discipline this record uses. The London record of Section 4 stands on primary documents. The PUP record stands on the Xerox PARC report, linked above from the Computer History Museum’s PARC archive. The Strazisar record stands on the Internet Hall of Fame’s published citation. The CYCLADES, EIN, Telenet, Datapac, Transpac, and IPSS dates carry from the standard histories, linked above, with primary pulls pending, and documented corrections are welcome.
6. Protocol Milestones Inside a Domain That Already Existed
The protocol chronology, stated in order, settles the category. The concept of TCP was first described in 1974. The TCP/IP suite was demonstrated in 1977 across ARPANET, SATNET, and PRNET. UDP was defined in 1980. TCP was formalized in 1981. ARPANET did not transition from NCP to TCP/IP until January 1, 1983.
That timeline matters because it destroys the birth claim. The Internet did not first exist when TCP was proposed in 1974. It did not first exist when TCP/IP was demonstrated in 1977. It did not first exist when UDP appeared in 1980. It did not first exist when TCP was formalized in 1981. It did not first exist on 1983 Flag Day. Those were later protocol milestones inside a domain that already existed as an operational internetwork.
7. Protocol Is Not System
This is the core technical mistake, and it can be stated as plain logic. TCP is a protocol. UDP is a protocol. Protocols are methods used within a system. An internet is a system composed of interconnected networks. Therefore, a protocol is not the same thing as an internet. The IETF’s own glossary draws the same line: RFC 1983, the Internet Users’ Glossary, edited by G. Malkin and published in August 1996, defines an internet as “a collection of networks interconnected with routers” and states that “The Internet is a multiprotocol internet.” A glossary that calls the Internet multiprotocol cannot be defining it as one protocol suite.
What Cerf and Kahn did in 1973 and 1974 was real, it is dated, and it is theirs. They authored a common envelope format and an addressing methodology that gateway machines could implement, and Cerf, Dalal, and Sunshine specified TCP in full in RFC 675 of December 1974. Protocol design is methodology, the plaque’s body describes that methodology accurately in design-work vocabulary, and every name in its rosters earned its place. But a methodology does not birth a system, and the system’s own documents say what the system is. RFC 1122, Requirements for Internet Hosts, edited by Robert Braden and published in October 1989, states the definition in seven words: “The Internet is a network of networks.” Networks are built, interconnected, and operated, so a definition that names networks names infrastructure, not paperwork. The definitional record is examined at The Internet Is a Network of Networks, Not a Protocol.
Nor was this methodology the category’s first member. Interconnecting networks at scale requires an envelope of the IP class: hierarchical addresses a router can summarize, and a hop count so packets cannot circle forever. An addressing protocol of IP’s class is necessary; IP specifically is not, because the category was populated on all sides: Xerox built PUP and XNS, Novell built IPX, Digital Equipment Corporation built DECnet, and the ISO built CLNP. Louis Pouzin, designer of the French CYCLADES network, coined “catenet” for a concatenation of networks, and Cerf’s own 1978 internetworking memo, IEN 48, was titled “The Catenet Model for Internetworking.” The category preceded the brand, the brand’s own author wrote under the category’s name, and the registry that governs the brand graded its transport half optional: IP Required, TCP Recommended, in RFC 1200 of April 1991 and in RFC 2200 of June 1997, unchanged.
TCP provided one later transport option. It was useful for packet assurance across an already existing internet. But usefulness is not birth, and importance is not origin. Even TCP was not the final or universal answer, because many of the reasons people actually use the Internet involve timely communication, not perfect sequencing and retransmission: voice calls, live audio, live video, video conferencing, live sports streams, live music events, multiplayer gaming, telemetry, control signaling, sensor data, market data feeds, astronaut-to-ground communications, and other real-time, latency-sensitive traffic. In many of those cases, a late packet is less useful than a lost packet. People use the Internet for many things TCP is poorly suited to carry well, and that makes it illogical to equate TCP with the Internet itself.
And TCP is optional in operation, not merely in the registry. TCP is a retransmission mechanism: it detects symptoms and resends. On a network engineered so that loss is the exception, the retry function idles, and on a network where the path has failed, the retry accomplishes nothing, because no retransmission creates a circuit. The benefit of TCP is defined by the network beneath it, and that benefit is a maybe. You cannot birth a system with a maybe. Systems are born when circuits are lit, gateways are operated, and traffic passes. A protocol cutover is a maintenance window, and a protocol transition is not a birth. The engineering record of what TCP was designed for is examined at TCP: The Optional Internet Protocol.
8. Dependency Alone Defeats the Origin Claim
TCP/IP was designed to operate across multiple networks. That means TCP/IP presupposed the existence of those networks. A protocol designed to work across multiple networks depends on a system of multiple networks already being there as its operating condition. A method that depends on a system cannot constitute the creation of that system. That is not rhetoric. It is basic logic.
If there were no network-of-networks, there would be nothing for an internetwork protocol to internetwork. Even on Stanford’s most generous reading, TCP/IP is downstream of the condition it claims to have created. The statement that TCP/IP, or any protocol, birthed the Internet is, unto itself and on face value, patently false, impossible, and a dereliction of engineering history. The operational side of that condition is examined at Protocol Architects Were Not the Creators of the Internet and at Infrastructure Activation vs Transport Semantics.
9. Common Defenses, Answered in Advance
“The headline is shorthand.” Bronze is not shorthand; bronze is the claim of record, on a university campus, dedicated in a public ceremony on July 28, 2005, and universities of all institutions do not get to plead informality about their own monuments.
“Everyone knows what it means.” The plaque’s closing line proves the drafters knew the difference between birth and evolution, chose “EVOLUTION” for the body, and chose “BIRTH” for the headline. The precision exists on the plaque, and it is the headline that departs from it.
“The 1977 demonstration proved it.” The plaque does not mention the 1977 three-network demonstration, and this letter takes the plaque at its own text.
“The correction diminishes the honorees.” The opposite is true. The current headline forces every name on the bronze to carry a claim the body never makes, while the corrected headline lets the body’s accurate, dated, disciplined text speak for itself, and the names lose nothing except an overstatement they never wrote.
10. Findings and Petition
Findings. The word “birth” appears only in the plaque’s headline, and the plaque’s body claims conception, specification, and testing, not an operational birth. The plaque’s own text attributes the linking of networks to a built gateway. The primary documentary record assembled in this letter begins with the Rutherford Laboratory annual reports of 1974, 1975, and 1976, INDRA Note 389 of October 10, 1974, and the Higginson-Hinchley gateway paper of September 1975, all in the NCP era. The category was populated worldwide before the brand: CYCLADES and the European Informatics Network interconnected in Europe by 1976, the PUP internetwork at Xerox PARC was documented in 1979 at approximately 1,000 computers across 25 networks through 20 gateways, and the public X.25 networks interconnected through X.75 gateways from 1978, none of it requiring TCP. The protocol milestones of 1974, 1977, 1980, 1981, and January 1, 1983 are all later events inside a domain that already existed as an operational internetwork. TCP/IP was designed to operate across multiple networks and therefore presupposed the system it is credited with creating. RFC 1122, published in October 1989, defines the Internet as a network of networks. The Internet’s own standards registry, in RFC 1200 of April 1991 and RFC 2200 of June 1997, graded IP Required and TCP Recommended, never Required. Therefore it is patently false, inaccurate, illogical, and impossible for the protocols TCP/IP to be claimed as the birth of the Internet, and Stanford University, which dedicated this plaque on July 28, 2005 and maintains it, is responsible for that misappropriation of credit and carries the burden of stolen valor until the headline is corrected.
Petition. Stanford University is petitioned to keep the plaque, keep every name, keep every date in the body, and replace the headline “BIRTH OF THE INTERNET” with “THE CONCEPTION OF AN OPTIONAL INTERNET ARCHITECTURE: TCP/IP,” or, failing that, with “THE CONCEPTION OF TCP/IP.” Keep the names. Correct the headline. The body already tells the truth; let the headline join it.
Mark Nichols
Architect of the Modern Internet
Co-Founder and Chief Architect, Digital Island, 1996
Designer and operator of the first Tier-0 global network, AS6553, issued August 29, 1996
Author of How I Made the Web World Wide
marknichols.com
mark@marknichols.com
775-600-3400