<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
+ 1 Keith - well put.<br>
<br>
<div class="moz-cite-prefix">On 5/20/2015 12:44 PM, Drazek, Keith
wrote:<br>
</div>
<blockquote
cite="mid:515216DA-58B9-4522-BC2C-6AF42D5114AF@verisign.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div><span></span></div>
<div>
<div>Hi Chris,</div>
<div><br>
</div>
<div>I think there's a fundamental flaw in your assessment. You
appear to be looking at this question through the lens of the
past and present, where NTIA holds the enforcement function
("enforceability") through its ability to rebid and transfer
the IANA functions contract if the ICANN Board and management
acts inappropriately. That is the existing and necessary check
on the Board's decision-making power. </div>
<div><br>
</div>
<div>Without NTIA in its current role, the community MUST have
the ability to check the Board's power, and the only way to
secure that check is to create legal enforceability.
Otherwise, the Board has ultimate authority, even if its
decisions are inconsistent with the interests and desires of
the community ICANN is supposed to serve.</div>
<div><br>
</div>
<div>You are proposing a transfer of power from NTIA to the
ICANN Board, which has a fiduciary obligation to first serve
the interests of the corporation. Alternatively, proponents of
legal enforceability are in favor of transferring final
authority to ICANN's multi-stakeholder community. </div>
<div><br>
</div>
<div>We should all be looking at this through the lens of the
future, when NTIA no longer holds the tether and is only
participating through the GAC. How do we, the
multi-stakeholder community, ensure that ICANN and its future
Boards and management are truly accountable once the NTIA
back-stop is gone? </div>
<div><br>
</div>
<div>The answer is to ensure the Board's decisions, in very
limited areas, can be challenged and overturned by a
significant majority of the community. We need to protect
against the "catastrophic" scenario you referenced. According
to our independent legal advisors, the best (and perhaps only)
way to guarantee this is through legal enforceability. </div>
<div><i><br>
</i></div>
<div>You asked, <i>"</i><span style="background-color: rgba(255,
255, 255, 0);"><i>Is addressing this most unlikely scenario
worth the significant structural changes a membership
model would require?"
</i>I believe the answer is yes. Not only worth it, but
necessary.</span></div>
<div><br>
</div>
<div>Regards,</div>
<div>Keith</div>
<div><br>
</div>
<div><br>
On May 20, 2015, at 2:40 AM, Chris Disspain <<a
moz-do-not-send="true" href="mailto:ceo@auda.org.au">ceo@auda.org.au</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span style="font-family: 'Verdana'; font-size: 13px;
color: rgb(102, 102, 102);">For clarity, the last sentence
of paragraph 8 below should read:
<div class=""><br class="">
</div>
<div class=""><span class="" style="color: rgb(68, 68,
68);">"However, </span><font class="" color="#444444">I
cannot think of a single</font><span class=""
style="color: rgb(68, 68, 68);"> example of a failure
throughout the history of ICANN that did result or
would have resulted in the community acting as one
against an action or decision of the ICANN Board."</span><br
class="">
<div class="">
<p class="p1"><br class="">
</p>
<p class="p1"><br class="">
</p>
<p class="p2">Cheers,</p>
<p class="p3"><br class="">
</p>
<p class="p2">Chris</p>
</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 20 May 2015, at 16:13 , Chris
Disspain <<a moz-do-not-send="true"
href="mailto:ceo@auda.org.au" class="">ceo@auda.org.au</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span style="font-family: Verdana;
font-size: 13px; font-style: normal;
font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; color: rgb(102,
102, 102);" class="">
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444">Jordan, All,<o:p
class=""></o:p></font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444"> </font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444">Thank you Jordan,
for attempting to bring some focus to the
current discussion about the UA model,
membership structures and all of the related
issues.<o:p class=""></o:p></font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444"><br class="">
</font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444">First of all, I
want to acknowledge that I concur with you
on a number points.<o:p class=""></o:p></font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444"> </font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444">I agree that we
need to develop a model that disrupts
ICANN’s operation as little as possible. We
can argue about how much disruption is
either possible or preferable, but the
principle is agreed. <o:p class=""></o:p></font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444"><br class="">
</font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444">I also agree that
levels of accountability are not “up to
scratch” and, irrespective of the model we
arrive at post-transition, these need to be
improved. </font><span class=""
style="color: rgb(68, 68, 68);">Many of the
improvements proposed by the CCWG: to the
IRP, reconsideration mechanisms and the role
of the ombudsman, the introduction of
fundamental bylaws and binding arbitration,
and the empowerment of the community to
spill the ICANN Board, are also supported.</span><span
class="" style="color: rgb(68, 68, 68);"> </span></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444"> </font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444">However, where I
disagree with you is in respect to the
absolute need for an <i class="">additional</i> mechanism,
to supersede the current IANA functions
contract, in order to ensure that the
community can ‘control’ the Board because it
has the right to bring a legal action in a
US court.</font><span class="" style="color:
rgb(68, 68, 68);"> </span></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444"> </font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444">I disagree with the
characterisation that the purpose of the
CCWG’s work is to wrest “control” from the
ICANN Board and deliver it to the
community. </font><span class=""
style="color: rgb(68, 68, 68);">From your
email, I gather that you are fundamentally
tying the concept of control to
“enforceability”, neither of which are goals
for the current process. </span><span
class="" style="color: rgb(68, 68, 68);">Rather,
I believe we are aiming to deliver a
structure where ICANN and its </span><font
class="" color="#444444">Board </font><span
class="" style="color: rgb(68, 68, 68);">are
held accountable to the community, via the
number of improvements I mentioned above.</span></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444"> </font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444">The need to assert
absolute “control” or enforceability could
only arise in the most catastrophic of
circumstances. </font><span class=""
style="color: rgb(68, 68, 68);">If we assume
a situation where proposed mechanisms for
escalation, independent review,</span><span
class="" style="color: rgb(68, 68, 68);"> </span><i
class="" style="color: rgb(68, 68, 68);">binding </i><span
class="" style="color: rgb(68, 68, 68);">arbitration
and direct instruction by the SOs and ACs
are not acknowledged by ICANN, wouldn’t the
entire multi-stakeholder model be
irreparably broken? </span><span class=""
style="color: rgb(68, 68, 68);">Is
addressing this most unlikely scenario worth
the significant structural changes a
membership model would require? </span></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444"> </font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444">Further, you refer
to a “long list” of community concerns about
ICANN’s current operations. </font><span
class="" style="color: rgb(68, 68, 68);">I
wonder whether these concerns are actually
held by individuals (or individual
constituencies) on particular issues and
have been aggregated in to a larger picture
of overall community dissatisfaction? </span><font
class="" color="#444444">Concerns by
distinct groups on particular topics can
certainly be dealt with by the increased
robustness proposed to ICANN’s bylaws and
operations.<span
class="Apple-converted-space"> </span></font><span
class="" style="color: rgb(68, 68, 68);">However, </span><font
class="" color="#444444">I cannot think of a
single</font><span class="" style="color:
rgb(68, 68, 68);"> example of a failure
throughout the history of ICANN that did
result or would have resulted in the
community as one against an action or
decision of the ICANN Board. </span></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444"> </font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444">To be clear – I am
100% supportive of improvements to
accountability. I believe that the CCWG has
initiated extremely useful work in
identifying these mechanisms.</font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444"><br class="">
</font></div>
<div class="" style="margin: 0cm 0cm 0.0001pt;"><font
class="" color="#444444">I remain
unconvinced regarding the argument that
accountability=control=enforceability, and
the subsequent recommendations of the CCWG
that arise from this assumption.</font></div>
<div apple-content-edited="true" class="">
<div style="margin: 0px; font-style: normal;
font-variant: normal; font-weight: normal;
font-size: 12px; line-height: normal;
font-family: Helvetica; min-height: 14px;"
class="">
<font class="" color="#444444"
face="Verdana" size="2"><br class="">
</font></div>
<div style="margin: 0px; font-style: normal;
font-variant: normal; font-weight: normal;
font-size: 12px; line-height: normal;
font-family: Helvetica; min-height: 14px;"
class="">
<br class="">
</div>
<div style="margin: 0px; font-style: normal;
font-variant: normal; font-weight: normal;
font-size: 13px; line-height: normal;
font-family: Verdana; color: rgb(148, 67,
251);" class="">
Cheers,</div>
<div style="margin: 0px; font-style: normal;
font-variant: normal; font-weight: normal;
font-size: 13px; line-height: normal;
font-family: Verdana; color: rgb(148, 67,
251); min-height: 16px;" class="">
<br class="">
</div>
<div style="margin: 0px; font-style: normal;
font-variant: normal; font-weight: normal;
font-size: 13px; line-height: normal;
font-family: Verdana; color: rgb(148, 67,
251);" class="">
Chris</div>
</div>
<br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On 20 May 2015, at 15:33 ,
Jordan Carter <<a
moz-do-not-send="true"
href="mailto:jordan@internetnz.net.nz"
class="">jordan@internetnz.net.nz</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">We need legal
persons to be members of ICANN.
<div class=""><br class="">
</div>
<div class="">They can be individual
humans or they can be organisations.</div>
<div class=""><br class="">
</div>
<div class="">UAs are the lightest
touch, most easily controlled,
non-human form of person that can fit
this mould.</div>
<div class=""><br class="">
</div>
<div class="">I do not understand the
propensity of parts of our community
to over-complicate things that look
reasonably straight forward from other
points of view. Has ICANN always been
like this? (Answers own question - it
can't have been, otherwise it would
never be organised the way it is
today....)</div>
<div class=""><br class="">
</div>
<div class="">cheers</div>
<div class="">Jordan</div>
<div class=""><br class="">
</div>
</div>
<div class="gmail_extra"><br class="">
<div class="gmail_quote">On 20 May 2015
at 17:21, Alan Greenberg<span
class="Apple-converted-space"> </span><span
dir="ltr" class=""><<a
moz-do-not-send="true"
href="mailto:alan.greenberg@mcgill.ca"
target="_blank" class="">alan.greenberg@mcgill.ca</a>></span><span
class="Apple-converted-space"> </span>wrote:<br
class="">
<blockquote class="gmail_quote"
style="margin: 0px 0px 0px 0.8ex;
border-left-width: 1px;
border-left-color: rgb(204, 204,
204); border-left-style: solid;
padding-left: 1ex;">
Avri, I think that you are generally
correct. We are putting this entire
infrastructure in place because we
want to be able to take ICANN or the
Board to court if they do not follow
the rules. I tend to agree with the
auDA comment that if it ever gets to
that stage, we are REALLY in
trouble, and a simple court decision
is not likelt to fix it.<br class="">
<br class="">
But that nothwithstanding, we
supposedly ned that UA because they
can take legal action. But if the UA
representatives do not listen to the
SO/AC. the SO/AC cannot take that
rep to court, because the SO/AC has
no legal persona. So we are again
left with a discontinuity where
something is largely unenforceable
and we have to take it on faith that
they will do the right thing.<br
class="">
<br class="">
Of course, the UA reps and the Board
members we select are basically
drawn from the same pool, perhaps
separated by a few years.<br
class="">
<br class="">
The difference between a Board
member and a UA rep is the Board
member has a duty to the
corporation, and the UA rep can, in
theory, be required to take
instruction from the SO/AC. But
enforcing that theory may be the
rub.<span class="HOEnZb"><font
class="" color="#888888"><br
class="">
<br class="">
Alan</font></span>
<div class="HOEnZb">
<div class="h5"><br class="">
<br class="">
At 20/05/2015 12:41 AM, Avri
Doria wrote:<br class="">
<blockquote class="gmail_quote"
style="margin: 0px 0px 0px
0.8ex; border-left-width: 1px;
border-left-color: rgb(204,
204, 204); border-left-style:
solid; padding-left: 1ex;">
Hi,<br class="">
<br class="">
I think I understand the
argument about members
becoming that to which<br
class="">
ICANN, and its Board, are
responsible and accountable.
From that<br class="">
perspective it sounds really
good.<br class="">
<br class="">
What I have having trouble
understanding is an
accountability structure<br
class="">
were there is a discontinuity
between the SOAC and the UA.
If each of<br class="">
the Board designating SOAC
were the UA, it think I would
understand.<br class="">
But I just do not see how the
UA are accountable to the
people and<br class="">
organizations that participate
in each of the SOAC. Yes, the
SOAC<br class="">
designates it UA
representative, but how is
(s)electing one of these any<br
class="">
more accountable than
(s)electing the Board as we do
now. Don't we just<br
class="">
move the perceived/possible
unaccountability down a layer
in the hierarchy?<br class="">
<br class="">
I think I am as comfortable
with complexity as the next
person. And I<br class="">
understand how in computer
science any problem can solved
by adding<br class="">
another layer of indirection,
but in this case the extra
layer we are<br class="">
creating does not seem to
really be accountable to
anyone but itself,<br class="">
except by (s)election
procedures.<br class="">
<br class="">
I am sure I am missing some
critical bit of understanding
and hope<br class="">
someone can explain the chain
of accountability in the
membership<br class="">
model. I feel that we are
still hand-waving a bit in the
explanations.<br class="">
In a sense it seems as if we
are creating a 'council' that
is omnipotent<br class="">
in the powers it is given,
except that they can somehow
be replaced.<br class="">
<br class="">
Thanks and apologies for my
persistent confusion.<br
class="">
<br class="">
avri<br class="">
<br class="">
<br class="">
<br class="">
On 20-May-15 01:14, Jordan
Carter wrote:<br class="">
> Hi all<br class="">
><br class="">
> This thread is useful to
tease out some of the
questions and concerns<br
class="">
> and confusions with the
UA model, and as rapporteur
for the WP<br class="">
> responsible for refining
this part of the proposal I am
reading it avidly.<br class="">
><br class="">
> I just want to take the
opportunity to remind us all
why membership<br class="">
> (or something analogous)
is an important aspect of the
reforms we are<br class="">
> proposing - no matter the
precise details.<br class="">
><br class="">
> At the moment without
members, ICANN is
fundamentally controlled by<br
class="">
> the Board. The only
external constraint is the
IANA functions contract<br
class="">
> with NTIA. The long list
of community concerns and
examples detailed<br class="">
> by our earlier work in
this CCWG shows that even with
that constraint,<br class="">
> accountability isn't up
to scratch.<br class="">
><br class="">
> We are working on a
settlement without that NTIA
contract.<br class="">
> Accountability has to get
better even *with* the
contract.<br class="">
> Fundamentally better,
without it.<br class="">
><br class="">
> Either we have a
membership structure or some
other durable approach<br
class="">
> that firmly embeds the
stewardship of ICANN and the
DNS in the ICANN<br class="">
> community, or... we
remain with Board control.<br
class="">
><br class="">
> Given ICANN's history,
anyone who is advocating a
continuation of<br class="">
> Board control is arguing
for a model that can't be
suitably<br class="">
> accountable, and that
seems highly likely to fail
over time, with real<br
class="">
> risks to the security and
stability of the DNS.<br
class="">
><br class="">
> A real, fundamental
source of power over the
company absent the<br class="">
> contract *has* to be
established. The membership
model is the most<br class="">
> suitable one to achieve
that that we have considered
so far.<br class="">
><br class="">
> So: we need to be
creative and thoughtful in how
we make that model<br class="">
> work in a fashion that
disrupts ICANN's general
operation as little as<br
class="">
> possible. But the key
there is "as possible." Real
change is needed<br class="">
> and much refinement and
comment is needed.<br class="">
><br class="">
> If there are proposals to
achieve the same shift in
control from ICANN<br class="">
> the corporation to ICANN
the community, I hope they
come through in<br class="">
> the comment period. So
far, none have - but there are
still two weeks<br class="">
> of comments to go.<br
class="">
><br class="">
> cheers<br class="">
> Jordan<br class="">
><br class="">
><br class="">
> On 20 May 2015 at 10:45,
Malcolm Hutty <<a
moz-do-not-send="true"
href="mailto:malcolm@linx.net"
target="_blank" class="">malcolm@linx.net</a><br
class="">
> <mailto:<a
moz-do-not-send="true"
href="mailto:malcolm@linx.net"
target="_blank" class="">malcolm@linx.net</a>>>
wrote:<br class="">
><br class="">
> This whole thread
seems to have massively
overcomplicated the<br
class="">
> question.<br class="">
><br class="">
><br class="">
> Unless I have missed
something, the only reason we
need "members"<br class="">
> is to<br class="">
> stand as
plaintiff-of-record in a
lawsuit against the ICANN
Board<br class="">
> complaining that the
Board has failed to adhere to
the corporations<br class="">
> bylaws. Such a
lawsuit would in reality be
conducted by an SO or<br
class="">
> AC, but<br class="">
> a person with legal
personality needs to act as
plaintiff-of-record.<br
class="">
><br class="">
> Why not simply
proceed, as Samantha
suggested, with the SOACs'<br
class="">
> Chairs as<br class="">
> the members of the
corporation? Could the
Articles (or Bylaws, as<br
class="">
> appropriate) not
simply identify the SOACs'
Chairs as the members, ex<br
class="">
> officio and pro
tempore?<br class="">
><br class="">
> An SOAC Chair that
refused to act as
plaintiff-of-record when
required<br class="">
> to do so by his SOAC
could simply be replaced.
Likewise a Chair that<br
class="">
> went rogue and
initiated a lawsuit without
their consent.<br class="">
><br class="">
> You can't make the
SOAC a member without turning
them into UAs,<br class="">
> with all<br class="">
> the attendent
complexity. But I don't see
that there should be any<br
class="">
> such<br class="">
> problem with
designating the chair of a
SOAC, who will be a natural<br
class="">
> person, as a member
of the corporation; the fact
that the SOAC is<br class="">
> not a<br class="">
> UA is then
irrelevant.<br class="">
><br class="">
> In the event that
there were any dispute as to
whether a particular<br
class="">
> person is in truth an
SOAC Chair, this would surely
be a simple<br class="">
> preliminary matter of
fact for the court. It is
surely beyond dispute<br
class="">
> that if the Articles
designated "Alan Greenberg" as
the member, it<br class="">
> would<br class="">
> be a matter of fact
as to whether or not the
person before the<br class="">
> court was<br class="">
> indeed Alan
Greenberg; surely it is the
same as to whether the person<br
class="">
> before the court is
"the current Chair of ALAC",
if that should be<br class="">
> what<br class="">
> is specified in the
Articles?<br class="">
><br class="">
> Malcolm.<br class="">
><br class="">
> --<br class="">
> Malcolm
Hutty | tel:<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="tel:%2B44%2020%207645%203523"
value="+442076453523"
target="_blank" class="">+44
20 7645 3523</a><br class="">
>
<a class="moz-txt-link-rfc2396E" href="tel:%2B44%2020%207645%203523"><tel:%2B44%2020%207645%203523></a><br
class="">
> Head of Public
Affairs | Read the LINX Public
Affairs blog<br class="">
> London Internet
Exchange |<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="http://publicaffairs.linx.net/"
target="_blank" class="">http://publicaffairs.linx.net/</a><br
class="">
><br class="">
>
London Internet Exchange Ltd<br
class="">
> 21-27 St
Thomas Street, London SE1 9RY<br
class="">
><br class="">
> Company
Registered in England No.
3137929<br class="">
> Trinity Court,
Trinity Street, Peterborough
PE1 1DA<br class="">
><br class="">
><br class="">
>
_______________________________________________<br
class="">
>
Accountability-Cross-Community
mailing list<br class="">
> <a
moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org"
target="_blank" class="">Accountability-Cross-Community@icann.org</a><br
class="">
> <mailto:<a
moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org"
target="_blank" class="">Accountability-Cross-Community@icann.org</a>><br
class="">
> <a
moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
target="_blank" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br
class="">
><br class="">
><br class="">
><br class="">
><br class="">
> --<br class="">
> Jordan Carter<br class="">
><br class="">
> Chief Executive<br
class="">
> *InternetNZ*<br class="">
><br class="">
><span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="tel:04%20495%202118"
value="+6444952118"
target="_blank" class="">04
495 2118</a><span
class="Apple-converted-space"> </span>(office)
|<span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="tel:%2B64%2021%20442%20649"
value="+6421442649"
target="_blank" class="">+64
21 442 649</a><span
class="Apple-converted-space"> </span>(mob)<br
class="">
><span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="mailto:jordan@internetnz.net.nz"
target="_blank" class="">jordan@internetnz.net.nz</a><span
class="Apple-converted-space"> </span><mailto:<a
moz-do-not-send="true"
href="mailto:jordan@internetnz.net.nz"
target="_blank" class="">jordan@internetnz.net.nz</a>><br
class="">
> Skype: jordancarter<br
class="">
><br class="">
> /A better world through a
better Internet /<br class="">
><br class="">
><br class="">
><br class="">
>
_______________________________________________<br
class="">
>
Accountability-Cross-Community
mailing list<br class="">
><span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org"
target="_blank" class="">Accountability-Cross-Community@icann.org</a><br
class="">
><span
class="Apple-converted-space"> </span><a
moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
target="_blank" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br
class="">
<br class="">
<br class="">
---<br class="">
This email has been checked
for viruses by Avast antivirus
software.<br class="">
<a moz-do-not-send="true"
href="http://www.avast.com/"
target="_blank" class="">http://www.avast.com</a><br
class="">
<br class="">
_______________________________________________<br class="">
Accountability-Cross-Community
mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org"
target="_blank" class="">Accountability-Cross-Community@icann.org</a><br
class="">
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
target="_blank" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br
class="">
</blockquote>
<br class="">
_______________________________________________<br class="">
Accountability-Cross-Community
mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org"
target="_blank" class="">Accountability-Cross-Community@icann.org</a><br
class="">
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
target="_blank" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br
class="">
</div>
</div>
</blockquote>
</div>
<br class="">
<br class="" clear="all">
<div class=""><br class="">
</div>
--<span class="Apple-converted-space"> </span><br
class="">
<div class="gmail_signature">
<div dir="ltr" class="">
<div class="">
<div dir="ltr" class="">Jordan
Carter<br class="">
<br class="">
Chief Executive<span
class="Apple-converted-space"> </span><br
class="">
<b class="">InternetNZ</b><br
class="">
<br class="">
04 495 2118 (office) | +64 21
442 649 (mob)<br class="">
<a moz-do-not-send="true"
href="mailto:jordan@internetnz.net.nz"
target="_blank" class="">jordan@internetnz.net.nz</a><span
class="Apple-converted-space"> </span><br
class="">
Skype: jordancarter<br class="">
<br class="">
<i class="">A better world
through a better Internet </i><br
class="">
<br class="">
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br class="">
Accountability-Cross-Community mailing
list<br class="">
<a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org"
class="">Accountability-Cross-Community@icann.org</a><br
class="">
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</span><span style="font-family: Verdana;
font-size: 13px; font-style: normal;
font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px; float: none;
display: inline !important;" class="">_______________________________________________</span><br
style="font-family: Verdana; font-size: 13px;
font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing:
0px; -webkit-text-stroke-width: 0px;" class="">
<span style="font-family: Verdana; font-size:
13px; font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing:
0px; -webkit-text-stroke-width: 0px; float:
none; display: inline !important;" class="">Accountability-Cross-Community
mailing list</span><br style="font-family:
Verdana; font-size: 13px; font-style: normal;
font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal;
orphans: auto; text-align: start; text-indent:
0px; text-transform: none; white-space: normal;
widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px;" class="">
<a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org"
style="font-family: Verdana; font-size: 13px;
font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing:
0px; -webkit-text-stroke-width: 0px;" class="">Accountability-Cross-Community@icann.org</a><br
style="font-family: Verdana; font-size: 13px;
font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing:
0px; -webkit-text-stroke-width: 0px;" class="">
<a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
style="font-family: Verdana; font-size: 13px;
font-style: normal; font-variant: normal;
font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: auto; text-align:
start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing:
0px; -webkit-text-stroke-width: 0px;" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></div>
</blockquote>
</div>
<br class="">
</div>
</span></div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>Accountability-Cross-Community mailing list</span><br>
<span><a moz-do-not-send="true"
href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a></span><br>
<span><a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br>
<span></span><br>
<span></span><br>
</div>
</blockquote>
</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
Global Internet Policy and Human Rights
Center for Democracy & Technology (CDT)
+ 44 (0)771 247 2987</pre>
</body>
</html>