<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> </head> <body> <div dir="ltr"> <div></div> <div> <div> <div dir="ltr"> <div dir="ltr" style="">In the GM a few weeks ago, resolution 4 or the proposal for charging 50 eur/ASN, which was <span style="background-color:rgb(255, 255, 255);text-decoration:none;display:inline !important">presented by NCC management and supported by the board, I believe, </span>was not adopted. The 67% of the membership votes cast or approximately 1500 votes were against<span id="ms-outlook-ios-cursor"></span>.</div> <div dir="ltr" style=""><br> </div> <div dir="ltr" style=""><br> </div> </div> </div> <div id="ms-outlook-mobile-signature"> <div><br> </div> <div dir="ltr"> <div dir="ltr">Kaj</div> <div dir="ltr"><br> </div> <div dir="ltr">Sent from my iPad</div> <div dir="ltr"><br> </div> </div> </div> <div id="mail-editor-reference-message-container" class="ms-outlook-mobile-reference-message"> <hr style="display:inline-block;width:98%" tabindex="-1"> <div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif"><b>From:</b> address-policy-wg <address-policy-wg-bounces@ripe.net> on behalf of Nick Hilliard <nick@foobar.org><br> <b>Sent:</b> Thursday, June 8, 2023 5:55 PM<br> <b>To:</b> Marco Schmidt <mschmidt@ripe.net><br> <b>Cc:</b> address-policy-wg@ripe.net <address-policy-wg@ripe.net><br> <b>Subject:</b> Re: [address-policy-wg] Input Requested: How to Ensure Responsible ASN Resource Management <div> </div> </font></div> <meta name="Generator" content="Microsoft Exchange Server"> <font size="2"><span style="font-size:11pt;"> <div class="PlainText">Marco Schmidt wrote on 08/06/2023 14:30:<br> > We also plan to intensify our ongoing project to clean up unused <br> > Autonomous System (AS) Numbers [2]. Almost 2,000 unused ASNs have been <br> > recovered as part of this work so far. Do you support our approach here? <br> > And are there other ways we could improve the situation? Perhaps you <br> > could add clarification on requesting and returning ASNs in the relevant <br> > RIPE policy, or maybe we could give a stronger mandate and <br> > responsibility to the sponsoring LIRs.<br> <br> Hi Marco,<br> <br> There are good reasons to clean up unused ASN16s, as they are <br> categorised by policy as scarce resources. There isn't a compelling <br> reason to get as excited about ASN32s, other than to say that normal <br> good stewardship practices should apply.<br> <br> Unfortunately there is a disconnect between RIPE policy and RIPE NCC <br> practice in regard to charges for ASNs. This is a real shame because <br> paying for resources is one of the simpler ways of creating positive <br> pressure to return them if they're unused. The community would benefit <br> from the board re-thinking this.<br> <br> Nick<br> <br> -- <br> <br> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a><br> </div> </span></font></div> </div> </div> </body> </html>