[address-policy-wg] IPv4 Maintenance Policy

hi!

On 04/13/2012 01:33 PM, Rob Blokzijl wrote:
>    This is a document that is slightly different from or usual type of
>    policy documents: it is an attempt to consolidate those policies and
>    practices that will still be relevant after the depletion of the IPv4
>    free pool.
> 
>    The aim is to have a consistent and complete collection of all things
>    relevant to IPv4 for the years to come.
> 
>    Read, digest, enjoy - and discuss :-)

ok, some thoughts:

- formal: actually not tied to 'after the depletion of the v4 free pool' at all.
- the way it's currently worded, it reads like this aims at ultimately disposing ripe. can be done, ofc, but imho that's not really desirable...
- no specific 'more equal than others' cases - that's fine.
- whois db as lir db - that's fine. this again calls for a refer attribute for inet*num.

from the discussions going on lately, it seems there's a strong need to define the nature of ip space, i'd suggest something like this:

2½ Number Resources
The number resources subject to the coordination task by RIPE, namely IP-Address-Space and AS-Number-Space, are considered a commons: they cannot be owned, everybody has equal rights to them, their distribution has to be done fair and equally according to need.

furthermore, i'd suggest to also handle IPv6 in the same single document (like, simply remove the "v4" part from every occurrence of "IPv4", except where really v4 specific).

point 5 actually introduces a subtle change creating a special case, so i'd suggest to change the last sentence simply into something like: "Allocations are treated identically whether they are transferred or directly allocated."

regarding point 8, i don't see any justification for bullet point 4 anymore. actually i think dropping point 8 completely would do, too - ymmv.

there also seems to be an interest in formalizing rir ip allocation in the face of depletion. so i guess this should be dealt with in such a single policy document, too (see my recent mail regarding this subject on this list for details).

regards,

	Chris