I see the point,

But this solution is not going to solve the problem.

Registrars will need to update all of their names as they renew, so if a registrar can update the expiry date in the registry via EPP, it might as well do an EPP <info> command, and update the record at the RAR level. Read operations are cheaper and faster.

In any of these approaches there will be a period in which both dates are out of sync.

Perhaps all we need is better wording explaining how this works, or even have a RAR and RY expiry date displayed in the RAR whois, the only entity that would have both of them.

In my opinion this is a HUGE effort (not in dev work but in Operational/implementation) with little gain.

regards,

Francisco Obispo 
CTO - Registry Operations
____________________________

2161 San Joaquin Hills Road 
Newport Beach, CA 92660 

Office +1 949 706 2300 x4202 
fobispo@uniregistry.link

On 21 Jan 2016, at 18:12, Greg Aaron wrote:

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?”)