Hello Niall, Thank you for your feedback. Here is the list of prefixes involved: 128.201.0.0/16 131.196.0.0/16 137.59.0.0/16 139.26.0.0/16 139.28.0.0/16 139.5.0.0/16 144.168.0.0/16 147.78.0.0/16 149.248.0.0/16 150.107.0.0/16 150.129.0.0/16 150.242.0.0/16 152.89.0.0/16 154.16.0.0/16 161.123.0.0/16 192.140.1.0-192.144.73.255 192.144.78.0-192.145.230.255 Regards, Nick Hyrka Communications Manager RIPE NCC On 3/14/12 6:01 PM, Niall O'Reilly wrote:
Thanks for this announcement, Axel.
I welcome it and have some comments, made in a personal capacity and specifically not to be taken as representing or prejudicing the position of my employer, either actual or future.
On 14 Mar 2012, at 16:28, Axel Pawlik wrote:
1,368,576 IPv4 addresses were removed from the available pool of IPv4 address space on 14 March, 2012.
May I suggest announcing the prefixes involved on ripe-list@ripe.net. This would not only achieve a reasonable approximation to full disclosure, but also provide protection against any error which might cause trouble.
It is intended that any IPv4 legacy space returned to the RIPE NCC will be placed in IANA's Recovered IPv4 Pool.
Fine.
Until now, legacy space returned to the RIPE NCC has been returned to the RIPE NCC's IPv4 available pool but is not re-distributed.
Good to know (or be reminded of).
By removing the legacy space from the RIPE NCC's IPv4 available pool, a more accurate overview of the actual space that can be distributed can be seen.
This improved accuracy is much to be desired, I think.
As legacy space was distributed before the RIR system was introduced, the RIPE NCC does not have any policy governing the re-distribution of returned legacy space. We believe that placing this legacy space in the IANA's Recovered IPv4 Pool for redistribution to the RIRs will contribute to the future well-being of the Internet.
Makes sense to me.
Best regards, Niall O'Reilly