Versions Compared

Version Old Version 3 New Version Current
Changes made by

Maryam Bakoshi

Aleksey Khapchenko

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Fix links.


You must read the CROP Procedures and Guidelines before applying

...

Info

FY21 Submission Deadline - Tuesday, 19 May 2020


Info


CROP TRIP Proposal Submission Deadline for ICANN Meetings in FY21

ICANN69 Hamburg - Friday, 28 August 2020

ICANN70 Cancún - Friday, 29 January 2021

ICANN71 The Hague - Friday, 25 April 2021

...

REMINDERS

  • CROP will continue to determine whether a specific country is within an applicable geographical region according to the list of countries and geographic regions currently used by the ICANN org Global Stakeholder Engagement (GSE) team. Click here to see the full GSE list of countries and regions. 
  • Any one of the three allocated trips for FY21 must be to either an ICANN Public Meeting or an ICANN-organized event in the applicable region. 
  • While event registration fees will not generally be supported, a limited exception has been created that requires approval from the CROP administrator in consultation with the relevant regional GSE vice president.
  • Trip proposals are due to the CROP administrator seven weeks before the start date of the proposed trip. Concurrence from the relevant regional GSE vice president is due at least six weeks before the start date of the proposed trip.

...

  1. Each RALO and eligible GNSO Constituency is allocated up to three (3) individual regional trips, to be utilized within a financial year (FY), and in accordance with the goals, strategies, and expected activities and outcomes detailed in each RALO’s and Constituency’s Outreach Strategic Plan.  
  2. The three allocated trips must be within the applicable geographical region for each RALO and eligible Constituency (as determined by the GSE list of countries and regions); and must be applied in the following manner:
    1. If, during the current FY, there is an ICANN Public Meeting or an ICANN-organized event occuring in the relevant region, at least one trip must be allocated either to that ICANN Public Meeting or ICANN-organized event.
    2. The remaining trip allocations must be used for events in the relevant region that are:
      1. Directly and demonstrably related to ongoing ICANN policy, technical, or advisory work, such as a Regional Internet Registry meeting
      2. Consistent with the ICANN org strategic plan for that region as directly assessed by the relevant regional GSE vice president
  3. For clarity, if there is no ICANN Public Meeting or ICANN-organized event taking place in the relevant region during the current fiscal year, all three trip allocations may be used in accordance with the criteria outlined in 2.b.

...