IETF Logo Mail Archive

Re: ipv6nd-02.txt & autoconfig

Grenville Armitage <gja@bellcore.com> Mon, 13 May 1996 17:59 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa17492; 13 May 96 13:59 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa17488; 13 May 96 13:59 EDT
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa11083; 13 May 96 13:59 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by guelah.nexen.com (8.7.3/8.7.3) with ESMTP id NAA07683; Mon, 13 May 1996 13:58:59 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id NAA29555 for ip-atm-out; Mon, 13 May 1996 13:49:34 -0400 (EDT)
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.7.3/8.7.3) with ESMTP id NAA29546 for <ip-atm@nexen.com>; Mon, 13 May 1996 13:49:31 -0400 (EDT)
Received: from thumper.bellcore.com (thumper.bellcore.com [128.96.41.1]) by guelah.nexen.com (8.7.3/8.7.3) with SMTP id NAA07546 for <ip-atm@nexen.com>; Mon, 13 May 1996 13:49:26 -0400 (EDT)
Received: from thumper (localhost [127.0.0.1]) by thumper.bellcore.com (8.6.12/8.6.11) with ESMTP id NAA02037; Mon, 13 May 1996 13:48:26 -0400
Message-Id: <199605131748.NAA02037@thumper.bellcore.com>
To: "Eric W. Gray" <gray@ctron.com>
cc: Albert Manfredi <manfredi@engr05.comsys.rockwell.com>, IP-ATM Working Group <ip-atm@nexen.com>, gja@thumper.bellcore.com
Subject: Re: ipv6nd-02.txt & autoconfig
In-reply-to: Your message of Mon, 13 May 1996 12:18:00 -0400. <319760B8.102F@ctron.com>
Date: Mon, 13 May 1996 13:48:07 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Grenville Armitage <gja@bellcore.com>
X-Orig-Sender: owner-ip-atm@nexen.com
Precedence: bulk
X-Info: Submissions to ip-atm@nexen.com
X-Info: [Un]Subscribe requests to majordomo@nexen.com
X-Info: Archives via http://cell-relay.indiana.edu/cell-relay/archives/IPATM/IPATM.html

>>Bert,
>>
>>You wrote:
	[..re ESIs ]
>>> How about 256 would give you everything that lamented SEL byte would have
>>> provided?
>>> 
>>
>>Are you offering to purchase new organization identifier numbers for all those
>>vendors that need to ship a lot of these?  Are you offering to placate their
>>customers that have already expressed dismay at the wanton use of ESIs (or some
>>other 48 bit address element)?

Good point.

I'd also observe that to really support the equivalent of the SEL
with multiple ESIs vendors MUST burn 256 ESIs into each NIC,
not just MAY burn them. Pity that this direction of architecture
would also make existing NICs obsolete overnight.....

gja

v2.23.0 | Report a Bug | By Email