<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 Sep 8, 2021, at 19:05 , 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="">
On 8 Sep 2021, at 4:30 PM, Owen DeLong <<a href="mailto:owen@delong.com" class="">owen@delong.com</a>> wrote:<br class="">
<div 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=""><br class="">
<blockquote type="cite" class="">
<div class="">...</div>
</blockquote>
</div>
<div 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="">I am unaware of the ARIN Board ever proposing policy aside from the circumstances in 2009 regarding the need for a usable transfer policy.</div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
Then you are forgetting two additional incidents…</div>
<div class=""><br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"></span>+<span class="Apple-tab-span" style="white-space:pre">
</span>The sudden retirement of the IPv4 aggregation policy</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"></span>+<span class="Apple-tab-span" style="white-space:pre">
</span>The suspension (and subsequent rewrite) of the Waiting List policy</div>
<div class=""><br class="">
</div>
<div class="">Admittedly in both of these cases, the board was suspending/terminating existing policy, but a deletion of a policy or a rewrite still amounts to the board changing policy.</div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
Owen - </div>
<div class=""><br class="">
</div>
<blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">
<div class="">Suspension of policy does not equate to “proposing policy” - The ARIN PDP provides that mechanisms for the ARIN Board to handle the situation where changing circumstance requires that policy be suspended so that the community can have time to review and
develop updated policy as they see fit for the changing circumstances. </div></blockquote></div></div></blockquote><div><br class=""></div>Sure… I’ll bite… But you can suspend enough policy that you simply stop issuing addresses until some change is enacted through some process, so…</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=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class="">
<div class="">The community can only develop policy so quickly, and yet significantly changed circumstances may require that the registry suspend policy to prevent harm to the community and/or the mission. Both of the situations you listed above are cases where the
ARIN Board acted with due care to suspend policy that had a high risk of number resources being issued contrary to the purposes of the current policy and in both cases the community responded with the updated policy it felt most appropriate. </div></blockquote></div></div></blockquote><div><br class=""></div>I’m not arguing that these capabilities are a bad thing… I’m just pointing out that they are circumstances where the board unilaterally changed the operation of the registry by effectively deleting policy (at least temporarily).</div><div><br class=""></div><div>Most people regard a deletion as a form of change.</div><div><br class=""></div><div>Owen</div><div><br class=""></div></body></html>