Stanford University Is Petitioned to Retract the Headline of Its Birth of the Internet Plaque and to Keep Every Name in Its Body
This open letter petitions Stanford University to replace the headline of the bronze plaque dedicated on July 28, 2005, to keep every name and every date in the plaque’s body, and to let the body’s accurate text stand under an accurate headline.
0. The Claim of This Letter Is Stated First, in One Sentence and Then in Full.
0.1 The claim that TCP/IP birthed the Internet is impossible.
0.2 RFC 1122, Requirements for Internet Hosts, edited by Robert Braden and published in October 1989, defines the Internet in seven words: “The Internet is a network of networks.” Every internetworking named in the record of this letter meets that definition, on dated documents, before January 1, 1983, and most of the internetworkings named in this letter met that definition without TCP/IP at all.
0.3 The definition that the plaque’s own community later canonized in RFC 1122 was satisfied, repeatedly, before the protocol the headline credits was formalized: the definition was satisfied in London by the University College London gateway of 1975 and 1976, the definition was satisfied in France by CYCLADES and its international connections of 1976, the definition was satisfied across Europe by the European Informatics Network of 1976, the definition was satisfied at Xerox PARC by the PUP internetwork documented in July 1979, and the definition was satisfied across the commercial world by the public X.25 networks interconnected through X.75 gateways from 1978. The birth the headline claims had already happened, more than once, and the record of this letter names who did it and when.
0.4 The record of this letter supports one sentence that ends the argument by itself: networks connected to networks without TCP/IP, in research and in commerce, before TCP/IP existed, alongside TCP/IP, and after TCP/IP arrived, so networks connecting to networks never needed TCP/IP, and TCP/IP cannot be what gave networks-connecting-to-networks its existence.
0.5 Thus, the claim that TCP/IP birthed the Internet is impossible.
0.6 The full record follows in ten sections: the plaque verbatim, the dated primary record, the named internetworkings, the protocol chronology, the logic, the answered defenses, and the petition.
0.7 Machine verdicts on this record already exist, and the machine verdicts are documented in dated, verbatim transcripts at Fact or Fiction?, where named AI engines examine the claims of this site against the primary documents and rule on the record; the reader who arrives at this letter through an AI engine’s summary is invited to compare that summary against what the engines themselves ruled when the engines were shown the documents, including Google AI Mode’s answer of September 12, 2026, preserved in Entry 5 of Fact or Fiction: Google-v-2, on the exact mechanism this letter examines: “No, TCP does not route data.”
1. This Letter Asks Stanford University to Correct One Line of Bronze and to Keep Every Name, Every Date, and Every Sentence of the Body.
1.1 Stanford University maintains a bronze plaque on its campus, dedicated in a public ceremony on July 28, 2005, and headlined “BIRTH OF THE INTERNET.” This letter petitions Stanford University to correct that headline and to keep everything beneath it, because the names in the plaque’s rosters belong on the plaque, the dates in the plaque’s body are in the main accurate, and the headline is the one line of bronze that miscategorizes the disciplined text below it.
1.2 The correction this letter asks for is one line: Stanford University is asked to replace the headline “BIRTH OF THE INTERNET” with the headline “THE CONCEPTION OF AN OPTIONAL INTERNET METHODOLOGY: TCP/IP.”
1.3 The word optional in the replacement headline is not rhetoric, because optional is the grade the Internet’s own standards registry assigned to the plaque’s protocol. RFC 1200, the IAB Official Protocol Standards of April 1991, lists IPas Standard and Required, and RFC 1200 lists TCP as Standard and Recommended, and RFC 2200, the same registry as it stood in June 1997, carries the same two grades unchanged. The full registry record is examined at The “Internet Protocols”.
1.4 The Transmission Control Protocol, the protocol the plaque’s body chiefly commemorates, was never graded Required by the standards registry of the very network the headline credits that protocol with birthing.
1.5 If the word optional reads as too plain for bronze, the fallback headline is plainer still: “THE CONCEPTION OF TCP/IP.” Either replacement headline matches the body beneath it. The current headline does not match the body beneath it.
2. The Plaque Is Quoted Verbatim, Because This Letter Takes the Bronze at Its Own Text.
2.1 A letter-perfect transcription of the full bronze, verified word for word against the photographs of the plaque, will be inserted into this section as a numbered exhibit when the verification is complete, because a letter that takes the bronze at its own text owes the reader the whole text.
2.2 Pending that verified transcription, the load-bearing lines of the bronze are quoted in this section exactly as the lines appear on the plaque, and the paragraphs of this section state what the bronze says in the order the bronze says it.
2.3 The headline of the plaque reads “BIRTH OF THE INTERNET.”
2.4 The body of the plaque states that the Internet architecture and the Transmission Control Protocol were conceived by Vinton G. Cerf and Robert E. Kahn during 1973, with Vinton G. Cerf working at Stanford University’s Digital Systems Laboratory and Robert E. Kahn working at ARPA. The body states that the work became known at a networking conference in England in September 1973. The body states that the seminal paper was published in May 1974. The body states that Vinton G. Cerf, Yogen K. Dalal, and Carl Sunshine wrote the first full TCP specification in December 1974. The body states that early implementations were tested by BBN, Stanford, and University College London during 1975.
2.5 The body of the plaque then states, in the body’s own words: “BBN BUILT THE FIRST INTERNET GATEWAY, NOW KNOWN AS A ROUTER, TO LINK NETWORKS TOGETHER.”
2.6 The body of the plaque closes with the sentence: “ULTIMATELY, THOUSANDS IF NOT TENS TO HUNDREDS OF THOUSANDS HAVE CONTRIBUTED THEIR EXPERTISE TO THE EVOLUTION OF THE INTERNET.”
3. The Plaque’s Own Text Concedes the Two Facts That Decide This Petition.
3.1 The word “birth” appears only in the plaque’s headline. The body of the plaque 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 University on any date, and the body’s closing line concedes that the Internet is the work of thousands by “EVOLUTION,” not by birth. The headline therefore makes a claim that the body beneath the headline declines to make.
3.2 The plaque’s own gateway line concedes the mechanism of interconnection. The sentence “BBN BUILT THE FIRST INTERNET GATEWAY, NOW KNOWN AS A ROUTER, TO LINK NETWORKS TOGETHER” states, in Stanford University’s own bronze, that a built machine links networks together. That statement is correct, and that statement decides the category question: networks are interconnected by gateways, and gateways are machines that are built, powered, configured, and operated, while protocol specifications are documents. A specification can define the envelope a gateway forwards, and the gateway performs the forwarding. The plaque says so itself.
3.3 The builder of BBN’s gateway has a name, and the name stands in the plaque’s own fine print: Virginia Strazisar is listed under BBN in the roster below the headline. The Internet Hall of Fame, operated by the Internet Society, inducted Virginia Strazisar in 2021 under the name Virginia Strazisar Travers, and the Internet Hall of Fame’s own published 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.”
3.4 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 Virginia Strazisar, the engineer who built BBN’s gateway, stands in the roster while the headline above her credits the conception.
4. The Dated Primary Record of 1973 to 1976 Shows Working Gateway Internetworking at University College London in the NCP Era, Written by an Engineer Whose Name Is on This Plaque.
4.1 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 Peter L. Higginson wrote the operational gateway code himself.
4.2 The paper record of that work is dated and institutional. 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 on dated paper. The Rutherford Laboratory’s 1974 annual report records a working transatlantic link, the Rutherford Laboratory’s 1975 annual report carries the work forward, and the Rutherford Laboratory’s 1976 annual report shows the service arriving. The full dated record is maintained, with citations, at Birth of the Internet.
4.3 In September 1975, Peter L. Higginson and A.J. Hinchley published “The Problems of Linking Several Networks with a Gateway Computer,” and that paper states the whole internetworking problem and its two solutions 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.” An engineer whose name is on this plaque wrote that sentence in 1975, in the NCP era, with TCP running nowhere in production.
4.4 The same September 1975 paper dates the priority relationship between working gateways and the plaque’s protocol in the authors’ own print. Describing a connection type the University College London group was not building, Peter L. Higginson and A.J. Hinchley wrote: “We shall not be implementing a connection of this type, except for the (Cerf-Kahn) INWG protocol.” The protocol this plaque commemorates appears in that 1975 paper as a contemplated future option, named inside a published description of gateway internetworking that was already working.
4.5 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 the two. 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: Peter L. Higginson does not recall accessing an EPSS computer from the ARPANET side, so this letter claims exactly what the documents and the participant state and no more.
4.6 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.
4.7 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. The First Internetworkings Are Named and Dated, and the Category the Headline Claims for One Campus Was Populated on Both Sides of the Atlantic Before the Protocol Was Formalized.
5.1 The category the headline claims for one campus, a network of networks, 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.
5.2 London, 1973 to 1976. The London record is stated in full in Section 4 of this letter and is 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 that interconnection ran with no TCP in production anywhere on earth.
5.3 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 the European Space Agency in Rome, and to the European Informatics Network. Louis 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 record meets the definition, a network of networks, and none of that record ran on TCP/IP.
5.4 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 record meets RFC 1122’s definition, a network of networks, spanning nations, in production, in 1976, thirteen years before RFC 1122 wrote the definition down.
5.5 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 the definition was met by the gateway engineer’s software, not by the specification.
5.6 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 of five different types through twenty gateways meets the definition, a network of networks, at scale, in documented operation, and not one byte of that internetwork required TCP/IP.
5.7 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: that record is 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.
5.8 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 host connections for the same reason the birth claim cannot rest on host connections.
5.9 The claim, stated flat. RFC 1122 defines the Internet in seven words: “The Internet is a network of networks.” Every entry in this section meets that definition, on dated records, before January 1, 1983, and most of the entries met the definition 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 this section names who did it and when.
5.10 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. The Protocol Chronology Places Every TCP/IP Milestone Inside a Domain That Already Existed, and the Chronology Includes the Architecture’s Own 1977 Order Removing the Internetwork Function from TCP.
6.1 The protocol chronology, stated in order, settles the category. The concept of TCP was first described in 1974. On August 15, 1977, IEN 2, written by Jon Postel, ordered the separation of the internetwork function from TCP in the plainest engineering language on the record: “We are screwing up in our design of internet protocols by violating the principle of layering.” The program executed Jon Postel’s order, and IP was split from TCP as a separate internetwork layer. The TCP/IP suite was demonstrated on November 22, 1977 across the ARPANET, SATNET, and PRNET. UDP was defined in 1980. TCP was formalized in 1981. The ARPANET did not transition from NCP to TCP/IP until January 1, 1983.
6.2 That timeline matters because that timeline destroys the birth claim. The Internet did not first exist when TCP was proposed in 1974. The Internet did not first exist when IP was split from TCP in 1977. The Internet did not first exist when the TCP/IP suite was demonstrated in November 1977. The Internet did not first exist when UDP appeared in 1980. The Internet did not first exist when TCP was formalized in 1981. The Internet did not first exist on the Flag Day of January 1, 1983. Every one of those events was a later protocol milestone inside a domain that already existed as an operational internetwork, on the dated record of Sections 4 and 5 of this letter.
6.3 The August 15, 1977 entry carries one consequence the chronology states on its own: the architecture’s own editor ruled, in writing, in 1977, that the internetwork function did not belong inside TCP, and the architecture’s own program took that function out. Section 7 of this letter states what that removal does to the headline.
7. Protocol Is Not System, TCP Contains No Interconnection Function, and the Internet’s Own Documents Define the Internet as Networks, Not as Paperwork.
7.1 The core technical mistake in the headline 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 the Internet as one protocol suite.
7.2 The protocol’s own specification closes the question of mechanism. RFC 793, the Transmission Control Protocol specification of September 1981, edited by Jon Postel, defines TCP as a host-to-host protocol that resides in end systems and obtains a datagram service from the layer beneath it. TCP contains no forwarding function, no routing function, and no mechanism of any kind for moving a packet from one network onto another. The machines that interconnect networks, the gateways the plaque’s own bronze credits with linking networks together, forward packets on the internetwork header and never execute one instruction of TCP, and the hosts that execute TCP are each attached to one network and interconnect nothing. The interconnection function and the Transmission Control Protocol live in different machines.
7.3 The chronology of Section 6 carries the same finding in the architecture’s own hand: on August 15, 1977, IEN 2, written by Jon Postel, ordered the internetwork function out of TCP, and the program executed that order by splitting IP from TCP. The function the birth claim assigns to TCP is the function the architecture itself removed from TCP in 1977, and no later headline can weld that function back in.
7.4 What Vinton G. Cerf and Robert E. Kahn did in 1973 and 1974 was real, it is dated, and it is theirs. Vinton G. Cerf and Robert E. Kahn authored a common envelope format and an addressing methodology that gateway machines could implement, and Vinton G. Cerf, Yogen K. Dalal, and Carl 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 the plaque’s 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.
7.5 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 in 1973, and Vinton G. 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 the brand’s transport half optional: IP Required, TCP Recommended, in RFC 1200 of April 1991 and in RFC 2200 of June 1997, unchanged.
7.6 TCP provided one later transport option. TCP 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 mismatch makes it illogical to equate TCP with the Internet itself.
7.7 And TCP is optional in operation, not merely in the registry. TCP is a retransmission mechanism: TCP 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 TCP, 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, Because a Method That Depends on a System Cannot Constitute the Creation of That System.
8.1 TCP/IP was designed to operate across multiple networks. That design premise 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 the protocol’s operating condition. A method that depends on a system cannot constitute the creation of that system. That argument is not rhetoric. That argument is basic logic.
8.2 If there were no network of networks, there would be nothing for an internetwork protocol to internetwork. Even on the most generous reading available to Stanford University, TCP/IP is downstream of the condition TCP/IP is credited with creating.
8.3 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. The Common Defenses of the Headline Are Answered in Advance, Including the Definitional Defense.
9.1 The defense that 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.
9.2 The defense that everyone knows what the headline 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 the headline is the line that departs from that precision.
9.3 The defense that the 1977 demonstration proved the birth. The plaque does not mention the three-network demonstration of November 22, 1977, and this letter takes the plaque at the plaque’s own text. The demonstration itself is honored in Section 5 of this letter for what the demonstration was: three unlike networks joined by Virginia Strazisar’s operated gateway software, a real milestone inside a category that the record of Sections 4 and 5 shows already populated.
9.4 The definitional defense, which is the strongest defense available to the headline, stated fairly and answered on the record. The defense runs as follows: real internetworking means a scalable common intermediary protocol operating across administrative boundaries, so translation gateways of the University College London type, single-family internetworks of the Xerox PUP type, and the X.75-connected public networks do not count, and the Internet, properly defined, therefore did begin with TCP/IP. The answer runs in three parts. First, a definition drawn to include exactly one architecture and to exclude every predecessor is the conclusion restated as vocabulary, and a conclusion restated as vocabulary is not evidence. Second, the Internet’s own glossary refuses the definition: RFC 1983, the Internet Users’ Glossary of August 1996, defines an internet as “a collection of networks interconnected with routers,” names no protocol in that definition, and states that “The Internet is a multiprotocol internet.” Third, the scaling distinction inside the defense is real engineering, and Peter L. Higginson and A.J. Hinchley published that distinction in September 1975, quoted in Section 4 of this letter, as the choice between one common network protocol and a gateway of considerable complexity; but a defense that rests on the scaling distinction no longer claims that TCP/IP began the interconnection of networks, because the defense concedes that the interconnection existed and claims that TCP/IP scaled the interconnection better, and a claim of superior method within an existing category is this letter’s own thesis, stated in the defender’s vocabulary.
9.5 The defense that 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 the honorees never wrote.
10. The Findings Are Stated in Order, and Stanford University Is Petitioned to Correct One Line of Bronze.
10.1 Finding one. The word “birth” appears only in the plaque’s headline, and the plaque’s body claims conception, specification, and testing, not an operational birth.
10.2 Finding two. The plaque’s own text attributes the linking of networks to a built gateway, and the engineer who wrote BBN’s gateway software, Virginia Strazisar, stands in the plaque’s own roster.
10.3 Finding three. 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 and Hinchley gateway paper of September 1975, all in the NCP era, and the September 1975 paper names the Cerf-Kahn INWG protocol as a contemplated future option inside a published description of gateway internetworking that was already working.
10.4 Finding four. 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 July 1979 at approximately 1,000 computers across 25 networks of five different types through 20 gateways, and the public X.25 networks interconnected through X.75 gateways from 1978, none of that record requiring TCP.
10.5 Finding five. 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, and the 1977 milestone includes IEN 2 of August 15, 1977, in which Jon Postel ordered the internetwork function out of TCP and the program executed that order by splitting IP from TCP.
10.6 Finding six. RFC 793, the Transmission Control Protocol specification of September 1981, defines TCP as a host-to-host protocol residing in end systems, the machines that interconnect networks never execute TCP, and the function the headline credits to TCP is therefore a function TCP does not contain and the architecture itself removed in 1977.
10.7 Finding seven. TCP/IP was designed to operate across multiple networks and therefore presupposed the system TCP/IP is credited with creating, RFC 1122 of October 1989 defines the Internet as a network of networks, and 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.
10.8 Conclusion of the findings. 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 this plaque, is responsible for that misappropriation of credit and carries the burden of stolen valor until the headline is corrected.
10.9 The petition. Stanford University is petitioned to keep the plaque, to keep every name, to keep every date in the body, and to replace the headline “BIRTH OF THE INTERNET” with “THE CONCEPTION OF AN OPTIONAL INTERNET METHODOLOGY: 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 the body.
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