Skip to main content

FY19 Community Regional Outreach Program (CROP) Ready for Use by Eligible ICANN Communities

The Global Stakeholder Engagement (GSE) and Policy teams are pleased to report that the Community Regional Outreach Program (CROP) FY19 is ready for the ICANN community to use as of 3 July 2018.

Following community consultations and Public Comments on the Draft FY19 Operating Plan and Budget, the ICANN Board allocated USD 50,000 for CROP in the final FY19 budget. To ensure that support for community outreach efforts remains within the appropriate budget framework while balancing the program goals, the ICANN organization was directed to review the existing CROP guidelines and develop improved, additional criteria for FY19. The ICANN org has also been tasked with assessing the CROP process at the end of FY19.

The final FY19 CROP guidelines are consistent with the other community travel and outreach programs that the ICANN org administers. Accordingly, the fundamental principle is that CROP funding is to be used for FY19 outreach efforts that are directly and demonstrably related to ongoing ICANN policy, technical, and advisory activities, in accordance with the new CROP guidelines and additional specific criteria.

The new CROP allocates up to three regional trips to each of the five Regional At-Large Organizations (RALOs) and each eligible constituency in the Generic Names Supporting Organization (GNSO) – Business Constituency (BC), Intellectual Property Constituency (IPC), Internet Service Providers and Connectivity Providers Constituency (ISPCP), Non-Commercial Users Constituency (NCUC), and Not-for-Profit Operational Concerns Constituency (NPOC). With a few specific exceptions as detailed in the new guidelines, these allocations are to be used mainly for outreach activities at ICANN Public Meetings in the relevant region or official regional meetings organized by the ICANN org.

As was previously the case, each eligible community group must have in place a relevant outreach strategic plan. Under the new CROP guidelines, the plan must address certain specific additional requirements. As before, trip requests need to be submitted at least six weeks prior to travel dates. In addition, the relevant regional GSE vice president must approve the request at least five working days before the six-week travel deadline.

We invite you to browse through the CROP FY19 space and the CROP Procedures and Guidelines page to familiarize yourself with the updated program. Please watch for the CROP team announcement on your community mailing lists. This announcement will give more details about how to coordinate with CROP team to begin using the program.

We are pleased to be able to continue to support the community's regional outreach activities for FY19. We look forward to your feedback at the end of this fiscal year so that we may continue to improve the program in line with the community's budgeting priorities in future years.

Comments

    Domain Name System
    Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."