Computer Old Farts Forum
 help / color / mirror / Atom feed
From: jnc at mercury.lcs.mit.edu (Noel Chiappa)
Subject: [COFF] ARPAnet now 4 nodes
Date: Fri,  6 Dec 2019 12:33:38 -0500 (EST)	[thread overview]
Message-ID: <20191206173338.2BB0218C07E@mercury.lcs.mit.edu> (raw)

    > From: Lars Brinkhoff

    >> PARC's MAXC appears in the mid-1970s.

    > Maybe this is a good time to ask if anyone knows whether any of those
    > diverse systems has software preserved? Specifically, the
    > implementation of the NCP and 1822 Host-to-IMP protocols?

Both MAXC's were PDP-10 re-implementations, and ran TENEX. So the basic
system is still around, not sure if they had any interesting local hacks
(well, probably PUP support; MIT tried to put it in MIT-XX, so it may
still exist on thats backup tapes).


    > From: Rob Gingell gingell at computer.org 

    > A collection of maps of the ARPAnet over time is available from the 
    > Computer History Museum

Interesting; I also have a large collection of maps:

  http://mercury.lcs.mit.edu/~jnc/tech/arpanet.html#Maps

all with hi-res versions (click on the thumbnails). Some of the ones
at the CHM I don't have, but the coverage time-wise is similar.

I also have a modest collection of hosts.txt files, ranging from 
Jul-77 to Apr-94.

    > I've forgotten at this point whether the assignments were documented in
    > RFCs or other assigned numbers documents from the Network Information Center

The first 'Assigned numbers' RFC was #739, from November 1977. It never
contained host addresses. There were a very few early RFC's which contained
host adresses (#226, #229, #236), but pretty quickly host addresses were done
via the hosts.txt file, distributed from the NIC. (Given the churn rate, using
RFC's didn't make sense.) Early RFCs about this are #606 and #627.  There were
a bunch of RFC's that reported on 'host status' (e.g. how their software was
doing), but their goal was different.


PS: A number of people are leaving out the definite article before 'ARPANET';
this seems to be popular these days (especially in the UK it seems, not sure
why), but it is incorrect. 

Also, the correct spelling is all capitals (check e.g. through old RFCs).
Until of course the AP gets their hands on it (I'm breathlessly awaiting
their announcement that the U.S. President's reference is to be referred
to as the 'white house').

	Noel


             reply	other threads:[~2019-12-06 17:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 17:33 jnc [this message]
2019-12-06 18:02 ` lm
2019-12-06 19:38 ` lars
2019-12-09  1:09 ` stewart
  -- strict thread matches above, loose matches on Subject: below --
2021-12-04 20:29 Dave Horsfall
2020-12-10  8:12 rudi.j.blom
2020-12-05 23:14 jnc
2020-12-09  2:41 ` dave
2020-12-04 21:05 dave
2019-12-05  0:08 dave
2019-12-05  4:19 ` lm
2019-12-05  8:01   ` lars
2019-12-05 12:37     ` clemc
2019-12-05 18:20   ` gingell
2019-12-05 18:33     ` lars
2019-12-05 19:05     ` lm
2019-12-05 20:41       ` gingell
2019-12-06  1:19         ` amp1ron
2019-12-06  3:25           ` gingell
2019-12-06  4:19             ` amp1ron
2019-12-06  4:43               ` amp1ron

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=20191206173338.2BB0218C07E@mercury.lcs.mit.edu \
    --to=coff@minnie.tuhs.org \
    /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).