<div dir="ltr">To be clear, Martin has been working on the RPM PDP, not the EPDP.<div><br></div><div>I see you commented on none of the other points I raised so maybe you could do that now?<br><br>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><br>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><br></div><div>-Raoul</div></div><br><div class="gmail_quote"><div dir="ltr">On Sun, 6 Jan 2019 at 00:48, Robin Gross via NCSG-EC <<a href="mailto:ncsg-ec@lists.ncsg.is">ncsg-ec@lists.ncsg.is</a>> wrote:<br></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;">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><br></div><div>Thanks,</div><div>Robin<br><div><br><div><blockquote type="cite"><div>On Jan 5, 2019, at 2:09 PM, Raoul Plommer via NCSG-EC <<a href="mailto:ncsg-ec@lists.ncsg.is" target="_blank">ncsg-ec@lists.ncsg.is</a>> wrote:</div><br class="gmail-m_3595950184674429608Apple-interchange-newline"><div><div dir="ltr">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><br>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><br>-Raoul</div><br><div class="gmail_quote"><div dir="ltr">On Sat, 5 Jan 2019 at 21:10, Stephanie Perrin via NCSG-EC <<a href="mailto:ncsg-ec@lists.ncsg.is" target="_blank">ncsg-ec@lists.ncsg.is</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><p><font size="+1"><font 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>
</font></font></p><p><font size="+1"><font face="Lucida Grande">Stephanie</font></font><br>
</p>
<div class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-email-headers-table" cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">Subject: </th>
<td>Re: Replacement for a council member in ICANN 64</td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">Date: </th>
<td>Sat, 5 Jan 2019 07:17:05 +0200</td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">From: </th>
<td>Tapani Tarvainen <a class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-txt-link-rfc2396E" href="mailto:ncsg@tapani.tarvainen.info" target="_blank">
<ncsg@tapani.tarvainen.info></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">To: </th>
<td>Stephanie Perrin <a class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-txt-link-rfc2396E" href="mailto:stephanie.perrin@MAIL.UTORONTO.CA" target="_blank">
<stephanie.perrin@MAIL.UTORONTO.CA></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap align="RIGHT">CC: </th>
<td>Maryam Bakoshi <a class="gmail-m_3595950184674429608gmail-m_-1745931914767642746moz-txt-link-rfc2396E" href="mailto:maryam.bakoshi@icann.org" target="_blank">
<maryam.bakoshi@icann.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
Hi Stephanie,<br>
<br>
Count me in. Even though I'm not currently in any working group<br>
apart from being an observer in the ePDP, I've been following<br>
council list and I've been around long enough to be able to<br>
handle this, I think.<br>
<br>
Regards,<br>
<br>
<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">stephanie.perrin@MAIL.UTORONTO.CA</a>) wrote:
</pre>
<blockquote type="cite"><br>
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>
<br>
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">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">
https://gnso.icann.org/en/group-activities/calendar</a><br>
<br>
<br>
Thanks for your interest! Deadline is Tuesday January 8, 12:00 UTC.<br>
<br>
<br>
Stephanie Perrin<br>
<br>
Chair, NCSG<br>
</blockquote>
</div>
</div>
_______________________________________________<br>
NCSG-EC mailing list<br>
<a href="mailto:NCSG-EC@lists.ncsg.is" target="_blank">NCSG-EC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-ec" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-ec</a><br>
</blockquote></div>
_______________________________________________<br>NCSG-EC mailing list<br><a href="mailto:NCSG-EC@lists.ncsg.is" target="_blank">NCSG-EC@lists.ncsg.is</a><br><a href="https://lists.ncsg.is/mailman/listinfo/ncsg-ec" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-ec</a><br></div></blockquote></div><br></div></div></div>_______________________________________________<br>
NCSG-EC mailing list<br>
<a href="mailto:NCSG-EC@lists.ncsg.is" target="_blank">NCSG-EC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-ec" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/listinfo/ncsg-ec</a><br>
</blockquote></div>