[Alac-sc-outreach] FW: Urgent questions about CROP guidelines for FY19
Glenn McKnight
mcknight.glenn at gmail.com
Wed Jul 25 13:24:34 UTC 2018
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.
G
Glenn McKnight
NARALO Secretariat
mcknight.glenn at gmail.com
http://toronto.ieee.ca/
IEEE Toronto SIGHT Chair
glenn.mcknight at ieee.org
skype gmcknight
twitter gmcknight
289-830 6259
.
On Wed, Jul 25, 2018 at 9:19 AM Judith Hellerstein <judith at jhellerstein.com>
wrote:
> Hi Vanda
> 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.
>
> Judith
>
> Sent from my iPhone
> Judith at jhellerstein.com
> Skype ID:Judithhellerstein
>
> > On Jul 24, 2018, at 12:28 PM, Vanda Scartezini <vanda at etges.com.br>
> wrote:
> >
> >
> > 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?
> >
> > Vanda Scartezini
> > Polo Consultores Associados
> > Av. Paulista 1159, cj 1004
> > 01311-200- Sao Paulo, SP, Brazil
> > Land Line: +55 11 3266.6253
> > Mobile: + 55 11 98181.1464
> > Sorry for any typos.
> >
> >
> >
> >
> >
> > On 7/20/18, 18:56, "Alac-sc-outreach on behalf of Dev Anand
> Teelucksingh" <alac-sc-outreach-bounces at atlarge-lists.icann.org on behalf
> of devtee at gmail.com> wrote:
> >
> > On Fri, Jul 20, 2018 at 2:37 PM Judith Hellerstein
> > <judith at jhellerstein.com> wrote:
> >> 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"
> >>
> >> 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:
> >> (a) an ICANN Public Meeting; or
> >> (b) an official meeting organized by the ICANN Organization (e.g. the
> GDD Summit); or
> >> (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.
> >> 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.
> >>
> >> Judith
> >
> > Sorry Judith, but I don't think that is correct. If you read
> further,
> > there is a paragraph that reads "Where a RALO has used at least
> one
> > (1) trip to an ICANN Public Meeting or official ICANN-organized
> > meeting occurring in its region, it may use its remaining
> > allocation(s) for a meeting occurring in its region that is
> assessed
> > by the relevant regional Global Stakeholder Engagement (GSE)
> regional
> > vice-president as being directly and demonstrably related to
> ongoing
> > ICANN policy, advisory or technical activities (e.g. a Regional
> > Internet Registry meeting)."
> >
> > So all RALOs must use at least one regional trip to either an
> ICANN
> > F2F ICANN meeting OR a ICANN organised meeting. EURALO, APRALO and
> > AFRALO have the benefit of having ICANN F2F meetings in FY19 to
> choose
> > for that trip, but all RALOs have to pick at least one ICANN
> organised
> > meeting in the region and then be able to pick a "meeting
> occurring in
> > its region that is assessed by the relevant regional Global
> > Stakeholder Engagement (GSE) regional vice-president as being
> directly
> > and demonstrably related to ongoing ICANN policy, advisory or
> > technical activities (e.g. a Regional Internet Registry meeting)".
> >
> >
> > Only if there are no ICANN organised events or public meetings in
> the
> > region, is (c) applied which essentially says.a RALO can use its 3
> > proposals for meetings "occurring in its region that is assessed
> by
> > the relevant regional Global Stakeholder Engagement (GSE) regional
> > vice-president as being directly and demonstrably related to
> ongoing
> > ICANN policy, advisory or technical activities (e.g. a Regional
> > Internet Registry meeting) ".
> >
> > Dev Anand
> > _______________________________________________
> > Alac-sc-outreach mailing list
> > Alac-sc-outreach at atlarge-lists.icann.org
> > https://mm.icann.org/mailman/listinfo/alac-sc-outreach
> >
> >
> > _______________________________________________
> > Alac-sc-outreach mailing list
> > Alac-sc-outreach at atlarge-lists.icann.org
> > https://mm.icann.org/mailman/listinfo/alac-sc-outreach
> >
> >
> >
> > _______________________________________________
> > Alac-sc-outreach mailing list
> > Alac-sc-outreach at atlarge-lists.icann.org
> > https://mm.icann.org/mailman/listinfo/alac-sc-outreach
>
> _______________________________________________
> Alac-sc-outreach mailing list
> Alac-sc-outreach at atlarge-lists.icann.org
> https://mm.icann.org/mailman/listinfo/alac-sc-outreach
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/alac-sc-outreach/attachments/20180725/9e6460e7/attachment-0001.html>
More information about the Alac-sc-outreach
mailing list