<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:0cm;
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;}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
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="DE-CH" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Thanks for these thoughts. I think they fit well with some of the points made yesterday by, among others, Valerie D’Costa,
about inclusion.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Jorge<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Von:</span></b><span lang="DE" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> accountability-cross-community-bounces@icann.org [mailto:accountability-cross-community-bounces@icann.org]
<b>Im Auftrag von </b>Arun Sukumar<br>
<b>Gesendet:</b> Montag, 23. März 2015 15:47<br>
<b>An:</b> Accountability Cross Community<br>
<b>Betreff:</b> [CCWG-ACCT] Engaging the community - some thoughts<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I understand the CCWG has identified who the community is based on who will be "directly" or "indirectly" affected by ICANN's actions, but most of the proposals, if not all of them, tabled today - be it on community empowerment, powers
to remove the Board, etc -- seem too focused on static ICANN constituencies. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">This is fine if the CCWG feels it is not within the group's remit to think beyond the SO/ACs of ICANN. Personally, I think any exercise to enhance the Corporation's accountability should consider the audience it will cater to in the future.
It is not enough that "business" or "at large" or "non-commercial users" are labelled so as ICANN constituencies. Where is the discussion in the CCWG on the concerns of representation within them - based on gender, age, geographical representation, nature
of internet access?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The most appropriate policy intervention that the CCWG can make in this regard to draft an expansive Mission Statement and Core Values. Yet, we seem happy to confine its vision to conform to ICANN Bylaws (which, wearing my lawyer's hat
is difficult to understand given the preamble is always more expansive than the operational statute).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I raise this only because the question of ICANN accountability is not a technocratic/legal exercise alone. The issue of accountability was brought to the table only later in 2014, although the NTIA did not feel it necessary to include it
in its original announcement. A political opening, therefore, requires, I hesitate to add, an equally sensitive response. Otherwise, the accountability working group's output will be seen as moving far too little in this direction.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">cheers<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">arun<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">-<o:p></o:p></p>
<div>
<p class="MsoNormal">@<a href="http://www.twitter.com/arunmsukumar" target="_blank">arunmsukumar</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Senior Fellow, <a href="http://www.ccgdelhi.org" target="_blank">
Centre for Communication Governance</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">National Law University, New Delhi<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Ph: +91-9871943272<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>