Hi Christian,

I think that we need to work on understanding the goals of globally-unique,
provider-independent addressing, so that we can properly evaluate the
different proposals that we are likely to see.

In my opinion, the addresses should be routable, although it isn't
necessary that ISPs advertise them in global routing tables.  For
instance, I think it would be good if two "sites" could route their
globally-unique, provider-independent addresses to each other.

I don't know what you mean by "free".  It would be acceptable, in my
opinion, if people had to pay a registration fee for an address block.

In what way is the consensus "just like site locals"?  I think that
we want something better than site-locals that solves the problems
of:

        - persistent addresses to put in configuration files,
                security filters, etc.
        - addresses that can be used in intermittently connected
                sites and remain valid
        - addresses that survive ISP renumbering

Without the use of ambiguous addresses.

In addition, there are some other things we should solve that site-locals
don't solve:

        - work properly when two organizations merge
        - be possible to associate with an administrative
                entity to which they are registered

Are there other problems that we need to solve to make these
addresses a preferrable alternative to site-locals?

Margaret



* we want to remove ambiguity, which is the root cause of many problems occuring when scoped addresses leak.

* we may or may not want to prevent routing of these addresses between sites. I guess we should certainly prevent routing between non-consenting sites.

* we definitely want the addresses to be provider independent, so they can survive renumbering or intermittent connectivity.

* indeed, it would be desirable that the addresses be usable in sites that are not connected.

* and we would definitely want the addresses to be free.

One of the main point of contention regarded routing. I guess that the consensus is, "just like site local addresses." We don't want to prevent usage in connected sites, but we expect that in these sites the hosts will also have provider based addresses, and that traffic routed out of the site will use the provider addresses.

Now, I guess we have to work from there.

-- Christian Huitema

--------------------------------------------------------------------
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]
--------------------------------------------------------------------

--------------------------------------------------------------------
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]
--------------------------------------------------------------------

Reply via email to