<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Tore,<br>
<br>
On 04/03/14 13:16, Tore Anderson wrote:<br>
</div>
<blockquote cite="mid:5315C413.1020808@fud.no" type="cite">
<pre wrap="">* Elvis Daniel Velea
</pre>
<blockquote type="cite">
<pre wrap="">Tore has also pointed out some precedent where ASSIGNED PIs have been
changed to ALLOCATED PAs.
</pre>
</blockquote>
<pre wrap="">
Small correction here, I only noted that there exist some ALLOCATED PA
in the database that are smaller than the minimum allocation size. I do
not know how that came to be, so I don't know if they were ASSIGNED PI
before.</pre>
</blockquote>
thanks for the correction. I was under the impression that you had
remarked PI to PA conversions. I've only now checked the history of
the blocks you have mentioned and these have always been ALLOCATED
PA (with an allocation size lower than the minimum).<br>
<br>
<blockquote cite="mid:5315C413.1020808@fud.no" type="cite">
<pre wrap="">
My point was that the minimum allocation size doesn't appear to be a
hard limit on what is the minimum ALLOCATED PA object that is allowed to
exist in the registry; but rather it should be considered the minimum
allocation size the RIPE NCC is willing to issue[1] new at any given
time. A PI->PA conversion isn't a "new issue" in that way, hence there's
no real reason to apply the minimum allocation size, IMHO. As those
mini-assignments are already in the registry, it doesn't hurt
aggregation either.</pre>
</blockquote>
<br>
I understand and agree with you. However, let's not forget that the
RIPE NCC has made in the past PI assignments of even a /29.<br>
<blockquote cite="mid:5315C413.1020808@fud.no" type="cite">
<pre wrap="">
In any case, it would appear to me that the community is simply waiting
for someone (perhaps you and/or Erik?) to care enough to actually submit
a formal policy proposal to allow for such conversions. The NCC
indicated that they felt clear policy was needed.</pre>
</blockquote>
I see. I was under a different impression, that the community was
waiting for a policy proposal from Erik which would enable PI
transfers. <br>
<br>
Erik, are you working on a proposal that would (also) enable status
changes? Do you need help with it?<br>
<br>
cheers,<br>
elvis<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.05010700.02090606@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.04030505.06040100@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>