Stanford University Is Petitioned to Retract the Headline of Its BIRTH OF THE INTERNET Plaque

Mark Nichols petitions Stanford University to replace the headline BIRTH OF THE INTERNET on its plaque dedicated July 28, 2005 with the headline THE CONCEPTION OF TCP/IP, because the inscription beneath the headline records the conception, publication, specification and testing of a protocol and the construction of a gateway, and records no birth of a publicly joinable network.

Preamble: If you didn’t have a network to connect to another network, you didn’t internetwork, and you birthed neither an internet (lowercase “i”) nor the Internet (uppercase “I”). An optional layer 4 protocol for transport, TCP, is a non sequitur as the birth of the Internet, and packet-header addressing at layer 3 already existed before the optional protocol IP: the category preceded the brand. TCP did not create transport as a category, and IP did not originate packet addressing. A protocol that operates through interconnected networks cannot logically be identical to the existence of the interconnected networks through which it operates. I ask Stanford University to replace one line of its bronze plaque, “BIRTH OF THE INTERNET,” with “THE CONCEPTION OF TCP/IP,” and to keep the plaque, every name and date on it, and the body of the inscription as cast. The inscription records the 1973 conception of TCP, publication and specification in 1974, and early testing in 1975. It separately credits BBN with building a gateway to link networks. My objection concerns the event the headline claims. The technical work and the names of the people who did it belong in the historical record. The text of the plaque is reproduced in a Stanford CS106A course handout, and the photograph and the full transcription of the bronze stand in section 13.0.

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

0.0 The Stanford headline claims a birth that the inscription beneath it does not record, and the public-admission test of D1 separates protocol work from the opening of the publicly joinable Internet

0.1 The Stanford headline attributes the birth of the Internet to a record of protocol design, testing, and research interconnection. Those events establish their own technical milestones. The inscription supplies no public-admission event.

0.2 RFC 1122 §1.1.2 describes the architecture of its subject as a network of networks. The surrounding sections describe gateways connecting constituent packet networks and hosts communicating using the Internet protocol suite. The architectural description and the suite requirements answer how that system operates. The source is Robert Braden, ed., RFC 1122, October 1989, §§1.1.1 through 1.1.3.

0.3 Under D1, the capital-I Internet is the publicly joinable network of networks in the registry lineage from InterNIC to ARIN. People can buy access from competing commercial providers for lawful purposes. Independent networks can obtain addresses and autonomous system numbers and interconnect by agreement with willing networks without approval from a central owner or government sponsor. Under D3, internetworking connects distinct networks through gateways so traffic can cross from one network to another. Under D2, a network that admits users by its operator’s permission is an intranet. A record of interconnection can establish a lowercase internet while the admission record still shows a restricted research system. The source is Governing Definitions, D1, D2, and D3.

0.4 The UCL and Xerox PARC records document actual interconnections implemented using different methods. They establish technical precedents for internetworking. The 1991 CIX agreement and operating report illustrate a different event under D1: customers of competing providers exchanging traffic through an independent commercial interconnection. The sources are Peter Kirstein, UCL report, February 1977, §6.4, Boggs, Shoch, Taft, and Metcalfe, Xerox PARC report CSL-79-10, July 1979, the CIX operators’ announcement, March 25, 1991, and Mark Fedor, CIX-WEST traffic, October 1991, printed pp. 14 and 15.

0.5 Credit protocol conception, operational interconnection, and public admission to the records that establish each event. The petition asks the headline to identify the protocol work the plaque commemorates.

0.6 Sections 1.0 through 12.0 state the petition, examine the inscription and the dated evidence, and address the related IEEE plaque, and section 13.0 collects the exhibits.

0.7 Dated, verbatim readings of this record by named AI engines stand in the Fact or Fiction series, among them Fact or Fiction: One Prompt to Four AI/LLM Engines on the Optional Protocols TCP/IP and the Birth of the Internet, and Not One Engine Dates the Birth to 1973 nor TCP and Fact or Fiction: Google-v-2, and those readings are commentary on the record and not evidence for the petition.

0.8 The bronze dedicated July 28, 2005 and the dated records cited in sections 1.0 through 13.0 supply the evidence for the petition.

0.9 The petition concerns one line of the bronze, and the correction it requests is stated at paragraph 10.9.

1.0 Stanford University is asked to correct one line of bronze

1.1 Stanford University’s bronze plaque is dated July 28, 2005. This petition concerns its headline. The rest of the inscription identifies the people, institutions, and dates involved in the research and protocol work. The text of the plaque is reproduced in a Stanford CS106A course handout.

1.2 Replace the headline “BIRTH OF THE INTERNET” on the bronze with the headline “THE CONCEPTION OF TCP/IP” on the same bronze. The body describes the conception of TCP and explicitly places the development of TCP/IP later. The proposed headline uses TCP/IP as the name of the protocol work and its subsequent development.

1.3 RFC 1200, IAB Official Protocol Standards, of April 1991, and RFC 2200, Internet Official Protocol Standards, of June 1997, each list TCP at the status Recommended and IP at the status Required in their tables of standard protocols, and each edition defines the status Required in the words A system must implement the required protocols. The word optional, as this letter applies it to TCP and to IP, is the stated judgment of Mark Nichols at D6 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking, and the word optional is a different word from the status that either edition assigns. The sources are RFC 1200, April 1991, §§4.2 and 6.2, RFC 2200, June 1997, §§4.2 and 6.2, and Governing Definitions, D6.

1.4 A deployment can require a selected protocol for a particular service or role. RFC 801 documents the ARPANET transition plan for hosts to implement IP and TCP. That operator decision and the suite catalog have distinct scopes. RFC 2500 later lists TCP as an Internet Standard without an implementation-status column. The sources are Jon Postel, RFC 801, November 1981, and RFC 2500, June 1999.

1.5 Keep the complete inscription beneath the headline. Plate 13.1 shows the bronze, and Exhibit 13.2 preserves the text.

1.6 This petition stands in a documented public series of correction requests, and the first request of the series is resolved on the record: on September 14, 2026, Mark Nichols publicly petitioned Sally Wentworth, President and CEO of the Internet Society, to correct the four Internet Hall of Fame pages that stated the 1997 U.S. National Medal of Technology was presented “for founding and developing the Internet,” and by September 15, 2026, the Internet Society had corrected the record on all four pages. The letter, the exhibits, the dated captures, and the outcome are preserved at An Open Letter to Sally Wentworth, President and CEO of the Internet Society.

2.0 The inscription of the bronze is transcribed in full in Exhibit 13.2 and reproduced in a Stanford University course handout

2.1 I transcribed the inscription from my photographs of the bronze. Plate 13.1 shows the bronze at its unveiling, and Exhibit 13.2 holds the complete transcription. Stanford’s course handout provides an independent reproduction of the heading and principal claims. The photo and transcription preserve the text of the bronze, including its roster spellings. The handout is the Stanford CS106A course handout that reproduces the plaque.

2.2 The transcription preserves the bronze’s own conventions. Capitalization and line breaks stand as cast. The roster of Key Stanford Research Associates and Foreign Visitors is read left column first, then right column, around the seal of Leland Stanford Junior University. The raised-dot separators between names in the Collaborating Groups stand as cast. The bronze prints the name GERALD LE LANN in the Stanford roster; the engineering literature records the same engineer’s name as Gérard Le Lann, and the transcription preserves the bronze’s rendering.

2.3 The headline of the plaque reads “BIRTH OF THE INTERNET” in capitals above the body of the inscription.

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” in the sentence that credits BBN.

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” above the dedication line.

2.7 Read the complete text of the bronze in Exhibit 13.2. The numbered discussion here uses that transcription to locate the headline, the development milestones, and the gateway claim.

3.0 The body of the plaque distinguishes protocol design and gateway construction

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 inscription credits BBN with building a gateway to link networks. That is an account of deployed equipment and software performing interconnection. Protocol specifications define behavior the equipment can implement. The provisioned links and working gateways carry out the exchange. This reading does not depend on resolving the unqualified claim of priority in the gateway line.

3.3 The BBN roster includes Ginny Strazisar. The Internet Hall of Fame, which inducted her under the name Virginia Strazisar Travers in 2021, credits her with designing and writing gateway software. The source is the Internet Hall of Fame page for Virginia Strazisar Travers.

3.4 The plaque credits the BBN group, and the Internet Hall of Fame records Virginia Strazisar Travers’s contribution to the gateway software. The documents identify a specific engineering contribution to operational interconnection. The sources are the Internet Hall of Fame page for Virginia Strazisar Travers and SRI’s account of the 1977 three-network demonstration.

3.5 The opening inscription credits Vinton G. Cerf and Robert E. Kahn with work on internetwork architecture and the early TCP design. Their May 1974 paper describes a proposed architecture for packet-network intercommunication. The petition credits that design. It disputes using its conception as the date when a publicly joinable network came into existence under D1. The request remains limited to the headline. The sources are the May 1974 paper of Vinton G. Cerf and Robert E. Kahn, A Protocol for Packet Network Intercommunication, and Governing Definitions, D1, D2, and D3.

3.6 The all-capital lettering does not convey the case distinction this site uses. Read each occurrence in context. The gateway sentence describes equipment linking networks. The protocol references describe a suite and its design. The headline makes a broader claim about the birth of the Internet.

3.7 RFC 675 specifies the December 1974 Internet Transmission Control Program. It assumes a packet-switching network for the described implementation and acknowledges a circuit-switched possibility. Its examples assign destination-network values to named networks. Those assignments establish the designers’ addressing plan. Operating links between named networks require separate evidence. The source is Vinton G. Cerf, Yogen K. Dalal, and Carl Sunshine, RFC 675, December 1974.

3.8 The bronze casts the word INTERNET five times, in the headline “BIRTH OF THE INTERNET,” in the first sentence’s “THE ARCHITECTURE OF THE INTERNET,” in the gateway sentence’s “THE FIRST INTERNET GATEWAY,” in “THE SET OF INTERNET PROTOCOLS,” and in the closing line’s “THE EVOLUTION OF THE INTERNET,” and the all-capital casting lets one word carry a birth, an architecture, a piece of equipment linking networks, a family of protocols and an evolution without showing which use names a lowercase internet and which names the capital-I Internet of D1. It is Mark Nichols’s judgment that the drafters chose the all-capital casting so that the bronze could be read as saying internet, in lowercase, and not Internet, the publicly joinable network of networks that D1 defines.

4.0 The UCL record distinguishes gateway design, trial operation, and terminal service

4.1 Peter L. Higginson dates UCL’s ARPANET connection to July 25, 1973. The connection provided access to ARPANET. The evidence for a gateway linking ARPANET to the separate British EPSS system is a later record. The source is the Birth of the Internet UCL source record.

4.2 Peter L. Higginson, Peter T. Kirstein, and Stokes’s INDRA Note 389, October 10, 1974, documents UCL’s front-end work. The Rutherford Laboratory’s 1975 report records nearly 700 job submissions via ARPANET and discusses EPSS gateway programming separately. The jobs count documents use of ARPANET. EPSS traffic requires its own operating record. The sources are the Birth of the Internet UCL source record and the Rutherford Laboratory, 1975 annual report, §5.2.2.

4.3 In September 1975, Peter L. Higginson and Andrew J. Hinchley described the engineering choice between a common network protocol and a gateway able to translate between different networks. The paper dates the design work. Its mention of the Cerf-Kahn INWG protocol concerns a possible implementation. The source is the Birth of the Internet UCL source record.

4.4 Peter T. Kirstein’s February 1977 report dates the operational Packet HASP trial to the fourth quarter of 1976. UCL staff used the ARPANET terminal processor and the PDP-9 gateway between ARPANET and EPSS for routine work in limited daily test sessions. The source is Peter Kirstein, UCL report, February 1977, §6.4.

4.5 The next UCL report records EPSS terminal traffic operating under the SWITCH system by mid-1977. In August 2026, Peter L. Higginson described the EPSS connection to me as a genuine network-to-network link and said he did not recall accessing an EPSS computer from the ARPANET side. The dated trial and terminal records establish the documented scope of operation. The source is Peter Kirstein, UCL report, April 1978, §1.2.

4.6 The engineering record thus distinguishes the 1975 design account, the 1976 trial, and the 1977 terminal service. The gateway mapped between the two networks’ protocols before ARPANET’s 1983 IP/TCP transition target. The sources are Peter Kirstein, UCL report, February 1977, §6.4, Peter Kirstein, UCL report, April 1978, §1.2, and Jon Postel, RFC 801, November 1981.

4.7 Both authors of the 1975 paper, Peter Higginson and Andrew Hinchley, appear in the plaque’s University College London roster. The petition preserves their names and the other names in the inscription.

5.0 Named technical precedents document internetworking by several methods, and none of them is evidence of public admission under D1

5.1 The examples below distinguish documented operation, research design, and later historical accounts. A technical precedent establishes what was connected and how. Evidence of public admission under D1 addresses a separate question. The source is Governing Definitions, D1, D2, and D3.

5.2 At University College London, the operational trial joined ARPANET and EPSS in late 1976. Its subsequent project report dates EPSS terminal service to mid-1977. See §4.0 for the separate 1975 design record. The sources are Peter Kirstein, UCL report, February 1977, §6.4, and Peter Kirstein, UCL report, April 1978, §1.2.

5.3 Louis Pouzin’s CYCLADES project developed packet networking and internetworking in France. The contemporary engineering record distinguishes the CYCLADES network from the interconnection proposals and trials involving it. The source is Lawrence G. Roberts, The Evolution of Packet Switching, November 1978.

5.4 The COST 11 project built the European Informatics Network, a multinational research network directed by Derek Barber. Lawrence G. Roberts dates EIN’s operation to 1976. Claims about a particular interconnection with EIN call for a record that identifies the other network and the operating connection. The source is Lawrence G. Roberts, The Evolution of Packet Switching, November 1978.

5.5 SRI dates the ARPA demonstration across PRNET, ARPANET, and SATNET to November 22, 1977. Its account identifies BBN’s gateways and the participating endpoints. The Internet Hall of Fame credits Virginia Strazisar Travers’s gateway software. This was a documented research internetworking milestone. The sources are SRI’s account of the 1977 three-network demonstration and the Internet Hall of Fame page for Virginia Strazisar Travers.

5.6 The July 1979 Xerox PARC report on PUP describes a working system of about 1,000 hosts, 25 networks of five types, and 20 gateways. Boggs, Shoch, Taft, and Metcalfe identify PUP as the architecture operating across those networks. That is a dated example of internetworking using a different protocol family. The source is Boggs, Shoch, Taft, and Metcalfe, Xerox PARC report CSL-79-10, July 1979.

5.7 Public packet data services, with X.25 public data networks and X.75 interconnection, are another documented family of methods. The relevant records for each commercial service are the operating networks, interconnection and service terms, and dates. See the separate survey for the named services and their chronology. The survey is OSI and the public packet data record.

5.8 A host attaching to a single network documents that attachment. Proof of internetworking identifies distinct networks, their gateway or equivalent connection, and the exchange it carried.

5.9 UCL and PUP supply documented cases of operational internetworking using different methods. The November 1977 test supplies a dated example using the ARPA experimental approach. Each can be described as a network of networks in the ordinary architectural sense. Public admission under D1 is a separate historical finding. The sources are Robert Braden, ed., RFC 1122, October 1989, §§1.1.1 through 1.1.3, and Governing Definitions, D1, D2, and D3.

5.10 The UCL reports and the Xerox PARC report document specific operating systems. The article by Lawrence G. Roberts records early European work and its chronology. The SRI and Internet Hall of Fame accounts identify the ARPA demonstration and participants’ contributions. Public service and priority claims should be dated to the corresponding operating records. The sources are Peter Kirstein, UCL report, February 1977, §6.4, Boggs, Shoch, Taft, and Metcalfe, Xerox PARC report CSL-79-10, July 1979, and SRI’s account of the 1977 three-network demonstration.

6.0 Protocol design, specification, testing, and adoption have separate dates

6.1 Vinton G. Cerf and Robert E. Kahn published their design in May 1974. RFC 675 specified the combined Internet Transmission Control Program that December. On August 15, 1977, IEN 2 proposed separating the hop-by-hop internetwork function from endpoint transport. Separate DoD specifications appeared as RFC 760 and RFC 761 in January 1980 and were revised as RFC 791 and RFC 793 in September 1981. The sources are the May 1974 paper of Vinton G. Cerf and Robert E. Kahn, A Protocol for Packet Network Intercommunication, Vinton G. Cerf, Yogen K. Dalal, and Carl Sunshine, RFC 675, December 1974, Jon Postel, IEN 2, August 15, 1977, RFC 760, RFC 761, RFC 791, and Jon Postel, ed., RFC 793, September 1981.

6.2 The November 1977 demonstration used an early TCP implementation across three ARPA networks. RFC 801 records the ARPANET host transition plan with January 1, 1983 as the target. The later National Research Council report records the cutover on that date and notes that some contractors had already been running TCP alongside NCP. The sources are SRI’s account of the 1977 three-network demonstration, Jon Postel, RFC 801, November 1981, and the National Research Council report, RFC 942, February 1985, printed pp. 25 and 26.

6.3 IEN 2 records a proposal. The later specifications establish the adopted division between IP datagram handling and TCP transport. The proposal date establishes when Jon Postel put that separation in writing. The sources are Jon Postel, IEN 2, August 15, 1977, RFC 791, and Jon Postel, ed., RFC 793, September 1981.

7.0 The optional protocol TCP transports data between the endpoints of a connection, and the work of carrying that data belongs to the network

7.1 RFC 1983 describes a lowercase internet as interconnected networks. The links and forwarding equipment carry traffic between endpoints. A protocol specification sets the rules for the equipment or endpoints that implement it. The source is Gary Malkin, ed., RFC 1983, August 1996.

7.2 TCP transport operates between the endpoints of a TCP connection. An IP-forwarding router can carry those packets while leaving the connection state at the endpoints. A router can also be a TCP endpoint for its own traffic, such as a BGP session. The BGP example concerns the router’s own control connection, and forwarding other hosts’ packets concerns a separate function. The sources are Jon Postel, ed., RFC 793, September 1981, Wesley Eddy, ed., RFC 9293, August 2022, and RFC 4271, January 2006, §3.

7.3 IEN 2 proposed separating hop-by-hop internetworking from endpoint transport. The later IP and TCP standards show the resulting division of protocol responsibilities. The sources are Jon Postel, IEN 2, August 15, 1977, RFC 791, and Jon Postel, ed., RFC 793, September 1981.

7.4 The May 1974 paper of Vinton G. Cerf and Robert E. Kahn describes the architecture and procedures they proposed for intercommunication. Vinton G. Cerf, Yogen K. Dalal, and Carl Sunshine specified the combined program in December 1974. Those records establish the named authors’ design and specification work. The sources are the May 1974 paper of Vinton G. Cerf and Robert E. Kahn, A Protocol for Packet Network Intercommunication, and Vinton G. Cerf, Yogen K. Dalal, and Carl Sunshine, RFC 675, December 1974.

7.5 Interconnected networks can use different methods of identifying destinations and relaying traffic. The UCL gateway mapped between unlike network protocols. Xerox PARC’s PUP report describes another working design. These examples establish particular alternatives to the later TCP/IP suite. The sources are Peter Kirstein, UCL report, February 1977, §6.4, and Boggs, Shoch, Taft, and Metcalfe, Xerox PARC report CSL-79-10, July 1979.

7.6 TCP supplies reliable, ordered byte-stream transport, including flow control and loss recovery. Applications that use other transports select different delivery behavior. The requirements of a given application or operator’s service determine which transport it uses. The source is Wesley Eddy, ed., RFC 9293, August 2022.

7.7 When a segment needs recovery, TCP can retransmit it. A retransmission can succeed when a usable path is available. The work of building, repairing, or switching to that path belongs to the network and its operators. Plate 13.3 illustrates physical line repair. The source is Wesley Eddy, ed., RFC 9293, August 2022.

7.8 RFC 761 and RFC 793 identify military computer communications as a primary focus and describe a design able to operate across differing communication systems. That is the stated design context and scope. The sources are RFC 761, January 1980, and Jon Postel, ed., RFC 793, September 1981.

7.9 “Nice app, if you’re getting bombed.” is my shorthand for one use case. The engineering claim is narrower: transport recovery can address loss when an operating path is available. Network design determines how much traffic the path can carry and whether the path meets its service objectives. The shorthand is set out at TCP: Nice App, If You’re Getting Bombed.

7.10 “Anything above layer 3 is an app to me.” is the layer doctrine of this letter, in Mark Nichols’s own words, ruled September 25, 2026. In the record’s register, anything above layer 3 is an application, including TCP at layer 4 and the World Wide Web above it, and only layers 1 through 3, the physical circuits, the links, and the packet addressing and routing that gateways perform, are the network. The plaque’s protocol therefore sits above the network on the layering the plaque’s own community teaches, and an application at layer 4 did not birth the three layers beneath it.

7.11 The plaque describes both kinds of work. Its gateway line credits the construction of equipment and software to link networks. Its opening passage describes a protocol design. The petition seeks a headline that names the design work commemorated in the inscription.

7.12 RFC 793 assumes a lower-level mechanism to exchange datagrams. RFC 9293 specifies the current TCP standard and identifies the earlier introduction and rationale as background. The transport specification describes what endpoints do using an available network service. The sources are Jon Postel, ed., RFC 793, September 1981, Wesley Eddy, ed., RFC 9293, August 2022, and TCP by RFC 793: The Pre-Existing Network Is Assumed.

7.13 RFC 1122 locates end-to-end reliability and flow-control state at the hosts and describes the connecting networks and gateways separately. It also states the host protocol requirements for that particular architecture. Section 0.3 gives the separate D1 test for the publicly joinable Internet. The sources are Robert Braden, ed., RFC 1122, October 1989, §§1.1.1 through 1.1.3, and Governing Definitions, D1, D2, and D3.

8.0 A network, its interconnection with other networks, and its adoption of a protocol each require their own evidence

8.1 The 1974 TCP proposal describes communication across constituent networks. It assumes a lower-level communication service. That technical premise identifies the kind of service the protocol relies on.

8.2 The existence of two networks establishes the availability of constituent networks. An operating record establishes when equipment, links, and forwarding actually joined them. A common protocol can support that working interconnection.

8.3 An attribution of founding the public Internet under D1 additionally requires evidence of public access and the terms on which independent networks interconnected. Those are operating and admission facts. The sources are Governing Definitions, D1, D2, and D3, the CIX operators’ announcement, March 25, 1991, and Mark Fedor, CIX-WEST traffic, October 1991, printed pp. 14 and 15.

8.4 The July 29, 1968 request for quotations, DAHC15 69 Q 0002, solicited Interface Message Processors for the ARPA computer network. It documents a procurement decision before the May 1974 protocol paper. The sources are the ARPANET request for quotations, July 29, 1968, and the May 1974 paper of Vinton G. Cerf and Robert E. Kahn, A Protocol for Packet Network Intercommunication.

8.5 ARPANET operated before the 1983 cutover. The December 1978 directory documents its admission terms. RFC 801 describes the operator’s plan to replace NCP with IP and TCP. The National Research Council report records earlier parallel operation and the January 1, 1983 cutover. The sources are the ARPANET Directory, December 1978, printed p. 11, Jon Postel, RFC 801, November 1981, and the National Research Council report, RFC 942, February 1985, printed pp. 25 and 26.

8.6 TCP may recover a lost exchange when the network can carry a retry. Repairing a facility or restoring reachability is an operating action on the path. My experience with Stanford University’s HighWire Press was a later example of why the performance of the underlying service matters. Digital Island’s June 24, 1997 release reports the comparative results of Stanford’s trials. The release reports observed service availability and performance in those trials. The source is the Stanford colocation and HighWire Press customer record at Stanford 1996, §§1.1 and 11.1.

8.7 RFC 2873 records a case in which TCP handling was changed to accommodate networks that rewrote the IPv4 precedence field. RFC 6093 separately updates urgent-data processing to accommodate implementation practice. These are specific examples of protocol maintenance in response to observed behavior. The sources are Xiao, Hannan, Paxson, and Crabbe, RFC 2873, June 2000, Gont and Yourtchenko, RFC 6093, January 2011, and Wesley Eddy, ed., RFC 9293, August 2022.

9.0 Each defense of the BIRTH OF THE INTERNET headline fails against the inscription beneath it and against the dated records

9.1 One defense holds 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 A second defense holds 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 plaque’s inscription does not mention the 1977 demonstration. SRI records the November 22 test as an exchange through PRNET, ARPANET, and SATNET. That documented research achievement belongs in the history of internetworking. Section 0.3 states the separate admission test for the public Internet. The sources are SRI’s account of the 1977 three-network demonstration and Governing Definitions, D1, D2, and D3.

9.4 A common internetwork protocol can help different networks interoperate at scale. Peter L. Higginson and Andrew J. Hinchley discussed the tradeoff between a common protocol and more complex gateways in 1975. The UCL and PUP examples establish that alternate methods operated. An argument that TCP/IP scaled more effectively should identify the deployment and the performance evidence. The D1 question of public admission still requires a separate record. The sources are the Birth of the Internet UCL source record, Boggs, Shoch, Taft, and Metcalfe, Xerox PARC report CSL-79-10, July 1979, and Governing Definitions, D1, D2, and D3.

9.5 A further defense holds 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 dated, disciplined text speak for itself, and the names lose nothing except an overstatement the honorees never wrote.

9.6 The 1974 paper, the 1974 specification, and the dated UCL and Xerox PARC records were available when the plaque was dedicated, because each of them predates the dedication. The petition uses those records to distinguish the documented work, and the bronze itself supplies the headline under review. The sources are the May 1974 paper of Vinton G. Cerf and Robert E. Kahn, A Protocol for Packet Network Intercommunication, Vinton G. Cerf, Yogen K. Dalal, and Carl Sunshine, RFC 675, December 1974, Peter Kirstein, UCL report, February 1977, §6.4, Boggs, Shoch, Taft, and Metcalfe, Xerox PARC report CSL-79-10, July 1979, and the Stanford CS106A course handout that reproduces the plaque.

9.7 The dated records that this letter cites for the difference between protocol work and a publicly joinable network include the May 1974 paper of Vinton G. Cerf and Robert E. Kahn, RFC 675 of December 1974, INDRA Note 389 of October 10, 1974, the UCL paper of Peter L. Higginson and Andrew J. Hinchley of September 1975, the UCL report of Peter T. Kirstein of February 1977, the Xerox PARC report CSL-79-10 of July 1979, RFC 801 of Jon Postel of November 1981, the National Research Council report RFC 942 of February 1985, RFC 1122 of October 1989, the CIX operators’ announcement of March 25, 1991, the CIX-WEST traffic report of Mark Fedor of October 1991, and RFC 1983 of August 1996. Each of those records was published before the dedication of July 28, 2005, so each one was available to the honorees named on the bronze and to Stanford University before the dedication. It is Mark Nichols’s judgment that the people involved in the plaque knew in 2005 that the Internet was not born at Stanford University, and was not born of the work that the plaque names.

10.0 The findings of the record support one correction, the replacement of the headline BIRTH OF THE INTERNET with the headline THE CONCEPTION OF TCP/IP

10.1 The headline uses the word “birth” for what the body records. The body records protocol conception, specification, testing, and the construction of a gateway.

10.2 The inscription credits BBN with building the gateway. The Internet Hall of Fame identifies Virginia Strazisar Travers’s contribution to the gateway software. The source is the Internet Hall of Fame page for Virginia Strazisar Travers.

10.3 The UCL record distinguishes the 1975 design account from the operational trial in late 1976 and terminal service by mid-1977. The sources are the Birth of the Internet UCL source record, Peter Kirstein, UCL report, February 1977, §6.4, and Peter Kirstein, UCL report, April 1978, §1.2.

10.4 PUP supplies a separate documented example of internetworking across 25 operating networks in 1979. The source is Boggs, Shoch, Taft, and Metcalfe, Xerox PARC report CSL-79-10, July 1979.

10.5 The 1977 separation proposal, the later separate specifications, and the ARPANET cutover plan each document different milestones. The sources are Jon Postel, IEN 2, August 15, 1977, RFC 760, RFC 761, and Jon Postel, RFC 801, November 1981.

10.6 TCP runs between the endpoints of a connection. A router can be an endpoint of its own control session while performing IP forwarding for traffic it carries on behalf of other hosts. The sources are Wesley Eddy, ed., RFC 9293, August 2022, and RFC 4271, January 2006, §3.

10.7 RFC 1122, Requirements for Internet Hosts -- Communication Layers, edited by Robert Braden for the Internet Engineering Task Force in October 1989, states at §1.1.2 that The Internet is a network of networks, and states at §1.1.1 that An Internet communication system consists of interconnected packet networks supporting communication among host computers using the Internet protocols. RFC 1200 of April 1991 and RFC 2200 of June 1997 list TCP at the status Recommended and IP at the status Required, and §6.3 of each edition states that it is elective to support any particular type of physical network. The public-admission criterion of D1 is a separate question from the status that RFC 1200 and RFC 2200 assign. The sources are Robert Braden, ed., RFC 1122, October 1989, §§1.1.1 through 1.1.3, RFC 1200, April 1991, §§6.2 and 6.3, RFC 2200, June 1997, §§6.2 and 6.3, and Governing Definitions, D1, D2, D3 and D6.

10.8 The bronze documents engineering and research milestones. The D1 public-admission claim requires a record of who could purchase service and how independent networks could interconnect.

10.9 The petition asks Stanford University to preserve the plaque and the complete inscription beneath the headline, and to replace “BIRTH OF THE INTERNET” with “THE CONCEPTION OF TCP/IP” on the bronze. Replacing the birth headline with the requested protocol-conception headline lets the monument credit the design, specification, testing, and gateway work documented in its inscription, while claims about founding the publicly joinable Internet remain subject to operating and admission evidence.

10.11 This letter is signed by Mark Nichols, Architect of the Modern Internet, Co-Founder and Chief Architect of Digital Island in 1996, designer and operator of the first Tier-0 global network, AS6553, issued August 29, 1996, and author of How I Made the Web World Wide, who is reached at mark@marknichols.com, and whose record stands at marknichols.com and in the Fact or Fiction series.

11.0 The claims of this letter are open to documented challenge on the standing terms of marknichols.com, and those terms are stated here in full

11.1 The claims on this page are open to challenge on the same terms as every claim on marknichols.com. A challenger who holds that a claim on this page is wrong, or that the Internet is something other than the publicly joinable network of networks of the registry lineage defined at The Governing Definitions and Controlling Facts of Telecommunications Internetworking, states the competing claim or definition in one sentence, names the document that carries it and the document’s date, and sends both to mark@marknichols.com. A challenge submitted with its document is answered on this page, and a competing definition submitted with its document is added to this page as an exhibit with attribution to the person who submitted it; a challenge submitted without a document is an opinion and is heard as one. The distinction the site’s definition rests on, that protocols enable interoperability and are not the Internet, is stated in the IETF’s own words, RFC 2026 and STD 1, in the Internet-Draft draft-mnichols-protocols-not-the-internet-01, posted by Mark Nichols to the IETF Datatracker on September 25, 2026 at the Datatracker page of draft-mnichols-protocols-not-the-internet and stated on this site at Protocols Are Not the Internet: The IETF Internet-Draft by Mark Nichols, so a challenger may also address the definition in the venue that publishes the protocol standards themselves. Any person who holds expertise in telecommunications and a competing claim or definition is invited to bring both, in writing, with the document.

12.0 The separate IEEE milestone plaque of May 2024 credits the optional protocol TCP with enabling the Internet in 1974 and dates an operational milestone to 1983

12.1 IEEE dedicated Milestone 254 in May 2024. IEEE’s record gives May 20 for the milestone and identifies a casting at Stanford University and another at the Computer History Museum. Its title reads “Transmission Control Protocol (TCP) Enables the Internet, 1974” on the casting. The citation identifies the May 1974 Cerf-Kahn paper, the later TCP and IP split, and a 1983 operational milestone. Exhibit 13.4 links to the separate IEEE plaque photograph. The source is the IEEE Milestone 254 inscription and dedication record.

12.2 The word “enables” can describe a contribution to interoperable communication. The body of the IEEE inscription supports that narrower reading by describing the early protocol work and the interconnection it supported. The scope objection is to treating protocol work as the opening of the public Internet defined under D1. The sources are the IEEE Milestone 254 inscription and dedication record and Governing Definitions, D1, D2, and D3.

12.3 IEEE’s May 13, 2024 release counts fifty years from the publication of the 1974 paper. The milestone’s body separately dates an operational event to 1983. One date refers to publication of a design. The other refers to the adoption and operation of that architecture in IEEE’s historical account. The sources are the IEEE press release of May 13, 2024 and the IEEE Milestone 254 inscription and dedication record.

12.4 RFC 801 establishes the ARPANET host transition plan and its January 1, 1983 target. The National Research Council’s account distinguishes the cutover from earlier TCP use and describes the ensuing transition. Under D1, an operational claim about the publicly joinable Internet requires evidence of public access and voluntary interconnection. Section 0.4 identifies the evidence used here for the 1991 public-commercial milestone. The sources are Jon Postel, RFC 801, November 1981, the National Research Council report, RFC 942, February 1985, printed pp. 25 and 26, the CIX operators’ announcement, March 25, 1991, and Mark Fedor, CIX-WEST traffic, October 1991, printed pp. 14 and 15.

12.5 The evidence identifies Vinton G. Cerf and Robert E. Kahn as the paper’s authors and separately credits the gateway and deployment work in the earlier sections. The IEEE plaque is a distinct source and is linked here for comparison with the 2005 Stanford inscription. The sources are the May 1974 paper of Vinton G. Cerf and Robert E. Kahn, A Protocol for Packet Network Intercommunication, and the IEEE Milestone 254 inscription and dedication record.

12.6 I credit the published 1974 design and the dated ARPANET protocol transition. My disagreement with IEEE concerns which event its wording dates as the arrival of the Internet. The request to replace one line on Stanford University’s 2005 plaque is stated in §10.9. The May 1974 design publication and the 1983 ARPANET protocol transition belong in the historical record as separate milestones, and any claimed opening of the publicly joinable Internet is established through its admission and operating records. The sources are Jon Postel, RFC 801, November 1981, and Governing Definitions, D1, D2, and D3.

13.0 Exhibits

13.1 Plate 13.1 shows the 2005 Stanford University plaque. The photograph below shows the bronze inscribed “BIRTH OF THE INTERNET” and dated July 28, 2005. The photograph is the primary visual record for the inscription and roster.

13.2 Exhibit 13.2 is the complete transcription of the Stanford University plaque. The transcription below retains the wording, capitalization, line breaks, and roster order as prepared from the bronze.

BIRTH OF THE INTERNET

THE ARCHITECTURE OF THE INTERNET AND THE DESIGN OF
THE CORE INTERNETWORKING PROTOCOL TCP (WHICH LATER BECAME TCP/IP)
WERE CONCEIVED BY VINTON G. CERF AND ROBERT E. KAHN DURING 1973
WHILE CERF WAS AT STANFORD'S DIGITAL SYSTEMS LABORATORY AND
KAHN WAS AT ARPA (LATER DARPA). IN THE SUMMER OF 1976, CERF LEFT STANFORD
TO MANAGE THE PROGRAM WITH KAHN AT ARPA.

THEIR WORK BECAME KNOWN IN SEPTEMBER 1973 AT A NETWORKING CONFERENCE IN ENGLAND.
CERF AND KAHN'S SEMINAL PAPER WAS PUBLISHED IN MAY 1974.

CERF, YOGEN K. DALAL, AND CARL SUNSHINE
WROTE THE FIRST FULL TCP SPECIFICATION IN DECEMBER 1974.
WITH THE SUPPORT OF DARPA, EARLY IMPLEMENTATIONS OF TCP (AND IP LATER)
WERE TESTED BY BOLT BERANEK AND NEWMAN (BBN),
STANFORD, AND UNIVERSITY COLLEGE LONDON DURING 1975.

BBN BUILT THE FIRST INTERNET GATEWAY, NOW KNOWN AS A ROUTER, TO LINK NETWORKS TOGETHER.
IN SUBSEQUENT YEARS, RESEARCHERS AT MIT AND USC-ISI, AMONG MANY OTHERS,
PLAYED KEY ROLES IN THE DEVELOPMENT OF THE SET OF INTERNET PROTOCOLS.

KEY STANFORD RESEARCH ASSOCIATES AND FOREIGN VISITORS

VINTON CERF

DAG BELSNES
RONALD CRANE
YOGEN DALAL
JUDITH ESTRIN
RICHARD KARP
GERALD LE LANN
JAMES MATHIS
BOB METCALFE
DARRYL RUBIN
JOHN SHOCH
CARL SUNSHINE
KUNINOBU TANNO

DARPA

ROBERT KAHN

COLLABORATING GROUPS

BOLT BERANEK AND NEWMAN
WILLIAM PLUMMER · GINNY STRAZISAR · RAY TOMLINSON

MIT
NOEL CHIAPPA · DAVID CLARK · STEPHEN KENT · DAVID P. REED

NDRE
YNGVAR LUNDH · PAAL SPILLING

UNIVERSITY COLLEGE LONDON
FRANK DEIGNAN · MARTINE GALLAND · PETER HIGGINSON
ANDREW HINCHLEY · PETER KIRSTEIN · ADRIAN STOKES

USC-ISI
ROBERT BRADEN · DANNY COHEN · DANIEL LYNCH · JON POSTEL

ULTIMATELY, THOUSANDS IF NOT TENS TO HUNDREDS OF THOUSANDS
HAVE CONTRIBUTED THEIR EXPERTISE TO THE EVOLUTION OF THE INTERNET.

DEDICATED JULY 28, 2005

13.3 Plate 13.3 shows physical line repair. The photograph below illustrates the work of restoring a damaged network facility. Section 7.7 explains its relation to transport recovery.

13.4 Exhibit 13.4 links to the 2024 IEEE milestone plaque. This is the separate plaque discussed in §12.0. IEEE’s record identifies the casting and the text of the citation. The sources are the IEEE milestone photograph and the IEEE Milestone 254 inscription and dedication record.