The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Happy birthday, Internet!
Date: Sat, 7 Apr 2018 11:21:10 -0400	[thread overview]
Message-ID: <CAC20D2OLd0axFg9sRj1ARMTiq9bdF3QrxxYSQm7DrPyam5MQcw@mail.gmail.com> (raw)
In-Reply-To: <CAMYpm84x2TUSoB4HC7O+=vtp2MkKHbC0ErwJjP9O08x=Bwfqqw@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]

On Sat, Apr 7, 2018 at 12:54 AM, Rudi Blom <rudi.j.blom at gmail.com> wrote:

> Just had a look at RFC-1, my first look ever. First thing I noticed is
> the enormous amount of abbreviations one is assumed to be able to
> instantly place :-)
>
> So looking up IMP for instance the wiki page gives me this funny titbit
>
> "When Massachusetts Senator Edward Kennedy learned of BBN's
> accomplishment in signing this million-dollar agreement, he sent a
> telegram congratulating the company for being contracted to build the
> "Interfaith Message Processor"."
> https://en.wikipedia.org/wiki/Interface_Message_Processor
>
​A small suggestion, instead of trying to piecemeal it together here; to
all if you have not yet read (but certainly to newer and maybe younger
readers of this list since I think this was late 1990s), please go find a
copy of Katie Hafner's: Where Wizards Stay Up Late: The Origins Of The
Internet <https://www.amazon.com/Where-Wizards-Stay-Up-Late/dp/0684832674> .
Many and more of these interesting facts can be found.

It's a great read and I can say, a large number of the parts I lived and
knew specifically about, pretty much follow the way I remembered it.  There
are things left out, and some other good stories not there [Dave Clark does
not get enough credit in my opinion or in the infamous milkshake spilled
into the CMU IMP].  But, the mail header wars are well handled.  And
certainly the road to the ARPAnet, then to the Internet itself is pretty
thoroughly examined.

Clem

ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180407/d7223dee/attachment-0001.html>


  reply	other threads:[~2018-04-07 15:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-07  4:54 Rudi Blom
2018-04-07 15:21 ` Clem Cole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-09 15:37 Noel Chiappa
2018-04-10 18:32 ` Clem Cole
2018-04-10 19:11 ` Clem Cole
2018-04-09 14:57 Noel Chiappa
2018-04-09 14:52 Noel Chiappa
2018-04-09 15:01 ` Erik E. Fair
2018-04-07 12:50 Noel Chiappa
2018-04-07 14:34 ` Steve Nickolas
2018-04-07 14:44   ` Clem Cole
2018-04-08 23:34   ` Dave Horsfall
2018-04-09  0:06     ` Clem Cole
2018-04-09  1:16       ` Kurt H Maier
2018-04-08 23:34 ` Dave Horsfall
2018-04-06 20:56 Dave Horsfall
2018-04-06 23:10 ` Nemo
2018-04-06 23:19   ` Dave Horsfall
2018-04-06 23:56   ` Kurt H Maier
2017-04-07  4:48 Dave Horsfall
2017-04-07  4:58 ` Warren Toomey
2017-04-07  5:13 ` Lars Brinkhoff
2017-04-07  6:57   ` Greg 'groggy' Lehey
2017-04-08  5:13     ` Dave Horsfall
2017-04-09  0:09       ` Greg 'groggy' Lehey
2017-04-09  2:42       ` Jason Stevens
2017-04-10  5:54   ` Dave Horsfall
2017-04-07 13:55 ` Nemo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAC20D2OLd0axFg9sRj1ARMTiq9bdF3QrxxYSQm7DrPyam5MQcw@mail.gmail.com \
    --to=clemc@ccc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).