<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 Nick,<br>
<br>
On 13/01/15 16:57, Nick Hilliard wrote:<br>
</div>
<blockquote cite="mid:54B54053.6040501@inex.ie" type="cite">
<pre wrap="">On 13/01/2015 14:46, Gert Doering wrote:
</pre>
<blockquote type="cite">
<pre wrap="">So your suggestion would be to stall this proposal until we know what
comes out of the next AGM, and then see if we need the clause in
question at all, anymore?
</pre>
</blockquote>
<pre wrap="">
yes, that was my suggestion. The current configuration is stable, so there
are no pressing operational reasons to change things in a hurry. If we're
going to change, we need to do that's best for N years down the road, not
what's best for a couple of months during 2015.
</pre>
</blockquote>
I do not think it is a good idea to stall a policy proposal in order
to see if the Board/AGM decides to take into consideration or ignore
in the future your presentation/proposal from the previous AGM.<br>
I think your suggestion sets a very dangerous precedent where a
policy proposal would be stalled pending a decision that may or not
be taken at the next AGM.<br>
<br>
Regarding the current configuration, well.. it requires the
requester of the ASN to come up with a reason that can not be
verified by the RIPE NCC and with a predicted set of peers that may
or not peer with the assigned ASN. <br>
For example, see the e-mail sent to the members-discuss mailing list
yesterday by Shahin Gharghi; the current policy requires the
requester to list the two ASNs they will peer with, what if some
companies can not peer with two ASNs because of local regulations.
Do you think that company should not receive the ASN they need?<br>
<br>
Also, from your e-mail I understand that you are sure the AGM will
vote within 'a couple of months' to charge for ASNs. Do you know
something that I don't?� :)<br>
<blockquote cite="mid:54B54053.6040501@inex.ie" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">What if the AGM decides to bring back a yearly recurring charge for
ASNs, we loosen up our policy, the AGM decides to remove the charge once
again,
</pre>
</blockquote>
<pre wrap="">
from previous email:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">As a more general issue, we need to accept as a community that there
is a crossover between RIPE Community policy and RIPE NCC membership
policy, and that this is one of those intersections.
</pre>
</blockquote>
</blockquote>
<pre wrap="">
Both the RIPE NCC membership and the AP working group tend to end up with
reasonable policies. I'm pretty confident that this isn't going to change
any time soon.
</pre>
</blockquote>
It has already changed from a year to the other and that is why I
did not like the proposal you made at the previous AGM. We need to
have a charging scheme that is predictable and will not change from
a year to the other. <br>
<br>
I think that if this policy proposal becomes policy and too many
companies start requesting 1000 ASNs, the AGM can react and start
charging (either from the first, the second or the 100th ASN) based
on numbers that the RIPE NCC will provide. I do not like the idea
that a policy proposal can be stalled because someone can imagine a
way the proposal/policy could be abused. If it does get abused, we
react on that and not on predictions.<br>
<blockquote cite="mid:54B54053.6040501@inex.ie" type="cite">
<pre wrap="">
Nick
</pre>
</blockquote>
Regards,<br>
Elvis<br>
<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.06030906.00060502@v4escrow.net"
style="margin:10px 40px 0px 0px" width="178"
height="96"></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
Executive Officer</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>�+31�(0)�61458�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.04010204.04080906@v4escrow.net"
usemap="#Map" style="margin-top:5px;" border="0"
width="376" height="28"> </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>