<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>
<div>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>. </div>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div 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><br>
</div>
<div>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:</div>
<div><br>
</div>
<div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>Work Stream 1 is designated for accountability enhancement mechanisms that must be in place [or firmly committed]</div>
<div>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.</div>
<div></div>
</blockquote>
<div>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:</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>On 1/2/15, 5:12 PM, "Steve DelBianco" <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>> wrote:</div>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
Alan Greenberg has questioned the accountability measures we were placing into Work Stream 1, saying, </div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
"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.”</div>
</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
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. </div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
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.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
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). </div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
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. </div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
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.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div id="">
<div>—</div>
<div>
<div>Steve DelBianco</div>
<div>Executive Director</div>
<div>NetChoice</div>
<div><a href="http://www.netchoice.org/">http://www.NetChoice.org</a> and <a href="http://blog.netchoice.org/">http://blog.netchoice.org</a></div>
<div>+1.202.420.7482</div>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</span></div>
</span>
</body>
</html>