[RDS-WHOIS2-RT] Common Interface rec.

[Jean-Baptiste Deroulez]

Dear review team members,

In response to your two questions below submitted on 12 December 2018, It seems that SME’S have previously addressed these questions in the WHOIS1 Implementation Briefings circulated in November 2017<https://mm.icann.org/pipermail/rds-whois2-rt/2017-November/000207.html>.  You can find the responses under questions 6, 7 and 8 in the following document<https://community.icann.org/download/attachments/63145823/WHOIS1-Implementation%20Briefings_final.docx?version=1&modificationDate=1510566466000&api=v2>.

Please kindly let us know if there is any other specific question that the Review Team would like SME’s to address.

Kind regards,

Jean-Baptiste

From: RDS-WHOIS2-RT <rds-whois2-rt-bounces at icann.org> on behalf of Susan Kawaguchi <susankpolicy at gmail.com>
Date: Wednesday, December 12, 2018 at 1:20 PM
To: RDS WHOIS2-RT List <rds-whois2-rt at icann.org>
Subject: [RDS-WHOIS2-RT] Common Interface rec.


We have additional questions for ICANN org. Please see highlighted below



We have found several error messages in using the tool referenced below:

The requested second-level domain was not found in the Registry or Registrar’s WHOIS Server. (the domain name was confirmed to be registered with the registry)


Sorry, but the Registry or Registrar WHOIS Server responded with a rate limit message due to high query volumes or has closed the connection without a response. Please try your request again later.


ICANN received a timeout while querying the Registry or Registrar’s WHOIS Server


Are these error messages created by ICANN or do they come directly from the Registrar or Registry?


Does ICANN track how often these error messages are presented in response to a WHOIS query?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt/attachments/20181218/41561d6a/attachment.html>