<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 28/03/15 22:43, LeaderTelecom Ltd.
wrote:<br>
</div>
<blockquote
cite="mid:1427579035.597050.254699434.735516.2@otrs.hostingconsult.ru"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
>�I disagree. At least, some members were satisfied with ASN
charge abolishment.<br>
And please, find some new arguments before introducing ASN charge
again. Garbage<br>
collection is not so important in terms of AS numbers.<br>
<br>
Sergey, I support your idea. Doesn't make sense to change anything
regards payments for ASN. Billing is more easy for RIPE NCC. And
this discussion started from garbage collection of ASN.<br>
<br>
</blockquote>
+1<br>
<br>
I think that if garbage collection is the problem, then we should
focus on garbage collection and ask the RIPE NCC what methods it
would see viable (including or excluding the ASN charge). We should
leave the Charging Scheme be, as it is one of the cleanest I have
seen and I remember (although I was not in that meeting in 2012)
that everyone appreciated a clean/simple CS.<br>
<br>
As for the discussion regarding ASN returns, I think we have a lot
of noise for nothing.. <br>
<br>
Firstly, the internet is using ~65K ASNs while the supply is 2MM. We
still have 64K*65K before we should really worry about garbage
collection.<br>
Secondly - since my company offers consulting services for various
companies in the region, I have noticed that many customers have
returned ASNs to the RIPE NCC after an M&A, so it's not like
they keep on holding them without a reason.. Although I would see
why 32bit ASNs could, soon, have a value (especially the 'vanity'
ones).<br>
Thirdly, I have already proposed a method, which does not ask the
NCC to chase but just to send a question to its members once a year,
asking them if they or their customer want to return the ASN that
has not been seen in the global routing table for more than 3
months. Such a script should be simple to make and would not involve
any follow-up from the NCC nor any chasing of the members. If the
members do respond and return any of the ASNs, then the garbage
collection mechanism has fulfilled it's purpose.<br>
<br>
regards,<br>
Elvis<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.07000701.06010307@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.00050904.07000608@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>