<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Speaking only in my personal capacity and NOT representing ARIN, the AC, or anyone else…</div><div class=""><br class=""></div>It has happened more than once in the ARIN region.<div class=""><br class=""></div><div class="">The two most recent examples are the board suspending issuance from the waiting list due to fraudulent activity and the boards suspension of a policy which allowed for renumber and return to facilitate aggregation (say you had 3 /22s, the policy would allow you to obtain a /20, renumber into that, and subsequently return the 3 /22s, for example).</div><div class=""><br class=""></div><div class="">In the case of the waiting list, there was minimal impact because the AC was able to provide a recommendation to the board for additional protections which went through the community comment period and was implemented before any additional space was ready to be issued to the waiting list. Any impact comes from the additional protections recommended by the AC which include a reduction in the maximum size issued to waiting list participants and additional restrictions on transferring blocks received from the waiting list.</div><div class=""><br class=""></div><div class="">In the case of the renumber and return policy, the AC concurred with the board and the policy was permanently removed from the NRPM (the ARIN equivalent of AfriNIC’s CPD).</div><div class=""><br class=""></div><div class="">For those interested, a GIT repository dating back to the first version of the ARIN Number Resource Policy Manual is available here:</div><div class=""><a href="https://bitbucket.org/arin-rir/number-resource-policy-manual" class="">https://bitbucket.org/arin-rir/number-resource-policy-manual</a></div><div class=""><br class=""></div><div class="">Thanks to Sean Hopkins for his excellent work in creating and maintaining this repository. It has proven a valuable tool in policy development.</div><div class=""><br class=""></div><div class="">The original announcement of this repository is here:</div><div class=""><a href="https://www.arin.net/vault/announcements/2018/20180917_nrpm.html" class="">https://www.arin.net/vault/announcements/2018/20180917_nrpm.html</a></div><div class=""><br class=""></div><div class=""><div>One very useful feature of this is the ability to side-by-side compare two versions of the NRPM. Currently bitbucket only supports inline diff, but they have promised future support for side-by-side diff mode too.</div><div><br class=""></div><div>Owen</div><div><br class=""></div><div><br class=""></div><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 14, 2019, at 02:32 , JORDI PALET MARTINEZ via RPD <<a href="mailto:rpd@afrinic.net" class="">rpd@afrinic.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi Ish,<br class=""><br class="">In all the RIRs there is such board prerogative to halt any policy.<br class=""><br class="">If I recall correctly, it just happened in ARIN a few months ago regarding a waiting list. I don't recall any other case, and this is actually not something needed in the policy text (is already in the bylaws), but I want to bring it just to make sure the community feels "safer".<br class=""><br class="">The other point that you mention, is not covered already with the same point that I'm proposing to add:<br class="">4. The staff can provisionally suspend any suspicious operation that creates a big unbalance against AFRINIC, until the board takes a decision.<br class=""><br class="">So, we don't need to wait for the board decision, the staff will able to suspend any suspicious operation. Then the board decides if this suspension is maintained for that operation, or something different should be done (even halting the policy).<br class=""><br class="">Regards,<br class="">Jordi<br class="">@jordipalet<br class=""><br class=""><br class=""><br class="">El 14/7/19 9:09, "Ish Sookun" <<a href="mailto:ish.sookun@lasentinelle.mu" class="">ish.sookun@lasentinelle.mu</a>> escribió:<br class=""><br class=""> Hi Lee,<br class=""><br class=""> On 7/13/19 11:53 PM, Lee Howard wrote:<br class=""><blockquote type="cite" class="">While I think this is a good idea, I think the idea that the Board could<br class="">halt the inter-RIR transfer if it's too imbalanced makes more sense.<br class=""><br class=""></blockquote><br class=""> The Board intervention sounds more "feasible" than having a complex<br class=""> three-party contract where the risk for the lessee is higher.<br class=""><br class=""> However, the idea I tossed earlier in this thread was to introduce a<br class=""> mechanism that could prevent the moving out of IPv4 addresses en masse,<br class=""> rather than having to rely on Board's intervention. Having a cap on the<br class=""> amount of resources per transfer and limiting the period of transfer<br class=""> could help.<br class=""><br class=""> Do we have any precedent of the Board's intervention in such a case?<br class=""><br class=""> Regards,<br class=""><br class=""> Ish Sookun<br class=""><br class=""> _______________________________________________<br class=""> RPD mailing list<br class=""> <a href="mailto:RPD@afrinic.net" class="">RPD@afrinic.net</a><br class=""> <a href="https://lists.afrinic.net/mailman/listinfo/rpd" class="">https://lists.afrinic.net/mailman/listinfo/rpd</a><br class=""><br class=""><br class=""><br class=""><br class="">**********************************************<br class="">IPv4 is over<br class="">Are you ready for the new Internet ?<br class=""><a href="http://www.theipv6company.com" class="">http://www.theipv6company.com</a><br class="">The IPv6 Company<br class=""><br class="">This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br class=""><br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">RPD mailing list<br class="">RPD@afrinic.net<br class="">https://lists.afrinic.net/mailman/listinfo/rpd<br class=""></div></div></blockquote></div><br class=""></div></body></html>