Trademark Post-Delegation Dispute Resolution Procedure: Difference between revisions
m JP moved page PDDRP to Trademark Post-Delegation Dispute Resolution Procedure |
m added Category:Rights Protection Mechanisms using HotCat |
||
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
'''Post-Delegation Dispute Resolution Procedure''' ('''PDDRP''') | The Trademark '''Post-Delegation Dispute Resolution Procedure''' ('''PDDRP''') is a [[Rights Protection Mechanisms|rights protection mechanism]] (RPM) designed to provide trademark holders (whether their marks are registered or not) to dispute the actions of a [[gTLD]] registry operator.<ref name="pddrp">[https://www.icann.org/resources/pages/pddrp-2014-01-09-en ICANN.org - PDDRP Resources]</ref> The mark holder can challenge the management of a gTLD, or a "bad faith" policy of registering second-level domains within a gTLD. PDDRP was recommended for use by various community participants, such as the World Intellectual Property Organization ([[WIPO]]) and Implementation Recommendation Team ([[IRT]]).<ref>[http://www.icann.org/en/topics/new-gtlds/draft-trademark-pddrp-04oct09-en.pdf ICANN Archive - Draft Trademark PDDRP], October 4, 2009 (PDF)</ref> Under the [[Registry Agreement]], a registry operator must participate in the procedure and is bound by decisions under the procedure. | ||
== | ==Background== | ||
The PDDRP was first proposed by the IRT in its report to ICANN.<ref name="irt">[https://www.icann.org/en/topics/new-gtlds/irt-final-report-trademark-protection-29may09-en.pdf IRT Report to ICANN], May 29, 2009 (PDF)</ref> The IRT called for some sort of "Post-Delegation Dispute Mechanism" (PDDM), and proposed a structure and process that is materially similar to the PDDRP.<ref name="irt" /> | |||
==Complaint Procedure & Standards== | |||
There are two available claims under the PDDRP: | |||
#Top-level: claimant must show abuse of a gTLD string that is "identical or confusingly similar" to the trademark in order to take commercial advantage of the mark, dilute the distinctiveness of the mark, damage the reputation of the mark holder, or create a likelihood of confusion.<ref name="proc">[https://newgtlds.icann.org/en/applicants/agb/pddrp-04jun12-en.pdf ICANN.org - PDDRP Procedure (PDF)]</ref> | |||
#Second level: claimant must show "a substantial pattern or practice of specific bad faith intent" to profit from "systematic registration of domain names within the gTLD that are identical or confusingly similar to the complainant’s mark," with the same consequences as claims at the top level: commercial advantage, dilution, damage to reputation, or consumer confusion.<ref name="proc" /> | |||
Both claims carry a heavy burden of proof for the claimant. The evidentiary standard for both claims is "clear and convincing," which is considered a more rigorous standard, though not as rigorous as standards in criminal cases (beyond a reasonable doubt).<ref name="proc" /><ref>[https://www.law.cornell.edu/wex/clear_and_convincing_evidence Definition of "clear and convincing,"] Cornell Legal Information Institute</ref> At the second level, the procedure document takes pains to exonerate the registry operator of the actions of unaffiliated registrants: | |||
<blockquote>In other words, it is not sufficient to show that the registry operator is on notice of possible trademark infringement through registrations in the gTLD. The registry operator is not liable under the PDDRP solely because: (i) infringing names are in its registry; or (ii) the registry operator knows that infringing names are in its registry; or (iii) the registry operator did not monitor the registrations within its registry.<br />A registry operator is not liable under the PDDRP for any domain name registration that: (i) is registered by a person or entity that is unaffiliated with the registry operator; (ii) is registered without the direct or indirect encouragement, inducement, initiation or direction of any person or entity affiliated with the registry operator; and (iii) provides no direct or indirect benefit to the registry operator other than the typical registration fee (which may include other fees collected incidental to the registration process for value added services such enhanced registration security).<ref name="proc" /></blockquote> | |||
After receiving the initial complaint, the dispute resolution service provider reviews the complaint for completeness and compliance with the procedural rules. Then, the provider appoints a one-panelist "Threshold Review Panel" to review the validity of the claim.<ref name="proc" /> This process is somewhat comparable to a summary judgement proceeding<ref>[https://www.law.cornell.edu/wex/summary_judgment "Summary Judgement,"] Cornell Legal Information Institute</ref> in civil court: the complaint is evaluated for sufficiency of evidence, proof of harm, and other proofs of fact. However, it is initiated automatically rather than on motion from one of the parties. It can also create additional costs for the complainant. In WIPO's supplemental procedural rules, for example, the respondent has the option to submit a $500 filing fee, which requires complainant to match the fee. If the complaint does not pass threshold review, respondent's fee is refunded.<ref>[https://www.wipo.int/export/sites/www/amc/en/docs/supplrulestmpddrp.pdf WIPO - PDDRP Supplemental Rules (PDF)]</ref> | |||
==Adoption and Use== | |||
Perhaps because of the difficulty of proving a case, the PDDRP mechanism has not been utilized. ICANN has established agreements with three PDDRP service providers: [[WIPO]], the [[National Arbitration Forum]], and the Asian Domain Name Dispute Resolution Centre.<ref name="pddrp" /> None of these service providers have reported decisions of cases under the PDDRP. The Final Report of GNSO's Phase 1 Review of all Rights Protection Mechanisms notes that there has never been a complaint.<ref name="pdpreport">[https://gnso.icann.org/en/issues/council-recommendations-rpm-pdp-phase-1-report-10feb21-en.pdf RPM PDP Phase 1 Report], February 10, 2021 (PDF)</ref> The GNSO recommended that it be made more clear that proceedings could be initiated by a group of claimants against a specific registry operator.<ref name="pdpreport" /> The recommendation notes that this was always implied by the procedures, but that clarifying the right for a "class" of complainants to initiate a complaint provides clarity regarding the potential for a collective complaint against a registry operator.<ref name="pdpreport" /> | |||
==Criticsm== | |||
During preparation of the [[Applicant Guidebook]], [[RySG]] argued that the PDDRP was unnecessary, and redundant to existing processes. <ref>[http://www.gtldregistries.org/sites/gtldregistries.org/files/RySG.Comments.PDDRP_.112209.VoteAmendment.112609.doc gTLDRegistries.org - RySG Comments on Trademark PDDRP]</ref> | |||
== References == | == References == | ||
Line 26: | Line 23: | ||
{{reflist}} | {{reflist}} | ||
[[ | |||
[[Category:Rights Protection Mechanisms]] | |||
__NOTOC__ | __NOTOC__ |