<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 Apr 12, 2015, at 1:53 PM, Milton L Mueller <<a href="mailto:mueller@syr.edu" class="">mueller@syr.edu</a>> wrote:<br class="">
<div>
<blockquote type="cite" class="">...<br class="Apple-interchange-newline">
<div class="">
<div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<span style="font-size: 11pt;" class="">Counsel states:</span></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
"ARIN is governed by ICANN ICP-2, which calls for establishment of a single RIR to serve each region."<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""> </o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Regional exclusivity is one of the more interesting and far-ranging issues raised by 2014-1. We need to have a clear and honest discussion of it.
</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
Indeed.</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
Counsel is claiming that ICP-2 requires all usage of numbers to be bound to exclusive RIR service regions</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Milton - </div>
<div> </div>
<div> Please provide reference for your statement above; I am unaware of any statement by ARIN's</div>
<div> Counsel that "ICP-2 requires all usage of numbers to be bound to exclusive RIR service regions”</div>
<div> i.e. it would appear that you are ascribing statements to ARIN Counsel that were not actually</div>
<div> made (and ddespite the rather laudable goal of clear and honest discussion.)</div>
<div> </div>
<div> For reference, the full paragraph regarding ICP-2 from the staff and legal assessment follows - </div>
<div><br class="">
</div>
<div>
<div class=""></div>
<blockquote type="cite" class="">
<div class=""></div>
<blockquote type="cite" class="">
<div class="">First, ARIN is governed by ICANN ICP-2, which calls for establishment of </div>
<div class="">a single RIR to serve each region. It further notes that multiple RIRs </div>
<div class="">serving in single region is likely to lead to difficulty for </div>
<div class="">co-ordination and co-operation between the RIRs as well as confusion for </div>
<div class="">the community within the region. The implication of that governance </div>
<div class="">structure is that each RIR can and should serve its service region. This </div>
<div class="">policy would allow entities with no real connection to the ARIN's </div>
<div class="">service region to obtain, for example, increasingly scarce IPv4 </div>
<div class="">resources from ARIN and related registry services. This policy would </div>
<div class="">result in ARIN effectively providing registry services to other regions, </div>
<div class="">and thus appears on its face to be inconsistent with ICP-2. ARIN has </div>
<div class="">obligations to follow the global policy in ICP2, or seek changes in it.</div>
</blockquote>
<blockquote type="cite" class=""></blockquote>
</blockquote>
<div class=""><br class="Apple-interchange-newline">
</div>
<div class=""> The paragraphs notes that providing resources which are for use entirely out of region </div>
<div class=""> may be inconsistent with ICP-2; it makes no statement that _all usage_ of ARIN-issued </div>
<div class=""> resources are bound to the service region. Note that organizations that receive numbers </div>
<div class=""> resources presently from ARIN often do make some use of them in other regions.</div>
<div class=""><br class="">
</div>
<div class=""> The statement in the staff and legal assessment is with regarding to issuing number </div>
<div class=""> resources to a party where it is clear that they are solely for use outside the ARIN </div>
<div class=""> service region, i.e. this is not a case of incidental use, or someone repurposing an</div>
<div class=""> address block, but instead ARIN knowingly providing registry services and resources</div>
<div class=""> to other region. </div>
<div class=""> </div>
</div>
<blockquote type="cite" class="">
<div class="WordSection1" style="page: WordSection1; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt;" class="">
But this claim has no basis in either ICP-2 itself nor in operational practice.<o:p class=""></o:p></div>
<font face="Calibri, sans-serif" class=""><span style="font-size: 15px;" class="">...</span></font><br class="">
<div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt;" class="">
- Even assuming that service regions shouldn’t overlap, ICP-2 does not articulate or establish a policy regarding use of number resources outside of a RIR’s service region.</div>
</div>
</blockquote>
<div><br class="">
</div>
You are correct - ICP-2 does not articulate any policy regarding _use_ of number </div>
<div> resources outside of a RIR’s service region, however, ICP-2 does identify issues </div>
<div> that can result from RIRs operating in the same region and thus supports the </div>
<div> actual statements which are within the staff and legal assessment. i.e. to the effect</div>
<div> that adoption of 2014-1 draft policy would result in ARIN effectively providing registry </div>
<div> services to other regions, it would appears on its face to be inconsistent with the </div>
<div> intent and language of ICP-2, as follows below - </div>
<div><br class="">
</div>
<div>"Each region should be served by a single RIR, established under one management and in one location. The establishment of multiple RIRs in one region is likely to lead to:</div>
<br class="">
<div class=""><span class="Apple-tab-span" style="white-space:pre"></span>• fragmentation of address space allocated to the region; <br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"></span>• difficulty for co-ordination and co-operation between the RIRs; <br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"></span>• confusion for the community within the region.”</div>
<div class=""><br class="">
</div>
<div class=""> Now it is possible that ICP-2 is rather dated and could use to be refreshed to look </div>
<div class=""> forward to the future which there is not significant new address allocations being </div>
<div class=""> made every day and where inter-RIR transfers already pose similar issues; however, </div>
<div class=""> that is probably a much larger discussion and ICP-2 stands as-is in the meantime.</div>
<div><br class="">
</div>
<div>
<blockquote type="cite" class="">
<div class="">
<div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
- ICP-2 is not a law, and thus raises no legal issues;<span class="Apple-converted-space"> </span></div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
ARIN’s compliance with its agreements to other parties can result in legal issues for </div>
<div> ARIN, and ARIN has an agreement with ICANN (ASO MOU) which directly incorporates </div>
<div> and references ICP-2.</div>
<div> </div>
<div>
<blockquote type="cite" class="">
<div class="">
<div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
<o:p class=""></o:p></div>
<div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">
- ICP-2 is not even a global policy, as its development and adoption by the ICANN board antedates the global policy development process </div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
ICP-2 is identified in the ASO MOU as containing "agreed requirements and policies”</div>
<div><br class="">
</div>
<div> It would be helpful to understand if you feel that there is no or nominal risk to the ARIN </div>
<div> community to setting aside the principles contained in ICP-2; if that is the case, then it</div>
<div> might be best to simply state that as your position. The guidance from ARIN Counsel</div>
<div> that we have obligations with respect to ICP-2 is quite clear, but that doesn’t preclude </div>
<div> the possiblity that there be nominal actual consequence (w.r.t. our relation with ICANN) </div>
<div> from doing otherwise.</div>
<div><br class="">
</div>
<div>Thank you,</div>
<div>/John</div>
<div><br class="">
</div>
<div>John Curran</div>
<div>President and CEO</div>
<div>ARIN</div>
<div><br class="">
</div>
<div><br class="">
</div>
</body>
</html>