<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 Aug 16, 2016, at 3:39 PM, John Curran <<a href="mailto:jcurran@istaff.org" class="">jcurran@istaff.org</a>> wrote:<div><blockquote type="cite" class=""> I will add one note to the document, and that is simply that we need to specifically<br class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""> consider SO/AC accountability _with respect to the scope of ICANN’s Mission_,</div><div class=""> rather than in general. For example, the ASO AC may perform activities on behalf </div><div class=""> of the Internet numbers community which are unrelated to the specific tasks in</div><div class=""> the ASO/ICANN agreement and the IETF for all practical matter performs all of</div><div class=""> its activities external to ICANN - It is perfectly reasonable to consider accountability</div><div class=""> of SO/AC’s within ICANN, but that should be for activities also within ICANN. </div><div class=""> This is not an issue with respect to organizations defined entirely by and within</div><div class=""> ICANN, but rather for those communities that organize independently of ICANN</div><div class=""> and have a formal legal agreement of the relationship with ICANN. </div></div></div></blockquote></div><div><br class=""></div><div>Apologies - apparently I was repeating a point (i.e. that the scope of this effort should </div><div>be explicitly defined to be with respect to the role of SO's and AC's within ICANN) that </div><div>was already stated by Athina Fragkouli [an ASO representative to the CCWG WS2] on </div><div>our 4 August call...</div><div><br class=""></div><div>From the transcript - <<a href="https://community.icann.org/pages/viewpage.action?pageId=61604121" class="">https://community.icann.org/pages/viewpage.action?pageId=61604121</a>></div><div><br class=""></div><div></div><blockquote type="cite" class=""><div></div><blockquote type="cite" class=""><div>ATHINA FRAGKOULI:<br class=""></div><div>Yes, thank you very much. The whole project is about ICANN’s accountability. Of course, SOs and ACs have a role and several responsibilities within the ICANN structure. I believe we should be very careful of that because for example, the number policy discussions are not taking place within ICANN. They’re taking place elsewhere, and ASO has a very specific role there. This role is to channel policy proposals that are made elsewhere.</div><div>Some of the accountability tools and measures we discussed might not be applicable in the ASO, for example. I would suggest that it might be appropriate to lead a little bit the scope of this SO/AC accountability in the role of each SO and AC within ICANN. Thank you.</div></blockquote><blockquote type="cite" class=""></blockquote></blockquote><div class=""><br class=""></div><div class="">It might be helpful if this point made into our draft progress report so it does not have </div><div class="">to be restated on each call. </div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">/John</div><div class=""><br class=""></div><div class="">Disclaimer: my views alone.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>