IETF Logo Mail Archive

Re: ipv6nd-02.txt & autoconfig

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Mon, 13 May 1996 01:29 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13905; 12 May 96 21:29 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa13901; 12 May 96 21:29 EDT
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa12937; 12 May 96 21:28 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 VAA03093; Sun, 12 May 1996 21:28:47 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id VAA21243 for ip-atm-out; Sun, 12 May 1996 21:15:05 -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 VAA21232 for <ip-atm@nexen.com>; Sun, 12 May 1996 21:15:01 -0400 (EDT)
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132]) by nexen.nexen.com (8.7.3/8.7.3) with ESMTP id VAA00303 for <ip-atm@nexen.com>; Sun, 12 May 1996 21:14:57 -0400 (EDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Message-Id: <199605130105.KAA03837@necom830.hpcl.titech.ac.jp>
Received: by necom830.hpcl.titech.ac.jp (8.6.11/TM2.1) id KAA03837; Mon, 13 May 1996 10:05:02 +0900
Subject: Re: ipv6nd-02.txt & autoconfig
To: Andrew Smith <fddi1-ncd@baynetworks.com>
Date: Mon, 13 May 1996 10:05:00 -0000
Cc: manfredi@engr05.comsys.rockwell.com, ip-atm@nexen.com
In-Reply-To: <9605101617.AA05218@milliways-le0.engwest>; from "Andrew Smith" at May 10, 96 9:17 am
X-Mailer: ELM [version 2.3 PL11]
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

> > The objective is exceedingly simple: use the 48-bit ESI _only_ to
> > generate unique IPv6 addresses using autoconfiguration. Do not use SEL.
> 
> And how many ESIs shall we all burn into our adapters, bridges and routers?

Only one, of course.

> How about 13? 42? 65536? 16777216?

We surely want to run more than 256 applications attached to
a single adapter.

BHLI, which has a 8 byte long field, will do the remaining
identification of 2^64 entities.

							Masataka Ohta

v2.23.0 | Report a Bug | By Email