[address-policy-wg] 2014-04 New Policy Proposal (Relaxing IPv6 Requirement for Receiving Space from the Final /8)

On Mon, May 5, 2014 at 3:17 PM, Marco Schmidt <mschmidt at ripe.net> wrote:
>
> Dear colleagues,
>
>
> A proposed change to RIPE Document ripe-606, "IPv4 Address Allocation
> and Assignment Policies for the RIPE NCC Service Region", is now
> available for discussion.
>
>
> You can find the full proposal at:
>
>     http://www.ripe.net/ripe/policies/proposals/2014-04
>
> We encourage you to review this proposal and send your comments to
> <address-policy-wg at ripe.net> before 3 June 2014.

The idea is good.

However - can we please stop introducing the term  PI and PA into yet
another document?
The other problem is as mention in the working group today, do we
really need to mention IPv6 there?

If we should keep IPv6 there, I suggest something like this:

"Allocations will only be made to LIRs if they have already received
an IPv6 allocation or assignment"

(old text : Allocations will only be made to LIRs if they have already
received an IPv6 allocation from an upstream LIR or the RIPE NCC.)


This just require them to have some sort of IPv6 registred to them, no
difference between PI/PA, RIPE NCC or other regions...
This is quite similar to what we had back in 6bone days, you first
needed a connection to 6bone and some address space before you would
get your own block.



-- 

Roger Jorgensen           | ROJO9-RIPE
rogerj at gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger at jorgensen.no