Re: ipv6nd-02.txt & autoconfig

Albert Manfredi <manfredi@engr05.comsys.rockwell.com> Thu, 09 May 1996 18:01 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20250; 9 May 96 14:01 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa20246; 9 May 96 14:01 EDT
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa12416; 9 May 96 14:01 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 NAA17281; Thu, 9 May 1996 13:50:40 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id NAA11576 for ip-atm-out; Thu, 9 May 1996 13:45:30 -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 NAA11565 for <ip-atm@nexen.com>; Thu, 9 May 1996 13:45:27 -0400 (EDT)
Received: from ENGR05 (engr05.comsys.rockwell.com [199.191.48.132]) by nexen.nexen.com (8.7.3/8.7.3) with SMTP id NAA11486 for <ip-atm@nexen.com>; Thu, 9 May 1996 13:45:23 -0400 (EDT)
Received: by engr05.comsys.rockwell.com (UCX V4.0-10B, OpenVMS V6.1 VAX); Thu, 9 May 1996 13:15:39 -0400
Message-ID: <3192528D.19E@engr05.comsys.rockwell.com>
Date: Thu, 09 May 1996 13:16:13 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Albert Manfredi <manfredi@engr05.comsys.rockwell.com>
Organization: Rockwell Defense Electronics - Collins
X-Mailer: Mozilla 2.01 (Win16; I)
MIME-Version: 1.0
To: gja@bellcore.com
CC: IP-ATM Working Group <ip-atm@nexen.com>
Subject: Re: ipv6nd-02.txt & autoconfig
References: <md5:7FBABA1F8115DB068B04643096F0685F>
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

gja@bellcore.com wrote:
> 
> Disclaimer: This is grumpy response.

I noticed.

> Bert, did you actually digest the paragraph you responded to? SEL field
> _is_ a neat-o feature, but it _is_ used to create logical ATM interfaces.
> End of story.

Did this proclamation get carved in stone? Just how much history do we
have to put with with behind IPv6 over ATM? Is there a big worry about
legacy networks?

What's wrong with saying "Do not use SEL when running IPv6 over ATM," for
instance? "Use of SEL is only for native ATM comms." Or "Use of SEL is
only permitted after the calling party is is made aware of the fact the
the called party is directly reachable over the ATM net." 

Or, alternatively, "All IPv6 communications over ATM SHALL be accomlished
over SEL = x (perhaps x = 0)."

The objective is exceedingly simple: use the 48-bit ESI _only_ to
generate unique IPv6 addresses using autoconfiguration. Do not use SEL.

Are you concerned that the IETF can't make such a ruling? That's fine, I
never implied it should be the IETF. It could be the ATMF. The simple
fact is that autoconfiguration would become much simpler this way, all to
the benefit of public perceptions of IP over ATM and ATM's survival.

Bert
manfredi@engr05.comsys.rockwell.com