[gnso-gac-closed-generics] Additional context and background for closed generic gTLDs

[Kathy Kleiman]

Jeff,

If we don't resolve the competition, consumer confusion and violation of 
trademark principle/law problems raised by governments, large and small 
entities, and individuals around the world about closed generic gTLDs in 
the first round, then how do we reach a public interest solution?  It's 
not "rehashing old arguments," it's getting to the heart of the matter.

No one is saying we cannot reach the goal, but GAC members and the 
public told us long ago what we must consider to get there.

Best, Kathy

On 11/7/2022 1:04 AM, Jeff Neuman wrote:
> Kathy,
>
> While I appreciate your advocacy piece from an organization called the 
> Domain Name Rights Coalition (which I admit I am not familiar with), 
> all of the sources referenced were thoroughly discussed over the many 
> years of the SubPro Working Group.  Our job is very narrow and does 
> not include revisiting all of the work done in SubPro, but rather to 
> discuss whether a compromise proposal can be presented to the GNSO and 
> the community for policy development.
>
> Your position opposing Closed Generics is well documented.  But with 
> all due respect, rehashing all of the old arguments for or against are 
> counterproductive at best.  We have agreed to a facilitator and I 
> would propose that we follow her lead if we are to make any progress 
> at all.
>
> Our job is to be objective in assessing potential compromises.  I fear 
> that advocating either completely for or completely against having 
> Closed Generics will lessen the likelihood of success of the group.
>
> We have existing GAC Advice that states the Closed Generics must 
> "serve a public interest goal."  It does not state that they should be 
> prohibited, nor does its state that it should be allowed without 
> restriction.  I would like to hear from the facilitator on how to proceed.
>
> Sincerely,
>
>
> Jeffrey J. Neuman
> Founder & CEO
> JJN Solutions, LLC
> Jeff at JJNSolutions.com
> +1.202.549.5079
> Http://www.jjnsolutions.com
>
>
> ------------------------------------------------------------------------
> *From:* gnso-gac-closed-generics 
> <gnso-gac-closed-generics-bounces at icann.org> on behalf of Kathy 
> Kleiman <Kathy at KathyKleiman.com>
> *Sent:* Friday, November 4, 2022 4:51 PM
> *To:* gnso-gac-closed-generics at icann.org 
> <gnso-gac-closed-generics at icann.org>
> *Subject:* [gnso-gac-closed-generics] Additional context and 
> background for closed generic gTLDs
>
> Hi All,
>
> In Kuala Lumpur, at the Public Forum, I shared my concern that we need 
> more background and context about closed generic issues raised by 
> governments and commenters in 2012 and 2013. Afterwards, others at the 
> Public Forum agreed and shared their hope that more information about 
> Early Warnings and community comments would be compiled.
>
> To that end, some members of the community prepared a paper with 
> additional background and context- a compendium of Early Warnings and 
> comments on closed generic gTLDs in the first round. Please see attached.
>
> Best regards,
>
> Kathy
>
>
> _______________________________________________
> gnso-gac-closed-generics mailing list
> gnso-gac-closed-generics at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/gnso-gac-closed-generics/attachments/20221107/4092526b/attachment.html>