Here’s a problem that raises the issue of whether date data from the registrar should be preserved (at least for a time) in a thin-to-thick registry migration. Some registrars have dates that are out of synch with the Verisign registry. The registry dates should be authoritative. But when data’s out of synch it creates questions and problems for registrants. (Like, “My registrar told me my domain doesn’t expire for another week – what do you mean it expired three days ago?”) Here’s a real-life example, where NONE of the dates match: VERISIGN WHOIS SEZ: Domain Name: DIRECTNIC.COM Updated Date: 03-sep-2014 Creation Date: 09-feb-2000 Expiration Date: 09-feb-2017 The REGISTRAR WHOIS SEZ: Domain Name: DIRECTNIC.COM Updated Date: 2015-05-26T07:01:01-05:00 Creation Date: 2000-05-25T05:45:12-05:00 Registrar Registration Expiration Date: 2016-05-25T05:45:12-05:00 All best, --Greg From: gtld-tech-bounces@icann.org [mailto:gtld-tech-bounces@icann.org] On Behalf Of Francisco Obispo Sent: Thursday, January 21, 2016 6:20 PM To: Francisco Arias Cc: gtld-tech@icann.org Subject: Re: [gtld-tech] Registrar Expiration Date I-D I thought that in the thick model, the Registry was the only authoritative source for the expiration date of the domain name. The documents linked there don’t provide an explanation on why the ‘registrar expiration date’, is needed at the registry level, they seem to focus on when but not on the why. Can we just simply say that the Registrar Expiration Date Is not applicable at the registry level? I’m just envisioning here having to implement yet-another-extension, and then try to get all RARs to update the information before a deadline, etc. Can someone please clarify what it is that we’re trying to achieve here? Thanks! On 21 Jan 2016, at 14:54, Francisco Arias wrote: Hi Ben and Michele, The requirement has been discussed in the context of the Thick Whois Policy implementation. Please see https://whois.icann.org/sites/default/files/files/thick-rdds-consensus-polic..., particularly section 2.1, starting on page 8. By the way, this document is in public comment at https://www.icann.org/public-comments/rdds-output-2015-12-03-en until 31 January. Regards, -- Francisco On 1/21/16, 2:30 PM, "gtld-tech-bounces@icann.orggtld-tech-bounces@icann.org on behalf of Benoit Levac" <gtld-tech-bounces@icann.org <mailto:gtld-tech-bounces@icann.org%3cmailto:gtld-tech-bounces@icann.org> <mailto:gtld-tech-bounces@icann.org> on behalf of benoit.levac@rightside.cobenoit.levac@rightside.co> wrote: Francisco, I don't see any explanation for making registries store and publish the "Registrar Registration Expiration Date" in the "ICANN Thick Whois Policy Recommendation". What is the use case we are trying to solve for? Ben On Thu, Jan 21, 2016 at 1:55 PM, Francisco Arias <francisco.arias@icann.org <mailto:francisco.arias@icann.org%3cmailto:francisco.arias@icann.org> <mailto:francisco.arias@icann.org>> wrote: On 1/21/16, 11:59 AM, "Gustavo Lozano" <gustavo.lozano@icann.org <mailto:gustavo.lozano@icann.org%3cmailto:gustavo.lozano@icann.org> <mailto:gustavo.lozano@icann.org>> wrote: Hello colleagues, I uploaded an I-D (http://www.ietf.org/id/draft-lozano-ietf-eppext-registrar-expiration-date- 00.txt) in order to define an EPP extension to support the transmission of the registrar registration expiration date from the registrar to the registry. This extension is defined in order to support the ICANN Thick Whois Policy Recommendation (http://gnso.icann.org/en/issues/whois/thick-final-21oct13-en.pdf) that requires gTLD domain name registries to display the registrar registration expiration date in the Registration Data Directory Service (e.g. Whois, RDAP). Your feedback is appreciated. Regards, Gustavo -- Benoit Levac VP Engineering, Registry Platform Office | 425-298-2337 Mobile | 613-617-4416 benoit.levac@rightside.cobenoit.levac@rightside.co www.rightside.cohttp://www.rightside.co * PGP Signed by an unknown key Francisco Obispo CTO - Registry Operations ____________________________ <http://www.uniregistry.com/> Uniregistry 2161 San Joaquin Hills Road Newport Beach, CA 92660 Office +1 949 706 2300 x4202 fobispo@uniregistry.link * Unknown Key * 0xB38DB1BE
