Skip to main content

Call for Volunteers: Implementation Review Team for Registration Data Policy Implementation

Los Angeles – 20 May 2019 – The Internet Corporation for Assigned Names and Numbers (ICANN) is seeking volunteers to participate in an Implementation Review Team (IRT) to assist in the implementation of the Expedited Policy Development Process (EPDP) Team's Phase 1 policy recommendations.

The IRT will:

  • Review the proposed implementation plan as drafted by ICANN org for consistency with the recommendations from the EPDP Team.
  • Assist where questions or clarifications from ICANN org are needed.
  • Advise on technical and operational details related to the implementation of the EPDP recommendations.

For this IRT, ICANN org is seeking volunteers, including current or former EPDP Team members that participated in the Team's Phase 1 work, who possess a deep understanding of the EPDP Team's policy recommendations and accompanying rationale. In addition, registry and registrar representatives responsible for implementing the policy requirements in relevant domain registration processes are encouraged to participate. All volunteers responding to this call are expected to understand the role and remit of the IRT for the implementation project.

The Generic Names Supporting Organization (GNSO) Council approved an EPDP Team recommendation to informally convene the IRT and allow for the necessary planning to take place before the ICANN Board considered the EPDP Team's Final Report. This pre-IRT was assembled in April 2019 and has assisted with the implementation of the Interim Registration Data Policy. All members of the pre-IRT will transition to the IRT. Additional members are invited to join the IRT going forward. For more details on the EPDP Recommendations and timeline, please go here: (See EPDP Team Recommendation 28.)

The work of the IRT is estimated to last until early 2020. The group is expected to meet via teleconference every two weeks starting in May 2019 for one hour each, with scheduling to be adjusted by the group as needed. Between the meetings, the IRT will work using collaborative tools. The expected time commitment for supporting the implementation is approximately three hours per week.

How to apply

To participate, please send an email to gnso-secs@icann.org.

Background

On 17 May 2018, the ICANN Board of Directors (ICANN Board) adopted the Temporary Specification for generic top-level domain (gTLD) Registration Data (Temporary Specification) pursuant to the procedures for the establishment of temporary policies in ICANN's agreements with registry operators and registrars. The Temporary Specification provides modifications to existing requirements in the Registrar Accreditation and Registry Agreements in order to comply with the European Union's General Data Protection Regulation (GDPR). Following the adoption of a temporary specification, the procedure for Temporary Policies as outlined in the Registrar Accreditation and Registry Agreements provides the Board "shall immediately implement the Consensus Policy development process set forth in ICANN's Bylaws." Additionally, the procedure provides this Consensus Policy development process on the Temporary Specification must be carried out within a one-year period as the Temporary Specification can only remain in force for up to one year; from the effective date of 25 May 2018, i.e., the Temporary Specification will expire on 20 May 2019.

On 19 July 2018, the GNSO Council initiated an EPDP and chartered the EPDP on the Temporary Specification for gTLD Registration Data Team. Unlike other GNSO Policy Development Process (PDP) efforts, which are open for anyone to join, the GNSO Council chose to limit the membership composition of this EPDP, primarily in recognition of the need to complete the work in a relatively short timeframe and to resource the effort responsibly. GNSO Stakeholder Groups, the Governmental Advisory Committee (GAC), the Country Code Names Supporting Organization (ccNSO), the At-Large Advisory Committee (ALAC), the Root Server System Advisory Committee (RSSAC), and the Security and Stability Advisory Committee (SSAC) were each invited to appoint a set number of members and alternates, as outlined in the charter. In addition, the ICANN Board and ICANN org were invited to assign a limited number of liaisons to this effort. A call for volunteers to the aforementioned groups was issued in July 2018 and the EPDP Team held its first meeting on 1 August 2018.

On 4 March 2019, the GNSO Council adopted the EPDP Team's Phase 1 Final Report and submitted it to the Board for their consideration. The Board has conducted a Public Comment and passed a resolution on 15 May 2019 to authorize the implementation of the recommendations.

About ICANN

ICANN's mission is to help ensure a stable, secure, and unified global Internet. To reach another person on the Internet, you need to type an address – a name or a number – into your computer or other device. That address must be unique so computers know where to find each other. ICANN helps coordinate and support these unique identifiers across the world. ICANN was formed in 1998 as a not-for-profit public-benefit corporation with a community of participants from all over the world.


More Announcements
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."