<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.EmailStyle17
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Thanks, Steve. It may also be helpful to highlight that we debated this issue within the CCWG drafting group and basically agreed
that the CCWG should be empowered to address accountability across the whole of ICANN – this should be reflected in the transcripts.
<o:p></o:p></span></p>
<p class="MsoNormal"><a name="_MailEndCompose"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></a></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> owner-bc-gnso@icann.org [mailto:owner-bc-gnso@icann.org]
<b>On Behalf Of </b>Steve DelBianco<br>
<b>Sent:</b> 02 January 2015 23:05<br>
<b>To:</b> BC List<br>
<b>Subject:</b> [bc-gnso] CCWG on ICANN Accountability: Work Stream 1 and the concept of Leverage<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">First, Happy New Year! And second, here’s an update from the Accountability
<a href="https://community.icann.org/display/acctcrosscomm/CCWG+on+Enhancing+ICANN+Accountability">
CCWG</a>. <o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">We had our 4th call on Tuesday (<a href="https://community.icann.org/pages/viewpage.action?pageId=51414982">call notes</a>). The work team I am leading has
<a href="https://community.icann.org/download/attachments/51414327/WorkArea2%20Accountability%20suggestions%20%5Bdraft%205.1%5D.pdf?version=1&modificationDate=1419814534000&api=v2">
documented</a> many accountability mechanisms, placing them into one of 2 ‘work streams’ according to this rationale:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<blockquote style="margin-left:30.0pt;margin-right:0cm">
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Work Stream 1 is designated for accountability enhancement mechanisms that must be in place [or firmly committed]<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">before IANA transition occurs. All other consensus items could be in Work Stream 2, provided there are mechanisms in WS1 adequate to force implementation of WS2 items despite
resistance from ICANN management and board.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif;color:black"></span><span style="font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">At this point the CCWG is debating that rationale, with some members fearing that ICANN's board might reject significant new accountability measures. Below is the response I gave
to Alan Greenberg when he expressed that concern:<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">On 1/2/15, 5:12 PM, "Steve DelBianco" <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>> wrote:<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Alan Greenberg has questioned the accountability measures we were placing into Work Stream 1, saying, <o:p></o:p></span></p>
</div>
<blockquote style="margin-left:30.0pt;margin-right:0cm">
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">"I am somewhat troubled by all of the items in WS1 where I do not see the direct link to the IANA transition. Note I am not saying that they might not be perfectly valid and desirable
accountability mechanism, just that I do not see the direct link, and thus perhaps greatly increasing our work to be done to allow transition.”<o:p></o:p></span></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">In responding to Alan, several of us said that a direct link to IANA transition is neither required nor desirable. Instead, the IANA transition is the community’s last bit of leverage
to force accountability measures on ICANN’s board. The leverage is directly held by NTIA, who has said they would not transition IANA unless there was consensus about holding ICANN accountable to the community once the IANA contract is gone. And the internet
community has indirect leverage, though pressure being brought on the US Administration and on Congress. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">So I would hope that Alan and others can gain confidence and comfort with the leverage our CCWG holds in this process. With that leverage comes the responsibility to create accountability
mechanisms that will guide DNS policy making for decades to come. And we must also get our work done without causing undue delay to the IANA transition process.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Alan’s group is the ALAC, which has often felt the lack of leverage over ICANN’s board and and management. As a recent example, ALAC called on ICANN to stop delegating new gTLDs
serving highly regulated sectors but lacking enforceable public interest commitments (<a href="https://www.icann.org/en/system/files/correspondence/alac-to-icann-board-16oct14-en.pdf">link</a>). ICANN’s board and management might continue signing contracts
despite concerns of the ALAC and others, perhaps fearing lawsuits by gTLD applicants. The fear of lawsuits may also have led the board to ignore community concerns over delegating both singular and plural forms of the same gTLDs. After all, the ICANN board’s
duty is to the interests of the ICANN corporation — not to the community. (see <a href="https://www.icann.org/resources/pages/bylaws-2012-02-25-en#VI">
Bylaws </a>Article 6, Section 7). <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">What would be the source of leverage to hold the board accountable to the community for this decision? We have seen the futility of Reconsideration requests and Independent Reviews
that lack leverage to reverse a board decision. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">This IANA transition is our last chance to create mechanisms that could hold ICANN’s board accountable to the community it was designed to serve. Let's embrace that challenge
and use all the leverage we have.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div id="">
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">—<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Steve DelBianco<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">Executive Director<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">NetChoice<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><a href="http://www.netchoice.org/">http://www.NetChoice.org</a> and <a href="http://blog.netchoice.org/">http://blog.netchoice.org</a><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black">+1.202.420.7482<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
This message and its attachments may contain legally privileged or confidential information. It is intended solely for the named addressee. If you are not the addressee indicated in this message (or responsible for delivery of the message to the addressee),
you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments that does not relate
to the official business of Twenty-First Century Fox, Inc. or its subsidiaries must be taken not to have been sent or endorsed by any of them. No representation is made that this email or its attachments are without defect.
</body>
</html>