<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
+ 1 <br>
<br>
<div class="moz-cite-prefix">On 08/10/2015 23:10, Robin Gross wrote:<br>
</div>
<blockquote
cite="mid:7D9F3E28-DD41-48D9-BA22-712033B16F39@ipjustice.org"
type="cite">+1. Well said - and much appreciated.
<div><br>
<div>
<div>On Oct 8, 2015, at 5:45 PM, Steve DelBianco wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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>Jordan,</div>
<div>Don’t apologize. Instead, just accept our
gratitude for the effort and integrity you have
contributed to this process for nearly a year. Your
blog post is both sobering and inspiring. Our task
remains, as you say:</div>
<div><br>
</div>
<blockquote style="margin:0 0 0 40px; border:none;
padding:0px;" type="cite">
<div><span style="color: rgb(45, 48, 49); font-family:
'Gotham Rounded SSm A', 'Gotham Rounded SSm B';
font-size: 14px; line-height:
25.200000762939453px;">The “what” is ensuring the
Internet community, able to organise through
ICANN’s open groupings, can hold a corporation
with hundreds of staff, hundreds of millions of
dollars, tight links with the American government,
a monopoly ability to extract rents from the
domain name industry, and a natural institutional
desire to be as free of restraint as it can – can
hold all that to account, given the huge imbalance
of power, knowledge, resources that tilt the
playing field of accountability entirely in
ICANN’s favour.</span></div>
</blockquote>
<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
moz-do-not-send="true"
href="mailto:accountability-cross-community-bounces@icann.org"><a class="moz-txt-link-abbreviated" href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a></a>>
on behalf of Jordan Carter<br>
<span style="font-weight:bold">Date: </span>Thursday,
October 8, 2015 at 8:19 PM<br>
<span style="font-weight:bold">To: </span>Accountability
Cross Community<br>
<span style="font-weight:bold">Subject: </span>[CCWG-ACCT]
Blog post on the Accountability work headed to Dublin<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr">
<div><font style="font-weight:normal" size="2"
color="#000000"
face="arial,helvetica,sans-serif">Hi all,</font></div>
<div><font style="font-weight:normal" size="2"
color="#000000"
face="arial,helvetica,sans-serif"><br>
</font></div>
<div><font style="font-weight:normal" size="2"
color="#000000"
face="arial,helvetica,sans-serif">Apologies
for the interruption to your inbox. I've
been doing a bit of work trying to make
sense of all the events in the ICANN
accountability debate. I wrote up a
chronology of that, which is available
attached to this post. A blog post with my
reflections is below. </font></div>
<div><font style="font-weight:normal" size="2"
color="#000000"
face="arial,helvetica,sans-serif"><br>
</font></div>
<div><font style="font-weight:normal" size="2"
color="#000000"
face="arial,helvetica,sans-serif">Whatever
part of the community you are from, and
whatever your view on the substance of the
debates we are having in the CCWG, I hope
you can stand up in support of the
multistakeholder model at this challenging
moment. There is a lot at stake if this
accountability effort fails, and the risk
of that is not high but it is increasing. </font></div>
<div><br>
</div>
<div><font style="font-weight:normal" size="2"
color="#000000"
face="arial,helvetica,sans-serif">See many
of you in Dublin next week!</font></div>
<div><font style="font-weight:normal" size="2"
color="#000000"
face="arial,helvetica,sans-serif"><br>
</font></div>
<div><font style="font-weight:normal" size="2"
color="#000000"
face="arial,helvetica,sans-serif">cheers</font></div>
<div><font style="font-weight:normal" size="2"
color="#000000"
face="arial,helvetica,sans-serif">Jordan</font></div>
<h1 style="margin:40px 0px
0px;font-size:2.6rem;font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';line-height:30.42px;padding-bottom:9px;border-bottom-style:none;padding-left:0px"><font
color="#000000">ICANN Accountability - the
chronology and Dublin thoughts</font></h1>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
9 October - at <a moz-do-not-send="true"
href="https://internetnz.nz/blog/icann-accountability-chronology-and-dublin-thoughts"
target="_blank">https://internetnz.nz/blog/icann-accountability-chronology-and-dublin-thoughts</a> </p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
You’ve probably had an experience in your
life of being part of a difficult or
complicated project – sometimes things go
into a blur, or after months or years you
find it hard to remember the order of
significant events.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
Well, the debate regarding ICANN’s
accountability is nothing if not complicated
(not to say difficult!). I’ve been a
participant in it as a member of the Working
Group representing country-code domains
since December 2014, and even over not quite
a year, things get a bit blurry.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
To help me, and possibly you, I decided to
pull together a short chronology of some of
the key milestones. Dates of proposals,
significant moments in the project, and so
on.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
You can review (and critique) the chronology
here:</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
<a moz-do-not-send="true"
href="https://internetnz.nz/sites/default/files/2015-10-09-ICANN-accty-chrono.pdf"
style="color:rgb(255,0,122);text-decoration:none;background:transparent"
target="_blank">.pdf</a><br>
<a moz-do-not-send="true"
href="https://internetnz.nz/sites/default/files/2015-10-09-ICANN-accty-chrono.docx"
style="color:rgb(255,0,122);text-decoration:none;background:transparent"
target="_blank">.docx</a></p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
I didn’t expect that seeing this story in
one short place would trigger some new
insights, or remind me of some old ones, but
it did. Here are some of them:</p>
<ul
style="margin-top:0px;margin-bottom:10px;padding-left:20px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
<li><strong>Astonishing progress:</strong> since
the end of last year, and the demise of
ICANN’s resistance to a community-led
accountability process, the Cross
Community Working Group (CCWG) has made
huge progress. It assessed previous
suggested accountability mechanisms; built
requirements for a new settlement; devised
models that could deliver; took feedback
in good faith and worked together to
overcome problems exposed in public
debate. The Second Draft Proposal of the
group is workable, though it does not
enjoy consensus in the ICANN community
yet.</li>
<li><strong>Consistent resistance and delay:</strong> the
powers-that-be at ICANN have resisted
community-driven accountability reforms
throughout this process. The multi-month
delay to establishing the CCWG speaks
volumes. The group’s work would have
concluded next week in Dublin if we’d had
the few more months back in 2014. I say
that not to lament it, but to make it
clear where responsibility lies for the
current time pressure. Hint: the CCWG
isn’t responsible.</li>
<li><strong>The rightness of
multistakeholderism: </strong>the
community has followed a true
multistakeholder process. Compromise,
diligence, thoroughness and a willingness
to compromise and think outside the box –
all these have been central to the work of
the group. That work process is hard to
maintain and has been seriously challenged
by the ICANN Board alleging a right to
insert “red lines” into part of the debate
– on the critical matters of enforcement. <span
style="font-size:13.008px;line-height:1.538em">Those interventions place
the credibility of the multistakeholder
process at risk. In doing so, the ICANN
Board isn’t only putting the
accountability reform process under
pressure it doesn’t need, it is delaying
the group’s ability to complete its task
(others have more forceful views - see
the note by William Currie, an Advisor
to the CCWG appointed by the Public
Experts Group last year, <a
moz-do-not-send="true"
href="http://mm.icann.org/pipermail/accountability-cross-community/2015-October/006410.html"
style="color:rgb(255,0,122);text-decoration:none;background:transparent"
target="_blank">here</a>). The follow
on consequence: the IANA Stewardship
transition itself is delayed, a
consequence only a very few people would
celebrate (and I am not one of them). </span></li>
</ul>
<ul
style="margin-top:0px;margin-bottom:10px;padding-left:20px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
<li><strong>Proof of need:</strong> looking
over the short history of the current
debate gives ample evidence of why the
reforms demanded by the community are
required. Without the spur provided by
the IANA Stewardship transition, this
opportunity would never have opened up. We
should be grateful to the Obama
administration for the chance provided to
build a long term, responsible framework
for ICANN accountability.</li>
<li><strong>Some welcome flexibility:</strong> a
year ago, if you’d thought you would hear
ICANN saying it would welcome binding
arbitration, the ability to remove Board
directors, a community right of veto in
bylaws changes – many would have stared at
you and laughed. If you’d suggested a
community group working in open
multistakeholder ways could deliver a work
output the quality the CCWG has matched,
the same stares and laughs. But both have
happened. Things have moved.</li>
</ul>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
Everyone involved with or watching this
process will have different insights, or may
agree happily or disagree sharply with mine.
I offer them up in public as part of my own
commitment to accountability: it is
reasonable for people involved in the
conversation to share their thinking. In any
case, my own thought processes work best
with dialogue – not with solitude.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
ICANN is on the verge of historic,
meaningful and positive reform. The Numbers
and Protocols communities, watching this
process through gritted teeth and very keen
for the transition to go ahead, can
hopefully celebrate what is happening. With
ICANN having a curious dual role for the
Names community (policy forum and IANA
functions operator), there has been no
alternative to making accountability
improvements now.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
(To my technical community friends - if
there’s any doubt in your mind about why we
need change – review the chronology,
remember the pushback, remember what you
guys faced early this year.)</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
We’re all close to the end of the debate.
You can sense it – proposals are
crystallising, timeframes are compressing,
volunteers are at the end of reasonable
commitments of time and energy.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
The imperatives now are to see things
through: to stick with the multistakeholder
process that listens to all perspectives but
gives nobody a right of veto; the
accountability framework the community
requires to accept the transition going
ahead; and the changes to ICANN’s culture
that will flow from a new accountability
settlement. </p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
Dublin is a week away. The elephant in the
room (the CCWG’s proposal and the ICANN
Board’s counterproposal for the way to
crystallise accountability powers) will need
to be resolved, or eaten, or thrown in the
ocean.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
My preference is of course for the product
of the multistakeholder process, the model
the CCWG has developed in public and with
the involvement of all stakeholders. But
unlike some others, I am not proclaiming
bottom lines on any of the “how” – it is the
“what,” the requirements and ability to meet
them, that matter. </p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
The “what” is ensuring the Internet
community, able to organise through ICANN’s
open groupings, can hold a corporation with
hundreds of staff, hundreds of millions of
dollars, tight links with the American
government, a monopoly ability to extract
rents from the domain name industry, and a
natural institutional desire to be as free
of restraint as it can – can hold all that
to account, given the huge imbalance of
power, knowledge, resources that tilt the
playing field of accountability entirely in
ICANN’s favour.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
Beyond the "elephant," there are lots of
other details that need to be sorted out.
It all matters – NTIA have been clear the
proposal has to be bullet proof.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
In the end though, if there isn’t an
accountability settlement that achieves
consensus, then there isn’t going to be a
proposal bullet proof or not.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
No accountability proposal – no IANA
Stewardship Transition proposal. No
transition proposal – no transition.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
No transition? All those risks the
transition is designed to head off come back
to life. And the multistakeholder approach
discredited to boot.</p>
<p style="margin:0px 0px
10px;color:rgb(45,48,49);font-family:'Gotham
Rounded SSm A','Gotham Rounded SSm
B';font-size:14px;line-height:25.2px">
Those are the stakes on the table as we head
to Dublin.</p>
<div style="margin-top: 0px; margin-right:
0px; margin-bottom: 0px; margin-left: 0px;
color: rgb(45, 48, 49); font-family: 'Gotham
Rounded SSm A', 'Gotham Rounded SSm B';
font-size: 14px; line-height: 25.2px; ">
Two final thoughts: where there’s a will
there’s a way. And as an old high-school
teacher used to say to me, “not easy, not
optional.”</div>
<span class="HOEnZb"><font color="#888888">
<div><br>
</div>
</font></span></div>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr"
style="font-size:small">Jordan
Carter<br>
<br>
Chief Executive <br>
<b>InternetNZ</b><br>
</div>
<div dir="ltr"
style="font-size:small"><br>
+64-4-495-2118 (office) |
+64-21-442-649 (mob)<br>
Email: <a moz-do-not-send="true"
href="mailto:jordan@internetnz.net.nz" style="color:rgb(17,85,204)"
target="_blank">jordan@internetnz.net.nz</a> <br>
Skype: jordancarter<br>
</div>
<div style="font-size:small">Web:
<a moz-do-not-send="true"
href="http://www.internetnz.nz/"
target="_blank">
www.internetnz.nz</a> </div>
<div dir="ltr"
style="font-size:small"><br>
<i>A better world through a
better Internet </i></div>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</span>
</div>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Accountability-Cross-Community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Matthew Shears
Director - Global Internet Policy and Human Rights
Center for Democracy & Technology
<a class="moz-txt-link-abbreviated" href="mailto:mshears@cdt.org">mshears@cdt.org</a>
+ 44 771 247 2987 </pre>
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
<tr>
<td style='border:none;padding:0px 15px 0px 8px'>
<a href="https://www.avast.com/antivirus">
<img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" />
</a>
</td>
<td>
<p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
This email has been checked for viruses by Avast antivirus software.
<br><a href="https://www.avast.com/antivirus">www.avast.com</a>
</p>
</td>
</tr>
</table>
<br />
</body>
</html>