<p dir="auto">On 27 Jan 2016, at 8:45, Thomas Corte wrote:
</p>
<blockquote>
<p dir="auto">On 27/01/2016 17:22, Greg Aaron wrote:
</p>
<blockquote>
<p dir="auto">So I see three options:
<br/>
1. Registrar-based WHOIS will always be required, because of expiration date
<br/>
variances we've been discussing here, caused by auto-renewals and registrar
<br/>
payment policies.
<br/>
2. Registrar-based WHOIS goes away. Registry WHOIS contains an Registry
<br/>
Expiration Date AND a Registrar Expiration Date field. The registrar
<br/>
populates and manages the latter.
<br/>
3. Registrar-based WHOIS goes away. The WHOIS only shows the registry
<br/>
expiration date, and registrars and registrants have to communicate with
<br/>
each other about expirations and payments etc.
</p>
</blockquote>
<br/>
<p dir="auto">My personal preference would be 3, however (as said before) it seems that
<br/>
registrant confusion about a domain's fate can best be avoided by option 2.
</p>
</blockquote>
<p dir="auto">I would argue that a significant portion of the Registrants reading
</p>
<p dir="auto">…yadda-yadda expiration date: <some date>
<br/>
…yadda-yadda expiration date: <some other date>
</p>
<p dir="auto">will be a greater source of confusion, possibly causing support tickets that someone will need to address. That, in addition to all the work that having the two fields in the same place will cause. And to note, if dates do not match today, they won’t match after implementation of the proposed extension either. This looks more and more like the wong solution for a non-problem.
</p>
<p dir="auto"><body style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><p style="font-family: 'Proxima Nova', Helvetica, Arial, sans-serif; line-height: 12px;"><span class="address-sep break" style="display: inline;"><b>Luis Muñoz</b><br></span><font color="#1e1e1e">Director, Registry Operations</font><br><span class="txt signature_jobtitle-input sig-hide" style="color: rgb(130, 130, 130); display: inline;">____________________________</span></p><p style="color: rgb(0, 0, 0); font-family: 'Proxima Nova', Helvetica, Arial, sans-serif; font-size: 10px; line-height: 14px;"><a href="http://www.uniregistry.link" class="clink sig-hide logo-container"><img src="http://static.uniregistry.net/assets/img/ur-logo@2x.png" alt="Uniregistry" class="sig-logo" height="40" border="0" width="165"></a></p><p style="color: rgb(0, 0, 0); font-family: 'Proxima Nova', Helvetica, Arial, sans-serif; font-size: 11px; line-height: 14px;"><span class="website-sep break" style="display: inline;">2161 San Joaquin Hills Road<br>Newport Beach, CA 92660</span></p><p style="color: rgb(0, 0, 0); font-family: 'Proxima Nova', Helvetica, Arial, sans-serif; font-size: 11px; line-height: 14px;"><span class="txt signature_officephone-input sig-hide" style="display: inline;">Office +1 949 706 2300 x 4242<br>lem@uniregistry.link</span></p></div></div></div></body>
</p>