<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 25, 2011, at 2:35 PM, John Curran wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>On Feb 26, 2011, at 4:26 AM, Benson Schliesser wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>
<div>
<div>
<div>What I don't see is anything limiting the formation of a registry/registrar system, post-allocation services, etc, especially if done within the scope of a single region. While prop 136 doesn't directly call for the formation of a registrar system or
post-allocation services, I admit that it does imply the opportunity. However, there is no requirement that "replacement directory services" are provided by a third party - I imagine that the address holder can provide a directory service for themselves.</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<span class="Apple-style-span" style="font-family: monospace; ">Again: if such registries where </span><span class="Apple-style-span" style="font-family: monospace; ">allowed under ARIN's local policy </span></div>
<div><span class="Apple-style-span" style="font-family: monospace; ">framework, then ICP-2 states that</span><span class="Apple-style-span" style="font-family: monospace; "> </span><span class="Apple-style-span" style="font-family: monospace; ">ARIN's policies
would need to apply </span></div>
<div><span class="Apple-style-span" style="font-family: monospace; ">in a fair and equitable manner </span><span class="Apple-style-span" style="font-family: monospace; ">these entities just as they apply to </span></div>
<div><span class="Apple-style-span" style="font-family: monospace; ">ISP's </span><span class="Apple-style-span" style="font-family: monospace; ">in the region. Does that </span><span class="Apple-style-span" style="font-family: monospace; ">actually meet your
requirements for </span></div>
<div><span class="Apple-style-span" style="font-family: monospace; "></span><span class="Apple-style-span" style="font-family: monospace; ">"opting out"? </span><span class="Apple-style-span" style="font-family: monospace; ">I expected otherwise from the policy</span><span class="Apple-style-span" style="font-family: monospace; "> </span><span class="Apple-style-span" style="font-family: monospace; ">background
statement</span></div>
<div><span class="Apple-style-span" style="font-family: monospace; ">as the policies adopted in the ARIN region would apply fully to any</span></div>
<div><span class="Apple-style-span" style="font-family: monospace; ">such </span><span class="Apple-style-span" style="font-family: monospace; ">"replacement directory services."</span></div>
</div></blockquote><br></div><div>Thanks for your clarification, John. Perhaps I understand you correctly now. To rephrase what I hear you saying: As a result of RIR recognition by ICANN per ICP-2, ARIN has a responsibility to apply address management policy to all organizations within their region, and is not permitted to allow anybody to opt-out of that policy. Have I captured your meaning correctly?</div><div><br></div><div>Thanks,</div><div>-Benson</div><div><br></div><br></body></html>