[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GLOBAL-V6]The list of current Issues in IPv6 Policy
From: leo vegoda <leo@ripe.net>
Subject: Re: [GLOBAL-V6]The list of current Issues in IPv6 Policy
Date: Sun, 21 Sep 2003 14:17:32 +0200
> On Wed, Sep 17, 2003 at 03:05:18PM +0300, Pekka Savola wrote:
>
> [...]
>
> > Nothing prevents you from *not* routing those addresses on the
> > Internet? Unless of course it's a problem in the global-v6 policy, which
> > should then be reviewed.
>
> The current policy says that to "qualify for an initial allocation
> of IPv6 address space, an organisation must [...] plan to provide
> IPv6 connectivity to organisations to which it will assign /48s
> by advertising that connectivity through its single aggregated
> address allocation".
>
> The implication is that an LIR must plan to announce its allocation
> to the public Internet.
>
> However, the wording is vague and leads to uncertainty for those
> requesting space and those evaluating requests. I would like to
> see the policy updated to use crisp, clear, unambiguous language.
> If there is a consensus that unique, public addresses should not be
> available to private networks that will not connect to the Internet
> then that should be stated clearly. If that is not the case then
> the reverse should be made clear.
I agree and in my view, RIR allocations to closed networks should be
accomodated under the current policy, given that they are unable to
avoid address duplicates otherwise.
I'm wondering how we can proceed from here. Is it just a matter of
confirming the actual situation with the RIRs, or do we need another
process to confirm the interpretation?
In anycase, I am interested to know how the RIRs deal with such
requests(allocation for closed networks) under the current
policy. Could I request the RIRs to share it in the ML?
Izumi
