<html 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="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Courier New";
panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:Calibri;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:98646873;
mso-list-type:hybrid;
mso-list-template-ids:-457542206 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1
{mso-list-id:1689671596;
mso-list-type:hybrid;
mso-list-template-ids:913357506 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Original link: https://www.icann.org/news/blog/co-chairs-statement-from-ccwg-accountability-meeting-in-hyderabad<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Co-Chairs Statement from CCWG-Accountability Meeting in Hyderabad<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">On 2 November 2016, the Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) held a
<a href="https://community.icann.org/pages/viewpage.action?pageId=62394381">face-to-face meeting</a> in Hyderabad, India, to further its discussions on Work Stream 2. 60 members and participants attended in-person, and many others joined the meeting remotely
using the virtual meeting room.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">As a part of Work Stream 1, the CCWG-Accountability defined areas where further accountability discussions needed to take place. These discussions, called Work Stream 2, have
<a href="https://www.icann.org/news/blog/launching-work-stream-2-in-helsinki">been underway</a> since June 2016. The purpose of Work Stream 2 is to disseminate the new accountability principles into several key parts of ICANN’s day-to-day operations, and to
develop a culture of accountability across the ICANN Community, Organization, and Board.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Co-Chair Thomas Rickert described the two accountability Work Streams as the two phases of building a home. “By completing Work Stream 1, [we] built the foundation of our new house. Now, with Work Stream 2,
we are putting in windows and adding furniture.” Completing Work Stream 2 will help ensure that ICANN remains accountable to the global Internet community for years to come.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">During the meeting, the CCWG-Accountability received updates from its nine subgroups and produced a
<a href="https://community.icann.org/x/DRC4Aw">dashboard</a> to update the ICANN Community about the status of its work. The CCWG-Accountability also made substantive progress in several areas:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span style="font-size:11.0pt">It reached consensus on a set of
<a href="http://mm.icann.org/pipermail/iot/attachments/20161031/1c89b83f/DraftIRPUpdatedSupplementaryProceduresReportv231oct16-0001.docx">
Draft Supplementary Rules for the Independent Review Process</a>. The draft will be published for public comment soon.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span style="font-size:11.0pt">It developed a
<a href="http://mm.icann.org/pipermail/accountability-cross-community/attachments/20161104/a3fee52d/SOACquestionsrevised2-Novv2-0001.docx">
set of questions</a> for ICANN’s Supporting Organizations (SOs) and Advisory Committees (ACs) to identify their existing accountability mechanisms. The
<a href="http://mm.icann.org/pipermail/accountability-cross-community/2016-November/013400.html">
co-Chairs sent</a> these questions to the SO and AC Chairs on 4 November.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span style="font-size:11.0pt">It determined that the
<a href="https://community.icann.org/x/lhWOAw">Ombuds Office subgroup</a> will act as a steering committee to oversee the external review of the Ombud function within ICANN, as mandated by the 2nd Accountability and Transparency Review Team (ATRT).
<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span style="font-size:11.0pt">It developed an initial set of guidelines for bringing forward any proposed Board removal actions. These guidelines are publicly available and will be refined based on the
any feedback received.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l0 level1 lfo1"><span style="font-size:11.0pt">It discussed a comprehensive set of recommendations to enhance ICANN’s transparency policies.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The CCWG-Accountability also had the pleasure to speak with ICANN’s CEO, Göran Marby. The discussions focused on the interaction between the working group’s accountability enhancements and the introduction
of a new “<a href="https://www.icann.org/news/blog/evolving-icann-s-executive-team">Complaints Officer</a>” position at ICANN. A constructive dialogue was initiated, and the CCWG-Accountability looks forward to further engagements with Mr. Marby in the future.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The CCWG-Accountability co-Chairs recognize the outstanding dedication of its volunteers, and express gratitude to ICANN staff for their diligent and skilled support. For more information on the CCWG-Accountability,
or to view meeting archives and draft documents, please refer to their <a href="https://community.icann.org/x/uQuOAw">
dedicated wiki page</a>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">About the CCWG-Accountability<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The CCWG-Accountability was established in 2014 as a part of the IANA stewardship transition. The group’s goal is to ensure that ICANN's accountability and transparency commitments to the global Internet community
are maintained and enhanced in the absence of the IANA functions contract with the U.S. Government.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The group divided its work into two Work Streams:<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l1 level1 lfo2"><span style="font-size:11.0pt">Work Stream 1 was focused on identifying mechanisms to enhance ICANN’s accountability that must be in place or committed to within the timeframe of the IANA stewardship transition.<o:p></o:p></span></li><li class="MsoNormal" style="mso-list:l1 level1 lfo2"><span style="font-size:11.0pt">Work Stream 2 is focused on addressing accountability topics for which a timeline for developing solutions and full implementation may extend beyond the IANA stewardship transition.
<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:11.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The CCWG-Accountability proposed twelve recommendations to enhance ICANN’s accountability as a part of the IANA stewardship transition. The consensus
<a href="https://www.icann.org/en/system/files/files/ccwg-accountability-supp-proposal-work-stream-1-recs-23feb16-en.pdf">
Work Stream 1 proposal</a> was <a href="https://www.icann.org/news/announcement-2016-03-10-en">
approved and transmitted</a> by the ICANN Board to the U.S. National Telecommunications and Information Administration in 9 March 2016. On 1 October 2016, the
<a href="https://www.icann.org/news/announcement-2016-10-01-en">IANA functions contract lapsed</a>, and CCWG-Accountability’s Work Stream 1 recommendations went into effect.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The CCWG-Accountability is <a href="https://community.icann.org/x/IIMHAw">
comprised of 227 people</a>, organized as: members appointed by and accountable to Chartering Organizations; individual participants; one ICANN Board liaison; one ICANN staff representative; and one former ATRT member who serves as a liaison. The group also
has over 130 <a href="https://community.icann.org/x/sIMHAw">mailing list observers</a>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">The CCWG-Accountability is an open group. Anyone interested in the work of the CCWG-Accountability can join as a participant or observer. For more information about how to join the CCWG-Accountability, please
send an email to acct-staff [at] icann.org.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</body>
</html>