<html 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=Windows-1252">
<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:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:ZH-CN;}
.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:1117829330;
mso-list-type:simple;
mso-list-template-ids:1117829330;}
@list l0:level1
{mso-level-suffix:space;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:0in;
text-indent:0in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-US">Below and attached is the comment of ICANN’s Business Constituency (BC) regarding </span>
</b><b><span style="font-size:12.0pt;color:black">Recommendations for ICANN’s Root Name Service Strategy and Implementation.</span><o:p></o:p></b></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">The BC commends ICANN’s Office of the Chief Technology Officer (OCTO) on studies generated so far, and supports the continuation of these research projects, preferably published in all UN languages.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">The recommendations came at a time when more users and businesses are depending upon the Internet to conduct their activities, significantly increasing the load on the existing Root Server System
(RSS) infrastructure. Placing Root Server Instances in diverse locations is a great strategy to handle increasing load and provide more resilience in areas where Internet adoption is growing – mostly via mobile.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">We recognize that the so-called Internet of Things (IoT) is still in its infancy, and we are yet to envision what the consequences of its deployment will truly look like once 5G networks and compatible
devices are installed in a significant way. However, we observe their potential destructive power against the DNS in the hands of rogue actors, and this paints a troubling picture. ICANN Org should have presence in associations and groups related to IoT device
manufacture to advance security by design, ensuring the DNS’ continued protection.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">To keep pace with the evolving threat landscape, we favor overprovisioning and erring on the side of caution, instead of potentially exposing businesses who are members of the BC to disruptions
that could result in significant losses and security risks. The BC will publicly support expenditures made in this direction.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">ICANN Org should support with funds and capability the placement of ICANN Managed Root Server (IMRS) single instances in geographic areas where it is required but not feasible due to financial
and/or knowledge restrictions. This will help build capability in these areas leading to innovation and more support for the RSS infrastructure.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">We support additional research into monitoring and how it would be performed, but request that a stream in the research should focus on the cost associated with the development, deployment and
maintenance of these monitoring systems and the relative benefit to the operations of the RSS infrastructure in the long run.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">The BC agrees with the strategy of encouraging hyperlocal deployment, and recommends that ICANN Org makes full use of its community’s resources in sourcing local partners, such as ISPs, considering
that they are working day-to-day with these actors. It would be a desirable gesture for ICANN Org to directly seek this kind of input, fostering stronger cooperation between both sides. The work of the regional managers should also be galvanized as the pandemic
starts to wane. We further recommend a higher level of promotion, publicity and collaboration for the deployment of DNSSEC to tackle the integrity exposure of Root zone data.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">We would also like to see OCTO further pursue studies on the potential of IMRS Cloud, for us to fully grasp how implementation of these solutions could further ensure the Internet is technically
stable, secure and reliable. We signal this a priority in terms of upcoming research. We would also like to better understand what are the opportunities to streamline the ICANN root zone encryption system with new technologies.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-US">--</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-US">This comment was drafted by Mark Datysgeld, Jimson Olufuye, and Vivek Goyal.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-US">It was approved in accord with our Charter.</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-US">Steve DelBianco</span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-US">Vice Chair for Policy Coordination </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-US">ICANN Business Constituency (BC) </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black;mso-fareast-language:EN-US"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"> </span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;mso-fareast-language:EN-US"> </span></p>
</div>
</body>
</html>