Thanks for the opportunity to provide comments, Gustavo. It would be helpful to add more introductory text (perhaps in a section titled something like “Operational Assumptions”) to explicitly note several implied functional points. Here are a few that I found:

In Section 3, the document says that HTTP Basic authentication is used. Without additional information, that means that credentials are exchanged in plaintext form. Encryption service is hidden in the description of the base URL mentioned in Section 2. I think it would be helpful to note somewhere that TLS protection is required, and that the credentials are protected using TLS.

Have you thought about using TLS with mutual authentication of both clients and servers? That would add an extra layer of protection to ensure that only authorized clients have access to TLD-specific data.

It would also be helpful to explicitly state that login credentials are provided by ICANN (how are they requested and delivered?), or at least provide a link to some other document that explains the process.

It would also be helpful to note that the client must provide (how?)  ICANN with a list of IP addresses to be added to a per-TLD white list. Are both IPv4 and IPv6 addresses acceptable? If not, why?

Scott

From: gtld-tech-bounces@icann.org [mailto:gtld-tech-bounces@icann.org] On Behalf Of Gustavo Lozano
Sent: Saturday, February 11, 2017 12:17 AM
To: gtld-tech@icann.org
Subject: [EXTERNAL] [gtld-tech] ICANN monitoring system API

Hello Colleagues,

Specification 10 of the base registry agreement (https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-09jan14-en.htm) describes the Service Level Requirements and emergency thresholds that a Registry Operator has to comply related to the Registry Services.

ICANN has been monitoring compliance of new gTLDs following the algorithms defined in this specification.

ICANN provides access to Registry Operators to the incident information of its TLDs through an API currently in beta, and we are planning on releasing the production version in the future.

The Registry Operators using the beta API had provided valuable feedback, and the specification to be implemented in the production version has been modified accordingly.

Attached you will find the latest draft of this specification. I appreciate your feedback no later than February 24, 2017.

Regards,

Gustavo