Date: Tue, 6 Nov 2001 09:05:57 -0800 (PST)
From: Michael Thomas <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
| Tangential -- all that's required is the prefix length,
| right?
Unless it is /64 in which case you'd also need to know whether EUI-64
was in use or not.
I know there's the theory that the initial 3 bit prefix, if between 1 and 6
(inclusive) mandates use of /64 and EUI-64 everywhere. That's simply
ludicrous, there's no reason for it, and long term it will never last.
So I certainly don't want to start designing anything anywhere that
is built based upon that assumption.
You'd also want to have some idea whether you can expect the relevant
anycast address to exist or not ... most links aren't going to have
mobile IP home agents for example (or in any case, not all links will).
All in all (if you actually want to achieve a productive result, rather
than just send out packets to see what happens) you're going to need a
reasonable amount of knowledge about the destination.
Computing addresses that relate to anything that isn't local has never
been a good idea, and it isn't going to start becoming one anytime soon.
jre
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
