<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Dear Co-Chairs,</div><div><br></div><div>IANA is a function, not an entity.</div><div><br></div><div><br>el<br>-- <span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); "></span><div><span class="Apple-style-span" style="font-size: 13pt; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.294118); -webkit-composition-fill-color: rgba(175, 192, 227, 0.231373);">Sent from </span><span style="font-size: 13pt;">Dr Lisse's iPhone 6</span></div><div><br></div></div><div><br>On Apr 12, 2015, at 00:04, Avri Doria <<a href="mailto:avri@acm.org">avri@acm.org</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
Hi,<br>
<br>
Does not need to be unilateral, but in the end:<br>
<br>
CCWG is reponsible for ICANN accountabilty<br>
CWG is repsonsible for IANA accountabilty.<br>
<br>
Of course they should be coordinated. <br>
That is in our requirements.<br>
<br>
avri<br>
<br>
<div class="moz-cite-prefix">On 11-Apr-15 19:00, Greg Shatan wrote:<br>
</div>
<blockquote cite="mid:CA+aOHUT4Kts6-=h0SBeSFCLnC7mxbELdyDWZ+nTOfNpRbLi0kg@mail.gmail.com" type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-family:verdana,sans-serif">I don't think the
decision of what goes into WS1A can be or needs to be a
unilateral decision of either WG. The chairs of the two WGs
have been coordinating, and I believe that one of the key
items of coordination has been to identify "dependencies";
i.e., those aspects of the CCWG's work where the CWG is
depending on the CCWG to deliver a particular piece of the
puzzle.f</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">That said, I'm not sure
I can point to a particular document or list where these
dependencies are explicitly identified. That doesn't mean the
list doesn't exist. If it does, I would love to be pointed
toward it!</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">Greg</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sat, Apr 11, 2015 at 6:50 PM, Jordan
Carter <span dir="ltr"><<a moz-do-not-send="true" href="mailto:jordan@internetnz.net.nz" target="_blank">jordan@internetnz.net.nz</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Who would
define what is in WS1A? The CCWG or the CWG?
<div><br>
</div>
<div>J
<div>
<div class="h5"><span></span><br>
<br>
On Sunday, 12 April 2015, Avri Doria <<a moz-do-not-send="true" href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#330033"> Hi,<br>
<br>
Makes sense to me. I agree that some of the
grander plans for rebuilding the ICANN governance
structure may be difficult to sort out in the next
few days.<br>
<br>
However, the actual required contents of WS1A may
vary baside on whether CWG-IANA picks the fully
internal model or the affiliated model. Until
they make that decsion it may be hard to minimize
the requirements for WS1a. <br>
<br>
Hopefully the CWG will be able to resolve this
issue in its Monday/Tuesday intense meeting
schedule.<br>
<br>
avri<br>
<br>
<div>On 10-Apr-15 15:37, Greg Shatan wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default">
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px">I
am less concerned with (and also less
surprised by) the current acceleration in
the CCWG's work.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">However,
if the group does decide to triage its
work, I suggest we look at solutions
other than simply extending the
timeline. Specifically, I suggest the
following:</span></div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px"><b>Split
Work Stream 1 into 2 parts</b>:</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px"><br>
</div>
<div class="gmail_default">
<ul>
<li style="font-family:verdana,sans-serif;font-size:12.8000001907349px"><span style="font-size:12.8000001907349px">WS1A:
Items that are required by the
CWG-IANA in order to present a
complete proposal -- i.e., clear and
necessary dependencies.</span></li>
<li><span style="font-family:verdana,sans-serif;font-size:12.8000001907349px">WS1B:
Items that the CCWG believes must
be in place prior to the transition,
but which are not "clear and
necessary dependencies" of the
CWG-IANA proposal.</span><br>
</li>
</ul>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px">WS1A
really needs to stay on the current
timeframe. This work is intertwined and
interdependent with the CWG. Without it,
there is a very significant risk that the
CWG's work product will be perceived as so
incomplete that it will be difficult for
some groups to give reasonable comments.
Under this proposal, the Draft Report on
the 21st would be limited to the WS1A
items.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px">WS1B
would then be put to the side while WS1A
is completed for the Draft Proposal. It
would then be worked on immediately after
the proposal goes out. It could then be
the subject of a separate draft report to
come out a few (or more than a few) weeks
hence.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px">This
would lighten the load and allow us to
focus on fewer moving parts, while still
meeting the timeline with the most
time-sensitive part of our deliverable.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px">I
look forward to comments on this proposed
solution.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px"><br>
</div>
<div class="gmail_default" style="font-family:verdana,sans-serif;font-size:12.8000001907349px">Greg
Shatan</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Apr 10, 2015
at 12:35 PM, Alice Munyua <span dir="ltr"><<a moz-do-not-send="true">alice@dotafrica.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>
<p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt"><span style="font-family:Calibri">Dear
Colleagues, <br>
</span></p>
<p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt"><span style="font-family:Calibri"><br>
We also support concerns raised by
our colleagues regarding our
rather aggressive working schedule
and agree with Brazil and Denmark
that it may defeat the purpose of
inclusiveness. Particularly taking
into consideration that some
stakeholders like governments have
to reflect and consult widely to
enable informed and meaningful
participation.</span></p>
<p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt"><span style="font-family:Calibri">We
support the proposal to review the
timelines and explore solutions to
address and manage the various
expectations. </span></p>
<p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt"><span style="font-family:Calibri"> </span></p>
<p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt"><span style="font-family:Calibri">Best
regards<span></span></span></p>
<span><font color="#888888">
<p class="MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt"><span style="font-family:Calibri">Alice
Munyua</span></p>
</font></span>
<div>
<div> <br>
<br>
On 10/04/2015 19:28, <a moz-do-not-send="true">Jorge.Cancio@bakom.admin.ch</a>
wrote:<br>
</div>
</div>
</div>
<div>
<div>
<blockquote type="cite">
<pre>+1 to Julias comment. There is a risk of losing too many people at this speed, where I feel some comments and positions might be lost down the road, just because their proponents are not able to follow each and every meeting.
Regards
Jorge Cancio
Von meinem iPhone gesendet
Am 10.04.2015 um 15:56 schrieb Julia Katja Wolman <<a moz-do-not-send="true">jukacz@erst.dk</a><a moz-do-not-send="true"><mailto:jukacz@erst.dk></a>>:
Dear Co-Chairs, Colleagues,
Firstly, I would like to take the opportunity to thank you for your hard work and commitment to this important work.
Secondly, acknowledging that this is an iterative process and the challenges of the timeline it is however challenging to follow where we are in all of the issues under discussion. We are fast approaching a stage where it is crucial to have an overview/clarity of all the bits and pieces of the work going on in the CCWG. Therefore I would kindly ask if all of the most recent versions of the key documents under discussion could be sent in one email to the CCWG list before the next CCWG meeting on Tuesday 14 April. This would be much appreciated.
Good weekend to you all,
Best,
Julia
Julia Katja Wolman
DANISH BUSINESS AUTHORITY
Dahlerups Pakhus
Langelinie Allé 17
DK-2100 København Ø
Telephone: <a moz-do-not-send="true" href="tel:%2B45%203529%201000" value="+4535291000" target="_blank">+45 3529 1000</a>
Direct: <a moz-do-not-send="true" href="tel:%2B45%2035291308" value="+4535291308" target="_blank">+45 35291308</a>
E-mail: <a moz-do-not-send="true">jukacz@erst.dk</a><a moz-do-not-send="true"><mailto:jukacz@erst.dk></a>
<a moz-do-not-send="true" href="http://www.erhvervsstyrelsen.dk" target="_blank">www.erhvervsstyrelsen.dk</a><a moz-do-not-send="true" href="http://www.erhvervsstyrelsen.dk" target="_blank"><http://www.erhvervsstyrelsen.dk></a>
MINISTRY FOR BUSINESS AND GROWTH
P Please consider the environment before printing this email.
Fra: <a moz-do-not-send="true">accountability-cross-community-bounces@icann.org</a><a moz-do-not-send="true"><mailto:accountability-cross-community-bounces@icann.org></a> [<a moz-do-not-send="true">mailto:accountability-cross-community-bounces@icann.org</a>] På vegne af Mathieu Weill
Sendt: 10. april 2015 13:50
Til: <a moz-do-not-send="true">accountability-cross-community@icann.org</a><a moz-do-not-send="true"><mailto:accountability-cross-community@icann.org></a>
Emne: Re: [CCWG-ACCT] Objection to our present work planning
Dear Colleagues,
This is to mention that, as co chairs, we are closely monitoring this discussion. As you know, we introduced this new work plan during the last CCWG call, meeting at the time no objection. We are however receptive to the concerns raised and welcome constructive inputs.
Since I have just finished our CCWG-CWG co-chair coordination call, I can however confirm that the main reason for meeting the target date we set in Istanbul remains very much up to date : the CWG needs clarity on our proposals to confirm its own options. Delay on our side might jeopardize their timeline, which in turn affects the ICG, etc.
We will get back to the group on Monday, once we also have greater clarity on the status of work party progress.
Thanks to all of you for your commitment and inputs, which we encourage to focus on the working party inputs at this precise point.
Mathieu
Le 10/04/2015 07:34, Dr Eberhard W Lisse a écrit :
No, Cheryl, it is not, with all due respect to Ed.
It is again fiddling with process and not dealing with substance.
el
--
Sent from Dr Lisse's iPhone 6
On Apr 10, 2015, at 04:20, Cheryl Langdon-Orr <<a moz-do-not-send="true">langdonorr@gmail.com</a><a moz-do-not-send="true"><mailto:langdonorr@gmail.com></a>> wrote:
This is an *Excellent* suggestion in my humble opinion Ed...
Cheryl Langdon-Orr ... (CLO)
<a moz-do-not-send="true" href="http://about.me/cheryl.LangdonOrr" target="_blank">about.me/cheryl.LangdonOrr</a><a moz-do-not-send="true" href="http://about.me/cheryl.LangdonOrr" target="_blank"><http://about.me/cheryl.LangdonOrr></a>
On 10 April 2015 at 11:03, Edward Morris <<a moz-do-not-send="true">egmorris1@toast.net</a><a moz-do-not-send="true"><mailto:egmorris1@toast.net></a>> wrote:
Roelof,
I share your concern and like you I'm not going to be able to attend every general, subgroup and sub-subgroup meeting going forward. We all have lives away from ICANN and invariably there are going to be times when other aspects of our existence need to take priority. I'm just amazed and very grateful that there are those who are able to volunteer and donate such an incredible amount of time to our joint effort. This is an exceptional group of people.
I'm very happy that our immediate deadline was shifted from early to late April at the Istanbul meeting. It helped. I too wish we could go forward at an even more reasoned and considered pace. I can't attend the meeting tonight or, frankly, a few other nights where they have been scheduled. I'm committed to this project but I'm also committed to attending my own birthday party later this month. I sort of need to be there for that. So be it. Our CCWG is not operating in isolation and I do understand the need for a tight deadline. I don't like it, but I do understand it.
I do have one request, though, that would allow me to participate in as complete a manner as I can going forward given my own circumstances. Would it be possible, even at additional cost, to have staff or contracted help to produce complete transcripts of the CCWG and WP sessions on a maximum 24 hour turnaround (or something approaching that)? My concern is that those of us who can't be at every meeting would either not participate in future sessions we could attend, feeling we weren't up to date on matters, or, even worse, would drag down future proceedings as we tried to understand that which we missed. Audio recordings are nice, but time consuming. Fast track transcripts, I think, could help alleviate some problems caused by the intensive work schedule.
Thanks for considering,
Ed
On Thu, Apr 9, 2015 at 1:01 PM, Roelof Meijer <<a moz-do-not-send="true">Roelof.Meijer@sidn.nl</a><a moz-do-not-send="true"><mailto:Roelof.Meijer@sidn.nl></a>> wrote:
Dear co-chairs, dear all,
I find myself in agreement with Eberhard with regard to the steep increase
in the number of calls for both the CCWG as well as its subgroups like wp1
and acct-legal.
It frustrates me to see that, after a period during which we burned a lot
of time on -let me politely phrase it as „less relevant and/or out of
scope”- subjects and several of us warned against the deadline becoming
unreachable, we have know replaced the deadline that has become
unrealistic with a work planning that is simply absurd.
As a result, we now have roughly a two hour conference call every day of
the week, several days with two calls, and thus more calls in a week at
unholy hours.
I object to this way of working, as it makes the whole process far less
inclusive. Many of us have both a demanding job as well as a private life,
both of which we cherish. For me it is now simply unavoidable to miss a
significant part of the calls and impossible to deal with all the
necessary working groups’ work in-between them. I know that this is now
the case for quite a number of us.
We are rushing forward to reach a deadline which is nothing more by now
than a dead line, and in our hurry seem to accept that the process loses
inclusiveness, transparency and accountability, leaving us with an outcome
that will be of much lower quality.
I for one, find this unacceptable.
Best regards,
Roelof A. Meijer
CEO
SIDN | Meander 501 | 6825 MD | P.O.
Box 5022 | 6802 EA | ARNHEM | THE NETHERLANDS
T +31 (0)26 352 55 00<a moz-do-not-send="true" href="tel:%2B31%20%280%2926%20352%2055%2000" target="_blank"><tel:%2B31%20%280%2926%20352%2055%2000></a> | M +31 (0)6 11 395 775<a moz-do-not-send="true" href="tel:%2B31%20%280%296%2011%20395%20775" target="_blank"><tel:%2B31%20%280%296%2011%20395%20775></a> | F +31 (0)26 352 55 05<a moz-do-not-send="true" href="tel:%2B31%20%280%2926%20352%2055%2005" target="_blank"><tel:%2B31%20%280%2926%20352%2055%2005></a>
<a moz-do-not-send="true">roelof.meijer@sidn.nl</a><a moz-do-not-send="true"><mailto:roelof.meijer@sidn.nl></a>
| <a moz-do-not-send="true" href="http://www.sidn.nl" target="_blank">www.sidn.nl</a><a moz-do-not-send="true" href="http://www.sidn.nl" target="_blank"><http://www.sidn.nl></a> <a moz-do-not-send="true" href="http://www.sidn.nl/" target="_blank"><http://www.sidn.nl/></a>
On 08-04-15 14:15, "Dr Eberhard Lisse" <<a moz-do-not-send="true">el@lisse.NA</a><a moz-do-not-send="true"><mailto:el@lisse.NA></a>> wrote:
</pre>
<blockquote type="cite">
<pre>Thank you very much.
so next week 3 calls (Tuesday, Thursday, Friday, the latter of which
I could not make even if I wanted to (see below))?
The following week another three (Monday, and 2 on Tuesday)?
More than one call per week is already difficult enough to absorb,
but three? And then two on one day? When we are already spending
too much time on process and very little on substance?
This is not conducive to thoughtful deliberation and as I have said
numerous times I am opposed to rushing things through just because
of a perceived deadline, which in our case does not even exist in
reality.
I object to this.
And while we are at it, I have asked NUMEROUS times to have the
legal foundation of the USG's claim to the root and/or the IANA
function researched by our legal advisers. I was told it would be
done, but it has not from what I can see and my repeated requests in
this regards have been ignored by the Co-Chairs.
I have made several requests/suggestions in how to deal with the
GAO, which the Co-Chairs do not agree with. Be that as it may, I
reserve the rights to communicate my thoughts to the GAO as they
have explicitly requested/suggested.
I have extremely serious concerns about at least the passage of the
German collaborative white paper (or whatever it is called), which
as far as ccTLDs are concerned is totally our of order and
unacceptable, in as much it suggests that ccTLD/ccNSO policy being
taken over by governments (which as we all know is opposed to the
USG's stated intent.
The GAC Representative of Denmark has proposed in Istanbul during
the ad-hoc Stress Test Breakfast, what I understand to be a total
removal of ccNSO's policy making powers, in favor of governments
deciding. Using the words "Out with the Old" he stated that the
RFCs must be done away with. I am not clear whether this is the
position of the Representative, his government or the GAC, but when
read together with the above, this is not acceptable to me.
I have not that many concerns with regards to Delegation of a ccTLD
(after establishment), including a Transfer of an exsiting ccTLD.
But as far as Revocation of an incumbent ccTLD Manager is concerned,
I have stated numerous times, that we need to preserve the existing
rights of incumbent ccTLD Managers.
This is NOT negotiable.
And the best way of doing this is by way of the Framework of
Interpretation Principles.
Mr Chehade has apparently in public (and on the record) accused
senior ccTLD managers of not knowing how the IANA functions work.
As a ccTLD Manager with 24 years uninterrupted service I tend to
agree that I do not know how the IANA function is operated by the
current Function Manager (ICANN), though I do have a really good
idea how it SHOULD be operated.
Therefor I have requested that Mr Chehade explain to us how this
works. I can not find any feedback on this issue.
Unless these issues are addressed to my satisfaction (and I am not
saying that they must be resolved necessarily to my satisfaction) I
shall, as a ccNSO appointed member, be formally objecting to any
output of the CCWG-Accountability.
I am circulating this to the usual ccTLD lists as well.
greetings, el
On 2015-04-08 12:10, Brenda Brewer wrote:
</pre>
<blockquote type="cite">
<pre>Hi Eberhard,
Please see attachment in pdf format.
Best,
Brenda
</pre>
</blockquote>
<pre>[...]
--
Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist (Saar)
<a moz-do-not-send="true">el@lisse.NA</a><a moz-do-not-send="true"><mailto:el@lisse.NA></a> / * | Telephone: <a moz-do-not-send="true" href="tel:%2B264%2081%20124%206733" value="+264811246733" target="_blank">+264 81 124 6733</a><a moz-do-not-send="true" href="tel:%2B264%2081%20124%206733" target="_blank"><tel:%2B264%2081%20124%206733></a> (cell)
PO Box 8421 \ /
Bachbrecht, Namibia ;____/
_______________________________________________
ccTLDcommunity mailing list
<a moz-do-not-send="true">ccTLDcommunity@cctld-managers.org</a><a moz-do-not-send="true"><mailto:ccTLDcommunity@cctld-managers.org></a>
<a moz-do-not-send="true" href="http://www.lists.cctld-managers.org/mailman/listinfo/cctldcommunity" target="_blank">http://www.lists.cctld-managers.org/mailman/listinfo/cctldcommunity</a>
To unsubscribe please send a blank email to
<a moz-do-not-send="true">ccTLDcommunity-unsubscribe@lists.cctld-managers.org</a><a moz-do-not-send="true"><mailto:ccTLDcommunity-unsubscribe@lists.cctld-managers.org></a>
</pre>
</blockquote>
<pre>_______________________________________________
Accountability-Cross-Community mailing list
<a moz-do-not-send="true">Accountability-Cross-Community@icann.org</a><a moz-do-not-send="true"><mailto:Accountability-Cross-Community@icann.org></a>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
_______________________________________________
Accountability-Cross-Community mailing list
<a moz-do-not-send="true">Accountability-Cross-Community@icann.org</a><a moz-do-not-send="true"><mailto:Accountability-Cross-Community@icann.org></a>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
_______________________________________________
Accountability-Cross-Community mailing list
<a moz-do-not-send="true">Accountability-Cross-Community@icann.org</a><a moz-do-not-send="true"><mailto:Accountability-Cross-Community@icann.org></a>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
_______________________________________________
Accountability-Cross-Community mailing list
<a moz-do-not-send="true">Accountability-Cross-Community@icann.org</a><a moz-do-not-send="true"><mailto:Accountability-Cross-Community@icann.org></a>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
--
*****************************
Mathieu WEILL
AFNIC - directeur général
Tél: <a moz-do-not-send="true" href="tel:%2B33%201%2039%2030%2083%2006" value="+33139308306" target="_blank">+33 1 39 30 83 06</a>
<a moz-do-not-send="true">mathieu.weill@afnic.fr</a><a moz-do-not-send="true"><mailto:mathieu.weill@afnic.fr></a>
Twitter : @mathieuweill
*****************************
_______________________________________________
Accountability-Cross-Community mailing list
<a moz-do-not-send="true">Accountability-Cross-Community@icann.org</a><a moz-do-not-send="true"><mailto:Accountability-Cross-Community@icann.org></a>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
_______________________________________________
Accountability-Cross-Community mailing list
<a moz-do-not-send="true">Accountability-Cross-Community@icann.org</a>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing
list<br>
<a moz-do-not-send="true">Accountability-Cross-Community@icann.org</a><br>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Accountability-Cross-Community mailing list
<a moz-do-not-send="true">Accountability-Cross-Community@icann.org</a>
<a moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
</blockquote>
<br>
<br>
<br>
<hr style="border:none;color:#909090;background-color:#b0b0b0;min-height:1px;width:99%">
<table style="border-collapse:collapse;border:none">
<tbody>
<tr>
<td style="border:none;padding:0px 15px 0px
8px"> <a moz-do-not-send="true" href="http://www.avast.com/" target="_blank"> <img moz-do-not-send="true" src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" border="0"> </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 moz-do-not-send="true" href="http://www.avast.com/" target="_blank">www.avast.com</a> </p>
</td>
</tr>
</tbody>
</table>
<br>
</div>
</blockquote>
</div>
</div>
</div>
<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Jordan Carter<br>
Chief Executive, InternetNZ
<p><a moz-do-not-send="true" href="tel:%2B64-21-442-649" value="+6421442649" target="_blank">+64-21-442-649</a>
| <a moz-do-not-send="true" href="mailto:jordan@internetnz.net.nz" target="_blank">jordan@internetnz.net.nz</a></p>
<p>Sent on the run, apologies for brevity<br>
</p>
</font></span><br>
_______________________________________________<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 moz-do-not-send="true" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<br><br>
<hr style="border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;">
<table style="border-collapse:collapse;border:none;">
<tbody><tr>
<td style="border:none;padding:0px 15px 0px 8px">
<a href="http://www.avast.com/">
<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="http://www.avast.com/">www.avast.com</a>
</p>
</td>
</tr>
</tbody></table>
<br>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Accountability-Cross-Community mailing list</span><br><span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br></div></blockquote></body></html>