[address-policy-wg] 2014-02 New Policy Proposal (Allow IPv4 PI transfer)

* Erik Bais

>> 1) The new policy says: «Changes to the original criteria must be
>> documented in the RIPE Registry, or the assignment will no longer be
>> considered valid». What exactly are the implications of this
>> requirement? I am assuming that the «RIPE Registry» is not the RIPE DB;
>> as the original criteria isn't documented in the RIPE DB to begin with.
> 
> The new phrase as it states in the policy proposal is:  
> - 6.3 Validity of an Assignment
> 
> - An assignment is valid as long as the original criteria on which it was
> based remain valid and it is properly registered in the RIPE Database.
> Changes to the original criteria must be documented in the RIPE Registry, or
> the assignment will no longer be 
> - considered valid. An assignment that was based on information that turns
> out to be incorrect is no longer valid.
> 
> There is indeed a difference with what we see in the RIPE DB and the actual
> RIPE Registry. (The RIPE back-end) 
> The reason of why I kept it in the policy is, is to keep the original policy
> text as much as possible and not change entire PI criteria.

Yeah, I fully understand why you want to remove the requirement that the
original criteria must be unchanged for the assignment to remain valid.
This requirement was always completely out of touch with operational
realities anyway. Good riddance!

However, considering that the NCC no longer has any mandate to evaluate
the validity of the given criteria, asking assignees to send updates to
the NCC whenever they want to change the way the assignment is being
used seems rather pointless to me. After all there's not much the NCC
would do with that information except to archive it somewhere.

If you want to allow people to change how they're using their
assignments, then I'd prefer that you let them do so freely, without
introducing any new bureaucracy and forms.

If I may, here's my suggested version of a new 6.3:

«All assignments are valid as long they are properly registered in the
RIPE Database. If an assignment is based on information that turns out
to be invalid, the assignment is no longer valid.»

> Good point .. we spoke about this and decided to get this through and then
> (via a 2 phased approach) take the transfer parts away in a new proposal to
> get them changed into a new RIPE document (away from RIPE 606)
> During the Athens meeting it was agreed that I would propose a Transfer
> policy for PI. (that is what I've done) 
> There are some other tasks that we came across during the prep for this
> proposal that I would like to fix (like the ability to transfer IPv6 and AS
> number resources), which would be able to in the above mentioned phase 2.

Understood, thanks for elaborating.

Tore