<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Wilfried,<br>
<br>
I agree with you in both scenarios you described below.<br>
However, the reality of the current world is not that simple.<br>
<br>
IP addresses have a value, whether we want to acknowledge that
fact or not.<br>
<br>
Some holders of PI address space have also realized that their PI
space has some value, some will do the right thing and become LIRs
in order to convert the PI to PA and then transfer the space. This
policy proposal does not intend to address these users, the ones
that will do the right thing by becoming a member and paying their
share.<br>
<br>
Some others, will just transfer the space (by making a
contract/document/agreement between them and an other party) or
just allow someone else to use the address space without any
notification to the RIPE NCC or updates in the registry.<br>
While these are the 'bad guys' and I do not thing we should be
making policy changes to encourage them, by not making a policy
change the registry will suffer. Not everyone will give up on
their PI space if they do not use it anymore. Especially if they
receive e-mails from people that want to 'rent/lease' their space
for some money.<br>
<br>
I still don't know if it's a good thing to allow PI transfers and
have individuals or companies that have only been paying 50E/year
to transfer (sell) their PI space for a nice profit <br>
AND<br>
keep the registry as clean and updated as possible.<br>
<br>
OR.. give the RIPE NCC a mandate to start hunting those that
violate the PI policy<br>
<br>
OR.. just pretend there's no problem and accept that the registry
data may get outdated with time.<br>
<br>
my 2 cents,<br>
elvis<br>
<br>
On 24/04/14 17:24, Wilfried Woeber wrote:<br>
</div>
<blockquote cite="mid:53592CAA.2090608@CC.UniVie.ac.at" type="cite">
<pre wrap="">A couple of observations, fwiw, and no, I'm not going to assess the role
of brokers :-)
In general, let me start with the statement that I support all ideas to
get rid of the different shapes and colours of address blocks. And that
actually includes Legacy, as they are simply PI, just a tad older...
How to deal with moving address space from a PI assignment to a different
party?
Well, I can see 2 *substantially* different scenarios:
1) the current holder of the address block doesn't need *all of it* any longer
(and wants to get money from an interested party, but that's a side issue).
2) the current holder of the address block doesn't need *any* of the addresses
any longer and wants to transfer the full block, in one chunk or in smaller
pieces.
Nr. 1 is pretty easy, and possible already or really soon now: convert the
PI block to PA, thus become an LIR, and proceed according to the rules.
Nr. 2 is more tricky. First of all, there was a good reason, why the resource
was tightly bound to the requester. That background and assumption is also
part of the basis for the low annual fee of �50,- per resource.
Now, as soon as the original criteria are no longer in place, the resource
MUST be returned. A PI holder offering the *full block* to an interested party
(for money or for free) obviously matches that provision. The resource needs
to get returned to the pool.
So, why would we want to bend into this direction or that direction to create
a special case for Nr. 2 to circumvent the existing policy? Just because some
money is seen on the horizon?
Which gets me to the point of *not* supporting this proposal!
Wilfried.
</pre>
</blockquote>
<br>
<br>
<div class="moz-signature">-- <br>
<table border="0" cellpadding="0" cellspacing="0" width="400">
<tbody>
<tr>
<td valign="top" width="180"><a href="http://v4escrow.net"
target="_blank"><img
src="cid:part1.07030504.04080801@v4escrow.net"
style="margin:10px 40px 0px 0px" height="96"
width="178"></a></td>
<td valign="top" width="200">
<h1 style="font-family: Arial, Helvetica, sans-serif;
font-size: 14px; color: rgb(51, 51, 51); margin: 0px 0px
10px;color:#1a9bd7;font-size:14px; ">Elvis Daniel Velea</h1>
<h2 style="font-family: Arial, Helvetica, sans-serif;
font-size: 14px; color: rgb(51, 51, 51); margin: 0px 0px
10px;color:#74757d;font-size:13px;font-weight:100; ">Chief
Business Analyst</h2>
<p style="font-family:Arial, Helvetica, sans-serif;
font-size:12px; line-height:20px; font-weight:regular;
color:#74757d; margin:5px 0px;"> <span
style="color:#000;">Email:</span>�<a
href="mailto:elvis@v4escrow.net" style="color:#74757d;
text-decoration: none; ">elvis@V4Escrow.net</a><br>
<span style="color:#000;">US Phone:</span>�+1�(702)�475�5914<br>
<span style="color:#000;">EU Phone:</span>�+3�(161)�458�1914<br>
</p>
</td>
</tr>
<tr>
<td colspan="2">
<p style="font-family:Arial, Helvetica, sans-serif;
font-size:12px;
line-height:15px;color:#000;margin-top:15px;text-align:center;"
align="center">Recognised IPv4 Broker/Facilitator in:</p>
</td>
</tr>
<tr>
<td colspan="2"> <img
src="cid:part4.03000708.03030109@v4escrow.net"
usemap="#Map" style="margin-top:5px;" border="0"
height="28" width="376"> </td>
</tr>
<tr>
<td colspan="2" style="padding-left:5px;padding-right:15px;">
<p style="color:#bbb;font-family: Arial, Helvetica,
sans-serif;font-size:10px;margin-top:15px;text-align:center;">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.</p>
</td>
</tr>
</tbody>
</table>
<map name="Map">
<area shape="rect" coords="1,2,65,28"
href="http://www.ripe.net/lir-services/resource-management/ipv4-transfers/brokers"
target="_blank">
<area shape="rect" coords="138,0,234,31"
href="http://www.apnic.net/services/become-a-member/manage-your-membership/transfer-resources/transfer-facilitators"
target="_blank">
<area shape="rect" coords="297,3,380,40"
href="https://www.arin.net/resources/transfer_listing/facilitator_list.html"
target="_blank">
</map>
</div>
</body>
</html>