[gnso-gac-closed-generics] Kathy's Use Cases
Manal Ismail
manal at tra.gov.eg
Sat Jan 14 01:39:00 UTC 2023
Many thanks Kathy and Jeff ..
I agree with Jason and Nigel .. This exchange is extremely useful and adds to the factors that we need to consider in our discussion, the interest being served (public / commercial), the portion of the community represented, closed generics vs community TLDs, ...etc.
Kind Regards
--Manal
From: gnso-gac-closed-generics <gnso-gac-closed-generics-bounces at icann.org> On Behalf Of Merritt, Jason (ISED/ISDE)
Sent: Friday, January 13, 2023 9:35 PM
To: Nigel Hickson <nigel.hickson at dcms.gov.uk>; Jeff Neuman <jeff at jjnsolutions.com>
Cc: gnso-gac-closed-generics at icann.org
Subject: Re: [gnso-gac-closed-generics] Kathy's Use Cases
Hello all!
Agree, this is a really interesting discussion topic. In my mind it adds more questions and cautious considerations around the complexities of trying to stretch the public interest framework around 'specific groups'... especially when you consider the existing models of community TLDs and restricted/verifiable TLDs.
Nonetheless, the community objection model gives a good frame of reference and precedent for how to build in some safeguards during the application process. A cornerstone of any closed generic framework will have to include some type of objection mechanism (and obviously some clear guidance for applicants and assessment criteria).
Kind regards,
Jason
Jason Merritt
Sr. Policy Advisor, Telecommunications and Internet Policy Branch
Innovation, Science and Economic Development Canada / Government of Canada
Jason.Merritt at ised-isde.gc.ca<mailto:Jason.Merritt at ised-isde.gc.ca> / Tel: 343-571-9775 / TTY: 1-866-694-8389
Conseiller(ère) en politiques princ., Direction generale des politiques de telecommunications et d'Internet
Innovation, Sciences et Développement économique Canada / Gouvernement du Canada
Jason.Merritt at ised-isde.gc.ca<mailto:Jason.Merritt at ised-isde.gc.ca> / Tél. : 343-571-9775 / ATS : 1-866-694-8389
From: gnso-gac-closed-generics <gnso-gac-closed-generics-bounces at icann.org<mailto:gnso-gac-closed-generics-bounces at icann.org>> On Behalf Of Nigel Hickson via gnso-gac-closed-generics
Sent: January 13, 2023 9:50 AM
To: Jeff Neuman <jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>>
Cc: gnso-gac-closed-generics at icann.org<mailto:gnso-gac-closed-generics at icann.org>
Subject: Re: [gnso-gac-closed-generics] Kathy's Use Cases
Colleagues
Good afternoon, I found this dialogue very interesting and useful. We need, I believe, to be very clear what a Community application is and what a closed generic application is. As our examples in the (really useful) "User Case" work has shown us, there may be public interest issues for an application but there may also be commercial / business issues as Jeff has ariculted.
best
Nigel
On Fri, 13 Jan 2023 at 04:00, Jeff Neuman <jeff at jjnsolutions.com<mailto:jeff at jjnsolutions.com>> wrote:
Thank you for this Kathy. But the criteria you have given are for "Community TLDs" which is not synonymous with a closed generic. If a community wanted to operate for the benefit of that community, it would not need this new "closed generic" category. It would simply apply as a community.
If your use case is that the US Polo Association that applied as a community for .polo said it represents the entire polo community, but it will only allow registrations by the US Polo Association members and no one else, then that in theory could be a "Closed Generic", but by definition it would fail a community analysis because the eligibility requirements for a string are not reasonably related to the community (which is polo in general). Stated another way, operating as closed generic does not benefit the community necessarily, but rather benefits the organization and its users (which may be some of the community, but not all).
My point is that we should not be using the community criteria in the closed generic discussion. They are two separate concepts that need to be destinct.
I would encourage us to look more at the proposed use of the TLD and how a closed generic can be used in a manner that can serve a public interest goal. Focusing on the WHO I believe takes us down a rabbit hole in my view.
In that vein it occurred to me that we have spent a lot of time on the who because our examples were all established institutions, associations, IGOs, etc. But today I came up with a cool Closed Generic idea which I have much more flushed out. But the short version is this:
I start a company to compete with ancestry.com<https://urldefense.com/v3/__https:/can01.safelinks.protection.outlook.com/?url=http*3A*2F*2Fancestry.com*2F&data=05*7C01*7Cjason.merritt*40ised-isde.gc.ca*7Cf9eb5b0542774895500708daf5758951*7Cb72ac62f06d54cd5824eee92319a4676*7C0*7C0*7C638092182680724562*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=OVqD6j66xKzF4z023wfhsmE2cbOoydBNEuR3yOcPsQ0*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSU!!JSZLGTNg!Tz-pjOlRhW1dHF8QvE_v1oUQps20nRBnACo46_tsXSq_RLvAzPLZ_Hb022Cf_E6X4I_34RFVU3G2YT_2z_GqvIoL3gKvZRU$> and I want a TLD for .familytree. I set up a portal that is able to aggregate data from each of the DNA/genealogy services, census data, newspapers, cemeteries, etc. when a user signs up for my service and consents to link their accounts to those other services. I set up my family tree on neuman.familytree and I grant access to whomever I want to be able to see my data, but also where applicable to import portions of my family tree into theirs and I can export their family tree data into mine. So my aunt/uncle/cousins whose last name is Lynn has Lynn.familytree where I can find their data and import the potions that relate to my family tree. Domain Names are only owned by my company that licenses the use of the .familytree domain names to paid subscribers of my service.
This example has some unique aspects that we previously have not really focused on:
1. The benefit to the registry is purely commercial
2. I am a new start up business and not an association or large commercial player
3. Benefits are accrued to my members because they are satisfied customers and can easily enable others to find them (when they want to be found).
Sincerely,
Jeffrey J. Neuman
Founder & CEO
JJN Solutions, LLC
Jeff at JJNSolutions.com<mailto:Jeff at JJNSolutions.com>
+1.202.549.5079
Http://www.jjnsolutions.com<https://urldefense.com/v3/__https:/can01.safelinks.protection.outlook.com/?url=http*3A*2F*2Fwww.jjnsolutions.com*2F&data=05*7C01*7Cjason.merritt*40ised-isde.gc.ca*7Cf9eb5b0542774895500708daf5758951*7Cb72ac62f06d54cd5824eee92319a4676*7C0*7C0*7C638092182680724562*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=l9UVj4YmPef9ni4TIC2lzSTyPV*2F4iy18tVK47DsYzHw*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUl!!JSZLGTNg!Tz-pjOlRhW1dHF8QvE_v1oUQps20nRBnACo46_tsXSq_RLvAzPLZ_Hb022Cf_E6X4I_34RFVU3G2YT_2z_GqvIoL8s2EGF0$>
________________________________
From: gnso-gac-closed-generics <gnso-gac-closed-generics-bounces at icann.org<mailto:gnso-gac-closed-generics-bounces at icann.org>> on behalf of Kathy Kleiman <Kathy at KathyKleiman.com<mailto:Kathy at KathyKleiman.com>>
Sent: Thursday, January 12, 2023 10:31 PM
To: gnso-gac-closed-generics at icann.org<mailto:gnso-gac-closed-generics at icann.org> <gnso-gac-closed-generics at icann.org<mailto:gnso-gac-closed-generics at icann.org>>
Subject: [gnso-gac-closed-generics] Kathy's Use Cases
Hi All,
I presented what sounded like a rather complex use case on Monday, and it's much simpler than it sounds! The ICANN Community has already discussed many of terms and concepts we are pondering in our Small Group via a process called the Community Objection to new gTLD applications. Let me share more details in writing.
Lawyers love "precedent" and there is a lot of valuable precedent in how the ICANN Community created rules to allow Communities to stop applications for new gTLD strings they felt involved words or terms strongly associated with which a group, association, set of companies, or set of organizations. Specifically, our ICANN rules allowed (and will continue to allow in future gTLD rounds) the filing of a Community Objection defined as follows:
"Community Objection - There is substantial opposition to the gTLD application from a significant portion of the community to which the gTLD string may be explicitly or implicitly targeted." Applicant Guidebook 3.2.1 [1]
To challenge an Applicant's choice of a proposed new gTLD, the group/association/company/organization had to show its qualifications as an established institution and level of global recognition and ongoing relationship with a clearly delineated community, and strong association between the applied-for gTLD string and the community, and a likelihood of material detriment to the rights or legitimate interests of a significant portion of the community if the applied-for gTLD string was delegated to the applicant(s) as registry.
The International Centre for Expertise of the International Chamber of Commerce (chosen by ICANN to run these proceedings) picked an Expert who then decided whether the group/ association/company/organization could stop the new gTLD application.
Of the Community Objections filed in the first round, the groups/associations/companies/ organizations below prevailed and these are the "Use Cases" I shared on Monday:[ii]
.architect
International Union of Architects
.banking
International Banking Federation
.mobile
CTIA The Wireless Assoc. joined by GSMA
.polo
US Polo Association
.rugby
International Rugby Board (now World Rugby)
.ski
Federation International de Ski
.sport
SportAccord
.sports
SportAccord
For future closed generic gTLDs, this process gives us a good model, namely that the group/association/company/organization filing for a closed generic gTLD should show that it is:
- an established institution with global recognition, and
- an ongoing relationship with the clearly delineated community, and
- a strong association with the applied-for gTLD string, and
- a clear proposal to use the gTLD for the benefit of a significant portion of the community to which the string may be explicitly or implicitly targeted.
(Quick note that the burden of proof must be with the group, association, company, or organization applying for a new gTLD closed generic application and they must show this proof clearly in the public portion of their application to ICANN and the Community.)
I look forward to discussing with you!
Kathy
Background information:
New gTLD Applicant Guidebook Rules for Community Objections
(New gTLD Applicant Guidebook 2012)
Key Terms and Criteria for Proving Them[iii]
Below are the key terms that the group/association/companies/organizations in the table above use in their proceedings before The International Centre for Expertise of the International Chamber of Commerce to stop a proposed gTLD string and application.
"It is an established institution - Factors that may be considered in making this determination include, but are not limited to:
* Level of global recognition of the institution;
* Length of time the institution has been in existence; and
* Public historical evidence of its existence, such as the presence of a formal charter or national or international registration, or validation by a
government, inter-governmental organization, or treaty. The institution must not have been established solely in conjunction with the gTLD
application process." Applicant Guidebook 3.2.2.4
It has an ongoing relationship with a clearly delineated community - Factors that may be considered in making this determination include, but are not limited to:
* The presence of mechanisms for participation in activities, membership, and leadership;
* Institutional purpose related to the benefit of the associated community;
* Performance of regular activities that benefit the associated community; and
* The level of formal boundaries around the community.
Applicant Guidebook 3.2.2.4
If the group met this "standing" requirement, the Expert would hear the rest of their arguments, and the Community had to show:
Substantial Opposition - The objector must prove substantial opposition within the community it has identified itself as representing. A panel could balance a number of factors to determine whether there is substantial opposition, including but not limited to:
* Number of expressions of opposition relative to the composition of the community;
* The representative nature of entities expressing opposition;
* Level of recognized stature or weight among sources of opposition;
* Distribution or diversity among sources of expressions of opposition, including:
* Regional
* Subsectors of community
* Leadership of community
* Membership of community
* Historical defense of the community in other contexts; and
* Costs incurred by objector in expressing opposition, including other channels the objector may have used to convey opposition.
If some opposition within the community is determined, but it does not meet the standard of substantial opposition, the objection will fail.
Applicant Guidebook 3.5.4
And
Targeting - The objector must prove a strong association between the applied-for gTLD string and the community represented by the objector. Factors that could be balanced by a panel to determine this include but are not limited to:
* Statements contained in application;
* Other public statements by the applicant;
* Associations by the public. Applicant Guidebook 3.5.4
And
Detriment - The objector must prove that the application creates a likelihood of material detriment to the rights or legitimate interests of a significant portion of the community to which the string may be explicitly or implicitly targeted. An allegation of detriment that consists only of the applicant being delegated the string instead of the objector will not be sufficient for a finding of material detriment. Factors that could be used by a panel in making this determination include but are not limited to:
* Nature and extent of damage to the reputation of the community represented by the objector that would result from the applicant's operation of the applied-for gTLD string;
* Evidence that the applicant is not acting or does not intend to act in accordance with the interests of the community or of users more widely, including evidence that the applicant has not proposed or does not intend to institute effective security protection for user interests;
* Interference with the core activities of the community that would result from the applicant's operation of the applied-for gTLD string;
* Dependence of the community represented by the objector on the DNS for its core activities;
* Nature and extent of concrete or economic damage to the community represented by the objector that would result from the applicant's operation of the applied-for gTLD string; and
* Level of certainty that alleged detrimental outcomes would occur.
Applicant Guidebook 3.5.4
(text also attached as Word doc)
________________________________
[1] 3.2.1 Grounds for Objection, gTLD Applicant Guidebook, Module 3, https://newgtlds.icann.org/sites/default/files/objection-procedures-04jun12-en.pdf<https://urldefense.com/v3/__https:/can01.safelinks.protection.outlook.com/?url=https*3A*2F*2Fnewgtlds.icann.org*2Fsites*2Fdefault*2Ffiles*2Fobjection-procedures-04jun12-en.pdf&data=05*7C01*7Cjason.merritt*40ised-isde.gc.ca*7Cf9eb5b0542774895500708daf5758951*7Cb72ac62f06d54cd5824eee92319a4676*7C0*7C0*7C638092182680724562*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=9saCiulyK6OE9Qw0g5EZU21c0EPNPXuLMIDYaV9VCnY*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!JSZLGTNg!Tz-pjOlRhW1dHF8QvE_v1oUQps20nRBnACo46_tsXSq_RLvAzPLZ_Hb022Cf_E6X4I_34RFVU3G2YT_2z_GqvIoLVrm4Ydg$>
[ii] ICC: ICANN New gTLD Dispute Resolution, https://iccwbo.org/dispute-resolution-services/icann-gtld-process/expert-determinations/<https://urldefense.com/v3/__https:/can01.safelinks.protection.outlook.com/?url=https*3A*2F*2Ficcwbo.org*2Fdispute-resolution-services*2Ficann-gtld-process*2Fexpert-determinations*2F&data=05*7C01*7Cjason.merritt*40ised-isde.gc.ca*7Cf9eb5b0542774895500708daf5758951*7Cb72ac62f06d54cd5824eee92319a4676*7C0*7C0*7C638092182680724562*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=935Y*2BmDKkeblaeh0zHGxEVFhVXFokMqAe7BAd*2B4BkDo*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!JSZLGTNg!Tz-pjOlRhW1dHF8QvE_v1oUQps20nRBnACo46_tsXSq_RLvAzPLZ_Hb022Cf_E6X4I_34RFVU3G2YT_2z_GqvIoLyLiEBAk$>
[iii] New gTLD Applicant Guidebook 4 June 2012, Module 3 Objection Procedures, https://newgtlds.icann.org/en/applicants/agb<https://urldefense.com/v3/__https:/can01.safelinks.protection.outlook.com/?url=https*3A*2F*2Fnewgtlds.icann.org*2Fen*2Fapplicants*2Fagb&data=05*7C01*7Cjason.merritt*40ised-isde.gc.ca*7Cf9eb5b0542774895500708daf5758951*7Cb72ac62f06d54cd5824eee92319a4676*7C0*7C0*7C638092182680724562*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=2Z2gbrkQ*2BxFQvqdmcFUX1IGtlvfoBRTjTPUJMW3G3yw*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSU!!JSZLGTNg!Tz-pjOlRhW1dHF8QvE_v1oUQps20nRBnACo46_tsXSq_RLvAzPLZ_Hb022Cf_E6X4I_34RFVU3G2YT_2z_GqvIoLcQToVLg$>
_______________________________________________
gnso-gac-closed-generics mailing list
gnso-gac-closed-generics at icann.org<mailto:gnso-gac-closed-generics at icann.org>
https://mm.icann.org/mailman/listinfo/gnso-gac-closed-generics<https://urldefense.com/v3/__https:/can01.safelinks.protection.outlook.com/?url=https*3A*2F*2Fmm.icann.org*2Fmailman*2Flistinfo*2Fgnso-gac-closed-generics&data=05*7C01*7Cjason.merritt*40ised-isde.gc.ca*7Cf9eb5b0542774895500708daf5758951*7Cb72ac62f06d54cd5824eee92319a4676*7C0*7C0*7C638092182680724562*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=tLkA8IKG8jGH9SiPd7V8YXcZS9JnPPIHxab2akJnHCU*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!JSZLGTNg!Tz-pjOlRhW1dHF8QvE_v1oUQps20nRBnACo46_tsXSq_RLvAzPLZ_Hb022Cf_E6X4I_34RFVU3G2YT_2z_GqvIoLx7lI01o$>
_______________________________________________
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://urldefense.com/v3/__https:/can01.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.icann.org*2Fprivacy*2Fpolicy&data=05*7C01*7Cjason.merritt*40ised-isde.gc.ca*7Cf9eb5b0542774895500708daf5758951*7Cb72ac62f06d54cd5824eee92319a4676*7C0*7C0*7C638092182680724562*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=rzpTfSlwZIIa3BRR*2FYxqy3jdki*2BzfRyi*2BLS*2Fla77hhY*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!JSZLGTNg!Tz-pjOlRhW1dHF8QvE_v1oUQps20nRBnACo46_tsXSq_RLvAzPLZ_Hb022Cf_E6X4I_34RFVU3G2YT_2z_GqvIoLUyu9ReY$>) and the website Terms of Service (https://www.icann.org/privacy/tos<https://urldefense.com/v3/__https:/can01.safelinks.protection.outlook.com/?url=https*3A*2F*2Fwww.icann.org*2Fprivacy*2Ftos&data=05*7C01*7Cjason.merritt*40ised-isde.gc.ca*7Cf9eb5b0542774895500708daf5758951*7Cb72ac62f06d54cd5824eee92319a4676*7C0*7C0*7C638092182680724562*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=loXPlnchQSKssCGCGPjxMNVsyZIJG4apea1G1IVzwdA*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUl!!JSZLGTNg!Tz-pjOlRhW1dHF8QvE_v1oUQps20nRBnACo46_tsXSq_RLvAzPLZ_Hb022Cf_E6X4I_34RFVU3G2YT_2z_GqvIoLhWOhQek$>). 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/20230114/91b68e84/attachment-0001.html>
More information about the gnso-gac-closed-generics
mailing list