DistOS 2014W Lecture 3

Questions to consider:

• What were the purposes envisioned for computer networks? How do those compare with the uses they are put to today?
• What sort of resources were shared? What resources are shared today?
• What network architecture did they envision? Do we still have the same architecture?
• What surprised you about this paper?
• What was unclear?

Group 1

• video was mostly a summary of Kahn's paper
• process migration through different zones of air traffic control
• "distributed OS" meant something different than we normally think about, because many people would log in remotely to a single machine, it is very much like cloud infrastructure that we talk about today
• alto paper makes reference to Kahn's paper, and the alto designers had the foresight to see that networks like arpanet would be necessary
• would it be useful to have a co-processor responsible for maintaining shared resources even today? Like the IMPs of the arpanet? Today, computers are usually so fast it doesn't really matter.

Questions

• What were the purposes envisioned for computer networks?
  • big computation, storage, resource sharing - "having a library on a hard disk"

• How do those compare with the uses they are put to today?
  • those things are being done, but mostly communication like instant messaging, email

• What sort of resources were shared?
  • databases, CPU time

• What resources are shared today?
  • mostly storage

• What network architecture did they envision?
  • they had a checksum and acknowledge on each packet
  • the IMPs were the network interface and the routers
  • packet-switching

• Do we still have the same architecture?
  • packet-switching definitely won
  • no, now IP doesn't checksum or acknowledge, but TCP has end-to-end checksum and acknowledge
  • Kahn went on to learn from the errors of arpanet to design TCP/IP
  • the job of network interface and router have been decoupled

• What surprised you about this paper?
  • everything
  • how they were able to do this
  • a network interface card and router was the size of a fridge
  • high-level languages
  • bootstrap protocol, bootstrapping an application
  • primitive computers
  • desktop publishing
  • the logistics of running a cable from one university to another

• What was unclear?
  • much of the more technical specifications, but we mostly skipped over those

Group 4

    What were the purposes envisioned for computer networks? How do those compare with the uses they are put to today?

remote access to machines that have the resources users need: large databases, computing power, instruction set/non-portable software

Today, we use networks mostly for sharing data, although with services like Amazon AWS, we're starting to share computing resources again. We're also moving to support collaboration (e.g. Google Docs, GitHub, etc.).

   What sort of resources were shared? What resources are shared today?

Computing power was the key resource being shared; today, it's access to data. (See above.)

   What network architecture did they envision? Do we still have the same architecture?

Surprisingly, yes: modern networks have substantially similar architecures to the ones described in these papers. Packet-switched networks are now ubiquitous. We no longer bother with circuit-switching even for telephony, in contrast to the assumption that non-network data would continue to use the circuit-switched common-carrier network.

   What surprised you about this paper?

We were surprised by the accuracy of the predictions given how early the paper was written.

mouse in alto, resolution, bus speed: we have networks faster than their integrated buses

   What was unclear? 

Nothing significant; we're looking at these with the benefit of hindsight.