Re: ipv6nd-02.txt & autoconfig

schulter@zk3.dec.com Thu, 09 May 1996 20:23 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23271; 9 May 96 16:23 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa23267; 9 May 96 16:23 EDT
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa14698; 9 May 96 16:23 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 QAA18718; Thu, 9 May 1996 16:16:46 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id QAA13173 for ip-atm-out; Thu, 9 May 1996 16:04:15 -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 QAA13164 for <ip-atm@nexen.com>; Thu, 9 May 1996 16:04:11 -0400 (EDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: schulter@zk3.dec.com
Received: from mail13.digital.com (mail13.digital.com [192.208.46.30]) by nexen.nexen.com (8.7.3/8.7.3) with ESMTP id QAA13974 for <ip-atm@nexen.com>; Thu, 9 May 1996 16:04:07 -0400 (EDT)
Received: from flume.zk3.dec.com by mail13.digital.com (8.7.5/UNX 1.2/1.0/WV) id PAA19724; Thu, 9 May 1996 15:45:05 -0400 (EDT)
Received: from dogfish.zk3.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM) id AA12760; Thu, 9 May 1996 15:44:33 -0400
Received: from localhost by dogfish.zk3.dec.com (5.65v3.2/1.1.10.3/27Jun95-1215PM) id AA10915; Thu, 9 May 1996 15:44:32 -0400
Message-Id: <9605091944.AA10915@dogfish.zk3.dec.com>
X-Mailer: exmh version 1.6.1 5/23/95
To: Grenville Armitage <gja@bellcore.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 "Thu, 09 May 96 14:17:08 EDT." <199605091817.OAA20030@thumper.bellcore.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 09 May 1996 15:44:32 -0400
X-Mts: smtp
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

> A given ATM switch will need to track multiple ESIs and map them to
> a single output port when forwarding the SETUP to the end system.

While I don't think that the use of the SEL should be restricted as Bert
has suggested, the ATM switch already has to be able to keep track of 
multiple ESIs per endsystem.  ILMI allows an endsystem to register any 
number of ESIs  (generally limited by implementation).  So, using multiple 
ESIs doesn't place any new requirements on the switches.  However, not
using the SEL byte does reduce the potential number of ATM services
that can be addressed on an end system by a factor of 256.

FWIW, all switches I've used have allowed each host to register at least
eight ESIs per port (and some at least 32).  Digital's UNIX implementation
of ATM typically registers nine ESIs per NIC with a switch, and so far
we haven't run into any switches that can't handle this.

 --- pete

------------------
Peter Schulter					schulter@zk3.dec.com
Digital UNIX Networking				voice (603) 881-2920
Digital Equipment Corp				voice (DTN) 381-2920
ZK3-03/U14					FAX   (603) 881-2257
110 Spit Brook Road				FAX   (DTN) 381-2257
Nashua, NH 03062