From: Clem Cole <clemc@ccc.com>
To: Bakul Shah <bakul@bitblocks.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] OSI stack (Was: Posters)
Date: Mon, 4 Feb 2019 16:34:16 -0500 [thread overview]
Message-ID: <CAC20D2PEQRMo1axEXpu7FAw1M9nUTPNHR7XrhXZN+zdhNLx9gg@mail.gmail.com> (raw)
In-Reply-To: <2CFCAF1D-9EEC-43EB-AEC5-D58C30C5D923@bitblocks.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
On Mon, Feb 4, 2019 at 4:23 PM Bakul Shah <bakul@bitblocks.com> wrote:
> On Feb 4, 2019, at 12:29 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
> >
> >> From: Grant Taylor
> >
> >> I'm not quite sure what you mean by naming a node vs network interface.
> >
> > Does one name (in the generic high-level sense of the term 'name'; e.g.
> an
> > 'address' is a name for a unit of main memory) apply to the node (host)
> no
> > matter how many interfaces it has, or where it is/moves in the network?
> If so,
> > that name names the node. If not...
>
> Xerox Network System (XNS) also had this property. A node had a
> unique 48 bit address and each network had a unique 32 bit address.
> Absolute host numbering meant you could move a host to another
> network easily. IDP packet layout
>
Yeah, at the time, MetCalfe had the advantage of seeing what NCP and IP had
already learned. We used to say in hindsight, Ethernet had too many
address bits and IP not enough. So Noel and team invented ARP ;-)
Clem
ᐧ
[-- Attachment #2: Type: text/html, Size: 2089 bytes --]
next prev parent reply other threads:[~2019-02-04 21:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 20:29 Noel Chiappa
2019-02-04 21:13 ` Bakul Shah
2019-02-04 21:34 ` Clem Cole [this message]
2019-02-05 18:01 ` Grant Taylor via TUHS
2019-02-05 22:14 ` [TUHS] IP weak/strong host model (was Re: OSI stack (Was: Posters)) Derek Fawcus
-- strict thread matches above, loose matches on Subject: below --
2019-02-07 19:04 [TUHS] OSI stack (Was: Posters) Noel Chiappa
2019-02-07 1:03 Noel Chiappa
2019-02-07 0:45 Noel Chiappa
2019-02-07 0:02 Noel Chiappa
2019-02-07 0:11 ` Kevin Bowling
2019-02-06 23:18 Noel Chiappa
2019-02-06 23:40 ` Kevin Bowling
2019-02-06 23:52 ` Larry McVoy
2019-02-07 0:04 ` Kevin Bowling
2019-02-06 17:49 Noel Chiappa
2019-02-06 18:22 ` Paul Winalski
2019-02-06 20:47 ` Kevin Bowling
2019-02-07 18:07 ` Grant Taylor via TUHS
2019-02-07 18:22 ` Andy Kosela
2019-02-07 18:50 ` Larry McVoy
2019-02-03 18:49 Norman Wilson
2019-02-03 15:02 Noel Chiappa
2019-02-03 16:51 ` Grant Taylor via TUHS
[not found] ` <CANCZdfq5PM9jFEi9=geC+CTnveXs5CprN7b+ku+s+FYzw1yQBw@mail.gmail.com>
2019-02-06 17:16 ` Warner Losh
2019-02-06 17:23 ` Larry McVoy
2019-02-06 23:37 ` George Michaelson
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=CAC20D2PEQRMo1axEXpu7FAw1M9nUTPNHR7XrhXZN+zdhNLx9gg@mail.gmail.com \
--to=clemc@ccc.com \
--cc=bakul@bitblocks.com \
--cc=tuhs@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).