<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=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 3, 2021, at 05:56 , John Curran <<a href="mailto:jcurran@arin.net" class="">jcurran@arin.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
NANOGers -
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">
<div class="">The following process change is being proposed in order to simplify customer request tickers for new number resources and improve overall service. </div>
<div class=""><br class="">
</div>
<div class="">If you have strong feelings one way or the other, thenplease join the arin-consult list and make them known. (Note - the arin-consult mailing list is open to all in accordance with ARIN’s Mailing List AUP and Standards of Behavior.)</div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">Thanks! </div>
<div class="">/John</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">John Curran</div>
<div class="">President and CEO</div>
<div class="">American Registry for Internet Numbers</div>
</div>
<div class="">
<div class=""><br class="">
<blockquote type="cite" class="">
<div class="">Begin forwarded message:</div>
<br class="Apple-interchange-newline">
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;" class=""><b class="">From:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">ARIN <<a href="mailto:info@arin.net" class="">info@arin.net</a>><br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;" class=""><b class="">Subject:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">[ARIN-consult] Consultation on Retiring the Officer Attestation Requirement</b><br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;" class=""><b class="">Date:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">3 August 2021 at 8:13:53 AM EDT<br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, "Helvetica Neue", Helvetica, sans-serif;" class=""><b class="">To:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><<a href="mailto:arin-consult@arin.net" class="">arin-consult@arin.net</a>><br class="">
</span></div>
<br class="">
<div class="">
<div class="">ARIN regularly reviews existing processes as part of our continual improvement efforts to be more responsive and improve the service our customers receive from ARIN. Recently ARIN reviewed the Officer Attestation process and as a result of that
review have determined the Officer Attestation process is no longer necessary for achievement of its original goals and should be retired. The purpose of this consultation is to review this proposed change with the community prior to its implementation.<br class="">
<br class="">
The Officer Attestation was introduced in 2007 in preparation for the depletion of IPv4 addresses. Currently, ARIN requires an Officer Attestation for all requests that involve a needs analysis (which today consist of waiting list requests, NRPM 4.4 micro-allocations,
NRPM 4.10 IPv6 transition, IPv6 requests, and transfer recipient requests.)<br class="">
<br class="">
However, conditions have changed since this requirement was established, and ARIN believes that the Officer Attestation for resource request tickets is no longer necessary for the following reasons:<br class="">
<br class="">
- Today IPv4 resources are issued by ARIN predominantly via the Waitlist policy, and this policy has been revised to only allow one small request per party (thus avoiding the original risk of “hoarding” via large suspect requests prior to runout).<br class=""></div></div></blockquote></div></div></div></div></blockquote><div><br class=""></div>Correct me if I am wrong, John, but I believe this is one small request per party at a time, not for all time. (e.g. unlike APNIC’s original final /22 per member policy for their last /8, ARIN does allow an organization to apply to the waitlist, receive addresses, then upon utilization of those addresses apply to the waitlist again).</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div class="">
- With regard to transfers of IPv4 resources obtained via the transfer market, the inherent costs for large transfers ensures organizational officers are “in the know”.<br class="">
- Given IPv6 availability, officer attestation of need for IPv6 resources is not necessary.<br class=""></div></div></blockquote></div></div></div></div></blockquote><div><br class=""></div>Interesting reversal. I argued when officer attestation was first introduced that applying it to IPv6 was silly and you were among those expressing skepticism. What brings about this change of heart? IPv6 is certainly no more plentiful today than it was back then.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div class="">
The review identified that at this point in time the Officer Attestation process is problematic for many customers, predominantly posing an administrative burden that does not materially improve policy implementation and resulting in numerous complaints and
adding unnecessary delay (varying between two days and an entire week) to completion of resource request tickets.<br class=""></div></div></blockquote></div></div></div></div></blockquote><div><br class=""></div>It’s a small administrative burden, but despite processing requests for many clients of a variety of sizes and assisting many other clients of significant size in handling their own requests, I have not encountered a single environment where I would call it “problematic”.</div><div><br class=""></div><div>I have always felt that it did not materially improve policy implementation with regard to IPv6 and I stand by that sentiment.</div><div><br class=""></div><div>I remain unconvinced that it is unimportant for IPv4, despite the escalating costs of IPv4 addresses.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div class="">
In light of the administrative burden to customers and undefined benefit, ARIN proposes dropping the Officer Attestation requirement – note that this specifically does not change documentation requirements related organization recovery of IP number resources
or related anti-fraud measures that ARIN has implemented.<br class=""></div></div></blockquote></div></div></div></div></blockquote><div><br class=""></div>I think removing this requirement for IPv4 is premature at best.</div><div><br class=""></div><div>I think removing this requirement for IPv6 is long overdue as it has never served a policy purpose.</div><div><br class=""></div><div>Owen</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class=""><div class="">
<br class="">
This consultation will remain open for 10 days.<br class="">
<br class="">
Please provide comments to <a href="mailto:arin-consult@arin.net" class="">arin-consult@arin.net</a>. You can subscribe to this mailing list at:
<a href="http://lists.arin.net/mailman/listinfo/arin-consult" class="">http://lists.arin.net/mailman/listinfo/arin-consult</a>.<br class="">
<br class="">
Discussion on <a href="mailto:arin-consult@arin.net" class="">arin-consult@arin.net</a> will close on 13 August 2021.<br class="">
<br class="">
Regards,<br class="">
<br class="">
John Curran<br class="">
President and CEO<br class="">
American Registry for Internet Numbers (ARIN)<br class="">
<br class="">
_______________________________________________<br class="">
ARIN-Consult<br class="">
You are receiving this message because you are subscribed to the ARIN Consult Mailing<br class="">
List (<a href="mailto:ARIN-consult@arin.net" class="">ARIN-consult@arin.net</a>).<br class="">
Unsubscribe or manage your mailing list subscription at:<br class="">
<a href="https://lists.arin.net/mailman/listinfo/arin-consult" class="">https://lists.arin.net/mailman/listinfo/arin-consult</a> Please contact the ARIN Member Services<br class="">
Help Desk at <a href="mailto:info@arin.net" class="">info@arin.net</a> if you experience any issues.<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div></blockquote></div><br class=""></body></html>