[Ssr2-review] Compliance follow-up to questions from SSR2 RT Meeting

Karen Mulberry karen.mulberry at icann.org
Thu Jul 13 19:15:51 UTC 2017

From: Maguy Serad <maguy.serad at icann.org>

Thank you for the opportunity to present a briefing on SSR1 Recommendation #10.
Below the responses to the questions from the session.
Please let me know if I missed anything or if you have more questions.



  1.  At DNS Symposium in Madrid, a presentation made about SLA indicated that 32 out of the 37 RSP had failed their DNS SLA. Can you please provide more information on this?

  *   Link to the presentation referenced in the question https://www.icann.org/en/system/files/files/presentation-slam-13may17-en.pdf - slide #23.
  *   The ICANN SLA monitoring system triggers automated escalated alerts to registry operators via the ICANN Contractual Compliance ticketing system for DNS and RDDS failures. Upon resolution of the issue, the Compliance team follows up with the registry operator to find out what happened and the registry operator’s remediation. The reasons for failures (and fixes) vary widely. The Compliance team consults with ICANN Technical Services before closing a ticket to ensure the response is sufficient.
  *   Compliance tracks the SLAM alerts by gTLD not by RSP.
  *   The decision to invoke emergency transition of a TLD (EBERO) is made by the EBERO event directors team. Invoking an EBERO event may not be deemed helpful when the impact is low, such as when there are no registrations or when a registry is responsive and addressing the failure.
  *   If you require more information, please send us the question and we can forward it to the ICANN Technical Services team for a follow-up.

  1.  Regarding WHOIS Bulk submission – what is the use of this tool?

  *   ICANN has 10 approved users; users can submit up to 300 WHOIS Inaccuracy complaints at a time per submission per week.
  *   During May 2017, ICANN processed a total of 154 tickets initiated from the bulk submission user. This information can be found in the monthly dashboard at this link https://features.icann.org/compliance .

  1.  Recent article about high rate of failure of registrars in an audit conducted by compliance – Share the link to the published report

  *   Link to the published registrar audit report https://www.icann.org/resources/pages/compliance-reports-2016

  1.  What does compliance do regarding enforcement of registry obligations for CZDS?

·         (CZDS) Zone File Access by Third Parties via the Centralized Zone Data Service

·         Compliance receives complaints alleging that registry operators are not responding to requests for zone file or denying/revoking access for reasons not permitted under the registry agreement.

·         The Registry Agreement is not explicit on when a registry operator must reply to requests for access. ICANN forwards the complaint to the RO and inquires about the pending requests and works toward a resolution of the issue. As for denial or revocation of access, registry operators collaborate with CZDS users to clarify the user’s credentials and usage. However, imposing requirements for access beyond those in the registry agreement and CZDS Terms and Conditions is noncompliant.

  1.  What actions does compliance take regarding Abuse?

  *   ICANN provided a detailed response on handling of abuse in the response to Annex 1 GAC Communique; the response is at this link https://gacweb.icann.org/display/gacweb/GAC+Correspondence?preview=/27492514/44663038/Marby-to-Schneider-with-Enclosure-8Feb2017.pdf


Karen Mulberry
Multistakeholder Strategy and Strategic Initiatives (MSSI)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ssr2-review/attachments/20170713/cec52601/attachment.html>

More information about the Ssr2-review mailing list