[Gnso-newgtld-wg] Some points on our proposal and "closed generics"
Jeff Neuman
jeff at jjnsolutions.com
Mon Jul 27 14:49:29 UTC 2020
We will spend at least the last 30 minutes of today’s call on Closed Generics. I would like to get us to finish up Predictability first.
[cid:image002.png at 01D66403.9D7AF990]
Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
p: +1.202.549.5079
E: jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>
http://jjnsolutions.com
From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces at icann.org> On Behalf Of George Sadowsky
Sent: Monday, July 27, 2020 10:40 AM
To: gnso-newgtld-wg at icann.org
Subject: [Gnso-newgtld-wg] Some points on our proposal and "closed generics"
Several points:
1. I had thought that it was decided that if we could produce a paper on closed generics in a week, that we would then be able to spend some time describing it to the group. We weren't able to do that at the time because we had not really formulate it sufficiently well for discussion. The proposed agenda takes this offer away.
In the interest of fairness and the previous agreement, we ask for a short period of time to make several points regarding the proposal and the process. My colleagues and I therefore ask for 10+ minutes, more or less, to make a number of points, and then move on. Closed generics are not the only important item on the agenda.
2. It appears that we now have three alternatives to present to the community for comment: (1) no restriction on closed generics; (2) our proposal for closed public interest generics; and (3) take no action,, leaving the issue in an undetermined state. perhaps the current status quo (whatever that is). The first two are buttressed by recent documents; I don't know if there has been a more formal defense of the third alternative. Rather than saying that we have not been abe to reach agreement, we think that it would be more helpful that while we have reached no agreement, we have been able to identify three possible results, and that most WG members appear to gravitate to one of these positions. This provides more structure for the community's reactions and discussions.
3. We believe that names should be attached to proposals. First, they are easily discoverable. Second, the stakeholder and commercial affiliations of the authors provide useful information for judging the proposals. Third, what is the argument for hiding them and does it make sense in this community context where to a large extent we know each other and attempt to work cooperatively? This is not a blind wine tasting.
4. My sense is that the specific details of the alternative proposals may be useful to indicate their feasibility, but that the main difference between them is contained in the goals and values that define them. These discussions are the provenance of the whole of ICANN, and in fact of an even broader set of actors, and any insights that we may have should be propagated to the level of public comment including the entire community. Given ICANN's role as a Public Benefit Corporation in the State of California, it's worth noting that the Attorney General of the State also has, and has recently voiced, a concern regarding ICANN behavior that could go against the citizens of that state with regard to non-adherence to ICANN's public benefit goal, so that the concerns of general goals and decisions of ICANN can go well beyond the level of community public comment.
5. I share Anne's concern regarding whether the domains we propose are really "closed" in a traditional sense. They are a hybrid of sorts, and therefore do need to be administered and processed differently. For my colleagues, it matters less what we cal them than that we protect generic strings from commercial exploitation when they have the real possibility of significant commercial exploitation when their semantic content makes them rich targets, and when their intrinsic value for the public interest is thereby thwarted.
Thanks for reading.
George
On Jul 27, 2020, at 6:29 AM, Alexander Schubert <alexander at schubert.berlin<mailto:alexander at schubert.berlin>> wrote:
Hi,
I agree. But since we can't even find concensus WITHIN this WG on the issue whether the allocation of closed generics (because of standing GAC advice and/or the bylaws) should follow a public interest goal - and how far reaching this should be in the realm of this new gTLD program:
Shouldn't we first lay the groundwork on which we then later can build on?
We are soon to publish a draft to the public and garner their input. And I fully agree that at this point of time we are in no position to advance concrete policy recommendation proposals.
But we could sample two general proposals for the community to elaborate on that would establish a base as to how the actual "picket fence" of "public interest" should look like. Not policy but guidelines for what the basis of our policies should be.
E.g.:
1) "Generally generic keyword based gTLDs should be available for registration of domains to a wider public. The benefit of operation as restricted or single registrant registry would have to outweigh the unavailability of domains to all or part of the community. The registry operator will have to convince the community that his operating model justifies making domains unavailable to some within or even all the community."
2) "There is an endless amount of strings available - and as any single registrant use is potentially fostering innovation just the prospect of innovation in and of itself justifies single registrant registries."
Btw: Picket Fence 1) is the basis for community gTLDs and restricted TLDs like .bank: 99.9999% of entities are denied to register a .bank domain: because it is indeed in the public interest that you end up on a bank's website if you visit a .bank domain. Yes that denies companies who produce or sell banks (seating, power banks, etc) to use .bank domains - but overall the benefits that the restriction generates outweighs the unavailability.
Let's the community decide to what degree the new gTLD program should be bound to the public interest. Right now would be an awesome moment in time to garner input on this topic from the community. We are acting ON BEHALF of the community - so why second guessing what the community wishes - just ask.
In case the community choses 2): we are done. Any string can be applied for as closed generic. If the community choses 1): we have finally very clear guidelines. Even when we still can't agree on a concrete policy we can put that portion into the applicant guidebook - and warn folks:
"In 2012 closed generics were barred from advancing. This program follows a clear public interest goal. If you restrict registrations just to yourself and affiliates then there shouldn't be a general expectation that your application will be approved."
We owe it to new entrants that they are warned. In 2012 we had mostly ICANN insiders applying (consulting). In the next round this will dramatically change.
See you later in the call.
Alexander
Sent from my Samsung device
-------- Original message --------
From: "Aikman-Scalese, Anne" <AAikman at lrrc.com<mailto:AAikman at lrrc.com>>
Date: 7/27/20 07:01 (GMT+02:00)
To: "mail at christopherwilkinson.eu<mailto:mail at christopherwilkinson.eu> CW" <mail at christopherwilkinson.eu<mailto:mail at christopherwilkinson.eu>>, Jeff Neuman <jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>>, gnso-newgtld-wg at icann.org<mailto:gnso-newgtld-wg at icann.org>
Subject: Re: [Gnso-newgtld-wg] Current Thinking on Closed Generics
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<mailto:gnso-newgtld-wg-bounces at icann.org>> On Behalf Of mail at christopherwilkinson.eu<mailto:mail at christopherwilkinson.eu> CW
Sent: Sunday, July 26, 2020 12:13 PM
To: Jeff Neuman <jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>>; gnso-newgtld-wg at icann.org<mailto: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<http://date.de> julio de 2020 a las 18:30 Jeff Neuman <jeff at jjnsolutions.com<mailto: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.
1. 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.
2. 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.
3. 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.
4. We solicit comments on all of the proposals.
5. 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.
6. 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?
1. We need to be realistic with ourselves as well as the community that to date there is no agreement on how to move forward.
2. 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).
3. 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.
4. 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?
[cid:image003.png at 01D6638F.003B0770]
Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
p: +1.202.549.5079
E: jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>
http://jjnsolutions.com<http://jjnsolutions.com/>
_______________________________________________
Gnso-newgtld-wg mailing list
Gnso-newgtld-wg at icann.org<mailto: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.
________________________________
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<mailto: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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
George Sadowsky Residence tel: +1.301.968.4325
8300 Burdette Road, Apt B-472 Mobile: +1.202.415.1933
Bethesda MD 20817-2831 USA Skype: sadowsky
george.sadowsky at gmail.com<mailto:george.sadowsky at gmail.com> http://www.georgesadowsky.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20200727/304a86f1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 113 bytes
Desc: image001.png
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20200727/304a86f1/image001-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 89681 bytes
Desc: image002.png
URL: <http://mm.icann.org/pipermail/gnso-newgtld-wg/attachments/20200727/304a86f1/image002-0001.png>
More information about the Gnso-newgtld-wg
mailing list