[Gnso-newgtld-wg] Current Thinking on Closed Generics

Alan Greenberg alan.greenberg at mcgill.ca
Mon Jul 27 14:50:23 UTC 2020 

Anne, with regard to your categorization of the 
proposal George submitted, I have already said 
that in theory, this COULD be done with an open 
but highly restricted TLD. It would mean 
venturing into a level of control over not just 
who the registrant is, but rigid control over 
what content they could present and how it is 
structured - it would not be easy to do.

Community status is really just a mechanism for 
giving priority if there is contention. Most city 
TLDs are community TLDs, some were not. It does 
not necessarily alter what the TLD does or how it 
does it. A closed PI TLD could in theory also be a Community TLD...

Alan


At 2020-07-27 12:01 AM, Aikman-Scalese, Anne wrote:

>As I understand it, Jeff does not see an 
>opportunity for consensus without obtaining 
>further public comment on the issue of Closed 
>Generics.  I believe that by definition, a 
>Closed Generic is one where only the applicant 
>and its strictly defined affiliates may occupy the domains.
>
>The WG has recently been to GNSO Council with a 
>request for a new timeline, which was approved. 
>That is where Jeff is getting his deadline.  I tend to agree with Jeff that:
>(a) further discussion by the WG at this time will not achieve consensus
>(b) additional public comment on the various 
>proposals (and anything new that comes in during 
>the next week) will better inform further 
>attempts of the WG to achieve consensus.
>
>Regarding the discussion on the public interest, 
>I don’t think every gTLD is required to serve 
>the public interest.  There is a general 
>assumption (which may be questioned of course) 
>that competition is fostered by the program 
>generally and that this will inure to the 
>benefit of consumers.  The topic of Closed 
>Generics serving a public interest is a separate 
>one entirely, due to standing GAC Consensus Advice.
>
>Personally, and certainly not speaking on behalf 
>of the IPC, I don’t think a long discussion 
>about why the Board should override GAC Advice 
>is a good use of our time.  Nor do I think the 
>proposal from the small group led by George is 
>actually a proposal for a Closed Generic.  It 
>appears to me to be more of a proposal that is 
>community and/or eligibility based.
>
>For the above reasons and subject to Monday’s 
>discussion, I support Jeff’s proposed approach 
>to the issue for purposes of the draft Final Report.
>Anne
>
>From: Gnso-newgtld-wg 
><gnso-newgtld-wg-bounces at icann.org> On Behalf Of 
>mail at christopherwilkinson.eu CW
>Sent: Sunday, July 26, 2020 12:13 PM
>To: Jeff Neuman <jeff at jjnsolutions.com>; gnso-newgtld-wg at icann.org
>Subject: Re: [Gnso-newgtld-wg] Current Thinking on Closed Generics
>
>[EXTERNAL]
>
>----------
>Dear Jeff:
>
>Allow me just a quick response.
>
>1.  The proposals that we have received merit a 
>full discussion by the PDP. I think that time should be made available.
>
>2.  Your latest communication seems to me to 
>ignore the current and prospective economic 
>situation arising from the global pandemic.
>
> > 
 we could get much further behind and 
> ultimately not meet our end of year date.
>
>On the contrary, there should now be no urgency. 
>If the objective is to successfully launch 
>another large opening of the DNS, then that 
>should be done in the context of substantial 
>international economic expansion. Which is 
>apparently not currently on the cards.
>
>I assume that Staff and Co-Chairs have 
>investigated the relationships between the macro 
>economic situation and the relative success of 
>introducing large numbers of new TLDs.-
>
>3.  Although I may have missed something, I do 
>not know where the 'end of year date' comes from.
>Nor the current twice a week PDP schedule. 
>Indeed, that has not brought matters forward, 
>rather just made more time for discussion.
>
>Just a few thoughts
>
>Best regards
>
>CW
>

>
>
>
>
>
>
>we could get much further behind and ultimately 
>not meet our end of year date.de julio de 2020 a 
>las 18:30 Jeff Neuman 
><<mailto:jeff at jjnsolutions.com>jeff at jjnsolutions.com> escribió:
>
>All,
>
>
>
>I wanted to throw something out for 
>consideration by the group in the interests of 
>getting to the draft final report.  We are 
>already a week or two behind and I am worried 
>that we could get much further behind and 
>ultimately not meet our end of year date.  So, I 
>am laying this out on the line as a 
>proposal.  This is not a definitive plan, but something to think about.
>
>
>For the Draft final report, we state that there 
>is No Agreement on the issue of Closed Generics 
>and keep the paragraph in the draft the way it is today.
>In addition to the text that is already in 
>there, we now have two proposals, one from 
>George et al., and one from Kurt, et al.  What 
>if we give everyone an additional week to come 
>up with any proposals on Closed generics they 
>would like to float out for public comment.
>We publish those proposals for public comment 
>being very specific that they are individual 
>proposals and do not have any level of support 
>within the working group.  We may even not want 
>to attach names to the proposal so as to try not 
>and bias the comments we get in.  We can of course discuss this last point.
>We solicit comments on all of the proposals.
>While the public comment period is going on, we 
>continue to discuss the proposals as a Working 
>Group to see if we can reach any sort of consensus on this issue.
>We make it very clear in our report that absent 
>reaching consensus within the Working Group on 
>any of these proposals, taking into 
>consideration public comments of course, that in 
>the final report, we will go with the language 
>that is in the Draft Final Report (without any 
>of the individual proposals); namely, No Agreement.
>
>
>Why do this?
>We need to be realistic with ourselves as well 
>as the community that to date there is no agreement on how to move forward.
>We also need to give the community a chance to 
>look at the various options people in the 
>working group have proposed so that they can 
>think about these as well (regardless of whether 
>one group of people like it or not).
>At the end of the day, we will need to 
>demonstrate to the GNSO Council and the Board 
>that we attempted every possible way to reach consensus on a compromise.
>And finally there are 40+ other topics that we 
>have come to some sort of final resolution on 
>and there is no reason to delay everything even more for these last few issues.
>
>
>What does this mean for us?
>
>i)                    On the call on Monday, we 
>will discuss this path of moving forward.
>
>ii)                   This means that we do not 
>need to use up time on the call discussing the 
>two existing proposals for which I am sure we 
>could spend hours going back and forth and 
>likely end up on Monday exactly where we are now.
>
>iii)                 It also means that others 
>have a week to submit their own proposals.  I 
>personally have some ideas that I may put into a 
>proposal that I may submit (not as a co-chair, 
>but personally speaking).   This may give us 
>another reason to not attach names to the 
>proposals so that if I submitted a proposal it 
>wouldn’t be associated with the “co-chair”.
>
>iv)                 We work on finalizing the 
>draft report sections on Predictability and 
>Mechanisms of Last Resort this week as well as 
>the Preamble and “Cant Live With” Package 7.
>
>v)                   This would enable us to stay only a week or to behind.
>
>
>
>Thoughts?
>
>
>
>[]
>
>
>
>
>[]
>
>
>Jeffrey J. Neuman
>
>Founder & CEO
>
>JJN Solutions, LLC
>
>p: +1.202.549.5079
>
>E: <mailto:jeff at jjnsolutions.com>jeff at jjnsolutions.com
>
>http://jjnsolutions.com
>
>
>
>
>
>
>
>_______________________________________________
>Gnso-newgtld-wg mailing list
><mailto:Gnso-newgtld-wg at icann.org>Gnso-newgtld-wg at icann.org
>https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg
>_______________________________________________
>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>https://www.icann.org/privacy/policy) 
>and the website Terms of Service 
>(<https://www.icann.org/privacy/tos>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.
>
>
>
>
>
>----------
>
>This message and any attachments are intended 
>only for the use of the individual or entity to 
>which they are addressed. If the reader of this 
>message or an attachment is not the intended 
>recipient or the employee or agent responsible 
>for delivering the message or attachment to the 
>intended recipient you are hereby notified that 
>any dissemination, distribution or copying of 
>this message or any attachment is strictly 
>prohibited. If you have received this 
>communication in error, please notify us 
>immediately by replying to the sender. The 
>information transmitted in this message and any 
>attachments may be privileged, is intended only 
>for the personal and confidential use of the 
>intended recipients, and is covered by the 
>Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.
>
>
>_______________________________________________
>Gnso-newgtld-wg mailing list
>Gnso-newgtld-wg at icann.org
>https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg
>_______________________________________________
>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: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20200727/6ceb9126/attachment-0001.html>

More information about the Gnso-newgtld-wg mailing list