<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="">
<div class="">On 30 Apr 2018, at 4:47 PM, John Curran <<a href="mailto:jcurran@arin.net" class="">jcurran@arin.net</a>> wrote:<br class="">
<div>
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class="">
<div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
<div dir="auto" class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">
On 2 Feb 2018, at 8:59 AM, ARIN <<a href="mailto:info@arin.net" class="">info@arin.net</a>> wrote:<br class="">
<div class="">
<blockquote type="cite" class=""><br class="Apple-interchange-newline">
<div class="">
<div class="">As a part of the Number Resource Organization (NRO), ARIN is seeking<br class="">
community input on the NRO community consultation on the ASO review.<br class="">
<br class="">
"The most recent ASO Review concluded with 18 recommendations, which the<br class="">
NRO has resolved to accept. The first 17 recommendations are well<br class="">
defined and practical, and can be implemented by actions of the NRO<br class="">
Secretariat, or of the ASO Address Council, with respect to<br class="">
administrative procedures, documentation, or in some cases adjustments<br class="">
to agreements which are expected to be non-controversial.<br class="">
<br class="">
The 18th recommendation of the Report is that "The NRO should initiate a<br class="">
public consultation, involving the five RIR communities, to determine<br class="">
the future structure of the ASO". The NRO EC has concluded to accept<br class="">
that recommendation and is hereby launching a consultation on the issues<br class="">
identified in the ASO Review Report."<br class="">
<br class="">
The full Consultation is available for review at:<br class="">
<br class="">
<a href="https://www.nro.net/aso-review-consultation-2018/" class="">https://www.nro.net/aso-review-consultation-2018/</a></div>
</div>
</blockquote>
<br class="">
</div>
<div class="">ARIN-Consult community:</div>
<div class=""><br class="">
</div>
<div class="">On Monday, 16 April 2018 (day 1 of the ARIN 41 Public Policy Meeting in Miami), a consultation session was held to gather additional input for this community consultation on the future structure of the ASO. As reported during that session, I
took on the responsibility to provide a brief summary of the discussion to this mailing list. Those interested in the full meeting transcript may review it here: <a href="https://www.arin.net/vault/participate/meetings/reports/ARIN_41/ppm.html" class="">https://www.arin.net/vault/participate/meetings/reports/ARIN_41/ppm.html</a></div>
<div class=""><br class="">
</div>
<div class="">In summary:</div>
<div class=""><br class="">
</div>
<div class="">1) Unlike the comments received on the arin-consult mailing list to date, the prevailing view was that the number community relationship with ICANN (that which is referred as the ASO relationship) should continue – presuming that it can be significantly
simplified and kept focused on number community matters</div>
<div class=""><br class="">
</div>
<div class="">2) It is important that ICANN recognize that the number community is not a typical ICANN Supporting Organization, and our engagement with ICANN serves primarily to facilitate interactions on number resource policy matters. This scope of the
number community engagement with ICANN needs to be made plain to the ICANN community, and both the NRO-EC and ASO AC need to be diligent in declining invitations that that lie outside this scope. </div>
<div class=""><br class="">
</div>
<div class="">3) Since the use of two names (“NRO” & “ASO”) increases confusion in the ICANN relationship, the number community should engage with ICANN as the Number Resource Organization (NRO), with the NRO Number Council (NRO NC) continuing to handle global
policy development and ICANN Board election matters as usual. </div>
<div class=""><br class="">
</div>
<div class="">4) More significant changes to the number community/ICANN relationship should be deferred for a future review cycle, as there is presently value in the relationship that should be preserved (presuming that it can be simplified as noted above.) </div>
<div class=""><br class="">
</div>
<div class="">Comments on this summary are most welcome - Thanks!</div>
<div class="">/John</div>
<div class=""><br class="">
</div>
<div class="">John Curran</div>
<div class="">President and CEO</div>
<div class="">ARIN</div>
</div>
</div>
</div>
</blockquote>
<br class="">
</div>
</div>
<div><br class="">
</div>
<div class="">ARIN Community - </div>
<div class=""><br class="">
</div>
<div class="">As an update, it is worth noting that consultations on the future structure of the ASO continue in several of the other RIR regions.</div>
<div class=""><br class="">
</div>
<div class="">Yesterday, the NRO-EC made the following statement (based on its consideration of results of this process to date) - </div>
<div class=""><br class="">
</div>
<div class=""><span class="Apple-tab-span" style="white-space:pre"></span><<a href="https://www.nro.net/input-by-the-nro-executive-council-on-the-public-consultation-to-determine-the-future-structure-of-the-aso/" class="">https://www.nro.net/input-by-the-nro-executive-council-on-the-public-consultation-to-determine-the-future-structure-of-the-aso/</a>></div>
<div class=""><br class="">
</div>
The NRO EC provides this statement to the RIR communities in each region as a possible common way forward to aid in their consideration of the future structure of the ASO.<br class="">
<div class=""><br class="">
</div>
<div class="">FYI,</div>
<div class="">/John</div>
<div class=""><br class="">
</div>
<div class="">John Curran</div>
<div class="">President and CEO</div>
<div class="">American Registry for Internet Numbers</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
</body>
</html>