Re: NHRP v6 - hardware type / address type
Grenville Armitage <gja@thumper.bellcore.com> Wed, 29 November 1995 22:24 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa29805;
29 Nov 95 17:24 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa29801;
29 Nov 95 17:24 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.98.5]) by
guelah.nexen.com (8.6.12/8.6.12) with ESMTP id QAA27490;
Wed, 29 Nov 1995 16:51:43 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
RAA06152 for rolc-out; Wed, 29 Nov 1995 17:03:27 -0500
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by
maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id RAA06143 for
<rolc@nexen.com>; Wed, 29 Nov 1995 17:03:24 -0500
Received: from thumper.bellcore.com (thumper.bellcore.com [128.96.41.1]) by
guelah.nexen.com (8.6.12/8.6.12) with ESMTP id QAA27365 for <rolc@nexen.com>;
Wed, 29 Nov 1995 16:48:52 -0500
Received: from thumper (localhost [127.0.0.1]) by thumper.bellcore.com
(8.6.9/8.6.10) with ESMTP id RAA14118; Wed, 29 Nov 1995 17:00:33 -0500
Message-Id: <199511292200.RAA14118@thumper.bellcore.com>
To: Paul Koning 1695 <pkoning@chipcom.com>
cc: Rolc mailing list <rolc@nexen.com>, gja@thumper.bellcore.com
Subject: Re: NHRP v6 - hardware type / address type
In-reply-to: Your message of Wed, 29 Nov 1995 16:30:00 -0800.
<30BCFC34@mailer2>
Date: Wed, 29 Nov 1995 17:00:31 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Grenville Armitage <gja@thumper.bellcore.com>
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via
ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/
Paul, [..] >>The reason media information should be lacking is to make it impossible >>for people to commit the mistake that's in your earlier note! >> >>"...identifies the media type, which also identifies the address type..." >>That simply is not true. And that is the experience Dave and I were >>referring to. >> >>Would you give Ethernet and FDDI different media types? Yup. >>If yes, note >>that they use the same address type, so your equating of media type >>and address type is not valid. If no, then what does "media type" mean? This is silly reasoning, and is not what I wrote. The quote from me above means: ar$hrd = X, media is Ethernet, address is 48 bit MAC. ar$hrd = Y, media is FDDI, address is 48 bit MAC. (and of course) ar$hrd = Z, media is ATM, address is either E.164 or NSAPA. What's wrong there? I never said that a different ar$hrd value has to mean a different address type from any other ar$hrd value. I dont know why anyone in their right minds would assume it had to. Your whole concern is predicated on an assumption that has no good reason for being made. So it was made in the early days of ARP. So it was dumb. Do you think no body has learned, or that we cant stick clarificatory text in the IANA numbers document? gja
- RE: NHRP v6 - hardware type / address type Paul Koning 1695
- RE: NHRP v6 - hardware type / address type Paul Koning 1695
- RE: NHRP v6 - hardware type / address type Paul Koning 1695
- Re: NHRP v6 - hardware type / address type Grenville Armitage
- Re: NHRP v6 - hardware type / address type Grenville Armitage
- NHRP v6 - hardware type / address type Dave Katz