michael.dillon@bt.com wrote:
Policy summary: This policy will establish a process for RIR-to-RIR redistribution of the tail-end of the IPv4 pool, taking effect after the IANA Reserve is exhausted. Each redistribution Allocation will be triggered by the recipient RIR depleting its reserve to a 30 day supply, and will result in up to a 3 month supply being transferred from the RIR with the longest remaining time before it exhausts its own pool.
This does sound interesting, and further helps fine-tune any tail-end disparity that exists following the final IANA allocations.
However, I believe the value of this would be weakened by having this policy implemented too frequently, e.g. if the fastest-allocating RIRs need to do this more than once, or if a slow-allocating RIR is "hit" more than once.
Finally some sensible discussion about the end-game that does not cause us to reach a crisis sooner, and may extend the overall life of IPv4 by a small amount. It also removes the incentives for companies to create shell companies in other regions to lock up a supply of IPv4 addresses.
We should discard all the other silly end-game proposals and do some serious work on making a workable variation of this one.
I would point out that this policy applies *after* the IANA reserve has been allocated. The other policies under discussion apply *before* the reserve has run out, and concern when and how the final IANA blocks are allocated to RIRs. As such, the two kinds of proposals are orthogonal. And, in fact, if both kinds are implemented, the benefit is greater than if only one or the other were implemented. As such, I would have to encourage support for both the "pie" proposal, *and* this "cooperative" proposal. Brian