RFC 1208: Disagreements | Network, Not Protocol

On November 16, 2026, Mark Nichols set Request for Comments (RFC) 1208, "A Glossary of Networking Terms," written by Ole J. Jacobsen and Daniel C. Lynch of Interop, Inc. and published in March 1991, against dated documents and found two of its sentences false as written, that the Advanced Research Projects Agency Network (ARPANET) was "A packet switched network developed in the early 1970s," which the completion report that Bolt Beranek and Newman Inc. (BBN) prepared on January 4, 1978 answers by recording that the first four packet switches of the network "were developed and installed on schedule by the end of 1969," and that an Autonomous System is a collection of gateways that "cooperate using a common Interior Gateway Protocol (IGP)," which RFC 1163 of June 1990 answers by recording that "it has become common for a single AS to use several interior gateway protocols," and found that the glossary calls the ARPANET the "grandfather" of today's Internet and names no document for that descent, and that the glossary makes connectivity under the optional protocol Internet Protocol (IP) the condition of being on the Internet, when the Internet, with a capital I, is defined on marknichols.com by open admission and was born in 1991.

Preamble: I created this page to examine how Request for Comments (RFC) 1208, "A Glossary of Networking Terms," a memo of March 1991 by Ole J. Jacobsen and Daniel C. Lynch of Interop, Inc., defines the networks, the bodies and the protocols of the Internet that it describes. The page tests the memo's date for the development of the Advanced Research Projects Agency Network (ARPANET), its description of the ARPANET as the "grandfather" of today's Internet, its statement that "To be on the Internet you must have IP connectivity," its definition of an Autonomous System by "a common Interior Gateway Protocol (IGP)," and its entries for the optional protocols Internet Protocol (IP) and Transmission Control Protocol (TCP). A glossary states how its authors used their terms on the date of the glossary, and a statement of history that stands inside a definition is a statement of history, to be read against the dated records of the network that it names. Each disagreement on this page cites the memo's sentence by its number in Exhibit A in section 8.0 and names the dated document that decides it. RFC Editor, RFC 1208 · The Governing Definitions and Controlling Facts of Telecommunications Internetworking. This page is Disagreement 1 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 1, 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 memo this page examines, the sources this page read, the way the sentence numbers on this page are read, the definitions and rules the findings apply, the audit of the memo as an authority, and the order of the sections that follow.

0.1 This page examines Request for Comments (RFC) 1208, "A Glossary of Networking Terms," in the text that the RFC Editor serves at rfc-editor.org. The memo is headed "Network Working Group," it names "O. Jacobsen" and "D. Lynch" as its authors and "Interop, Inc." as their company, it is dated "March 1991," and its closing section, "Authors' Addresses," names the two authors in full as Ole J. Jacobsen and Daniel C. Lynch. The memo runs to 18 printed pages, and each printed page after the first carries the running head "INTEROP Pocket Glossary." Its first section, "Status of this Memo," says at sentence 1 that the memo is a glossary adapted from a pocket glossary of networking terms that was "distributed at Interop '90," and it says at sentence 2 and at sentence 3: "This memo provides information for the Internet community." "It does not specify an Internet standard." The record of the RFC Editor for RFC 1208, read on November 16, 2026, gives the status of the memo as "INFORMATIONAL" and its source as "Legacy." The memo names no working group as its source, no vote and no adopting body, and it has no list of references. RFC Editor, RFC 1208 · RFC Editor, record of RFC 1208.

0.2 This page read the following sources on November 16, 2026, and it states for each source that it did not read in full the part of the source that it read.

  1. RFC 1208 was read in full, all 18 printed pages, in the text that the RFC Editor serves, and the 470 sentence units of Exhibit A in section 8.0 were compared with that text on November 16, 2026 and reproduce it character for character, apart from the spaces between words and the four divided words that 8.1 records. The record of the RFC Editor for RFC 1208 was read in full.
  2. RFC 1160, "The Internet Activities Board," by Vinton G. Cerf of the Corporation for National Research Initiatives, dated May 1990, and RFC 4, "Network Timetable," by Elmer B. Shapiro of Stanford Research Institute, dated 24 March 1969, were each read in full in the text that the RFC Editor serves.
  3. RFC 1, "Host Software," by Steve Crocker of the University of California at Los Angeles (UCLA), dated 7 April 1969, was read at its heading, its table of contents and its introduction. The rest of the memo was not read.
  4. RFC 1009, "Requirements for Internet Gateways," by R. Braden and J. Postel of the Information Sciences Institute (ISI), dated June 1987, was read at its heading, its first section and its section 1, which holds sections 1.1 through 1.3. The rest of the memo was not read.
  5. RFC 1163, "A Border Gateway Protocol (BGP)," by Kirk Lougheed of cisco Systems, Inc. and Yakov Rekhter of the T.J. Watson Research Center of IBM Corporation, dated June 1990, was read at its heading, its first section, its sections 1 through 3 and its closing section on its authors. The rest of the memo was not read. RFC 1105 of June 1989, the earlier memo on the same protocol that RFC 1163 obsoletes, was searched in full for the passage that 4.4 quotes and was not read.
  6. RFC 1930, "Guidelines for creation, selection, and registration of an Autonomous System (AS)," by John Hawkinson of BBN Planet and Tony Bates of MCI, dated March 1996, was read at its heading, its abstract, its sections 1 through 3 and its section 8. The rest of the memo was not read.
  7. RFC 1200, "IAB OFFICIAL PROTOCOL STANDARDS," issued by the Internet Activities Board (IAB) with J. Postel as editor and dated April 1991, was read at its introduction, its sections 1 and 2, its section 4.1.5, its section 4.2, its section 5.1, the entry for RFC 1208 in its section 6.1.1 and its section 6.2, in the copy of the RFC Editor's text that the Wayback Machine of the Internet Archive saved on December 19, 2024. RFC 2200, "INTERNET OFFICIAL PROTOCOL STANDARDS," issued by the Internet Architecture Board with J. Postel as editor and dated June 1997, was read at its heading, its definitions of the grades and its section 6.2, in the copy that the Wayback Machine saved on October 12, 2025. The rest of each memo was not read.
  8. RFC 1251, "Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members," by Gary Scott Malkin of FTP Software, Inc., dated August 1991, was read at its heading, its sections 1 through 3, the headings of its eighteen biographies and its sections 4.15 through 4.18. The bodies of the other fourteen biographies were not read.
  9. RFC 791 of September 1981, the specification of the Internet Protocol, was read in full at its sections 1 and 2. RFC 793 of September 1981, the specification of the Transmission Control Protocol, RFC 1122 and RFC 1123 of October 1989, RFC 1812 of June 1995 and RFC 2684 of September 1999 were each retrieved in full and searched, and each was read at its heading and at the passages that this page quotes, RFC 1812 in full at its sections 4.3.3.6 and 5.3.9 and RFC 1122 in full at its section 1.1.3. The rest of each memo was not read on this date.
  10. The completion report of the ARPANET, dated January 4, 1978, within BBN Report 4799, "A History of the ARPANET: The First Decade," dated April 1981, was retrieved in full, 208 pages, and its text was searched in full for the year 1969. It was read in page images at its title pages and at its printed pages II-12, III-18, III-55 and III-79. The rest of the report was not read for this page.
  11. The ARPANET Directory of December 1978, numbered NIC 46099, is a file of 1,086 pages that Google digitized from a copy of the library of Stanford University. This page read its cover, its table of contents and its printed pages 1 through 13 and 15, and it checked the cover and the printed pages 6, 11 and 13 against the page images. The rest of the directory was not read.
  12. The page "ARPANET" of SRI International was read in full at its own address. The release of March 25, 1991 on the Commercial Internet Exchange (CIX) was read in full in the copy that marknichols.com preserves from message 441 of the com-priv archive at the Massachusetts Institute of Technology, which F52 of the Governing Definitions seats.
  13. RFC 1983, "Internet Users' Glossary," with G. Malkin of Xylogics as editor, dated August 1996, was read at its entry for the InterNIC, and the page "About" of the American Registry for Internet Numbers (ARIN) was read at its first paragraph. The rest of each was not read for this page.
  14. The Governing Definitions and Controlling Facts of Telecommunications Internetworking were read in full at D1 with D1.1 through D1.8, at D2, D3, D5, D7, D8, D9, D11, D12 and D13, at D6.12, and at F27, F31, F33, F37, F38, F40, F52, F56 and F57, and were read at the opening parts of D4, D6 and D10.

0.3 Each sentence number on this page refers to Exhibit A in section 8.0. Exhibit A lists the text of RFC 1208 sentence by sentence, in the order the memo prints it, under the memo's own headings, and it numbers the sentence units from 1 through 470. The numbers are editorial locators that this page adds, and they are not numbers of the memo's authors. The count begins with the first sentence of the section "Status of this Memo" and ends with the one sentence of the section "Security Considerations." Each sentence of prose, each expansion of an acronym that the memo punctuates as a sentence, each fragment of a glossary entry and each cross-reference that begins with the word See counts as one unit, and the label of a glossary entry stays with the first unit of the entry. An abbreviation, a decimal point or a page break does not begin a new unit. The printed page that this page gives for a sentence is the page of the memo on which the sentence begins. Each disagreement also quotes the sentence it answers.

0.4 The capital-I Internet (D1) is the publicly joinable network of networks of the registry lineage, whose addresses and autonomous system numbers were issued by the InterNIC, the project of network information services that began operations in April 1993 with the partial support of the National Science Foundation and whose registration services Network Solutions, Inc. provided, and are maintained today by the American Registry for Internet Numbers (ARIN). On that network, a person can buy access from competing providers for lawful purposes, and an independent network can obtain addresses and an autonomous system number and interconnect by agreement with a willing network, without the permission of a central owner or the sponsorship of a government. An intranet (D2) is a network, at any scale and under any protocol, whose members join by an owner's permission. Internetworking (D3) is the technique of interconnecting distinct networks through gateways so that traffic originating on one network can reach hosts on another. A lowercase internet (D11) is any interconnection of networks, including gated ones, and the capital I in this site's own prose means the publicly joinable network of the registry lineage born in 1991 and nothing else. Under D1.7, the ARPANET and the National Science Foundation Network (NSFNET) are not in the lineage of the capital-I Internet, and the words "foundation," "precursor," "ancestor," "became" and "evolved into" are not applied in this site's voice to the ARPANET relative to the Internet. D1.7 also names the word that sentence 42 of the memo uses: no page of marknichols.com calls the ARPANET or the NSFNET the grandfather, the ancestor, the parent, the precursor or the forerunner of the Internet. Governing Definitions, D1, D1.7, D2, D3, and D11.

0.5 This page answers three kinds of disagreement, and each disagreement on this page names the kind that applies.

  1. A documentary contradiction occurs when a dated record conflicts with a sentence as written. This page answers it with the dated record and a dated correction.
  2. A scope overstatement occurs when the evidence establishes a narrower event, network, date or function than the sentence claims. This page answers it with the scope the evidence establishes.
  3. A definitional disagreement occurs when the memo and this site apply different criteria to the same term. This page answers it by attributing each usage to its source.

Under D6, the Internet protocols are the optional protocols TCP and IP, utilities whose messages the networks carry, and the optional protocols TCP and IP are not the networks and are not the Internet. A protocol designer writes a specification that hosts and routers implement, and a specification does not by itself supply the networks, the equipment, the agreements, or the historical acts that put an operating network into service. An entry of a glossary for a protocol is therefore read on this page as a description of the protocol, and this page assigns each function that an entry names to the component, the network and the document that the record names. Governing Definitions, D6 · Protocol Designers Were Not the Creators of the Internet.

0.6 The memo names two authors and no adopting body. This page applies to it the five checks that Mark Nichols ruled on October 2, 2026, and extended on October 23, 2026, for every authority a page cites or disputes, and the five checks return the following results.

  1. The issuing body is the series of memos called Request for Comments, and its membership rule is open submission. RFC 1200 of April 1991 calls the memos of the series the working notes of the "Network Working Group," a group that it describes in the words "the Internet research and development community," and it says: "Anyone can submit a document for publication as an RFC." RFC 1160 of May 1990 says that the Internet Activities Board (IAB) "Manages the RFC publication process," and it says of the board itself: "New members are appointed by the chairman of the IAB, with the advice and consent of the remaining members."
  2. The roster on the date of the act is the two authors that the memo names and the editor of the series. The memo names Ole J. Jacobsen and Daniel C. Lynch of Interop, Inc. and states the title of neither. RFC 1251 of August 1991 says: "Daniel C. Lynch, 49, is president and founder of Interop, Inc." The title of Ole J. Jacobsen at Interop, Inc. is not stated in a document that this page read and is stated on this page as unknown. RFC 1160 of May 1990 lists "Jonathan Postel/USC-ISI" as "RFC Editor," where USC-ISI is the Information Sciences Institute of the University of Southern California, and RFC 1251 of August 1991 heads his biography "Dr. Jonathan B. Postel, IAB Member, RFC Editor."
  3. The instrument carries two named authors and no vote. RFC 1200 of April 1991, issued in the month after the memo, lists RFC 1208 among the new memos of the series with the words: "This is an information document and does not specify any level of standard." The decision table of RFC 1200 leaves a paper of information or opinion that comes from a source other than the IAB to the discretion of the RFC Editor, in the words: "The RFC Editor decides if a review is needed and if so by whom." RFC 1200 also says: "While RFCs are not refereed publications, they do receive technical review from the task forces, individual technical experts, or the RFC Editor, as appropriate." The documents that this page read record no review of RFC 1208, and this page makes no finding on whether a review took place.
  4. The custodian is the RFC Editor, which serves the memo at rfc-editor.org. The record of the RFC Editor for RFC 1208, read on November 16, 2026, gives the status of the memo as "INFORMATIONAL" and its source as "Legacy," lists no memo that obsoletes it and no memo that updates it, and holds no entry in its field for errata. RFC 1200 says of the series: "Once a document is assigned an RFC number and published, that RFC is never revised or re-issued with the same number." The memo is therefore a dated instrument of March 1991 and not a living text. The heading of the memo names the Network Working Group and two persons of Interop, Inc., and the memo does not name the Internet Engineering Task Force (IETF) as its source; the memo's own sentence 203 and sentence 204 describe the IETF as one of the task forces of the IAB.
  5. The overlap between the memo's authors and the author of this page is none, because this page names its author, Mark Nichols, and the memo names Ole J. Jacobsen and Daniel C. Lynch. The overlap between the memo's authors and the body that the memo describes is recorded here as a finding. RFC 1160 of May 1990 lists "Daniel Lynch/Interop, Inc." among the eleven members of the Internet Activities Board, RFC 1251 of August 1991 heads his biography "Daniel C. Lynch, IAB Member," and sentences 195 through 197 of the memo describe that board. The memo's own sentence 1 and sentence 5 say that its text is adapted from a pocket glossary that was "distributed at Interop '90" and was produced for "the INTEROP Tutorials, Conference, and Exhibition," the conference and exhibition of the company that RFC 1251 says Daniel C. Lynch founded. This page makes no finding on what the overlap caused.

Under D12, contemporaneous primary documents control over retrospective accounts. The memo is a glossary of two named authors that, in its own words at sentence 3, does not specify an Internet standard, it has no list of references, and its entry for the ARPANET names no document. Its statements about the history of the ARPANET are a retrospective account, written nine months after June 1990, the month in which the memo's own sentence 43 says that the ARPANET was decommissioned. No sentence of the memo is carried on this page as controlling. Every disagreement below is decided by the dated document that the disagreement names, and not by the standing of the memo. Governing Definitions, D12.

0.7 Under F56, Mark Nichols ruled on October 23, 2026 that a sentence of history or of definition is true or false as written. This page reads every sentence of the memo as written. The meaning an author may have intended but did not write is not in the record, and a sentence whose predicate is false as written is false, whether the falsity arose from compression, from shorthand or from intent. Each corrected statement on this page supplies the network, the document, the date or the event that the sentence left out. Governing Definitions, F56.

0.8 Sections 1.0 through 4.0 each state one disagreement.

  1. Section 1.0 answers the date that sentence 41 gives for the development of the ARPANET.
  2. Section 2.0 answers the word "grandfather" at sentence 42.
  3. Section 3.0 answers the condition of being on the Internet that sentence 219 states.
  4. Section 4.0 answers the definition of an Autonomous System at sentence 51.
  5. Section 5.0 records the entries for the optional protocols Internet Protocol (IP) and Transmission Control Protocol (TCP) at sentence 226, sentence 227 and sentences 434 through 437, and the component at which each protocol does its work.
  6. Section 6.0 records the statements of the memo that the documents support. Section 7.0 states the findings of this page and their consequences for the memo as an authority. Section 8.0 holds Exhibit A, the numbered text of RFC 1208.

1.0 Sentence 41 says that the ARPANET was "A packet switched network developed in the early 1970s," which is false as written as to the date, because the completion report that Bolt Beranek and Newman Inc. prepared on January 4, 1978 records that the first four packet switches of the network "were developed and installed on schedule by the end of 1969," and the ARPANET Directory that the Network Information Center of SRI International published for the Defense Communications Agency in December 1978 dates the origin of the network to late 1969.

1.1 The entry for the ARPANET stands on printed page 2 of the memo and has three sentences. Sentence 41 says: "ARPANET: A packet switched network developed in the early 1970s." Sentence 42 reads in full, with the memo's own quotation marks around one word: The "grandfather" of today's Internet. Sentence 43 says: "ARPANET was decommissioned in June 1990."

1.2 Mark Nichols disputes the words "developed in the early 1970s." The sentence introduces the network by the period of its development, and the period that it gives begins after the network was in operation. This is a documentary contradiction, decided by the report of the company that built the packet switches of the network, by the directory of the agency that operated the network, and by two memos of the network's own working group that are dated in the spring of 1969. The disagreement concerns the date of the ARPANET itself, and it does not deny that the network continued to be developed and enlarged during the 1970s. The finding assigns no date to any later internetwork or to the Internet, with a capital I, which was born in 1991.

1.3 The completion report of the ARPANET is dated January 4, 1978, was prepared by F. Heart, A. McKenzie, J. McQuillan and D. Walden of Bolt Beranek and Newman Inc. (BBN), the company that built the packet switches of the network, and stands within BBN Report 4799, "A History of the ARPANET: The First Decade," dated April 1981. Its printed page II-12 says of the solicitation, which it calls an RFP: "An RFP was prepared and issued in July 1968." Its printed page III-18 says of the contract for the Interface Message Processors (IMPs), the packet switches of the network: "The contract was awarded and work began the second day of the New Year in 1969." Its printed page III-55 says: "The first four IMPs were developed and installed on schedule by the end of 1969." Its printed page III-79 says: "The first ARPANET node was installed at the University of California at Los Angeles in late 1969 and the next three nodes were installed in California and Utah." The map on the same page carries the caption "Figure 5: The ARPANET in December 1969." The report of the company that built the packet switches therefore places the solicitation in July 1968, the start of the work on the second day of 1969, and the development and the installation of the first four packet switches before the end of 1969. F37 of the Governing Definitions records the solicitation as Request for Quotations No. DAHC15 69 Q 0002, issued July 29, 1968. BBN Report 4799, April 1981, printed pages II-12, III-18, III-55 and III-79 · Governing Definitions, F37.

1.4 The ARPANET Directory of December 1978, numbered NIC 46099, was prepared for the Defense Communications Agency (DCA) and was produced and published by the Network Information Center of SRI International in Menlo Park, California. Its printed page 6 says: "In July 1975, the DCA became the operational manager of the ARPANET." The same page, under the heading "WHAT THE ARPANET IS," says that the ARPANET began "as a purely experimental network in late 1969 under a research and development program sponsored by DARPA," the Defense Advanced Research Projects Agency. The directory of the agency that operated the network therefore dated the origin of the network, nine years after the event, to late 1969. ARPANET Directory, December 1978, printed page 6.

1.5 Two memos of the network's own working group carry dates in the spring of 1969. RFC 4, "Network Timetable," by Elmer B. Shapiro of Stanford Research Institute, is dated 24 March 1969, and its entries read "Imp installation 9/15/69" and "Test messages between UCLA-SRI 10/15/69," followed by test messages with the University of California, Santa Barbara for 11/15/69 and with the University of Utah for 12/15/69. RFC 1, "Host Software," by Steve Crocker of the University of California at Los Angeles (UCLA), is dated 7 April 1969, and it says: "The software for the ARPA Network exists partly in the IMPs and partly in the respective HOSTs." RFC 1 also says: "During the summer of 1968, representatives from the initial four sites met several times to discuss the HOST software and initial experiments on the network." RFC 4 is a timetable and records a plan, and this page cites it for the plan and not for the acts. The two memos establish that the software and the schedule of the network were the subjects of written memos in March and April of 1969. RFC 4, 24 March 1969 · RFC 1, 7 April 1969.

1.6 SRI International, one end of the first transmission, dates that transmission to the autumn of 1969. Its page "ARPANET," read on November 16, 2026, says: "The very first transmission on the ARPANET occurred at 10:30 p.m. on October 29, 1969, when UCLA attempted to send a message to SRI." The page continues: "The University of California, Santa Barbara and the University of Utah joined ARPANET later that year to create a four-node network." The page is a retrospective account of the institution, and this page cites it for the date and for the four nodes only. The opening sentence of the page, which places in the ARPANET the beginning of what it calls "The internet as we know it today," is the page's own, and section 2.0 answers that claim. SRI International, ARPANET.

1.7 The memo's own entry for RFC and a memo of the same series of May 1990 stand beside sentence 41. Sentence 377 of the memo, in the entry for RFC, describes the Request for Comments as "The document series, begun in 1969, which describes the Internet suite of protocols and related experiments." RFC 1160 of May 1990, "The Internet Activities Board," by Vinton G. Cerf of the Corporation for National Research Initiatives, says: "The archival RFC series was initiated in 1969 by Dr. Stephen D. Crocker as a means of documenting the development of the original ARPANET protocol suite." RFC 1160 dates the effort itself one year earlier: "In 1968, the U.S. Defense Advanced Research Projects Agency (DARPA) initiated an effort to develop a technology which is now known as packet switching." RFC 1160 gives the early 1970s to other programs: "During the early 1970's, DARPA initiated a number of programs to explore the use of packet switching methods in alternative media including mobile radio, satellite and cable." Ten months before the glossary was published, therefore, a memo of the same series dated the effort to 1968, dated to 1969 the series of memos that documented the development of the ARPANET's protocols, and gave the early 1970s to the programs in radio, satellite and cable. This page makes no finding on how sentence 41 came to give the early 1970s to the ARPANET. RFC 1160, May 1990.

1.8 The words "developed in the early 1970s" in sentence 41 of RFC 1208 of March 1991 are false as written under F56, because the completion report that Bolt Beranek and Newman Inc. prepared on January 4, 1978 records that the first four Interface Message Processors were developed and installed by the end of 1969, the ARPANET Directory of December 1978 dates the origin of the network to late 1969, and RFC 4 of 24 March 1969 and RFC 1 of 7 April 1969 are dated memos of the network's development. The network continued to be developed and enlarged during the 1970s, and that later work does not make the early 1970s the period in which the network was developed. Governing Definitions, F56.

1.9 Corrected statement: The ARPANET was a packet switched network of the Advanced Research Projects Agency of the United States Department of Defense, for which the solicitation was issued in July 1968, on which Bolt Beranek and Newman Inc. began work on the second day of 1969, and whose first four Interface Message Processors were developed and installed by the end of 1969, the first of them at the University of California at Los Angeles. The network continued to be developed and enlarged during the 1970s, and sentence 43 of the memo records that it was decommissioned in June 1990.

2.0 Sentence 42 calls the ARPANET the "grandfather" of today's Internet, which is a definitional disagreement under D1, D1.7 and D2, because the ARPANET Directory of December 1978 admits subscribers to the ARPANET only by the authorization of the agency that operated it, the memo names no document for the descent that it asserts, and the Internet, with a capital I, was born in 1991 of an agreement among the commercial networks AlterNet, CERFnet and PSINet that their operators announced on March 25, 1991.

2.1 Sentence 42 of the memo, the second sentence of the entry for the ARPANET on printed page 2, reads in full, with the memo's own quotation marks around one word: The "grandfather" of today's Internet. Sentence 217, on printed page 8, states what the memo means by the Internet, and after the label of the entry and a note on the capital letter it says: "The largest internet in the world consisting of large national backbone nets (such as MILNET, NSFNET, and CREN) and a myriad of regional and local campus networks all over the world."

2.2 Mark Nichols disputes the word "grandfather" and the descent that the word asserts. The word is a metaphor of family, and it gives the ARPANET a place in the lineage of the Internet without naming the act, the date or the document by which the one network descended from the other. This is a definitional disagreement under D1, D1.7 and D2. The memo applies the name Internet to the system of interconnected networks that it describes in March 1991, and this site applies the name to the publicly joinable network of networks of the registry lineage, which was born in 1991 and which admits anyone.

2.3 The memo names no document for the descent. RFC 1208 has no list of references, and the entry for the ARPANET cites nothing. The section "For More Information" sends the reader, at sentence 469, to the books, the standards documents and the other sources that are listed under the title "Information Sources" in "the December 1989 issue of ConneXions--The Interoperability Report." D1.5 of the Governing Definitions records the same fact, that the memo calls the ARPANET the "grandfather" of today's Internet with no document for the descent it asserts. A reader of sentence 42 therefore receives the claim of descent on the authority of the memo alone, and 0.6 records what that authority is. Governing Definitions, D1.5.

2.4 In December 1978 the ARPANET admitted its subscribers by the authorization of the agency that operated it. The ARPANET Directory of December 1978 states, on its printed page 11 and under the heading "WHO MAY BE A SUBSCRIBER ON THE ARPANET," four classes of subscriber. Of the activities of the Department of Defense (DoD) the directory says: "Subject to the availability of assets, DoD activities will be connected to the ARPANET provided the requests are processed through normal communications validating channels." Of the other activities of the government it says: "Requests for ARPANET service from non-DoD U.S. Government activities will be considered by DCA on a case-by-case basis." Of activities outside the government it says: "A DoD or other U. S. Government activity authorized to use the network may sponsor, as a user, a non-government activity performing contract work for the U. S. Government." Of activities outside the United States it says: "Non-U. S. activities will not be directly connected to the ARPANET." Printed page 13 of the directory says: "The ARPANET is intended to be used solely for the conduct of, or in support of, official U. S. Government business." The same page says that the use of the network "is not intended to compete with existing commercial services." In December 1978, therefore, no person and no company could join the ARPANET by buying access. An activity of the government applied to the Defense Communications Agency, and a company entered only as the sponsored contractor of an activity of the government. Under D2, a network whose members join by an owner's permission is an intranet, and the directory of the network's own operator states that permission in four classes. D1.2 of the Governing Definitions records that the ARPANET admitted its members by its owner's authorization from its procurement to its end. ARPANET Directory, December 1978, printed pages 11 and 13 · Governing Definitions, D1.2, D2 and D4.

2.5 The memo's own entries describe the networks of its Internet as funded and sponsored networks. Sentence 40 calls the Advanced Research Projects Agency "the U.S. government agency that funded the ARPANET." Sentence 267 says that the Military Network (MILNET) was partitioned from the ARPANET "to make it possible for military installations to have reliable network service, while the ARPANET continued to be used for research." Sentence 306 calls the National Science Foundation the "Sponsors of the NSFNET," the National Science Foundation Network, and sentence 309 says: "NSFNET provides scientists access to a number of supercomputers across the country." Sentence 43 says: "ARPANET was decommissioned in June 1990." By the memo's own account, therefore, the ARPANET was a network that one agency funded and that was used for research, and it had been decommissioned nine months before the memo was published.

2.6 The specification of the gateways of June 1987 lists the ARPANET among sponsored networks. RFC 1009, "Requirements for Internet Gateways," by R. Braden and J. Postel of the Information Sciences Institute (ISI), dated June 1987, calls itself in its first section "an official specification for the Internet community," and its introduction says: "The Internet system presently supports a variety of government and government-sponsored operational and research activities." Its section 1.3 names the networks of what it calls the global-interconnect system. The list begins with the words "The global-interconnect system includes the ARPANET," it continues with the backbone of the NSFNET, and it ends with the words "the various NSF regional and consortium networks, other ARPA sponsored networks such as the SATNET and the WBNET, and the DCA sponsored MILNET." The section continues: "It is anticipated that additional networks sponsored by these and other agencies (such as NASA and DOE) will join the global-interconnect system." In June 1987, therefore, the ARPANET was one of several networks, each sponsored by an agency of the government of the United States, that gateways interconnected. Under D3 that interconnection is internetworking among gated networks, and under D11 the word for the system that it makes is written in lowercase. RFC 1009, June 1987, section 1.3 · Governing Definitions, D3 and D11.

2.7 The property that defines the Internet under D1 was announced in the month in which the memo was published, by three operators of commercial networks. The release headed "General Atomics, Performance Systems International and UUNET Technologies, Inc. Establish the First Commercial Internet Exchange (CIX)" is datelined "San Francisco, CA - March 25, 1991," and it says: "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." The release says: "The CIX will allow firms connected to one network, such as CERFnet, to communicate with firms connected to AlterNet or PSINet without traversing the government restricted backbones, such as the NSFNET (National Science Foundation Network)." The release says that the interconnection "is expected to be operational within 60 days." F52 of the Governing Definitions seats the release, and D1 and D9 date the birth of the Internet, with a capital I, from the agreement that it announces: an exchange of traffic among competing commercial networks, at no additional cost to their customers and with no policy that screened the purpose of the traffic, made so that the traffic need not cross the government restricted backbones. The release, which this page read in full, does not name the ARPANET. Release of March 25, 1991 on the Commercial Internet Exchange · Governing Definitions, D1, D9 and F52.

2.8 Under D1.7, the ARPANET and the NSFNET belong to the history of internetworking and not to the lineage of the Internet. D1.1 states the test: a network stands in the lineage of the Internet only if it carried the trait that defines the Internet, which D1 names as open admission, and the ARPANET never carried it. D1.8 states the result in plain words: "The ARPANET is not the grandfather, the ancestor, the parent, or the precursor of the Internet." On marknichols.com the ARPANET is named an earlier gated network that also performed internetworking, and an intranet under D2. Governing Definitions, D1, D1.1, D1.7, D1.8 and D2.

2.9 This section records a definitional disagreement under D1, D1.7 and D2, and it does not count sentence 42 among the false-as-written verdicts. Sentence 42 is a metaphor that states no act that a dated document can confirm or refute, and it names no date and no document. The documents of 2.4 through 2.7 establish what the ARPANET was and where the trait that defines the Internet came from, and under the definitions of this site the descent that the metaphor asserts did not occur. Read as a statement that the ARPANET was an earlier network on which internetworking was practiced, the sentence agrees with RFC 1009 of June 1987.

2.10 Corrected statement: The ARPANET was the packet switched network of the Advanced Research Projects Agency of the United States Department of Defense, an intranet whose users were admitted by the authorization of its owner, and one of the sponsored networks that RFC 1009 of June 1987 lists in its global-interconnect system. The ARPANET was decommissioned in June 1990, as sentence 43 of the memo records. The Internet, with a capital I, the publicly joinable network of networks of the registry lineage, was born in 1991, when General Atomics, Performance Systems International, Inc. and UUNET Technologies, Inc. announced on March 25, 1991 the agreement by which the customers of CERFnet, PSINet and AlterNet exchange traffic directly, and the ARPANET is not the grandfather, the ancestor, the parent or the precursor of that network.

3.0 Sentence 219 says that "To be on the Internet you must have IP connectivity," and it gives as the sign of that connectivity the ability to "Telnet to--or ping--other systems," which is a definitional disagreement under D1, D2, D6 and D11 as to the condition, because under D1 the Internet is defined by open admission and under D6 the optional protocol Internet Protocol (IP) is a utility that a network elects, and which is a scope overstatement as to the sign, because a session of the optional protocol Telnet or a reply to a ping establishes one exchange between two systems at one time.

3.1 The entry for the Internet stands on printed pages 8 and 9 of the memo and has four sentences. Sentence 217 says, after the label of the entry and a note on the capital letter: "The largest internet in the world consisting of large national backbone nets (such as MILNET, NSFNET, and CREN) and a myriad of regional and local campus networks all over the world." Sentence 218 says: "The Internet uses the Internet protocol suite." Sentence 219 says: "To be on the Internet you must have IP connectivity, i.e., be able to Telnet to--or ping--other systems." Sentence 220 says: "Networks with only e-mail connectivity are not actually classified as being on the Internet."

3.2 Mark Nichols disputes sentence 219 in two respects. The sentence makes connectivity under one protocol the condition of being on the Internet, when under D1 the condition is open admission and the protocol is an election of the networks that use it, which is a definitional disagreement under D1, D2, D6 and D11. The sentence also states that connectivity by a sign, the ability to reach other systems with Telnet or with ping, and the sign establishes less than the condition claims, which is a scope overstatement.

3.3 Under D1, a person joins the Internet by purchasing access from any of competing commercial providers, and a network joins it by obtaining addresses and an autonomous system number from the numbering registry and then interconnecting by agreement with any willing network. Under D2, a gated network that adopts the optional protocols Transmission Control Protocol and Internet Protocol (TCP/IP) has changed its plumbing and not its admission policy. D11 states the rule of usage in these words: "at the level of Internet membership there are no required protocols, only elected ones." The question that sentence 219 answers, whether one system can exchange the datagrams of IP with another system, is a question about a protocol, and the question that D1 asks, who may join and on what terms, is a question about admission. A host on a gated research network could pass the test of sentence 219 on any day on which the network used IP, and its success would show that the host could reach another host and would not show that a member of the public could join the network. Governing Definitions, D1, D2, D6 and D11.

3.4 Two documents of the memo's own time describe the Internet as a system of more than one suite of protocols. RFC 1160 of May 1990, "The Internet Activities Board," says: "The IAB focuses on the TCP/IP protocol suite, and extensions to the Internet system to support multiple protocol suites." RFC 1160 sets this aim: "The Internet should be positioned to support the use of OSI protocols by the end of 1990 or sooner, if possible." OSI is Open Systems Interconnection, which sentence 316 of the memo calls "An international standardization program to facilitate communications among computers from different manufacturers." The release of March 25, 1991 on the Commercial Internet Exchange says that its three firms "provide nearly 100% of the commercial TCP/IP - OSI internetworking services in the United States," and it says that UUNET Technologies, Inc. "provides a range of communications services including high speed TCP/IP or OSI based internetworking." Ten months before the glossary and in the month of the glossary, therefore, the memo of May 1990 on the board that the glossary describes and the release of the commercial networks from whose agreement D1 dates the Internet each named a second suite of protocols beside TCP/IP. The memo's own entries name the counterparts in that second suite: sentence 98 says that "CLNP is the OSI equivalent to Internet IP," where CLNP is the optional protocol that sentence 96 expands as Connectionless Network Protocol, and sentence 445 says: "TP4 is the OSI equivalent to TCP." F33 of the Governing Definitions records the converse case from RFC 2026 of October 1996, whose section 1.1 states that many isolated interconnected networks use the Internet Standards without being connected to the global Internet, so that the use of the protocols does not place a network on the Internet. RFC 1160, May 1990 · Release of March 25, 1991 on the Commercial Internet Exchange · Governing Definitions, F33 and F52.

3.5 The sign that sentence 219 names establishes one exchange. Sentence 337 of the memo defines ping as "A program used to test reachability of destinations by sending them an ICMP echo request and waiting for a reply." ICMP is the optional protocol Internet Control Message Protocol, and sentence 439 says that Telnet "Allows users of one host to log into a remote host and interact as normal terminal users of that host." A reply to a ping shows that one destination answered one request at one time, and a login by Telnet shows that one host admitted one user. The registry of the month after the memo did not give Telnet its highest grade: RFC 1200 of April 1991 lists the Telnet Protocol at the status "Recommended," which it defines in the words: "A system should implement the recommended protocols." A system that conforms to the registry therefore need not offer Telnet, and a failed attempt with Telnet may show no more than a host that does not offer that service. A failed ping does not show the absence of connectivity. The memo itself records the filtering of traffic at sentence 72: "Bridges can usually be made to filter packets, that is, to forward only certain traffic." RFC 1812, "Requirements for IP Version 4 Routers," edited by F. Baker of Cisco Systems and dated June 1995, says at its section 4.3.3.6: "A router SHOULD have a configuration option that, if enabled, causes the router to silently ignore all ICMP echo requests; if provided, this option MUST default to allowing responses." Its section 5.3.9 says: "As a means of providing security and/or limiting traffic through portions of a network a router SHOULD provide the ability to selectively forward (or filter) packets." RFC 1812 is dated four years after the memo, and this page cites it for the capabilities that it documents in June 1995 and not for the practice of March 1991. A system can therefore hold connectivity under IP and fail the test, and a system can pass the test from inside a gated network, so the sign does not establish the condition, and the condition does not establish admission. RFC 1200, April 1991, section 6.2 · RFC 1812, June 1995, section 4.3.3.6 · section 5.3.9.

3.6 Sentence 220 sets apart the networks that have only electronic mail connectivity. Sentence 256 of the memo defines a mail gateway as "A machine that connects two or more electronic mail systems (especially dissimilar mail systems on two different networks) and transfers messages between them." A message that arrives through a mail gateway therefore establishes the delivery of mail by an application, and it establishes neither a path of IP between the two ends nor the admission of the public to either network. The delivery of mail, the reach of IP and admission are three facts, and each is established by its own evidence.

3.7 This section records a definitional disagreement under D1, D2, D6 and D11 and a scope overstatement, and it does not count sentence 219 among the false-as-written verdicts. Read as a statement of the criterion by which the two authors classed a system as on the Internet that they describe in March 1991, the sentence states the usage of its authors. This site applies a different criterion to the same name, and each usage is attributed to its source.

3.8 Corrected statement: In March 1991, the glossary of Ole J. Jacobsen and Daniel C. Lynch classed a system as on the Internet that it describes if the system had connectivity under the optional protocol Internet Protocol (IP), and it gave as the sign of that connectivity the ability to reach other systems with Telnet or with ping. A session of Telnet or a reply to a ping establishes one exchange with one system at one time, and a failed ping establishes nothing by itself. On marknichols.com, the Internet, with a capital I, is the publicly joinable network of networks of the registry lineage, a network is on it by open admission and by interconnection by agreement, and the protocols that its networks use are elected by those networks.

4.0 Sentence 51 defines an Autonomous System as a collection of gateways that "cooperate using a common Interior Gateway Protocol (IGP)," which is false as written as a definition, because RFC 1163 of June 1990, the specification of the optional protocol Border Gateway Protocol (BGP), names that description the "classic definition" and records that "it has become common for a single AS to use several interior gateway protocols."

4.1 The entry for Autonomous System stands on printed page 3 of the memo and has two sentences. Sentence 51 says: "Autonomous System: Internet (TCP/IP) terminology for a collection of gateways (routers) that fall under one administrative entity and cooperate using a common Interior Gateway Protocol (IGP)." Sentence 52 says: "See subnetwork." Sentence 208, in the entry for the Interior Gateway Protocol (IGP), calls such a protocol "The protocol used to exchange routing information between collaborating routers in the Internet."

4.2 Mark Nichols disputes the words "cooperate using a common Interior Gateway Protocol (IGP)." An interior gateway protocol is an optional protocol by which the routers of one administration exchange routing information among themselves. The sentence makes one common interior gateway protocol a part of the definition of an autonomous system, and a specification of the same series, dated nine months before the memo, records autonomous systems that use several. This is a documentary contradiction, decided by the specification of June 1990. The disagreement does not hold that an autonomous system cannot use one interior gateway protocol, and it holds that one common interior gateway protocol is not a condition of being an autonomous system.

4.3 The description that sentence 51 gives has a dated source in the series. RFC 1009 of June 1987, "Requirements for Internet Gateways," says at its section 1.1.3 that the gateways of the Internet system are grouped into collections called autonomous systems, and that the gateways of a single autonomous system are expected to "Be under the control of a single operations and maintenance (O&M) organization" and to "Employ common routing protocols among themselves, to maintain their routing data-bases dynamically." The section adds: "the particular choice of routing protocol within a single AS is generically called an interior gateway protocol or IGP." In June 1987, therefore, the specification of the gateways stated an expectation of common routing protocols, in the plural, among the gateways of one autonomous system. RFC 1009, June 1987, section 1.1.3.

4.4 RFC 1163, "A Border Gateway Protocol (BGP)," by Kirk Lougheed of cisco Systems, Inc. and Yakov Rekhter of the T.J. Watson Research Center of IBM Corporation, is dated June 1990, and its first section says that the memo and its companion "define a Proposed Standard for an inter-autonomous system routing protocol for the Internet." Its section 2 says: "The classic definition of an Autonomous System is a set of routers under a single technical administration, using an interior gateway protocol and common metrics to route packets within the AS, and using an exterior gateway protocol to route packets to other ASs." The next sentence of the section says: "Since this classic definition was developed, it has become common for a single AS to use several interior gateway protocols and sometimes several sets of metrics within an AS." The section then states what makes such a system one autonomous system: "The use of the term Autonomous System here stresses the fact that, even when multiple IGPs and metrics are used, the administration of an AS appears to other ASs to have a single coherent interior routing plan and presents a consistent picture of what networks are reachable through it." In June 1990, nine months before the memo, the specification of the routing protocol between autonomous systems recorded that a single autonomous system commonly used several interior gateway protocols, and it placed the identity of an autonomous system in the routing plan that the system presents to other autonomous systems. RFC 1105 of June 1989, the earlier memo on the Border Gateway Protocol that RFC 1163 obsoletes, was searched in full for the passage on the classic definition, and the search found no such passage. RFC 1163, June 1990, section 2.

4.5 RFC 1930, "Guidelines for creation, selection, and registration of an Autonomous System (AS)," by John Hawkinson of BBN Planet and Tony Bates of MCI, dated March 1996 and published as Best Current Practice 6, says at its section 3: "The definition of AS has been unclear and ambiguous for some time." RFC 1930 quotes the passage on the classic definition, and it restates the term: "An AS is a connected group of one or more IP prefixes run by one or more network operators which has a SINGLE and CLEARLY DEFINED routing policy." The same section says: "In routing terms, an AS will normally use one or more interior gateway protocols (IGPs) when exchanging reachability information within its own AS." RFC 1930 is dated five years after the memo, and this page cites it for the definition that the series reached and not for the practice of March 1991. The document that decides this section is RFC 1163 of June 1990. RFC 1930, March 1996, section 3.

4.6 The words "cooperate using a common Interior Gateway Protocol (IGP)" in sentence 51 of RFC 1208 of March 1991 are false as written under F56 as a definition of an autonomous system, because RFC 1163 of June 1990 records that it had become common for a single autonomous system to use several interior gateway protocols, so that the sentence excludes from the term systems that the specification of June 1990 calls autonomous systems. The sentence restates the description that RFC 1163 names the classic definition and that RFC 1009 of June 1987 states as an expectation, and the specification of June 1990 had recorded, nine months before the memo, that the classic definition no longer described common practice. Governing Definitions, F56.

4.7 Corrected statement: In the routing of the Internet, an autonomous system is a set of routers under a single technical administration that presents to other autonomous systems a single coherent interior routing plan and a consistent picture of the networks that are reachable through it, as RFC 1163 of June 1990 states. An autonomous system may use one interior gateway protocol or several, and one common interior gateway protocol is not a condition of the term.

5.0 Sentences 226 and 227 and sentences 434 through 437 describe the optional protocols Internet Protocol (IP) and Transmission Control Protocol (TCP) by their places in the Internet protocol suite, which the specifications of September 1981 support as descriptions of the two protocols, and which this page answers under D6 with the component at which each protocol does its work, because a place in a suite of protocols is not the network that carries the traffic.

5.1 The entry for IP stands on printed page 9 of the memo. Sentence 226 says: "IP: Internet Protocol." Sentence 227 says: "The network layer protocol for the Internet protocol suite." The entry for TCP stands on printed page 16. Sentence 434 says: "TCP: Transmission Control Protocol." Sentence 435 says: "The major transport protocol in the Internet suite of protocols providing reliable, connection-oriented, full-duplex streams." Sentence 436 says: "Uses IP for delivery." Sentence 437 says: "See TP4."

5.2 Mark Nichols does not dispute the place that the two entries give to each protocol within the suite. The two entries name a layer and a service, and neither entry says that a protocol is the network, that every internetwork must use the protocol, or that the design of the protocol created the network that carries its traffic, so a reading that attributes those claims to these entries misquotes the memo. The words "Internet (TCP/IP) terminology" at sentence 51 name the vocabulary from which the term Autonomous System comes, and they do not say that every flow of traffic uses TCP. This section records, under D6, the functions that the two short entries leave out, so that the credit for the operation of a network is assigned to the component that performs each function.

5.3 RFC 791, the specification of the Internet Protocol of September 1981, with Jon Postel as editor, says at its section 1.4: "The internet protocol implements two basic functions: addressing and fragmentation." The same section places the protocol in two kinds of machine: "The model of operation is that an internet module resides in each host engaged in internet communication and in each gateway that interconnects networks." Its section 2.4 says: "Gateways implement internet protocol to forward datagrams between networks." Its section 1.3 names what carries the datagram from one machine to the next: "This protocol calls on local network protocols to carry the internet datagram to the next gateway or destination host." The Internet Protocol is therefore processed in the hosts and in the gateways, and the carriage between them is the work of the networks. RFC 791, September 1981, sections 1.3, 1.4 and 2.4.

5.4 RFC 793, the specification of the Transmission Control Protocol of September 1981, describes TCP as "a highly reliable host-to-host protocol between hosts in packet-switched computer communication networks," and it says: "The TCP interfaces on one side to user or application processes and on the other side to a lower level protocol such as Internet Protocol." Sentence 436 of the memo agrees with RFC 793, which says: "The lower level protocol which is assumed throughout this document is the Internet Protocol." RFC 793 also states the wider principle: "In principle, the TCP should be able to operate above a wide spectrum of communication systems ranging from hard-wired connections to packet-switched or circuit-switched networks." RFC 793 says that the TCP recovers from data that is damaged, lost, duplicated or delivered out of order "by assigning a sequence number to each octet transmitted, and requiring a positive acknowledgment (ACK) from the receiving TCP." RFC 791 says of the gateways at its section 2.4: "In a gateway the higher level protocols need not be implemented." TCP therefore does its work in the two hosts at the ends of a connection, where it supplies the sequencing, the acknowledgments, the retransmission and the control of flow, and a gateway forwards the datagrams of IP without implementing TCP. A router that holds a connection of TCP for its own use, as a router that speaks the Border Gateway Protocol does under RFC 1163, is an end of that connection. The word transport at sentence 435 names a service between the two ends, and it does not mean that TCP provisions a path or switches the traffic of a carrier. F27.9 of the Governing Definitions records the usage of marknichols.com, under which anything above layer 3 is an application, TCP at layer 4 included, and only layers 1 through 3 are the network, and that usage states the relation of TCP to the network that carries its traffic and does not rename the layers that the memo and RFC 793 name. F27.10 records that the retransmission of TCP acts only when a packet fails to arrive, so that the repair presupposes a network that is already carrying traffic. RFC 793, September 1981 · Governing Definitions, F27.9 and F27.10.

5.5 The suite that the two entries name holds more than two protocols. RFC 1122, "Requirements for Internet Hosts -- Communication Layers," and RFC 1123, "Requirements for Internet Hosts -- Application and Support," are each headed with the name of the Internet Engineering Task Force, each edited by R. Braden and each dated October 1989. RFC 1122 says at its section 1.1.3: "There are two primary transport layer protocols at present," which it names as the Transmission Control Protocol and the optional protocol User Datagram Protocol (UDP). The same section opens with the condition under which the memo applies: "To communicate using the Internet system, a host must implement the layered set of protocols comprising the Internet protocol suite." The condition is stated for a host that elects to communicate using the Internet system, which is the election that D6.12 of the Governing Definitions records. A place in the suite does not make a protocol a part of every communication, of every switch of a carrier or of every internetwork, and the disagreement of this site concerns compulsory use and the credit for creation, and not the grouping of the protocols into a suite. RFC 1122, October 1989 · RFC 1123, October 1989 · Governing Definitions, D6.12.

5.6 The registry of the Internet's own standards grades the two protocols differently. RFC 1200 of April 1991, "IAB OFFICIAL PROTOCOL STANDARDS," issued by the Internet Activities Board with J. Postel as editor in the month after the memo, lists TCP at the status "Recommended," and RFC 2200 of June 1997, "INTERNET OFFICIAL PROTOCOL STANDARDS," issued by the Internet Architecture Board with J. Postel as editor, lists TCP at the status "Rec," and each of the two defines that status in the words: "A system should implement the recommended protocols." Each of the two lists IP at the status "Required," printed "Req" in RFC 2200, a grade that binds only systems electing to implement the standard suite, as D6.12 states. Sentence 435 calls TCP "The major transport protocol" of the suite, and the registry of April 1991 did not give TCP the grade that it gave to IP. The grade does not deny the usefulness of TCP in a system that deploys it. Under D6, the two protocols are optional protocols, methods of communication that a system selects, and the design of a protocol, its grade in a registry, the requirement of an operator and the opening of an operating service each have their own scope. RFC 1200, April 1991, section 6.2 · RFC 2200, June 1997, section 6.2 · Governing Definitions, D6.

5.7 The carriage is supplied by provisioned links, switches and adaptation services. RFC 2684, "Multiprotocol Encapsulation over ATM Adaptation Layer 5," by D. Grossman of Motorola, Inc. and J. Heinanen of Telia, dated September 1999, says: "Asynchronous Transfer Mode (ATM) wide area, campus and local area networks are used to transport IP datagrams and other connectionless traffic between hosts, routers, bridges and other networking devices." A fabric of Asynchronous Transfer Mode switches can therefore switch the cells that hold the traffic of IP through the fabric, and the switches of that fabric forward cells and do not forward the datagrams of IP. The deployed service is supplied by the operator's facilities, configuration and interconnections. Admission, capacity, redundancy, availability and guarantees of service are recorded in the operating records and the service records of the operator, and no protocol specification supplies them. RFC 2684, September 1999.

5.8 This section records no disagreement with the two entries and counts neither entry among the false-as-written verdicts. Read as descriptions of two protocols within a suite that a system elects, sentence 227 agrees with RFC 791 of September 1981, and sentence 435 and sentence 436 agree with RFC 793 of September 1981. The implementation of TCP or of IP does not by itself provision a path, secure admission to a network or put an operating service into operation, and the network and the component that perform each function are named before credit for the operation of a network is assigned.

5.9 Statement in full: The optional protocol Internet Protocol (IP) is the network layer protocol of the Internet protocol suite, it is processed in the hosts and in the gateways, and it calls on the networks to carry its datagrams from one machine to the next. The optional protocol Transmission Control Protocol (TCP) is a host-to-host protocol of the same suite that supplies a reliable, connection-oriented, full-duplex stream between two hosts, and a gateway forwards the datagrams of IP without implementing TCP. The registry of April 1991 lists TCP at the status "Recommended" and IP at the status "Required," a grade that binds only systems electing to implement the standard suite, and neither protocol is the network that carries the traffic.

6.0 RFC 1208, "A Glossary of Networking Terms," of March 1991 states six things correctly that this page checked, and the documents that support each one are named here.

6.1 Sentence 2 and sentence 3 say: "This memo provides information for the Internet community." "It does not specify an Internet standard." The statement is supported. RFC 1200 of April 1991 says of RFC 1208: "This is an information document and does not specify any level of standard." The record of the RFC Editor, read on November 16, 2026, gives the status of the memo as "INFORMATIONAL."

6.2 Sentence 216 says: "internet: A collection of networks interconnected by a set of routers which allow them to function as a single, large virtual network." The entry defines the lowercase word by interconnection alone and names no protocol, which agrees with the lowercase usage that D11 of the Governing Definitions states. The entry does not establish that no network of March 1991 obliged its members to use a named protocol, and this page draws no such conclusion from it.

6.3 Sentences 195 through 197 describe the Internet Activities Board (IAB). Sentence 196 calls the board "The technical body that oversees the development of the Internet suite of protocols," and sentence 197 says: "It has two task forces (the IRTF and the IETF) each charged with investigating a particular area." The description is supported. RFC 1160 of May 1990 says that "The IAB has two principal subsidiary task forces," and it names them as the Internet Engineering Task Force (IETF) and the Internet Research Task Force (IRTF). RFC 1160 gives the board a wider office than the memo states: "The Internet Activities Board (IAB) is the coordinating committee for Internet design, engineering and management." The entry establishes the oversight of protocols by the board in March 1991, and it does not establish that the board created, financed, built, owned or operated the networks that used those protocols.

6.4 Sentence 377 and sentence 378 describe the Request for Comments. Sentence 377 dates the series to 1969, and sentence 378 says: "Not all (in fact very few) RFCs describe Internet standards, but all Internet standards are written up as RFCs." Both statements are supported. RFC 1 is dated 7 April 1969, and RFC 1200 of April 1991 says: "All standards are published as RFCs, but not all RFCs specify standards."

6.5 Sentence 227 gives the Internet Protocol its place in the suite, and sentence 435 and sentence 436 give the Transmission Control Protocol its place and name the protocol that it uses for delivery. The three statements are supported by RFC 791 and RFC 793 of September 1981, as section 5.0 records.

6.6 Sentence 40 calls the Advanced Research Projects Agency "the U.S. government agency that funded the ARPANET." The statement is supported. The ARPANET Directory of December 1978 says on its printed page 6 that the network originated "under a research and development program sponsored by DARPA."

6.7 A glossary is evidence of the terms that its authors used on its date, and under D12 a statement of history within it is a retrospective account. RFC 1208 documents the usage of Ole J. Jacobsen and Daniel C. Lynch in March 1991. Its informational status does not make every entry of the glossary wrong, and it does not turn the descriptions of the glossary into obligations of every network. The usefulness of a protocol, conformance to a protocol, the construction of a network, interconnection, public admission and operation are separate achievements, each is credited on its own dated documents, and neither the design of a protocol nor the adoption of a protocol by an operator takes the place of those documents. Governing Definitions, D12.

6.8 Section 6.0 credits sentence 2 and sentence 3, sentence 216, sentences 195 through 197, sentence 377 and sentence 378, sentence 227, sentence 435 and sentence 436 (as section 5.0 records), and sentence 40 as supported.

7.0 Two sentences of RFC 1208 of March 1991 are false as written, two further findings record two definitional disagreements and a scope overstatement, and the memo is not carried on marknichols.com as an authority on the date of the ARPANET, on the lineage of the Internet, on the condition of being on the Internet or on the definition of an autonomous system.

7.1 The following two sentences of the memo are false as written under F56. Each is decided by the dated documents named in the section cited.

  1. Sentence 41 says that the ARPANET was "A packet switched network developed in the early 1970s." It is false as written as to the date, because the completion report that Bolt Beranek and Newman Inc. prepared on January 4, 1978 records that the first four Interface Message Processors were developed and installed by the end of 1969, and the ARPANET Directory of December 1978 dates the origin of the network to late 1969, as section 1.0 records.
  2. Sentence 51 defines an Autonomous System as a collection of gateways that "cooperate using a common Interior Gateway Protocol (IGP)." It is false as written as a definition, because RFC 1163 of June 1990 records that it had become common for a single autonomous system to use several interior gateway protocols, as section 4.0 records.

7.2 Two further findings record disagreements that are not counted among the false-as-written verdicts.

  1. Sentence 42 calls the ARPANET the "grandfather" of today's Internet and names no document for the descent, while the ARPANET Directory of December 1978 admits subscribers only by the authorization of the Defense Communications Agency and the release of March 25, 1991 on the Commercial Internet Exchange announces the direct exchange of traffic among the customers of three commercial networks, which is a definitional disagreement under D1, D1.7 and D2, as section 2.0 records.
  2. Sentence 219 makes connectivity under the optional protocol Internet Protocol (IP) the condition of being on the Internet and gives the ability to reach other systems with Telnet or with ping as its sign, which is a definitional disagreement under D1, D2, D6 and D11 as to the condition and a scope overstatement as to the sign, as section 3.0 records.

7.3 Under D12, contemporaneous primary documents control over retrospective accounts, and this page has decided each disagreement by the following documents.

  1. RFC 4, "Network Timetable," by Elmer B. Shapiro of Stanford Research Institute, is dated 24 March 1969, and RFC 1, "Host Software," by Steve Crocker of the University of California at Los Angeles, is dated 7 April 1969.
  2. The completion report of the ARPANET, prepared by F. Heart, A. McKenzie, J. McQuillan and D. Walden of Bolt Beranek and Newman Inc., is dated January 4, 1978, and BBN Report 4799, which holds it, is dated April 1981.
  3. The ARPANET Directory, numbered NIC 46099, prepared for the Defense Communications Agency and published by the Network Information Center of SRI International, is dated December 1978.
  4. RFC 791, the specification of the Internet Protocol, and RFC 793, the specification of the Transmission Control Protocol, are dated September 1981.
  5. RFC 1009, "Requirements for Internet Gateways," by R. Braden and J. Postel, is dated June 1987, and RFC 1122 and RFC 1123, each edited by R. Braden, are dated October 1989.
  6. RFC 1160, "The Internet Activities Board," by Vinton G. Cerf, is dated May 1990, and RFC 1163, "A Border Gateway Protocol (BGP)," by Kirk Lougheed and Yakov Rekhter, is dated June 1990.
  7. The release of General Atomics, Performance Systems International, Inc. and UUNET Technologies, Inc. on the Commercial Internet Exchange is dated March 25, 1991.
  8. RFC 1200, "IAB OFFICIAL PROTOCOL STANDARDS," with J. Postel as editor, is dated April 1991, and RFC 1251, "Who's Who in the Internet," by Gary Scott Malkin, is dated August 1991.
  9. RFC 1812, edited by F. Baker, is dated June 1995, RFC 1930, by John Hawkinson and Tony Bates, is dated March 1996, RFC 2200, with J. Postel as editor, is dated June 1997, and RFC 2684, by D. Grossman and J. Heinanen, is dated September 1999.

The page also uses the page "ARPANET" of SRI International and the record of the RFC Editor for RFC 1208, each as the statement of its custodian and each for the words that this page quotes from it. The memo is a glossary of two named authors that in its own words does not specify an Internet standard, that has no list of references, and whose statement of the period in which the ARPANET was developed is answered by the report of the company that built the packet switches of the network and by the directory of the agency that operated it, so the memo is not an authority on the date of the ARPANET, on the lineage of the Internet, on the condition of being on the Internet or on the definition of an autonomous system. No sentence of it is carried on marknichols.com as controlling. Governing Definitions, D12.

7.4 The findings on this page are open to challenge on the terms stated at F40 of The Governing Definitions and Controlling Facts of Telecommunications Internetworking. A challenger who holds that a finding on this page is wrong states the competing claim in one sentence, names the document that carries it and the document's date, and submits both as F40 directs. A challenge submitted with its document is answered on this page, and a challenge submitted without a document is an opinion and is heard as one.

8.0 This section holds Exhibit A, the numbered text of Request for Comments (RFC) 1208, "A Glossary of Networking Terms," of March 1991.

8.1 Exhibit A reproduces the text of RFC 1208 sentence by sentence, under the memo's own headings, so that every sentence number cited on this page can be read in place.

The exhibit prints the heading of the memo, with a vertical bar between its lines, and the title of the memo without numbers, and it prints the 470 sentence units of the sections "Status of this Memo," "Introduction," "Glossary," "For More Information" and "Security Considerations" with the numbers that 0.3 describes.

The exhibit omits the foot of each of the 18 printed pages and the running head of each printed page after the first, and it joins each sentence that the memo prints on more than one line into one line. Four words that the memo divides with a hyphen at the end of a printed line are joined at the hyphen, at sentence 95, sentence 435, sentence 449 and sentence 460.

The exhibit prints the lines of the closing section "Authors' Addresses" without numbers and with a vertical bar between the lines of each address, including the two lines that the memo prints twice under the name of Daniel C. Lynch. The exhibit omits from that section the telephone number and the two electronic mail addresses that the memo prints, because the only personal electronic mail address that appears on marknichols.com is the address of Mark Nichols.

The exhibit prints every sentence as the memo prints it, including the example of a mailing list address at sentence 255.

The text is quoted from RFC 1208, whose sentence 4 says: "Distribution of this memo is unlimited." RFC Editor, RFC 1208.

Exhibit A: Request for Comments (RFC) 1208, A Glossary of Networking Terms, March 1991

Network Working Group | Request for Comments: 1208 | O. Jacobsen | D. Lynch | Interop, Inc. | March 1991

A Glossary of Networking Terms

Status of this Memo

1. This RFC is a glossary adapted from "The INTEROP Pocket Glossary of Networking Terms" distributed at Interop '90.

2. This memo provides information for the Internet community.

3. It does not specify an Internet standard.

4. Distribution of this memo is unlimited.

Introduction

5. This glossary is adapted from "The INTEROP Pocket Glossary of Networking Terms" produced to help you understand the many terms--and in particular the myriad of acronyms--that can be encountered at the INTEROP Tutorials, Conference, and Exhibition.

6. To keep this document reasonably small we have deliberately omitted common computer and communications terms such as disk, modem, byte, and VLSI.

7. In addition, the definitions have been kept brief.

8. We recommend that you consult the glossaries found in the major computer networking textbooks for more comprehensive definitions.

9. We also realize that producing this glossary is akin to shooting at a moving target.

10. The computer and communications industries are moving very rapidly, and terms and acronyms are born every day.

11. You are invited to submit words which you think should be included in future editions.

Glossary

12. abstract syntax: A description of a data structure that is independent of machine-oriented structures and encodings.

13. ACSE: Association Control Service Element.

14. The method used in OSI for establishing a call between two applications.

15. Checks the identities and contexts of the application entities, and could apply an authentication security check.

16. address mask: A bit mask used to select bits from an Internet address for subnet addressing.

17. The mask is 32 bits long and selects the network portion of the Internet address and one or more bits of the local portion.

18. Sometimes called subnet mask.

19. address resolution: A means for mapping Network Layer addresses onto media-specific addresses.

20. See ARP.

21. ADMD: Administration Management Domain.

22. An X.400 Message Handling System public service carrier.

23. Examples: MCImail and ATTmail in the U.S., British Telecom Gold400mail in the U.K.

24. The ADMDs in all countries worldwide together provide the X.400 backbone.

25. See PRMD.

26. agent: In the client-server model, the part of the system that performs information preparation and exchange on behalf of a client or server application.

27. See NMS, DUA, MTA.

28. ANSI: American National Standards Institute.

29. The U.S. standardization body.

30. ANSI is a member of the International Organization for Standardization (ISO)

31. AOW: Asia and Oceania Workshop.

32. One of the three regional OSI Implementors Workshops, equivalent to OIW and EWOS.

33. API: Application Program Interface.

34. A set of calling conventions defining how a service is invoked through a software package.

35. Application Layer: The top-most layer in the OSI Reference Model providing such communication services as electronic mail and file transfer.

36. ARP: Address Resolution Protocol.

37. The Internet protocol used to dynamically map Internet addresses to physical (hardware) addresses on local area networks.

38. Limited to networks that support hardware broadcast.

39. ARPA: Advanced Research Projects Agency.

40. Now called DARPA, the U.S. government agency that funded the ARPANET.

41. ARPANET: A packet switched network developed in the early 1970s.

42. The "grandfather" of today's Internet.

43. ARPANET was decommissioned in June 1990.

44. ASN.1: Abstract Syntax Notation One.

45. The OSI language for describing abstract syntax.

46. See BER.

47. attribute: The form of information items provided by the X.500 Directory Service.

48. The directory information base consists of entries, each containing one or more attributes.

49. Each attribute consists of a type identifier together with one or more values.

50. Each directory Read operation can retrieve some or all attributes from a designated entry.

51. Autonomous System: Internet (TCP/IP) terminology for a collection of gateways (routers) that fall under one administrative entity and cooperate using a common Interior Gateway Protocol (IGP).

52. See subnetwork.

53. backbone: The primary connectivity mechanism of a hierarchical distributed system.

54. All systems which have connectivity to an intermediate system on the backbone are assured of connectivity to each other.

55. This does not prevent systems from setting up private arrangements with each other to bypass the backbone for reasons of cost, performance, or security.

56. Bart Simpson (R): Internet and OSI cult hero.

57. baseband: Characteristic of any network technology that uses a single carrier frequency and requires all stations attached to the network to participate in every transmission.

58. See broadband.

59. BER: Basic Encoding Rules.

60. Standard rules for encoding data units described in ASN.1.

61. Sometimes incorrectly lumped under the term ASN.1, which properly refers only to the abstract syntax description language, not the encoding technique.

62. big-endian: A format for storage or transmission of binary data in which the most significant bit (or byte) comes first.

63. The reverse convention is called little-endian.

64. BITNET: Because It's Time NETwork.

65. An academic computer network based originally on IBM mainframe systems interconnected via leased 9600 bps lines.

66. BITNET has recently merged with CSNET, The Computer+Science Network (another academic computer network) to form CREN: The Corporation for Research and Educational Networking.

67. See CSNET.

68. BOC: Bell Operating Company.

69. More commonly referred to as RBOC for Regional Bell Operating Company.

70. The local telephone company in each of the seven U.S. regions.

71. bridge: A device that connects two or more physical networks and forwards packets between them.

72. Bridges can usually be made to filter packets, that is, to forward only certain traffic.

73. Related devices are: repeaters which simply forward electrical signals from one cable to another, and full-fledged routers which make routing decisions based on several criteria.

74. In OSI terminology, a bridge is a Data Link Layer intermediate system.

75. See repeater and router.

76. broadband: Characteristic of any network that multiplexes multiple, independent network carriers onto a single cable.

77. This is usually done using frequency division multiplexing.

78. Broadband technology allows several networks to coexist on one single cable; traffic from one network does not interfere with traffic from another since the "conversations" happen on different frequencies in the "ether," rather like the commercial radio system.

79. broadcast: A packet delivery system where a copy of a given packet is given to all hosts attached to the network.

80. Example: Ethernet.

81. BSD: Berkeley Software Distribution.

82. Term used when describing different versions of the Berkeley UNIX software, as in "4.3BSD UNIX."

83. catenet: A network in which hosts are connected to networks with varying characteristics, and the networks are interconnected by gateways (routers).

84. The Internet is an example of a catenet.

85. See IONL.

86. CCITT: International Consultative Committee for Telegraphy and Telephony.

87. A unit of the International Telecommunications Union (ITU) of the United Nations.

88. An organization with representatives from the PTTs of the world.

89. CCITT produces technical standards, known as "Recommendations," for all internationally controlled aspects of analog and digital communications.

90. See X Recommendations.

91. CCR: Commitment, Concurrency, and Recovery.

92. An OSI application service element used to create atomic operations across distributed systems.

93. Used primarily to implement two-phase commit for transactions and nonstop operations.

94. client-server model: A common way to describenetwork services and the model user processes (programs) of those services.

95. Examples include the name-server/name-resolver paradigm of the DNS and file-server/file-client relationships such as NFS and diskless hosts.

96. CLNP: Connectionless Network Protocol.

97. The OSI protocol for providing the OSI Connectionless Network Service (datagram service).

98. CLNP is the OSI equivalent to Internet IP, and is sometimes called ISO IP.

99. CLTP: Connectionless Transport Protocol.

100. Provides for end-to-end Transport data addressing (via Transport selector) and error control (via checksum), but cannot guarantee delivery or provide flow control.

101. The OSI equivalent of UDP.

102. CMIP: Common Management Information Protocol.

103. The OSI network management protocol.

104. CMOT: CMIP Over TCP.

105. An effort to use the OSI network management protocol to manage TCP/IP networks.

106. connectionless: The model of interconnection in which communication takes place without first establishing a connection.

107. Sometimes (imprecisely) called datagram.

108. Examples: LANs, Internet IP and OSI CLNP, UDP, ordinary postcards.

109. connection-oriented: The model of interconnection in which communication proceeds through three well-defined phases: connection establishment, data transfer, connection release.

110. Examples: X.25, Internet TCP and OSI TP4, ordinary telephone calls.

111. core gateway: Historically, one of a set of gateways (routers) operated by the Internet Network Operations Center at BBN.

112. The core gateway system forms a central part of Internet routing in that all groups must advertise paths to their networks from a core gateway, using the Exterior Gateway Protocol (EGP).

113. See EGP, backbone.

114. COS: Corporation for Open Systems.

115. A vendor and user group for conformance testing, certification, and promotion of OSI products.

116. COSINE: Cooperation for Open Systems Interconnection Networking in Europe.

117. A program sponsored by the European Commission, aimed at using OSI to tie together European research networks.

118. CREN: See BITNET and CSNET.

119. CSMA/CD: Carrier Sense Multiple Access with Collision Detection.

120. The access method used by local area networking technologies such as Ethernet.

121. CSNET: Computer+Science Network.

122. A large computer network, mostly in the U.S. but with international connections.

123. CSNET sites include universities, research labs, and some commercial companies.

124. Now merged with BITNET to form CREN.

125. See BITNET.

126. DARPA: Defense Advanced Research Projects Agency.

127. The U.S. government agency that funded the ARPANET.

128. Data Link Layer: The OSI layer that is responsible for data transfer across a single physical connection, or series of bridged connections, between two Network entities.

129. DCA: Defense Communications Agency.

130. The government agency responsible for the Defense Data Network (DDN).

131. DCE: Distributed Computing Environment.

132. An architecture of standard programming interfaces, conventions, and server functionalities (e.g., naming, distributed file system, remote procedure call) for distributing applications transparently across networks of heterogeneous computers.

133. Promoted and controlled by the Open Software Foundation (OSF), a consortium led by HP, DEC, and IBM.

134. See ONC.

135. DDN: Defense Data Network.

136. Comprises the MILNET and several other DoD networks.

137. DECnet: Digital Equipment Corporation's proprietary network architecture.

138. DNS: Domain Name System.

139. The distributed name/address mechanism used in the Internet.

140. domain: In the Internet, a part of a naming hierarchy.

141. Syntactically, an Internet domain name consists of a sequence of names (labels) separated by periods (dots), e.g., "tundra.mpk.ca.us."

142. In OSI, "domain" is generally used as an administrative partition of a complex distributed system, as in MHS Private Management Domain (PRMD), and Directory Management Domain (DMD).

143. dotted decimal notation: The syntactic representation for a 32-bit integer that consists of four 8-bit numbers written in base 10 with periods (dots) separating them.

144. Used to represent IP addresses in the Internet as in: 192.67.67.20.

145. DSA: Directory System Agent.

146. The software that provides the X.500 Directory Service for a portion of the directory information base.

147. Generally, each DSA is responsible for the directory information for a single organization or organizational unit.

148. DUA: Directory User Agent.

149. The software that accesses the X.500 Directory Service on behalf of the directory user.

150. The directory user may be a person or another software element.

151. EARN: European Academic Research Network.

152. A network using BITNET technology connecting universities and research labs in Europe.

153. EGP: Exterior Gateway Protocol.

154. A reachability routing protocol used by gateways in a two-level internet.

155. EGP is used in the Internet core system.

156. See core gateway.

157. encapsulation: The technique used by layered protocols in which a layer adds header information to the protocol data unit (PDU) from the layer above.

158. As an example, in Internet terminology, a packet would contain a header from the physical layer, followed by a header from the network layer (IP), followed by a header from the transport layer (TCP), followed by the application protocol data.

159. end system: An OSI system which contains application processes capable of communicating through all seven layers of OSI protocols.

160. Equivalent to Internet host.

161. entity: OSI terminology for a layer protocol machine.

162. An entity within a layer performs the functions of the layer within a single computer system, accessing the layer entity below and providing services to the layer entity above at local service access points.

163. ES-IS: End system to Intermediate system protocol.

164. The OSI protocol by which end systems announce themselves to intermediate systems.

165. EUnet: European UNIX Network.

166. EUUG: European UNIX Users Group.

167. EWOS: European Workshop for Open Systems.

168. The OSI Implementors Workshop for Europe.

169. See OIW.

170. FARNET: Federation of American Research NETworks.

171. FDDI: Fiber Distributed Data Interface.

172. An emerging high-speed networking standard.

173. The underlying medium is fiber optics, and the topology is a dual-attached, counter-rotating Token Ring.

174. FDDI networks can often be spotted by the orange fiber "cable."

175. FIPS: Federal Information Processing Standard.

176. flame: To express strong opinion and/or criticism of something, usually as a frank inflammatory statement in an electronic message.

177. FNC: Federal Networking Council.

178. The body responsible for coordinating networking needs among U.S. Federal agencies.

179. fragmentation: The process in which an IP datagram is broken into smaller pieces to fit the requirements of a given physical network.

180. The reverse process is termed reassembly.

181. See MTU.

182. FRICC: Federal Research Internet Coordinating Committee.

183. Now replaced by the FNC.

184. FTAM: File Transfer, Access, and Management.

185. The OSI remote file service and protocol.

186. FTP: File Transfer Protocol.

187. The Internet protocol (and program) used to transfer files between hosts.

188. See FTAM.

189. gateway: The original Internet term for what is now called router or more precisely, IP router.

190. In modern usage, the terms "gateway" and "application gateway" refer to systems which do translation from some native format to another.

191. Examples include X.400 to/from RFC 822 electronic mail gateways.

192. See router.

193. GOSIP: Government OSI Profile.

194. A U.S. Government procurement specification for OSI protocols.

195. IAB: Internet Activities Board.

196. The technical body that oversees the development of the Internet suite of protocols (commonly referred to as "TCP/IP").

197. It has two task forces (the IRTF and the IETF) each charged with investigating a particular area.

198. ICMP: Internet Control Message Protocol.

199. The protocol used to handle errors and control messages at the IP layer.

200. ICMP is actually part of the IP protocol.

201. IESG: Internet Engineering Steering Group.

202. The executive committee of the IETF.

203. IETF: Internet Engineering Task Force.

204. One of the task forces of the IAB.

205. The IETF is responsible for solving short-term engineering needs of the Internet.

206. It has over 40 Working Groups.

207. IGP: Interior Gateway Protocol.

208. The protocol used to exchange routing information between collaborating routers in the Internet.

209. RIP and OSPF are examples of IGPs.

210. IGRP: Internet Gateway Routing Protocol.

211. A proprietary IGP used by cisco System's routers.

212. INTAP: Interoperability Technology Association for Information Processing.

213. The technical organization which has the official charter to develop Japanese OSI profiles and conformance tests.

214. intermediate system: An OSI system which is not an end system, but which serves instead to relay communications between end systems.

215. See repeater, bridge, and router.

216. internet: A collection of networks interconnected by a set of routers which allow them to function as a single, large virtual network.

217. Internet: (note the capital "I") The largest internet in the world consisting of large national backbone nets (such as MILNET, NSFNET, and CREN) and a myriad of regional and local campus networks all over the world.

218. The Internet uses the Internet protocol suite.

219. To be on the Internet you must have IP connectivity, i.e., be able to Telnet to--or ping--other systems.

220. Networks with only e-mail connectivity are not actually classified as being on the Internet.

221. Internet address: A 32-bit address assigned to hosts using TCP/IP.

222. See dotted decimal notation.

223. IONL: Internal Organization of the Network Layer.

224. The OSI standard for the detailed architecture of the Network Layer.

225. Basically, it partitions the Network layer into subnetworks interconnected by convergence protocols (equivalent to internetworking protocols), creating what Internet calls a catenet or internet.

226. IP: Internet Protocol.

227. The network layer protocol for the Internet protocol suite.

228. IP datagram: The fundamental unit of information passed across the Internet.

229. Contains source and destination addresses along with data and a number of fields which define such things as the length of the datagram, the header checksum, and flags to say whether the datagram can be (or has been) fragmented.

230. IRTF: Internet Research Task Force.

231. One of the task forces of the IAB.

232. The group responsible for research and development of the Internet protocol suite.

233. ISDN: Integrated Services Digital Network.

234. An emerging technology which is beginning to be offered by the telephone carriers of the world.

235. ISDN combines voice and digital network services in a single medium making it possible to offer customers digital data services as well as voice connections through a single "wire."

236. The standards that define ISDN are specified by CCITT.

237. IS-IS: Intermediate system to Intermediate system protocol.

238. The OSI protocol by which intermediate systems exchange routing information.

239. ISO: International Organization for Standardization.

240. You knew that, right?

241. Best known for the 7-layer OSI Reference Model.

242. See OSI.

243. ISODE: ISO Development Environment.

244. A popular implementation of the upper layers of OSI.

245. Pronounced eye-so-dee-eee.

246. JANET: Joint Academic Network.

247. A university network in the U.K.

248. JUNET: Japan UNIX Network.

249. KA9Q: A popular implementation of TCP/IP and associated protocols for amateur packet radio systems.

250. Kermit: A popular file transfer and terminal emulation program.

251. little-endian: A format for storage or transmission of binary data in which the least significant byte (bit) comes first.

252. See big-endian.

253. mail exploder: Part of an electronic mail delivery system which allows a message to be delivered to a list of addressees.

254. Mail exploders are used to implement mailing lists.

255. Users send messages to a single address (e.g., hacks@somehost.edu) and the mail exploder takes care of delivery to the individual mailboxes in the list.

256. mail gateway: A machine that connects two or more electronic mail systems (especially dissimilar mail systems on two different networks) and transfers messages between them.

257. Sometimes the mapping and translation can be quite complex, and generally it requires a store-and-forward scheme whereby the message is received from one system completely before it is transmitted to the next system after suitable translations.

258. Martian: Humorous term applied to packets that turn up unexpectedly on the wrong network because of bogus routing entries.

259. Also used as a name for a packet which has an altogether bogus (non-registered or ill-formed) Internet address.

260. MHS: Message Handling System.

261. The system of message user agents, message transfer agents, message stores, and access units which together provide OSI electronic mail.

262. MHS is specified in the CCITT X.400 series of Recommendations.

263. MIB: Management Information Base.

264. A collection of objects that can be accessed via a network management protocol.

265. See SMI.

266. MILNET: MILitary NETwork.

267. Originally part of the ARPANET, MILNET was partitioned in 1984 to make it possible for military installations to have reliable network service, while the ARPANET continued to be used for research.

268. See DDN.

269. MTA: Message Transfer Agent.

270. An OSI application process used to store and forward messages in the X.400 Message Handling System.

271. Equivalent to Internet mail agent.

272. MTU: Maximum Transmission Unit.

273. The largest possible unit of data that can be sent on a given physical medium.

274. Example: The MTU of Ethernet is 1500 bytes.

275. See fragmentation.

276. multicast: A special form of broadcast where copies of the packet are delivered to only a subset of all possible destinations.

277. See broadcast.

278. multi-homed host: A computer connected to more than one physical data link.

279. The data links may or may not be attached to the same network.

280. name resolution: The process of mapping a name into the corresponding address.

281. See DNS.

282. NetBIOS: Network Basic Input Output System.

283. The standard interface to networks on IBM PC and compatible systems.

284. Network Address: See Internet address or OSI Network Address.

285. Network Layer: The OSI layer that is responsible for routing, switching, and subnetwork access across the entire OSI environment.

286. NFS(R): Network File System.

287. A distributed file system developed by Sun Microsystems which allows a set of computers to cooperatively access each other's files in a transparent manner.

288. NIC: Network Information Center.

289. Originally there was only one, located at SRI International and tasked to serve the ARPANET (and later DDN) community.

290. Today, there are many NICs, operated by local, regional, and national networks all over the world.

291. Such centers provide user assistance, document service, training, and much more.

292. NIST: National Institute of Standards and Technology.

293. (Formerly NBS).

294. See OIW.

295. NMS: Network Management Station.

296. The system responsible for managing a (portion of a) network.

297. The NMS talks to network management agents, which reside in the managed nodes, via a network management protocol.

298. See agent.

299. NOC: Network Operations Center.

300. Any center tasked with the operational aspects of a production network.

301. These tasks include monitoring and control, trouble-shooting, user assistance, and so on.

302. NSAP: Network Service Access Point.

303. The point at which the OSI Network Service is made available to a Transport entity.

304. The NSAPs are identified by OSI Network Addresses.

305. NSF: National Science Foundation.

306. Sponsors of the NSFNET.

307. NSFNET: National Science Foundation NETwork.

308. A collection of local, regional, and mid-level networks in the U.S. tied together by a high-speed backbone.

309. NSFNET provides scientists access to a number of supercomputers across the country.

310. OIW: Workshop for Implementors of OSI.

311. Frequently called NIST OIW or the NIST Workshop, this is the North American regional forum at which OSI implementation agreements are decided.

312. It is equivalent to EWOS in Europe and AOW in the Pacific.

313. ONC(tm): Open Network Computing.

314. A distributed applications architecture promoted and controlled by a consortium led by Sun Microsystems.

315. OSI: Open Systems Interconnection.

316. An international standardization program to facilitate communications among computers from different manufacturers.

317. See ISO.

318. OSI Network Address: The address, consisting of up to 20 octets, used to locate an OSI Transport entity.

319. The address is formatted into an Initial Domain Part which is standardized for each of several addressing domains, and a Domain Specific Part which is the responsibility of the addressing authority for that domain.

320. OSI Presentation Address: The address used to locate an OSI Application entity.

321. It consists of an OSI Network Address and up to three selectors, one each for use by the Transport, Session, and Presentation entities.

322. OSPF: Open Shortest Path First.

323. A "Proposed Standard" IGP for the Internet.

324. See IGP.

325. PCI: Protocol Control Information.

326. The protocol information added by an OSI entity to the service data unit passed down from the layer above, all together forming a Protocol Data Unit (PDU).

327. PDU: Protocol Data Unit.

328. This is OSI terminology for "packet."

329. A PDU is a data object exchanged by protocol machines (entities) within a given layer.

330. PDUs consist of both Protocol Control Information (PCI) and user data.

331. Physical Layer: The OSI layer that provides the means to activate and use physical connections for bit transmission.

332. In plain terms, the Physical Layer provides the procedures for transferring a single bit across a Physical Media.

333. Physical Media: Any means in the physical world for transferring signals between OSI systems.

334. Considered to be outside the OSI Model, and therefore sometimes referred to as "Layer 0."

335. The physical connector to the media can be considered as defining the bottom interface of the Physical Layer, i.e., the bottom of the OSI Reference Model.

336. ping: Packet internet groper.

337. A program used to test reachability of destinations by sending them an ICMP echo request and waiting for a reply.

338. The term is used as a verb: "Ping host X to see if it is up!"

339. port: The abstraction used by Internet transport protocols to distinguish among multiple simultaneous connections to a single destination host.

340. See selector.

341. POSI: Promoting Conference for OSI.

342. The OSI "800-pound gorilla" in Japan.

343. Consists of executives from the six major Japanese computer manufacturers and Nippon Telephone and Telegraph.

344. They set policies and commit resources to promote OSI.

345. PPP: Point-to-Point Protocol.

346. The successor to SLIP, PPP provides router-to-router and host-to-network connections over both synchronous and asynchronous circuits.

347. See SLIP.

348. Presentation Address: See OSI Presentation Address.

349. Presentation Layer: The OSI layer that determines how Application information is represented (i.e., encoded) while in transit between two end systems.

350. PRMD: Private Management Domain.

351. An X.400 Message Handling System private organization mail system.

352. Example: NASAmail.

353. See ADMD.

354. protocol: A formal description of messages to be exchanged and rules to be followed for two or more systems to exchange information.

355. proxy: The mechanism whereby one system "fronts for" another system in responding to protocol requests.

356. Proxy systems are used in network management to avoid having to implement full protocol stacks in simple devices, such as modems.

357. proxy ARP: The technique in which one machine, usually a router, answers ARP requests intended for another machine.

358. By "faking" its identity, the router accepts responsibility for routing packets to the "real" destination.

359. Proxy ARP allows a site to use a single IP address with two physical networks.

360. Subnetting would normally be a better solution.

361. PSN: Packet Switch Node.

362. The modern term used for nodes in the ARPANET and MILNET.

363. These used to be called IMPs (Interface Message Processors).

364. PSNs are currently implemented with BBN C30 or C300 minicomputers.

365. RARE: Reseaux Associes pour la Recherche Europeenne.

366. European association of research networks.

367. RARP: Reverse Address Resolution Protocol.

368. The Internet protocol a diskless host uses to find its Internet address at startup.

369. RARP maps a physical (hardware) address to an Internet address.

370. See ARP.

371. RBOC: Regional Bell Operating Company.

372. See BOC.

373. repeater: A device which propagates electrical signals from one cable to another without making routing decisions or providing packet filtering.

374. In OSI terminology, a repeater is a Physical Layer intermediate system.

375. See bridge and router.

376. RFC: Request For Comments.

377. The document series, begun in 1969, which describes the Internet suite of protocols and related experiments.

378. Not all (in fact very few) RFCs describe Internet standards, but all Internet standards are written up as RFCs.

379. RFS: Remote File System.

380. A distributed file system, similar to NFS, developed by AT&T and distributed with their UNIX System V operating system.

381. See NFS.

382. RIP: Routing Information Protocol.

383. An Interior Gateway Protocol (IGP) supplied with Berkeley UNIX.

384. RIPE: Reseaux IP Europeenne.

385. European continental TCP/IP network operated by EUnet.

386. See EUnet.

387. rlogin: A service offered by Berkeley UNIX which allows users of one machine to log into other UNIX systems (for which they are authorized) and interact as if their terminals were connected directly.

388. Similar to Telnet.

389. ROSE: Remote Operations Service Element.

390. A lightweight RPC protocol, used in OSI Message Handling, Directory, and Network Management application protocols.

391. router: A system responsible for making decisions about which of several paths network (or Internet) traffic will follow.

392. To do this it uses a routing protocol to gain information about the network, and algorithms to choose the best route based on several criteria known as "routing metrics."

393. In OSI terminology, a router is a Network Layer intermediate system.

394. See gateway, bridge and repeater.

395. RPC: Remote Procedure Call.

396. An easy and popular paradigm for implementing the client-server model of distributed computing.

397. A request is sent to a remote system to execute a designated procedure, using arguments supplied, and the result returned to the caller.

398. There are many variations and subtleties, resulting in a variety of different RPC protocols.

399. RTSE: Reliable Transfer Service Element.

400. A lightweight OSI application service used above X.25 networks to handshake application PDUs across the Session Service and TP0.

401. Not needed with TP4, and not recommended for use in the U.S. except when talking to X.400 ADMDs.

402. SAP: Service Access Point.

403. The point at which the services of an OSI layer are made available to the next higher layer.

404. The SAP is named according to the layer providing the services: e.g., Transport services are provided at a Transport SAP (TSAP) at the top of the Transport Layer.

405. selector: The identifier used by an OSI entity to distinguish among multiple SAPs at which it provides services to the layer above.

406. See port.

407. Session Layer: The OSI layer that provides means for dialogue control between end systems.

408. SGMP: Simple Gateway Management Protocol.

409. The predecessor to SNMP.

410. See SNMP.

411. SLIP: Serial Line IP.

412. An Internet protocol used to run IP over serial lines such as telephone circuits or RS-232 cables interconnecting two systems.

413. SLIP is now being replaced by PPP.

414. See PPP.

415. SMDS: Switched Multimegabit Data Service.

416. An emerging high-speed networking technology to be offered by the telephone companies in the U.S.

417. SMI: Structure of Management Information.

418. The rules used to define the objects that can be accessed via a network management protocol.

419. See MIB.

420. SMTP: Simple Mail Transfer Protocol.

421. The Internet electronic mail protocol.

422. Defined in RFC 821, with associated message format descriptions in RFC 822.

423. SNA: Systems Network Architecture.

424. IBM's proprietary network architecture.

425. SNMP: Simple Network Management Protocol.

426. The network management protocol of choice for TCP/IP-based internets.

427. SPAG: Standards Promotion and Application Group.

428. A group of European OSI manufacturers which chooses option subsets and publishes these in a "Guide to the Use of Standards" (GUS).

429. SQL: Structured Query Language.

430. The international standard language for defining and accessing relational databases.

431. subnet mask: See address mask.

432. subnetwork: A collection of OSI end systems and intermediate systems under the control of a single administrative domain and utilizing a single network access protocol.

433. Examples: private X.25 networks, collection of bridged LANs.

434. TCP: Transmission Control Protocol.

435. The major transport protocol in the Internet suite of protocols providing reliable, connection-oriented, full-duplex streams.

436. Uses IP for delivery.

437. See TP4.

438. Telnet: The virtual terminal protocol in the Internet suite of protocols.

439. Allows users of one host to log into a remote host and interact as normal terminal users of that host.

440. three-way-handshake: The process whereby two protocol entities synchronize during connection establishment.

441. TP0: OSI Transport Protocol Class 0 (Simple Class).

442. This is the simplest OSI Transport Protocol, useful only on top of an X.25 network (or other network that does not lose or damage data).

443. TP4: OSI Transport Protocol Class 4 (Error Detection and Recovery Class).

444. This is the most powerful OSI Transport Protocol, useful on top of any type of network.

445. TP4 is the OSI equivalent to TCP.

446. transceiver: Transmitter-receiver.

447. The physical device that connects a host interface to a local area network, such as Ethernet.

448. Ethernet transceivers contain electronics that apply signals to the cable and sense collisions.

449. Transport Layer: The OSI layer that is responsible for reliable end-to-end data transfer between end systems.

450. UA: User Agent.

451. An OSI application process that represents a human user or organization in the X.400 Message Handling System.

452. Creates, submits, and takes delivery of messages on the user's behalf.

453. UDP: User Datagram Protocol.

454. A transport protocol in the Internet suite of protocols.

455. UDP, like TCP, uses IP for delivery; however, unlike TCP, UDP provides for exchange of datagrams without acknowledgements or guaranteed delivery.

456. See CLTP.

457. UUCP: UNIX to UNIX Copy Program.

458. A protocol used for communication between consenting UNIX systems.

459. XDR: eXternal Data Representation.

460. A standard for machine-independent data structures developed by Sun Microsystems.

461. Similar to ASN.1.

462. X/Open: A group of computer manufacturers that promotes the development of portable applications based on UNIX.

463. They publish a document called the X/Open Portability Guide.

464. X Recommendations: The CCITT documents that describe data communication network standards.

465. Well-known ones include: X.25 Packet Switching standard, X.400 Message Handling System, and X.500 Directory Services.

466. The X Window System (TM): A popular window system developed by MIT and implemented on a number of workstations.

For More Information

467. As indicated in the introduction, this is only a partial list of words from the world of interoperability.

468. Yes, you're right, we didn't list "interoperability" because the jury is still out on exactly what it means, and we invite you to suggest a definition.

469. To learn more about these topics, consult the books, standards documents, bibliographies, periodicals, mailing lists, etc. listed in "Information Sources" in the December 1989 issue of ConneXions--The Interoperability Report.

Security Considerations

470. Security issues are not discussed in this memo.

Authors' Addresses

Ole J. Jacobsen | Interop, Inc. | 480 San Antonio Road | Suite 100 | Mountain View, CA 94040

Daniel C. Lynch | Interop, Inc. | 480 San Antonio Road | Interop, Inc. | 480 San Antonio Road | Suite 100 | Mountain View, CA 94040

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.

D11.1 Definitions govern meaning. Documents govern facts. Findings govern conclusions.

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.