Changes

The UDRP has remained unchanged since its adoption. The policy has been largely successful. In 2010, ICANN received reports of community concerns about variations in process between different dispute resolution services, and the risk of "forum shopping" to achieve favorable results.<ref name="providers" /> After a review of those concerns and all of its service providers, ICANN issued a memo regarding the uniformity of application of the UDRP rules in 2013.<ref name="udrpstatus">[https://www.icann.org/en/help/dndr/udrp/providers/uniformity-process-19jul13-en.pdf UDRP Providers and Uniformity of Process - Status Report], July 2013 (PDF)</ref> Although they noted that each provider can set its own procedural rules, ICANN found no indication that service providers were varying in their application of the UDRP rules.<ref name="udrpstatus" /> They noted further that variation in processes (as well as localized language understanding) provided diversity of choice for claimants, and that the "forum shopping" claims did not have support within the actual results under the UDRP rules.<ref name="udrpstatus" />

The UDRP has remained unchanged since its adoption. The policy has been largely successful. In 2010, ICANN received reports of community concerns about variations in process between different dispute resolution services, and the risk of "forum shopping" to achieve favorable results.<ref name="providers" /> After a review of those concerns and all of its service providers, ICANN issued a memo regarding the uniformity of application of the UDRP rules in 2013.<ref name="udrpstatus">[https://www.icann.org/en/help/dndr/udrp/providers/uniformity-process-19jul13-en.pdf UDRP Providers and Uniformity of Process - Status Report], July 2013 (PDF)</ref> Although they noted that each provider can set its own procedural rules, ICANN found no indication that service providers were varying in their application of the UDRP rules.<ref name="udrpstatus" /> They noted further that variation in processes (as well as localized language understanding) provided diversity of choice for claimants, and that the "forum shopping" claims did not have support within the actual results under the UDRP rules.<ref name="udrpstatus" />

===[[New gTLD Program]] Mechanisms: 2012===

===[[New gTLD Program]] Mechanisms: 2009-2014===

As part of the New gTLD Program, ICANN introduced a variety of rights protection mechanisms to address specific concerns of rights holders and advisory committees, as well as to comply with international law and treaties.

As part of the New gTLD Program, ICANN introduced a variety of rights protection mechanisms to address specific concerns of rights holders and advisory committees, as well as to comply with international law and treaties. Work on intellectual property issues began in 2009, when ICANN assembled a

====International Nongovernmental Organizations (INGO) Claims Notification====

====International Nongovernmental Organizations (INGO) Claims Notification====

In addition, the names and acronyms of many international nongovernmental organizations were subject to a claims notification process across all new gTLDs.<ref name="ingo" /> Attempts to register a domain that matched a label on the INGO identifier list<ref>For a downloadable XML list of INGO identifiers, see [https://www.icann.org/resources/pages/ingo-identifier-list-2018-01-16-en ICANN's INGO Identifier List]</ref> were met with a notice that the registrant may or may not have rights to register the name. Such an attempt also triggered a notification to the INGO in question. The Claims Notification process was designed to assist INGOs in protecting their rights during an initial launch period for registration within a new gTLD. The idea was for registries to conform to a specific "Claim System Specification."<ref name="ingo" /> However, as of March 2021, no Claims System Specification is listed as having been adopted.<ref>[https://www.icann.org/resources/pages/ingo-claims-system-specification-2018-01-16-en ICANN.org - INGO Claims System Specification]</ref>

In addition, the names and acronyms of many international nongovernmental organizations were subject to a claims notification process across all new gTLDs.<ref name="ingo" /> Attempts to register a domain that matched a label on the INGO identifier list<ref>For a downloadable XML list of INGO identifiers, see [https://www.icann.org/resources/pages/ingo-identifier-list-2018-01-16-en ICANN's INGO Identifier List]</ref> were met with a notice that the registrant may or may not have rights to register the name. Such an attempt also triggered a notification to the INGO in question. The Claims Notification process was designed to assist INGOs in protecting their rights during an initial launch period for registration within a new gTLD. The idea was for registries to conform to a specific "Claim System Specification."<ref name="ingo" /> However, as of March 2021, no Claims System Specification is listed as having been adopted.<ref>[https://www.icann.org/resources/pages/ingo-claims-system-specification-2018-01-16-en ICANN.org - INGO Claims System Specification]</ref>

==GNSO Review of Rights Protection Mechanisms==

==GNSO Review of Rights Protection Mechanisms==