ICANN: Initial Report Inter-Registrar Transfer Policy (IRTP) Part D PDP

ICANN logoPurpose (Brief): This Public Forum invites comments on the Initial Report [PDF, 936 KB] of the IRTP Part D PDP. The Report provides 12 preliminary recommendations to the six questions that this PDP Working Group (WG) was charted with. Please note that the WG is seeking public comment especially on Charter questions B and C to help inform its final recommendation.
Current Status: The WG has completed and published its Initial Report. The Working Group will present the report, its preliminary recommendations, and all remaining open issues during the ICANN Meeting in Singapore at a Public Workshop. Public comment is especially sought on the recommendations for Charter questions B and C since the WG has decided to concretize its recommendation on some of the issues raised in these questions only once they have received and reviewed all public comments. In addition, the WG will refine the Initial Report’s Annex C, containing a list of use cases, in time for the publication of its Final Report.
Next Steps: Following the review of the Community discussion during the ICANN Meeting in Singapore and all public comments and replies received during the comment and reply periods, the WG will finalize its recommendations and publish its Final Report.
Detailed Information
Section I: Description, Explanation, and Purpose:

In addition to background information, an overview of the WG‘s deliberations and community input received to date, the Initial Report [LINK] contains the following preliminary recommendations:

Proposed Recommendation to Charter Question A

Recommendation #1: The WG recommends that reporting requirements be incorporated into the TDRP policy. Outcomes of all rulings by Dispute Resolution Providers1 should be published on Providers’ website, except in exceptional cases. The Group recommends publishing reports that follow the example of the Asian Domain Name Dispute Resolution Centre (ADNDRC).2 These reports should include at a minimum: a) Information about parties involved in the dispute; b) The full decision of the case; c) The date of the implementation of the decision

Recommendation #2: The WG recommends that the TDRP be amended to include language along the lines of this revised version of the UDRP: ‘The relevant Dispute Resolution Provider shall report any decision made with respect to a transfer dispute initiated under the TDRP. All decisions under this Policy will be published in full over the Internet, except when a Dispute Resolution Panel determines, in an exceptional case, to redact portions of its decision. In any event, the portion of any decision determining a complaint to have been brought in bad faith shall be published.’

Proposed Recommendation to Charter Question B

Recommendation #3: The WG recommends that the TDRP be amended as follows: “Transfers from a Gaining Registrar to a third registrar, and all other subsequent transfers, are null and void if the Gaining Registrar acquired sponsorship from the Registrar of Record through an invalid transfer,** as determined through the dispute resolution process set forth in the Transfer Dispute Resolution Policy.”*

Recommendation #4: The WG recommends that a domain name be returned to the original Registrar of Record if it is found through a TDRP procedure that a non-IRTP compliant domain name transfer has occurred. The TDRP as well as guidelines to registrars, registries and third party dispute providers should be modified accordingly.

Recommendation #5: The WG recommends that the statute of limitation to launch a TDRP be extended from current 6 months to 12 months from the initial transfer. This is to provide registrants the opportunity to become aware of fraudulent transfers when they would no longer receive their registrar’s annual WDRP notification.

Recommendation #6: The WG recommends that if a request for enforcement is initiated under the TDRP the relevant domain should be ‘locked’ against further transfers. The TDRP as well as guidelines to registrars, registries and third party dispute providers should be modified accordingly.

*NB: The Working Group would like to encourage Public Comment on the question of whether costs would need to be refunded to registrars in case of negating/reversing transfers under a multiple-hop scenario.

** NB: The Working Group would like to encourage Public Comment on whether in this context there is a need to clearly define ‘invalid transfer’; and if so, how.

Proposed Recommendation to Charter Question C

The WG does not recommend that dispute options for registrants be developed and implemented as part of the current TDRP.

Recommendation #7: The WG recommends that the GNSO ensure that IRTP-C inter-registrant transfer recommendations are implemented and include appropriate dispute-resolution mechanisms. The IRTP-C and IRTP-D Implementation Review Teams should determine whether the inter-registrant transfer use cases documented in Appendix [?] have been addressed. If there are use cases that have not been addressed by the implementation of IRTP-C-2, the Implementation Review Teams are charged with formulating a request for an Issue Report to review the remaining use cases and consider whether any additional dispute resolution mechanisms (or changes to the TDRP) should be developed. That request should then be forwarded to the GNSO Council for consideration.

Recommendation #8: The WG recommends that the TDRP be modified to eliminate the First Level (Registry) layer of the TDRP.***  

Observation: The WG observes that the information on the ICANN website describing registrant options with regard to inter-registrar and inter-registrant transfers is not as clearly formulated and prominently displayed as it should be. The recommendations for Charter question D below address this issue in detail.

***NB: The Working Group would like to encourage Public Comment on the issue of whether to remove the registry layer from the TDRP.

Proposed Recommendation to Charter Question D

Recommendation #9: The WG recommends that ICANN create and maintains a one-stop website containing all relevant information concerning disputed transfers and potential remedies to registrants. This should include: a) Improvements to the ICANN website regarding the display of information on the Inter Registrar Transfer Policy and the Transfer Dispute Resolution Policy is regularly updated; b) Links to the relevant information for registrants on the ICANN website being clearly worded and prominently displayed on the ICANN home page. This will contribute to improving visibility and content of the ICANN website that is devoted to offering guidance to registrants with transfer issues; c) ICANN Compliance clearly indicates on its FAQ/help section under which circumstances it can assist registrants with transfer disputes. This should include situations when registrants can ask ICANN Compliance to insist on registrars taking action on behalf of said registrant; d) Improvements in terms of accessibility and user-friendliness should be devoted especially to these pages:




Links to these registrant help-website should also be prominently displayed on internic.net and iana.org in order to assure further that registrants have easy access to information

Recommendation #10: The WG recommends that, as best practice, ICANN accredited Registrars prominently display a link on their website to this ICANN registrant help site. Registrars may chose to add this link to those sections of their website that already contains Registrant-relevant information such as the Registrant Rights and Responsibilities, the WHOIS information and/or other relevant ICANN-required links as noted under 3.16 of the 2013 RAA.

Proposed Recommendation to Charter Question E

Recommendation #11: The WG recommends that no additional penalty provisions be added to the existing policy. The WG concludes that the penalty structures introduced in the 2009 RAA and the 2013 RA are sufficiently nuanced to deal with IRTP violations.

Recommendation #12: The WG recommends that, as a matter of principle, GNSO Consensus Policy should avoid policy-specific sanctions. Rather, it is desirable that the overarching RAA and RA penalty structures be drafted in a way that assures uniformity and consistency of policy violation penalties .

Proposed Recommendation to Charter Question F

The WG does not recommend the elimination of FOAs.

1 The Working Group recommends in Charter question C to remove the Registry as the first dispute resolution layer of the TDRP. Therefore, despite wording of Charter question A, no reporting requirements for the Registries are included here.

2 See four ADNDRC Reports on TDRP decisions: http://www.adndrc.org/mten/TDRP_Decisions.php?st=6

Section II: Background:

The aim of the Inter-Registrar Transfer Policy (IRTP) is to provide a straightforward procedure for domain name holders to transfer their names from one ICANN-accredited registrar to another. The GNSO Council is reviewing and considering revisions to this policy through a series of Working Groups it has established to conduct these efforts. The IRTP Part D PDP Working Group has been tasked to consider the following six questions:

a) Whether reporting requirements for registries and dispute providers should be developed, in order to make precedent and trend information available to the community and allow reference to past cases in dispute submissions;

b) Whether additional provisions should be included in the TDRP (Transfer Dispute Resolution Policy) on how to handle disputes when multiple transfers have occurred;

c) Whether dispute options for registrants should be developed and implemented as part of the policy (registrants currently depend on registrars to initiate a dispute on their behalf);

d) Whether requirements or best practices should be put into place for registrars to make information on transfer dispute resolution options available to registrants;

Penalties for IRTP Violations
e) Whether existing penalties for policy violations are sufficient or if additional provisions/penalties for specific violations should be added into the policy;

Need for FOAs
f) Whether the universal adoption and implementation of EPP AuthInfo codes has eliminated the need of FOAs.

Section III: Document and Resource Links:


Section IV: Additional Information:

Comment / Reply Periods (*)

  • Comment Open Date: 3 March 2014
  • Comment Close Date: 3 April 2014 – 23:59 UTC
  • Reply Open Date: 4 April 2014
  • Reply Close Date: 25 April 2014 – 23:59 UTC

Important Information Links