Protection of IGO and INGO Identifiers in All gTLDs
Implementation Project Status
Updated 1 June 2020
- Protection of Red Cross and Red Crescent Identifiers Policy published on 18 February 2020
- "Reserved Names" Policy published on 16 January 2018
- An Implementation Review Team (IRT) comprised of community members and led by GDD met regularly during the course of the implementation to discuss and agree on timelines and steps for implementation
Effective Dates:
- 12-months from the release of the Claims System Specification for INGOs
- 1 August 2020: Protection of Certain Red Cross and Red Crescent Identifiers
- 1 August 2018: "Reserved Names"
Timeframe
- Announcement of Implementation ("Red Cross/Red Crescent"): February 2020
- Public Comment ("Red Cross/Red Crescent"): October 2019
- Announcement of Implementation ("Reserved Names"): January 2018
- Public Comment: July 2017
- Board Approval: April 2014
Summary
Issues emerged during the development of the New gTLD Program regarding whether certain international (non-) governmental organizations (IGOs/INGOs) such as the Red Cross/Red Crescent Movement (RCRC) and International Olympic Committee (IOC) should receive special protection for their names in top- and second-level domains in new gTLDs. To explore the issue in detail, the ICANN Board requested policy advice from the GNSO Council and Governmental Advisory Committee (GAC) on whether special protections should be afforded to the RCRC, IOC and/or IGOs in general.
In October 2012, the GNSO formally initiated a Policy Development Process (PDP) to make recommendations on these issues. The Board adopted the recommendations of the PDP Working Group’s Final Report on 30 April 2014. Their Resolution included a request for additional time to consider Governmental Advisory Committee (GAC) advice on IGO/INGO issues.
The PDP WG was reconvened to produce an additional recommendation regarding Red Cross/Red Crescent Identifiers Protections. The ICANN Board approved these recommendations for implementation on 27 January 2019. This implementation work has been added to the work scope.