Re: ipv6nd-02.txt & autoconfig

[Andrew Smith <[e-mail]>]

Pete,

> BTW, I think LANE generally does what you have suggested.  That is, use
> the ESI (MAC) for the NIC as the stations MAC address on the ELAN.  This
> limits the number of ELANs a station can join.  In the Digital case, our
> current adapters have 8 ROM MAC addresses to support up to 8 ELANs.  However,
> using the same 8 MAC addresses we can get 2K LISs. Big difference.

LANE did not seem to need any mention of what was inside the NSAPA: nowhere
in the protocol is any structure assumed and the only requirements that
LANE imposes are that clients have uniqueness in the complete opaque bitstring.
Now I appreciate that IPv6 might have some different requirements but it
would be a noble goal to try to keep any requirements on the internal 
structure of the ATM addresses as close to zero as possible.

BTW, in LANE, a client can use whatever MAC address it wants to to be bound
to its "primary ATM address" - there is no requirement for ESIs to match
the declared MAC address. Also, a client can use as many other ATM addresses or 
MAC addresses as it wants (the bindings between them must be relatively 
static of course) although that is probably not relevant here.


>  --- pete
> 

Andrew

********************************************************************************
Andrew Smith					TEL:	[phone]
Bay Networks, Inc. 				FAX:	[phone]
Santa Clara, CA					E-m:	[e-mail]
********************************************************************************