Re: ipv6nd-02.txt & autoconfig

"Eric W. Gray" <gray@ctron.com> Mon, 13 May 1996 16:24 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa14878; 13 May 96 12:24 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa14870; 13 May 96 12:24 EDT
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa09641; 13 May 96 12:24 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 MAA06613; Mon, 13 May 1996 12:24:16 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id MAA28336 for ip-atm-out; Mon, 13 May 1996 12:18:40 -0400 (EDT)
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.7.3/8.7.3) with ESMTP id MAA28327 for <ip-atm@nexen.com>; Mon, 13 May 1996 12:18:36 -0400 (EDT)
Received: from gatekeeper.ctron.com (ctron.com [134.141.197.25]) by nexen.nexen.com (8.7.3/8.7.3) with SMTP id MAA14632 for <ip-atm@nexen.com>; Mon, 13 May 1996 12:18:34 -0400 (EDT)
Received: (from news@localhost) by gatekeeper.ctron.com (8.6.12/8.6.9) id MAA05659; Mon, 13 May 1996 12:18:32 -0400
Received: from stealth.ctron.com(134.141.5.107) by gatekeeper via smap (V1.3mjr) id sma005643; Mon May 13 12:17:48 1996
Received: from olympus.ctron.com by stealth.ctron.com (4.1/SMI-4.1) id AA28592; Mon, 13 May 96 12:09:50 EDT
Received: from blarney (blarney.ctron.com [134.141.66.40]) by olympus.ctron.com (8.6.12/8.6.9) with ESMTP id MAA15370; Mon, 13 May 1996 12:17:41 -0400
Received: from blarney by blarney via SMTP (940816.SGI.8.6.9/930416.SGI) id MAA06033; Mon, 13 May 1996 12:18:05 -0400
Message-Id: <319760B8.102F@ctron.com>
Date: Mon, 13 May 1996 12:18:00 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Eric W. Gray" <gray@ctron.com>
Organization: Cabletron Systems, Inc.
X-Mailer: Mozilla 2.0 (X11; I; IRIX 5.3 IP12)
Mime-Version: 1.0
To: Albert Manfredi <manfredi@engr05.comsys.rockwell.com>
Cc: IP-ATM Working Group <ip-atm@nexen.com>
Subject: Re: ipv6nd-02.txt & autoconfig
References: <md5:AE311E69E1CFCE13CEF6CD169F7B5BD9> <31939C1A.7801@engr05.comsys.rockwell.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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:
> 
> fddi1-ncd@baynetworks.com wrote:
> 
> > I think you mean "Use of SEL is only for native ATM comms, Classical IP-over-ATM,
> > LAN Emulation and MPOA".
> 
> I suppose, although I find it hard to believe that these other schemes
> _must_ have 20 bytes of ATM address to play with. But _yes_ for native
> ATM, of course. (I mean, LANE and RFC-1577 really must make use of SEL?
> Or else what?)
>

Or else use a new ESI or use a physically different box for logically closely
related functionality.  This argument really comes along way too late for it
to make sense not to include this exception as Andrew suggest - we are not
talking academic issues here, there are actual implemetnations out there that
use SEL this way...

> 
> > And how many ESIs shall we all burn into our adapters, bridges and routers?
> > How about 13? 42? 65536? 16777216?
> 
> 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)?

>
> Bert
> manfredi@engr05.comsys.rockwell.com

--
Eric Gray