<div dir="ltr">Ciprian:<div><br></div><div>I don't believe UK tax payers will be ok with their government giving up 100m Euro assets, that being said, market is the market, just like the land in California 200 years ago are practically free while today might cost 10m to get a small apartment in the bay area, it is the new reality here and everybody have to deal with it.</div><div><br></div><div>And for the /22, I fully support the policy and I believe such abuse should not happen. and such abuse practically turns the last /8 policy useless. If we should allow such abuse then why shouldn't we just completely deplete the IPv4 instead of reserving the last /8.</div><div><br></div><div>One thing do worries me though, by doing a simple math:</div><div>(2000+1600+1600)/1000=5.2Euro/IP in cost, if future IP price reaches 10 Euro or up, we might still not able to stop such abuse, unless we make the last /22 totally untransferable.</div><div><br></div><div>Just my two cents.</div><div><br></div><div>With regards.</div><div><br></div><div>Lu</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 9, 2015 at 10:16 PM, <span dir="ltr"><<a href="mailto:address-policy-wg-request@ripe.net" target="_blank">address-policy-wg-request@ripe.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send address-policy-wg mailing list submissions to<br>
<a href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://www.ripe.net/mailman/listinfo/address-policy-wg" target="_blank">https://www.ripe.net/mailman/listinfo/address-policy-wg</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:address-policy-wg-request@ripe.net">address-policy-wg-request@ripe.net</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:address-policy-wg-owner@ripe.net">address-policy-wg-owner@ripe.net</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of address-policy-wg digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: 2015-01 Draft Document and Impact Analysis Published<br>
(Alignment of Transfer Requirements for IPv4 Allocations)<br>
(Garry Glendown)<br>
2. Re: 2015-01 Draft Document and Impact Analysis Published<br>
(Alignment of Transfer Requirements for IPv4 Allocations)<br>
(Ciprian Nica)<br>
3. Re: 2015-01 Draft Document and Impact Analysis Published<br>
(Alignment of Transfer Requirements for IPv4 Allocations)<br>
(Opteamax GmbH)<br>
4. Re: 2015-01 Draft Document and Impact Analysis Published<br>
(Alignment of Transfer Requirements for IPv4 Allocations)<br>
(Tore Anderson)<br>
5. Re: 2015-01 Draft Document and Impact Analysis Published<br>
(Alignment of Transfer Requirements for IPv4 Allocations)<br>
(Ciprian Nica)<br>
6. Re: 2015-01 Draft Document and Impact Analysis Published<br>
(Alignment of Transfer Requirements for IPv4 Allocations)<br>
(Ciprian Nica)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 09 Jun 2015 21:49:57 +0200<br>
From: Garry Glendown <<a href="mailto:garry@nethinks.com">garry@nethinks.com</a>><br>
To: <a href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a><br>
Subject: Re: [address-policy-wg] 2015-01 Draft Document and Impact<br>
Analysis Published (Alignment of Transfer Requirements for IPv4<br>
Allocations)<br>
Message-ID: <<a href="mailto:55774365.9050801@nethinks.com">55774365.9050801@nethinks.com</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
Guten Tag,<br>
> We all hate some things, wish for others... But making the life harder<br>
> is not equal to solving the problem.<br>
_WHO_ is this policy change affecting? Any legitimate business not set<br>
on circumventing RIPE policy will, as Ciprian wrote, become an LIR in<br>
order to use the IPs. And use them for 2+ years ... the only situations<br>
that come to mind in which an LIR might want to transfer their IPs is<br>
either if they are being bought (tough luck for the buying company, at<br>
least they will not be able to transfer ownership for up to two years),<br>
or if they go broke, in which case the IPs assigned wouldn't need to be<br>
available anymore ...<br>
<br>
-garry<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 09 Jun 2015 22:53:17 +0300<br>
From: Ciprian Nica <<a href="mailto:office@ip-broker.uk">office@ip-broker.uk</a>><br>
To: Garry Glendown <<a href="mailto:garry@nethinks.com">garry@nethinks.com</a>>, <a href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a><br>
Subject: Re: [address-policy-wg] 2015-01 Draft Document and Impact<br>
Analysis Published (Alignment of Transfer Requirements for IPv4<br>
Allocations)<br>
Message-ID: <<a href="mailto:5577442D.7060903@ip-broker.uk">5577442D.7060903@ip-broker.uk</a>><br>
Content-Type: text/plain; charset=windows-1252<br>
<br>
Hi,<br>
<br>
<br>
On 6/9/2015 10:28 PM, Garry Glendown wrote:<br>
<br>
<br>
>>>> - help the last /8 pool become even larger<br>
>>> Measures for IP space conservation have ensured availability of<br>
>>> addresses over the last ~10 years - if sensible decisions about policies<br>
>>> cause push the frame further than previous measures have, I'd say: Job<br>
>>> well done! Hopefully, by the time the Internet disables IPv4 there are<br>
>>> still IPv4 addresses available for assignment by RIRs ...<br>
>> Here I can't agree but I also can't contradict you. There are opinions<br>
>> that say if the perspective that IPv4 will really be exhausted it will<br>
>> push ISPs to deploy IPv6 sooner. If you tell them that there will be<br>
>> IPv4 resources for RIPE to give even in 10-20 years, then probably many<br>
>> will say let's see if we live to that time and then we'll make a decision.<br>
> OK, maybe we are getting somewhere: Apart from you contradicting<br>
> yourself in part, you would consider IPv4 shortage to push v6<br>
> deployment.<br>
<br>
As I said, there are opinions that say the perspective of real IPv4<br>
exhaustion would push IPv6 deployment. I don't have a maginifing glass<br>
to make predictions, I have my opinion on that matter but I don't think<br>
it's usefull to elaborate on that.<br>
<br>
>> Let's not help the prices raise then. The demand for IPs is supported<br>
>> by real needs as otherwise nobody would pay so much money for them. In<br>
>> a free economy when you shorten the supply, prices will grow. If there<br>
>> would have been a policy that would say let's get back the IPs from<br>
>> those who don't use them, that would really help.<br>
> But we have a limited supply - if RIRs didn't put policies in place to<br>
> reduce IP use, we would have already run out quite some time ago. Just<br>
> by ignoring the fact that there is an IP shortage doesn't make it go away.<br>
<br>
Again, my opinion is that we can learn by observing the effects of<br>
previous policies.<br>
<br>
I didn't want to get involved into discussing this policy as I noticed<br>
everyone gets in all kind of details which don't get the problem solved.<br>
I don't believe this policy is a usefull step in the right direction.<br>
<br>
As I mentioned earlier there are no positive effects, it doesn't help<br>
conserve the last /8 pool and there are no benefits to the community by<br>
adopting it. That's what's important. All other discussions lead to<br>
polemics that should be taken somewhere else. Maybe at the RIPE meetings.<br>
<br>
Ciprian Nica<br>
IP Broker Ltd.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 09 Jun 2015 21:57:37 +0200<br>
From: Opteamax GmbH <<a href="mailto:ripe@opteamax.de">ripe@opteamax.de</a>><br>
To: <a href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a><br>
Subject: Re: [address-policy-wg] 2015-01 Draft Document and Impact<br>
Analysis Published (Alignment of Transfer Requirements for IPv4<br>
Allocations)<br>
Message-ID: <<a href="mailto:55774531.9050009@opteamax.de">55774531.9050009@opteamax.de</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
<br>
On <a href="tel:09.06.2015%2019" value="+31906201519">09.06.2015 19</a>:54, Ciprian Nica wrote:><br>
> Come up with a proposal that will really stop this kind of activity and<br>
> I'll fully support it.<br>
<br>
The only proposal which would actually fully stop this is actually<br>
refusing Prefix-Transfers completely and enforce returning to the RIPE-Pool.<br>
<br>
The only chance for taking-over Resources then should be a real "merge"<br>
of two LIR including the demand of their individual customers justifying<br>
why it is important to not being renumbered ... That kind of proposal<br>
would actually remove a lot of "profit-making" for brokers etc. on one<br>
hand, but on the other hand it offers the opportunity to the ones really<br>
needing IPv4-Space to get their need fullfilled by RIPE... at least if<br>
that kind of proposal would also enforce withdrawing IP-space which is<br>
not being really used for a while.<br>
<br>
Actually if that'd be done world-wide with all address-space not<br>
publicly routed - and therefore easily to replace with <a href="http://10.0.0.0/8" target="_blank">10.0.0.0/8</a> - we'd<br>
have sufficient IPv4 for the next decades ... Just a brief look into the<br>
routing-table on my router and I see 10 complete /8 (so called public<br>
IP-Space-prefixes) which are completely not announced and another 4 /8<br>
with less then one /21 announced.... and I do not want to know how many<br>
of the large /8 to /14 announcements are actually routed into a<br>
blackholes, as there are no real users on large parts of those nets.<br>
<br>
... and we discuss about /22 nets being "hoarded"?<br>
<br>
Sorry, could not resist to point on that.<br>
<br>
Still I support the proposal because it reduces the win for abusers and<br>
raises the risk that the now "hoarded" addresses are less worth when<br>
they are sellable. Hey, it is on us to make IPv4-Prefixes worthless.<br>
<br>
Best regards<br>
<br>
--<br>
Jens Ott<br>
<br>
Opteamax GmbH<br>
<br>
Simrockstr. 4b<br>
53619 Rheinbreitbach<br>
<br>
Tel.: +49 2224 969500<br>
Fax: +49 2224 97691059<br>
Email: <a href="mailto:jo@opteamax.de">jo@opteamax.de</a><br>
<br>
HRB: 23144, Amtsgericht Montabaur<br>
Umsatzsteuer-ID.: DE264133989<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 9 Jun 2015 21:59:57 +0200<br>
From: Tore Anderson <<a href="mailto:tore@fud.no">tore@fud.no</a>><br>
To: Ciprian Nica <<a href="mailto:office@ip-broker.uk">office@ip-broker.uk</a>><br>
Cc: Gert Doering <<a href="mailto:gert@space.net">gert@space.net</a>>, <a href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a><br>
Subject: Re: [address-policy-wg] 2015-01 Draft Document and Impact<br>
Analysis Published (Alignment of Transfer Requirements for IPv4<br>
Allocations)<br>
Message-ID: <<a href="mailto:20150609215957.407aba88@envy.fud.no">20150609215957.407aba88@envy.fud.no</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Hi Ciprian,<br>
<br>
* Ciprian Nica<br>
<br>
> What should be pointed out is the effects of the policy and if the<br>
> community will benefit from it or some small group of people.<br>
><br>
> To summarize the effects will be :<br>
> - higher membership fees<br>
<br>
Nope. The RIPE NCC membership is steadily growing[1], and as a result the<br>
membership fee has steadily been decreasing[2].<br>
<br>
[1] <a href="https://labs.ripe.net/statistics/number-of-lirs" target="_blank">https://labs.ripe.net/statistics/number-of-lirs</a><br>
[2] <a href="https://www.ripe.net/publications/docs/ripe-620" target="_blank">https://www.ripe.net/publications/docs/ripe-620</a><br>
<br>
The main reason for this growth is *actual network operators* joining<br>
in order to make use of the ?last /8 policy?. Even if we managed to<br>
stop *all* the "create LIR; transfer /22; close LIR" abuse, that would<br>
not reverse this trend.<br>
<br>
Also, keep in mind that these "create; transfer; close" LIRs will pay<br>
the NCC as little as they can get away with. As I understand it, that<br>
means the sign-up fee and one yearly membership fee. If the goal is to<br>
increase the NCC's revenue and lower the membership fees, it is much<br>
better long-term strategy to deny these "create; transfer; close" LIRs<br>
and instead keep the /22s in reserve for future LIRs belonging to<br>
*actual network operators*. Why? Because these will actually *keep<br>
paying their membership fees* instead of closing down as soon as<br>
possible.<br>
<br>
> What is the expected positive effect ? To preserve the last /8 pool ?<br>
> The one that increased to 18.1 million IPs ?<br>
<br>
The by far biggest contributor to the RIPE NCC's ?last /8? pool has<br>
been the IANA IPv4 Recovered Address Space pool[4].<br>
<br>
[4] <a href="https://www.iana.org/assignments/ipv4-recovered-address-space/ipv4-recovered-address-space.xhtml" target="_blank">https://www.iana.org/assignments/ipv4-recovered-address-space/ipv4-recovered-address-space.xhtml</a><br>
<br>
This pool contained quite a bit of space when it was first activate,<br>
and the RIPE NCC has to date received 3,670,016 IPv4 addresses from it<br>
(/11+/12+/13). It is important to note, though, that the IANA pool *is<br>
not replenishing*. It has been almost three years ago since any<br>
significant amounts of space was added to it (back in 2012-08).<br>
<br>
So we cannot expect that allocations from the IANA pool will continue<br>
to match the rate of /22 allocations from the RIPE NCC's ?last /8? pool<br>
in the future. Therefore I have every expectation that we'll start<br>
seeing ?last /8? pool actually start to drain soon.<br>
<br>
For what it's worth, since the first ?last /8? allocation was made 995<br>
days ago (cake in five days!), a total of 6,657,280 IPv4 addresses has<br>
been delegated by the NCC. Our share of the remaining IANA pool is on<br>
the other hand only 425,625 addresses.<br>
<br>
So all in all, I think that preserving the last /8 pool is indeed a<br>
valuable goal. If possible I'd like to see it last for another ten<br>
years - but given today's burn rate, the current 18.1M addresses plus<br>
whatever's coming from IANA will not suffice.<br>
<br>
Tore<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Tue, 09 Jun 2015 23:00:55 +0300<br>
From: Ciprian Nica <<a href="mailto:office@ip-broker.uk">office@ip-broker.uk</a>><br>
To: Garry Glendown <<a href="mailto:garry@nethinks.com">garry@nethinks.com</a>>, <a href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a><br>
Subject: Re: [address-policy-wg] 2015-01 Draft Document and Impact<br>
Analysis Published (Alignment of Transfer Requirements for IPv4<br>
Allocations)<br>
Message-ID: <<a href="mailto:557745F7.8060102@ip-broker.uk">557745F7.8060102@ip-broker.uk</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
There can be startups that get sold before 2 years and they would get<br>
affected or companies that go broke and try to get back part of their<br>
investment, but, as you saw, the guys that do circumvent RIPE policy<br>
will still be able to do it, so it won't affect them.<br>
<br>
Ciprian<br>
<br>
On 6/9/2015 10:49 PM, Garry Glendown wrote:<br>
> Guten Tag,<br>
>> We all hate some things, wish for others... But making the life harder<br>
>> is not equal to solving the problem.<br>
> _WHO_ is this policy change affecting? Any legitimate business not set<br>
> on circumventing RIPE policy will, as Ciprian wrote, become an LIR in<br>
> order to use the IPs. And use them for 2+ years ... the only situations<br>
> that come to mind in which an LIR might want to transfer their IPs is<br>
> either if they are being bought (tough luck for the buying company, at<br>
> least they will not be able to transfer ownership for up to two years),<br>
> or if they go broke, in which case the IPs assigned wouldn't need to be<br>
> available anymore ...<br>
><br>
> -garry<br>
><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Tue, 09 Jun 2015 23:16:27 +0300<br>
From: Ciprian Nica <<a href="mailto:office@ip-broker.uk">office@ip-broker.uk</a>><br>
To: Opteamax GmbH <<a href="mailto:ripe@opteamax.de">ripe@opteamax.de</a>>, <a href="mailto:address-policy-wg@ripe.net">address-policy-wg@ripe.net</a><br>
Subject: Re: [address-policy-wg] 2015-01 Draft Document and Impact<br>
Analysis Published (Alignment of Transfer Requirements for IPv4<br>
Allocations)<br>
Message-ID: <<a href="mailto:5577499B.6020801@ip-broker.uk">5577499B.6020801@ip-broker.uk</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
Hi Jens,<br>
<br>
I totally agree with most of what you said. When the "depletion" was<br>
announced I took a look at the global routing table and when I saw that<br>
only 60% of the 4.2 billion IPv4 addresses were announced, I thought<br>
something is wrong.<br>
<br>
I really didn't imagine any sane person would pay so much money for IPs<br>
but probably the ones that predicted or helped this happen, were smart<br>
enough to hoard the pre-last /8s.<br>
<br>
If it were possible, I think they should be the first source for taking<br>
back IPs and obviously corporations or organisations that sit on /8s<br>
should be somehow persuaded to give them back.<br>
<br>
When I've heared that UK's Department for Work and Pensions started to<br>
sell the IPs a couple weeks I couldn't believe it, although there were<br>
rumors about it some months ago. I remember that in 2012 they were asked<br>
about the /8 they keep for the internal network and they said it's in<br>
use and they can't give up on it.<br>
<br>
Imagine if they would have returned the IPs to RIPE instead of taking<br>
advantage and making a huge profit. If Daimler, UK's ministry of defence<br>
and other holders of large blocks would give them back to the community,<br>
that would be a real benefit.<br>
<br>
UK's DWP sold 131K IPs in one shot. They sit on another 16+ million IPs<br>
and you take your rage on the 2 russians that sold 30K IPs each over the<br>
last year ? Let's stop the ants too, but I would rather start with the<br>
elefants.<br>
<br>
Ciprian<br>
<br>
On 6/9/2015 10:57 PM, Opteamax GmbH wrote:<br>
><br>
> On 09.06.2015 19:54, Ciprian Nica wrote:><br>
>> Come up with a proposal that will really stop this kind of activity and<br>
>> I'll fully support it.<br>
><br>
> The only proposal which would actually fully stop this is actually<br>
> refusing Prefix-Transfers completely and enforce returning to the RIPE-Pool.<br>
><br>
> The only chance for taking-over Resources then should be a real "merge"<br>
> of two LIR including the demand of their individual customers justifying<br>
> why it is important to not being renumbered ... That kind of proposal<br>
> would actually remove a lot of "profit-making" for brokers etc. on one<br>
> hand, but on the other hand it offers the opportunity to the ones really<br>
> needing IPv4-Space to get their need fullfilled by RIPE... at least if<br>
> that kind of proposal would also enforce withdrawing IP-space which is<br>
> not being really used for a while.<br>
><br>
> Actually if that'd be done world-wide with all address-space not<br>
> publicly routed - and therefore easily to replace with <a href="http://10.0.0.0/8" target="_blank">10.0.0.0/8</a> - we'd<br>
> have sufficient IPv4 for the next decades ... Just a brief look into the<br>
> routing-table on my router and I see 10 complete /8 (so called public<br>
> IP-Space-prefixes) which are completely not announced and another 4 /8<br>
> with less then one /21 announced.... and I do not want to know how many<br>
> of the large /8 to /14 announcements are actually routed into a<br>
> blackholes, as there are no real users on large parts of those nets.<br>
><br>
> ... and we discuss about /22 nets being "hoarded"?<br>
><br>
> Sorry, could not resist to point on that.<br>
><br>
> Still I support the proposal because it reduces the win for abusers and<br>
> raises the risk that the now "hoarded" addresses are less worth when<br>
> they are sellable. Hey, it is on us to make IPv4-Prefixes worthless.<br>
><br>
> Best regards<br>
><br>
<br>
<br>
<br>
End of address-policy-wg Digest, Vol 46, Issue 20<br>
*************************************************<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><br></div>
</div></div>