* McTim
I think that perhaps we should all read the latest draft of the RFC2050 update:
https://www.ripe.net/ripe/policies/proposals/2013-03
1) Allocation Pool Management: Due to the fixed lengths of IP addresses and AS numbers, the pools from which these resources are allocated are finite. As such, allocations must be made in accordance with the operational needs of those running the networks that make use of these number resources and by taking into consideration pool limitations at the time of allocation.
This proposal seems counter to the above, as well as in conflict with 2050 itself.
I note the author has tried to provide counter arguments, but to me they are not sufficient to persuade me to support this proposal.
Hi McTim, The pool from which all allocations are drawn in the RIPE region is exclusively governed by the «last /8 policy», currently found in section 5.6 of the policy document. In a nutshell, it says: «a single /22 per LIR, no more, no less - regardless of actual operational needs». 2013-03 does not change the mechanics of this last /8 policy, at least that is not my intention. The proposal does "promote" it to be the main and only allocation policy found in the document, instead of being contained in section 5.6 all by itself - but again, the intention of this change is just editorial cleanup, clarification, and getting rid of defunct policy text - not to actually modify the effective policy. So, in summary, I don't see 2013-03 running any more afoul of the 2050-bis passage you quoted than what the current last /8 policy already have. Best regards, Tore Anderson