Hobbes' Internet Timeline
Another source of links to historic reading material: Hobbes' Internet Timeline
It is 50 years today since the first message was sent on the ARPANET, a precursor of the internet as we know it today. The Advanced Research Projects Agency Network (ARPANET) can trace its roots back to 1962 and MIT computer scientist Joseph Licklider's "Galactic Network" concept. Around the same time, Leonard Kleinrock, also …
Another source of links to historic reading material: Hobbes' Internet Timeline
Part of me deeply regrets being too young (and in entirely the wrong place) to see what was going on in the world of computing at this time, the construction and design of these vast systems that were sufficiently well designed so that even today they're still working* despite the enormously higher scale and volume that was envisaged at the time.
It must have been an amazing place watching the future get built in front of your eyes, greybeards.
*IPv4 still did a damn good job
No argument there, The amount of legwork IPv4 has done in the past 40ish years is absurd and the reason that it's ended up insufficient for the present only serves to highlight the sheer scale of what the internet has become, which I assume was quite literally unimaginable back when the system was designed.
I rather suspect that Gathercole would be a better read than any of those you list.
Mine is being written. I don't know if I'll be able to publish it in my lifetime ... my brother (a land-shark) says that I can probably get releases from the living, but the estates of the deceased might have issues in some cases.
Dr. Kleinrock was mentioned in the article, ICANN has just posted a blog written by him: The First Message Transmission
I recall talking to one of these pioneers after he gave a talk on ARPANet history, and getting a bit more info about that message. Yes, this is hearsay and an unreliable memory at work.
As he told it, the issue was that (at least) one of the nodes involved had concocted the network interface to the OS with a slightly modified serial-port driver. There was apparently some sort of race condition in that driver, that had never been noticed, because the window of vulnerability was so short that it could not be hit with a max data rate of 9600bps (or whatever), but when the network interface had inhaled and digested a whole packet and then hit it with a slug of characters in rapid succession, "Bad Things Happened" (tm)
Stuff like that (from mods not anticipated by the original coders) has always been with us. Finding and fixing it in just a few days impressed me.
And many younger people don't realise that the interfaces and actual connections in those days were all serial (no LANs, ethernets, token rings, etc) and (almost) all synchronous. (I am fairly sure about that last part -- there was certainly almost no async data comms at the time I started working on this in 1979).
And I would be surprised if it was any faster than 300bps.
The Hobbs timeline shows 56kbs in 1970. So I wonder what was used in 1969?
56kbs sounds like it could have been some sort of ISDN. Which when I used it, usually didn't give me the full 64 kbs it could have had but was always better than my 56kbs modem did. And I had a second line so could get double speed when big downloads started up.
But looking up ISDN, it looks like it came out in 1978.
Probably not cheaper, but most likely a long-term lease. In the 1970s through the mid '80s $TELCO sailsdroids were selling 20 and 30 and even 50 year leases on Switched56. I know one company in Silly Con Valley that still has almost 6 years left on a 50 year lease ... it "only" costs them about twelve hundred bucks a month. It is unused. I don't think they even own the necessary termination equipment anymore.
I know several other people who are locked into paying for low bandwidth ISDN. A couple are still paying for 2B+D; they got suckered into a "low cost" 30 year contract in early '90s and $TELCO won't let them off the hook ...
The IMPs communicated with each other but the interface between the IMPs and a local computer was a bit serial interface with a specification. Each client had to build their own interface to the IMP. This was the day when machines had all kinds of bit lengths (12, 15, 18, 20, 24, 36 etc.) and the ARPANET protocol was designed to line up words if the communicating machines were of the same word length and all of the bits were preserved if they were not.
I do not, in any way, want to minimise the contribution, genius and insights of the Arpanet pioneers, but we shouldn't forget that there were soon several competing computer network technologies being created at around the same time. Major corporate players like IBM and DEC and the PTTs (through CCITT) were working on different packet switched data communications networks through the 1970's.
These eventually lost out to (the evolution of) the Arpanet protocols, that we now call TCP/IP, although parts of those were adopted into it (such as Ethernet, IP V6 addressing, IS-IS Routing).
In the late 1990s DECnet inter-networks were as big as IP inter-networks. I had DECnet on Macs as well as microVAXes and Ultrix workstations, it was widespread and pretty easy to use.
If DEC had not crashed and burned it could have been a very different world.
When I was in Cambridge in the early 80's, everyone was talking about the Cambridge Ring
The ARPANET itself was finally decommissioned in 1990.
All Astute Military Presences would have ARPANET recommissioned rather than decommissioned, methinks.
I suppose that takes All into Skunkworks Territory on Virtual Terrain with Real Spooky Surreal IntelAIgent Stuff Freely Available to Present and Entertain All with CHAOS ..... Clouds Hosting Advanced Operating Systems.
Or do you disagree and deny yourself the perfect opportunity to exclaim your objection and articulate the evidence for the reasoning? Surely such halts Progress at every stop/disagreement, which is not at all accommodating whenever reasons are unknown.
But amfm, ARPANET was wrapped up because the .mil never really used it. They have their own command and control infrastructure outside the global TCP/IP network. Shirley a martian of your learned background and ability knows this?
But amfm, ARPANET was wrapped up because the .mil never really used it. They have their own command and control infrastructure outside the global TCP/IP network. Shirley a martian of your learned background and ability knows this? ... jake
Howdy, jake,
Sounds to me very much like their own command and control infrastructure outside the global TCP/IP network is an ARPANET recommissioned.
Such has constantly proven itself thoroughly incapable of global infrastructure command and control though ......... so a monumental program/project fail.
That old ignorant saw again?
Al Gore actually did push the Bill through Congress that liberated NSFnet to commercial use, thus allowing our ignorant commentardary here on ElReg. Please, look it up before regurgitating crap. And I don't even like Al Gore!
HTH, HAND.