The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: <ron@ronnatalie.com>
To: "'The Eunuchs Hysterical Society'" <tuhs@tuhs.org>
Subject: Re: [TUHS] ARPAnrt, and the Unix epoch
Date: Thu, 3 Jan 2019 10:52:31 -0500	[thread overview]
Message-ID: <051901d4a37c$56a6ef40$03f4cdc0$@ronnatalie.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.1901011435110.79986@aneurin.horsfall.org>

Yes, it was a string of changes the network did on January 1.   A few years
earlier (1980?) they switched to long leaders on the IMPs on Jan 1.
This Jan 1 cutover meant that Mike Muuss and his staff (including me) at BRL
always had work to do over the holidays.
	
Shutting off NCP support was easy.   All NCP control messages traveled on
the IMP link 0.  IP traveled on link 155.

The IMPs were a gentle test for IP.   The virtual circuits were reliable and
flowed controlled even if the early TCPs were ornery.   A good IP
implementation did try to deal with the RFNM throttling.
The only real issue is the MTU mismatch between Ethernet and the IMP (1008
vs. 1500).

A while later, I noticed that the BRL Gateway (an early IP router) was
printing out messages that it was receiving link 0 messages.    Someone had
unblocked link 0, and there was some site out there was still some NCP host
trying to contact us (we had moved all our actual hosts OFF the outside imps
in favor of a pair of BRL Gateways).   Our interior network at that point
also comprised a handful of our own class B addressed IMPs.   An amusing
story there was as they were delivered and uncrated by the BBN guys I was
running around connecting up the data trunks and plugging hosts into them.
I sent a message to our BBN contact and told them that I had done this and I
got a long message back explaining it was impossible.    I'm sure glad I
didn't know it was impossible when I did it.    Later on, Joe Pistritto
managed to get the NOC protocol spec out of someone, and we wrote our own
NOC for the private IMP network.

Still, when they finally split the Arpanet from the Milnet, we got them to
do it on the first of the Fiscal Year (October) which fit our time schedule
at the labs a lot better.    Amusingly, there was one small hitch with the
"MAILBRIDGE" gateways that connected the two networks.    Apparently, BBN
forgot that we had the only IP router that was connected to the MILNET
(other than the MAILBRIDGES) and they screwed up that routing.




      reply	other threads:[~2019-01-03 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-01  3:41 Dave Horsfall
2019-01-03 15:52 ` ron [this message]

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='051901d4a37c$56a6ef40$03f4cdc0$@ronnatalie.com' \
    --to=ron@ronnatalie.com \
    --cc=tuhs@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).