On Sun, 2002-11-24 at 11:56, Margaret Wasserman wrote:
>
> All of these issues are present for any sort of private addressing,
> and I don't think that the use of globally-unique local addresses
> will significantly complicate any of these issues.
>
> I think that we should stop calling these addresses "site-local",
> as that is prone to confusion. We would create a separate set
> of globally-unique/provider-independent (GUPI? Pronounced
> "guppy" or "goopy", depending on how much you like them? :-))
> addresses for use as local addresses in Internet connected sites.
>
Firstly, let me say that I'm a "guppy" type person :-)
I agree renaming or creating a different allocation than fec0::/10 would
be a good idea.
However, I think it is important to ensure that the name implies that
these GUPIs are only supposed to be used in an aquarium (of any size),
rather than the deep blue ocean.
Maybe they could be "internal, globally-unique, provider-independent"
addresses or IGUPIs ("iguppy" or "igoopy"). (I'd prefer globally-unique,
provider-independent, internal" address space - but GUPII is not as good
sounding acronym :-) ).
I think the DNS issues might be a bit simpler as well :
1) If the DNS returns an IGUPI address, the device assumes it can get to
it, and lets ICMP dest unreachables or connection timeouts tell it
otherwise. The device's IGUPI address would be used as the source
address.
2) If the DNS returns a global address, the device assumes it can get to
it, and lets ICMP dest unreachables or connection timeouts tell it
otherwise. The device's global address would be used as the source
address.
As for the source address of the DNS request itself :
1) If the DNS server address is a global address, the device uses its
global address as the source address. This would be typical for a
residential user for example.
2) If the DNS server address is a IGUPI address, the device uses its
IGUPI address as the source address. This would be typical for an
enterprise / corporate user for example.
A DNS server may have to return either a global or IGUPI address based
on the source address of the request, for a single query. Still, with
only two types of destination addresses, and IGUPIs probably preferred
over globals, I don't think it is all that complicated.
(sorry about using the IGUPI acronym I came up with in the above, just
doing a test drive on it, seems to work ok, at least for me anyway :-)
).
Mark.
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
