[address-policy-wg] Use of the Reserved IP Pool

Hi,

you will probably say - you represent a broker so you will not win 
anything if companies will get an additional /22 for free ( someone 
already said that in a previous message - using more or less these 
words) and therefore that is why you are against the proposal.
I will respond saying that Brokers do not really handle /22 
transactions. The amount of work done by a Broker for a transfer takes a 
lot of time. The commission received from a /22 transfer is so tiny that 
it's not really worth it.

I'd also like to provide my input to a few statements below:

On 02/07/14 21:01, Dpto. Datos Television Costa Blanca wrote:
>
> El 02/07/2014 19:25, Tomasz Śląski GMAIL escribió:
>> W dniu 2014-07-02 12:56, Erik Bais pisze:
>>
>>> If you require additional space, other options are :
>>
>>> - Transfer Market
>>
>> Dangerous, you can easily fall victim to fraud, especially on legacy 
>> resources, and RIPE will do nothing to help you.
> True
I would say that it is only dangerous if you have never done business 
before. You should never pay in advance for something that you have not 
yet received. Various types of Escrow agreements or Bank Guarantee 
Letters are used, usually, when an IPv4 allocation is transferred. These 
are processes that do not involve the RIPE NCC but which make the 
transfers happen. Brokers are happy to assist with these processes.
>>
>>> - setup a new LIR
>>
>> It is not obvious. I have an official position from Johem de Ruig 
>> that the new LIR does not always get the allocation.
> Very true
Any new LIR will receive a /22 allocation as long as they can justify 
the use of at least one IP address. The policy is very simple in this 
regard. Off course, if you just open a new LIR to trick the system, you 
may end up not having a justification for that /22 (or that one IP). On 
the other hand, what stops you from opening a new company in a group for 
every 1000 customers? ;)

>>
>>> - buy an existing LIR that is moving out of business.
>>
>> Same as above. RIPE NCC simply just can not accept the transfer, and 
>> you're cooked hard.
> And...also true too!

RIPE NCC can not refuse the merger between two companies. If proper 
documentation is provided and (again) they do not smell the attempt of 
fraud, they will process and merge two LIRs easily. It is when you try 
to fraud or trick the system that you are 'cooked hard'.


To conclude, my point of view is that we already have a process that 
works and that will provide the minimum amount of IP addresses to any 
start-up company for years to come. I do not have my crystal ball with 
me to see whether this will be for 1, 5, 10 or 20 years. I hope it will 
be for 20 years rather than 5.
I say, let's keep the policy as is. Changing it from /22 to /21 will 
bring the pool down to 0 sooner than we expect and that may have really 
bad consequences for any new start-up registered in the RIPE Region.

Kind regards,
elvis
-- 
<http://v4escrow.net> 	


  Elvis Daniel Velea


    Chief Business Analyst

Email: elvis at V4Escrow.net <mailto:elvis at v4escrow.net>
US Phone: +1 (702) 475 5914
EU Phone: +3 (161) 458 1914

Recognised IPv4 Broker/Facilitator in:

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/address-policy-wg/attachments/20140703/29421e2d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo.png
Type: image/png
Size: 5043 bytes
Desc: not available
URL: </ripe/mail/archives/address-policy-wg/attachments/20140703/29421e2d/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1.png
Type: image/png
Size: 11971 bytes
Desc: not available
URL: </ripe/mail/archives/address-policy-wg/attachments/20140703/29421e2d/attachment-0001.png>