4 ms·
Indeed! I was one of what I called "a cast of tens" in that effort, responsible for a MIT Math Department applied math computer lab, a long run to the south co
by hga 14y ago
Indeed! I was one of what I called "a cast of tens" in that effort, responsible for a MIT Math Department applied math computer lab, a long run to the south corner of Building 2. We didn't have significant problems with our cable, but I did hear of others, and there was the fun time "a backhoe tried to connect to the CHAOSnet" at Vassar Street, between the main campus and the AI Lab and LCS.
I still miss symbolically named ports (e.g. "TELNET") vs. IP's numbered ones (then again IP had to run on the ARPAnet's old routers and was explicitly a WAN and a very well designed one, CHAOSnet was a LAN which was something of a quick hack, like NFS).
- cpr 14y agoYes, I remember some backhoe incidents, perhaps the same ones. ;-) Funny, IP at the time seemed very clunky and verbose to those of us used to the concision of WANs like the pre-IP ARPAnet host-to-host protocols, and I remember the massive hair involved in the first DEC-20/TENEX implementations of TCP/IP. It took a while before people really understood TCP/IP enough to implement it well. (Some of the faster, smaller implementations first came out of Dave Clark's group at LCS, he being one of the designers of IP.)
- hga 14y agoClunky and verbose by comparison indeed, but at least it was to a purpose. I can remember the day/night? the ARPAnet turned off the old "NCP" protocol, and from MIT-Multics we were able to e.g. ping a machine in Norway. What's really impressive is how it's stood the test of time, albeit with critical implementation improvements like Van Jacobson's flow control (http://en.wikipedia.org/wiki/Van_Jacobson http://en.wikipedia.org/wiki/Van_Jacobson). But we did have to scramble for quite a while.