<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p><font size="+1"><font face="Lucida Grande">I did not comment on some of the other points you raised, Raoul, partly for the reasons which Robin has raised below. Furthermore, the last time I checked, Amr is a non-affiliated member of NCSG, so discussing
why NCUC should cover his travel is not just out of scope in a discussion re Council representation, it is inaccurate. Please let me know if I am wrong here, this is our membership list.
<a class="moz-txt-link-freetext" href="https://www.ncuc.org/about/membership/">https://www.ncuc.org/about/membership/</a><br>
</font></font></p>
<p><font size="+1"><font face="Lucida Grande">I am not sure what you are talking about when discussing PIR slots, and I think we should probably have another discussion at policy committee to clarify exactly how travel is funded at ICANN, as I gather there
is quite a bit of confusion. I certainly find the discussions confusing, and I think I am not alone.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">I am very, very focused on how much work some people are doing....attending council, ccwg, and pdp meetings. Reviewing documents. Listening to recordings and reviewing transcripts. Responding to complex eamil
threads and arguments. Writing comments, letters, blogs and summaries, all on the actual work that ICANN and its stakeholders are working on. I would respectfully submit that this ought to be our priority. We are blessed with many excellent members of NCSG,
who are knowledgible about Internet-related matters and work hard in their regular lives. However, it is the ones who are actually producing product for us....work in the committees here, that I think we need at public meetings. We are at a critical point
for burnout....if we lost two or three key people who are doing most of the work at NCSG, we would become irrelevant. Sorry to be blunt, and I mean no offence to those who are not actually engaged in our work...everyone has their priorities and not everyone
has the dozens of hours a week required to devote to these tasks. But this is what we are here to do.</font></font></p>
<p><font size="+1"><font face="Lucida Grande">kind regards Stephanie</font></font><br>
</p>
<div class="moz-cite-prefix">On 2019-01-05 18:36, Robin Gross via NCSG-EC wrote:<br>
</div>
<blockquote type="cite" cite="mid:C351E8D1-1F83-47F9-BCEB-BBF6346D997C@ipjustice.org">
Thanks, Raoul. It is extremely important that these NCSG travel slots remain faithful to NCSG purposes and are not used by the underlying constituencies instead of by the NCSG. NCSG has an important separation of powers built into our 2-tiered system (NCSG
and constituencies), and we need to maintain that separation of powers by ensuring that NCSG resources are put toward NCSG uses, and not siphoned off to the underlying constituencies.
<div class=""><br class="">
</div>
<div class="">We are NCSG Executive Committee Members charged with putting NCSG resources to NCSG purposes in this instance. It is important we do not allow allegiances to particular constituencies tempt us into diverting NCSG resources away from NCSG purposes
and toward constituency purposes instead. It is up to us to maintain this separation of powers and keep focused on the interest we are charged with advancing on this committee, the NCSG.</div>
<div class=""><br class="">
</div>
<div class="">If you have questions about NCUC’s use of travel slots, please take it up with the constituency. This is a NCSG list for NCSG business. Who is wearing a red shirt and who is wearing a blue shirt simply isn’t relevant to this conversation on
NCSG resources. We aren't going down that path.</div>
<div class=""><br class="">
</div>
<div class="">Best,</div>
<div class="">Robin<br class="">
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jan 5, 2019, at 3:08 PM, Raoul Plommer <<a href="mailto:plommer@gmail.com" class="" moz-do-not-send="true">plommer@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">To be clear, Martin has been working on the RPM PDP, not the EPDP.
<div class=""><br class="">
</div>
<div class="">I see you commented on none of the other points I raised so maybe you could do that now?<br class="">
<br class="">
How many people are coming to Kobe from the NCUC? While I totally agree that Amr is a strong advocate for the NCSG policies in the GNSO, why aren't you using one of the many NCUC slots for him? Who's using the PIR-slot? That seems like a natural choice for
Amr from my point of view. Like I said, NPOC has very little choices over our few slots and Martin's replacement is now one of them. We also want Martin's replacement to attend the NPOC sessions and do work for us like he has always done. Tapani is willing
to do this, like he has done in the past.<br class="">
<br class="">
Tapani has maybe not attended PDPs, but he's written quite a bit of policy for the Finnish government on digital rights and has a wealth of experience in dissecting policy and analysing it.</div>
<div class=""><br class="">
</div>
<div class="">-Raoul</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="">On Sun, 6 Jan 2019 at 00:48, Robin Gross via NCSG-EC <<a href="mailto:ncsg-ec@lists.ncsg.is" class="" moz-do-not-send="true">ncsg-ec@lists.ncsg.is</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div style="overflow-wrap: break-word;" class="">As this is travel slot and replacement specifically for NCSG GNSO policy work, I think it must be used for that purpose. That means it should go to someone who is most advancing NCSG’s policy work, particularly
the GNSO Council work. Given that important understanding, I think Amr and Farell are the two strongest candidates that we’ve seen so far. Amr is knee-deep in GNSO policy, particularly the EPDP and is just coming off time as a GNSO policy staff member, so
Amr really knows what is happening in that space and is best able to advocate for NCSG’s interests there. Farrell is also an active member of the NCSG policy committee, is keeping on top of NCSG policy work, and has made significant contributions on that
front in recent months, so he’d be my second choice for this GNSO policy work slot.
<div class=""><br class="">
</div>
<div class="">Thanks,</div>
<div class="">Robin<br class="">
<div class=""><br class="">
<div class="">
<blockquote type="cite" class="">
<div class="">On Jan 5, 2019, at 2:09 PM, Raoul Plommer via NCSG-EC <<a href="mailto:ncsg-ec@lists.ncsg.is" target="_blank" class="" moz-do-not-send="true">ncsg-ec@lists.ncsg.is</a>> wrote:</div>
<br class="gmail-m_3595950184674429608Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">I think our strongest candidates so far are Amr and Tapani, and because NPOC has only one seat in the council, I'd actually like to see Martin replaced by another competent NPOC member if we had one. I think Tapani certainly is more
than capable to handle the council's F2F meetings and he's been following the list until now, so yeah, I'd really want to see him there. It's also about Tapani working for NPOC during the meeting, as well as keeping him activated overall.<br class="">
<br class="">
There are also other available options that NCUC has to get Amr there, and I have to say I'm somewhat surprised he's not given a PIR-slot, for example. NPOC has really none of these other possible slots at the moment, apart from the standard four of the constituency
and NCSG EC slot. With Dave using NPOC's CROP-slot (as opposed to NCUC's) and Martin missing, we'd only have five members coming to Kobe, as it is. How many does NCUC have coming over?<br class="">
<br class="">
-Raoul</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="">On Sat, 5 Jan 2019 at 21:10, Stephanie Perrin via NCSG-EC <<a href="mailto:ncsg-ec@lists.ncsg.is" target="_blank" class="" moz-do-not-send="true">ncsg-ec@lists.ncsg.is</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div class="">
<p class=""><font class="" size="+1"><font class="" face="Lucida Grande">While this statement of interest is a little lean, we all know that Tapani was EC Chair recently and is well versed in council matters. I am therefore not proposing to ask him for more
details, unless someone on the EC wishes me to.<br class="">
</font></font></p>
<p class=""><font class="" size="+1"><font class="" face="Lucida Grande">Stephanie</font></font><br class="">
</p>
<div class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-forward-container">
<br class="">
<br class="">
-------- Forwarded Message --------
<table class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-email-headers-table" cellspacing="0" cellpadding="0" border="0">
<tbody class="">
<tr class="">
<th class="" valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject: </th>
<td class="">Re: Replacement for a council member in ICANN 64</td>
</tr>
<tr class="">
<th class="" valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
<td class="">Sat, 5 Jan 2019 07:17:05 +0200</td>
</tr>
<tr class="">
<th class="" valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
<td class="">Tapani Tarvainen <a class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-txt-link-rfc2396E" href="mailto:ncsg@tapani.tarvainen.info" target="_blank" moz-do-not-send="true">
<ncsg@tapani.tarvainen.info></a></td>
</tr>
<tr class="">
<th class="" valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
<td class="">Stephanie Perrin <a class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-txt-link-rfc2396E" href="mailto:stephanie.perrin@MAIL.UTORONTO.CA" target="_blank" moz-do-not-send="true">
<stephanie.perrin@MAIL.UTORONTO.CA></a></td>
</tr>
<tr class="">
<th class="" valign="BASELINE" nowrap="nowrap" align="RIGHT">CC: </th>
<td class="">Maryam Bakoshi <a class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-txt-link-rfc2396E" href="mailto:maryam.bakoshi@icann.org" target="_blank" moz-do-not-send="true">
<maryam.bakoshi@icann.org></a></td>
</tr>
</tbody>
</table>
<br class="">
<br class="">
Hi Stephanie,<br class="">
<br class="">
Count me in. Even though I'm not currently in any working group<br class="">
apart from being an observer in the ePDP, I've been following<br class="">
council list and I've been around long enough to be able to<br class="">
handle this, I think.<br class="">
<br class="">
Regards,<br class="">
<br class="">
<pre class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-signature">--
Tapani Tarvainen
On Jan 03 16:43, Stephanie Perrin (<a class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-txt-link-abbreviated" href="mailto:stephanie.perrin@MAIL.UTORONTO.CA" target="_blank" moz-do-not-send="true">stephanie.perrin@MAIL.UTORONTO.CA</a>) wrote:
</pre>
<blockquote type="cite" class=""><br class="">
First, may I take this opportunity to wish you all a very happy and successful New Year! I am looking forward to the great work we will be doing together in 2019.<br class="">
<br class="">
Readers of this list will be aware that the next ICANN public meeting is in Kobe in March
<a class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-txt-link-freetext" href="https://meetings.icann.org/en/kobe64" target="_blank" moz-do-not-send="true">
https://meetings.icann.org/en/kobe64</a>. One of our GNSO Council members, Martin Valent, is unable to attend the meeting because of other commitments and we need to replace him quickly, in order to make use of his travel funding allotment, which is allocated
by Council. This decision is done through the NCSG EC, and we need to make it very quickly. If you are interested in applying to replace Martin at the meeting, please do so in the next five (5) days, sending me and Maryam Bakoshi a brief statement of your
interest, your experience with the council, current working group membership etc. This is not for a novice, Council has a lot of important work on the agenda and if you have not been following the work of Council or the key working groups and policy development
processes at the moment, you will find it a struggle. For those not familiar with GNSO Council, it is pretty easy to get engaged...check out the website, follow the lists, attend the monthly Council calls as an observer, or listen to the recordings of any
of the working groups you are interested in. You will find the website (unlike many at ICANN) is actually well organized and helpful.
<a class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-txt-link-freetext" href="https://gnso.icann.org/en/group-activities/calendar" target="_blank" moz-do-not-send="true">
https://gnso.icann.org/en/group-activities/calendar</a><br class="">
<br class="">
<br class="">
Thanks for your interest! Deadline is Tuesday January 8, 12:00 UTC.<br class="">
<br class="">
<br class="">
Stephanie Perrin<br class="">
<br class="">
Chair, NCSG<br class="">
</blockquote>
</div>
</div>
_______________________________________________<br class="">
NCSG-EC mailing list<br class="">
<a href="mailto:NCSG-EC@lists.ncsg.is" target="_blank" class="" moz-do-not-send="true">NCSG-EC@lists.ncsg.is</a><br class="">
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-ec" rel="noreferrer" target="_blank" class="" moz-do-not-send="true">https://lists.ncsg.is/mailman/listinfo/ncsg-ec</a><br class="">
</blockquote>
</div>
_______________________________________________<br class="">
NCSG-EC mailing list<br class="">
<a href="mailto:NCSG-EC@lists.ncsg.is" target="_blank" class="" moz-do-not-send="true">NCSG-EC@lists.ncsg.is</a><br class="">
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-ec" target="_blank" class="" moz-do-not-send="true">https://lists.ncsg.is/mailman/listinfo/ncsg-ec</a><br class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
_______________________________________________<br class="">
NCSG-EC mailing list<br class="">
<a href="mailto:NCSG-EC@lists.ncsg.is" target="_blank" class="" moz-do-not-send="true">NCSG-EC@lists.ncsg.is</a><br class="">
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-ec" rel="noreferrer" target="_blank" class="" moz-do-not-send="true">https://lists.ncsg.is/mailman/listinfo/ncsg-ec</a><br class="">
</blockquote>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
NCSG-EC mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NCSG-EC@lists.ncsg.is">NCSG-EC@lists.ncsg.is</a>
<a class="moz-txt-link-freetext" href="https://lists.ncsg.is/mailman/listinfo/ncsg-ec">https://lists.ncsg.is/mailman/listinfo/ncsg-ec</a>
</pre>
</blockquote>
</body>
</html>