<div dir="ltr">Really its up to the GSE. I suggest that the RALO's make a list of CROP trips and compare it to the regional GSE. You don't want to second guess what is a legitimate trip for approval. <br>G<br><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Glenn McKnight</div><div dir="ltr">NARALO Secretariat<br><a href="mailto:mcknight.glenn@gmail.com" target="_blank">mcknight.glenn@gmail.com</a></div><div dir="ltr"><a href="http://toronto.ieee.ca/" target="_blank">http://toronto.ieee.ca/</a></div><div dir="ltr">IEEE Toronto SIGHT Chair </div><div dir="ltr"><a href="mailto:glenn.mcknight@ieee.org" target="_blank">glenn.mcknight@ieee.org</a><br>skype gmcknight<br>twitter gmcknight</div><div>289-830 6259<br>.</div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Jul 25, 2018 at 9:19 AM Judith Hellerstein <<a href="mailto:judith@jhellerstein.com">judith@jhellerstein.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Vanda <br>
Yes you could use it for LACNIC or for any other program that is in LACRALO’s outreach plan and approved by your GSE. I would also say that the GSE may also approve IGF especially if the panel is icann related. <br>
<br>
Judith <br>
<br>
Sent from my iPhone<br>
<a href="mailto:Judith@jhellerstein.com" target="_blank">Judith@jhellerstein.com</a><br>
Skype ID:Judithhellerstein <br>
<br>
> On Jul 24, 2018, at 12:28 PM, Vanda Scartezini <<a href="mailto:vanda@etges.com.br" target="_blank">vanda@etges.com.br</a>> wrote:<br>
> <br>
> <br>
> So, since we will not have an ICANN direct meeting in our region nezt fiscal year, shall we use it for a LACNIC, for instance, that is part of ICANN relevante stakeholder community? <br>
> <br>
> Vanda Scartezini<br>
> Polo Consultores Associados<br>
> Av. Paulista 1159, cj 1004<br>
> 01311-200- Sao Paulo, SP, Brazil<br>
> Land Line: +55 11 3266.6253<br>
> Mobile: + 55 11 98181.1464 <br>
> Sorry for any typos. <br>
> <br>
> <br>
> <br>
> <br>
> <br>
> On 7/20/18, 18:56, "Alac-sc-outreach on behalf of Dev Anand Teelucksingh" <<a href="mailto:alac-sc-outreach-bounces@atlarge-lists.icann.org" target="_blank">alac-sc-outreach-bounces@atlarge-lists.icann.org</a> on behalf of <a href="mailto:devtee@gmail.com" target="_blank">devtee@gmail.com</a>> wrote:<br>
> <br>
> On Fri, Jul 20, 2018 at 2:37 PM Judith Hellerstein<br>
> <<a href="mailto:judith@jhellerstein.com" target="_blank">judith@jhellerstein.com</a>> wrote:<br>
>> I understand this a bit differently based on the discussions that we had with Benedetta and Mary at ICANN Panama. Benedetta was clear that if there is no ICANN meeting or an ICANN sponsored meeting we can choose #C and use the trips or anything > that is in our outreach plan and also in the GSE plan for our region or that is signed of from the GSE. If you see on the guidelines it is an "OR" not an "and"<br>
>> <br>
>> Each RALO is allocated up to three (3) individual regional trips, to be utilized for the following events occurring in that respective RALO’s region in a financial year (FY), and in accordance with the goals, strategies, and expected activities and outcomes detailed in each RALO’s Outreach Strategic Plan:<br>
>> (a) an ICANN Public Meeting; or<br>
>> (b) an official meeting organized by the ICANN Organization (e.g. the GDD Summit); or<br>
>> (c) if there is no Public Meeting or official ICANN meeting occurring in that RALO’s region in that FY, a meeting in that region that is assessed by the relevant regional Global Stakeholder Engagement (GSE) regional vice-president as being: (i) directly and demonstrably related to ongoing ICANN policy, advisory or technical activities (e.g. a Regional Internet Registry meeting), and (ii) consistent with the ICANN Organization’s outreach plan for that region.<br>
>> It is clear that we do not have to use a trip for A or B as there is C. Benedetta said they put in C because of our questions. I think that Benedetta did not clear up the item in the wiki since item C Is what she was telling us at the meeting and is what is listed on the chart.<br>
>> <br>
>> Judith<br>
> <br>
> Sorry Judith, but I don't think that is correct. If you read further,<br>
> there is a paragraph that reads "Where a RALO has used at least one<br>
> (1) trip to an ICANN Public Meeting or official ICANN-organized<br>
> meeting occurring in its region, it may use its remaining<br>
> allocation(s) for a meeting occurring in its region that is assessed<br>
> by the relevant regional Global Stakeholder Engagement (GSE) regional<br>
> vice-president as being directly and demonstrably related to ongoing<br>
> ICANN policy, advisory or technical activities (e.g. a Regional<br>
> Internet Registry meeting)."<br>
> <br>
> So all RALOs must use at least one regional trip to either an ICANN<br>
> F2F ICANN meeting OR a ICANN organised meeting. EURALO, APRALO and<br>
> AFRALO have the benefit of having ICANN F2F meetings in FY19 to choose<br>
> for that trip, but all RALOs have to pick at least one ICANN organised<br>
> meeting in the region and then be able to pick a "meeting occurring in<br>
> its region that is assessed by the relevant regional Global<br>
> Stakeholder Engagement (GSE) regional vice-president as being directly<br>
> and demonstrably related to ongoing ICANN policy, advisory or<br>
> technical activities (e.g. a Regional Internet Registry meeting)".<br>
> <br>
> <br>
> Only if there are no ICANN organised events or public meetings in the<br>
> region, is (c) applied which essentially says.a RALO can use its 3<br>
> proposals for meetings "occurring in its region that is assessed by<br>
> the relevant regional Global Stakeholder Engagement (GSE) regional<br>
> vice-president as being directly and demonstrably related to ongoing<br>
> ICANN policy, advisory or technical activities (e.g. a Regional<br>
> Internet Registry meeting) ".<br>
> <br>
> Dev Anand<br>
> _______________________________________________<br>
> Alac-sc-outreach mailing list<br>
> <a href="mailto:Alac-sc-outreach@atlarge-lists.icann.org" target="_blank">Alac-sc-outreach@atlarge-lists.icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/alac-sc-outreach" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/alac-sc-outreach</a><br>
> <br>
> <br>
> _______________________________________________<br>
> Alac-sc-outreach mailing list<br>
> <a href="mailto:Alac-sc-outreach@atlarge-lists.icann.org" target="_blank">Alac-sc-outreach@atlarge-lists.icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/alac-sc-outreach" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/alac-sc-outreach</a><br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> Alac-sc-outreach mailing list<br>
> <a href="mailto:Alac-sc-outreach@atlarge-lists.icann.org" target="_blank">Alac-sc-outreach@atlarge-lists.icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/alac-sc-outreach" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/alac-sc-outreach</a><br>
<br>
_______________________________________________<br>
Alac-sc-outreach mailing list<br>
<a href="mailto:Alac-sc-outreach@atlarge-lists.icann.org" target="_blank">Alac-sc-outreach@atlarge-lists.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/alac-sc-outreach" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/alac-sc-outreach</a><br>
</blockquote></div>