Pekka Savola <[EMAIL PROTECTED]> wrote:
|> I'm all in favor of unique site locals,
|> but I don't see how they eliminate the need to deal with scopes.
|
|I'm not sure why we'd have to be able to kill scopes.
Fine by me. It's just that dealing with scopes seems to be the problem that
most people are complaining about rather than the existence of the addresses
themselves.
|> They are
|> extremely attractive in that they will allow us to interconnect sites with
|> dynamic tunnels, bypassing ISP restrictions on address count and stability.
|> By treating "native" aggregated addresses in effect as routes we can easily
|> build a distributed routing layer that scales indefinitely and hides all the
|> problems of unstable addresses from the applications.
|
|I don't see any significant problems which would prevent this, even though
|we may still want to prevent the use of these site-locals to disconnected
|or semi-disconnected sites.
Then I propose the same thing I (and others) have proposed in the past. Pick
a prefix xxxxxx from the SL space at random and append the hex to some well
known string, e.g., "mysiteprefix" giving mysiteprefixxxxxxx. Register
mysiteprefixxxxxxx.com as a domain name. If it already exists, pick a new
random number and try again. This provides the uniqueness without involving
a new registry service and the nominal fee will discourage people from over-
consuming.
To move to the next step (assuming you want outside connectivity), register an
ISP-provided global as the address for this domain (or a sub-domain; there are
some optimizations that can be made). This is your tunnel destination. When
another site wants to send packets to you, their router recognizes the prefix
as a site-local-unique address and, if the tunnel destination isn't already
cached, performs a DNS lookup of mysiteprefixyyyyy.com. If (as some folks
claim) the dynamic DNS will be good enough to handle the instability of that
ISP-provided global for host name lookups then it will be good enough for
this as well. If (as is more likely) the DNS won't be up to the task the
situation can be improved by having tunnel end points send hints to recent
partners when their addresses are renumbered.
Dan Lanciani
ddl@danlan.*com
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
