<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Gustavo,<div><br></div><div>Thank you for setting up the call to discuss this. </div><div><br></div><div>One of the items discussed on the call was support for partial matches. We previously requested for item 18 “WHOIS queries for domain name MUST return only one record per query” to be removed. This was further discussed at IETF-91. On the call there was confusion on whether other registries supported the partial match feature. Please note per the meeting minutes ( <a href="http://mm.icann.org/pipermail/gtld-tech/2014-November/000363.html">http://mm.icann.org/pipermail/gtld-tech/2014-November/000363.html</a> ) that I posted to the gtld-tech list, that states "<font face="Helvetica"><span style="font-size: 13px;">Multiple registries support wildcard queries in WHOIS, where if more than one object (domain or host) matches the query name ( with or without TLD ), a list of matching names is returned instead of a single record.” I confirmed this by connecting to a sample of the old and new gTLD WHOIS servers, that showed that at least three other registries support partial match. Not only was the feedback disregarded, but the language was tightened in clarification 18 and a new clarification 28 was added that further prohibited the feature. The reason stated on the call to forbid this feature was that it wasn’t explicitly defined in Specification 4 of the Registry Agreement. This feature exists solely for the benefit of the end user and should not be disallowed in a clarifications document with no real compelling reason. </span></font></div><div><br></div><div><font face="Helvetica"><span style="font-size: 13px;">Following the discussion on the partial match we discussed clarification 30, which defines support for querying name servers by roid. In clarification 30, ICANN defines a new feature that is also not </span></font><span style="font-family: Helvetica; font-size: 13px;">explicitly allowed in Specification 4 of the Registry Agreement. The reason stated on the call for adding this feature </span><span style="font-family: Helvetica; font-size: 13px;">in the clarifications document </span><span style="font-family: Helvetica; font-size: 13px;">was that ICANN felt it provided value to the end user. </span></div><div><span style="font-family: Helvetica; font-size: 13px;"><br></span></div><div><font face="Helvetica"><span style="font-size: 13px;">In the clarifications document ICANN is taking an inconsistent approach to their interpretation of Specification 4. Please stop using a clarifications document to disallow features you don’t like and add features you want. </span></font></div><div><br></div><div>Thanks,</div><div><br><div>
<div style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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;"><p style="margin: 0px;"><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size: 15px;">—</span></font></p><p style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;"><font face="Calibri,Verdana,Helvetica,Arial" style="font-size: 14px;"><span style="font-size: 11pt;"><br></span></font></p><p style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; margin: 0px;"><font face="Calibri,Verdana,Helvetica,Arial" style="font-size: 14px;"><span style="font-size: 11pt;">JG<br><br></span></font></p></div><span style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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;"><br class="Apple-interchange-newline" style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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;"><span style="color: rgb(0, 0, 0); font-family: Verdana; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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;"><span><img height="64" width="73" apple-inline="yes" id="145A9DB9-1A37-4A8E-94CB-8729AA499E36" apple-width="yes" apple-height="yes" src="cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com"></span><font face="Calibri,Verdana,Helvetica,Arial" style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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; font-size: 14px;"><span style="font-size: 11pt;"><br></span></font><font face="Times,Times New Roman" style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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; font-size: 14px;"><span style="font-size: 12pt;"><br></span></font><font color="#006AAA" style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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; font-family: Calibri, sans-serif; font-size: 14px;"><font size="2"><font face="Helvetica,Verdana,Arial"><span style="font-size: 10pt;"><b>James Gould<br></b></span></font></font></font><font size="2" style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 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; font-family: Calibri, sans-serif;"><font face="Helvetica, Verdana, Arial"><span style="font-size: 10pt;"><font color="#6B6D71">Distinguished Engineer<br><a href="jgould@Verisign.com">jgould@Verisign.com</a><br><br>703-948-3271<br>12061 Bluemont Way<br>Reston, VA 20190<br><br></font><font color="#006AAA"><a href="http://VerisignInc.com">VerisignInc.com</a></font></span></font></font>
</span></span></div>
<br><div><div>On Dec 9, 2014, at 7:41 PM, Gustavo Lozano <<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;"><div><div>Hello colleagues,</div><div><br></div><div>Attached you will find the Draft Updated WHOIS Clarification Advisory. Two versions are provided for your reference: clean version and redline against the original advisory (v 1.0) as published on 12 September 2014 (<a href="https://www.icann.org/resources/pages/registry-agreement-spec4-raa-rdds-2014-09-12-en">https://www.icann.org/resources/pages/registry-agreement-spec4-raa-rdds-2014-09-12-en</a>).</div><div><br></div><div>This draft version incorporates feedback gathered from various contracted parties, cases/emails sent to ICANN, the WHOIS Clarification Advisory meeting held at IETF 91 in November, and feedback sent to the gtld-tech mailing list. </div><div><br></div><div>A conference call, with the objective of gathering feedback on this draft version, will take place on Tuesday 16 December 2014. If you want to participate in the conference call, please send me an email to <a href="mailto:fabien.betremieux@icann.org">fabien.betremieux@icann.org</a>.</div><div><br></div><div>Please send any feedback or questions you have on this version of the advisory to the mailing list as soon as possible, in order for ICANN Staff to discuss internally and provide an answer during the conference call.</div><div><br></div><div>It's important to remember:</div><div>* This advisory is not meant to create new requirements for contracted parties.</div><div>* This advisory is not meant to redefine the WHOIS protocol.</div><div>* This advisory resulted from questions sent by contracted and third parties seeking clarification on the Whois (RDDS) requirements in the New gTLD base RA and 2013 RAA.</div></div><div><br></div><div>Regards,</div><div>Gustavo</div><div>ICANN</div></div>
<span><Registry and Registrar RDDS Advisory - 1.0 vs 20141209[1][1].docx></span><span><Registry and Registrar RDDS Advisory - 20141209[3].docx></span></blockquote></div><br></div></body></html>