ETHW Robert Kahn Oral History: Disagreements | Network, Not Protocol

The introduction to the oral history of Robert Kahn that the IEEE History Center recorded on February 17, 2004 says he ended up “eventually becoming the director of DARPA” and was “critical in transforming Arpanet into the full-fledged Internet”, while Robert Kahn says in the same interview that he was “the longest tenured office director in IPTO”, that Larry Roberts “really architected the whole thing”, and that “The Internet was sort of a lot of LANs connected to the Arpanet with linkages to satellite nets.”

Preamble: I examine the oral history of Robert Kahn that Michael Geselowitz of the IEEE History Center recorded at the Corporation for National Research Initiatives in Reston, Virginia, on February 17, 2004, as interview #432, and that the Engineering and Technology History Wiki publishes with an introduction of its own. I test the introduction and four of Robert Kahn's own statements against the design paper of the Interface Message Processor of 1970, Robert Kahn's paper of November 1972 in the Proceedings of the IEEE, the profile of Robert Kahn published by the IEEE Computer Society, Robert Kahn's own words elsewhere in the same interview, and the Governing Definitions of marknichols.com. Exhibit A at section 8.0 reproduces the twenty-four excerpts that the findings cite, numbered and anchored, and every finding on this page cites those numbers. This page is Disagreement 91 in the standing index of the series, Disagreements of Published Claims | Network, Not Protocol, and a finding on this page is cited by that number followed by the finding's locus, as Disagreement 91, 1.1.

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

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

0.0 This section records the oral history this page examines, the excerpts it reproduces, and the definitions on which the findings depend.

0.1 The source examined on this page is Oral-History:Robert Kahn on the Engineering and Technology History Wiki at https://ethw.org/Oral-History:Robert_Kahn. The page heads the transcript with the line “ROBERT KAHN: An Interview Conducted by Michael Geselowitz, IEEE History Center, 17 February 2004” and asks that it be cited as “Robert Kahn, an oral history conducted in 2004 by Michael Geselowitz, IEEE History Center, Piscataway, NJ, USA.” Mark Nichols supplied the full text of the page to this record on November 13, 2026, and this page read it in full, all 666 lines.

0.2 The page carries two kinds of text. The introduction headed About Robert Kahn names no author, so the author of the introduction is unknown on this page. The transcript records the words of Robert Kahn and of Michael Geselowitz. Exhibit A at section 8.0 reproduces twenty-four excerpts, each a whole paragraph of the page: excerpts 1 and 2 are the introduction, excerpt 3 is the heading of the interview, and excerpts 4 through 24 are paragraphs of Robert Kahn's answers, under the transcript's own headings Bell Laboratories, DARPA Proposal, International Computer Conference (1972), Work at DARPA, Vint Cerf and the Growth of Arpanet, Leaving DARPA, Development of the Internet, The World Wide Web, Impact of the Internet and Deep Gratitude. The other paragraphs of the transcript are not reproduced, and this page makes no finding on them.

0.3 D1 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking defines the Internet as “The publicly joinable network of networks of the registry lineage”, and D6 states: “Protocols are utilities whose messages the networks carry; they are not the networks, and they are not the Internet.” The Definitions Addendum at section 9.0 reproduces D1 through D13 in full.

1.0 The introduction says Robert Kahn was “eventually becoming the director of DARPA”, while Robert Kahn says in the same interview that he was “the longest tenured office director in IPTO”, and the IEEE Computer Society records that he “became Director of DARPA's Information Processing Techniques Office (IPTO).”

1.1 Excerpt 1, the introduction, says: “Kahn would straddle the divide, first working at BBN and eventually becoming the director of DARPA.”

1.2 In excerpt 18, Robert Kahn says of his own post: “I’m sure that I was the longest tenured office director in IPTO.” The profile IEEE Computer Society, Robert Kahn, Award Recipient says: “In 1972 he moved to DARPA and subsequently became Director of DARPA's Information Processing Techniques Office (IPTO).” The Information Processing Techniques Office was one office of the agency, and the post that Robert Kahn held was the directorship of that office.

1.3 The kind is a documentary finding. The introduction's sentence is false as written under F56, because Robert Kahn directed the Information Processing Techniques Office of DARPA and not DARPA itself, as his own words in excerpt 18 and the profile of the IEEE Computer Society record. Governing Definitions, F56.

1.4 Corrected statement: Robert Kahn worked at Bolt Beranek and Newman, joined DARPA in 1972, and became the director of DARPA's Information Processing Techniques Office, the office he describes in excerpt 18 as the one he led longer than any other director.

2.0 The introduction says Robert Kahn “was instrumental in the creation of the Internet, from its earliest inception as ARPANET,” and “critical in transforming Arpanet into the full-fledged Internet”, while Robert Kahn says in the same interview that “We started out with just the three long-haul ones: the Arpanet, the packet radio net, and the satellite net”, and under D1 the ARPANET was one network and not the Internet.

2.1 Excerpt 1 says: “Robert Kahn was instrumental in the creation of the Internet, from its earliest inception as ARPANET, a private/public collaboration between Bolt Beranek and Newman (BBN) and the Defense Advanced Research Projects Agency (DARPA).” It ends: “He was also critical in transforming Arpanet into the full-fledged Internet.”

2.2 Robert Kahn describes the Internet in the same interview as networks joined, with the ARPANET as one of them. In excerpt 17 he says: “We started out with just the three long-haul ones: the Arpanet, the packet radio net, and the satellite net.” In excerpt 16 he says: “The Internet was sort of a lot of LANs connected to the Arpanet with linkages to satellite nets.” In excerpt 24 he says: “we started it out as a little research experiment, three nets that DARPA had been building”. In Robert Kahn's own words, the ARPANET was one of the networks that were joined, and it was not transformed into the Internet.

2.3 The kind is a definitional finding. Under D1, the Internet is the publicly joinable network of networks of the registry lineage born in 1991, and the ARPANET was one network. Section 3.0 of Internet Society Brief History of the Internet: Disagreements | Network, Not Protocol, Disagreement 6, records the same finding for the words “the budding Internet was off the ground.” The introduction's words “was instrumental in” and “was also critical in transforming” are recorded in Soft Verbs: A Running Register | Network, Not Protocol. Governing Definitions, D1.

2.4 The consequence for the historical record is that the ARPANET is recorded as one of the networks that DARPA's Internetting program joined, in Robert Kahn's own words of February 17, 2004, and not as the inception of the Internet.

3.0 Robert Kahn says he “played a very key role as principal designer of the Arpanet,” while in the same sentence group he says that Larry Roberts “really architected the whole thing” and that “I was actually the detail designer of how to make it work”, and the design paper of the Interface Message Processor of 1970 names five authors.

3.1 In excerpt 23, Robert Kahn says: “So from the point of view of creating nets where I think I played a very key role as principal designer of the Arpanet, not to take anything away from Larry. Because it wouldn't have happened without Larry Roberts, who really architected the whole thing and produced it and came up with the concept. I was actually the detail designer of how to make it work.”

3.2 Robert Kahn describes the division of the work in two further excerpts. In excerpt 5, he says of the request for quotation that DARPA issued: “So these were kind of architectural decisions that they had made on a very structural level.” In excerpt 6, he says of the proposal that Bolt Beranek and Newman submitted: “I actually wrote the technical part of the proposal.” He adds: “I wasn’t a hardware designer, and I didn’t consider myself a real time system programmer,” and he names “Severo Ornstein, who was the hardware guy.”

3.3 The design paper “The interface message processor for the ARPA computer network,” published in the Proceedings of the Spring Joint Computer Conference of 1970, AFIPS Conference Proceedings, volume 36, at pages 551 to 567, names its authors as F. E. Heart, R. E. Kahn, S. Ornstein, W. Crowther and D. Walden, as section 2.0 of Computer History Museum Robert Kahn: Disagreements | Network, Not Protocol, Disagreement 90, records.

3.4 The kind is a scope overstatement. Robert Kahn's own excerpts give the architecture of the ARPANET to Larry Roberts, the structural decisions to DARPA's request for quotation, the hardware to Severo Ornstein, and to himself the technical part of the proposal and the detail design, and the paper of 1970 names five designers of the Interface Message Processor. The words “principal designer of the Arpanet” claim more than the excerpts establish. The words “played a very key role as” are recorded in Soft Verbs: A Running Register | Network, Not Protocol.

3.5 Corrected statement: Larry Roberts of DARPA architected the ARPANET and set its structural decisions in the request for quotation of 1968, Robert Kahn wrote the technical part of the proposal of Bolt Beranek and Newman with Severo Ornstein on the hardware, and the design paper of the Interface Message Processor of 1970 names F. E. Heart, R. E. Kahn, S. Ornstein, W. Crowther and D. Walden as its authors.

4.0 Robert Kahn says “I had a basic architectural approach to deal with it, which is what became the Internet”, while his own account dates that approach to after his first day at DARPA, “probably early 1973,” his paper received on June 7, 1972 joins separate networks only if they “are jointly planned before development,” and under D1 the Internet was born in 1991.

4.1 In excerpt 12, Robert Kahn says: “So I had the problem of trying to figure in those nets, and I had a basic architectural approach to deal with it, which is what became the Internet.”

4.2 Robert Kahn dates the approach himself. In excerpt 9, he says: “I ended up going to DARPA right after that ICCC demo.” He says: “I think October 29th was my start date at DARPA, although I don’t know that I actually showed up on that day.” He says: “My first day was election day.” In excerpt 10, he says that the program he had come to run was killed “Probably one month after arriving or less,” and that “this was probably early 1973”. In excerpt 11, he says he then set up the packet radio program, and excerpt 12 follows it.

4.3 Robert Kahn's paper in the Proceedings of the IEEE of November 1972, received June 7, 1972 while he was at Bolt Beranek and Newman Inc., says: “If separate data networks are jointly planned before development, at least at the interconnection level, they may be connected at a later date and viewed together as a single network that evolved by way of separate networks.” Section 11.0 of Internet Society Brief History of the Internet: Disagreements | Network, Not Protocol, Disagreement 6, reproduces the passage and records that the condition of joint planning is the opposite of the ground rule that A Brief History of the Internet attributes to Robert Kahn.

4.4 The kind is a definitional finding under D1, with the date of the approach established by Robert Kahn's own words. The approach that Robert Kahn describes in excerpt 12 is dated by his own account to early 1973, after his first day at DARPA, and the words “which is what became the Internet” join that approach to the Internet that D1 dates to 1991. The words “which is what became” are recorded in Soft Verbs: A Running Register | Network, Not Protocol. Governing Definitions, D1.

4.5 Corrected statement: By Robert Kahn's own account of February 17, 2004, he began work on joining the packet radio, packet satellite and ARPANET networks at DARPA in early 1973, after a paper of his received June 7, 1972 had made the later connection of separate networks depend on joint planning before development. The capital-I Internet, publicly joinable by buyers and by independent networks, was born in 1991.

5.0 The transcript has Robert Kahn at Bell Laboratories “from roughly January of 1950 when I graduated from undergraduate school”, while the IEEE Computer Society and the Computer History Museum record his Bachelor of Electrical Engineering from the City College of New York in 1960.

5.1 In excerpt 4, the transcript says: “I was actually at Bell Labs only from roughly January of 1950 when I graduated from undergraduate school until September, when I went off to Princeton.”

5.2 The profile IEEE Computer Society, Robert Kahn, Award Recipient says: “After receiving a B.E.E. from the City College of New York in 1960, Dr. Kahn earned M.A. and Ph.D. degrees from Princeton University in 1962 and 1964 respectively.” Line 7 of the profile of the Computer History Museum, reproduced in Exhibit A of Computer History Museum Robert Kahn: Disagreements | Network, Not Protocol, says: “He holds a BEE from the City College of New York (1960), and MA and PhD degrees from Princeton (1962, 1964).”

5.3 The kind is a documentary finding. The transcript's year 1950 is false as written under F56, because Robert Kahn graduated from the City College of New York in 1960. On this page's inference, and only as an inference, the year 1950 is an error of transcription and not of Robert Kahn's memory, and the inference does not change the finding. Governing Definitions, F56.

5.4 Corrected statement: Robert Kahn worked at Bell Laboratories from about January 1960, when he graduated from the City College of New York, until September 1960, when he went to Princeton University.

6.0 Twenty excerpts of the oral history are examined and not disputed on this page, and several of them state in Robert Kahn's own words the findings that marknichols.com makes.

6.1 Excerpts 2, 3, 7, 8, 11, 13, 14, 19 and 20 state an introduction, a heading, the preparation of the demonstration of October 1972, the programs that Robert Kahn started at DARPA, the need for a better protocol, the collaboration with Vinton Cerf, the name National Information Infrastructure and the gigabit testbeds that no dated document on this page contradicts. Excerpt 19 and excerpt 20 carry Robert Kahn's own claims, “but I was calling it the National Information Infrastructure.” and “We funded the University of Illinois to build what became the Mosaic browser, which opened up the World Wide Web.”, and this page records both as his testimony and has not tested them against a dated document.

6.2 Excerpts 15, 16, 17, 21, 22 and 24 state in Robert Kahn's own words the account that marknichols.com gives. In excerpt 15 he says of the change of the ARPANET to TCP/IP: “It took about six months before everybody converted over”. In excerpt 16 and excerpt 17 he describes the Internet as networks joined. In excerpt 21 he says of the World Wide Web: “It’s an application, as I see it, on top of the Net. It doesn’t rebuild the Net.” In excerpt 22 he says: “What’s transformed society was the rapid propagation of networking, the creation of commercial Internet service providers, which really started in the late 1980s with places like UUnet and PSInet and a variety of others, both in the US and around the world. That’s what made it an international phenomenon.” Under D6, the growth of the Internet is credited to the networks, and in excerpt 22 Robert Kahn credits it to networking and to commercial Internet service providers, not to the protocols. Governing Definitions, D6.

6.3 Excerpts 5, 6, 9, 10 and 18 are relied on by sections 1.0, 3.0 and 4.0, and excerpt 23, in its words that credit Larry Roberts, is relied on by section 3.0 and by section 2.0 of Computer History Museum Robert Kahn: Disagreements | Network, Not Protocol, Disagreement 90, at its unit 2.3.

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

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

7.2 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 https://datatracker.ietf.org/doc/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.

8.0 Exhibit A reproduces the twenty-four excerpts of the oral history of Robert Kahn that the findings cite, each a whole paragraph of the page, numbered in the order of the page and anchored for citation.

8.1 Exhibit A. Engineering and Technology History Wiki, Oral-History:Robert Kahn, interview #432 conducted by Michael Geselowitz of the IEEE History Center on February 17, 2004, with an introduction whose author is unknown, as supplied by Mark Nichols on November 13, 2026 from https://ethw.org/Oral-History:Robert_Kahn. Excerpts 1 and 2 are the introduction, excerpt 3 is the heading of the interview, and excerpts 4 through 24 are paragraphs of Robert Kahn's answers, in the order of the page.

1. Robert Kahn was instrumental in the creation of the Internet, from its earliest inception as ARPANET, a private/public collaboration between Bolt Beranek and Newman (BBN) and the Defense Advanced Research Projects Agency (DARPA). Kahn would straddle the divide, first working at BBN and eventually becoming the director of DARPA. He was also critical in transforming Arpanet into the full-fledged Internet.

2. Like Leo Kleinrock, he thinks wireless will become like cell phones, and that we are currently in a transitory period. Also, like Kleinrock, the elderly Kahn is still working. He is CEO and President for the Corporation for National Research Initiatives (CNRI). Kahn views what has happened over the last thirty years or so as the “networking revolution.”

3. ROBERT KAHN: An Interview Conducted by Michael Geselowitz, IEEE History Center, 17 February 2004

4. I was hoping at the time to go to graduate school, but it wasn’t clear how we were going to finance that exactly. While I was at Bell Labs, I won an NSF fellowship, which let me go to a school of my choice. I ended up opting to go to Princeton, got accepted that fall. I was actually at Bell Labs only from roughly January of 1950 when I graduated from undergraduate school until September, when I went off to Princeton.

5. I got to meet Larry and Bob and those guys as a result of that, and shared with them what I had been doing. Lo and behold, I would say within a year of that time, they had worked up a whole package to get people to bid on building this network for them. And when the Request for Quotations came out, they pretty much thought they had specified what they wanted. It was general, like, “Deliver packets in a fraction of a second. They’re going to have these little nodes. They’re going to be linked together with 50 kilobits”—that sort of stuff was all prepackaged. But what they didn’t describe was how to build the actual network itself. So these were kind of architectural decisions that they had made on a very structural level.

6. I actually wrote the technical part of the proposal. I didn’t package all of it because a lot of it had to do with striking the deal through Honeywell to buy the computers and all of the stuff that was more management oriented. But the technical part of it I wrote with some very valuable help from Severo Ornstein, who was the hardware guy. As part of the proposal I had to describe what the hardware was. I wasn’t a hardware designer, and I didn’t consider myself a real time system programmer, but I could sit down with them and say, “Here’s how the hardware has to work. There’s this thing coming down that has to do this, this, this, this, and this.” He’d be designing in real time as I was talking, just manufacturing the specs on the spot. We put the whole proposal together, and it went in, and it worked. Here I was, trying to figure out?

7. We had four nodes that weren’t working, which was the problem at that time. My goal at that time was to do whatever I could to get the system design fixed, if you will. It had 80% of what I had in there originally, but there were still some problems. I spent until the next year doing that kind of thing. I recall there was a discussion that Larry Roberts—Larry had replaced Bob Taylor running the DARPA office. I had suggested that we do some kind of a public demonstration. My original thought was the Spring Joint Computer Conference. Larry actually made some arrangements to do it at the First International Computer Conference, which was to be held in October, I think, of 1972. He asked me if I would make that happen. He was actually working with Steve Crocker at the time, who was at the office. Steve and I interacted a lot on those issues.

8. I basically thought that would be a lot of fun, do a public demonstration. This was exciting stuff. I agreed to do a public demonstration of it, which may sound pretty dull, but it involved figuring out how to put a first node of the national net into a hotel room in the Washington, D.C. area and leave it up for the better part of a week, bring all the researchers and network people who knew anything to that area. We went around and got manufacturers to deliver terminals. We had to get all the machines up and working. We had to get the protocols on the machines. It was the driving force for making the whole network work, writing scenarios.

9. I didn’t really think of myself as a government employee or moving to Washington. But as it drew closer and closer, I finally ended up deciding maybe that was a good thing to do. I’m not sure I can articulate all the reasons for doing that, but I ended up going to DARPA right after that ICCC demo. I think October 29th was my start date at DARPA, although I don’t know that I actually showed up on that day. I think I went up to Boston, closed some things up, and ended up voting in the election of 1972 up in Cambridge and then getting on a plane. My first day was election day.

10. Probably one month after arriving or less, it was announced to me that Congress had killed the program. It wasn’t going to happen. I had the very agonizing decision, then, of deciding do I really want to be here, since what I came to do was not going to happen? I think I probably could have gone back up and gone into teaching again at that point. But this was probably early 1973, and what Larry said to me was, “Look. You know as much about networking as anybody, if not more. Why don’t you stay on and figure out some new things to do about networking?” Well, I had been thinking about it little by little in the background, because one of the things that I was sort of doing while I was getting started here was thinking how we could get a packet radio network going. Larry had started an effort on applying packet switching to satellites. I insisted I didn’t want anything to do with the Arpanet. I just didn’t want to have those issues come up again. So I didn’t. I think the program manager for it was either some combination of Steve Crocker or later Craig Fields. I eventually said, “Fine. I’ll do that for a few years,” again thinking I’ll just do that a year or two and then I’ll head out.

11. I ended up setting up the packet radio program. I revamped the satellite program something fierce, ended up starting a number of other programs in what’s now voice-over IP, packet-type speech recognition, and end-to-end security—some related problems like that. We had gotten enough support to get those programs up and launched. Here I am sitting with the notion of multiple networks, and I’m trying to think, how would we actually do anything interesting with them if we don’t connect them? Because the computers were all very big. If I have a radio net, what am I going to do with the radio net? I can maybe plug a terminal into a little interfacing computer, but I’ve got to get to some big machine to do anything interesting.

12. So I had the problem of trying to figure in those nets, and I had a basic architectural approach to deal with it, which is what became the Internet. The one problem that I did not know how to deal with back then was how to take the functionality that I knew needed to be in the computers and actually get them into all these different machines? Because they were all different. That was exactly the problem that Vint Cerf and Steve Crocker and others had worked on in developing the original host protocol for the Arpanet. You have to remember, that protocol was one that left you with just a wire coming out. The problem was that you sent something up that wire, and that wire was connected to another net. What were you going to do to direct where a packet should go? Furthermore, the Arpanet was a perfectly reliable network, or supposedly so, so what were you going to do in a radio case where you were behind a mountain and a signal couldn’t get there or in a tunnel or somebody jammed you, or just errors in propagation had caused errors to occur. How was this all going to play out?

13. We knew we needed a better protocol, something that involved some kind of an error detection and retransmission or correction scheme. We knew we needed to have a more robust—or at least I did, at that point—addressing mechanism. I had a pretty good idea of what we needed to do, but I didn’t know how to take that and actually figure out how to get it in the first machine. That’s why I asked Vint to work with me on this whole mission.

14. That’s how we actually got together was that thing. Through the interaction, what I had been proposing and what he knew from before actually got much better. The synergy between the two of us caused it to be far better than either one of us could ever have done alone. We then worked together and we gave contracts to Stanford, University College London, and BBN to do some initial implementations and do some testing. Of course, it started to roll out experimentally, I would say by the late ’75–’76 time frame. We did some three-node testing in ’77 and it was reported in that book, A Century of Innovation, produced by the National Academy of Engineering. But there were probably two network tests that were done in either late ’75 or ’76, most likely at BBN where they were building some of the gateway technology. No real record of exactly who did what, when, or how much. I have in some of their technical reports, which I haven’t gone back to really look at.

15. That’s sort of how things got started. The Internet really remained in a very experimental form until we decided that we would cut the Arpanet over to the use of TCP/IP in the early 1980s. The actual cut-over was supposed to be on 1 January of 1983. In fact, it didn’t all happen like that. It took about six months before everybody converted over, mainly because there were some that didn’t really believe it until the day it happened; others were just slow in doing their importations. But within a few weeks we had a big chunk of the Arpanet converted over.

16. People were plugging in local area nets into the system experimentally before that. This was a way to make all of that local area network traffic and computers become actually part of a working composite system. Remember, the IBM PC didn’t really come into being until the early 1980s, and even then it didn’t have enough power to really run TCP/IP protocols. These were mainly experimental workstations. Sun Microsystems was one of the first out of the box to have it bundled in. By the early 1980s, there were pockets of real capability developing, and they were all on LANs [Local Area Networks]. The Internet was sort of a lot of LANs connected to the Arpanet with linkages to satellite nets.

17. Well, no. We started out with just the three long-haul ones: the Arpanet, the packet radio net, and the satellite net. The LANs didn’t come along till a little bit later. We weren’t thinking personal computers and workstations for LANs at the time, but we were thinking general purpose nets. Of course the architecture of the Internet was just sufficiently general purpose that it didn’t matter whether it was a LAN or anything else, you could just sort of plug it in and keep going.

18. People normally don’t stay at DARPA. It’s intended to be a place you come in, spend a few years, and leave. In fact, I had thought about leaving several times, but I kept getting my arm twisted. I ended up staying there about as long as anybody ever has. I’m sure that I was the longest tenured office director in IPTO. In the mid-1980s, we had grown the office from perhaps the smallest office in all of DARPA when I took it over to perhaps the largest when I left. Part of that period involved spitting out all of the technology from DARPA that was involved with the FBI program. That might have been the biggest one, had it stayed. But with that gone, I think we had pretty much become if not the largest, one of the largest. In today’s knowledge, it was probably three quarters of a billion or a billion dollar equivalent. Back then I think the actual dollars were in the $200 million range, although some part of that money had actually gotten siphoned off into different offices. We created the Engineering Applications Office and the like, but we pretty much had the dominant research support for the whole field.

19. What I wanted to work on was information infrastructure, equivalent to building the superhighway. That’s something that Al Gore later popularized, but I was calling it the National Information Infrastructure. The Reagan administration at the time was very supportive of this, but not with government money. They thought the private sector should do it because they thought it smacked of industrial policy. The private sector viewed it like clean water and fresh air—they were all for it too, just a question of who paid for it.

20. We set that project up and ran it. I think it was a smashing success. We not only showed that high speed networking was viable, we built five independent networks. They had a big spread on me in the Business Section of the New York Times about three weeks later with a photo taken with a fish-eye lens from a very low level, so it made me look like I was about 300 pounds bigger than I am. But it was a very important thing. It put ATM on the map. It was the first demonstration of an ATM switch in a carrier central office. We demonstrated the first all-optical link between Illinois and Wisconsin. AT&T did it—I said “we”. AT&T did it with using their erbium-doped fiber amplifier technology, I believe. We funded the University of Illinois to build what became the Mosaic browser, which opened up the World Wide Web. It was a major effort.

21. The World Wide Web has become an extremely important means for people to access information. What most people don’t realize is, rather than the last word on information access, it’s really one of the early ones. Just like the Arpanet was an early step into networking, many people thought this was going to propagate around the world and be Arpanet forever. Well, the Internet showed that that was probably not the case. Just like with the Web, it’s a very important first step. That’s how many people access information, but it’s basically dealing with the public kinds of information for most people—whatever they can get to people and make available to them. It’s an application, as I see it, on top of the Net. It doesn’t rebuild the Net. It’s sort of using it for like connectivity in order to allow people to access resources. As a social phenomenon, it’s almost mind-boggling what’s happened. It’s energized the whole world to put up all kinds of information. There’s hardly any topic you can’t find useful information about on the Web. And of course, all the search engines which go through and gobble up everything and index it for you, has made it pretty easy for people to gain access to the public side of it.

22. E-mail has been around since the early 1970s. What’s transformed society was the rapid propagation of networking, the creation of commercial Internet service providers, which really started in the late 1980s with places like UUnet and PSInet and a variety of others, both in the US and around the world. That’s what made it an international phenomenon. The e-mails were there right from the get-go, so I think what it did was enable people to essentially rely on that as an alternative to necessarily sending letters or calling on the phone. What the Web did was enable people who now were motivated to get on to the Internet through whatever mechanism, to be able to access all kinds of public information of all types. I think that has made a huge difference in how things work, because if you wanted to track what was going on in Washington, you had to either come to Washington or know somebody here. It was hard to get official documents. You didn’t even know what was out there. If you wanted to deal with your local tax regime, you had to go there, and people had to take time out of their lives to do that. Today, almost all of this information is just directly available. You simply go on your machine and download it.

23. Well, I’ve been privileged to be part of this networking revolution almost literally from day one. In fact, from day one of actual implementation. Nothing like this could have happened on such a scale without a lot of people being actively involved. So from the point of view of creating nets where I think I played a very key role as principal designer of the Arpanet, not to take anything away from Larry. Because it wouldn't have happened without Larry Roberts, who really architected the whole thing and produced it and came up with the concept. I was actually the detail designer of how to make it work. To all the people that helped in the creation of the Internet, of which Vint Cerf is my sort of alter ego on this because he and I really did the basic work on that together. There are thousands of people around the world who have been involved in helping to make that a reality, many today who would probably not even recognize our names as original contributors because they probably weren't even born when we did that, that the whole evolution of this thing has really been amazing to me.

24. If I had to predict it, I never could have predicted it as it turned out, because we started it out as a little research experiment, three nets that DARPA had been building and watched all of these things that pulled around us. No one could have predicted the chain of events: The creation of the personal computer market; the willingness of the Defense Department to open up their networks to broader scientific use; the willingness of the National Science Foundation to open to all of science and education; the congressional willingness to open up the NSF Tech to commercial use; the evolution of the Dell system, which brought more competition in the market. If you had known that up front, it never would have happened. Probably the reason I think we were successful was that so few people saw it as that meaningful when we started it; whereas today in the world of the digital object world, everybody’s dealing with managing information, whether it’s a library community, the publishers, the banks--so it’s a much more difficult road to hoe. But what happened with the Internet probably could not have happened if people understood what a big impact it was likely to have. So for that, I think I’ve been very fortunate to have a very special place in history, and to have watched it really from square zero.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

D12. Contemporary primary-source documents control over retrospective accounts, institutional narratives, biographies, media summaries, machine-generated responses, and personal recollections.

D13. Any finding in this record may be amended upon production of contemporaneous documentary evidence demonstrating a materially earlier, later, or contrary fact.