The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Unix NCP protocol stack for ARPANET
Date: Sun, 24 Oct 2021 13:24:34 -0400	[thread overview]
Message-ID: <CAC20D2P5vtw2FPiWNLz9TjD1k4aooJS=BkPW4Ke7rC_Oj3HatA@mail.gmail.com> (raw)
In-Reply-To: <7wtuh6e6u6.fsf@junk.nocrew.org>

[-- Attachment #1: Type: text/plain, Size: 2133 bytes --]

On Sun, Oct 24, 2021 at 12:57 PM Lars Brinkhoff <lars@nocrew.org> wrote:

> Has any other NCP implementation for Unix survived?  From old host
> tables I think there may have been some VAXen online before the switch
> to TCP/IP.
>
Hmmm... I find that interesting because  Stan Smith and I wrote the
original IP/TCP for the VAX in 1979/1980 when we were at Tektronix(in
BLISS-32, BTW -- which I gave back to CMU, and CMU added mailer and
eventual DNS support, and then distributed it as the Tek-CMU TCP/IP - DEC
eventually used it to start their in-house effort - I have that code on
9-track and may have it on a CD somewhere).   When Stan and I started that
work, I had looked everywhere I could think to find an NCP implementation,
and never found one.   Our Vax was connected to the Teklabs 11/70 running
V7 and the 3Com UNET stack that Bruce Bordan and crew wrote.

The reason was that IMP's ports were a rare commodity and free ones almost
non-existent.  So when Vaxen started to roll out, the IMPs were
usually filed with PDP-10s at the research sites.   Vaxen also tended to
have Xerox 3M Ethernet boards.  I also don't know of anyone connecting a
DR-11B to an 1822 for a Vax - could have been done, but I don't know of
one.   At both CMU and UCB, we used Xerox boards until the real ones from
3Com, Interlan and DEC showed up and that was not until 1981-82 and the IP
transition has already begun.

You tell me, but I was under the impression, that you folks at MIT did a
ChaosNet interface, IIRC, so there may have been some sort of conversion on
your LAN, but I really doubt there was a real NCP running.

FYI: CMU had Vax serial #1, and it was never on the ARPAnet.  It was in the
same machine room as the IBM 360s, PDP-20s, and Univac 1108, not the CS
PDP-10s where the IMP was.

My guess is that people had Vaxen assigned in the host tables, but never
connected for lack of an NCP implementation.  And until the Tek stack for
VMS and the BBN stack for 4.1 BSD, I don't think there were any Vaxen yet
on either the NCP based ARPAnet much less the later IP-based one.

Clem
ᐧ
ᐧ

[-- Attachment #2: Type: text/html, Size: 4534 bytes --]

  reply	other threads:[~2021-10-24 17:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24 16:16 Lars Brinkhoff
2021-10-24 17:24 ` Clem Cole [this message]
2021-10-24 18:32   ` Ron Natalie
2021-10-24 19:28     ` Clem Cole
2021-10-24 19:28     ` Warner Losh
2021-10-24 20:25       ` Clem Cole
2021-10-25  9:26   ` Lars Brinkhoff
2021-10-25 16:50 Paul Ruizendaal
2021-10-25 19:04 ` Lars Brinkhoff
2021-10-25 18:50 Noel Chiappa
2021-10-28  9:41 ` Lars Brinkhoff
2021-10-26  8:06 Paul Ruizendaal

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='CAC20D2P5vtw2FPiWNLz9TjD1k4aooJS=BkPW4Ke7rC_Oj3HatA@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=lars@nocrew.org \
    --cc=tuhs@tuhs.org \
    --subject='Re: [TUHS] Unix NCP protocol stack for ARPANET' \
    /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

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).