The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] BerkNet
Date: Thu, 27 Nov 2014 09:38:20 -0500 (EST)	[thread overview]
Message-ID: <20141127143820.0BDFD18C0C7@mercury.lcs.mit.edu> (raw)

    > From: jnc at mercury.lcs.mit.edu (Noel Chiappa)

    > The replacement, the first Link-State routing algorithm, worked much,
    > much, better; but it still had minor issues
    >
    > damping fixed most of those too).

Oop, the editor 'ate' a line there (or, rather the editor's operator spaced
out :-): it should say "it still had minor issues, such as oscillation
between two equal-cost paths, with the traffic 'chasing itself' from path to
path; proper damping fixed most of those too".


    > I always give Dave Clark credit (what I call "Clark's Observation") for
    > the most powerful part of the replacement for the ARPAnet - aka the
    > idea of a network of network.

Not sure exactly what you're referring to here (the concept of an internet
as a collection of networks seems to have occurred to a number of people,
see the Internet Working Group notes from the early 70s).

    > Dave once quipped: "Why does a change at CMU have to affect MIT?"

Subnets (which first appeared at MIT, due to our, ah, fractured
infrastructure) again were an idea which occurred to a number of people all
at the same time; in part because MIT's CHAOSNET already had a collection of
subnets (the term may in fact come from CHAOSNET, I'd have to check) inside
MIT.

    > I've forgotten what we did at CMU at the time, but I remember the MIT
    > folk were not happy about it.

I used to know the answer to that, but I've forgotten what it was! I have this
bit set that CMU did something sui generis, not plain ARP sub-netting, but I
just can't remember the details! (Quick Google search...) Ah, I see, it's
described in RFC-917 - it's ARP sub-netting, but instead of the first-hop
router answering the ARP based on its subnet routing tables, it did something
where ARP requests were flooded across the entire network.

No wonder we disapproved! :-)


    > Thought, didn't you guys have the 3Mbit stuff like we did at CMU and
    > UCB first?

MIT, CMU and Stanford all got the 3Mbit Ethernet at about the same time, as
part of the same university donation scheme. (I don't recall UCB being part
of that - maybe they got it later?)

The donation included a couple of UNIBUS 3Mbit Ethernet cards (a hex card,
IIRC) the first 3MB connections at MIT were i) kludged into one of the MIT-AI
front-end 11's (I forget the details, but I know it just translated CHAOS
protocol packets into EFTP so they could print things on the Dover laser
printer), and ii) a total kludge I whipped up which could forward IP packets
back and forth between the 3M Ethernet, and the other MIT IP-speaking LANs.
(It was written in MACRO-11, and with N interfaces, it used hairy macro
expansions to create separate code for each of all 'N^2' possible forwarding
paths!) Dave Clark did the Alto TCP/IP implementation (which was used to
create a TFTP->EFTP translating spooler for IP access to the Dover).

I can give you the exact data, if you care, because Dave Clark and I had
a competition to see who could be done first, and the judge (Karen Sollins)
declared it a draw, and I still have the certificate! :-)

	Noel



             reply	other threads:[~2014-11-27 14:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27 14:38 Noel Chiappa [this message]
2014-11-29 16:34 ` Clem Cole
  -- strict thread matches above, loose matches on Subject: below --
2014-11-26 18:49 Noel Chiappa
2014-11-26 20:16 ` Clem Cole
2014-11-27 20:40   ` Dave Horsfall
2014-11-29 16:39     ` Clem Cole
2014-11-26 23:33 ` Jesus Cea
2014-11-21  5:46 [TUHS] 2.10 Clem Cole
2014-11-21  6:07 ` Cory Smelosky
2014-11-26  6:28   ` [TUHS] BerkNet Erik E. Fair
2014-11-26  6:48     ` Cory Smelosky
2014-11-27 16:42       ` Mary Ann Horton
2014-11-29 16:38         ` Clem Cole
2014-11-26 18:24     ` Clem Cole
2014-11-26 18:35       ` Dan Cross
2014-11-26 20:03         ` Clem Cole
2014-11-26 18:26     ` Dave Horsfall

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=20141127143820.0BDFD18C0C7@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).