<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">+1 angela .. <div class="">Your Contribution is very relevant and in line with the situation of registries and the role that cctlds should play in Africa …The confusion between ccTLD and GTLD’s </div><div class=""><br class=""></div><div class="">I have made a french translation, and i believe it can be a common statement from @AfTLD </div><div class=""><br class=""></div><div class="">== FR ===</div><div class=""><div class="">Cher Barrack, merci pour ces informations.</div><div class=""> </div><div class="">Je ne pense pas que les ccTLD feraient bien d'être gouvernés comme les gTLD et imposer des politiques nationales n'est pas idéal. Encouragez plutôt les gouvernements à reconnaître les ccTLD dans leurs politiques nationales, et même à subventionner et à soutenir la gestion des ccTLD. Pour les gouvernements dotés de lois sur la protection des données qui ont des obligations en matière d'exactitude des données, le commissaire DPA concerné doit travailler avec les registres et être encouragé à adopter des moyens d'assurer l'exactitude des données du titulaire.</div><div class=""> </div><div class="">Ce avec quoi je semble être d'accord à propos du NIST2, c'est que les pays devraient déclarer/reconnaître les ccTLD en tant qu'infrastructures critiques. Dans mon pays, par exemple, tout ce qui est considéré comme une infrastructure nationale d'information critique est traité en priorité, notamment en assurant la continuité, la stabilité et la sécurité de cette infrastructure. Le rôle de l'unité de cybersécurité comprend la lutte contre la cybercriminalité perpétrée via le DNS ou sur le DNS.</div><div class=""> </div><div class="">Ce modèle n'est pas le seul à contourner. Les ccTLD peuvent collaborer avec les CIRT nationaux sans avoir recours à des mesures d'application strictes et à une supervision rigoureuse. Dans notre cas où il n'y a pas de loi sur la cybersécurité, la sensibilisation à la cybersécurité a donné plus de résultats en obligeant les organisations détenant des informations critiques à se conformer. De plus, nous avons été en mesure de lutter contre la cybercriminalité grâce à des politiques ccTLD qui reconnaissent également l'utilisation abusive du DNS sous la forme d'abus de contenu ainsi que les infractions à la propriété intellectuelle qui ne relèvent actuellement pas de la compétence de l'ICANN.</div><div class=""> </div><div class="">Dans l'état actuel des choses, les actes liés à la cybercriminalité et à l'informatique, les actes de criminalité financière et d'autres actes mentionnant la cybercriminalité élaborés par les États membres comportent déjà des sanctions et avoir des sanctions supplémentaires pour moi serait contre-productif ; La collaboration et la coopération sont essentielles pour atteindre la cyber-résilience et, le cas échéant, l'harmonisation pourrait également aider, et pour y parvenir, les responsables de la cybersécurité doivent sensibiliser toutes les parties prenantes concernées à l'importance de disposer de capacités de cybersécurité, et non d'imposer.</div><div class="">
<meta charset="UTF-8" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div style="orphans: 2; widows: 2;" class=""><div class=""><br class=""></div><div class=""><div class="WordSection1" style="page: WordSection1;"><div class=""><div class="" style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;"><b class=""><span lang="EN-GB" class="" style="font-size: 11pt;">Ms. </span><span class="" style="font-size: 11pt;">Angela Matlapeng (.BW)</span></b></div></div></div></div><div class=""><br class=""></div><div class="">Alex Corenthin</div><div class=""><div class="">Responsable Technique NIC Sénégal (<a href="http://www.nic.sn" class="">www.nicsenegal.sn</a>)</div><div class="">Centre Universitaire de Recherche et de Formation aux technologies de l’Internet (<a href="http://www.curi.sn" class="">www.curi.sn</a>)</div><div class="">Université Cheikh Anta Diop de Dakar (<a href="http://www.ucad.sn" class="">www.ucad.sn</a>)</div><div class="">BP 16370 Dakar-Fann (Senegal)</div><div class="">Tel : +221 338219190 / 776317776</div></div></div></div></div></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">Le 14 juin 2022 à 08:17, Angela Matlapeng <<a href="mailto:matlapeng@bocra.org.bw" class="">matlapeng@bocra.org.bw</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class="">Dear Barrack, thank you for this information.<o:p class=""></o:p></span></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class="">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 class=""></o:p></span></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class="">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 class=""></o:p></span></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class="">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 class=""></o:p></span></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class="">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 class=""></o:p></span></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div class=""><div class=""><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class="">Warm Regards,<o:p class=""></o:p></span></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span lang="EN-GB" style="font-size: 11pt;" class="">Ms.<span class="Apple-converted-space"> </span></span><span style="font-size: 11pt;" class="">Angela Matlapeng<span class="Apple-converted-space"> </span></span><span style="font-size: 11pt;" class=""><o:p class=""></o:p></span></div></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class=""><o:p class=""> </o:p></span></div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0cm 0cm;" class=""><p class="MsoNormal" style="margin: 0cm 0cm 12pt; font-size: 10pt; font-family: Calibri, sans-serif;"><b class=""><span style="font-size: 12pt;" class="">From:<span class="Apple-converted-space"> </span></span></b><span style="font-size: 12pt;" class="">EXCOM <<a href="mailto:excom-bounces@aftld.org" class="">excom-bounces@aftld.org</a>> on behalf of <a href="mailto:barrack@aftld.org" class="">barrack@aftld.org</a> <<a href="mailto:barrack@aftld.org" class="">barrack@aftld.org</a>><br class=""><b class="">Date:<span class="Apple-converted-space"> </span></b>Thursday, 09 June 2022 at 10:49<br class=""><b class="">To:<span class="Apple-converted-space"> </span></b><a href="mailto:excom@aftld.org" class="">excom@aftld.org</a> <<a href="mailto:excom@aftld.org" class="">excom@aftld.org</a>><br class=""><b class="">Subject:<span class="Apple-converted-space"> </span></b>[Excom] Fwd: Re: [ccnso-council] CENTR Board letter to ICANN<o:p class=""></o:p></span></p></div><div style="margin: 0cm; font-size: 10pt; font-family: Calibri, sans-serif;" class=""><span style="font-size: 11pt;" class="">Dear EXCOM,<br class=""><br class="">What are your thoughts on this matter?<br class=""><br class="">Regards<br class=""><br class="">-------- Original Message --------<br class="">Subject: Re: [ccnso-council] CENTR Board letter to ICANN<br class="">Date: 2022-06-08 15:02<br class="">From: Peter Van Roste via Ccnso-council <<a href="mailto:ccnso-council@icann.org" class="">ccnso-council@icann.org</a>><br class="">To: Nick Wenban-Smith <<a href="mailto:Nick.Wenban-Smith@nominet.uk" class="">Nick.Wenban-Smith@nominet.uk</a>>,<span class="Apple-converted-space"> </span><br class="">"<a href="mailto:ccNSO-Council@icann.org" class="">ccNSO-Council@icann.org</a>" <<a href="mailto:ccnso-council@icann.org" class="">ccnso-council@icann.org</a>><br class="">Reply-To: Peter Van Roste <<a href="mailto:peter@centr.org" class="">peter@centr.org</a>><br class=""><br class="">Hi Nick,<br class=""><br class="">Thanks for forwarding.<br class=""><br class="">Luckily, this seems to be a EU specific issue.<br class=""><br class="">However, if there is an interest, I'd be happy to summarise at the next<br class="">call or answer any individual questions people may have in the meantime.<br class=""><br class=""><br class="">Hope to see many of you in The Hague!<br class=""><br class="">Peter<br class=""><br class="">Van: Ccnso-council <<a href="mailto:ccnso-council-bounces@icann.org" class="">ccnso-council-bounces@icann.org</a>> Namens Nick<br class="">Wenban-Smith via Ccnso-council<br class="">Verzonden: dinsdag 7 juni 2022 18:30<br class="">Aan: <a href="mailto:ccNSO-Council@icann.org" class="">ccNSO-Council@icann.org</a><br class="">Onderwerp: [ccnso-council] FW: CENTR Board letter to ICANN<br class=""><br class="">FYI, is this something that could be discussed under AOB at council next<br class="">week perhaps?<br class=""><br class="">From: <a href="mailto:fm-request@centrlists.org" class="">fm-request@centrlists.org</a> <<a href="mailto:fm-request@centrlists.org" class="">fm-request@centrlists.org</a>> On Behalf Of<br class="">Peter Van Roste<br class="">Sent: Tuesday, June 7, 2022 11:58 AM<br class="">To: <a href="mailto:fm@centrlists.org" class="">fm@centrlists.org</a><br class="">Cc: <a href="mailto:leaders@centrlists.org" class="">leaders@centrlists.org</a><br class="">Subject: [centr-fm] CENTR Board letter to ICANN<br class=""><br class="">Hi Everyone,<br class=""><br class="">As mentioned in a previous email, a Member had signalled that ICANN had<br class="">reached out to European governments in the context of the NIS2<br class="">negotiations.<br class=""><br class="">In that exchange, ICANN suggested that governments apply internationally<br class="">approved policies and procedures on their national ccTLD.<br class=""><br class="">If successful, this outreach would result in ccTLDs having to abide by<br class="">rules developed for gTLDs.<br class=""><br class="">Feedback from Members indicated that this was indeed not a stand-alone<br class="">case.<br class=""><br class="">Wording I've seen, included indeed the encouragement for governments to<br class="">establish internationally agreed policies regarding registrant data for<br class="">ccTLDs.<br class=""><br class="">As many expressed during the Jamboree, this is worrisome and we need to<br class="">fully understand the scope of this effort by ICANN.<br class=""><br class="">As a follow-up, the CENTR Board has sent a letter to the ICANN CEO to<br class="">highlight this issue and request some clarifications.<br class=""><br class="">Full letter is attached, here are the clarifications requested:<br class=""><br class="">* How many European governments were approached in the context of this<br class="">outreach?<br class="">* On what grounds did ICANN suggest that governments should consider<br class="">imposing regulation on ccTLDs?<br class="">* How was this particular suggested amendment developed and what<br class="">consultation process was followed?<br class="">* On what basis does ICANN believe this specific message and related<br class="">proactive outreach to governments is within its mandate?<br class="">* Why did ICANN decide to advise governments on how to govern their<br class="">national ccTLDs without consulting the ccTLD community?<br class=""><br class="">Most importantly, the Board asks ICANN to discuss how this issue can be<br class="">avoided in the future and insists on synchronisation with the relevant<br class="">ccTLD should there ever be a need for ICANN to discuss ccTLD regulations<br class="">with a government.<br class=""><br class="">I will keep you posted of any follow-up.<br class=""><br class="">Best Regards,<br class=""><br class="">Peter<br class=""><br class="">Peter Van Roste<br class=""><br class="">General Manager<br class=""><br class="">CENTR - Belliardstraat 20, 1040 Brussels, Belgium<br class=""><br class="">tel +32 2 627 55 50 - direct +32 2 627 55 51<br class=""><br class=""><a href="http://www.centr.org" class="">www.centr.org</a> [1] - Twitter [2] - Facebook [3] - LinkedIn [4] - Skype:<br class="">pvanroste<br class=""><br class=""><br class=""><br class="">Links:<br class="">------<br class="">[1]<span class="Apple-converted-space"> </span><br class=""><a href="https://protect-za.mimecast.com/s/Kg_SC8qgo6SvRxpCECPwS?domain=secure-web.cisco.com" style="color: blue; text-decoration: underline;" class="">http://secure-web.cisco.com/1VGztXNRCK7nLwageqXDot1U0BUJoO5jOHItWop9NEgn5wZ39EHq1d2U5AiLh8arHi8fFBQ5cIC1d4UbUPyTwFvaCl6uadojgUdlFQPsscGw4I8nZwtpwA5GzRolC39MulZjafVlWASueAxcc_U9TILMUU8q32B2t2ATHldNPuVh7tuS1NdrZLMJzfdwODnqunEmAU6JC2Ezn77zimQ68exgO_LeqnNxMMjlDRZaaqSPyJ9STGr_c-IhaR-wQbDl9/http%3A%2F%2Fwww.centr.org%2F</a><br class="">[2]<span class="Apple-converted-space"> </span><a href="https://protect-za.mimecast.com/s/wiYRC98jpQC3BPEtQ14NY?domain=twitter.com" style="color: blue; text-decoration: underline;" class="">https://twitter.com/CENTRnews</a><br class="">[3]<span class="Apple-converted-space"> </span><a href="https://protect-za.mimecast.com/s/qLCqC0gM2Vuo3lwCpAxV8?domain=facebook.com" style="color: blue; text-decoration: underline;" class="">https://www.facebook.com/centrnews</a><br class="">[4]<span class="Apple-converted-space"> </span><a href="https://protect-za.mimecast.com/s/tRHgCg5yxLc02nZcxvkQe?domain=linkedin.com" style="color: blue; text-decoration: underline;" class="">https://www.linkedin.com/company/centr</a><br class="">_______________________________________________<br class="">Ccnso-council mailing list<br class=""><a href="mailto:Ccnso-council@icann.org" class="">Ccnso-council@icann.org</a><br class=""><a href="https://protect-za.mimecast.com/s/UtDPCj2Bvqf5qkQiJBNN0?domain=mm.icann.org" style="color: blue; text-decoration: underline;" class="">https://mm.icann.org/mailman/listinfo/ccnso-council</a><br class="">_______________________________________________<br class="">By submitting your personal data, you consent to the processing of your<span class="Apple-converted-space"> </span><br class="">personal data for purposes of subscribing to this mailing list<span class="Apple-converted-space"> </span><br class="">accordance with the ICANN Privacy Policy<span class="Apple-converted-space"> </span><br class="">(<a href="https://protect-za.mimecast.com/s/zWKsCk5gwZcWQZztzaCuH?domain=icann.org" style="color: blue; text-decoration: underline;" class="">https://www.icann.org/privacy/policy</a>) and the website Terms of Service<span class="Apple-converted-space"> </span><br class="">(<a href="https://protect-za.mimecast.com/s/t3UDClO0v5inZDNh4smte?domain=icann.org" style="color: blue; text-decoration: underline;" class="">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link<span class="Apple-converted-space"> </span><br class="">above to change your membership status or configuration, including<span class="Apple-converted-space"> </span><br class="">unsubscribing, setting digest-style delivery or disabling delivery<span class="Apple-converted-space"> </span><br class="">altogether (e.g., for a vacation), and so on.<br class="">_______________________________________________<br class="">EXCOM mailing list<br class="">EXCOM@aftld.org<br class=""><a href="https://protect-za.mimecast.com/s/hpp6Cmwk2QcJnGNUlXaBB?domain=mail.aftld.org" style="color: blue; text-decoration: underline;" class="">https://mail.aftld.org/cgi-bin/mailman/listinfo/excom</a><o:p class=""></o:p></span></div></div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">_______________________________________________</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">EXCOM mailing list</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="mailto:EXCOM@aftld.org" style="color: blue; text-decoration: underline; font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">EXCOM@aftld.org</a><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><a href="https://mail.aftld.org/cgi-bin/mailman/listinfo/excom" style="color: blue; text-decoration: underline; font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class="">https://mail.aftld.org/cgi-bin/mailman/listinfo/excom</a></div></blockquote></div><br class=""></div></body></html>