IETF Logo Mail Archive

Re: ipv6nd-02.txt & autoconfig

Albert Manfredi <manfredi@engr05.comsys.rockwell.com> Fri, 10 May 1996 16:53 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa19043; 10 May 96 12:53 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa19038; 10 May 96 12:53 EDT
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa10909; 10 May 96 12:53 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 MAA24970; Fri, 10 May 1996 12:46:25 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id MAA29285 for ip-atm-out; Fri, 10 May 1996 12:41:24 -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 MAA29276 for <ip-atm@nexen.com>; Fri, 10 May 1996 12:41:21 -0400 (EDT)
Received: from ENGR05 (engr05.comsys.rockwell.com [199.191.48.132]) by guelah.nexen.com (8.7.3/8.7.3) with SMTP id MAA24895 for <ip-atm@nexen.com>; Fri, 10 May 1996 12:41:17 -0400 (EDT)
Received: by engr05.comsys.rockwell.com (UCX V4.0-10B, OpenVMS V6.1 VAX); Fri, 10 May 1996 12:41:50 -0400
Message-ID: <31939C1A.7801@engr05.comsys.rockwell.com>
Date: Fri, 10 May 1996 12:42:18 -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: fddi1-ncd@baynetworks.com
CC: IP-ATM Working Group <ip-atm@nexen.com>
Subject: Re: ipv6nd-02.txt & autoconfig
References: <md5:AE311E69E1CFCE13CEF6CD169F7B5BD9>
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

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?)

> 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?

Bert
manfredi@engr05.comsys.rockwell.com

v2.23.0 | Report a Bug | By Email