Skip to main content

Welcome to the new ICANN.org! Learn more, and send us your feedback. Dismiss

New Measures Proposed to Enhance Post-Expiration and Renewal Related Policies and Practices | GNSO Post-Expiration Domain Name Recovery Working Group Presents Final Report

The GNSO Post-Expiration Domain Name Recovery (PEDNR) Working Group has submitted its Final Report [PDF, 998 KB] to the Generic Names Supporting Organization (GNSO) Council today, 14 June 2011. The PEDNR WG was tasked to address questions in relation to what extent registrants should be able to renew their domain names after they expire. Following review of the comments received on its proposed Final Report, the Working Group now presents its Final Report, which contains 18 recommendations including the following:

  • Provide a minimum of 8 days after expiration for renewal by registrant (Recommendation #2)
  • An expired website must explicitly say that registration has expired and instructions on how to recover the registration (Recommendation #3)
  • The registration agreement must include information on the fees charged for the post-expiration renewal of a domain name (Recommendation #5)
  • Clear indication of methods used to deliver pre- and post-expiration notifications must be provided (Recommendation #6)
  • At least two notices prior to expiration need to be sent at set times and one after expiration (Recommendation #7 & #8)
  • Notifications must not solely be done by methods which require explicit action by the Registrant (Recommendation #9)
  • All gTLDs and registrars must offer Redemption Grace Period (RGP), with the exception of sponsored gTLDs (Recommendation #13 & 14)
  • The transfer of a domain name during the RGP should not be allowed (Rec#15)
  • ICANN should develop educational materials on how to properly steward a domain name and prevent unintended loss (Recommendation #16)
  • Best practice recommendations: Post-expiration notifications should be sent to some other contact point than to the email address associated with the expired registration (Recommendation #10), provide notice of where notification emails will be sent from (Recommendation #11), encourage registrants to provide a secondary email point of contact (Recommendation #12)

Further details and background on each of these and the other recommendations can be found in the PEDNR Final Report [PDF, 998 KB]. The GNSO Council will now consider these recommendations for adoption.

Background

At the ICANN Meeting in Cairo in November 2008, the At-Large Advisory Committee (ALAC), voted to request an Issues Report on the subject of registrants being able to recover domain names after their formal expiration date. The ALAC request was submitted to ICANN policy staff and the GNSO Council on 20 November 2008. The Issues Report on Post-Expiration Domain Name Recovery [PDF, 422 KB] was submitted to the GNSO Council on 5 December 2008. The GNSO Council initiated a PDP on 7 May 2009 and tasked a Working Group to answer the following charter questions:

  • Whether adequate opportunity exists for registrants to redeem their expired domain names;
  • Whether expiration-related provisions in typical registration agreements are clear and conspicuous enough;
  • Whether adequate notice exists to alert registrants of upcoming expirations;
  • Whether additional measures need to be implemented to indicate that once a domain name enters the Auto-Renew Grace Period, it has expired (e.g., hold status, a notice on the site with a link to information on how to renew, or other options to be determined);
  • Whether to allow the transfer of a domain name during the RGP.

The Post-Expiration Domain Name Recovery (PEDNR) PDP Working Group started its deliberations in July 2009.

Further Information:

Staff responsible: Marika Konings


More Announcements
Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."