<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 29/11/13 14:11, Yannis Li wrote:<br>
</div>
<blockquote
cite="mid:A451A1FA-B7E7-4694-AB08-BD24AB49F44A@registry.asia"
type="cite">On 28/11/2013 10:00, Sally Costerton wrote:<br>
<div>
<div>
<div dir="ltr">
<div class="gmail_quote">
> Olivier<br>
> Just picked this up and I need to correct this. The
request from<br>
> Fadi/Adiel is for two contributors from civil society
to serve on the<br>
> Brazil Meeting Steering Committee which will be one
of the four groups<br>
> that were announced by CGI on Tuesday that will
organize the meeting<br>
> in Brazil next year. This request came from Adiel on
the 1net<br>
> coordination list and this is the one that has a
deadline attached.<br>
><br>
> The meeting in London on Dec 12 and 13 is different.
It is a meeting<br>
> of the Panel members already announced last week and
Chaired by Vint<br>
> Cerf and President Thomas Ilves.<br>
<br>
I see that people are mixing the two issues -- and indeed,
based on the<br>
second hand information on the list, I was also mixing the
two issues.<br>
So as you can read: there is NO additional search for the
meeting on Dec<br>
12 & 13 according to Sally Costerton.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
This is a misunderstanding by Sally, then. :-) We are putting
forward names for the December 12 and 13 meeting not main in
response to Fadi's suggestion, but rather because it is our
expectation that the High Level Panel should be balanced as between
the stakeholder groups, and as such we are entitled to be more
evenly represented on the High Level Panel than we are now, with
representatives whom we, rather than ICANN, choose.<br>
<br>
<blockquote
cite="mid:A451A1FA-B7E7-4694-AB08-BD24AB49F44A@registry.asia"
type="cite">
<div>
<div>
<div dir="ltr">
<div class="gmail_quote">
On the issue of the request from Fadi/Adiel for two
contributors from<br>
civil society to serve on the Brazil Meeting Steering
Committee, this<br>
request was made on the 1net coordination list so this is
not something<br>
asked from the NCSG exclusively.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Agreed that that is a separate and equally important issue, and a
separate point that have made is that despite claims to the
contrary, it is now clear that 1net is not to be coordinating
stakeholder representation for the Brazil meeting. So we will not
be nominating people in response to any call that 1net makes, but
rather liaising directly with the Brazilian organisers in this
regard.<br>
<br>
<div class="moz-signature">-- <br>
<p style="font-size:9.0pt;color:black"><b>Dr Jeremy Malcolm<br>
Senior Policy Officer<br>
Consumers International | the global campaigning voice for
consumers</b><br>
Office for Asia-Pacific and the Middle East<br>
Lot 5-1 Wisma WIM, 7 Jalan Abang Haji Openg, TTDI, 60000 Kuala
Lumpur, Malaysia<br>
Tel: +60 3 7726 1599</p>
<!--<p style="font-size:9.0pt;color:black"><b>Your rights, our mission – download CI's Strategy 2015:</b> <a href="http://consint.info/RightsMission">http://consint.info/RightsMission</a></p>-->
<p style="font-size:9.0pt;color:black">Explore our new Resource
Zone - the global consumer movement knowledge hub | <a
href="http://www.consumersinternational.org/news-and-media/resource-zone">http://www.consumersinternational.org/news-and-media/resource-zone</a></p>
<p style="font-size:9.0pt;color:black">@Consumers_Int | <a
href="http://www.consumersinternational.org">www.consumersinternational.org</a>
| <a href="http://www.facebook.com/consumersinternational">www.facebook.com/consumersinternational</a></p>
<p style="font-size:8.0pt;color:#999999">Read our <a
href="http://www.consumersinternational.org/email-confidentiality"
target="_blank">email confidentiality notice</a>. Don't print
this email unless necessary.</p>
<p><strong><span style="color:red;">WARNING</span></strong><span
style="color:black;">: This email has not been encrypted. You
are strongly recommended to enable PGP or S/MIME encryption at
your end. For instructions, see <a href="http://jere.my/l/8m">http://jere.my/l/8m</a>.</span></p>
</div>
</body>
</html>