<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1163475193;
mso-list-template-ids:-175628148;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1377966307;
mso-list-template-ids:114186450;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2
{mso-list-id:2048404297;
mso-list-template-ids:-1787637054;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3
{mso-list-id:2116123438;
mso-list-template-ids:-1391328148;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Dear WG Members,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In response to the request for additional data on EBERO and SLA Monitoring (see email thread below for details and context), <i>please find the response from ICANN org’s Global Domains Division</i>:<o:p></o:p></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal style='margin-left:.5in'><b><u><span style='color:black'>Sub Pro PDP Request #1:</span></u></b><b><span style='color:black'> Looking at the failures, the WG needs clarity on whether they refer to service availability or Round Trip Time (RTT).</span></b><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in;text-indent:-.25in'><span style='font-size:10.0pt;color:black'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif;color:black'> </span><b><span style='color:black'>ICANN org Response to Request #1: </span></b><span style='color:black'>The failures refer to <i>Service Availability</i> and NOT Round Trip Time (RTT).<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><b><u><span style='color:black'>Sub Pro PDP Request #2:</span></u></b><b><span style='color:black'> For the failures that did NOT reach the EBERO threshold, the WG would like summary data of which of the SLRs was missed.</span></b><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in;text-indent:-.25in'><span style='font-size:10.0pt;color:black'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif;color:black'> </span><b><span style='color:black'>ICANN org Response to Request #2:</span></b><span style='color:black'> The SLRs that were missed were DNS Service Availability and RDDS Service Availability<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><b><u><span style='color:black'>Sub Pro PDP Request #3:</span></u></b><b><span style='color:black'> For the failures that DID reach the EBERO threshold, a detailed breakdown (e.g., similar specificity that was shared at the Madrid DNS Symposium / GDD Summit), which includes the timing of the failure.</span></b><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in;text-indent:-.25in'><span style='font-size:10.0pt;color:black'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif;color:black'> </span><b><span style='color:black'>ICANN org Response to Request #3:</span></b><span style='color:black'> See Below<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:black'>The ICANN SLAM Stats from Jan 2014 – Nov 2019 shows that there have been 52 cases where a gTLD reached one of the emergency thresholds:<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in;text-indent:-.25in'><span style='color:black'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif;color:black'> </span><span style='color:black'>23 out of the 52 cases were triggered by failures in the DNS/DNSSEC services<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in;text-indent:-.25in'><span style='color:black'>·</span><span style='font-size:7.0pt;font-family:"Times New Roman",serif;color:black'> </span><span style='color:black'>29 out of the 52 cases were triggered by failures in the RDDS<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.0in'><span style='color:black'>Of the 52 cases, 11 occurred prior to the TLDs Sunrise period, 8 during Sunrise, 2 post Sunrise, 4 before General Availability and 27 during General Availability.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.25in'><b><span style='color:black'> </span></b><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><b><span style='color:black'>DNS Failures:</span></b><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='color:black'>· Prior to Sunrise: 4 TLDs<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='color:black'>· During Sunrise: 2 TLDs<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='color:black'>· Post Sunrise: 0 TLDs<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='color:black'>· Before General Availability: 2 TLDs<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='color:black'>· General Availability: 15 TLDs<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><b><span style='color:black'>RDDS Failures: </span></b><span style='color:black'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='color:black'>· Prior to Sunrise: 7 TLDs<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='color:black'>· During Sunrise: 6 TLDs<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='color:black'>· Post Sunrise: 2 TLDs<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='color:black'>· Before General Availability: 2 TLDs<o:p></o:p></span></p><p class=MsoNormal style='margin-left:1.5in'><span style='color:black'>· General Availability: 12 TLDs<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.25in'><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:.5in'><span style='color:black'>13 RSPs, 35 gTLDs and a total of 760.7k active names were involved in the 52 cases.<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:.5in'><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in;text-indent:.5in'><span style='color:black'>The root cause, which ICANN began tracking in 2015, can be broken down as follows:<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=532 style='width:399.0pt;border-collapse:collapse'><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;background:#44546A;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><b><span style='color:white'>DNS</span></b><o:p></o:p></p></td><td width=53 style='width:39.4pt;border:solid windowtext 1.0pt;border-left:none;background:#44546A;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:white'>23</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>The DNS name servers were timing out</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>8</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>ICANN does not know the root cause</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>4</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>Either the DNS servers were not responding or if they were responding, they were returning a malformed DNSSEC response where the NSEC3 records were not included</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>4</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>There was no response from the DNS servers (apparently a routing issue)</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>2</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>Expired signatures followed by breakage of the chain of trust in DNSSEC</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>2</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>Break in the chain of trust in DNSSEC</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>1</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>Expire DNSSEC signatures</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>1</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>There were no DS records when requesting delegation from IANA</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>1</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;background:#44546A;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:white'>RDDS</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;background:#44546A;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:white'>29</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>ICANN does not know the root cause</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>12</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>IPv6 transport failure</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>12</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>RDDS name servers were timing out</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>2</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>Web WHOIS service not responding</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>2</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal><span style='color:black'>Broken chain of trust in DNSSEC</span><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>1</span></b><o:p></o:p></p></td></tr><tr style='height:14.0pt'><td width=479 style='width:359.6pt;border:solid windowtext 1.0pt;border-top:none;background:#A6A6A6;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=right style='text-align:right'><b><span style='color:black'>Total</span></b><o:p></o:p></p></td><td width=53 style='width:39.4pt;border-top:none;border-left:none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;background:#A6A6A6;padding:0in 5.4pt 0in 5.4pt;height:14.0pt'><p class=MsoNormal align=center style='text-align:center'><b><span style='color:black'>52</span></b><o:p></o:p></p></td></tr></table><p class=MsoNormal><span style='color:black'> <o:p></o:p></span></p><p class=MsoNormal><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='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'>Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> on behalf of Steve Chan <steve.chan@icann.org><br><b>Date: </b>Friday, October 18, 2019 at 2:00 PM<br><b>To: </b>Jeff Neuman <jeff.neuman@comlaude.com>, "gnso-newgtld-wg@icann.org" <gnso-newgtld-wg@icann.org><br><b>Subject: </b>Re: [Gnso-newgtld-wg] EBERO / SLAM Data Status and next steps<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>Dear All,<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>There did not appear to be any comments, questions, or objections to how the EBERO/SLAM data topic was characterized by Jeff, including what will be sought from ICANN Org’s GDD team. The information below will be sent to GDD for their review and resolution.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Best,<o:p></o:p></p><p class=MsoNormal>Steve<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='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'>Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> on behalf of Jeff Neuman <jeff.neuman@comlaude.com><br><b>Date: </b>Wednesday, October 2, 2019 at 8:14 AM<br><b>To: </b>"gnso-newgtld-wg@icann.org" <gnso-newgtld-wg@icann.org><br><b>Subject: </b>[Gnso-newgtld-wg] EBERO / SLAM Data Status and next steps</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><p class=MsoNormal>All,<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><span style='color:black'>On 23 August 2019, high-level statistics were shared from ICANN org’s SLA Monitoring program (attached). These statistics provided the monthly number of 1) DNS failures 2) RDDS failures and 3) DNS and RDDS failures that reached the EBERO threshold.</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>On 26 August 2019, Donna Austin shared a RySG document which included data previously shared by ICANN org at the Madrid DNS Symposium / GDD Summit (attached). This data provided more detail on group 3 above in particular, including elements like:</span><o:p></o:p></p><ul style='margin-top:0in' type=disc><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo3'>The cause for why the EBERO threshold was reached (i.e., DNS/DNSSEC or RDDS) <o:p></o:p></li><ul style='margin-top:0in' type=circle><li class=MsoNormal style='color:black;mso-list:l2 level2 lfo3'>A further, more specific breakdown within each of the two categories that indicate why the EBERO threshold was reached (e.g., IPv6 transport error, broken chain of trust in DNSSEC, etc.)<o:p></o:p></li></ul></ul><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>Within our Working Group there has been some discussion about what impact this data may have. For example, we discussed whether past failures should have any impact on future application evaluations or RSP pre-approval for future rounds? The Working Group, however, is trending towards agreeing that evaluation and thus RSP pre-approval (which is likely to leverage the same or substantially the same evaluation criteria) should be <i>forward looking</i> and <b><i>not be</i></b> impacted by past performance. The Working Group is also trending towards requiring the pre-approval prior to each evaluation round and that the approval will be good for the duration of the then-current round.</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>A second area in which this data could have an impact is whether or not existing Registry Service Providers should be grandfathered into any future pre-approval processes? Based on the Working Group’s deliberations and public comment received, the answer appears to be no. Most of the comments seem to point to requiring all RSPs (whether new or existing) to go through the same processes in future rounds.</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='color:red'>Therefore, based on where the Working Group is heading, the Co-Chairs do no believe that we are in need of additional historical data for purposes of finalizing its work on the RSP Pre-approval program. </span></b><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>We recognize that registry service provider performance has been a topic of discussion for matters other than the pre-approval program. We understand that there has been discussion about whether the relatively high number of registry services failures indicates that RSP might need to improve how they operate to ensure the security and stability of the DNS. While this WG is forward looking and not intending to impose new commitments for existing RSPs, lessons may be learned to improve the evaluation process for future applicants/RSPs. </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>Based on the above, the WG believes it does need more context from GDD to understand the data it has been provided, since not all SLA failures are equally harmful. Therefore in looking at the failures, for example, the WG needs clarity on whether they refer to service availability or Round Trip Time (RTT). The WG also wants to try and examine if there was any harm caused by the downtime, which is benefitted in part by understanding the timing of the failure (e.g., prior to Sunrise, during Sunrise, before General Availability, after GA).</span><o:p></o:p></p><ul style='margin-top:0in' type=disc><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo6'><b><i>For the failures that did NOT reach the EBERO threshold, the WG would like summary data of which of the SLRs was missed.</i></b><o:p></o:p></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo6'><b><i>For the failures that DID reach the EBERO threshold, a detailed breakdown (e.g., similar specificity that was shared at the Madrid DNS Symposium / GDD Summit), which includes the timing of the failure. </i></b><o:p></o:p></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo6'><b><i>This information may help identify weaknesses in the <u>evaluation criteria, registry system testing, and/or contractual requirements captured in the Registry Agreement</u>. </i></b><o:p></o:p></li></ul><p class=MsoNormal><b><span style='color:black'> </span></b><o:p></o:p></p><p class=MsoNormal><span style='color:black'>The leadership intends to send the request for additional context next week, but we would like to know if there are any comments from the Working Group. </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>Thanks for your attention to this matter.</span><o:p></o:p></p><p class=MsoNormal><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal><span style='color:black'>Best regards,</span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><b><span lang=EN-GB style='font-size:9.0pt;font-family:"Arial",sans-serif;color:black'>Jeff Neuman and Cheryl Langdon-Orr</span></b><o:p></o:p></p><p class=MsoNormal><b><span lang=EN-GB style='font-size:9.0pt;font-family:"Arial",sans-serif;color:black'>SubPro PDP Co-Chairs</span></b><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=1 width="100%" align=center></div><p class=MsoNormal>The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan. For further information see <a href="https://comlaude.com" target="_blank">www.comlaude.com</a> <o:p></o:p></p></div></body></html>