<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:mv="http://macVmlSchemaUri" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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;}
@font-face
{font-family:"Source Sans Pro";
panose-1:2 11 5 3 3 4 3 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
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;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:595.0pt 842.0pt;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1027"/>
</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 bgcolor="white" lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Dear all,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Below are some Future Challenges workstream answers. The complete list of questions and answers are here:
<a href="https://docs.google.com/document/d/14eJwDGP-LvS9ltTmZoh1i19Fi0_pB2nJ4JYMsS7lsco/edit#">
https://docs.google.com/document/d/14eJwDGP-LvS9ltTmZoh1i19Fi0_pB2nJ4JYMsS7lsco/edit#</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Review Team volunteers: <span style="background:yellow;mso-highlight:yellow">
Laurin, Eric, Kerry-Ann</span> <o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Workstream: Future Challenges<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Topic: New uses for DNS (IoT, etc.)
<o:p></o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Q: Has ICANN identified any scenarios where the current DNS infrastructure would fail?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">A: DDoS attacks on all the root servers, or on all the servers for one or more TLDs, could cause some domains to be unreachable by some users, but the infrastructure itself would not be damaged, and reachability
for domains in those zones would recover as the attacks abated.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Q: Are there any groups, reports, or is there any work being done to track new uses of DNS?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">A: OCTO regularly discusses new uses of the DNS with the ICANN community at ICANN meetings. This is based on OCTO's following of new uses of the DNS in the IETF. This has happened many times. For example,
at ICANN 60, we presented to the TEG and Board about using DOA in the DNS <<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__icann60abudhabi2017.sched.com_event_CbHh_joint-2Dmeeting-2Dicann-2Dboard-2Dtechnical-2Dexperts-2Dgroup-2Dteg-253E&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=VuRMFw6YascG5ysc1jEHBZgGTtD6QSLrFmqdvMx5FM8&m=GvklFCzIizIWEcI97Lg03KCQ1TfUfh6r8EuQOyA8DqM&s=8ddr3AvKyAWwf5Dw3tm_c2pNRL1W2EAKgNlXh0Brt00&e=">https://icann60abudhabi2017.sched.com/event/CbHh/joint-meeting-icann-board-technical-experts-group-teg>
[icann60abudhabi2017.sched.com]</a>. We will present to the community at ICANN 64 about DNS-over-TLS and DNS-over-HTTP <<a href="https://64.schedule.icann.org/meetings/961998">https://64.schedule.icann.org/meetings/961998</a>>.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Outstanding questions on this topic: 0<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Review Team volunteers: <span style="background:yellow;mso-highlight:yellow">
Eric, Norm, Laurin, Kerry-Ann, Noorul</span></span></b><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Workstream: Future Challenges
</span></b><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Topic: Privacy protections
</span></b><span style="font-size:11.0pt">(<i>DNS over TLS / over HTTPS; Circular dependencies between WebPKI and DNSSEC; Impact on Proactive anti-abuse and investigations)</i><b><o:p></o:p></b></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Q: Does ICANN track these developments, what are the findings, and how do they feed into ICANN operations and policy?
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">A: ICANN follows DoT and DoH. There are no particular findings about these new technologies. To date, nothing about DoT or DoH has needed to be fed into ICANN operations and policy.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Outstanding questions on this topic: 1
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Review Team volunteers: <span style="background:yellow;mso-highlight:yellow">
Eric, Russ, Ram, Laurin</span></span></b><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Workstream: Future Challenges
</span></b><span style="font-size:11.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt">Topic: New crypto systems in DNSSEC<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Q: What resources and processes are in place to track and make the Board aware and factor into strategic planning for this?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">A: OCTO regularly informs the Board Technical Committee and executive team about technical news that might affect Board decisions. OCTO informed the BTC and execs of NIST's report on the progress of the post-quantum
cryptography work. <a href="https://www.nist.gov/publications/status-report-first-round-nist-post-quantum-cryptography-standardization-process">
https://www.nist.gov/publications/status-report-first-round-nist-post-quantum-cryptography-standardization-process</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Q: What analyses or study/studies have been done?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">A: NIST is the primary creator of such reports and studies. As these reports are published, OCTO informs the Board Technical Committee and the executive team of the reports and gives brief background on them.
Eg. <a href="https://csrc.nist.gov/publications/detail/nistir/8240/final">https://csrc.nist.gov/publications/detail/nistir/8240/final</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Outstanding questions on this topic: 1<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.5pt;color:black">-- <o:p></o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">Jennifer Bryce</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">Senior Reviews Coordinator </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">Internet Corporation for Assigned Names and Numbers (ICANN)</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">Email: jennifer.bryce@icann.org</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">Skype: jennifer.bryce.icann</span><span style="color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Source Sans Pro";color:#595959">www.icann.org</span><o:p></o:p></p>
</div>
</body>
</html>