Wikipedia Defines the History of the Internet: Disagreements | Network, Not Protocol

On October 22, 2026, Mark Nichols assembled eight disagreements with Wikipedia’s History of the Internet, revision 1370792739.

Preamble: I created this page to examine how Wikipedia describes the interconnection of research networks, the protocols those networks used, and the opening of commercial network access. Each disagreement identifies the passage and the dated evidence used to assess it. Section 0.3 defines the terms used here, and the findings apply those definitions to the evidence where they matter. The numbered Wikipedia source text in §11.1 supplies this page’s sentence locators. The demonstration diagram appears at the bottom as Plate 11.2. Wikipedia revision 1370792739 · The Governing Definitions and Controlling Facts of Telecommunications Internetworking.

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.

Diagram of the three-network demonstration of November 22, 1977 as reproduced in the Wikipedia article History of the Internet, showing the San Francisco Bay Area Packet Radio Net with the SRI van at Menlo Park, California, the ARPANET with Bolt Beranek and Newman at Cambridge, Massachusetts, and the Atlantic Packet Satellite Net through the Etam, West Virginia and Goonhilly Downs, England earth stations and INTELSAT IV-A, with internetwork gateways at SRI, University College London and the Norwegian Defense Research Establishment at Kjeller, Norway, and the path of packets ending at the University of Southern California Information Sciences Institute in Marina del Rey, California
November 22, 1977 demonstration of internetworking among PRNET, ARPANET, and SATNET.

0.0 This section records the revision of the Wikipedia article this page examines and the way the numbers on this page are read.

0.1 The Wikipedia article History of the Internet, page id 13692 on en.wikipedia.org, is examined on this page at its revision 1370792739, saved at 03:16 UTC on August 23, 2026 (August 22, 2026, Pacific) by the account Sickerboi, which was the current revision on October 22, 2026, at the permanent link https://en.wikipedia.org/w/index.php?title=History_of_the_Internet&oldid=1370792739, and the article’s protection record on October 22, 2026 reads edit: autoconfirmed and move: autoconfirmed with no expiry, which is Wikipedia’s semi-protection and not a lock.

0.2 Sentence locators. Each sentence number refers to the numbered Wikipedia source text in §11.1, which lists the article’s body sentences in the order they appear in revision 1370792739. Each disagreement also identifies the article section that contains its passage. The diagram cited in §1.0 appears as Plate 11.2.

0.3 Definitions used on this page. The capital-I Internet (D1) is the publicly joinable network of networks in the registry lineage from InterNIC to ARIN. People can buy access from competing providers for lawful purposes. Independent networks can obtain addresses and an autonomous system number from the registry and interconnect by agreement with a willing network. Admission requires no central owner’s permission or government sponsorship. An intranet (D2) is a network whose operator controls who may join. Internetworking (D3) connects distinct networks through gateways so traffic from a host on one network can reach a host on another. A lowercase internet (D11) is an interconnection of networks, including networks with restricted admission. The capital I in this site’s own prose identifies the publicly joinable system defined in D1. Governing Definitions, D1, D2, D3, and D11.

0.4 Kinds of disagreement. A documentary contradiction occurs when a dated record conflicts with the disputed statement as written. A scope overstatement occurs when the evidence establishes a narrower event, policy, or technical behavior than the sentence claims. A definitional disagreement occurs when the article and this site use different criteria for the same term. The findings identify which kind applies and attribute each usage to its source.

0.5 The glossaries of the standards body’s own RFC series define the capital-I Internet in part by its protocols, and this page states those definitions at 10.0, verbatim and dated, before any reader cites them against it, and 10.7 and 10.8 examine the authorship of the oldest of them and the places where the documents this record examines break them.

0.6 Scope of the protocol rules. D6 separates an operating network from the protocols its equipment and hosts implement. TCP provides transport between endpoints. IP supplies datagram addressing and is processed by hosts and by routers performing IP forwarding. HTTP, DNS, and SMTP perform application-layer functions. RFC 1200 and RFC 2200 give TCP the grade “Recommended.” They give IP the grade “Required” for systems electing to implement the listed suite, which describes conformance within that standards framework. Network operators select the technologies they deploy and may set requirements for their own systems. Links, gateways, and forwarding carry traffic in a deployment. The protocol specifications describe how participating implementations handle it. Governing Definitions, D6 · RFC 791 · RFC 793 · RFC 1200, §6.2 · RFC 2200, §6.2.

0.7 The article has no author of record, and this page applies to it the five checks it applies to every authority a page cites or disputes, under the audit standard Mark Nichols ruled on October 2, 2026 and extended on October 23, 2026: the issuing body’s membership rule is that any account Wikipedia classes as autoconfirmed may edit the article, as the protection record stated at 0.1 records; the roster on the date of the act is the single account name Sickerboi, which saved revision 1370792739 at 03:16 UTC on August 23, 2026 and which names no person, no title and no employer, so the author of the revision is unknown to this record and is stated as unknown; the instrument carries no named author and no vote, because a Wikipedia revision is saved by one account and adopted by no body; the custodian is the Wikimedia Foundation, which serves the article at en.wikipedia.org as a text that changes with every saved revision, so the article is a living text and not a dated instrument, which is why 0.1 fixes the revision this page examines by its permanent link; and the overlap between the article’s authors and the author of this page cannot be computed, because this page names its author, Mark Nichols, and the article names none, so the overlap is recorded as not computable. Under D12 of The Governing Definitions, contemporary primary-source documents control over retrospective accounts, and the article is a retrospective account with no author of record, so no sentence of the article is carried on this page as controlling, and every disagreement below is decided by the dated document the disagreement names and not by the article’s standing.

0.8 How the claims are read. This page reads each passage in its article context and identifies the precise claim the evidence addresses. If wording leaves the network, date, or comparison unclear, the proposed correction supplies that scope. The revised statements distinguish the article’s account, the dated documentary record, and the terminology this site applies. Governing Definitions, F56.

1.0 The 1977 diagram shows three research networks linked for a demonstration

1.1 See Plate 11.2 at the bottom of this page. The disputed wording. The diagram caption in the TCP/IP subsection calls the event the “First Internet demonstration” and identifies ARPANET, PRNET, SATNET, and November 22, 1977. Wikipedia revision 1370792739.

1.2 The disagreement. Mark Nichols disputes using “Internet” with a capital I for this research demonstration under this site’s public admission criterion. Internetworking (D3) connects distinct networks through gateways so traffic from a host on one network can reach a host on another. The demonstration route ran from SRI’s packet-radio van through PRNET, ARPANET, and SATNET and back through ARPANET to USC’s Information Sciences Institute. Under D3 and D11, that was internetworking across three networks. Under D2, the documented permission rules at UCL’s ARPANET node make the ARPANET portion an intranet. British users of that node needed project committee approval, and U.S. users needed ARPA permission. D1 identifies the publicly joinable network in the InterNIC-to-ARIN registry lineage. The test routed traffic among project endpoints through an access-controlled network. The evidence establishes their ability to exchange traffic. Public admission and interconnection by willing providers require their own evidence. SRI route figure, reproduced by Don Nielson · Kirstein’s February 1977 report, printed pp. 3 and 4 · Governing Definitions, D1, D2, D3, and D11.

1.3 Kind and evidence. This is a definitional disagreement about the caption’s referent. SRI’s institutional account dates the test to November 22. The February 1978 SRI figure documents the route. The later Nielson article gives November 22 in its body and November 27 in its caption, so this finding uses that figure for the route and SRI’s institutional account for the date. The UCL annual report supplies the documented admission rule on the route. SRI’s institutional account · SRI route figure and Nielson’s account · Kirstein’s February 1977 report.

1.4 Historical terminology. Cerf, Dalal, and Sunshine used the lowercase form in the text of RFC 675. The cover of RFC 791 uses the capitalized form in the name of DARPA’s research program. Jon Postel used ARPA Internet for the interconnected research system in RFC 801 in 1981. Shirey’s 2000 glossary distinguishes the generic lowercase term from the name of a particular worldwide system. These records establish different historical uses of the term. The 2000 glossary supplies a later usage distinction. The test and admission records establish what the 1977 participants demonstrated and under what access conditions. RFC 675, December 1974 · RFC 791, September 1981 · RFC 801, November 1981 · RFC 2828, May 2000.

1.5 Corrected caption. November 22, 1977 demonstration of internetworking among PRNET, ARPANET, and SATNET.

1.6 Scope of the finding. The test documents a specific three-network exchange. A priority claim requires a defined comparison, such as the first documented test of these three particular networks together. Claims about earlier internetworking elsewhere require a separate comparison. The term Internet in Wikipedia’s caption reflects its historical usage. This site applies the capitalized term under D1’s public admission rule.

Consequence for the Historical Record. Credit the November 1977 test with its documented three-network exchange, and assess any claim that it founded the publicly joinable Internet against D1’s admission criteria.

2.0 Sentence 200 makes a common protocol the general criterion for an internet

2.1 The disputed wording. Sentence 200 of the numbered list, in the subsection Transition towards the Internet, defines an internet in general by networks linked through a common protocol.

2.2 The disagreement. Mark Nichols disputes the use of a shared protocol as the general test for whether separate networks form an internet. Internetworking (D3) connects distinct networks through gateways so traffic from a host on one network can reach a host on another. D11 calls the resulting interconnection a lowercase internet. A shared protocol can give gateways compatible information to interpret. An operating interconnection also needs gateways, links, and forwarding that give traffic a path between networks. Two disconnected networks can run the same protocol and remain disconnected. Governing Definitions, D3 and D11.

2.3 Kind and evidence. This is a definitional disagreement about the general criterion. RFC 1208, RFC 1392, and RFC 1983 describe networks interconnected by routers. RFC 2828 defines an internetwork as a system of interconnected networks. Its short definition leaves the equipment and protocol unspecified. The four entries describe the interconnection. A particular deployment can still use a common protocol across its gateways. Jacobsen and Lynch, March 1991 · Malkin and LaQuey Parker, January 1993 · Malkin, August 1996 · Shirey, May 2000.

2.4 Corrected statement. An internet is a collection of interconnected networks. Gateways and links provide the connection, and a common protocol or a gateway mapping can specify how equipment handles traffic across it.

2.5 Application to the article’s examples. Sentences 117 and 294 identify a gateway and exchange points as actual means of interconnection. Sentence 156 describes a common protocol used to handle differences among networks. Each describes a separate part of the system. Identifying the implementation and the operating path makes the difference clear.

Consequence for the Historical Record. Establish internetworking from the working gateways, links, and forwarding between networks, and credit the common protocol or gateway mapping with the functions it supplied.

3.0 The NSFNET commercial-use restriction applied to its backbone service

3.1 The disputed wording. Sentence 25 in the lead describes the 1995 retirement of the NSFNET backbone as removing the last restrictions on commercial Internet traffic.

3.2 The disagreement. Mark Nichols disputes the Internet-wide scope of the claim. The dated policy governed the NSFNET Backbone Service. The National Science Foundation limited backbone use under its Acceptable Use Policy and expected connecting networks to set their own policies. The CIX providers announced direct exchange outside government-restricted backbones in March 1991. The October 1991 CIX-WEST traffic report records actual traffic for all three providers. Those records show commercial interconnection operating while the NSFNET restriction remained in place. NSFNET policy reproduced in RFC 1359, Appendix B · March 25, 1991 CIX announcement · Mark Fedor’s CIX-WEST traffic report, October 1991, printed pp. 14 and 15.

3.3 Kind and evidence. This is a scope overstatement. Merit’s retirement account dates the end of the NSFNET Backbone Service to April 30, 1995. The policy and retirement account establish which restriction ended with which service. Determining whether it was the final restriction across the entire Internet would require identifying the other operators and their policies. Susan R. Harris and Elise Gerich, April 1996.

3.4 Corrected statement. The NSFNET Backbone Service retired on April 30, 1995, ending the commercial-use restrictions that governed traffic on that backbone. Commercial providers had already exchanged traffic through CIX in 1991.

Consequence for the Historical Record. Date the end of the NSFNET Backbone Service’s restrictions to April 30, 1995, while preserving the separate evidence of commercial traffic exchange through CIX in 1991.

4.0 Ethernet is one technology for carrying IP datagrams

4.1 The disputed wording. Sentence 320, in the discussion of storage and data-access speeds, calls Ethernet the enabling technology for TCP/IP.

4.2 The disagreement. Mark Nichols disputes assigning Ethernet the general role of enabling TCP/IP. RFC 791 describes IP relying on the local network to carry a datagram to the next gateway or destination host. RFC 894 specifies how to encapsulate an IP datagram when that local network is Ethernet. The 1977 research test separately documents an earlier internetworking protocol implementation crossing packet radio, ARPANET, and satellite networks. The test and the later specifications address different generations of the protocol work. Jon Postel, ed., RFC 791, September 1981, §1.3 · Charles Hornig, RFC 894, April 1984 · SRI three-network demonstration account.

4.3 Kind and evidence. This is a scope overstatement. Ethernet enabled carriage where operators deployed Ethernet. The general IP specification assigns delivery across each local network to the applicable local-network protocol.

4.4 Corrected statement. Ethernet became a widely used local-network technology for carrying IP traffic. RFC 894 specified the Ethernet encapsulation in 1984.

Consequence for the Historical Record. Credit Ethernet with carrying IP traffic where Ethernet was deployed, and preserve the documented operation of internetworking protocols over other network technologies.

5.0 IP datagram discard, TCP retransmission, and bundle forwarding are separate behaviors

5.1 The disputed wording. Sentence 366, in the subsection Networking in outer space, contrasts delay-tolerant networking retransmission with dropping and attributes the latter to the “standard TCP/IP Internet Protocol.”

5.2 The disagreement. Mark Nichols disputes attributing one dropping behavior to TCP and IP as though they were a single protocol. RFC 791 specifies IP datagram handling. For example, a datagram is discarded when its time to live expires. RFC 793 specifies TCP retransmission of unacknowledged data. RFC 5050 separately specifies bundle forwarding in delay-tolerant networking. It calls for bundle deletion on expiry and permits a further forwarding attempt in specified custody-failure processing. Each behavior has its own trigger and protocol scope. RFC 791, §1.4 · RFC 793, §1.5 · RFC 5050, §5.5 · RFC 5050, §5.12.

5.3 Kind and evidence. This is a documentary contradiction when the sentence assigns discard to TCP and IP collectively and makes retransmission the contrasting behavior of delay-tolerant networking alone. Jon Postel edited the 1981 IP and TCP specifications. Keith Scott and Scott Burleigh wrote the 2007 experimental Bundle Protocol specification. Each document addresses a different function.

5.4 Corrected statement. Delay-tolerant networking can retain and forward bundles across interruptions subject to its forwarding and expiry rules. IP can discard datagrams, and TCP separately retransmits unacknowledged data under its transport rules.

Consequence for the Historical Record. Attribute IP datagram discard, TCP retransmission, and Bundle Protocol retention and forwarding to their respective specifications, triggers, and versions.

6.0 NSFNET expansion, DNS, and TCP/IP adoption address a different milestone from public commercial admission

6.1 The disputed wording. Sentence 22 in the lead dates the beginnings of the Internet by NSFNET’s international connections, the emergence of DNS, and adoption of TCP/IP on existing networks.

6.2 The disagreement. Mark Nichols disputes using those events to date the opening of the publicly joinable Internet as defined on this site. The capital-I Internet (D1) is the publicly joinable network of networks in the registry lineage from InterNIC to ARIN. People can buy access from competing providers for lawful purposes. Independent networks can obtain addresses and an autonomous system number from the registry and interconnect by agreement with a willing network. Admission requires no central owner’s permission or government sponsorship. International links show where NSFNET reached. DNS shows how systems could resolve names. TCP/IP adoption shows which protocols operators selected. The NSFNET Backbone Service still operated under the National Science Foundation’s Acceptable Use Policy, which generally limited traffic to uses supporting research and education, with stated exceptions. Under D7, that operating policy distinguishes the restricted research backbone from the public commercial interconnection. Governing Definitions, D1 and D7 · NSFNET policy, RFC 1359, Appendix B.

6.3 Kind and evidence. This is a definitional disagreement about which milestone counts as the beginning. Under D9, this site dates public commercial interconnection to the 1991 CIX agreement among PSINet, UUNET’s AlterNet, and CERFnet. The March 25 announcement records the arrangement for customers of the competing providers to exchange traffic outside government-restricted backbones. The October report documents operating traffic through CIX-WEST. Together they establish the commercial terms and operation this site uses to date the milestone. Governing Definitions, D9 and A3 · March 25, 1991 CIX announcement · October 1991 CIX-WEST traffic report.

6.4 Attribution. Wikipedia dates a research and deployment lineage through international links, DNS, and TCP/IP. This site dates the D1 public-admission milestone by a documented commercial interconnection. Attribute each account to its source and identify the event each dates.

6.5 Corrected statement. NSFNET’s international connections, DNS deployment, and TCP/IP adoption were milestones in the growth of research and technical interconnection. This site dates the public commercial interconnection it defines as the capital-I Internet to CIX in 1991.

Consequence for the Historical Record. Credit international expansion, DNS deployment, and TCP/IP adoption as technical and deployment milestones, and date D1’s public-commercial interconnection from the separate admission and operating records.

7.0 ARPANET’s research role and the public Internet’s opening are separate historical claims

7.1 The disputed wording. Sentence 120 in the ARPANET subsection calls ARPANET the technical core of what would become the Internet and credits it as a tool for developing the technologies used.

7.2 The disagreement. Mark Nichols disputes treating ARPANET’s technical role as the operating core of the publicly joinable Internet defined here. Under D2 and D4, ARPANET was a restricted research intranet. The December 1978 directory identifies who could subscribe, when sponsorship was required, and how foreign organizations could obtain coordinated access. In June 1987, RFC 1009 lists ARPANET as one constituent of a larger interconnect alongside the NSFNET backbone and other networks. These documents establish ARPANET’s technical role and its admission limits. Under D1, people can buy service from competing providers, and independent networks in the registry lineage can interconnect by agreement with a willing network without central-owner permission or government sponsorship. ARPANET’s subscription rules followed a different admission model. ARPANET Directory, December 1978, printed p. 11 · Braden and Postel, RFC 1009, June 1987, §1.3 · Governing Definitions, D1, D2, and D4.

7.3 Kind and evidence. This is a definitional disagreement about the historical referent and the meaning of technical core. The article’s sentences 193 and 291 date ARPANET’s retirement to 1990. The 1991 CIX records identify different operators opening direct commercial exchange. The retirement date establishes when ARPANET ceased operating. The admission and operating records establish what each system did. RFC 1208, March 1991, ARPANET entry · March 25, 1991 CIX announcement · October 1991 CIX-WEST traffic report.

7.4 Attribution. Wikipedia uses technical lineage to describe ARPANET’s role. This site calls ARPANET a research precedent and applies D1 to the public commercial network. A claim that particular technology or infrastructure carried over requires evidence identifying what carried over and where it operated.

7.5 Corrected statement. ARPANET was a restricted research network and a constituent of the interconnect documented in 1987. Its use supported network research. The opening of public commercial interconnection has a separate operating and admission record.

Consequence for the Historical Record. Credit ARPANET’s documented research role and participation in research internetworking separately from the commercial interconnection and admission events that establish the public Internet under D1.

8.0 The UCL gateway documents working interconnection before the 1978 TCP/IP split

8.1 The disputed wording. Sentence 162 in the TCP/IP subsection credits a reduced set of network functions with making exchange possible across networks of different designs and with solving the fundamental problems of internetworking.

8.2 The disagreement. Mark Nichols disputes treating that architectural approach as a prerequisite for operating an interconnection between unlike networks. Internetworking (D3) connects distinct networks through gateways so traffic from a host on one network can reach a host on another. Peter Kirstein’s February 1977 annual report records that Packet HASP became operational in the fourth quarter of 1976. UCL staff used the ARPANET terminal processor and a PDP-9 gateway to do routine work in limited daily test sessions over the ARPANET and EPSS interconnection. The report describes the gateway mapping between the two networks’ protocols. The next annual report records EPSS terminal traffic operational under UCL’s SWITCH system by mid-1977. These dates establish a working interconnection before the 1978 TCP/IP split discussed in the article. Kirstein, February 1977, §§6.1 and 6.4 · Kirstein, April 1978, §1.2.

8.3 Kind and evidence. This is a disagreement about scope. Wikipedia describes the architectural benefit of moving selected functions to hosts. The UCL records establish that a gateway could map between unlike networks and carry traffic before the later protocol split. Rutherford Laboratory’s 1975 report counts jobs submitted over ARPANET and discusses EPSS gateway programming in a separate entry. The 1975 job count therefore measures ARPANET use. The UCL reports supply the dated evidence for the ARPANET-to-EPSS operational trial and terminal service. Rutherford Laboratory annual report, 1975, §5.2.2 · February 1977 UCL report · April 1978 UCL report.

8.4 Application of the definition. The gateway satisfied D3 because traffic actually passed between distinct networks. An account of scalable interoperability across many networks calls for separate evidence about the architecture’s deployment and performance.

8.5 Corrected statement. The protocol architecture described by Wikipedia offered one way to exchange traffic across unlike networks. The UCL gateway between ARPANET and EPSS documents another approach, using protocol mapping in a working interconnection by late 1976.

Consequence for the Historical Record. Record the ARPANET-to-EPSS gateway as a working protocol-mapping interconnection by late 1976, and evaluate broader claims about scalable interoperability against the relevant deployment and performance evidence.

9.0 Sixteen further sentences of the article were examined against the documents on October 22, 2026 and are left standing on this page, and this section records which sentences and why.

9.1 Sentence 2 stands, because RFC 2828 of May 2000 itself states of the protocols of the Internet Protocol Suite that “These protocols enable a user of any one of the networks in the Internet to communicate with, or use services located on, any of the other networks.”, which is the sense in which the article’s sentence describes the suite as rules used for communication between networks and devices.

9.2 Sentence 299 stands, because it calls the World Wide Web an application on the Internet, which is what D8 of The Governing Definitions states.

9.3 Sentences 27, 43, 196, 233, 240, 259, 284, 350, 375 and 541 stand, because no dated document contradicts any of them as written, and a disagreement without a document has no place on this page.

9.4 Sentences 141, 150, 156 and 255 stand on this page as written, because each can be read consistently with D3 and D6 of The Governing Definitions, under which the protocol supplies the common header the gateways read and the gateways, links and routing perform the interconnection, and this page disputes a sentence only where no reading consistent with the record is available.

10.0 The glossaries of the standards body’s own RFC series define the capital-I Internet in part by its protocols, and this page states those definitions here, verbatim and dated, so that no reader cites them against this record as if the record had not read them, examines the authorship of the oldest of them, and counts the places where the documents this record examines break them.

10.1 RFC 1208, INTEROP Pocket Glossary, by O. Jacobsen and D. Lynch, March 1991, states under Internet: “The Internet uses the Internet protocol suite. To be on the Internet you must have IP connectivity, i.e., be able to Telnet to--or ping--other systems. Networks with only e-mail connectivity are not actually classified as being on the Internet.”

10.2 RFC 1122, Requirements for Internet Hosts, Communication Layers, R. Braden, editor, October 1989, states at section 1.1.1: “An Internet communication system consists of interconnected packet networks supporting communication among host computers using the Internet protocols. The networks are interconnected using packet-switching computers called “gateways” or “IP routers” by the Internet community, and “Intermediate Systems” by the OSI world [INTRO:13].” and at section 1.1.3: “To communicate using the Internet system, a host must implement the layered set of protocols comprising the Internet protocol suite.”

10.3 RFC 2828, Internet Security Glossary, by R. Shirey, May 2000, states under internet vs. Internet that the capitalized word names “the single, interconnected, worldwide system of commercial, government, educational, and other computer networks that share the set of protocols specified by the IAB [R2026] and the name and address spaces managed by the ICANN.”

10.4 RFC 1392 of January 1993 and RFC 1983 of August 1996, the Internet Users’ Glossary, state under Internet: “The Internet is the largest internet in the world.” and “The Internet is a multiprotocol internet.”

10.5 What the glossaries define. This site uses the capital-I Internet for the publicly joinable network of networks in the InterNIC-to-ARIN registry lineage, with admission through competing providers and voluntary network interconnection (D1). The RFC entries above use criteria that include size, suite use, or reachability. For the lowercase term, RFC 1208, RFC 1392, and RFC 1983 describe networks interconnected by routers. RFC 2828 gives the broader definition of a system of interconnected networks. The shared point is actual interconnection. A protocol used within a particular system answers a separate question about how that system communicates. Governing Definitions, D1 and D11 · RFC 1208 · RFC 1392 · RFC 1983 · RFC 2828.

10.6 The custodian of every standards document this page cites is the RFC Editor, each document carries a named author or editor and a date, and their status as the RFC Editor states it on October 23, 2026 is this: RFC 675 of December 1974, by Vinton Cerf, Yogen Dalal and Carl Sunshine, is Historic, obsoleted by RFC 7805 of April 2016 by A. Zimmermann, W. Eddy and L. Eggert; RFC 791 of September 1981, Jon Postel, editor, is Internet Standard STD 5, updated by RFC 1349, RFC 2474 and RFC 6864 and not obsoleted; RFC 793 of September 1981, Jon Postel, editor, is obsoleted by RFC 9293 of August 2022, Transmission Control Protocol (TCP), W. Eddy, editor, Internet Standard STD 7, which by its own abstract collects the changes made to TCP since RFC 793 together with the specification of RFC 793; RFC 894 of April 1984, by Charles Hornig, is Internet Standard STD 41 and not obsoleted; RFC 1122 of October 1989, R. Braden, editor, is Internet Standard STD 3, updated by RFC 1349, RFC 4379, RFC 5884, RFC 6093, RFC 6298, RFC 6633, RFC 6864, RFC 8029 and RFC 9293 and not obsoleted; RFC 1208 of March 1991, by O.J. Jacobsen and D.C. Lynch, is Informational and not obsoleted; RFC 1392 of January 1993 is obsoleted by RFC 1983 of August 1996, G. Malkin, editor, FYI 18, Informational and not obsoleted; RFC 2828 of May 2000, by R. Shirey, FYI 36, is obsoleted by RFC 4949 of August 2007, Internet Security Glossary, Version 2, by R. Shirey, FYI 36, Informational, whose entry internet, Internet carries the capital-I definition quoted at 10.3 in the same words but for “governmental” in place of “government” and the lettering of its two conditions (a) and (b), whose entry internetwork carries the definition quoted at 2.2 unchanged, whose RFC Editor Note states that the recommendations and some particular interpretations in its definitions are the author’s and not an official IETF position, and which does not carry the commentary sentence of RFC 2828 that 9.1 quotes, so that 9.1 rests on the glossary of 2000 and not on its successor of 2007; and RFC 5050 of November 2007, by K. Scott and S. Burleigh, is Experimental and not obsoleted, with RFC 9171 of January 2022, Bundle Protocol Version 7, by S. Burleigh, K. Fall and E. Birrane III, Proposed Standard, presenting the protocol adapted from it. The authors of these documents cannot be cross-read against the authors of the Wikipedia article, because the article has none of record, as 0.7 states.

10.7 RFC 1208 is examined here under the five checks of the audit standard stated at 0.7, because this page and three other pages of this record rest their reading of the lowercase internet on it. The instrument is A Glossary of Networking Terms, March 1991, headed INTEROP Pocket Glossary on every page after its first, signed by Ole J. Jacobsen and Daniel C. Lynch of Interop, Inc., 480 San Antonio Road, Mountain View, California, with Lynch’s electronic mail address printed in the domain of the Information Sciences Institute of the University of Southern California, ISI.EDU, where the RFC Editor, Jonathan Postel, sat; by its own status note it is adapted from The INTEROP Pocket Glossary of Networking Terms distributed at Interop ’90, a conference handout, and it is an Informational memo that by its own words does not specify an Internet standard, so that its definitions carry two named authors and the vote of no body. The issuing body is Interop, Inc., the company that ran the Interop trade show, and no membership rule governed the handout beyond the company’s own. The roster on the date is the two authors, and Daniel Lynch is listed as a member of the Internet Activities Board in RFC 1120 of September 1989, by Vinton Cerf, under Vinton Cerf as Chairman, David Clark as IRTF Chairman, Phillip Gross as IETF Chairman, Jonathan Postel as RFC Editor and Robert Braden as Executive Director, with Hans-Werner Braun, Barry Leiner and Stephen Kent as the other members, and again in RFC 1160 of May 1990, by Vinton Cerf, as Daniel Lynch of Interop, Inc., with Lyman Chapin, listed at DG, and Anthony Lauck of Digital added to the members, the board that RFC 1208’s own entry for IAB calls the technical body that oversees the development of the Internet suite of protocols. The custodian is the RFC Editor, maintained by the Internet Engineering Task Force, which holds RFC 1208 as Informational and not obsoleted, as 10.6 records. The overlap with the authors of the documents this record disputes is this: Daniel C. Lynch co-wrote the glossary of 1991, sat on the board of 1989 and 1990 over the protocols the glossary names as what the Internet uses, and is one of the nine authors of A Brief History of the Internet of 1997, which calls him a founder of the Interop trade show and conferences and credits him with arranging the three-day TCP/IP workshop for vendors of 1985 in cooperation with the IAB, with speakers mostly from the DARPA research community, and with the first Interop show of September 1988; and five of that history’s nine authors, Vinton G. Cerf, David D. Clark, Barry M. Leiner, Daniel C. Lynch and Jon Postel, sat on the board of 1989 and 1990. The overlap is recorded as a finding of the documents and not as motive, under the audit standard. The booklet itself was not found in any public copy on October 23, 2026, and RFC 1208 is its surviving text; Ole J. Jacobsen’s further role is not stated in the documents read and is recorded as not established.

10.8 Comparison with RFC 1208. The examples below concern three different questions. A passage may describe an operating network as a standard or protocol, use a different capitalization convention, or give a historical lineage. Classify each example by the claim the passage makes and cite the applicable glossary entry. RFC 1208 describes both the interconnection and the protocol suite used by the capital-I system it identifies. Jacobsen and Lynch, March 1991.

  • Wikipedia Internet, revision 1381320565. Sentences 197, 222, 249, and 265 address software, standards, IP operation, and IPv6. Sentences 1, 3, 71, 99, 134, 234, 235, and 253 provide capitalization examples. Sentences 17 through 20 discuss usage. The lead combines the network and its use of the suite, an approach also found in RFC 1208. This site’s D1 objection concerns the criterion used to identify the network. See §§1.1, 1.2, 1.7, and 1.8 of the companion page. Wikipedia Internet Disagreements.
  • History of the Internet, revision 1370792739. Sentence 200 makes a common protocol part of its general description. Sentences 347, 459, 460, 499, and 537 provide capitalization examples. Sentence 543 quotes an account of the global Internet developing from ARPANET. That attribution calls for historical evidence about the asserted relationship.
  • A Brief History of the Internet (1997). Sentences 46 and 59 concern the relation to ARPANET. Sentences 3, 174, and 238 describe technical functions or communities. Sentence 311 provides a capitalization example. Sentence 313 reproduces the Federal Networking Council’s 1995 definition. Internet Society disagreement page.
  • What Is the Internet (And What Makes It Work) (1999), by Robert E. Kahn and Vinton G. Cerf. Sentences 28, 164, and 199 concern the relationship of the Internet to its architecture and the Federal Networking Council’s definition. Kahn and Cerf disagreement page.

11.0 Exhibits

11.1 Numbered Wikipedia source text. The register below identifies the article’s body sentences by number in revision 1370792739. Those numbers are the sentence locators used in the findings. Wikipedia permanent revision 1370792739.

11.2 Plate. The diagram below traces the November 22, 1977 internetworking demonstration through PRNET, ARPANET, and SATNET. Traffic traveled from SRI’s packet-radio van to USC’s Information Sciences Institute. Wikipedia’s caption is the wording examined in §1.0. SRI demonstration account · SRI route figure, reproduced by Don Nielson.

Complete sequential list of body sentences from the Wikipedia page “History of the Internet”

(Excluding references, notes, captions that are purely image labels, and further-reading sections.)

History of the Internet

1. The Internet originated in the efforts of scientists and engineers to build and interconnect computer networks.
2. The Internet Protocol Suite, the set of rules used to communicate between networks and devices on the Internet, arose from research and development in the United States and involved international collaboration, particularly with researchers in the United Kingdom and France.
3. Computer science was an emerging discipline in the late 1950s that began to consider time-sharing between computer users, and later, the possibility of achieving this over wide area networks.
4. J. C. R. Licklider articulated the idea of a universal network at the Information Processing Techniques Office (IPTO) of the United States Department of Defense (DoD) Advanced Research Projects Agency (ARPA).
5. Independently, Paul Baran at the RAND Corporation proposed a distributed network based on data in message blocks in the early 1960s, and Donald Davies conceived of packet switching in 1965 at the National Physical Laboratory (NPL), proposing a national commercial data network in the United Kingdom.
6. ARPA awarded contracts in 1969 for the development of the ARPANET project, directed by Robert Taylor and managed by Lawrence Roberts.
7. ARPANET adopted the packet switching technology proposed by Davies and sought input from Baran.
8. The network of Interface Message Processors (IMPs) was built by a team at Bolt, Beranek, and Newman, with the design and specification led by Bob Kahn.
9. The host-to-host protocol was specified mainly by graduate students, led by Steve Crocker at UCLA, along with Jon Postel and others.
10. The ARPANET expanded rapidly across the United States with connections to the United Kingdom and Norway.
11. Several early packet-switched networks emerged in the 1970s which researched and provided data networking.
12. Louis Pouzin and Hubert Zimmermann pioneered a simplified end-to-end approach to internetworking at the IRIA.
13. Peter Kirstein put internetworking into practice at University College London in 1973.
14. Bob Metcalfe developed the theory and practice behind Ethernet and the PARC Universal Packet.
15. ARPA initiatives and the International Network Working Group developed and refined ideas for internetworking, in which multiple separate networks could be joined into a network of networks.
16. Vint Cerf, now at Stanford University, and Bob Kahn, now at DARPA, published their research on internetworking in 1974.
17. Through the Internet Experiment Note series and later RFCs this evolved into the Transmission Control Protocol (TCP) and Internet Protocol (IP), two protocols of the Internet protocol suite.
18. The design reflected concepts pioneered in the French CYCLADES project directed by Louis Pouzin.
19. The development of packet switching networks was complemented by mathematical work in the 1970s by Leonard Kleinrock at UCLA.
20. In the late 1970s, national and international public data networks emerged based on the X.25 protocol, designed by Rémi Després and others.
21. In the United States, the National Science Foundation (NSF) funded national supercomputing centers at several universities in the United States, and provided interconnectivity in 1986 with the NSFNET project, thus creating network access to these supercomputer sites for research and academic organizations in the United States.
22. International connections to NSFNET, the emergence of architecture such as the Domain Name System, and the adoption of TCP/IP on existing networks in the United States and around the world marked the beginnings of the Internet.
23. Commercial Internet service providers (ISPs) emerged in 1989 in the United States and Australia.
24. Limited private connections to parts of the Internet by officially commercial entities emerged in several American cities by late 1989 and 1990.
25. The optical backbone of the NSFNET was decommissioned in 1995, removing the last restrictions on the use of the Internet to carry commercial traffic, as traffic transitioned to optical networks managed by Sprint, MCI and AT&T in the United States.
26. Research at CERN in Switzerland by the British computer scientist Tim Berners-Lee in 1989–90 resulted in the World Wide Web, linking hypertext documents into an information system, accessible from any node on the network.
27. The dramatic expansion of the capacity of the Internet, enabled by the advent of wave division multiplexing (WDM) and the rollout of fiber optic cables in the mid-1990s, had a revolutionary impact on culture, commerce, and technology.
28. This made possible the rise of near-instant communication by electronic mail, instant messaging, voice over Internet Protocol (VoIP) telephone calls, video chat, and the World Wide Web with its discussion forums, blogs, social networking services, and online shopping sites.
29. Increasing amounts of data are transmitted at higher and higher speeds over fiber-optic networks operating at 1 Gbit/s, 10 Gbit/s, and 800 Gbit/s by 2019.
30. The Internet's takeover of the global communication landscape was rapid in historical terms: it only communicated 1% of the information flowing through two-way telecommunications networks in the year 1993, 51% by 2000, and more than 97% of the telecommunicated information by 2007.
31. The Internet continues to grow, driven by ever greater amounts of online information, commerce, entertainment, and social networking services.
32. However, the future of the global network may be shaped by regional differences.

Foundations

33. The practice of transmitting messages between two different places through an electromagnetic medium dates back to the electrical telegraph in the late 19th century, which was the first fully digital communication system.
34. Radiotelegraphy began to be used commercially in the early 20th century.
35. Telex became an operational teleprinter service in the 1930s.
36. Such systems were limited to point-to-point communication between two end devices.
37. Fundamental theoretical work in telecommunications technology was developed by Harry Nyquist and Ralph Hartley in the 1920s.
38. Information theory, as enunciated by Claude Shannon in 1948, provided a firm theoretical underpinning to understand the trade-offs between signal-to-noise ratio, bandwidth, and error-free transmission in the presence of noise.
39. Early fixed-program computers in the 1940s were operated manually by entering small programs via switches in order to load and run a series of programs.
40. As transistor technology evolved in the 1950s, central processing units and user terminals came into use by 1955.
41. The mainframe computer model was devised, and modems, such as the Bell 101, allowed digital data to be transmitted over regular unconditioned telephone lines at low speeds by the late 1950s.
42. These technologies made it possible to exchange data between remote computers.
43. However, a fixed-line link was still necessary; the point-to-point communication model did not allow for direct communication between any two arbitrary systems.
44. In addition, the applications were specific and not general purpose.
45. Examples included SAGE (1958) and SABRE (1960).
46. Christopher Strachey, who became Oxford University's first Professor of Computation, filed a patent application in the United Kingdom for time-sharing in February 1959.
47. In June that year, he gave a paper "Time Sharing in Large Fast Computers" at the UNESCO Information Processing Conference in Paris where he passed the concept on to J. C. R. Licklider.
48. Licklider, a vice president at Bolt Beranek and Newman, Inc. (BBN), promoted the idea of time-sharing as an alternative to batch processing.
49. John McCarthy, at MIT, wrote a memo in 1959 that broadened the concept of time sharing to encompass multiple interactive user sessions, which resulted in the Compatible Time-Sharing System (CTSS) implemented at MIT.
50. Other multi-user mainframe systems developed, such as PLATO at the University of Illinois Chicago.
51. In the early 1960, the Advanced Research Projects Agency (ARPA) of the United States Department of Defense funded further research into time-sharing at MIT through Project MAC.
52. J. C. R. Licklider, while working at BBN, proposed a computer network in his March 1960 paper Man–Computer Symbiosis.
53. A network of such centers, connected to one another by wide-band communication lines [...] the functions of present-day libraries together with anticipated advances in information storage and retrieval and symbiotic functions suggested earlier in this paper.
54. In August 1962, Licklider and Welden Clark published the paper "On-Line Man-Computer Communication" which was one of the first descriptions of a networked future.
55. In October 1962, Licklider was hired by Jack Ruina as director of the newly established Information Processing Techniques Office (IPTO) within ARPA, with a mandate to interconnect the United States Department of Defense's main computers at Cheyenne Mountain, the Pentagon, and SAC HQ.
56. There he formed an informal group within DARPA to further computer research.
57. He began by writing memos in 1963 describing a distributed network to the IPTO staff, whom he called "Members and Affiliates of the Intergalactic Computer Network".
58. Although he left the IPTO in 1964, five years before the ARPANET went live, it was his vision of universal networking that provided the impetus for one of his successors, Robert Taylor, to initiate the ARPANET development.
59. Licklider later returned to lead the IPTO in 1973 for two years.
60. The "message block", designed by Paul Baran in 1962 and refined in 1964, is the first proposal of a data packet.
61. The infrastructure for telephone systems at the time was based on circuit switching, which requires pre-allocation of a dedicated communication line for the duration of the call.
62. Telegram services had developed store and forward telecommunication techniques.
63. Western Union's Automatic Telegraph Switching System Plan 55-A was based on message switching.
64. The U.S. military's AUTODIN network became operational in 1962.
65. These systems, like SAGE and SBRE, still required rigid routing structures that were prone to single point of failure.
66. The technology was considered vulnerable for strategic and military use because there were no alternative paths for the communication in case of a broken link.
67. In the early 1960s, Paul Baran of the RAND Corporation produced a study of survivable networks for the U.S. military in the event of nuclear war.
68. Information would be transmitted across a "distributed" network, divided into what he called "message blocks".
69. Baran's design was intended for high-speed digital communication of voice messages using low-cost hardware; it was not implemented.
70. In addition to being prone to a single point of failure, existing telegraphic techniques were inefficient and inflexible.
71. Beginning in 1965 Donald Davies, at the National Physical Laboratory in the United Kingdom, independently developed a similar proposal of the concept, designed for high-speed data communication in computer networks, which he called packet switching, the term that would ultimately be adopted.
72. Packet switching is a technique for transmitting computer data by splitting it into very short, standardized chunks, attaching routing information to each of these chunks, and transmitting them independently through a computer network.
73. It provides better bandwidth utilization than traditional circuit-switching used for telephony, and enables the connection of computers with different transmission and receive rates.
74. It is a distinct concept to message switching.

Networks that led to the Internet

75. Following discussions with J. C. R. Licklider in 1965, Donald Davies became interested in data communications for computer networks.
76. Later that year, at the National Physical Laboratory (NPL) in the United Kingdom, Davies designed and proposed a national commercial data network based on packet switching.
77. The following year, he described the use of "switching nodes" to act as routers in a digital communication network.
78. The proposal was not taken up nationally but he produced a design for a local network to serve the needs of the NPL and prove the feasibility of packet switching using high-speed data transmission.
79. To deal with packet permutations (due to dynamically updated route preferences) and to datagram losses (unavoidable when fast sources send to a slow destinations), he assumed that "all users of the network will provide themselves with some kind of error control", thus inventing what came to be known as the end-to-end principle.
80. In 1967, he and his team were the first to use the term 'protocol' in a modern data-commutation context.
81. In 1968, Davies began building the Mark I packet-switched network to meet the needs of his multidisciplinary laboratory and prove the technology under operational conditions.
82. The network's development was described at a 1968 conference.
83. Elements of the network became operational in early 1969, the first implementation of packet switching, and the NPL network was the first to use high-speed links.
84. Many other packet switching networks built in the 1970s were similar "in nearly all respects" to Davies' original 1965 design.
85. The Mark II version which operated from 1973 used a layered protocol architecture.
86. In 1977, there were roughly 30 computers, 30 peripherals and 100 VDU terminals all able to interact through the NPL Network.
87. The NPL team carried out simulation work on wide-area packet networks, including datagrams and congestion; and research into internetworking and secure communications.
88. The network was replaced in 1986.
89. Robert Taylor was promoted to the head of the Information Processing Techniques Office (IPTO) at Advanced Research Projects Agency (ARPA) in 1966.
90. He intended to realize Licklider's ideas of an interconnected networking system.
91. As part of the IPTO's role, three network terminals had been installed: one for System Development Corporation in Santa Monica, one for Project Genie at University of California, Berkeley, and one for the Compatible Time-Sharing System project at Massachusetts Institute of Technology (MIT).
92. Taylor's identified need for networking became obvious from the waste of resources apparent to him.
93. For each of these three terminals, I had three different sets of user commands. So if I was talking online with someone at S.D.C. and I wanted to talk to someone I knew at Berkeley or M.I.T. about this, I had to get up from the S.D.C. terminal, go over and log into the other terminal and get in touch with them.... I said, oh man, it's obvious what to do: If you have these three terminals, there ought to be one terminal that goes anywhere you want to go where you have interactive computing. That idea is the ARPAnet.
94. Bringing in Larry Roberts from MIT in January 1967, he initiated a project to build such a network.
95. Roberts and Thomas Merrill had been researching computer time-sharing over wide area networks (WANs).
96. Wide area networks emerged during the late 1950s and became established during the 1960s.
97. At the first ACM Symposium on Operating Systems Principles in October 1967, Roberts presented a proposal for the "ARPA net", based on Wesley Clark's idea to use Interface Message Processors (IMP) to create a message switching network.
98. At the conference, Roger Scantlebury presented Donald Davies' work on a hierarchical digital communications network using packet switching and referenced the work of Paul Baran at RAND.
99. Roberts incorporated the packet switching concepts proposed by Davies into the ARPANET design.
100. He upgraded the proposed communications speed from 2.4 kbit/s to 50 kbit/s and sought input from Baran.
101. ARPA awarded the contract to build the network to Bolt Beranek & Newman.
102. The "IMP guys", led by Frank Heart and Bob Kahn, developed the routing, flow control, software design and network control.
103. The first ARPANET link was established between the Network Measurement Center at the University of California, Los Angeles (UCLA) Henry Samueli School of Engineering and Applied Science led by Leonard Kleinrock, and the NLS system at Stanford Research Institute (SRI) led by Douglas Engelbart in Menlo Park, California at 22:30 hours on October 29, 1969.
104. With reference to the actions of the graduate and undergraduate students working with the IMPs, Kleinrock said: "We set up a telephone connection between us and the guys at SRI ...", Kleinrock ... said in an interview: "We typed the L and we asked on the phone, "Do you see the L?" "Yes, we see the L," came the response. We typed the O, and we asked, "Do you see the O." "Yes, we see the O." Then we typed the G, and the system crashed ... Yet a revolution had begun".
105. In 1969, Taylor helped fund ALOHAnet, a system designed by professor Norman Abramson and others at the University of Hawaiʻi at Mānoa that transmitted data by radio between seven computers on four islands on Hawaii.
106. By December 1969, a three-node network was connected by adding an IBM 360/75 computer using the OS/MVT operating system from the Culler-Fried Interactive Mathematics Center at the University of California, Santa Barbara followed by the fourth, a DEC PDP-10 computer using the Tenex operating system the University of Utah Graphics Department.
107. Steve Crocker, a graduate student at UCLA, formed the "Network Working Group" in 1969.
108. Working with Jon Postel and others, he initiated and managed the Request for Comments (RFC) process, which is still used today for proposing and distributing contributions.
109. RFC 1, entitled "Host Software", was written by Crocker and published on April 7, 1969.
110. The protocol for establishing links between network sites in the ARPANET, the Network Control Program (NCP), was completed in 1970.
111. These early years were documented in the 1972 film Computer Networks: The Heralds of Resource Sharing.
112. Roberts presented the idea of packet switching to the communication professionals, and faced anger and hostility.
113. Before ARPANET was operating, they argued that the router buffers would quickly run out.
114. After the ARPANET was operating, they argued packet switching would never be economic without the government subsidy.
115. Baran had faced the same rejection and thus failed to convince the military into constructing a packet switching network.
116. Early international collaborations via the ARPANET were sparse.
117. Connections were made in 1973 to Norway (NORSAR), via a satellite link at the Tanum Earth Station in Sweden, and to Peter Kirstein's research group at University College London, which provided a gateway to British academic networks, the first international heterogenous resource sharing network.
118. Throughout the 1970s, Leonard Kleinrock developed the mathematical theory to model and measure the performance of packet-switching technology, building on his earlier work on the application of queueing theory to message switching systems.
119. By 1981, the number of hosts had grown to 213.
120. The ARPANET became the technical core of what would become the Internet, and a primary tool in developing the technologies used.
121. CYCLADES was a French research network designed and directed by Louis Pouzin.
122. In 1972, he began implementing his ideas to build on the work of Donald Davies and explore alternatives to the early ARPANET design.
123. His goal was to enable internetworking, which he called a "catenet".
124. This was the first network to implement the end-to-end principle by making the hosts responsible for reliable delivery of data, rather than the network itself, using unreliable datagrams.
125. Concepts implemented in this network influenced the initial proposal of the Transmission Control Program, and were reflected in the later TCP/IP architecture.
126. Based on international research initiatives, particularly the contributions of Rémi Després, packet switching network standards were developed by the CCITT, which is now the International Telegraph and Telephone Consultative Committee (ITU-T), in the form of X.25 and related standards.
127. X.25 is built on the concept of virtual circuits emulating traditional telephone connections.
128. The initial ITU Standard on X.25 was approved in March 1976.
129. Existing networks, such as Telenet in the United States adopted X.25 as well as new public data networks, such as DATAPAC in Canada and TRANSPAC in France.
130. The protocol formed the basis for the SERCnet network between British academic and research sites, which became JANET in the 1980s, the United Kingdom's high-speed national research and education network (NREN).
131. The British Post Office, Western Union International, and Tymnet collaborated to create the first international packet-switched network, referred to as the International Packet Switched Service (IPSS), in 1978.
132. This network grew from Europe and the US to cover Canada, Hong Kong, and Australia by 1981.
133. By the 1990s it provided a worldwide networking infrastructure.
134. X.25 was supplemented by the X.75 protocol which enabled internetworking between national PTT networks in Europe and commercial networks in North America.
135. Unlike the ARPANET and its protocols, X.25 was available for business use.
136. In 1979, CompuServe became the first service to offer commercial electronic mail capabilities and technical support to personal computer users.
137. The company broke new ground again in 1980 as the first to offer real-time chat with its CB Simulator.
138. Telenet offered its Telemail electronic mail service, which was also targeted to enterprise use unlike the network mail system of the ARPANET.
139. Other major dial-in networks were America Online (AOL) and Prodigy that also provided communications, content, and entertainment features.
140. Bulletin board system (BBS) networks also provided on-line access, such as FidoNet which was popular amongst hobbyist computer users, many of them hackers and amateur radio operators.
141. Many of these public data networks went on to adopt TCP/IP and formed the infrastructure of the early Internet.
142. In 1979, two students at Duke University, Tom Truscott and Jim Ellis, originated the idea of using Bourne shell scripts to transfer news and messages on a serial line UUCP connection with nearby University of North Carolina at Chapel Hill.
143. Following public release of the software in 1980, the mesh of UUCP hosts forwarding on the Usenet news rapidly expanded.
144. UUCPnet, as it would later be named, also created gateways and links between FidoNet and dial-up BBS hosts.
145. UUCP networks spread quickly due to the lower costs involved, ability to use existing leased lines, X.25 links or even ARPANET connections, and the lack of strict use policies compared to later networks like CSNET and BITNET.
146. All connects were local.
147. By 1981 the number of UUCP hosts had grown to 550, nearly doubling to 940 in 1984.
148. Sublink Network, operating since 1987 and officially founded in Italy in 1989, based its interconnectivity upon UUCP to redistribute mail and news groups messages throughout its Italian nodes (about 100 at the time) owned both by private individuals and small companies.
149. Sublink Network evolved into one of the first examples of Internet technology coming into use through popular diffusion.

1973-1989: Merging the networks and creating the Internet

150. With so many different networking methods seeking interconnection, a method was needed to unify them.
151. Louis Pouzin initiated the CYCLADES project in 1972, building on the work of Donald Davies and the ARPANET.
152. An International Network Working Group formed in 1972; active members included Vint Cerf from Stanford University, Alex McKenzie from BBN, Donald Davies and Roger Scantlebury from NPL, and Louis Pouzin and Hubert Zimmermann from IRIA.
153. Pouzin coined the term catenet for concatenated network.
154. Bob Metcalfe at Xerox PARC outlined the idea of Ethernet and PARC Universal Packet (PUP) for internetworking.
155. Bob Kahn, now at DARPA, recruited Vint Cerf to work with him on the problem.
156. By 1973, these groups had worked out a fundamental reformulation, in which the differences between network protocols were hidden by using a common internetworking protocol.
157. Instead of the network being responsible for reliability, as in the ARPANET, the hosts became responsible.
158. Cerf and Kahn published their ideas in May 1974, which incorporated concepts implemented by Louis Pouzin and Hubert Zimmermann in the CYCLADES network.
159. The specification of the resulting protocol, the Transmission Control Program, was published as RFC 675 by the Network Working Group in December 1974.
160. It contains the first attested use of the term internet, as a shorthand for internetwork.
161. This software was monolithic in design using two simplex communication channels for each user session.
162. With the role of the network reduced to a core of functionality, it became possible to exchange traffic with other networks independently from their detailed characteristics, thereby solving the fundamental problems of internetworking.
163. The software was redesigned as a modular protocol stack, using full-duplex channels; between 1976 and 1977, Yogen Dalal, John Shoch and Robert Metcalfe among others, proposed separating TCP's routing and transmission control functions into two discrete layers, which led to the splitting of the Transmission Control Program into the Transmission Control Protocol (TCP) and the Internet Protocol (IP) in version 3 in 1978.
164. Version 4 was described in IETF publication RFC 791 (September 1981), 792 and 793.
165. It was installed on SATNET in 1982 and the ARPANET in January 1983 after the DoD made it standard for all military computer networking.
166. This resulted in a networking model that became known informally as TCP/IP.
167. It was also referred to as the Department of Defense (DoD) model or DARPA model.
168. Cerf credits several of his graduate students with important work on the design and testing.
169. DARPA sponsored or encouraged the development of TCP/IP implementations for many operating systems.
170. After the ARPANET had been up and running for several years, ARPA looked for another agency to hand off the network to; ARPA's primary mission was funding cutting-edge research and development, not running a communications utility.
171. In July 1975, the network was turned over to the Defense Communications Agency, also part of the Department of Defense.
172. In 1983, the U.S. military portion of the ARPANET was broken off as a separate network, the MILNET.
173. MILNET subsequently became the unclassified but military-only NIPRNET, in parallel with the SECRET-level SIPRNET and JWICS for TOP SECRET and above.
174. NIPRNET does have controlled security gateways to the public Internet.
175. The networks based on the ARPANET were government funded and therefore restricted to noncommercial uses such as research; unrelated commercial use was strictly forbidden.
176. This initially restricted connections to military sites and universities.
177. During the 1980s, the connections expanded to more educational institutions, and a growing number of companies such as Digital Equipment Corporation and Hewlett-Packard, which were participating in research projects or providing services to those who were.
178. Data transmission speeds depended upon the type of connection, the slowest being analog telephone lines and the fastest using optical networking technology.
179. Several other branches of the U.S. government, the National Aeronautics and Space Administration (NASA), the National Science Foundation (NSF), and the Department of Energy (DOE) became heavily involved in Internet research and started development of a successor to ARPANET.
180. In the mid-1980s, all three of these branches developed the first Wide Area Networks based on TCP/IP.
181. NASA developed the NASA Science Network, NSF developed CSNET and DOE evolved the Energy Sciences Network or ESNet.
182. NASA developed the TCP/IP based NASA Science Network (NSN) in the mid-1980s, connecting space scientists to data and information stored anywhere in the world.
183. In 1989, the DECnet-based Space Physics Analysis Network (SPAN) and the TCP/IP-based NASA Science Network (NSN) were brought together at NASA Ames Research Center creating the first multiprotocol wide area network called the NASA Science Internet, or NSI.
184. NSI was established to provide a totally integrated communications infrastructure to the NASA scientific community for the advancement of earth, space and life sciences.
185. As a high-speed, multiprotocol, international network, NSI provided connectivity to over 20,000 scientists across all seven continents.
186. In 1981, NSF supported the development of the Computer Science Network (CSNET).
187. CSNET connected with ARPANET using TCP/IP, and ran TCP/IP over X.25, but it also supported departments without sophisticated network connections, using automated dial-up mail exchange.
188. CSNET played a central role in popularizing the Internet outside the ARPANET.
189. In 1986, the NSF created NSFNET, a 56 kbit/s backbone to support the NSF-sponsored supercomputing centers.
190. The NSFNET also provided support for the creation of regional research and education networks in the United States, and for the connection of university and college campus networks to the regional networks.
191. The use of NSFNET and the regional networks was not limited to supercomputer users and the 56 kbit/s network quickly became overloaded.
192. NSFNET was upgraded to 1.5 Mbit/s in 1988 under a cooperative agreement with the Merit Network in partnership with IBM, MCI, and the State of Michigan.
193. The existence of NSFNET and the creation of Federal Internet Exchanges (FIXes) allowed the ARPANET to be decommissioned in 1990.
194. NSFNET was expanded and upgraded to dedicated fiber, optical lasers and optical amplifier systems capable of delivering T3 start up speeds or 45 Mbit/s in 1991.
195. However, the T3 transition by MCI took longer than expected, allowing Sprint to establish a coast-to-coast long-distance commercial Internet service.
196. When NSFNET was decommissioned in 1995, its optical networking backbones were handed off to several commercial Internet service providers, including MCI, PSI Net and Sprint.
197. As a result, when the handoff was complete, Sprint and its Washington DC Network Access Points began to carry Internet traffic, and by 1996, Sprint was the world's largest carrier of Internet traffic.
198. The research and academic community continues to develop and use advanced networks such as Internet2 in the United States and JANET in the United Kingdom.
199. The term "internet" was reflected in the first RFC published on the TCP protocol (RFC 675: Internet Transmission Control Program, December 1974) as a short form of internetworking, when the two terms were used interchangeably.
200. In general, an internet was a collection of networks linked by a common protocol.
201. In the time period when the ARPANET was connected to the newly formed NSFNET project in the late 1980s, the term was used as the name of the network, Internet, being the large and global TCP/IP network.
202. Opening the Internet and the fiber optic backbone to corporate and consumers increased demand for network capacity.
203. The expense and delay of laying new fiber led providers to test a fiber bandwidth expansion alternative that had been pioneered in the late 1970s by Optelecom using "interactions between light and matter, such as lasers and optical devices used for optical amplification and wave mixing".
204. This technology became known as wave division multiplexing (WDM).
205. Bell Labs deployed a 4-channel WDM system in 1995.
206. To develop a mass capacity (dense) WDM system, Optelecom and its former head of Light Systems Research, David R. Huber formed a new venture, Ciena Corp., that deployed the world's first dense WDM system on the Sprint fiber network in June 1996.
207. This was referred to as the real start of optical networking.
208. As interest in networking grew by needs of collaboration, exchange of data, and access of remote computing resources, the Internet technologies spread throughout the rest of the world.
209. The hardware-agnostic approach in TCP/IP supported the use of existing network infrastructure, such as the International Packet Switched Service (IPSS) X.25 network, to carry Internet traffic.
210. Many sites unable to link directly to the Internet created simple gateways for the transfer of electronic mail, the most important application of the time.
211. Sites with only intermittent connections used UUCP or FidoNet and relied on the gateways between these networks and the Internet.
212. Some gateway services went beyond simple mail peering, such as allowing access to File Transfer Protocol (FTP) sites via UUCP or mail.
213. Finally, routing technologies were developed for the Internet to remove the remaining centralized routing aspects.
214. The Exterior Gateway Protocol (EGP) was replaced by a new protocol, the Border Gateway Protocol (BGP).
215. This provided a meshed topology for the Internet and reduced the centric architecture which ARPANET had emphasized.
216. In 1994, Classless Inter-Domain Routing (CIDR) was introduced to support better conservation of address space which allowed use of route aggregation to decrease the size of routing tables.
217. The MOS transistor underpinned the rapid growth of telecommunication bandwidth over the second half of the 20th century.
218. To address the need for transmission capacity beyond that provided by radio, satellite and analog copper telephone lines, engineers developed optical communications systems based on fiber optic cables powered by lasers and optical amplifier techniques.
219. The concept of lasing arose from a 1917 paper by Albert Einstein, "On the Quantum Theory of Radiation".
220. Einstein expanded upon a conversation with Max Planck on how atoms absorb and emit light, part of a thought process that, with input from Erwin Schrödinger, Werner Heisenberg and others, gave rise to quantum mechanics.
221. Specifically, in his quantum theory, Einstein mathematically determined that light could be generated not only by spontaneous emission, such as the light emitted by an incandescent light or the Sun, but also by stimulated emission.
222. Forty years later, on November 13, 1957, Columbia University physics student Gordon Gould first realized how to make light by stimulated emission through a process of optical amplification.
223. He coined the term LASER for this technology—Light Amplification by Stimulated Emission of Radiation.
224. Using Gould's light amplification method (patented as "Optically Pumped Laser Amplifier"), Theodore Maiman made the first working laser on May 16, 1960.
225. Gould co-founded Optelecom in 1973 to commercialize his inventions in optical fiber telecommunications, just as Corning Glass was producing the first commercial fiber optic cable in small quantities.
226. Optelecom configured its own fiber lasers and optical amplifiers into the first commercial optical communication systems which it delivered to Chevron and the US Army Missile Defense.
227. Three years later, GTE deployed the first optical telephone system in 1977 in Long Beach, California.
228. By the early 1980s, optical networks powered by lasers, LED and optical amplifier equipment supplied by Bell Labs, NTT and Perelli were used by select universities and long-distance telephone providers.
229. In 1982, Norway (NORSAR and NDRE) and Peter Kirstein's research group at University College London (UCL) left the ARPANET and reconnected using TCP/IP over SATNET.
230. There were 40 British research groups using UCL's link to ARPANET in 1975; by 1984 there was a user population of about 150 people on both sides of the Atlantic.
231. Between 1984 and 1988, CERN began installation and operation of TCP/IP to interconnect its major internal computer systems, workstations, PCs, and an accelerator control system.
232. CERN continued to operate a limited self-developed system (CERNET) internally and several incompatible (typically proprietary) network protocols externally.
233. There was considerable resistance in Europe towards more widespread use of TCP/IP, and the CERN TCP/IP intranets remained isolated from the Internet until 1989, when a transatlantic connection to Cornell University was established.
234. The Computer Science Network (CSNET) began operation in 1981 to provide networking connections to institutions that could not connect directly to ARPANET.
235. Its first international connection was to Israel in 1984.
236. Soon after, connections were established to computer science departments in Canada, France, and Germany.
237. In 1988, the first international connections to NSFNET was established by France's INRIA, and Piet Beertema at the Centrum Wiskunde & Informatica (CWI) in the Netherlands.
238. Daniel Karrenberg, from CWI, visited Ben Segal, CERN's TCP/IP coordinator, looking for advice about the transition of EUnet, the European side of the UUCP Usenet network (much of which ran over X.25 links), over to TCP/IP.
239. The previous year, Segal had met with Len Bosack from the then still small company Cisco about purchasing some TCP/IP routers for CERN, and Segal was able to give Karrenberg advice and forward him on to Cisco for the appropriate hardware.
240. This expanded the European portion of the Internet across the existing UUCP networks.
241. The NORDUnet connection to NSFNET was in place soon after, providing open access for university students in Denmark, Finland, Iceland, Norway, and Sweden.
242. In January 1989, CERN opened its first external TCP/IP connections.
243. This coincided with the creation of Réseaux IP Européens (RIPE), initially a group of IP network administrators who met regularly to carry out coordination work together.
244. Later, in 1992, RIPE was formally registered as a cooperative in Amsterdam.
245. The United Kingdom's national research and education network (NREN), JANET, began operation in 1984 using the UK's Coloured Book protocols and connected to NSFNET in 1989.
246. In 1991, JANET adopted Internet Protocol on the existing network.
247. The same year, Dai Davies introduced Internet technology into the pan-European NREN, EuropaNet, which was built on the X.25 protocol.
248. The European Academic and Research Network (EARN) and RARE adopted IP around the same time, and the European Internet backbone EBONE became operational in 1992.
249. Nonetheless, for a period in the late 1980s and early 1990s, engineers, organizations and nations were polarized over the issue of which standard, the OSI model or the Internet protocol suite would result in the best and most robust computer networks.
250. Japan, which had built the UUCP-based network JUNET in 1984, connected to CSNET, and later to NSFNET in 1989, marking the spread of the Internet to Asia.
251. South Korea set up a two-node domestic TCP/IP network in 1982, the System Development Network (SDN), adding a third node the following year.
252. SDN was connected to the rest of the world in August 1983 using UUCP (Unix-to-Unix-Copy); connected to CSNET in December 1984; and formally connected to the NSFNET in 1990.
253. In Australia, ad hoc networking to ARPA and in-between Australian universities formed in the late 1980s, based on various technologies such as X.25, UUCPNet, and via a CSNET.
254. These were limited in their connection to the global networks, due to the cost of making individual international UUCP dial-up or X.25 connections.
255. In 1989, Australian universities joined the push towards using IP protocols to unify their networking infrastructures.
256. AARNet was formed in 1989 by the Australian Vice-Chancellors' Committee and provided a dedicated IP based network for Australia.
257. New Zealand adopted the UK's Coloured Book protocols as an interim standard and established its first international IP connection to the U.S. in 1989.
258. While developed countries with technological infrastructures were joining the Internet, developing countries began to experience a digital divide separating them from the Internet.
259. On an essentially continental basis, they built organizations for Internet resource administration and to share operational experience, which enabled more transmission facilities to be put into place.
260. At the beginning of the 1990s, African countries relied upon X.25 IPSS and 2400 baud modem UUCP links for international and internetwork computer communications.
261. In August 1995, InfoMail Uganda, Ltd., a privately held firm in Kampala now known as InfoCom, and NSN Network Services of Avon, Colorado, sold in 1997 and now known as Clear Channel Satellite, established Africa's first native TCP/IP high-speed satellite Internet services.
262. The data connection was originally carried by a C-Band RSCC Russian satellite which connected InfoMail's Kampala offices directly to NSN's MAE-West point of presence using a private network from NSN's leased ground station in New Jersey.
263. InfoCom's first satellite connection was just 64 kbit/s, serving a Sun host computer and twelve US Robotics dial-up modems.
264. In 1996, a USAID funded project, the Leland Initiative, started work on developing full Internet connectivity for the continent.
265. Guinea, Mozambique, Madagascar and Rwanda gained satellite earth stations in 1997, followed by Ivory Coast and Benin in 1998.
266. Africa is building an Internet infrastructure.
267. AFRINIC, headquartered in Mauritius, manages IP address allocation for the continent.
268. As with other Internet regions, there is an operational forum, the Internet Community of Operational Networking Specialists.
269. There are many programs to provide high-performance transmission plant, and the western and southern coasts have undersea optical cable.
270. High-speed cables join North Africa and the Horn of Africa to intercontinental cable systems.
271. Undersea cable development is slower for East Africa; the original joint effort between New Partnership for Africa's Development (NEPAD) and the East Africa Submarine System (Eassy) has broken off and may become two efforts.
272. The Asia Pacific Network Information Centre (APNIC), headquartered in Australia, manages IP address allocation for the continent.
273. APNIC sponsors an operational forum, the Asia-Pacific Regional Internet Conference on Operational Technologies (APRICOT).
274. In South Korea, VDSL, a last mile technology developed in the 1990s by NextLevel Communications, connected corporate and consumer copper-based telephone lines to the Internet.
275. The People's Republic of China established its first TCP/IP college network, Tsinghua University's TUNET in 1991.
276. The PRC went on to make its first global Internet connection in 1994, between the Beijing Electro-Spectrometer Collaboration and Stanford University's Linear Accelerator Center.
277. However, China went on to implement its own digital divide by implementing a country-wide content filter.
278. Japan hosted the annual meeting of the Internet Society, INET'92, in Kobe.
279. Singapore developed TECHNET in 1990, and Thailand gained a global Internet connection between Chulalongkorn University and UUNET in 1992.
280. As with the other regions, the Latin American and Caribbean Internet Addresses Registry (LACNIC) manages the IP address space and other resources for its area.
281. LACNIC, headquartered in Uruguay, operates DNS root, reverse DNS, and other key services.

1989-2004: Rise of the global Internet, Web 1.0

282. Initially, as with its predecessor networks, the system that would evolve into the Internet was primarily for government and government body use.
283. Although commercial use was forbidden, the exact definition of commercial use was unclear and subjective.
284. UUCPNet and the X.25 IPSS had no such restrictions, which would eventually see the official barring of UUCPNet use of ARPANET and NSFNET connections.
285. As a result, during the late 1980s, the first Internet service provider (ISP) companies were formed.
286. Companies like PSINet, UUNET, Netcom, and Portal Software were formed to provide service to the regional research networks and provide alternate network access, UUCP-based email and Usenet News to the public.
287. In 1989, MCI Mail became the first commercial email provider to get an experimental gateway to the Internet.
288. The first commercial dialup ISP in the United States was The World, which opened in 1989.
289. In 1992, the U.S. Congress passed the Scientific and Advanced-Technology Act, 42 U.S.C. § 1862(g), which allowed NSF to support access by the research and education communities to computer networks which were not used exclusively for research and education purposes, thus permitting NSFNET to interconnect with commercial networks.
290. This caused controversy within the research and education community, who were concerned commercial use of the network might lead to an Internet that was less responsive to their needs, and within the community of commercial network providers, who felt that government subsidies were giving an unfair advantage to some organizations.
291. By 1990, ARPANET's goals had been fulfilled and new networking technologies exceeded the original scope and the project came to a close.
292. New network service providers including PSINet, Alternet, CERFNet, ANS CO+RE, and many others were offering network access to commercial customers.
293. NSFNET was no longer the de facto backbone and exchange point of the Internet.
294. The Commercial Internet eXchange (CIX), Metropolitan Area Exchanges (MAEs), and later Network Access Points (NAPs) were becoming the primary interconnections between many networks.
295. The final restrictions on carrying commercial traffic ended on April 30, 1995, when the National Science Foundation ended its sponsorship of the NSFNET Backbone Service.
296. NSF provided initial support for the NAPs and interim support to help the regional research and education networks transition to commercial ISPs.
297. NSF also sponsored the very high speed Backbone Network Service (vBNS) which continued to provide support for the supercomputing centers and research and education in the United States.
298. An event held on 11 January 1994, The Superhighway Summit at UCLA's Royce Hall, was the "first public conference bringing together all of the major industry, government and academic leaders in the field also began the national dialogue about the Information Superhighway and its implications".
299. The invention of the World Wide Web by Tim Berners-Lee at CERN, as an application on the Internet, brought many social and commercial uses to what was, at the time, a network of networks for academic and research institutions.
300. The Web opened to the public in 1991 and began to enter general use in 1993–4, when websites for everyday use started to become available.
301. During the first decade or so of the public Internet, the immense changes it would eventually enable in the 2000s were still nascent.
302. In terms of providing context for this period, mobile cellular devices ("smartphones" and other cellular devices) which today provide near-universal access, were used for business and not a routine household item owned by parents and children worldwide.
303. Social media in the modern sense had yet to come into existence, laptops were bulky and most households did not have computers.
304. Data rates were slow and most people lacked means to video or digitize video; media storage was transitioning slowly from analog tape to digital optical discs (DVD and to an extent still, floppy disc to CD).
305. Enabling technologies used from the early 2000s such as PHP, modern JavaScript and Java, technologies such as AJAX, HTML 4 (and its emphasis on CSS), and various software frameworks, which enabled and simplified speed of web development, largely awaited invention and their eventual widespread adoption.
306. The Internet was widely used for mailing lists, emails, creating and distributing maps with tools like MapQuest, e-commerce and early popular online shopping (Amazon and eBay for example), online forums and bulletin boards, and personal websites and blogs, and use was growing rapidly, but by more modern standards, the systems used were static and lacked widespread social engagement.
307. It awaited a number of events in the early 2000s to change from a communications technology to gradually develop into a key part of global society's infrastructure.
308. Typical design elements of these "Web 1.0" era websites included: Static pages instead of dynamic HTML; content served from filesystems instead of relational databases; pages built using Server Side Includes or CGI instead of a web application written in a dynamic programming language; HTML 3.2-era structures such as frames and tables to create page layouts; online guestbooks; overuse of GIF buttons and similar small graphics promoting particular items; and HTML forms sent via email.
309. Support for server side scripting was rare on shared servers so the usual feedback mechanism was via email, using mailto forms and their email program.
310. From 1995 to 2000, the first speculative investment bubble related to the Internet took place, in which "dot-com" companies (referring to the ".com" top level domain used by businesses) were propelled to exceedingly high valuations as investors rapidly stoked stock values, followed by a market crash; the first dot-com bubble.
311. However this only temporarily slowed enthusiasm and growth, which quickly recovered and continued to grow.
312. The history of the World Wide Web up to around 2004 was retrospectively named and described by some as "Web 1.0".
313. In the final stage of IPv4 address exhaustion, the last IPv4 address block was assigned in January 2011 at the level of the regional Internet registries.
314. IPv4 uses 32-bit addresses which limits the address space to 2^32 addresses, i.e. 4,294,967,296 addresses.
315. IPv4 is in the process of replacement by IPv6, its successor, which uses 128-bit addresses, providing 2^128 addresses, i.e. 340,282,366,920,938,463,463,374,607,431,768,211,456, a vastly increased address space.
316. The shift to IPv6 is expected to take a long time to complete.

2004-present: Web 2.0, global ubiquity, social media

317. The rapid technical advances that would propel the Internet into its place as a social system, which has completely transformed the way humans interact with each other, took place during a relatively short period from around 2005 to 2010, coinciding with the point in time in which IoT devices surpassed the number of humans alive at some point in the late 2000s.
318. They included: The call to "Web 2.0" in 2004 (first suggested in 1999).
319. Accelerating adoption and commoditization among households of, and familiarity with, the necessary hardware (such as computers).
320. Accelerating storage technology and data access speeds – hard drives emerged, took over from far smaller, slower floppy discs, and grew from megabytes to gigabytes (and by around 2010, terabytes), RAM from hundreds of kilobytes to gigabytes as typical amounts on a system, and Ethernet, the enabling technology for TCP/IP, moved from common speeds of kilobits to tens of megabits per second, to gigabits per second.
321. High speed Internet and wider coverage of data connections, at lower prices, allowing larger traffic rates, more reliable simpler traffic, and traffic from more locations.
322. The public's accelerating perception of the potential of computers to create new means and approaches to communication, the emergence of social media and websites such as Twitter and Facebook to their later prominence, and global collaborations such as Wikipedia (which existed before but gained prominence as a result).
323. The mobile device revolution, particularly with smartphones and tablet computers becoming widespread, which began to provide easy access to the Internet to much of human society of all ages, in their daily lives, and allowed them to share, discuss, and continually update, inquire, and respond.
324. Non-volatile RAM rapidly grew in size and reliability, and decreased in price, becoming a commodity capable of enabling high levels of computing activity on these small handheld devices as well as solid-state drives (SSD).
325. An emphasis on power efficient processor and device design, rather than purely high processing power; one of the beneficiaries of this was Arm, a British company which had focused since the 1980s on powerful but low cost simple microprocessors.
326. The ARM architecture family rapidly gained dominance in the market for mobile and embedded devices.
327. The term "Web 2.0" describes websites that emphasize user-generated content (including user-to-user interaction), usability, and interoperability.
328. It first appeared in a January 1999 article called "Fragmented Future" written by Darcy DiNucci, a consultant on electronic information design, where she wrote: The Web we know now, which loads into a browser window in essentially static screenfuls, is only an embryo of the Web to come. The first glimmerings of Web 2.0 are beginning to appear, and we are just starting to see how that embryo might develop. The Web will be understood not as screenfuls of text and graphics but as a transport mechanism, the ether through which interactivity happens. It will [...] appear on your computer screen, [...] on your TV set [...] your car dashboard [...] your cell phone [...] hand-held game machines [...] maybe even your microwave oven.
329. The term resurfaced during 2002–2004, and gained prominence in late 2004 following presentations by Tim O'Reilly and Dale Dougherty at the first Web 2.0 Conference.
330. In their opening remarks, John Battelle and Tim O'Reilly outlined their definition of the "Web as Platform", where software applications are built upon the Web as opposed to upon the desktop.
331. The unique aspect of this migration, they argued, is that "customers are building your business for you".
332. They argued that the activities of users generating content (in the form of ideas, text, videos, or pictures) could be "harnessed" to create value.
333. "Web 2.0" does not refer to an update to any technical specification, but rather to cumulative changes in the way Web pages are made and used.
334. "Web 2.0" describes an approach, in which sites focus substantially upon allowing users to interact and collaborate with each other in a social media dialogue as creators of user-generated content in a virtual community, in contrast to Web sites where people are limited to the passive viewing of content.
335. Examples of Web 2.0 include social networking services, blogs, wikis, folksonomies, video sharing sites, hosted services, Web applications, and mashups.
336. Terry Flew, in his 3rd edition of New Media, described what he believed to characterize the differences between Web 1.0 and Web 2.0: [The] move from personal websites to blogs and blog site aggregation, from publishing to participation, from web content as the outcome of large up-front investment to an ongoing and interactive process, and from content management systems to links based on tagging (folksonomy).
337. This era saw several household names gain prominence through their community-oriented operation – YouTube, Twitter, Facebook, Reddit and Wikipedia being some examples.
338. Telephone systems have been slowly adopting voice over IP since 2003.
339. Early experiments proved that voice can be converted to digital packets and sent over the Internet.
340. The packets are collected and converted back to analog voice.
341. The process of change that generally coincided with Web 2.0 was itself greatly accelerated and transformed only a short time later by the increasing growth in mobile devices.
342. This mobile revolution meant that computers in the form of smartphones became something many people used, took with them everywhere, communicated with, used for photographs and videos they instantly shared or to shop or seek information "on the move" – and used socially, as opposed to items on a desk at home or just used for work.
343. Location-based services, services using location and other sensor information, and crowdsourcing (frequently but not always location based), became common, with posts tagged by location, or websites and services becoming location aware.
344. Mobile-targeted websites (such as "m.example.com") became common, designed especially for the new devices used.
345. Netbooks, ultrabooks, widespread 4G and Wi-Fi, and mobile chips capable or running at nearly the power of desktops from not many years before on far lower power usage, became enablers of this stage of Internet development, and the term "App" (short for "Application program" or "Program") became popularized, as did the "App store".
346. This "mobile revolution" has allowed for people to have a nearly unlimited amount of information at all times.
347. With the ability to access the internet from cell phones came a change in the way media was consumed.
348. Media consumption statistics show that over half of media consumption between those aged 18 and 34 were using a smartphone.
349. In the transition to Web 2.0 in the mid-2000s, a number of research groups emerged aiming to improve the existing infrastructure of the Internet.
350. These future Internet groups coalesced around the idea that the current Internet and its legacy protocols were inadequate to support the exponential increase in traffic and the integration of mobile technologies.
351. A number of experimental networking schemes and protocols were developed, seeking to either build upon the existing Internet in an evolutionary approach or to supplant it entirely in a clean-slate approach.
352. These schemes varied in scope, but usually prioritized enhanced support for mobile networking, cloud computing, content delivery, and user privacy.
353. The most prominent of these future Internet groups included the NSF's Future Internet Design (FIND), established in 2006, as well as its successor, the Future Internet Architecture (FIA), established in 2010.
354. Following the NSF's lead, in 2006 Japan's NICT established the AKARI Project, while in 2008 the European Union established the Evolved Internet Future for European Leadership (EIFFEL).
355. These efforts were supported by experimental testbeds, such as the NSF's Global Environment for Network Innovations (GENI); the EU's Future Internet Research and Experimentation (FIRE); and NICT's JGN2plus.
356. Each of these testbeds facilitated the large-scale validation of their networking schemes and protocols.
357. One of the few tangible results of the NSF's future Internet initiatives include the increased use of software-defined networking as well as the proposal for named data networking.
358. Both FIRE and GENI dissolved in 2022 and 2023 respectively.
359. The first Internet link into low Earth orbit was established on January 22, 2010, when astronaut T. J. Creamer posted the first unassisted update to his Twitter account from the International Space Station, marking the extension of the Internet into space.
360. (Astronauts at the ISS had used email and Twitter before, but these messages had been relayed to the ground through a NASA data link before being posted by a human proxy.)
361. This personal Web access, which NASA calls the Crew Support LAN, uses the space station's high-speed Ku band microwave link.
362. To surf the Web, astronauts can use a station laptop computer to control a desktop computer on Earth, and they can talk to their families and friends on Earth using Voice over IP equipment.
363. Communication with spacecraft beyond Earth orbit has traditionally been over point-to-point links through the Deep Space Network.
364. Each such data link must be manually scheduled and configured.
365. In the late 1990s NASA and Google began working on a new network protocol, delay-tolerant networking (DTN), which automates this process, allows networking of spaceborne transmission nodes, and takes the fact into account that spacecraft can temporarily lose contact because they move behind the Moon or planets, or because space weather disrupts the connection.
366. Under such conditions, DTN retransmits data packages instead of dropping them, as the standard TCP/IP Internet Protocol does.
367. NASA conducted the first field test of what it calls the "deep space internet" in November 2008.
368. Testing of DTN-based communications between the International Space Station and Earth (now termed disruption-tolerant networking) has been ongoing since March 2009, and was scheduled to continue until March 2014.
369. This network technology is supposed to ultimately enable missions that involve multiple spacecraft where reliable inter-vessel communication might take precedence over vessel-to-Earth downlinks.
370. According to a February 2011 statement by Google's Vint Cerf, the so-called "bundle protocols" have been uploaded to NASA's EPOXI mission spacecraft (which is in orbit around the Sun) and communication with Earth has been tested at a distance of approximately 80 light seconds.

Internet governance

371. As a globally distributed network of voluntarily interconnected autonomous networks, the Internet operates without a central governing body.
372. Each constituent network chooses the technologies and protocols it deploys from the technical standards that are developed by the Internet Engineering Task Force (IETF).
373. However, successful interoperation of many networks requires certain parameters that must be common throughout the network.
374. For managing such parameters, the Internet Assigned Numbers Authority (IANA) oversees the allocation and assignment of various technical identifiers.
375. In addition, the Internet Corporation for Assigned Names and Numbers (ICANN) provides oversight and coordination for the two principal name spaces in the Internet, the Internet Protocol address space and the Domain Name System.
376. The IANA function was originally performed by USC Information Sciences Institute (ISI), and it delegated portions of this responsibility with respect to numeric network and autonomous system identifiers to the Network Information Center (NIC) at Stanford Research Institute (SRI International) in Menlo Park, California.
377. ISI's Jonathan Postel managed the IANA, served as RFC Editor and performed other key roles until his death in 1998.
378. As the early ARPANET grew, hosts were referred to by names, and a HOSTS.TXT file would be distributed from SRI International to each host on the network.
379. As the network grew, this became cumbersome.
380. A technical solution came in the form of the Domain Name System, created by ISI's Paul Mockapetris in 1983.
381. The Defense Data Network—Network Information Center (DDN-NIC) at SRI handled all registration services, including the top-level domains (TLDs) of .mil, .gov, .edu, .org, .net, .com and .us, root nameserver administration and Internet number assignments under a United States Department of Defense contract.
382. In 1991, the Defense Information Systems Agency (DISA) awarded the administration and maintenance of DDN-NIC (managed by SRI up until this point) to Government Systems, Inc., who subcontracted it to the small private-sector Network Solutions, Inc.
383. The increasing cultural diversity of the Internet also posed administrative challenges for centralized management of the IP addresses.
384. In October 1992, the Internet Engineering Task Force (IETF) published RFC 1366, which described the "growth of the Internet and its increasing globalization" and set out the basis for an evolution of the IP registry process, based on a regionally distributed registry model.
385. This document stressed the need for a single Internet number registry to exist in each geographical region of the world (which would be of "continental dimensions").
386. Registries would be "unbiased and widely recognized by network providers and subscribers" within their region.
387. The RIPE Network Coordination Centre (RIPE NCC) was established as the first RIR in May 1992.
388. The second RIR, the Asia Pacific Network Information Centre (APNIC), was established in Tokyo in 1993, as a pilot project of the Asia Pacific Networking Group.
389. Since at this point in history most of the growth on the Internet was coming from non-military sources, it was decided that the Department of Defense would no longer fund registration services outside of the .mil TLD.
390. In 1993 the U.S. National Science Foundation, after a competitive bidding process in 1992, created the InterNIC to manage the allocations of addresses and management of the address databases, and awarded the contract to three organizations.
391. Registration Services would be provided by Network Solutions; Directory and Database Services would be provided by AT&T; and Information Services would be provided by General Atomics.
392. Over time, after consultation with the IANA, the IETF, RIPE NCC, APNIC, and the Federal Networking Council (FNC), the decision was made to separate the management of domain names from the management of IP numbers.
393. Following the examples of RIPE NCC and APNIC, it was recommended that management of IP address space then administered by the InterNIC should be under the control of those that use it, specifically the ISPs, end-user organizations, corporate entities, universities, and individuals.
394. As a result, the American Registry for Internet Numbers (ARIN) was established as in December 1997, as an independent, not-for-profit corporation by direction of the National Science Foundation and became the third Regional Internet Registry.
395. In 1998, both the IANA and remaining DNS-related InterNIC functions were reorganized under the control of ICANN, a California non-profit corporation contracted by the United States Department of Commerce to manage a number of Internet-related tasks.
396. As these tasks involved technical coordination for two principal Internet name spaces (DNS names and IP addresses) created by the IETF, ICANN also signed a memorandum of understanding with the IAB to define the technical work to be carried out by the Internet Assigned Numbers Authority.
397. The management of Internet address space remained with the regional Internet registries, which collectively were defined as a supporting organization within the ICANN structure.
398. ICANN provides central coordination for the DNS system, including policy coordination for the split registry / registrar system, with competition among registry service providers to serve each top-level-domain and multiple competing registrars offering DNS services to end-users.
399. The Internet Engineering Task Force (IETF) is the largest and most visible of several loosely related ad-hoc groups that provide technical direction for the Internet, including the Internet Architecture Board (IAB), the Internet Engineering Steering Group (IESG), and the Internet Research Task Force (IRTF).
400. The IETF is a loosely self-organized group of international volunteers who contribute to the engineering and evolution of Internet technologies.
401. It is the principal body engaged in the development of new Internet standard specifications.
402. Much of the work of the IETF is organized into Working Groups.
403. Standardization efforts of the Working Groups are often adopted by the Internet community, but the IETF does not control or patrol the Internet.
404. The IETF grew out of quarterly meetings with U.S. government-funded researchers, starting in January 1986.
405. Non-government representatives were invited by the fourth IETF meeting in October 1986.
406. The concept of Working Groups was introduced at the fifth meeting in February 1987.
407. The seventh meeting in July 1987 was the first meeting with more than one hundred attendees.
408. In 1992, the Internet Society, a professional membership society, was formed and IETF began to operate under it as an independent international standards body.
409. The first IETF meeting outside of the United States was held in Amsterdam, the Netherlands, in July 1993.
410. Today, the IETF meets three times per year and attendance has been as high as ca. 2,000 participants.
411. Typically one in three IETF meetings are held in Europe or Asia.
412. The number of non-US attendees is typically ca. 50%, even at meetings held in the United States.
413. The IETF is not a legal entity, has no governing board, no members, and no dues.
414. The closest status resembling membership is being on an IETF or Working Group mailing list.
415. IETF volunteers come from all over the world and from many different parts of the Internet community.
416. The IETF works closely with and under the supervision of the Internet Engineering Steering Group (IESG) and the Internet Architecture Board (IAB).
417. The Internet Research Task Force (IRTF) and the Internet Research Steering Group (IRSG), peer activities to the IETF and IESG under the general supervision of the IAB, focus on longer-term research issues.
418. RFCs are the main documentation for the work of the IAB, IESG, IETF, and IRTF.
419. Originally intended as requests for comments, RFC 1, "Host Software", was written by Steve Crocker at UCLA in April 1969.
420. These technical memos documented aspects of ARPANET development.
421. They were edited by Jon Postel, the first RFC Editor.
422. RFCs cover a wide range of information from proposed standards, draft standards, full standards, best practices, experimental protocols, history, and other informational topics.
423. RFCs can be written by individuals or informal groups of individuals, but many are the product of a more formal Working Group.
424. Drafts are submitted to the IESG either by individuals or by the Working Group Chair.
425. An RFC Editor, appointed by the IAB, separate from IANA, and working in conjunction with the IESG, receives drafts from the IESG and edits, formats, and publishes them.
426. Once an RFC is published, it is never revised.
427. If the standard it describes changes or its information becomes obsolete, the revised standard or updated information will be re-published as a new RFC that "obsoletes" the original.
428. The Internet Society (ISOC) is an international, nonprofit organization founded during 1992 "to assure the open development, evolution and use of the Internet for the benefit of all people throughout the world".
429. With offices near Washington, DC, US, and in Geneva, Switzerland, ISOC has a membership base comprising more than 80 organizational and more than 50,000 individual members.
430. Members also form "chapters" based on either common geographical location or special interests.
431. There are currently more than 90 chapters around the world.
432. ISOC provides financial and organizational support to and promotes the work of the standards settings bodies for which it is the organizational home: the Internet Engineering Task Force (IETF), the Internet Architecture Board (IAB), the Internet Engineering Steering Group (IESG), and the Internet Research Task Force (IRTF).
433. ISOC also promotes understanding and appreciation of the Internet model of open, transparent processes and consensus-based decision-making.
434. Since the 1990s, the Internet's governance and organization has been of global importance to governments, commerce, civil society, and individuals.
435. The organizations which held control of certain technical aspects of the Internet were the successors of the old ARPANET oversight and the current decision-makers in the day-to-day technical aspects of the network.
436. While recognized as the administrators of certain aspects of the Internet, their roles and their decision-making authority are limited and subject to increasing international scrutiny and increasing objections.
437. These objections have led to the ICANN removing themselves from relationships with first the University of Southern California in 2000, and in September 2009 gaining autonomy from the US government by the ending of its longstanding agreements, although some contractual obligations with the U.S. Department of Commerce continued.
438. Finally, on October 1, 2016, ICANN ended its contract with the United States Department of Commerce National Telecommunications and Information Administration (NTIA), allowing oversight to pass to the global Internet community.
439. The IETF, with financial and organizational support from the Internet Society, continues to serve as the Internet's ad-hoc standards body and issues Request for Comments.
440. In November 2005, the World Summit on the Information Society, held in Tunis, called for an Internet Governance Forum (IGF) to be convened by United Nations Secretary General.
441. The IGF opened an ongoing, non-binding conversation among stakeholders representing governments, the private sector, civil society, and the technical and academic communities about the future of Internet governance.
442. The first IGF meeting was held in October/November 2006 with follow up meetings annually thereafter.
443. Since WSIS, the term "Internet governance" has been broadened beyond narrow technical concerns to include a wider range of Internet-related policy issues.
444. Tim Berners-Lee, inventor of the web, was becoming concerned about threats to the web's future and in November 2009 at the IGF in Washington DC launched the World Wide Web Foundation (WWWF) to campaign to make the web a safe and empowering tool for the good of humanity with access to all.
445. In November 2019 at the IGF in Berlin, Berners-Lee and the WWWF went on to launch the Contract for the Web, a campaign initiative to persuade governments, companies and citizens to commit to nine principles to stop "misuse" with the warning "If we don't act now - and act together - to prevent the web being misused by those who want to exploit, divide and undermine, we are at risk of squandering" (its potential for good).

Politicization of the Internet

446. Due to its prominence and immediacy as an effective means of mass communication, the Internet has also become more politicized as it has grown.
447. This has led in turn, to discourses and activities that would once have taken place in other ways, migrating to being mediated by internet.
448. Examples include political activities such as public protest and canvassing of support and votes, but also:
449. The spreading of ideas and opinions;
450. Recruitment of followers, and "coming together" of members of the public, for ideas, products, and causes;
451. Providing and widely distributing and sharing information that might be deemed sensitive or relates to whistleblowing (and efforts by specific countries to prevent this by censorship);
452. Criminal activity and terrorism (and resulting law enforcement use, together with its facilitation by mass surveillance);
453. Politically motivated fake news.

Net neutrality

454. On April 23, 2014, the Federal Communications Commission (FCC) was reported to be considering a new rule that would permit Internet service providers to offer content providers a faster track to send content, thus reversing their earlier net neutrality position.
455. A possible solution to net neutrality concerns may be municipal broadband, according to Professor Susan Crawford, a legal and technology expert at Harvard Law School.
456. On May 15, 2014, the FCC decided to consider two options regarding Internet services: first, permit fast and slow broadband lanes, thereby compromising net neutrality; and second, reclassify broadband as a telecommunication service, thereby preserving net neutrality.
457. On November 10, 2014, President Obama recommended the FCC reclassify broadband Internet service as a telecommunications service in order to preserve net neutrality.
458. On January 16, 2015, Republicans presented legislation, in the form of a U.S. Congress HR discussion draft bill, that makes concessions to net neutrality but prohibits the FCC from accomplishing the goal or enacting any further regulation affecting Internet service providers (ISPs).
459. On January 31, 2015, AP News reported that the FCC will present the notion of applying ("with some caveats") Title II (common carrier) of the Communications Act of 1934 to the internet in a vote expected on February 26, 2015.
460. Adoption of this notion would reclassify internet service from one of information to one of telecommunications and, according to Tom Wheeler, chairman of the FCC, ensure net neutrality.
461. The FCC is expected to enforce net neutrality in its vote, according to The New York Times.
462. On February 26, 2015, the FCC ruled in favor of net neutrality by applying Title II (common carrier) of the Communications Act of 1934 and Section 706 of the Telecommunications act of 1996 to the Internet.
463. The FCC chairman, Tom Wheeler, commented, "This is no more a plan to regulate the Internet than the First Amendment is a plan to regulate free speech. They both stand for the same concept."
464. On March 12, 2015, the FCC released the specific details of the net neutrality rules.
465. On April 13, 2015, the FCC published the final rule on its new "Net Neutrality" regulations.
466. On December 14, 2017, the FCC repealed their March 12, 2015 decision by a 3–2 vote regarding net neutrality rules.

Use and culture

467. Email has often been called the killer application of the Internet.
468. It predates the Internet, and was a crucial tool in creating it.
469. Email started in 1965 as a way for multiple users of a time-sharing mainframe computer to communicate.
470. Although the history is undocumented, among the first systems to have such a facility were the System Development Corporation (SDC) Q32 and the Compatible Time-Sharing System (CTSS) at MIT.
471. The ARPANET computer network made a large contribution to the evolution of electronic mail.
472. An experimental inter-system transferred mail on the ARPANET shortly after its creation.
473. In 1971 Ray Tomlinson created what was to become the standard Internet electronic mail addressing format, using the @ sign to separate mailbox names from host names.
474. A number of protocols were developed to deliver messages among groups of time-sharing computers over alternative transmission systems, such as UUCP and IBM's VNET email system.
475. Email could be passed this way between a number of networks, including ARPANET, BITNET and NSFNET, as well as to hosts connected directly to other sites via UUCP.
476. See the history of SMTP protocol.
477. In addition, UUCP allowed the publication of text files that could be read by many others.
478. The News software developed by Steve Daniel and Tom Truscott in 1979 was used to distribute news and bulletin board-like messages.
479. This quickly grew into discussion groups, known as newsgroups, on a wide range of topics.
480. On ARPANET and NSFNET similar discussion groups would form via mailing lists, discussing both technical issues and more culturally focused topics (such as science fiction, discussed on the sflovers mailing list).
481. During the early years of the Internet, email and similar mechanisms were also fundamental to allow people to access resources that were not available due to the absence of online connectivity.
482. UUCP was often used to distribute files using the 'alt.binary' groups.
483. Also, FTP e-mail gateways allowed people that lived outside the US and Europe to download files using ftp commands written inside email messages.
484. The file was encoded, broken in pieces and sent by email; the receiver had to reassemble and decode it later, and it was the only way for people living overseas to download items such as the earlier Linux versions using the slow dial-up connections available at the time.
485. After the popularization of the Web and the HTTP protocol such tools were slowly abandoned.
486. Resource or file sharing has been an important activity on computer networks from well before the Internet was established and was supported in a variety of ways including bulletin board systems (1978), Usenet (1980), Kermit (1981), and many others.
487. The File Transfer Protocol (FTP) for use on the Internet was standardized in 1985 and is still in use today.
488. A variety of tools were developed to aid the use of FTP by helping users discover files they might want to transfer, including the Wide Area Information Server (WAIS) in 1991, Gopher in 1991, Archie in 1991, Veronica in 1992, Jughead in 1993, Internet Relay Chat (IRC) in 1988, and eventually the World Wide Web (WWW) in 1991 with Web directories and Web search engines.
489. In 1999, Napster became the first peer-to-peer file sharing system.
490. Napster used a central server for indexing and peer discovery, but the storage and transfer of files was decentralized.
491. A variety of peer-to-peer file sharing programs and services with different levels of decentralization and anonymity followed, including: Gnutella, eDonkey2000, and Freenet in 2000, FastTrack, Kazaa, Limewire, and BitTorrent in 2001, and Poisoned in 2003.
492. All of these tools are general purpose and can be used to share a wide variety of content, but sharing of music files, software, and later movies and videos are major uses.
493. And while some of this sharing is legal, large portions are not.
494. Lawsuits and other legal actions caused Napster in 2001, eDonkey2000 in 2005, Kazaa in 2006, and Limewire in 2010 to shut down or refocus their efforts.
495. The Pirate Bay, founded in Sweden in 2003, continues despite a trial and appeal in 2009 and 2010 that resulted in jail terms and large fines for several of its founders.
496. File sharing remains contentious and controversial with charges of theft of intellectual property on the one hand and charges of censorship on the other.
497. File hosting allowed for people to expand their computer's hard drives and "host" their files on a server.
498. Most file hosting services offer free storage, as well as larger storage amount for a fee.
499. These services have greatly expanded the internet for business and personal use.
500. Google Drive, launched on April 24, 2012, has become the most popular file hosting service.
501. Google Drive allows users to store, edit, and share files with themselves and other users.
502. Not only does this application allow for file editing, hosting, and sharing.
503. It also acts as Google's own free-to-access office programs, such as Google Docs, Google Slides, and Google Sheets.
504. This application served as a useful tool for University professors and students, as well as those who are in need of Cloud storage.
505. Dropbox, released in June 2007 is a similar file hosting service that allows users to keep all of their files in a folder on their computer, which is synced with Dropbox's servers.
506. This differs from Google Drive as it is not web-browser based.
507. Now, Dropbox works to keep workers and files in sync and efficient.
508. Mega, having over 200 million users, is an encrypted storage and communication system that offers users free and paid storage, with an emphasis on privacy.
509. Being three of the largest file hosting services, Google Drive, Dropbox, and Mega all represent the core ideas and values of these services.

Online piracy

510. The earliest form of online piracy began with a P2P (peer to peer) music sharing service named Napster, launched in 1999.
511. Sites like LimeWire, The Pirate Bay, and BitTorrent allowed for anyone to engage in online piracy, sending ripples through the media industry.
512. With online piracy came a change in the media industry as a whole.

Mobile telephone data traffic

513. Total global mobile data traffic reached 588 exabytes during 2020, a 150-fold increase from 3.86 exabytes/year in 2010.
514. Most recently, smartphones accounted for 95% of this mobile data traffic with video accounting for 66% by type of data.
515. Mobile traffic travels by radio frequency to the closest cell phone tower and its base station where the radio signal is converted into an optical signal that is transmitted over high-capacity optical networking systems that convey the information to data centers.
516. The optical backbones enable much of this traffic as well as a host of emerging mobile services including the Internet of things, 3-D virtual reality, gaming and autonomous vehicles.
517. The most popular mobile phone application is texting, of which 2.1 trillion messages were logged in 2020.
518. The texting phenomenon began on December 3, 1992, when Neil Papworth sent the first text message of "Merry Christmas" over a commercial cell phone network to the CEO of Vodafone.
519. The first mobile phone with Internet connectivity was the Nokia 9000 Communicator, launched in Finland in 1996.
520. The viability of Internet services access on mobile phones was limited until prices came down from that model, and network providers started to develop systems and services conveniently accessible on phones.
521. NTT DoCoMo in Japan launched the first mobile Internet service, i-mode, in 1999 and this is considered the birth of the mobile phone Internet services.
522. In 2001, the mobile phone email system by Research in Motion (now BlackBerry Limited) for their BlackBerry product was launched in America.
523. To make efficient use of the small screen and tiny keypad and one-handed operation typical of mobile phones, a specific document and networking model was created for mobile devices, the Wireless Application Protocol (WAP).
524. Most mobile device Internet services operate using WAP.
525. The growth of mobile phone services was initially a primarily Asian phenomenon with Japan, South Korea and Taiwan all soon finding the majority of their Internet users accessing resources by phone rather than by PC.
526. Developing countries followed, with India, South Africa, Kenya, the Philippines, and Pakistan all reporting that the majority of their domestic users accessed the Internet from a mobile phone rather than a PC.
527. The European and North American use of the Internet was influenced by a large installed base of personal computers, and the growth of mobile phone Internet access was more gradual, but had reached national penetration levels of 20–30% in most Western countries.
528. The cross-over occurred in 2008, when more Internet access devices were mobile phones than personal computers.
529. In many parts of the developing world, the ratio is as much as 10 mobile phone users to one PC user.

Growth in demand

530. Global Internet traffic continues to grow at a rapid rate, rising 23% from 2020 to 2021 when the number of active Internet users reached 4.66 billion people, representing half of the global population.
531. Further demand for data, and the capacity to satisfy this demand, are forecast to increase to 717 terabits per second in 2021.
532. This capacity stems from the optical amplification and WDM systems that are the common basis of virtually every metro, regional, national, international and submarine telecommunications networks.
533. These optical networking systems have been installed throughout the 5 billion kilometers of fiber optic lines deployed around the world.
534. Continued growth in traffic is expected for the foreseeable future from a combination of new users, increased mobile phone adoption, machine-to-machine connections, connected homes, 5G devices and the burgeoning requirement for cloud and Internet services such as Amazon, Facebook, Apple Music and YouTube.

Historiography

535. There are nearly insurmountable problems in supplying a historiography of the Internet's development.
536. The process of digitization represents a twofold challenge both for historiography in general and, in particular, for historical communication research.
537. A sense of the difficulty in documenting early developments that led to the internet can be gathered from the quote:
538. "The Arpanet period is somewhat well documented because the corporation in charge – BBN – left a physical record. Moving into the NSFNET era, it became an extraordinarily decentralized process. The record exists in people's basements, in closets. ... So much of what happened was done verbally and on the basis of individual trust."
539. — Doug Gale (2007)
540. Notable works on the subject include a book by journalists Katie Hafner and Matthew Lyon, Where Wizards Stay Up Late: The Origins Of The Internet (1996); and professor Janet Abbate's book Inventing the Internet (2000).
541. Most scholarship and literature on the Internet lists ARPANET as the prior network that was iterated on and studied to create it, although other early computer networks and experiments existed alongside or before ARPANET.
542. Such histories of the Internet have since been criticized as teleologies and Whig history; that is, they take the present to be the end point toward which history has been unfolding based on a single cause:
543. In the case of Internet history, the epoch-making event is usually said to be the demonstration of the 4-node ARPANET network in 1969. From that single happening the global Internet developed.
544. — Martin Campbell-Kelly, Daniel D. Garcia-Swartz
545. In addition to these characteristics, historians have cited methodological problems arising in their work:
546. "Internet history" ... tends to be too close to its sources. Many Internet pioneers are alive, active, and eager to shape the histories that describe their accomplishments. Many museums and historians are equally eager to interview the pioneers and to publicize their stories.
547. — Andrew L. Russell (2012)