On Sun, Nov 09, 2003 at 02:16:10PM -0800, Alain Durand wrote:
>
> My suggestion is to let the authority in charge of administering
> the public IP address space to allocate directly address space
> from a specific bloc to whoever wants it, with no expectation that
> it will be routable and leave it up to the customers and their ISP
> to see if this gets routed or not (with a recommendation that by
> default it is not).
OK, let's compare that against the aims stated in Hinden-Haberman
in section 1.0:
- Globally unique prefix.
- Well known prefix to allow for easy filtering at site
boundaries.
- Allows sites to be combined or privately interconnected without
creating any address conflicts or require renumbering of
interfaces using these prefixes.
- Internet Service Provider independent and can be used for
communications inside of a site without having any permanent or
intermittent Internet connectivity.
- If accidentally leaked outside of a site via routing or DNS,
there is no conflict with any other addresses.
- In practice, applications may treat these address like global
scoped addresses.
Although I'm a little lagged :) I don't see that your proposal has
different properties, "only" that you allocate from some specific
block. If that block is fc00::/8 as per Hinden-Haberman, aren't we
in the same position? So the real issue is the locally-assigned addresses
(given that leakage is inevitable)?
I think the "probably unique locally assigned" prefix crept in maybe
after the above goals were written, given that the locally assigned
prefixes may not be unique, and would not be registered/traceable?
The one addition you have to the above goals seems to be traceability.
[You also suggest a recurring fee, which this draft does not. I would
prefer the draft to just say words to the effect to deter land rush on
the address space, and not specifics of how.]
Would it help or hurt to split this into two drafts, one proposal that
is unique by registration/escrow (and that thus has traceability) and
one that is probabilistically unique?
Tim
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
