<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Jacques,</div><div><br></div><div>I was thinking the same thing, or rather, would that not be a good topic for TechDay?</div><div><br></div><div>el<br><br><div>-- <div>Sent from Dr Lisse's iPad mini 4</div></div></div><div><br>On 13 May 2017, at 11:02, Jacques Latour <<a href="mailto:jacques.latour@cira.ca">jacques.latour@cira.ca</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<div>Hi,</div>
<div>Will this API be available to ccTLD as well?</div>
<div>Jacques</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>On 2017-05-12, 6:12 PM, "Victor Figueroa" <<a href="mailto:gtld-tech-bounces@icann.org">gtld-tech-bounces@icann.org</a> on behalf of
<a href="mailto:victor.figueroa@icann.org">victor.figueroa@icann.org</a>> wrote:</div>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:Calibri;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hello Ron Geens, <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">ICANN is currently working on the development of the production version of the Monitoring System API (MoSAPI). There is no date yet for the release of this version. We plan to notify registries in advance of the release.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In the meantime, the MoSAPI beta version is available. Registries can request access to the MoSAPI beta through ICANN's Global Support Center, please see
<a href="https://www.icann.org/resources/pages/customer-support-2015-06-22-en">https://www.icann.org/resources/pages/customer-support-2015-06-22-en</a>.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards, <o:p></o:p></p>
<p class="MsoNormal">Victor Figueroa<o:p></o:p></p>
<p class="MsoNormal">Technical Services Senior Manager<o:p></o:p></p>
<p class="MsoNormal">ICANN<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black"><<a href="mailto:gtld-tech-bounces@icann.org">gtld-tech-bounces@icann.org</a>> on behalf of Ronald Geens <<a href="mailto:ronald.geens@dnsbelgium.be">ronald.geens@dnsbelgium.be</a>><br>
<b>Date: </b>Thursday, May 4, 2017 at 1:33 AM<br>
<b>To: </b>"<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>" <<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>><br>
<b>Subject: </b>Re: [gtld-tech] ICANN monitoring system API</span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman""><o:p> </o:p></span></p>
</div>
<p class="MsoNormal">Hi, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"> I am re-opening this thread to inform about any progress that has been made on specifying or even rolling out this API.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">We would be interested in using this as an additional monitoring service but I cannot find a more recent update than this mail thread from February.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Ron Geens<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">DNS Belgium<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 25 Feb 2017, at 01:48, Gustavo Lozano <<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><i>Thank you for your feedback, Scott, and </i>Michele<i>,</i><o:p></o:p></p>
<p class="MsoNormal"><i> </i><o:p></o:p></p>
<p class="MsoNormal"><i>@Scott,</i><o:p></o:p></p>
<p class="MsoNormal"><i> </i><o:p></o:p></p>
<p class="MsoNormal">I think it would be helpful to note somewhere that TLS protection is required, and that the credentials are protected using TLS.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#002060">[Gustavo Lozano] - OK, I will add text in this regard.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#002060">[Gustavo Lozano] - Thank you for the suggestion, we have it in our to-do list.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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.<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#002060">[Gustavo Lozano] - OK, I will add text in this regard.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">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?<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span style="color:#002060">[Gustavo Lozano] - OK, I will add text in this regard. The input mechanism for IP address blocks supports IPv4 and IPv6, however in the beta of the Monitoring System API, we only have IPv4 transport support.</span><o:p></o:p></p>
<p class="MsoNormal"><i> </i><o:p></o:p></p>
<p class="MsoNormal"><i>@Michele,</i><o:p></o:p></p>
<p class="MsoNormal"><i> </i><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Speaking of IPs .. </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Ideally being able to provide blocks, rather than lists of IPs ..
</span><o:p></o:p></p>
<p class="MsoNormal"><i> </i><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#002060">[Gustavo Lozano] - In the GDD Portal, the Registry Operator can set the list of IP address blocks to be allowed to access the RRI (Registry Reporting Interface). The Monitoring System API uses the same credentials.</span><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Regards,<o:p></o:p></p>
<p class="MsoNormal">Gustavo<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Michele Neylon - Blacknight [<a href="mailto:michele@blacknight.com">mailto:michele@blacknight.com</a>]
<br>
<b>Sent:</b> Friday, February 17, 2017 5:15 AM<br>
<b>To:</b> Hollenbeck, Scott <<a href="mailto:shollenbeck@verisign.com">shollenbeck@verisign.com</a>>; Gustavo Lozano <<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>>; '<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>' <<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>><br>
<b>Subject:</b> [Ext] Re: [gtld-tech] ICANN monitoring system API<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Speaking of IPs .. </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Ideally being able to provide blocks, rather than lists of IPs ..
</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span lang="EN-GB">--</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Mr Michele Neylon</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Blacknight Solutions</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Hosting, Colocation & Domains</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB"><a href="https://www.blacknight.com/">https://www.blacknight.com/</a></span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB"><a href="http://blacknight.blog/">http://blacknight.blog/</a></span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Intl. +353 (0) 59 9183072</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Direct Dial: +353 (0)59 9183090</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Personal blog: <a href="https://michele.blog/">
https://michele.blog/</a></span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Some thoughts: <a href="https://ceo.hosting/">
https://ceo.hosting/</a> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">-------------------------------</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span lang="EN-GB">Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-GB">From: </span></b><span lang="EN-GB"><<a href="mailto:gtld-tech-bounces@icann.org">gtld-tech-bounces@icann.org</a>> on behalf of Scott Hollenbeck <<a href="mailto:shollenbeck@verisign.com">shollenbeck@verisign.com</a>><br>
<b>Date: </b>Friday 17 February 2017 at 13:05<br>
<b>To: </b>"'<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>'" <<a href="mailto:gustavo.lozano@icann.org">gustavo.lozano@icann.org</a>>, "'<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>'" <<a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a>><br>
<b>Subject: </b>Re: [gtld-tech] ICANN monitoring system API</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-family:"Times New Roman""> </span><o:p></o:p></p>
</div>
<p class="MsoNormal"><a name="_MailEndCompose"><span lang="EN-GB" style="color:#1F497D">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:</span></a><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">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.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">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.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">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.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">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?</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D">Scott</span><o:p></o:p></p>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="color:#1F497D"> </span><o:p></o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-GB">From:</span></b><span lang="EN-GB"> <a href="mailto:gtld-tech-bounces@icann.org">
gtld-tech-bounces@icann.org</a> [<a href="mailto:gtld-tech-bounces@icann.org">mailto:gtld-tech-bounces@icann.org</a>]
<b>On Behalf Of </b>Gustavo Lozano<br>
<b>Sent:</b> Saturday, February 11, 2017 12:17 AM<br>
<b>To:</b> <a href="mailto:gtld-tech@icann.org">gtld-tech@icann.org</a><br>
<b>Subject:</b> [EXTERNAL] [gtld-tech] ICANN monitoring system API</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Hello Colleagues,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Specification 10 of the base registry agreement (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__newgtlds.icann.org_sites_default_files_agreements_agreement-2Dapproved-2D09jan14-2Den.htm&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=VbweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=cTdHSr5Ru2vE9oxoRasvA_FP8b5lxG_LgBzPtUN6cuc&s=cN9Uyg3mU-hTu7dDU3f-oCpzmJG_1sKiAvIoKReQo28&e=">https://newgtlds.icann.org/sites/default/files/agreements/agreement-approved-09jan14-en.htm[newgtlds.icann.org]</a>)
describes the Service Level Requirements and emergency thresholds that a Registry Operator has to comply related to the Registry Services.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">ICANN has been monitoring compliance of new gTLDs following the algorithms defined in this specification.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">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.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">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.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Attached you will find the latest draft of this specification. I appreciate your feedback no later than February 24, 2017.</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Regards,</span><o:p></o:p></p>
<p class="MsoNormal"><span lang="EN-GB">Gustavo</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman""><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</div></blockquote></body></html>