<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>I think technically no, but we as the GNSO do need to 'defend our turf' for want of a better phrase. Generic names should be defended as the exclusive purview of the GNSO, we can reach out to cc community on how to better run those, but for the purposes
of policy that is our domain and we need to defend that.</p>
<p><br>
</p>
<p>-James</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Ncuc-discuss <ncuc-discuss-bounces@lists.ncuc.org> on behalf of Niels ten Oever <lists@digitaldissidents.org><br>
<b>Sent:</b> 29 June 2017 13:59:49<br>
<b>To:</b> farzaneh badii<br>
<b>Cc:</b> NCUC-discuss<br>
<b>Subject:</b> Re: [NCUC-DISCUSS] Cross Community Discussion/ Geographic Names at the Top Level Session II</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Do we think this is a bad thing per se?<br>
<br>
Maybe ccTLDs are better at building TLDs than the ppl in the gTLD space,<br>
especially if you look at the outcomes of the last gTLD round (largely<br>
spam and defensive registration).<br>
<br>
Best,<br>
<br>
Niels<br>
<br>
On 06/29/2017 02:34 PM, farzaneh badii wrote:<br>
> Hi <br>
> <br>
> This is about procedures for new gtlds and does not affect the already<br>
> existing ones.<br>
> <br>
> The issue is some in GAC and CCNSO want to claim any name that is<br>
> remotely related to the sovereign. The danger is that, they can claim<br>
> some generic names too that happen to relate to a sovereign. If they are<br>
> delegated the names, they will have whatever rule the sovereign wants<br>
> for domain registration. It is certainly a landgrab. The plan is to grab<br>
> as much as they can from gTLD space and move it to ccTLD space.<br>
> <br>
> <br>
> <br>
> Farzaneh<br>
> <br>
> On Thu, Jun 29, 2017 at 8:07 AM, Niels ten Oever<br>
> <lists@digitaldissidents.org <<a href="mailto:lists@digitaldissidents.org">mailto:lists@digitaldissidents.org</a>>> wrote:<br>
> <br>
> I liked the presentation of Jaap Akkerhuis when he presented to the GAC<br>
> about this issue. The ISO list has a clear hierarchy, but this is not<br>
> present in the DNS. There is a Berlin in Wisconsin, Idaho, Ohio, New<br>
> Jersey, Maryland and Germany. Who should get it?<br>
> <br>
> And what happens to already allocated geonames such as .amsterdam,<br>
> .berlin, .friesland, etc?<br>
> <br>
> The GAC has no model to solve this whatsoever, so am not so clear what<br>
> they are pushing for. Or do they want to offer priority in the auction<br>
> process to geographies? I would not necessarily be against that. Or did<br>
> I miss something?<br>
> <br>
> Cheers,<br>
> <br>
> Niels<br>
> <br>
> <br>
> <br>
> On 06/29/2017 01:49 PM, hfaiedh ines wrote:<br>
> > We are currently attending the session. If you have any opinions or<br>
> > questions you would like me to transmit please don't hesitate.<br>
> ><br>
> > On Jun 29, 2017 11:05, "Farell Folly" <farellfolly@gmail.com <<a href="mailto:farellfolly@gmail.com">mailto:farellfolly@gmail.com</a>><br>
> > <<a href=""></a>mailto:farellfolly@gmail.com <<a href="mailto:farellfolly@gmail.com">mailto:farellfolly@gmail.com</a>>>> wrote:<br>
> ><br>
> > Dear Farzaneh,<br>
> ><br>
> > You are totally right.. I attended the 1st meeting few days ago and<br>
> > I will attend the one of the afternoon. Discussions are very<br>
> > serious. I would like to work on that.<br>
> ><br>
> ><br>
> ><br>
> > Regards<br>
> > @__f_f__<br>
> ><br>
> > Computer Security | Internet of Things<br>
> > <a href="https://www.linkedin.com/in/farellf">https://www.linkedin.com/in/farellf</a><br>
> <<a href="https://www.linkedin.com/in/farellf">https://www.linkedin.com/in/farellf</a>><br>
> > <<a href=""></a>https://www.linkedin.com/in/farellf<br>
> <<a href="https://www.linkedin.com/in/farellf">https://www.linkedin.com/in/farellf</a>>><br>
> > ________________________________.<br>
> > Mail sent from my mobile phone. Excuse for brievety.<br>
> ><br>
> > Le 29 juin 2017 10:21, "farzaneh badii" <farzaneh.badii@gmail.com <<a href="mailto:farzaneh.badii@gmail.com">mailto:farzaneh.badii@gmail.com</a>><br>
> > <<a href=""></a>mailto:farzaneh.badii@gmail.com<br>
> <<a href="mailto:farzaneh.badii@gmail.com">mailto:farzaneh.badii@gmail.com</a>>>> a ¨¦crit :<br>
> ><br>
> > Dear all,<br>
> ><br>
> > I think as the noncommercial group we have not paid enough<br>
> > attention to the issue of Geographic names at the top level.By<br>
> > claiming sovereignty over Geo names, governments will<br>
> claim the<br>
> > Geo names. If we do not wake up and get active, we will not be<br>
> > able to rescue the generic names that happen to be Geo<br>
> names as<br>
> > well.<br>
> ><br>
> ><br>
> > Today there will be a cross-community session and they will<br>
> > discuss various important issues but some of the questions are<br>
> > important and I recommend NCUC members attend the session. I<br>
> > have attached the agenda and some of the questions that<br>
> will be<br>
> > addressed are copied below:<br>
> ><br>
> > 17:00 Key Geo Names Issues to Address in the PDP<br>
> ><br>
> > 1. What makes a string a ¡°geographic name¡±?<br>
> ><br>
> > 2. When can a geographic name:<br>
> ><br>
> > ¡ñ Be applied for;<br>
> ><br>
> > ¡ñ Be delegated to a particular applicant?<br>
> ><br>
> > 3. If there are simultaneous applications for a geographic<br>
> name,<br>
> > how should this be<br>
> ><br>
> > resolved?<br>
> ><br>
> > 4. How could ¡°geographic use¡± be distinguished from<br>
> ¡°generic use¡±?<br>
> ><br>
> > 5. How can commitments to restrict a TLD to non-geographic use<br>
> > be monitored and enforced?<br>
> ><br>
> > Best<br>
> ><br>
> ><br>
> > Farzaneh<br>
> ><br>
> > _______________________________________________<br>
> > Ncuc-discuss mailing list<br>
> > Ncuc-discuss@lists.ncuc.org<br>
> <<a href="mailto:Ncuc-discuss@lists.ncuc.org">mailto:Ncuc-discuss@lists.ncuc.org</a>><br>
> <<a href=""></a>mailto:Ncuc-discuss@lists.ncuc.org<br>
> <<a href="mailto:Ncuc-discuss@lists.ncuc.org">mailto:Ncuc-discuss@lists.ncuc.org</a>>><br>
> > <br>
> <a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a><br>
> <<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a>><br>
> > <<a href=""></a>http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss<br>
> <<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a>>><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Ncuc-discuss mailing list<br>
> > Ncuc-discuss@lists.ncuc.org<br>
> <<a href="mailto:Ncuc-discuss@lists.ncuc.org">mailto:Ncuc-discuss@lists.ncuc.org</a>><br>
> <<a href=""></a>mailto:Ncuc-discuss@lists.ncuc.org<br>
> <<a href="mailto:Ncuc-discuss@lists.ncuc.org">mailto:Ncuc-discuss@lists.ncuc.org</a>>><br>
> > <a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">
http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a><br>
> <<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a>><br>
> > <<a href=""></a>http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss<br>
> <<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a>>><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Ncuc-discuss mailing list<br>
> > Ncuc-discuss@lists.ncuc.org <<a href="mailto:Ncuc-discuss@lists.ncuc.org">mailto:Ncuc-discuss@lists.ncuc.org</a>><br>
> > <a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a><br>
> <<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a>><br>
> ><br>
> <br>
> --<br>
> Niels ten Oever<br>
> Head of Digital<br>
> <br>
> Article 19<br>
> <a href="http://www.article19.org">www.article19.org</a> <<a href="http://www.article19.org">http://www.article19.org</a>><br>
> <br>
> PGP fingerprint 8D9F C567 BEE4 A431 56C4<br>
> 678B 08B5 A0F2 636D 68E9<br>
> _______________________________________________<br>
> Ncuc-discuss mailing list<br>
> Ncuc-discuss@lists.ncuc.org <<a href="mailto:Ncuc-discuss@lists.ncuc.org">mailto:Ncuc-discuss@lists.ncuc.org</a>><br>
> <a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a><br>
> <<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a>><br>
> <br>
> <br>
<br>
-- <br>
Niels ten Oever<br>
Head of Digital<br>
<br>
Article 19<br>
<a href="http://www.article19.org">www.article19.org</a><br>
<br>
PGP fingerprint 8D9F C567 BEE4 A431 56C4<br>
678B 08B5 A0F2 636D 68E9<br>
_______________________________________________<br>
Ncuc-discuss mailing list<br>
Ncuc-discuss@lists.ncuc.org<br>
<a href="http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a><br>
</div>
</span></font>
</body>
</html>