If it was not pity it could be funny. We are in this situation, because RIPE total wrong polices in the years. To sell public resources that no one own and that drive modern life of almost all human being on the planet says we are on total wrong road. I am sure between 25% and 35% from all IPV4 addresses are unused now and maybe half of them are on the market. Of course the prices for IPV4 will go much higher (is there anything changed to stop this ?). Speculators who even do not know what is abbreviature of IP, hijacking public resources with agreement of the organization that have to cover and prevent such scenarios and to guarantee stable work of the system. Obviously RIPE will not change its policies to stop this (as I can see the tries in the past), so what we can do: 1. Do not buy even a single IPV4 address for your bussines. 2. Do not buy IP transit if no IPV6 support, or push upstreams to put such. 3. Fully deploy IPV6 dual stack in your network 2.1 Use IPV4 private addresses + NAT, and spam sites your clients mostly using to make them available and on IPV6. 2.2 If your bussiness is hosting, provide services that need unique IP address on IPV6 only (if you do not have any more available IPV4) 2.3 Push hard all software developers to add IPV6 support in their software if there are no such. You payed for that software right ? Keep in mind IPV6 is the future and you can get them brand new, all IPV4 you can buy now are "second hand" (was used before and may be blacklisted or privately blocked) so if you buy IPV4 you are buying second hand equipment (in unknown condition) on hundred times greater price that it costs as new. Is it a good deal ? Ivaylo Josifov Varteh LTD Varna, Bulgaria On Fri, 29 Nov 2019, Piotr Siwicki - Connected wrote:
Hello,
You made my day. :-)
But, why not to try - YOLO. :-)
Piotr Siwicki
W dniu 2019-11-29 09:42, Jose Manuel Giner napisa?(a):
Hello,
we're interested to buy (full-transfer) a /22,
If anybody is interested to sell us with a special price, please contact me with the proposal details.
Thanks.