Page History
https://www.icann.org/news/announcement-2019-05-20-en
Los Angeles – 20 May 2019 – The Internet Corporation for Assigned Names and Numbers (ICANN) is seeking volunteers to participate in an
The following message went out for the call for IRT in February 2019 to supplement the existing IRT for the Red Cross Names update effort.
Call for Volunteers: IGO and INGO Identifiers Protection Policy Implementation
On 27 January 2019, the Boardadopted policy recommendations on Protections for Certain Red Cross and Red Crescent Names in All Generic Top-Level Domains and directed their implementation. This new consensus policy will supplement the previously-adopted Protection of IGO and INGO Identifiers in All gTLDs Policy by which the specific terms Red Cross, Red Crescent, Red Lion & Sun and Red Crystal were withheld from registration. The Implementation Review Team (IRT) supporting to assist in the implementation of the Protection of IGO and INGO Identifiers in All gTLDs Policy will add these new recommendations to its scope.
The key responsibilities of the IRT are as follows:
Expedited Policy Development Process (EPDP) Team's Phase 1 policy recommendations.
The IRT will:
Work with ICANN org to ensure that the implementation fulfills the original intentions of the approved policy recommendations
- Review the proposed implementation plan as drafted by ICANN org for consistency with the recommendations as approved by the Board
- from the EPDP Team.
- Assist in case of questions or need for clarification related to the adopted recommendations
- where questions or clarifications from ICANN org are needed.
- Advise on technical and operational details related to the implementation of recommendations by contracted parties
- the EPDP recommendations.
For this IRT, volunteers involved in the Red Cross organization, members from the Reconvened Working Group, and Registry professionals capable of implementing the reservation of labels (that will range in the thousands) in the domain registration process are particularly sought. Familiarity with the policy recommendations as well as the deliberations that informed those recommendations is a minimum requirement for IRT members. 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 2021. 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 of these recommendations is estimated to take approximately one year. The IRT is anticipated to meet monthly starting in late March 2019 for one hour. These meeting will be held remotely but there may be opportunities to meet in person during ICANN meetings. Between the meetings, the IRT will be working work using collaborative tools. The expected time commitment for supporting the implementation is about one to two approximately three hours per week.
How to apply
To participate, please send an email todennis andrea.chang@icannglandon@icann.org before Monday, 18 March 2019, 11:59 UTC.Please seeIGO and INGO Policy IRT wiki page for the list of current IRT members.
Background
In November 2012, the GNSO Council launched the PDP on the Protection of IGO-INGO Identifiers in All gTLDs. The aim was to consider what the appropriate form and scope of protection for IGO and INGO identifiers would be at both the top level and second level of the Domain Name System (DNS), for the Red Cross, the International Olympic Committee (IOC), and other IGOs and INGOs. All these organizations perform important public interest or humanitarian work. Cybersquatting and related abuse of domain names identical or confusingly similar to their names and acronyms could significantly impact their missions and resources.
In April 2014, the Board adopted part of the PDP outcomes, which included consensus recommendations that a limited list of Red Cross, IOC, IGO, and INGO identifiers be reserved. For the Red Cross, these are “Red Cross,” “Red Crescent,” “Red Crystal,” and “Red Lion and Sun” at the top level and second level. For IGOs, only their full organizational names are reserved at the second level.
The appropriate protections for many of the other identifiers associated with the Red Cross and IGOs – i.e., Red Cross National Society names, the names and acronyms of the International Red Cross Movement, and IGO acronyms – had not been finalized.
The Board facilitated a set of dialogues with the GAC and the GNSO to reconcile the inconsistencies between GAC advice and the GNSO PDP recommendations for the Red Cross names while the discussion continues over the acronyms.
In May 2017, the GNSO Council initiated the policy amendment process only for specific names associated with the Red Cross names and reconvened the PDP WG.
The recommendations that emerged from the Reconvened PDP WG are as follows:
a finite list of the full names of the 191 Red Cross National Societies, the International Committee of the Red Cross (ICRC) and the International Federation of Red Cross and Red Crescent Societies (IFRC) to be placed into Specification 5 of the Base gTLD Registry Agreement [for reservation.]
an exception procedure is to be put in place for cases where the relevant RCRC Organization wishes to apply for its protected string(s) at the second level.
future error corrections, additions to and deletions [for the list] of reserved names [shall be done] in accordance with the criteria listed in Recommendations #4-6 below.
changes to the finite list [to be done] in accordance with the variant criteria as defined by this WG.
any and all future changes to the finite list be made only upon notification to ICANN Organization and the confirmation, by designated representatives of the International Red Cross and Red Crescent Movement (Movement), to the effect that: (a) the proposed changes have been communicated to the GAC as well as the GNSO Council; (b) any new National Societies’ names to be added to the list have been recognized in accordance with all the applicable rules and procedures of the Movement; and (c) any proposed deletions from the list would be based on the cessation of operations of that National Society or its removal from the Movement in accordance with all applicable rules and procedures of the Red Cross Movement.
...
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.
