Hi Sacha,

On 11/05/15 19:45, Sascha Luck [ml] wrote:
On Mon, May 11, 2015 at 07:25:42PM +0200, Andre Keller wrote:
If my interpretation of the IA is correct, the retroactive part is
restricted to evaluation of transfer requests. It means if/once the
policy is implemented, it applies to resources already allocated by RIPE
NCC but not yet transferred. Resources already transferred wont be
affected. I think this is a sensible approach.

Your interpretation is the same as mine, correct or not ;) The
crux is, though: it changes ripe-623, the "IPv4 Address
Allocation and Assignment Policies for the RIPE NCC Service
Region" document, not a hypothetical "Transfer Policies"
document.
correct...
This sets a precedent for changing *everything else* in
this document and applying the changes retrospectively.
This has already happened before (remember 2007-01?) and it happens with every change of policy..
For example, criteria for making IPv4 assignments, 5 years ago, is no longer the same today, the IPv4 policy has changed several times since 2010 and everything that used to be policy in the past no longer matters, what matters is the latest policy document and not the criteria from years ago.
I can't be the only one who does not want to go there?
I understand what you mean but, seriously, this will affect (based on the IA) a maximum of 580 /22s (and for a period of 1 day to 2 years depending on the date the allocation would be received vs policy implementation).
It will not be a precedent, the precedent has been already approved years ago.

I would not support an implementation that would require the RIPE NCC to apply the same policy differently for an allocation received on the 20th of July vs an allocation received on the 21st of July. This policy proposal's intent is to bring all allocations under the same umbrella (once implemented) and not create more umbrellas..

rgds,
Sascha Luck

regards,
elvis
--

Elvis Daniel Velea

Chief Executive Officer

Email: elvis@V4Escrow.net
US Phone: +1 (702) 475 5914
EU Phone: +31 (0) 61458 1914

Recognised IPv4 Broker/Facilitator in:

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received this email in error, please notify the sender immediately and delete the original.Any other use of this email is strictly prohibited.