Systems Approach Next week I am heading to Edinburgh University, where I did my PhD back in the 1980s, to give a lecture as part of the events celebrating 60 years of Computer Science and Artificial Intelligence at Edinburgh.

Having decided that I would [1]speak about networking (stick to what you know, after all), I realized that there was a lot going on in the networking world 60 years ago too, making for a nice tie-in to the event. My research for the talk inspired me to write this article.

I’m sure I will be hearing from readers if I make any claims here (or in my talk) that can’t be backed up – some of the stories here are hard to verify, but there are some good primary sources cited in the following post.

In the beginning

Most people with some knowledge of networking history can name a few famous people from its history, such as the inventors of TCP/IP (Bob Kahn and Vint Cerf) and of the World Wide Web (Sir Tim Berners-Lee). While TCP/IP dates back to the early 1970s, and the Web to the 1990s, I wanted to go back further to cover the 60-year period being celebrated at Edinburgh.

I found a wonderful resource in “A Brief History of the Internet”

[2]PDF

by Barry Leiner et al (with co-authors including Kahn and Cerf among a long list of famous names). One of the striking things about that paper is just how many people were involved in the creation of the internet. Fortuitously, Leiner et al trace the internet’s roots back to the early 1960s, lining up nicely with the timeframe I wanted to cover, and highlighting a number of developments I was unfamiliar with. I’ve leaned heavily on that paper for my talk.

[3]

First up is the invention of packet switching. It’s worth noting that the dominant network in the 1960s was the telephone network, which dealt in circuits. A small group of computer scientists recognized that there might be a form of networking that was better suited to computer communication.

[4]

[5]

Len Kleinrock wrote a report on the queuing theory behind packet switching (without using the term packet) in 1961 (and later wrote books that were part of my education). Over the next few years Paul Baran in America and Donald Davies in the UK independently developed the main concepts of packet switching – they are generally recognized as packet switching’s co–inventors. Davies gets the nod for having coined the term “packet” to describe a bundle of bits packaged for transmission.

Arguably just as important was the work of J.C.R. Licklider, who seems to have been an amazing visionary across wide areas of computing. He proposed the idea of an “Intergalactic Computer Network” around the time he joined ARPA in 1962. These ideas took hold with Larry Roberts, who was appointed as the first program manager for ARPANET.

[6]

The ideas of Kleinrock, Davies and Baran were adopted in the ARPANET design, with the “Interface Message Processors (IMPs)” being the first routers and ARPANET the first wide-area packet-switched network. Prior to this, Roberts apparently built a long-haul connection between two computers on opposite sides of the United States using a telephone circuit, illustrating by counterexample that packet switching really was the way to go. Leiner calls this the first wide-area computer network.

[7]ARPANET pioneer Jack Haverty says the internet was never finished

[8]Turing Award goes to Robert Metcalfe, co-inventor of the Ethernet

[9]Packet pioneer Larry Roberts dies at 81

[10]How the internet as we know it was born

While the ARPANET is generally viewed as the predecessor of the internet, what surprised me is how quickly the ideas of the internet came together once the ARPANET existed.

The first ARPANET hosts were connected in 1969, and as early as 1972 Bob Kahn was working on the ideas of “internetting”: connecting different networks together. There weren’t a lot of networks to connect, but packet radio was developed around the same time, so the idea that very different networks could be connected arose quite early.

Realizing that the protocols that he was creating to support internetting were going to need to be implemented on various operating systems, Kahn teamed up with Vint Cerf, who had experience with the implementation of NCP (which can be viewed as the predecessor of TCP/IP) on ARPANET. The idea that TCP/IP had to support heterogeneous networks was another big departure from the networks of the past–telephone networks were much more homogeneous.

Much more than just TCP and IP

My favorite paper on how the internet developed is the 1988 paper

[11]PDF

by David Clark: The Design Philosophy of the DARPA Internet Protocols. With the benefit of 15 years of experience, Clark – often referred to as The Architect of the Internet – clearly lays out what he, Kahn, Cerf, and many others were trying to achieve when the internet was designed.

There was a lot more to the internet than the TCP and IP protocols, and Clark lays out a detailed list of design goals, all in service of one top-level goal: to interconnect existing networks. That meant, importantly, that you couldn’t impose changes on the existing networks to make them “fit” the internet architecture: the internet had to be able to accommodate widely varying types of networks, eg: those with no reliable delivery mechanisms or ability to provide notifications of failures.

The ability to accommodate networks in spite of wide variations among their capabilities, including networks not yet invented, was quite a radical idea, and drove a lot of critical design decisions, such as the adoption of a best-effort service model.

[12]

The list of second-order design goals starts with:

Internet communication must continue despite loss of networks or gateways.

I feel obligated to point out that there is no mention in this paper of the internet being designed to withstand nuclear attack. Unfortunately, I was responsible for perpetuating that misconception in an early edition of Computer Networks: A Systems Approach . Leiner et al debunk this myth and explain its origins in their paper, but it’s a remarkably persistent one. “[C]ontinue despite loss of networks or gateways” is as close as it gets.

Of the other design goals, the one that I keep coming back to is “distributed management of resources.” I’m personally very interested in the many ways in which the decentralized architecture of the internet has been eroding, and have written about this topic [13]here and [14]here .

As far back as 2016 I began to take an interest in blockchains as a possible path to a more decentralized approach, but these days I mostly find myself agreeing with Molly White and her ironic [15]Web3 is Going Just Great site, which catalogs the steady stream of Web3 failures and grifts. Fortunately, there is more to the decentralization of the internet than blockchains and Web3.

There is no mention in this paper of the internet being designed to withstand nuclear attack

As we [16]discussed last year , there are real signs of life for the decentralization of social media thanks to the emergence of [17]ActivityPub and the Fediverse. Just as I was putting finishing touches on my slide deck, there was yet another meltdown in the world of centralized platforms, with the CEO of Reddit [18]deciding that sudden changes to API pricing – to the point that lots of third-party applications become economically unsustainable – was such a good idea at Twitter that he would bring the same approach to Reddit.

The [19]response from volunteer moderators at Reddit – the unpaid community members who make the platform valuable to users – has been swift and, in some cases, hilarious. But the aspect of this story that really caught my eye was the rapid rise of ActivityPub-powered Reddit alternatives [20]Kbin and [21]Lemmy .

The future

The number of users of these services, which are interoperable with each other and connect to the rest of the Fediverse, has roughly tripled in a week (off a low base). Furthermore, there is a flurry of activity to beef up the implementations so that moderation tools – an essential part of any social media platform – can keep up with the growth in users.

As an active user of another part of the Fediverse, [22]Mastodon , I can tell you that there is lots of discussion among Fediverse users at present around how best to deal with all this growth and what it would take to scale the Fediverse up to the size of the big centralized platforms (which are still orders of magnitude larger than the Fediverse).

It’s really too early to tell how this will all play out, and there is certainly more to the internet than social media platforms, but I do feel a degree of optimism that the pendulum is swinging back towards the decentralized approaches that enabled the internet to grow and flourish over the last sixty years. ®

Larry Peterson and Bruce Davie are the authors of [23]Computer Networks: A Systems Approach and the related [24]Systems Approach series of books. All their content is open source and available on [25]GitHub . You can find them on [26]Mastodon , their writings on [27]Substack , and past The Register columns [28]here .

Get our [29]Tech Resources



[1] https://www.ed.ac.uk/informatics/60-years-of-computer-science-and-ai/60-years-of-computer-science-and-ai-events/academic-and-industry/distinguished-lecture-bruce-davie

[2] https://groups.csail.mit.edu/ana/A%20brief%20history%20of%20the%20internet%20-%20p22-leiner.pdf

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/networks&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZJytftjLf8oFKjHHFkKytQAAAUY&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/networks&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZJytftjLf8oFKjHHFkKytQAAAUY&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/networks&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZJytftjLf8oFKjHHFkKytQAAAUY&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/networks&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZJytftjLf8oFKjHHFkKytQAAAUY&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[7] https://www.theregister.com/2022/03/01/the_internet_is_so_hard/

[8] https://www.theregister.com/2023/03/23/turing_award_goes_to_robert/

[9] https://www.theregister.com/2019/01/02/arpanet_larry_roberts_dies_aged_81/

[10] https://www.theregister.com/2013/01/03/operational_internet_anniversary/

[11] http://ccr.sigcomm.org/archive/1995/jan95/ccr-9501-clark.pdf

[12] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/networks&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZJytftjLf8oFKjHHFkKytQAAAUY&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[13] https://www.theregister.com/2021/08/11/decentralized_internet/

[14] https://systemsapproach.substack.com/p/what-can-we-learn-from-internet-outages

[15] https://web3isgoinggreat.com/about

[16] https://www.theregister.com/2023/01/01/mastodon_activitypub/

[17] https://www.w3.org/TR/activitypub/

[18] https://www.theregister.com/2023/06/05/reddit_blackout_planned_over_appkilling/

[19] https://www.theregister.com/2023/06/12/reddit_api_outage/

[20] https://github.com/ernestwisniewski/kbin

[21] https://join-lemmy.org/

[22] https://aus.social/@Drbruced

[23] https://book.systemsapproach.org/

[24] https://www.systemsapproach.org/

[25] https://github.com/SystemsApproach

[26] https://discuss.systems/@SystemsAppr

[27] https://systemsapproach.substack.com/

[28] https://www.theregister.com/Tag/Systems%20Approach

[29] https://whitepapers.theregister.com/