<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; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;">
<div>
<div>Thanks, Chantelle . Since that update was written back on 2-Feb, we’ve made considerable progress on the CCWG recommendations listed as “still under discussion”</div>
<div><br>
</div>
<div>On today’s CCWG call, we finalized text for all 12 recommendations, to be published as our Final Supplemental proposal. CCWG is working with staff and our lawyers to generate the final document by week of Feb 15, in time for Chartering Organizations
(incl GNSO) to consider before (or at Marrakesh).</div>
<div><br>
</div>
<div>On Rec 11 dealing with Stress Test 18, our final proposal is:</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">The board’s obligation to “try to find a mutually acceptable solution” will <u>only</u> apply for GAC advice that is approved by broad agreement in the absence of any formal objection.</blockquote>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><br>
</blockquote>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">For GAC advice that is "approved by broad agreement in the absence of any formal objection”, the ICANN board needs 60% threshold to reject, instead of 50%. That is an increase of 1 board vote,
relative to today’s bylaws. It is one vote less than the 2/3 threshold published in the CCWG 3rd draft.</blockquote>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div><br>
</div>
<div>Formal Advice from any AC must include a rationale.</div>
<div><br>
</div>
<div>If the community is considering a challenge to the Board’s implementation of GAC Advice, the community decision should not be blocked by the GAC as a decisional participant. So the GAC will not be given a formal decisional role in a community decision
on whether to challenge board action based on GAC advice. We designed a process for this carve-out, which I’ll share before our BC call this week. </div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</blockquote>
<div> </div>
<div>
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:12pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><<a href="mailto:owner-bc-gnso@icann.org">owner-bc-gnso@icann.org</a>> on behalf of Chantelle Doerksen <<a href="mailto:chantelle.doerksen@icann.org">chantelle.doerksen@icann.org</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, February 9, 2016 at 12:53 PM<br>
<span style="font-weight:bold">Subject: </span>[bc-gnso] Leading into Marrakech: An Update from the CCWG-Accountability co-Chairs<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div>For your review.</div>
<div><br>
</div>
<div style="font-size: 14px; font-family: Calibri, sans-serif;"><span style="font-family: 'Times New Roman', serif; font-size: 12pt;">_____________________________ </span></div>
<span id="OLK_SRC_BODY_SECTION" style="font-size: 14px; font-family: Calibri, sans-serif;">
<div lang="FR" link="blue" vlink="purple">
<div class="WordSection1">
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"><a href="https://www.icann.org/news/blog/leading-into-marrakech-an-update-from-the-ccwg-accountability-co-chairs">https://www.icann.org/news/blog/leading-into-marrakech-an-update-from-the-ccwg-accountability-co-chairs</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"><o:p> </o:p></span></p>
</div>
<div>
<h1><span style="font-family: Calibri, sans-serif;">Leading into Marrakech: An Update from the CCWG-Accountability co-Chairs<o:p></o:p></span></h1>
<div>
<p><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">The Cross Community Working Group on Enhancing ICANN’s Accountability (CCWG-Accountability) has ushered in 2016 with a full schedule and renewed dedication to its mission. <o:p></o:p></span></p>
<p><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">Following the release of the
<a href="https://www.icann.org/en/system/files/files/report-comments-draft-ccwg-accountability-proposal-08jan16-en.pdf">
staff report</a> and the <a href="https://www.icann.org/en/system/files/files/summary-comments-draft-ccwg-accountability-proposal-08jan16-en.xlsx">
summary of public comments</a>, both of which were published on 8 January, the group wasted no time in setting up a rigorous schedule of conference calls for the rest of the month.<o:p></o:p></span></p>
<p><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">The schedule was designed to enable inclusive and informed debates about the input received during the 21-day public comment period and the feedback provided by the six Chartering Organizations
of CCWG-Accountability. <o:p></o:p></span></p>
<p><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">The dedication of our members and participants, along with the increased involvement by members of the ICANN Board, has allowed us to make significant progress over the past four weeks. The
collaborative environment has brought us even closer to our goal of a consensus proposal that will meet the requirements of the National Telecommunications and Information Administration (NTIA) and fulfill the dependencies of the CWG-Stewardship in the ICG
Final Proposal.<o:p></o:p></span></p>
<p><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">Here is the current status of each CCWG-Accountability Work Stream 1 Recommendations:<o:p></o:p></span></p>
<table class="MsoNormalTable" border="1" cellspacing="1" cellpadding="0" width="938" style="width: 562.5pt;">
<tbody>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #1:</strong> Establishing an Empowered Community for Enforcing Community Powers<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p>Finalized.<o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #2:</strong> Empowering the Community Through Consensus: Engagement, Escalation, Enforcement<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p>Final comments by CCWG-Accountability. Expect final by February 5th.<o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #3:</strong> Redefining ICANN’s Bylaws as ‘Standard Bylaws’ and ‘Fundamental Bylaws<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p class="MsoNormal">Finalized.<o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #4:</strong> Ensuring Community Engagement in ICANN Decision-making: Seven New Community Powers<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p>Edits to reflect input on PTI budget (CWG-Stewardship) and indemnification language for removal of Directors by the Empowered Community.<o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #5:</strong> Changing Aspects of ICANN’s Mission, Commitments and Core Values<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p>Still under discussion by the CCWG-Accountability.<o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #6:</strong> Reaffirming ICANN’s Commitment to Respect Internationally Recognized Human Rights as it Carries Out its Mission<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p>Final comments by CCWG-Accountability. Expect final by February 5th.<o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #7:</strong> Strengthening ICANN’s Independent Review Process<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p>Edits to reflect input on applicability to PTI. <o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #8:</strong> Improving ICANN’s Request for Reconsideration Process<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p>Final comments by CCWG-Accountability. Expect final by February 5th.<o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #9:</strong> Incorporating the Affirmation of Commitments in ICANN’s Bylaws<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p>Still under discussion by the CCWG-Accountability.<o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #10:</strong> Incorporating the Affirmation of Commitments in ICANN’s Bylaws<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p>Final draft to be reviewed by lawyers before final comments by CCWG-Accountability. Expect final by February 5th.<o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #11:</strong> Board Obligations with regards to Governmental Advisory Committee Advice (Stress Test 18)<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p>Still under discussion by the CCWG-Accountability.<o:p></o:p></p>
</td>
</tr>
<tr>
<td style="padding:.6pt .6pt .6pt .6pt">
<p><strong>Recommendation #12:</strong> Committing to Further Accountability Work in Work Stream 2<o:p></o:p></p>
</td>
<td style="padding:.6pt .6pt .6pt .6pt">
<p>Finalized.<o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">For the latest versions of all of the recommendations above, visit the
<a href="https://community.icann.org/x/8JVlAw">CCWG-Accountability wiki</a>.<o:p></o:p></span></p>
<p><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">After consensus has been reached on our few outstanding issues, the CCWG-Accountability will develop a “supplemental” report of the Work Stream 1 Recommendations, including a summary of changes
from the Third Draft Report. <o:p></o:p></span></p>
<p><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">The supplemental report is currently being developed, and will go through an
<a href="http://mm.icann.org/pipermail/accountability-cross-community/attachments/20160120/0e76810a/Timelineandnextsteps-0001.pdf">
open and transparent process</a> of 1) CCWG-Accountability consultation, 2) support staff editing/proofing, 3) co-Chair and Rapporteur finalization, 4) legal review and 5) final publication. Our hope is that the majority of changes from the Third Draft Report
will relate to specificities of implementation rather than content, and as such, an additional public comment period will not be necessary before approval by the Chartering Organizations.<o:p></o:p></span></p>
<p><strong><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">Our goal is to distribute the supplemental report to our Chartering Organizations in time for consideration and approval on all Work Stream 1 Recommendations at ICANN55 in Marrakech.</span></strong><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">
Keeping in mind the working methods for the various Supporting Organizations and Advisory Committees, we ask that this be into account as the Chartering Organizations plan their discussions and schedules leading into and during ICANN55. With that said, we
encourage any Chartering Organizations that can deliberate and/or approve the Work Stream 1 Recommendations prior to Marrakech to do so.<o:p></o:p></span></p>
<p><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;">We are grateful for the increased involvement of the ICANN Board as our work has progressed since the Third Draft Report. It has been helpful to understand Board comments in real-time, including
ways to ensure any global public interest concerns are debated and considered as the recommendations are being revised. We hope to continue this open dialogue as the supplemental report is finalized, and ask the ICANN Board to be mindful of the timeline as
they plan their review period of the Work Stream 1 Recommendations and submission to NTIA.<o:p></o:p></span></p>
<p><span style="font-size: 10.5pt; font-family: Calibri, sans-serif;"><br>
<strong><span style="font-family: Calibri, sans-serif;">CCWG-Accountability co-Chairs</span></strong><br>
Mathieu Weill, Thomas Rickert, León Sanchez<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</span><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:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:24.0pt;
font-family:"Times New Roman",serif;
font-weight:bold;}
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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Calibri Light",sans-serif;
color:#2E74B5;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style></div>
</div>
</span>
</body>
</html>