<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="en-BW" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;mso-fareast-language:EN-US">Dear Barrack, thank you for this information.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;mso-fareast-language:EN-US">I do not think ccTLDs would do good being governed like gTLDs and imposing national policies is not ideal. Rather encourage Governments to recognize ccTLDs in their
National policies, and even subsidise and support the running of ccTLDs. For those Governments with Data Protection Acts which have data accuracy obligations, the relevant DPA Commissioner needs to work with Registries and encouraged to adopt ways of ensuring
accuracy of Registrant data.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;mso-fareast-language:EN-US">What I seem to agree with about the NIST2 is that countries should declare/recognize ccTLDs as Critical Infrastructure. In my country for instance, anything deemed as
National Critical Information Infrastructure is treated with priority including ensuring its continuity, stability, and security of that infrastructure. The cybersecurity unit’s role includes dealing with cybercrime perpetuated through the DNS or on the DNS.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;mso-fareast-language:EN-US">This model isn’t the only work around. ccTLDs can collaborate with National CIRTs without using strict enforcements and stringent supervision. In our case where there
is absence of a Cybersecurity Law, cybersecurity awareness has yielded more results in having organizations with critical information comply. Additionally, we have been able to deal with cybercrime through ccTLD policies that also recognize DNS Abuse in the
form of content abuse as well as IP infringements which are currently not ICANN’s remit.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;mso-fareast-language:EN-US">As it is, cybercrime and computer related acts, financial crime acts, and other acts that mention cybercrime developed by Member states already have penalties and to
have additional sanctions for me, would be counterproductive; Collaboration and cooperation key to achieving cyber resilience, and where need-be, harmonization could help as well, and to achieve this, those in charge of cybersecurity need to make all relevant
stakeholders aware of the importance of having cybersecurity capabilities, not impose.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;color:black;mso-fareast-language:EN-US">Warm Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;color:black">Ms. </span>
<span style="font-size:11.0pt;color:black">Angela Matlapeng </span><span style="font-size:11.0pt"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">EXCOM <excom-bounces@aftld.org> on behalf of barrack@aftld.org <barrack@aftld.org><br>
<b>Date: </b>Thursday, 09 June 2022 at 10:49<br>
<b>To: </b>excom@aftld.org <excom@aftld.org><br>
<b>Subject: </b>[Excom] Fwd: Re: [ccnso-council] CENTR Board letter to ICANN<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear EXCOM,<br>
<br>
What are your thoughts on this matter?<br>
<br>
Regards<br>
<br>
-------- Original Message --------<br>
Subject: Re: [ccnso-council] CENTR Board letter to ICANN<br>
Date: 2022-06-08 15:02<br>
From: Peter Van Roste via Ccnso-council <ccnso-council@icann.org><br>
To: Nick Wenban-Smith <Nick.Wenban-Smith@nominet.uk>, <br>
"ccNSO-Council@icann.org" <ccnso-council@icann.org><br>
Reply-To: Peter Van Roste <peter@centr.org><br>
<br>
Hi Nick,<br>
<br>
Thanks for forwarding.<br>
<br>
Luckily, this seems to be a EU specific issue.<br>
<br>
However, if there is an interest, I'd be happy to summarise at the next<br>
call or answer any individual questions people may have in the meantime.<br>
<br>
<br>
Hope to see many of you in The Hague!<br>
<br>
Peter<br>
<br>
Van: Ccnso-council <ccnso-council-bounces@icann.org> Namens Nick<br>
Wenban-Smith via Ccnso-council<br>
Verzonden: dinsdag 7 juni 2022 18:30<br>
Aan: ccNSO-Council@icann.org<br>
Onderwerp: [ccnso-council] FW: CENTR Board letter to ICANN<br>
<br>
FYI, is this something that could be discussed under AOB at council next<br>
week perhaps?<br>
<br>
From: fm-request@centrlists.org <fm-request@centrlists.org> On Behalf Of<br>
Peter Van Roste<br>
Sent: Tuesday, June 7, 2022 11:58 AM<br>
To: fm@centrlists.org<br>
Cc: leaders@centrlists.org<br>
Subject: [centr-fm] CENTR Board letter to ICANN<br>
<br>
Hi Everyone,<br>
<br>
As mentioned in a previous email, a Member had signalled that ICANN had<br>
reached out to European governments in the context of the NIS2<br>
negotiations.<br>
<br>
In that exchange, ICANN suggested that governments apply internationally<br>
approved policies and procedures on their national ccTLD.<br>
<br>
If successful, this outreach would result in ccTLDs having to abide by<br>
rules developed for gTLDs.<br>
<br>
Feedback from Members indicated that this was indeed not a stand-alone<br>
case.<br>
<br>
Wording I've seen, included indeed the encouragement for governments to<br>
establish internationally agreed policies regarding registrant data for<br>
ccTLDs.<br>
<br>
As many expressed during the Jamboree, this is worrisome and we need to<br>
fully understand the scope of this effort by ICANN.<br>
<br>
As a follow-up, the CENTR Board has sent a letter to the ICANN CEO to<br>
highlight this issue and request some clarifications.<br>
<br>
Full letter is attached, here are the clarifications requested:<br>
<br>
* How many European governments were approached in the context of this<br>
outreach?<br>
* On what grounds did ICANN suggest that governments should consider<br>
imposing regulation on ccTLDs?<br>
* How was this particular suggested amendment developed and what<br>
consultation process was followed?<br>
* On what basis does ICANN believe this specific message and related<br>
proactive outreach to governments is within its mandate?<br>
* Why did ICANN decide to advise governments on how to govern their<br>
national ccTLDs without consulting the ccTLD community?<br>
<br>
Most importantly, the Board asks ICANN to discuss how this issue can be<br>
avoided in the future and insists on synchronisation with the relevant<br>
ccTLD should there ever be a need for ICANN to discuss ccTLD regulations<br>
with a government.<br>
<br>
I will keep you posted of any follow-up.<br>
<br>
Best Regards,<br>
<br>
Peter<br>
<br>
Peter Van Roste<br>
<br>
General Manager<br>
<br>
CENTR - Belliardstraat 20, 1040 Brussels, Belgium<br>
<br>
tel +32 2 627 55 50 - direct +32 2 627 55 51<br>
<br>
www.centr.org [1] - Twitter [2] - Facebook [3] - LinkedIn [4] - Skype:<br>
pvanroste<br>
<br>
<br>
<br>
Links:<br>
------<br>
[1] <br>
<a href="https://protect-za.mimecast.com/s/Kg_SC8qgo6SvRxpCECPwS?domain=secure-web.cisco.com">http://secure-web.cisco.com/1VGztXNRCK7nLwageqXDot1U0BUJoO5jOHItWop9NEgn5wZ39EHq1d2U5AiLh8arHi8fFBQ5cIC1d4UbUPyTwFvaCl6uadojgUdlFQPsscGw4I8nZwtpwA5GzRolC39MulZjafVlWASueAxcc_U9TILMUU8q32B2t2ATHldNPuVh7tuS1NdrZLMJzfdwODnqunEmAU6JC2Ezn77zimQ68exgO_LeqnNxMMjlDRZaaqSPyJ9STGr_c-IhaR-wQbDl9/http%3A%2F%2Fwww.centr.org%2F</a><br>
[2] <a href="https://protect-za.mimecast.com/s/wiYRC98jpQC3BPEtQ14NY?domain=twitter.com">
https://twitter.com/CENTRnews</a><br>
[3] <a href="https://protect-za.mimecast.com/s/qLCqC0gM2Vuo3lwCpAxV8?domain=facebook.com">
https://www.facebook.com/centrnews</a><br>
[4] <a href="https://protect-za.mimecast.com/s/tRHgCg5yxLc02nZcxvkQe?domain=linkedin.com">
https://www.linkedin.com/company/centr</a><br>
_______________________________________________<br>
Ccnso-council mailing list<br>
Ccnso-council@icann.org<br>
<a href="https://protect-za.mimecast.com/s/UtDPCj2Bvqf5qkQiJBNN0?domain=mm.icann.org">https://mm.icann.org/mailman/listinfo/ccnso-council</a><br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your <br>
personal data for purposes of subscribing to this mailing list <br>
accordance with the ICANN Privacy Policy <br>
(<a href="https://protect-za.mimecast.com/s/zWKsCk5gwZcWQZztzaCuH?domain=icann.org">https://www.icann.org/privacy/policy</a>) and the website Terms of Service
<br>
(<a href="https://protect-za.mimecast.com/s/t3UDClO0v5inZDNh4smte?domain=icann.org">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link
<br>
above to change your membership status or configuration, including <br>
unsubscribing, setting digest-style delivery or disabling delivery <br>
altogether (e.g., for a vacation), and so on.<br>
_______________________________________________<br>
EXCOM mailing list<br>
EXCOM@aftld.org<br>
<a href="https://protect-za.mimecast.com/s/hpp6Cmwk2QcJnGNUlXaBB?domain=mail.aftld.org">https://mail.aftld.org/cgi-bin/mailman/listinfo/excom</a><o:p></o:p></span></p>
</div>
</body>
</html>