<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.gmail-m-1649711386684943605msolistparagraph, li.gmail-m-1649711386684943605msolistparagraph, div.gmail-m-1649711386684943605msolistparagraph
{mso-style-name:gmail-m_-1649711386684943605msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Hi James<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The approach, as outlined below, seems to make sense provided there are sufficient volunteers with the desired expertise to undertake the review.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Donna<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> council-bounces@gnso.icann.org [mailto:council-bounces@gnso.icann.org]
<b>On Behalf Of </b>James M. Bladel<br>
<b>Sent:</b> Friday, January 27, 2017 7:57 PM<br>
<b>To:</b> GNSO Council List <council@gnso.icann.org><br>
<b>Subject:</b> [council] Fwd: CCWG-Accountability WG proposal for a Limited Scope of the ATRT3 Review - reminder<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div id="compose">
<div>
<p class="MsoNormal">Councilors -<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Please see the message from CCWG Staff, below. Most of the SO-AC chairs (myself included) took this note as informational, and missed the call to action.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">In a nutshell, the CCWG co-chairs note that the upcoming ATRT3 review team will overlap significantly with the recently completed (Workstream 1) and ongoing work (Workstream 2) of CCWG-ACCT. Like the approach to WHOIS2, they are proposing
a reduced scope for this next review to avoid collision/duplication of work.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I'd welcome any comments or thoughts you might have on this, and we can add it as a discussion item for our draft agenda for our Council call in February.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Thank you, <br>
<br>
J.<br>
-------------<br>
James Bladel<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">_____________________________<br>
From: Bernard Turcotte <<a href="mailto:turcotte.bernard@gmail.com">turcotte.bernard@gmail.com</a>><br>
Sent: Wednesday, January 25, 2017 14:41<br>
Subject: CCWG-Accountability WG proposal for a Limited Scope of the ATRT3 Review - reminder<br>
<br>
<br>
<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">SO and AC Chairs,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">This is a reminder that the CCWG-Accountability has not received any replies to its December 2nd proposal (original message below) regarding the scope of the upcoming ATRT3 review which will be publishing its call for volunteers by the
end of January.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">As stated in the proposal there are a number of significant overlaps between the work of the CCWG-Accountability and a standard ATRT review which would cause an important duplication of work between these two processes.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The CCWG-Accountability simply wishes to ensure that the SO's and AC's are aware that if there is no request from the SO's and AC's to modify the scope of the ATRT3 review prior to its launch that it will proceed as a standard review.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The Co-Chairs of the CCWG-Accountability remain available to the SO's and AC's for further discussions or answer any questions.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Bernard Turcotte<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">ICANN Staff Support to the CCWG-Accountability for <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">The Co-Chairs of the <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">CCWG-Accountability.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Dec 2, 2016 at 5:07 AM, Mathieu Weill <<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:11.3pt;line-height:105%">
Dear SO & AC Chairs, <span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:11.3pt;line-height:105%">
The CCWG-Accountability (CCWG) at its face to face meeting at the ICANN 56 in Helsinki considered the implications of the collision of topics, and therefore efforts, between ATRT3 and Work Stream 2 (WS2) (please see Annex 1 for a detailed consideration of this
issue).<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:11.3pt;line-height:105%">
In its discussion of this issue the CCWG considered the following points:<span lang="FR"><o:p></o:p></span></p>
<p class="gmail-m-1649711386684943605msolistparagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:35.3pt;margin-bottom:.0001pt;line-height:105%">
<span style="font-family:Symbol">·</span><span style="font-size:7.0pt;line-height:105%"> </span>Collision of topics between WS2 and ATRT3 - There is potential for significant overlap between WS2 topics and the scope of ATRT3 as 6 of the 9 WS2 topics
are accountability and transparency issues ATRT3 could also consider.<span lang="FR"><o:p></o:p></span></p>
<p class="gmail-m-1649711386684943605msolistparagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:35.3pt;margin-bottom:.0001pt;line-height:105%">
<span style="font-family:Symbol">·</span><span style="font-size:7.0pt;line-height:105%"> </span>Timing of the two activities - WS2 began in July 2016 with an objective of completing its work by the end of 2017. ATRT3, which is expected to take 12 months
to complete, is currently scheduled to begin in January 2017 but could potentially be delayed until February 2018 under the new Bylaws (which require ATRT every 5 years versus the AoC requirement for every 3 years). It would seem inefficient, at best, to have
both of these activities working on the same topics independently, while drawing on the same pool of community volunteers. At worst, ATRT3 and WS2 groups could issue recommendations that are conflicting or duplicative.<span lang="FR"><o:p></o:p></span></p>
<p class="gmail-m-1649711386684943605msolistparagraph" style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:35.3pt;margin-bottom:.0001pt;line-height:105%">
<span style="font-family:Symbol">·</span><span style="font-size:7.0pt;line-height:105%"> </span>Implementation of recommendations – The Bylaws for WS2 give CCWG recommendations greater weight when it comes to board consideration, relative to recommendations
from an ATRT organized under the AoC.<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;line-height:105%">While in Helsinki, the CCWG concluded its preferred approach, as communicated in our 8-Aug-2016<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_correspondence_sanchez-2Det-2Dal-2Dto-2Dicann-2Dboard-2D08aug16-2Den.pdf&d=DwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=rveDVaatHC6nvjfOWf9C6dVdV-UfhGU2TId8SjMWpF8&s=4cXv0guFv6lketxw24bLH_UjkvkfcNHxwnspXXsuocc&e=" target="_blank">letter</a>
to the Board of ICANN:<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:36.7pt;line-height:105%">
Convene ATRT3 as soon as possible with the limited scope of assessing implementation of ATRT2 recommendations. Allow WS2 to handle new recommendations for accountability and transparency. The fourth ATRT would convene before 2022 and would assess all accountability
and transparency topics and make recommendations<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">The ICANN Board <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_en_system_files_correspondence_crocker-2Dto-2Dsanchez-2Det-2Dal-2D24oct16-2Den.pdf&d=DwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=rveDVaatHC6nvjfOWf9C6dVdV-UfhGU2TId8SjMWpF8&s=Kg2IUhDhzIcuRXwvKBG3ebII0gfTEnFFUoxX0QIxUfY&e=" target="_blank">
replied</a> to the CCWG letter on 24-Oct-2016, saying,<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:.5in">It is not up to the Board to dictate the scope of this important community review. While we share the concerns raised of avoiding duplication of resources, it is essential that the broader
ICANN community have a voice in determining how the ATRT3 should be scoped in alignment with the Bylaws. The Board and the ICANN Organization stand ready to support the community’s direction.<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto">Accordingly, the CCWG is now proposing to community leadership the following approach:<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-left:36.5pt"><span style="font-family:"Arial",sans-serif;border:none windowtext 1.0pt;padding:0in">•</span><span style="font-size:7.0pt;border:none windowtext 1.0pt;padding:0in"> </span>Requesting
that the SO/AC leadership select (following the new Bylaws) a small group of review team members that have either participated in or closely tracked ATRT2.<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-right:.35pt;margin-bottom:2.4pt;margin-left:36.5pt">
<span style="font-family:"Arial",sans-serif;border:none windowtext 1.0pt;padding:0in">•</span><span style="font-size:7.0pt;border:none windowtext 1.0pt;padding:0in"> </span>Requesting the ICANN organization to do a "self-assessment" reporting on a) the
extent to which each recommendation was followed and/or implemented; b) the effectiveness in addressing the issues identified by ATRT2; and c) the need for additional implementation.
<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-right:.35pt;margin-bottom:2.4pt;margin-left:36.5pt">
<span style="font-family:"Arial",sans-serif;border:none windowtext 1.0pt;padding:0in">•</span><span style="font-size:7.0pt;border:none windowtext 1.0pt;padding:0in"> </span>Specifically request that the Review Team exclude the issues that are already covered
by the CCWG-Accountability WS2 (see Annex 1).<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-right:.35pt;margin-bottom:2.4pt;margin-left:36.5pt">
<span style="font-family:"Arial",sans-serif;border:none windowtext 1.0pt;padding:0in">•</span><span style="font-size:7.0pt;border:none windowtext 1.0pt;padding:0in"> </span>Suggesting that the work be conducted & completed more quickly than normal, such
as asking that the Final Report be issued within six months<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:11.3pt;line-height:105%">
If the suggested approach above is agreeable to SO/AC community, the next steps would be:<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-right:.35pt;margin-bottom:2.4pt;margin-left:36.5pt">
<span style="font-family:"Arial",sans-serif;border:none windowtext 1.0pt;padding:0in">•</span><span style="font-size:7.0pt;border:none windowtext 1.0pt;padding:0in"> </span>SO/AC leadership to issue a public statement or a letter to ICANN CEO and Board
Chair that explains why limited scope is appropriate and articulates that they have broad support of the ICANN community<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-right:.35pt;margin-bottom:2.4pt;margin-left:36.5pt">
<span style="font-family:"Arial",sans-serif;border:none windowtext 1.0pt;padding:0in">•</span><span style="font-size:7.0pt;border:none windowtext 1.0pt;padding:0in"> </span>Call for Volunteers to note limited scope & unique expertise sought<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-right:.35pt;margin-bottom:2.4pt;margin-left:36.5pt">
<span style="font-family:"Arial",sans-serif;border:none windowtext 1.0pt;padding:0in">•</span><span style="font-size:7.0pt;border:none windowtext 1.0pt;padding:0in"> </span>Reach out to previous ATRT Review Team members and encourage them to apply for
the narrowly-scoped ATRT3 Review Team<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-right:.35pt;margin-left:36.5pt">
<span style="font-family:"Arial",sans-serif;border:none windowtext 1.0pt;padding:0in">•</span><span style="font-size:7.0pt;border:none windowtext 1.0pt;padding:0in"> </span>Propose a Charter for the ATRT3 Review Team to adopt that tracks the limited Scope<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Best regards,<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Thomas Rickert, Leon Sanchez & Mathieu Weill<span lang="FR"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">CCWG-Accountability Co-chairs<span lang="FR"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Acct-Staff mailing list<br>
<a href="mailto:Acct-Staff@icann.org">Acct-Staff@icann.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_acct-2Dstaff&d=DwMGaQ&c=MOptNlVtIETeDALC_lULrw&r=4A3LwUUER9_CePZ11QJsr56eryGQiPHEqv4TL7JH87w&m=rveDVaatHC6nvjfOWf9C6dVdV-UfhGU2TId8SjMWpF8&s=THvbsip6pDvGSyLxoywCDK42Lez6Pa5O4sH9113uBYQ&e=" target="_blank">https://mm.icann.org/mailman/listinfo/acct-staff</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
</div>
</body>
</html>