IETF Logo Mail Archive

NHRP v6 - hardware type / address type

Dave Katz <dkatz@cisco.com> Thu, 30 November 1995 06:44 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07745; 30 Nov 95 1:44 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa07741; 30 Nov 95 1:44 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 BAA00433; Thu, 30 Nov 1995 01:13:07 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id BAA09944 for rolc-out; Thu, 30 Nov 1995 01:26:48 -0500
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id BAA09935; Thu, 30 Nov 1995 01:26:45 -0500
Received: from puli.cisco.com (puli.cisco.com [171.69.1.174]) by nexen.nexen.com (8.6.12/8.6.12) with ESMTP id BAA04548; Thu, 30 Nov 1995 01:26:40 -0500
Received: (dkatz@localhost) by puli.cisco.com (8.6.8+c/8.6.5) id WAA08832; Wed, 29 Nov 1995 22:23:38 -0800
Date: Wed, 29 Nov 1995 22:23:38 -0800
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Dave Katz <dkatz@cisco.com>
Message-Id: <199511300623.WAA08832@puli.cisco.com>
To: gja@thumper.bellcore.com
Cc: bcole@cisco.com, gja@thumper.bellcore.com, rolc@nexen.com, luciani@nexen.com
In-Reply-To: Grenville Armitage's message of Wed, 29 Nov 1995 16:04:42 -0500 <199511292104.QAA09958@thumper.bellcore.com>
Subject: NHRP v6 - hardware type / address type
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/ If multiple codepoints (regardless of the number space) are allowed, you've answered your own first implied problem above. If we find a media that has 3, or 4, or 5 address types then you define ar$hrd codepoints for each address type of the same media. (But as a reality check, can you name any current examples, or good reasons why such a situation would arise in the future that NHRP would be relevant to?)

So what you're suggesting is semantically equivalent to just using address
families, with the unfortunate side effect of precluding the use of the
same address type over different media types.

I ask again, why should anyone care about the media type?  We're mapping
subnetwork addresses to network addresses.  It has nothing to do with
media types.

v2.8.7 | Report a Bug | By Email