<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body bgcolor="white" lang="DE" link="blue" vlink="purple"> <div class="WordSection1"> Hi Elvis,<o:p></o:p> I agree with your proposal. I’m interested in the fact: Are there such “loophole” cases right now or is it a theoretical problem, that could be happen if 2015-01 would not be accepted?<o:p></o:p> Regards,<o:p></o:p> Carsten<o:p></o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> Von: address-policy-wg [mailto:address-policy-wg-bounces@ripe.net] Im Auftrag von Elvis Daniel Velea Gesendet: Montag, 9. M�rz 2015 17:32 An: address-policy-wg@ripe.net Betreff: Re: [address-policy-wg] 2015-01 New Policy Proposal (Alignment ofTransfer Requirements for IPv4 Allocations)<o:p></o:p> </div> </div> <o:p> </o:p> Hi everyone, I have thinking at what to answer regarding the comments on this proposal. Firstly, the /22 from the last /8 policy proposal aimed to create a method for anyone to receive at least a few (1024) IPv4 addresses by becoming a member of the RIPE NCC. Even then, the proposers had noted that anyone can open multiple LIRs and receive from the RIPE NCC more than 1024 IP addresses and asked the RIPE NCC to be vigilant. [1] What happens now is not in the spirit of that policy proposal as the /22 from the RIPE NCC does not have the two years holding period so a few found a way to make a business using this loophole. This policy proposal is just trying to add the same holding period for a transfer of the /22 as it is already for the rest of the allocations made by the RIPE NCC. While I do agree that if the RIPE NCC free pool would be depleted, the market would takeover and normalize the price, the community has decided to have IPv4 addresses available for anyone that wants to become a member of the RIPE NCC and therefore request & receive a /22. I think that a separate proposal could tackle this issue, there were some discussions last year (if I remember correctly) and some members of this community suggested the increasing the limit from /22 to /21. That may deplete the free pool faster, but it will still slowly bleed out in a few years. If we do not agree that this policy proposal is fair and needed, I predict that we will see more and more companies opening LIRs just to make use of this loophole and make a profit from selling one or more /22s from the last /8. Actually, this policy proposal may have already harmed the free pool because if it does not get approved, more people have found out of the loophole and nothing will stop them from using it, they will have the endorsement of the community to just go ahead and open multiple LIRs. I would not be surprised to see a very large ISP or (content) hosting company setting up 1.000 LIRs to get 1million IP addresses.. and if they setup 1024 LIRs in the same 'day' they may even get a /12 as a contiguous block. In that case, would you find it fair that if someone wants to use a loophole (1024 times) they can get a /12 from the RIPE NCC while others need to use the market? Considering these, Martin (and whoever else does not like this policy proposal), please let me know if you oppose to to this proposal as it is written and if you have any suggestion on what would be acceptable. regards, Elvis [1] <a href="https://www.ripe.net/ripe/policies/proposals/2010-02">https://www.ripe.net/ripe/policies/proposals/2010-02</a> "Some organisations may set up multiple LIR registrations in an effort to get more address space than proposed. The RIPE NCC must be vigilant regarding these, but the authors accept that it is hard to ensure complete compliance."<o:p></o:p> <div> -- <o:p></o:p> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="400" style="width:300.0pt"> <tbody> <tr> <td width="180" valign="top" style="width:135.0pt;padding:0cm 0cm 0cm 0cm"> <a href="http://v4escrow.net" target="_blank"><img border="0" width="178" height="96" id="_x0000_i1025" src="cid:image001.png@01D05B11.E2664830"></a><o:p></o:p> </td> <td width="200" valign="top" style="width:150.0pt;padding:0cm 0cm 0cm 0cm"> <h1 style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:7.5pt;margin-left:0cm"> Elvis Daniel Velea<o:p></o:p></h1> <h2 style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:7.5pt;margin-left:0cm"> Chief Executive Officer<o:p></o:p></h2> Email: <a href="mailto:elvis@v4escrow.net">elvis@V4Escrow.net</a> US Phone: +1 (702) 475 5914 EU Phone: +31 (0) 61458 1914<o:p></o:p> </td> </tr> <tr> <td colspan="2" style="padding:0cm 0cm 0cm 0cm"> Recognised IPv4 Broker/Facilitator in:<o:p></o:p> </td> </tr> <tr> <td colspan="2" style="padding:0cm 0cm 0cm 0cm"> <![if !vml]><map name="MicrosoftOfficeMap0"><area shape="Rect" coords="0, 2, 64, 28" href="http://www.ripe.net/lir-services/resource-management/ipv4-transfers/brokers" target="_blank"><area shape="Rect" coords="137, 0, 233, 31" href="http://www.apnic.net/services/become-a-member/manage-your-membership/transfer-resources/transfer-facilitators" target="_blank"><area shape="Rect" coords="296, 3, 379, 40" href="https://www.arin.net/resources/transfer_listing/facilitator_list.html" target="_blank"></map><img border="0" width="379" height="40" src="cid:image002.png@01D05B11.E2664830" usemap="#MicrosoftOfficeMap0" v:shapes="_x0000_s1026 _x0000_s1027 _x0000_s1028 _x0000_s1029"><![endif]><img border="0" width="376" height="28" id="_x0000_i1026" src="cid:image003.png@01D05B11.E2664830"><o:p></o:p> </td> </tr> <tr> <td colspan="2" style="padding:0cm 11.25pt 0cm 3.75pt"> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received this email in error, please notify the sender immediately and delete the original.Any other use of this email is strictly prohibited.<o:p></o:p> </td> </tr> </tbody> </table> <o:p> </o:p> </div> </div> </body> </html>