Discard spec 12 in new gtld registries, the so called "community new gtld" clause

David Cake dave at DAVECAKE.NET
Mon Feb 21 22:52:27 EET 2022


Great blog that lays out the issues very well. 

I now it is only part of the issue, but I am personally becoming quite shocked at how slowly ICANN moves towards implementation of the policies that the community works so hard on. Would ICANN getting an OFAC licence significantly improve this situation?

I agree with the issue with Spec 12 exacerbating the problem significantly, though it seems like it would not fix it entirely. Do you think there is significant community support for removing Spec 12 entirely, or would there need to be a review or replacement process?

David

> On 18 Feb 2022, at 2:40 am, farzaneh badii <farzaneh.badii at GMAIL.COM> wrote:
> 
> It turns out that the new gTLDs can't or won't provide their services to ordinary people in sanctioned countries mainly because of spec 12. Spec 12 has been an awfully controversial clause. One problem that it raises is the issue of sanctions.
> 
> How can we go about this, NCSG? 
> 
> Here is a blog that I wrote about the issue: https://digitalmedusa.org/oneworld-someinternet-new-gtld-registries-and-sanctioned-countries/ <https://digitalmedusa.org/oneworld-someinternet-new-gtld-registries-and-sanctioned-countries/>
> 
> P.S. another policy that can block access for ordinary registrants in sanctioned countries is thick WHOIS! we need to stop coming up with policies that goes against ICANN mission which is global coordination and not global elimination. 
> 
> Best regards, 
> 
> 
> Farzaneh 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-discuss/attachments/20220221/6397c62a/attachment.htm>


More information about the Ncsg-discuss mailing list