<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
On Jul 6, 2015, at 12:41 PM, William Herrin <<a href="mailto:bill@herrin.us" class="">bill@herrin.us</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class="">On Mon, Jul 6, 2015 at 12:08 PM, Milton L Mueller <<a href="mailto:mueller@syr.edu" class="">mueller@syr.edu</a>> wrote:<br class="">
<blockquote type="cite" class="">
<blockquote type="cite" class="">start from the perspective that<br class="">
it is simply to clarify that the resources are for global use, and ARIN's role is<br class="">
simply to be a facilitator within a reasonably local time-zone, and having<br class="">
local language support. Any language that implies that there is a limitation<br class="">
to use needs to be removed, or an explanation as to why that restriction is<br class="">
any different than nationally aligned allocations needs to be added.<br class="">
</blockquote>
<br class="">
That kind of language/approach is how I intended to follow up on the failure of the old Out of Region Use proposal.<br class="">
Such a proposal should probably be conceived as a global policy rather than an ARIN policy, however.<br class="">
</blockquote>
<br class="">
Yes, a global policy. No single region alone has the right. And a very<br class="">
carefully conceived policy at that, lest the subregistries in each<br class="">
region subvert it in various anticompetitive ways.</div>
</blockquote>
</div>
<div><br class="">
</div>
<div>Bill - </div>
<div><br class="">
</div>
<div>In general, the Internet numbers community has used the term “global policy” to refer to policy </div>
<div>that is used by IANA in administration of the global unicast number resource free pools, and </div>
<div>has used the term “globally coordinated policy” to refer to policy that was developed with the </div>
<div>intent of global scope, but is ultimately adopted by each RIR community for use during the</div>
<div>administration of their respective regional Internet number registry.</div>
<div><br class="">
</div>
<div>In this case, it may not matter which term you use, as the policy that you seek to establish may </div>
<div>be more fundamental in nature, i.e. related to requirements presently embedded within ICANN </div>
<div>Internet Coordination Policy 2 (ICP-2) <<a href="https://www.icann.org/resources/pages/new-rirs-criteria-2012-02-25-en" class="">https://www.icann.org/resources/pages/new-rirs-criteria-2012-02-25-en</a>></div>
<div>ICP-2 is likely long overdue for a refresh at this point, and if there were a group of brave souls</div>
<div>who wished to take that on (in conjunction with the ASO AC), we might be able to achieve a </div>
<div>framework more suitable for the years that lie ahead...</div>
<div><br class="">
</div>
<div>Thanks!</div>
<div>/John</div>
<div><br class="">
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br class="">
</div>
</body>
</html>