From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] BerkNet
Date: Wed, 26 Nov 2014 15:16:10 -0500 [thread overview]
Message-ID: <CAC20D2M905DtMdmZqs05juhvUJ00PAjRvsFa9E-yTbdyo=qP6Q@mail.gmail.com> (raw)
In-Reply-To: <20141126184945.CA2A418C0B7@mercury.lcs.mit.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3068 bytes --]
below.
On Wed, Nov 26, 2014 at 1:49 PM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:
> > From: Clem Cole
>
> A few comments on aspects I know something of:
>
>
> > BTW: the Arpanet was not much better at the time
>
> The people at BBN might disagree with you... :-)
>
Fair enough...
>
> But seriously, throughout its life, the ARPANET had 'load-dependent
> routing',
> i.e. paths were adjusted not just in response to links going up or down,
> but
> depending on load (so that traffic would avoid loaded links).
>
> The first attempt at this (basically a Destination-Vector algorithm, i.e.
> like
> RIP but with non-static per-hop costs) didn't work too well, for reasons I
> won't get into unless anyone cares. The replacement, the first Link-State
> routing algorithm, worked much, much, better; but it still had minor issues
>
> damping fixed most of those too).
>
You're right of course. I was referring more to the fact that changes
tended to be an issue.
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. Dave once quipped: "Why does a change at CMU have to
affect MIT?" I've forgotten what we did at CMU at the time, but I remember
the MIT folk were not happy about it.
>
>
> > DH11's which were a full "system unit"
>
> Actually, two; they were double (9-slot, I guess?) backplanes.
>
Right.
>
>
> > The MIT guys did ARP for ChaosNet which quickly migrated down the
> street
> > to BBN for the 4.1 IP stack.
>
> Actually, ARP was jointly designed by David Plummer and I for use on both
> TCP/IP and CHAOS (which is why it has that whole multi-protocol thing
> going);
> we added the multi-hardware thing because, well, we'd gone half-way to
> making
> it totally general by adding multi-protocol support, so why stop there?
>
Thanks, I never knew that. Makes sense.
>
> As soon as it was done it was used on a variety of IP-speaking MIT machines
> that were connected to a 10MBit Ethernet; I don't recall them all, but one
> kind was the MIT C Gateway multi-protocol routers.
>
Thought, didn't you guys have the 3Mbit stuff like we did at CMU and UCB
first?
>
>
> > Hey it worked just fine at the time.
>
> For some definition of 'work'! (Memories of wrapping protocol A inside
> protocol B, because some intervening router/link didn't support protocol A,
> only B...)
Hey when we did it, we were trying to a UNIX machine to talk to CDC Cyber
and an VMS/VAX. No routers. We were happy to just have those systems
communicating ;-)
I was not smart enough to see something like ARP - which later seemed like
such a D'oh moment.
Then again -- at the time 48 bits of Ethernet was supposed to me "enough"
and you were not going to need anything else. Funny how it all worked out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20141126/e37468b1/attachment.html>
next prev parent reply other threads:[~2014-11-26 20:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 18:49 Noel Chiappa
2014-11-26 20:16 ` Clem Cole [this message]
2014-11-27 20:40 ` Dave Horsfall
2014-11-29 16:39 ` Clem Cole
2014-11-26 23:33 ` Jesus Cea
-- strict thread matches above, loose matches on Subject: below --
2014-11-27 14:38 Noel Chiappa
2014-11-29 16:34 ` Clem Cole
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='CAC20D2M905DtMdmZqs05juhvUJ00PAjRvsFa9E-yTbdyo=qP6Q@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).