![]() |
Staff Report on Implementation Documents for the Uniform Dispute Resolution PolicyDate posted: September 29, 1999 |
![]()
At its meeting held in Santiago, Chile, on August 26, 1999, the ICANN Board of Directors, on the recommendation of the ICANN Domain Names Supporting Organization, adopted a uniform dispute resolution policy for all accredited registrars in the .com, .net, and .org top-level domains. (Board Resolution 99-81.) The Board directed the President, with the assistance of ICANN staff and counsel, to prepare implementation documents for approval by the Board after public notice and comment in time for the policy to be put in place within 45 days. (Board Resolution 99-82.)
Under the direction of ICANN’s President and Chief Executive Officer, ICANN staff and counsel have prepared two documents to implement the policy as adopted by the Board, which can be found at the following links: (1) a written statement of the policy for use by registrars and (2) procedural rules under which administrative proceedings would be conducted in cases involving abusive registrations. Until October 13, 1999, public comments are solicited on whether these documents faithfully implement the policy adopted on August 26. Comments should be sent to comment-udrp@icann.org.
How the Implementation Documents Were Drafted.
In its August 26 resolutions, the Board indicated that implementation documents for an interim voluntary policy prepared by a group of ICANN-accredited registrars and Network Solutions, Inc. and presented at the ICANN meeting in Santiago should be used as the starting point in drafting implementation documents for the Board-adopted policy. The Board also indicated that the President or his delegate should convene a small drafting group to advise staff and counsel as they prepared the implementation language. The Board suggested that the drafting group should consist of persons selected to express views and consider the interests of registrar, non-commercial, individual, intellectual property, and business interests. (Board Resolution 99-83, paragraphs 1 & 2.)
Earlier this month, a drafting group was formed including Kathryn A. Kleiman (of the Association for Computing Machinery's Internet Governance Committee, a member of the DNSO Non-Commercial Domain Name Holders' Constituency, and co-founder of the Domain Name Rights Coalition), Steven J. Metalitz (General Counsel of the International Intellectual Property Alliance, a member of the DNSO Trademark, Intellectual Property, Anti-counterfeiting Interests Constituency), Rita A. Rodin (of Skadden, Arps, Slate, Meagher & Flom, retained by America Online, a member of the DNSO Registrars Constituency), A. Michael Froomkin (of the University of Miami School of Law, a former member of the WIPO Panel of Experts), and J. Scott Evans (of the Adams Law Firm P.A., a member of the International Trademark Association's Internet Committee and chair of its DNS subcommittee). These individuals were selected because of their legal drafting abilities and because they collectively represent a diversity of viewpoints.
ICANN counsel prepared the implementation documents by starting with the policy statement (entitled "Model Domain Name Dispute Resolution Policy for Voluntary Adoption by Registrars") and rules of procedure (entitled "Model Rules for Uniform Domain Name Dispute Resolution Policy") prepared by the group of ICANN-accredited registrars and Network Solutions. In its August 26 resolutions, the ICANN Board pointed out several areas in which revisions should be made to these documents:
(Board Resolution 99.83, paragraphs 3-5.)
Throughout this process, the committee members provided valuable and insightful advice. It should be clearly understood, however, that the responsibility for selecting the language in the posted documents was that of ICANN staff and counsel, not the committee members. In some respects, the implementation language differs from that which individual committee members would have selected.
How the Board’s Policy Guidance Was Implemented.
As noted above, Board Resolution 99-83 listed various specific policy features that should be included in the implementation documents. To assist the public in commenting on whether the implementation documents presented here faithfully implement the Board’s resolutions, this section describes what measures were taken to implement these features.
2. Parity of Appeal. Paragraph 4 of Resolution 99-83 states the principle that "[t]here should be a general parity of appeal rights of complainants and domain name holders." Two aspects of non-parity were discussed by the drafting committee. First, it was noted that in some cases the domain-name holder would have no clear mechanism under the registrars’ documents for seeking judicial review of a decision of an administrative panel canceling or transferring the domain name. Second, it was noted that, under the policy statement prepared by the registrars, the domain-name holder had a unique advantage in that, even if an administrative panel decided that the domain name should be canceled or transferred, during court proceedings to review the decision it could obtain an automatic stay simply by presenting evidence that it had filed a complaint in any court against the complainant. As a practical matter, this could require complainants to litigate in courts with which they have no connection, while there is no similar requirement for domain-name holders.
With the assistance of the drafting committee, an integrated solution to these two aspects of non-parity was devised. First, in paragraph 3(b)(xiii) of the rules of procedure, the complainant is required to include in its complaint a statement submitting to jurisdiction for purposes of court review of administrative panel decisions in its favor. Correspondingly, paragraph 4(k) of the policy statement was revised to provide a staying effect only when the domain-name holder files suit in that jurisdiction.
Remaining Open Implementation Issues as to Which Comment Is Sought.
Comment is invited on a limited number of implementation issues left open in the draft documents:
![]()