<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="">All,<div class="">please find below the note we sent to the co-chairs of the CWG. </div><div class=""><br class=""></div><div class="">Thank you for your contributions to this.</div><div class=""><br class=""></div><div class="">Kind regards,</div><div class="">Thomas Rickert<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Anfang der weitergeleiteten Nachricht:</div><br class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Betreff: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">High Level Statements</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Von: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Thomas Rickert <<a href="mailto:rickert@anwaelte.de" class="">rickert@anwaelte.de</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Datum: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">8. Januar 2015 18:07:04 MEZ<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Kopie: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Mathieu Weill <<a href="mailto:Mathieu.Weill@afnic.fr" class="">Mathieu.Weill@afnic.fr</a>>, León Felipe Sánchez Ambía <<a href="mailto:leonfelipe@sanchez.mx" class="">leonfelipe@sanchez.mx</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">An: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">Lise Fuhr <<a href="mailto:lise.fuhr@difo.dk" class="">lise.fuhr@difo.dk</a>>, Jonathan Robinson <<a href="mailto:jrobinson@afilias.info" class="">jrobinson@afilias.info</a>><br class=""></span></div><br class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Dear Lise and Jonathan,</div><div class=""><br class=""></div><div class=""><div class=""><span lang="EN-CA" class="" style="line-height: 12.84000015258789px;">the Cross Community Working Group on Naming Related Functions (CWG-Stewardship) and the Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) are regularly liaising and co-ordinating their work as both work areas are interdependent and interlinked. The co-chairs of both groups have agreed that it would be valuable for the CWG-Stewardship to provide the CCWG-Accountability with a list of issues it has identified during its deliberations where the work of both group overlaps. Subsequently, the following items from the proposal published on Dec. 1st, 2014 have been identified:</span></div><div class=""><span lang="EN-CA" class="" style="line-height: 12.84000015258789px;"><br class=""></span></div><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;"><div class=""><span lang="EN-CA" class="" style="line-height: 12.84000015258789px;"><p class="MsoListParagraphCxSpFirst" style="text-indent: -18pt;"><span lang="EN-CA" class="">·<span class="" style="line-height: normal;"> </span></span><span lang="EN-CA" class="">Section 3.3</span><span lang="EN-CA" class=""> – “Independent Review of Board Actions – the CWG-Stewardship may propose that this becomes binding under certain circumstances directly related to IANA; no other changes proposed”. If this were to be included in the final proposal implementation would require a change to the ICANN Bylaws regarding the IRP.<o:p class=""></o:p></span></p></span></div><div class=""><span lang="EN-CA" class="" style="line-height: 12.84000015258789px;"><p class="MsoListParagraphCxSpMiddle" style="text-indent: -18pt;"><span lang="EN-CA" class="">·<span class="" style="line-height: normal;"> </span></span><span lang="EN-CA" class="">Section 3.4.3.2 - Independent certification for delegation and re-delegation requests</span><span lang="EN-CA" class="">. This is still under consideration by the CWG-Stewardship but would be a replacement for the authorization function for all changes to the Root Zone or its WHOIS Database currently performed by the NTIA. The replacement mechanism would have gTLD requests for delegations and re-delegations authorized by an independent third party and its decision on these matters would be binding on ICANN/IANA. This would probably require modifications to the ICANN Bylaws.<o:p class=""></o:p></span></p></span></div><div class=""><span lang="EN-CA" class="" style="line-height: 12.84000015258789px;"><p class="MsoListParagraphCxSpLast" style="text-indent: -18pt;"><span lang="EN-CA" class="">·<span class="" style="line-height: normal;"> </span></span><span lang="EN-CA" class="">Section 3.4.3.3 - Independent Appeals Panel – </span><span lang="EN-CA" class="">The CWG-Stewardship is proposing that an independent review panel be set up to deal with contested changes to the Root Zone or its WHOIS Database. Although discussions are still ongoing as to the specifics of such a proposal it is generally agreed that such a mechanism should be part of the final proposal and that its decisions would be binding. As such this would also require changes to the ICANN Bylaws.</span></p><p class="MsoListParagraphCxSpLast" style="text-indent: -18pt;"><span class="" style="text-indent: -18pt;"><br class=""></span></p><p class="MsoListParagraphCxSpLast" style="text-indent: -18pt;"><span class="" style="text-indent: -18pt;">Additionally, the CCWG-Accountability has been advised that "ICANN-only“ proposals currently considered might have significant input on the Accountability mechanisms required. </span></p></span></div></blockquote><div class=""><span lang="EN-CA" class=""><div class="" style="line-height: 12.84000015258789px;"><br class=""></div><div class="" style="line-height: 12.84000015258789px;">Finally, the CWG-Stewardship pointed out that feedback would ideally be received early enough to be taken into account when finalizing the proposal to be submitted to the ICG. </div><div class="" style="line-height: 12.84000015258789px;"><br class=""></div><div class="" style="line-height: 12.84000015258789px;">While the CCWG-Accountability appreciates the sense of urgency and works as expeditiously as possible on the tasks it has been chartered with, it is not feasible to publish a work results of the group in January. </div><div class="" style="line-height: 12.84000015258789px;"><br class=""></div><div class="" style="line-height: 12.84000015258789px;">Nonetheless, the CCWG-Accountability has chosen to publish high level statements as a preliminary assessment of the situation. </div><div class="" style="line-height: 12.84000015258789px;"><br class=""></div><div class="">However, the CCWG-Accountability is cognizant that any preliminary assessment might be subject to change because of<br class=""><br class=""><span class="">- changes made to the proposal published by the CWG-Sterwardship on Dec.1st, 2014</span><br class=""><span class="">- other proposals and</span><br class=""><span class="">- changes due to other external and internal factors, such as evolving deliberations of our group.</span><br class=""></div><div class=""><span class=""><br class=""></span></div><div class=""><span class=""><p class="MsoNormal"><span lang="EN-US" class="">The below high level statements might be valuable to all groups or individuals working on proposals to be submitted to the ICG, which is why they are not only a response to the CWG-Stewardship, but published as a status update by the CCWG-Accountability.</span> </p><p class="MsoNormal"><span lang="EN-US" class="">1. The CCWG-Accountability noted that a significant number of contributions during the two Public Comments on Enhancing ICANN Accountability called for the implementation of independent mechanisms enabling to review and, when appropriate, redress, decisions from the ICANN Board of Directors. It was often noted that these mechanisms should be in place or committed to before the IANA Stewardship Transition takes place. The CCWG-Accountability is therefore considering addressing this need in its Work Stream 1 (WS1). Unless the CWG-Stewardship specifies otherwise, Board decisions that are directly related to IANA Functions could be added to the remit of such independent mechanisms for the review and redress of decisions of the ICANN Board of Directors, which the CCWG-Accountability may address in Work Stream 1. Other issues that were brought up by many and could qualify for being in the remit of such mechanism were decisions broadening or altering ICANN’s mandate as well as recalling one or multiple ICANN Board members. Please note that the legal nature, composition, and specific mandate of this mechanism are yet to be determined. </span></p><p class="MsoNormal"><span lang="EN-US" class="">2. The CCWG-Accountability acknowledges the expectation for certain internal and / or external review and / or appeals processes to be implemented or committed to prior to the transition and will consider these as part of its work. </span></p><p class="MsoNormal"><span lang="EN-US" class="">3. Further, we would like to assure you that the CCWG-Accountability output will adhere to the following considerations;<o:p class=""></o:p></span></p><p class="MsoListParagraphCxSpFirst" style="margin-left: 39.35pt; text-indent: -18pt;"><span lang="EN-US" class="">· </span><span lang="EN-US" class="">Any proposal will address the concern on to whom should ICANN be held accountable.<o:p class=""></o:p></span></p><p class="MsoListParagraphCxSpMiddle" style="margin-left: 39.35pt; text-indent: -18pt;"><span lang="EN-US" class="">· </span><span lang="EN-US" class="">Any proposal will address the concern on what should ICANN be held accountable for.<o:p class=""></o:p></span></p><p class="MsoListParagraphCxSpLast" style="margin-left: 39.35pt; text-indent: -18pt;"><span lang="EN-US" class="">· </span><span lang="EN-US" class="">Any proposal will address the concern on how ICANN or its Board of Directors should be held accountable.</span></p><p class="MsoNormal"><span lang="EN-US" class="">We hope this broad but clear roadmap helps the CWG complement their work and that we continue to work on a coordinated fashion.</span></p><p class="MsoNormal"><span lang="EN-US" class="">Please note that these statements reflect the current status of deliberations of the CCWG-Accountability and might be subject to change for the reasons mentioned above and further input from the community.<o:p class=""></o:p></span></p><p class="MsoNormal"><span lang="EN-US" class=""><o:p class=""> </o:p></span></p><p class="MsoNormal"><span lang="EN-US" class="">Kind regards,<o:p class=""></o:p></span></p><p class="MsoNormal"><span lang="EN-US" class="">Mathieu Weill, León Sánchez and Thomas Rickert<o:p class=""></o:p></span></p><p class="MsoNormal"><span lang="EN-US" class="">Co-Chars of the CCWG-Accountability</span></p></span></div></span></div></div></div></div></blockquote></div><br class=""></div></body></html>