Comment Close Date | Statement Name | Status | Assignee(s) and | Call for Comments | Call for Comments Close | Vote Announcement | Vote Open | Vote Reminder | Vote Close | Date of Submission | Staff Contact and Email | Statement Number |
---|---|---|---|---|---|---|---|---|---|---|---|---|
18.11.2012 | Expired Registration Recovery Policy | In Progress-ALAC voting | Alan Greenberg (NARALO) | 27.11.2012 | 30.11.2012 00:00 UTC | 30.11.2012 18:00 UTC | 30.11.2012 20:00 UTC | 05.12.2012 | 06.12.2012 | 07.12.2012 | Steve Gobin steve.gobin@icann.org | TBC |
* Status will be confined to the following terms: Drafting, Commenting, Voting, Adopted, Rejected, Suspended, No consensus, No statement, To Be Confirmed (TBC), Other
Comment/Reply Periods (*) | Important Information Links | |||
Comment Open: | 11 October 2012 | |||
Comment Close: | ||||
Close Time (UTC): | 23:59 | Public Comment Announcement | ||
Reply Open: | To Submit Your Comments (Forum) | |||
Reply Close: | View Comments Submitted | |||
Close Time (UTC): | 23:59 | Report of Public Comments | ||
Brief Overview | ||||
Originating Organization: | ICANN Registrar Relations Department | |||
Categories/Tags: | Top Level Domains, Policy Processes, Contracted Party Agreements | |||
Purpose (Brief): | ICANN is opening a Public Comment Period for the draft Expired Registration Recovery Policy. Members of the Internet Community are asked to provide feedback on the proposed document. The proposed Policy is based on recommendations from the Generic Names Supporting Organization Council related to Post-Expiration Domain Name Recovery ("PEDNR") | |||
Current Status: | The Generic Names Supporting Organization Council ("GNSO") initiated a Policy Development Process in May 2009, which resulted in the submission of several policy and process recommendations to theICANN Board of Directors, which the Board approved on 28 October 2011. ICANN staff developed this proposed, draft Policy in consultation with an Implementation Review Team convened by the GNSO. | |||
Next Steps: | ICANN will review the submitted comments and, where appropriate, incorporate suggested modifications into the Policy. Once finalized, the Policy will be implemented and made effective for allgTLD registrars and registries. | |||
Staff Contact: | Steve Gobin | Email: | steve.gobin@icann.org | |
Detailed Information | ||||
Section I: Description, Explanation, and Purpose | ||||
The Registrar Accreditation Agreement between the registrars and ICANN contains a number of provisions outlining the obligations of registrars to communicate the details of their deletion and auto-renewal policies to new registrants. However, because of diverse registrar business practices in the way registrations are handled after they expire, some registrants might not fully understand their available options for recovering domain names post-expiration. Many registrars currently offer post-expiration grace periods of varying lengths, during which registrants can renew expired names. Similarly, manygTLD registries and registrars offer registrants a redemption service, allowing registrants a certain amount of time to redeem names after they are deleted. The proposed Expired Registration Recovery Policy is intended to help align registrant expectations with registrar practices by establishing certain minimum communications requirements and making renewal and redemption of registrations uniformly available in prescribed circumstances. When the Policy is finalized, ICANN will create educational materials in consultation with interested stakeholders to help registrants properly manage their registrations. | ||||
Section II: Background | ||||
At the request of ICANN's At-Large Advisory Committee, on 5 December 2008, ICANN published an Issues Report [PDF, 422 KB] on the topic of Post-Expiration Domain Name Recovery. The Generic Names Supporting Organization Council ("GNSO") initiated a Policy Development Process in May 2009, which resulted in the submission of several policy and process recommendations to the ICANN Board of Directors. The ICANN Board approved the recommendations on 28 October 2011, directing staff to implement this policy. | ||||
Section III: Document and Resource Links | ||||
Draft Expired Registration Recovery Policy [PDF, 94 KB] | ||||
Section IV: Additional Information | ||||
None |
(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.
FINAL STATEMENT
The final Statement in PDF format is to be added here if the draft below is ratified.
DRAFT STATEMENT
As you know the Post Expiration Domain Name Recovery (PEDNR) PDP was approved by the Board last year and the resultant Policy (now called the Expired Registration Recovery Policy - ERRP) was posted for comment.
The PDP recommended that registrars who operate web site for registration must post their renewal fees and state what method they will use to contact registrants. The recommendation was silent regarding resellers because it was the belief that registrars, in honoring all of the terms of their contract, would require resellers to post this information as well.
Although it was not clear why at the time, ICANN staff working on the resultant changes to the RAA added very welcome wording explicitly requiring that registrars require resellers to post this information as well. The proposed policy can be found athttp://www.icann.org/en/resources/registrars/consensus-policies/errp/draft-policy-11oct12-en.pdf and the sections in question are paragraphs 4.1.2 and 4.2.3.
There were no negative comments about this in the public comments which were due to close on Nov. 11th. Staff extended the comment period for one more week, and had explicitly called attention to the changes on the Implementation Review Group mailing list and explicitly asking for comments to be posted on this.
Michele Neylon, the registrar who was on the Implementation Review Group submitted a statement to the ERRP Comment saying that the proposed language about resellers was debated at length by the PDP WG and the final decision was to not include such language in the recommendation. That is factually correct and indeed the report made reference to the fact that there was an explicit decision to not include it. His statement can be found at http://forum.icann.org/lists/draft-errp-policy/msg00001.html.
The ICANN Registrar Relations staff person who I had been working with was unavailable, so I asked compliance whether that was how they saw this as well. The reply was direct and clear that this was not how they interpreted the RAA terms and that the web posting provisions would not apply to resellers unless the explicit. The exchange is appending to this message.
I propose the following:
- Under my own name but as former Chair of the PEDNR WG and a member of the Implementation Review Team, I will post the statement from Compliance that without the explicit reseller language, that the new Policy will not benefit all Registrants, but only those who deal directly with Registrars, and based on my understanding, that was not the intent of the WG.
- ALAC should post a statement supporting the need to keep the explicit reseller language. This statement may need to be altered if registrars in the interim post a message agreeing to keep the language.