Kathy, Just for clarity, after all of us have suffered through endless dissecting and re-arguing every other topic and issue including many where there was clearly no consensus and following the Newman rule would have permitted us to simply move on to the next topic, we are now following the Newman rule again when doing so would achieve the result you want? Best regards, Marc H. Trachtenberg Shareholder Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 Tel 312.456.1020 Mobile 773.677.3305 trac@gtlaw.com<mailto:trac@gtlaw.com> | www.gtlaw.com<http://www.gtlaw.com/> [Greenberg Traurig] From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 12:53 PM To: Aikman-Scalese, Anne <AAikman@lrrc.com>; gnso-newgtld-wg@icann.org Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry *EXTERNAL TO GT* Hi Anne, Per the discussion in the WG and on the chat, I don't agree that this is the right assessment at all. The Board adopted policy in 2012, and ICANN Org, Board and Community did followed it and dozens of closed applications became open in Round 1. Far more important than the order of processing of applications (an implementation issue), this is a fundamental policy issue. The Board acted, with enormous public input during a formal comment period, and then created the bar. The default by the Newman rule and everything else we follow is to keep this policy, and practice of 2012, absent some overwhelming reason to change it. In all these months, no overwhelming need or agreement has materialized. Best, Kathy On 2/18/2020 12:16 PM, Aikman-Scalese, Anne wrote: HI Kathy, I do think it’s important for the WG to understand what Jeff’s position is procedurally on this topic. It appears to me that Paul is correct that there was no policy against Closed Generics in 2012 and that the Board resolution is limited to the 2012 round. So if we stick with the “ground rules” of the PDP, it appears that the next round will be “open season” for Closed Generic applications. This is especially important to consider now that the Working Group has taken a “rough consensus” position (with some of us dissenting) that going forward, if a string is applied for in the next round, that application will act as a complete bar to applications for the same string in any subsequent round. I would strongly advocate for skipping this topic in the next call and scheduling it for the F2F meeting. Anne From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org><mailto:gnso-newgtld-wg-bounces@icann.org> On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 8:36 AM To: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry [EXTERNAL] ________________________________ As we revisit the topic of Closed Generics, I would like to share a few thoughts as a reminder on how this issue (of "generic words") has been dealt with in other forums. This is a long-established issue... 1) Trademark Manual of Examining Procedure, US Trademark Office: "Generic terms are incapable of functioning as marks denoting source, and are not registrable on the Principal Register under §2(f) or on the Supplemental Register." 807.14(e)(ii) 2) Our own Community Objection process reviewed and raised the same deep concerns for gTLDs in which the applicant (a competitor in a field) ICC New gTLD Community Objections determination: "The establishment of unrestricted, exclusive rights to a gTLD that is strongly associated with a certain community or communities, particularly where those communities are, or are likely to be, active in the Internet sphere seems to me inherently detrimental to those communities' interests." [Note: the "communities" being referred to here are commercial communities. The issue of a closed .MOBILE was raised by the CTIA which represents the US mobile wireless industry. 1-1316-6133 Best, Kathy ________________________________ 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. ---------------------------------------------------------------------- If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster@gtlaw.com, and do not use or disseminate the information.

Marc, Kathy, et al I think it’s important for us to get a better sense of exactly what “The Newman Rule” is and how to apply it to the document that will go out for public comment. As Jeff stated, consistency in application of the Rule is important. One factor missing from the discussion on today’s call was the significance of action taken by Resolution of the New gTLD Program Committee. https://www.icann.org/resources/board-material/resolutions-2012-04-10-en Rationale: In order to have efficient meetings and take appropriate actions with respect to the New gTLD Program for the current round of the Program and as related to the Applicant Guidebook, the Board decided to create the "New gTLD Program Committee" in accordance with Article XII of the Bylaws and has delegated decision making authority to the Committee as it relates to the New gTLD Program for the current round of the Program which commenced in January 2012 and for the related Applicant Guidebook that applies to this current round. The discussion on idns this morning did not seem to follow the rule that the WG has been operating under for a couple of years. This was based on the idea that this was a staff decision, but I would like to know whether the New gTLD Program Committee endorsed this idn priority processing approach. Maybe the application of the Newman Rule needs to vary depending on various other circumstances? This is why we need for Jeff to clarify when he wants to make exceptions to the Newman Rule and on what basis. Jeff may be suggesting a “corollary” to the Newman Rule based on whether the Board (or the New gTLD Program Committee) ratified the staff’s action or not, but the corollary isn’t really clear based on today’s discussion. In other words, Jeff seemed to say that (a) the Newman rule does not necessarily apply to idn priority application processing because that approach was developed by Staff and (b) the Newman rule does not apply to Closed Generics because the Board’s resolution was limited to the 2012 round applications. Having worked on the Policy and Implementation WG (and given what we have gone through in relation to the Predictability Framework), I believe that if we try to distinguish the exceptions based on which case presents “policy” versus which case presents “implementation”, we are going down a rabbit hole that will result in more delay to the next round opening. On the other hand, we can’t really approach this as a rule that Leadership applies as it determines on a case-by-case basis. (There is no consistency in that approach.) And as several WG members pointed out, it’s quite different from the operating presumption that that been applied during the course of this WG’s deliberations. The operating presumption was: If no consensus, the 2012 practice stands. Maybe we should talk about how the proposed variations in the application of the Newman Rule as described by Leadership on today’s call would apply to other issues finalized after the 2012 AGB was issued (but as to which we may not have Consensus). Off the top of my head, so far I think the list includes at least the following: 1. Giving application processing priority to IDNs. Developed by staff but the Board endorsed? When we say “ Staff” here, do we mean the New gTLD Program Committee? Because that was a subset of Board members who were not conflicted and they were given full authority by the Board. 2. Closed generic applications – Board resolution says limited to 2012. GAC Advice says “only if in the Public Interest” which the ICANN Board is trying to define with reference to the policy process. 3. Community Priority Evaluation – further evaluation process developed subsequent to the publication of the AGB. WG has yet to agree on whether to adopt the point system. 4. Requiring disclosure of all proposed services in response to Question 18 of the application. (This was in the 2012 AGB but some want to relegate it to the RSEP process so applications can move through more quickly.) 5. Specification 13 – not developed through a policy process but endorsed by the Board. Was there a Board Resolution? Action by the New gTLD Program Committee? 6. Name Collision Framework (Resolution passed by the New gTLD Program Committee.) https://www.icann.org/en/system/files/files/name-collision-framework-30jul14... 7. YOUR TOPIC HERE 8. YOUR TOPIC HERE Anne From: trachtenbergm@gtlaw.com <trachtenbergm@gtlaw.com> Sent: Tuesday, February 18, 2020 12:30 PM To: kathy@kathykleiman.com; Aikman-Scalese, Anne <AAikman@lrrc.com>; gnso-newgtld-wg@icann.org Subject: RE: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry [EXTERNAL] ________________________________ Kathy, Just for clarity, after all of us have suffered through endless dissecting and re-arguing every other topic and issue including many where there was clearly no consensus and following the Newman rule would have permitted us to simply move on to the next topic, we are now following the Newman rule again when doing so would achieve the result you want? Best regards, Marc H. Trachtenberg Shareholder Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 Tel 312.456.1020 Mobile 773.677.3305 trac@gtlaw.com<mailto:trac@gtlaw.com> | www.gtlaw.com<http://www.gtlaw.com/> [Greenberg Traurig] From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 12:53 PM To: Aikman-Scalese, Anne <AAikman@lrrc.com<mailto:AAikman@lrrc.com>>; gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry *EXTERNAL TO GT* Hi Anne, Per the discussion in the WG and on the chat, I don't agree that this is the right assessment at all. The Board adopted policy in 2012, and ICANN Org, Board and Community did followed it and dozens of closed applications became open in Round 1. Far more important than the order of processing of applications (an implementation issue), this is a fundamental policy issue. The Board acted, with enormous public input during a formal comment period, and then created the bar. The default by the Newman rule and everything else we follow is to keep this policy, and practice of 2012, absent some overwhelming reason to change it. In all these months, no overwhelming need or agreement has materialized. Best, Kathy On 2/18/2020 12:16 PM, Aikman-Scalese, Anne wrote: HI Kathy, I do think it’s important for the WG to understand what Jeff’s position is procedurally on this topic. It appears to me that Paul is correct that there was no policy against Closed Generics in 2012 and that the Board resolution is limited to the 2012 round. So if we stick with the “ground rules” of the PDP, it appears that the next round will be “open season” for Closed Generic applications. This is especially important to consider now that the Working Group has taken a “rough consensus” position (with some of us dissenting) that going forward, if a string is applied for in the next round, that application will act as a complete bar to applications for the same string in any subsequent round. I would strongly advocate for skipping this topic in the next call and scheduling it for the F2F meeting. Anne From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org><mailto:gnso-newgtld-wg-bounces@icann.org> On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 8:36 AM To: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry [EXTERNAL] ________________________________ As we revisit the topic of Closed Generics, I would like to share a few thoughts as a reminder on how this issue (of "generic words") has been dealt with in other forums. This is a long-established issue... 1) Trademark Manual of Examining Procedure, US Trademark Office: "Generic terms are incapable of functioning as marks denoting source, and are not registrable on the Principal Register under §2(f) or on the Supplemental Register." 807.14(e)(ii) 2) Our own Community Objection process reviewed and raised the same deep concerns for gTLDs in which the applicant (a competitor in a field) ICC New gTLD Community Objections determination: "The establishment of unrestricted, exclusive rights to a gTLD that is strongly associated with a certain community or communities, particularly where those communities are, or are likely to be, active in the Internet sphere seems to me inherently detrimental to those communities' interests." [Note: the "communities" being referred to here are commercial communities. The issue of a closed .MOBILE was raised by the CTIA which represents the US mobile wireless industry. 1-1316-6133 Best, Kathy ________________________________ 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. ________________________________ If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster@gtlaw.com<mailto:postmaster@gtlaw.com>, and do not use or disseminate the information. ________________________________ 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.

Agreed Mike – very sorry Jeff that I picked up this spelling error – the Neuman Rule. But it’s definitely not a new rule - it’s the rule that has applied for a couple of years now as the WG was deliberating. And it affects a lot of issues so it’s a good thing it’s coming up now and not later. From: Mike Rodenbaugh <mike@rodenbaugh.com> Sent: Tuesday, February 18, 2020 3:28 PM To: Aikman-Scalese, Anne <AAikman@lrrc.com> Cc: trachtenbergm@gtlaw.com; kathy@kathykleiman.com; gnso-newgtld-wg@icann.org Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry [EXTERNAL] ________________________________ I feel pretty strongly that, at bare minimum, we should give Jeff the respect of spelling his name correctly -- especially if we are going to name a whole new capitalized Rule after him. We owe him at least that much. Sincerely, Mike Rodenbaw RODENBAUGH LAW tel/fax: +1.415.738.8087 http://rodenbaugh.law On Tue, Feb 18, 2020 at 2:12 PM Aikman-Scalese, Anne <AAikman@lrrc.com<mailto:AAikman@lrrc.com>> wrote: Marc, Kathy, et al I think it’s important for us to get a better sense of exactly what “The Newman Rule” is and how to apply it to the document that will go out for public comment. As Jeff stated, consistency in application of the Rule is important. One factor missing from the discussion on today’s call was the significance of action taken by Resolution of the New gTLD Program Committee. https://www.icann.org/resources/board-material/resolutions-2012-04-10-en Rationale: In order to have efficient meetings and take appropriate actions with respect to the New gTLD Program for the current round of the Program and as related to the Applicant Guidebook, the Board decided to create the "New gTLD Program Committee" in accordance with Article XII of the Bylaws and has delegated decision making authority to the Committee as it relates to the New gTLD Program for the current round of the Program which commenced in January 2012 and for the related Applicant Guidebook that applies to this current round. The discussion on idns this morning did not seem to follow the rule that the WG has been operating under for a couple of years. This was based on the idea that this was a staff decision, but I would like to know whether the New gTLD Program Committee endorsed this idn priority processing approach. Maybe the application of the Newman Rule needs to vary depending on various other circumstances? This is why we need for Jeff to clarify when he wants to make exceptions to the Newman Rule and on what basis. Jeff may be suggesting a “corollary” to the Newman Rule based on whether the Board (or the New gTLD Program Committee) ratified the staff’s action or not, but the corollary isn’t really clear based on today’s discussion. In other words, Jeff seemed to say that (a) the Newman rule does not necessarily apply to idn priority application processing because that approach was developed by Staff and (b) the Newman rule does not apply to Closed Generics because the Board’s resolution was limited to the 2012 round applications. Having worked on the Policy and Implementation WG (and given what we have gone through in relation to the Predictability Framework), I believe that if we try to distinguish the exceptions based on which case presents “policy” versus which case presents “implementation”, we are going down a rabbit hole that will result in more delay to the next round opening. On the other hand, we can’t really approach this as a rule that Leadership applies as it determines on a case-by-case basis. (There is no consistency in that approach.) And as several WG members pointed out, it’s quite different from the operating presumption that that been applied during the course of this WG’s deliberations. The operating presumption was: If no consensus, the 2012 practice stands. Maybe we should talk about how the proposed variations in the application of the Newman Rule as described by Leadership on today’s call would apply to other issues finalized after the 2012 AGB was issued (but as to which we may not have Consensus). Off the top of my head, so far I think the list includes at least the following: 1. Giving application processing priority to IDNs. Developed by staff but the Board endorsed? When we say “ Staff” here, do we mean the New gTLD Program Committee? Because that was a subset of Board members who were not conflicted and they were given full authority by the Board. 2. Closed generic applications – Board resolution says limited to 2012. GAC Advice says “only if in the Public Interest” which the ICANN Board is trying to define with reference to the policy process. 3. Community Priority Evaluation – further evaluation process developed subsequent to the publication of the AGB. WG has yet to agree on whether to adopt the point system. 4. Requiring disclosure of all proposed services in response to Question 18 of the application. (This was in the 2012 AGB but some want to relegate it to the RSEP process so applications can move through more quickly.) 5. Specification 13 – not developed through a policy process but endorsed by the Board. Was there a Board Resolution? Action by the New gTLD Program Committee? 6. Name Collision Framework (Resolution passed by the New gTLD Program Committee.) https://www.icann.org/en/system/files/files/name-collision-framework-30jul14... 7. YOUR TOPIC HERE 8. YOUR TOPIC HERE Anne From: trachtenbergm@gtlaw.com<mailto:trachtenbergm@gtlaw.com> <trachtenbergm@gtlaw.com<mailto:trachtenbergm@gtlaw.com>> Sent: Tuesday, February 18, 2020 12:30 PM To: kathy@kathykleiman.com<mailto:kathy@kathykleiman.com>; Aikman-Scalese, Anne <AAikman@lrrc.com<mailto:AAikman@lrrc.com>>; gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry [EXTERNAL] ________________________________ Kathy, Just for clarity, after all of us have suffered through endless dissecting and re-arguing every other topic and issue including many where there was clearly no consensus and following the Newman rule would have permitted us to simply move on to the next topic, we are now following the Newman rule again when doing so would achieve the result you want? Best regards, Marc H. Trachtenberg Shareholder Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 Tel 312.456.1020 Mobile 773.677.3305 trac@gtlaw.com<mailto:trac@gtlaw.com> | www.gtlaw.com<http://www.gtlaw.com/> [Greenberg Traurig] From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 12:53 PM To: Aikman-Scalese, Anne <AAikman@lrrc.com<mailto:AAikman@lrrc.com>>; gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry *EXTERNAL TO GT* Hi Anne, Per the discussion in the WG and on the chat, I don't agree that this is the right assessment at all. The Board adopted policy in 2012, and ICANN Org, Board and Community did followed it and dozens of closed applications became open in Round 1. Far more important than the order of processing of applications (an implementation issue), this is a fundamental policy issue. The Board acted, with enormous public input during a formal comment period, and then created the bar. The default by the Newman rule and everything else we follow is to keep this policy, and practice of 2012, absent some overwhelming reason to change it. In all these months, no overwhelming need or agreement has materialized. Best, Kathy On 2/18/2020 12:16 PM, Aikman-Scalese, Anne wrote: HI Kathy, I do think it’s important for the WG to understand what Jeff’s position is procedurally on this topic. It appears to me that Paul is correct that there was no policy against Closed Generics in 2012 and that the Board resolution is limited to the 2012 round. So if we stick with the “ground rules” of the PDP, it appears that the next round will be “open season” for Closed Generic applications. This is especially important to consider now that the Working Group has taken a “rough consensus” position (with some of us dissenting) that going forward, if a string is applied for in the next round, that application will act as a complete bar to applications for the same string in any subsequent round. I would strongly advocate for skipping this topic in the next call and scheduling it for the F2F meeting. Anne From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org><mailto:gnso-newgtld-wg-bounces@icann.org> On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 8:36 AM To: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry [EXTERNAL] ________________________________ As we revisit the topic of Closed Generics, I would like to share a few thoughts as a reminder on how this issue (of "generic words") has been dealt with in other forums. This is a long-established issue... 1) Trademark Manual of Examining Procedure, US Trademark Office: "Generic terms are incapable of functioning as marks denoting source, and are not registrable on the Principal Register under §2(f) or on the Supplemental Register." 807.14(e)(ii) 2) Our own Community Objection process reviewed and raised the same deep concerns for gTLDs in which the applicant (a competitor in a field) ICC New gTLD Community Objections determination: "The establishment of unrestricted, exclusive rights to a gTLD that is strongly associated with a certain community or communities, particularly where those communities are, or are likely to be, active in the Internet sphere seems to me inherently detrimental to those communities' interests." [Note: the "communities" being referred to here are commercial communities. The issue of a closed .MOBILE was raised by the CTIA which represents the US mobile wireless industry. 1-1316-6133 Best, Kathy ________________________________ 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. ________________________________ If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster@gtlaw.com<mailto:postmaster@gtlaw.com>, and do not use or disseminate the information. ________________________________ 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@icann.org<mailto:Gnso-newgtld-wg@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.

The SubPro meeting today began discussing Closed Generics. One of my interventions was that although I was strongly opposed to closed generics in the general case, I did support the concept that a closed generic could be in the public interest, with the example of .disaster operating by the International Red Cross as the example. I proposed that we allow closed generic applications, but the decision on whether a particular application would move forward or not would rest with the ICANN Board. The Board would have to agree, by an overwhelming majority (say at least 90% of sitting, non-conflicted, Board members) that the TLD would be in the public interest. The decision would be final and not appealable through the ICANN Reconsideration or IRP processes. This latter condition would require an amendment to the ICANN Bylaws to exempt such decision from the accountability measures, but this is identical to an amendment being recommended by the CCWG-Auction Proceeds, so there is a current precedent. If, despite the fact that the decision would have to be near unanimous, there is still distrust of the ICANN Board in this matter, the approval of such TLDs could be subject to the Empowered Community Approval or Rejection Actions (also requiring a Bylaw change). However, in my mind, such caution would be overkill. This proposal would allow a closed generic when it is clearly (in the view of the Board) in the Public Interest. Alan

Dear All Yes I agree with you Anne Preservation of or decision or to agree or disagree with any issue before board based on public interest has always prevailed Regards KAVOUSS Sent from my iPhone

On 19 Feb 2020, at 19:16, Aikman-Scalese, Anne <AAikman@lrrc.com> wrote:

With the caveat that this is a personal opinion, I support open face-to-face discussion of Alan's proposal. After all, the AGB contained a provision that the Board has a right to refuse any single application based on the public interest so that suggests that individual evaluation could be appropriate. Anne

-----Original Message----- From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> On Behalf Of Alan Greenberg Sent: Tuesday, February 18, 2020 7:27 PM To: gnso-newgtld-wg@icann.org Subject: [Gnso-newgtld-wg] Proposal re Closed Generics

[EXTERNAL]

The SubPro meeting today began discussing Closed Generics.

One of my interventions was that although I was strongly opposed to closed generics in the general case, I did support the concept that a closed generic could be in the public interest, with the example of .disaster operating by the International Red Cross as the example.

I proposed that we allow closed generic applications, but the decision on whether a particular application would move forward or not would rest with the ICANN Board.

The Board would have to agree, by an overwhelming majority (say at least 90% of sitting, non-conflicted, Board members) that the TLD would be in the public interest.

The decision would be final and not appealable through the ICANN Reconsideration or IRP processes. This latter condition would require an amendment to the ICANN Bylaws to exempt such decision from the accountability measures, but this is identical to an amendment being recommended by the CCWG-Auction Proceeds, so there is a current precedent.

If, despite the fact that the decision would have to be near unanimous, there is still distrust of the ICANN Board in this matter, the approval of such TLDs could be subject to the Empowered Community Approval or Rejection Actions (also requiring a Bylaw change). However, in my mind, such caution would be overkill.

This proposal would allow a closed generic when it is clearly (in the view of the Board) in the Public Interest.

Alan

_______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg@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@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.

Anne, This is a contradiction. If the board denied “closed generics” (gTLD applications for generic keyword based strings) in 2012 then they did for a REASON. Unless the board specified a “conditional aspect” for that reason then the rationale for that decision hasn’t changed just because a decade went by. So the “ground rule” would be to keep the application rules as they were in 2012 – namely denying closed generics. UNLESS the gNSO develops new recommendations – which then need a new board approval. Some might argue that in 2012 the “problem” with closed generics wasn’t that bad: only a few dozen generic terms where taken by industry leaders (apparently mostly to just block off the entire vertical). So why bothering? Well: In 2012 the COST for a new gTLD was enormous! Application writing and submission wasn’t yet streamlined and expensive. Consulting (partly due to a steep “learning curve”) was expensive. Application fees alone where almost US $200k. By definition in 2012 there was no PRECEDENCE that industry leaders would snag up entire category defining killer keyword based gTLDs. The entire “new gTLD” issue was “murky”. All of this will have DRASTICALLY changed by 2022: * There will be a DECADE of public experience and exposure of the new gTLD program and new gTLDs * The consulting and application submission related fees will be DRASTICALLY lower – some consultants already offer packages lower than US $30k – which includes application writing, submission, contracting and testing! * The application fee will likely be low, too. Some already fabulize about US $25k fee floors – or even BELOW! * The “myth” that leading industry giants are massively hoarding “their” verticals (industry defining category killer generic terms) ain’t a “myth” anymore: it’s a viable truth – proven by the 2012 application roster. * Consultants will swarm out to big corporations who have ample marketing budgets and inflated egos: “If YOU are not securing ‘.CategoryDefiningKeyword’ then your competition will: be clever and have at minimum a horse in the race: let us apply for it on your behalf”. Image how incredibly STUPID the head of digital marketing of a Multi-Billion corporation looks if their smaller competitor controls “their” category keyword gTLD: this could cost him his head. In comparison for the price of a half page New York Times ad he could play hero and showcase to his board how “farsighted” he is. So if anything then the underlying “problem” that lead the board in 2012 to deny “closed generics” only got worse – MUCH worse: Lower “fees & overall cost” combined with established precedence = disaster! And while we have an obligation to keep harm away from the Internet community by continuing to deny “closed generics” that logically implies that we also make sure that in the 2nd round there will be no possibility for “effectively closed generics”: namely generic term based open applications that prove their “public interest” by promising launch periods (e.g. the Sunrise period) – but then never EXECUTE the Sunrise period – but rather are closed to the public and still allow the applicant to run 100 domains. If you have a Sunrise period in your application then you ought to execute that in a reasonable frame of time – or else you render the gTLD “closed”. I suggest we provide 12 month (extendable by another 12 month if reasons are provided for the delay) to launch your Sunrise (if you have one in your application) – but at BARE MINUMUM ICANN should be crystal clear that for registries that have a Sunrise in their application any “contract renewal expectation” will only apply if such Sunrise has been executed. Otherwise industry giants will simply snag up category defining keyword based gTLDs – and leave them inactive – just to make sure they “control the namespace”. Or they use their 100 domains and effectively run it as closed generic. If the general public (or Congress for that matter) would get wind of how sloppy we are protecting the public interest here: they would go bananas. Thanks, Alexander From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Aikman-Scalese, Anne Sent: Dienstag, 18. Februar 2020 12:16 To: Kathy Kleiman <kathy@kathykleiman.com>; gnso-newgtld-wg@icann.org Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry HI Kathy, I do think it’s important for the WG to understand what Jeff’s position is procedurally on this topic. It appears to me that Paul is correct that there was no policy against Closed Generics in 2012 and that the Board resolution is limited to the 2012 round. So if we stick with the “ground rules” of the PDP, it appears that the next round will be “open season” for Closed Generic applications. This is especially important to consider now that the Working Group has taken a “rough consensus” position (with some of us dissenting) that going forward, if a string is applied for in the next round, that application will act as a complete bar to applications for the same string in any subsequent round. I would strongly advocate for skipping this topic in the next call and scheduling it for the F2F meeting. Anne From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org <mailto:gnso-newgtld-wg-bounces@icann.org> > On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 8:36 AM To: gnso-newgtld-wg@icann.org <mailto:gnso-newgtld-wg@icann.org> Subject: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry [EXTERNAL] _____ As we revisit the topic of Closed Generics, I would like to share a few thoughts as a reminder on how this issue (of "generic words") has been dealt with in other forums. This is a long-established issue... 1) Trademark Manual of Examining Procedure, US Trademark Office: "Generic terms are incapable of functioning as marks denoting source, and are not registrable on the Principal Register under §2(f) or on the Supplemental Register." 807.14(e)(ii) 2) Our own Community Objection process reviewed and raised the same deep concerns for gTLDs in which the applicant (a competitor in a field) ICC New gTLD Community Objections determination: "The establishment of unrestricted, exclusive rights to a gTLD that is strongly associated with a certain community or communities, particularly where those communities are, or are likely to be, active in the Internet sphere seems to me inherently detrimental to those communities' interests." [Note: the "communities" being referred to here are commercial communities. The issue of a closed .MOBILE was raised by the CTIA which represents the US mobile wireless industry. 1-1316-6133 Best, Kathy _____ 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.

Dear Group, Here from the June 2015 board meeting resolutions (these are quotes directly from the ICANN.org website): https://www.icann.org/resources/board-material/resolutions-new-gtld-2015-06-... Advise Exclusive Generic Applicants for non-contended strings, or Exclusive Generic Applicants prevailing in contention resolution that they must elect within a reasonably limited time to either: submit a change request to no longer be an exclusive generic TLD, and sign the current form of the New gTLD Registry Agreement; maintain their plan to operate an exclusive generic TLD. As a result, their application will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs; or withdraw their application for a refund consistent with the refund schedule in the Applicant Guidebook. I would like to draw emphasis to: “…. will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” The board clearly states that there is a SEVERE PROBLEM, that it denies closed generic applications, that those REMAIN ineligible UNTIL the GNSO has “developed advice concerning exclusive generic gTLDs”. Hairsplitters could argue that this is only true for the 2012 roster. But hey: come on. This is in striking contrast to the assentation that the ineligibility where to be restricted to the 2012 round only. The board INSTRUCTED the gNSO to “develop policy advice concerning exclusive generic TLD”, so in absence of a consensus around such policy advice it is self-evident that the board’s concerns aren’t addressed at all; and their “ban” stays active (or we force them to activate it yet again) We run the risk to look incompetent if we run into this knife yet again: if we (like suggested by some here) maintain that our 2007 PDP was “flawless” – and that we have to repeat this obvious mistake (allowing closed generics) again; then here what will happen: * GAC will point out the same as it has done in the 2012 round: asking the board to deny closed generics! * The board will note that the gNSO has denied their explicit request to develop new policy advice; and as a result will deny closed generics AGAIN! * This creates MASSIVE confusion for applicants; something that we should allow I assume it would be best if we abide by the Board request to “develop policy advice concerning exclusive generic TLD”. A subgroup was initiated last year – I am in there; but the group was inactive so far. We simply should create policy advice. If there is a consensus around under what set of circumstances allowing closed generics: fine! Then we allow them. If there is no consensus: then I guess we have established just that: No consensus to allow closed generics. Here a bit more from the June 2015 board resolutions: A Policy Development Process with respect to operating exclusive generic strings in the "public interest" should be undertaken by the community. Policy issues on "closed generic" TLDs should be resolved through the multistakeholder process. The public interest goal requirement as stated is too general and requires greater specificity for enforceability. The NGPC should add relevant meaning to the "public interest" concept by applying the GNSO rationales regarding the promotion of competition, consumer choice, market differentiation, and geographical and service provider diversity as standards for such affirmative objective showings and findings. Safeguards are important when applicants have chosen to apply for closed control of a generic term designating a particular industry where the applicant is engaged in the conduct of business activities in that industry. Requiring applicants to demonstrate some additional public interest goal in the context of exclusive registry access for generic strings would reverse the deliberate choices made by the ICANN community in its bottom-up process and impose new evaluation criteria. The status quo as set out in the Applicant Guidebook should apply so that both "open" and "closed" registry access for generic strings should continue to be allowed in this first application round, but both should be subject to significant scrutiny after launch by ICANN to ensure that the interests of rights owners and consumers are protected. So to say that the board decision was only pertaining the first round – but the 2nd round would be “open season for anything” is ignoring the board’s very clear advice. Board resolutions are our “safety valve” – we should try to establish our policies in a way that doesn’t require the board to issue them. And while we are at it: Submitting a generic term based gTLD application, trying to “prove public interest” by implementing clear launch phases (e.g. Sunrise), then never living up to such commitment: Should result in the denial of contract renewal after 10 years – at least for the 2nd round participants. If you prove your public interest through public availability (via defined launch periods) – but do not enact any: you have failed to serve the public interest. Why should ICANN renew your contract? It shouldn’t! As always: Exceptions might apply under extraordinary circumstances (Istanbul based .kurds denied to launch via court order for example). Thanks, Alexander From: Mike Rodenbaugh [mailto:mike@rodenbaugh.com] Sent: Dienstag, 18. Februar 2020 16:10 To: Alexander Schubert <alexander@schubert.berlin> Cc: gnso-newgtld-wg@icann.org Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry So-called Closed Generics (however anyone may define them) were allowed in 2012, as a Consensus Policy insofar they were very heavily debated by the GNSO for many years, including the same arguments and many of the same participants in today's debate. And Closed Generics were neither defined nor prohibited in the GNSO Consensus Policy adopted by the Board and then implemented by Staff and GNSO in the AGB. Thus, Closed Generics were essentially, explicitly allowed -- and unsurprisingly then there was some number of applicants for strings that the Board later unilaterally defined as Closed Generics. The Board then made a variance to one small part of that Consensus Policy, only as to a specifically defined subset of 2012 applications that the GAC and some others objected to. The Board specifically said that resolution had no bearing on future GNSO policy work. That resolution was never discussed or debated by the GNSO, until this PDP. So, neither the GNSO nor the Board have ever changed the 2012 Consensus Policy that allowed what some call "Closed Generics". To change it now will require consensus of this WG, which seems unlikely to happen. Mike Rodenbaugh RODENBAUGH LAW tel/fax: +1.415.738.8087 http://rodenbaugh.law On Tue, Feb 18, 2020 at 12:26 PM Alexander Schubert <alexander@schubert.berlin <mailto:alexander@schubert.berlin> > wrote: Anne, This is a contradiction. If the board denied “closed generics” (gTLD applications for generic keyword based strings) in 2012 then they did for a REASON. Unless the board specified a “conditional aspect” for that reason then the rationale for that decision hasn’t changed just because a decade went by. So the “ground rule” would be to keep the application rules as they were in 2012 – namely denying closed generics. UNLESS the gNSO develops new recommendations – which then need a new board approval. Some might argue that in 2012 the “problem” with closed generics wasn’t that bad: only a few dozen generic terms where taken by industry leaders (apparently mostly to just block off the entire vertical). So why bothering? Well: In 2012 the COST for a new gTLD was enormous! Application writing and submission wasn’t yet streamlined and expensive. Consulting (partly due to a steep “learning curve”) was expensive. Application fees alone where almost US $200k. By definition in 2012 there was no PRECEDENCE that industry leaders would snag up entire category defining killer keyword based gTLDs. The entire “new gTLD” issue was “murky”. All of this will have DRASTICALLY changed by 2022: * There will be a DECADE of public experience and exposure of the new gTLD program and new gTLDs * The consulting and application submission related fees will be DRASTICALLY lower – some consultants already offer packages lower than US $30k – which includes application writing, submission, contracting and testing! * The application fee will likely be low, too. Some already fabulize about US $25k fee floors – or even BELOW! * The “myth” that leading industry giants are massively hoarding “their” verticals (industry defining category killer generic terms) ain’t a “myth” anymore: it’s a viable truth – proven by the 2012 application roster. * Consultants will swarm out to big corporations who have ample marketing budgets and inflated egos: “If YOU are not securing ‘.CategoryDefiningKeyword’ then your competition will: be clever and have at minimum a horse in the race: let us apply for it on your behalf”. Image how incredibly STUPID the head of digital marketing of a Multi-Billion corporation looks if their smaller competitor controls “their” category keyword gTLD: this could cost him his head. In comparison for the price of a half page New York Times ad he could play hero and showcase to his board how “farsighted” he is. So if anything then the underlying “problem” that lead the board in 2012 to deny “closed generics” only got worse – MUCH worse: Lower “fees & overall cost” combined with established precedence = disaster! And while we have an obligation to keep harm away from the Internet community by continuing to deny “closed generics” that logically implies that we also make sure that in the 2nd round there will be no possibility for “effectively closed generics”: namely generic term based open applications that prove their “public interest” by promising launch periods (e.g. the Sunrise period) – but then never EXECUTE the Sunrise period – but rather are closed to the public and still allow the applicant to run 100 domains. If you have a Sunrise period in your application then you ought to execute that in a reasonable frame of time – or else you render the gTLD “closed”. I suggest we provide 12 month (extendable by another 12 month if reasons are provided for the delay) to launch your Sunrise (if you have one in your application) – but at BARE MINUMUM ICANN should be crystal clear that for registries that have a Sunrise in their application any “contract renewal expectation” will only apply if such Sunrise has been executed. Otherwise industry giants will simply snag up category defining keyword based gTLDs – and leave them inactive – just to make sure they “control the namespace”. Or they use their 100 domains and effectively run it as closed generic. If the general public (or Congress for that matter) would get wind of how sloppy we are protecting the public interest here: they would go bananas. Thanks, Alexander From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org <mailto:gnso-newgtld-wg-bounces@icann.org> ] On Behalf Of Aikman-Scalese, Anne Sent: Dienstag, 18. Februar 2020 12:16 To: Kathy Kleiman <kathy@kathykleiman.com <mailto:kathy@kathykleiman.com> >; gnso-newgtld-wg@icann.org <mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry HI Kathy, I do think it’s important for the WG to understand what Jeff’s position is procedurally on this topic. It appears to me that Paul is correct that there was no policy against Closed Generics in 2012 and that the Board resolution is limited to the 2012 round. So if we stick with the “ground rules” of the PDP, it appears that the next round will be “open season” for Closed Generic applications. This is especially important to consider now that the Working Group has taken a “rough consensus” position (with some of us dissenting) that going forward, if a string is applied for in the next round, that application will act as a complete bar to applications for the same string in any subsequent round. I would strongly advocate for skipping this topic in the next call and scheduling it for the F2F meeting. Anne From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org <mailto:gnso-newgtld-wg-bounces@icann.org> > On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 8:36 AM To: gnso-newgtld-wg@icann.org <mailto:gnso-newgtld-wg@icann.org> Subject: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry [EXTERNAL] _____ As we revisit the topic of Closed Generics, I would like to share a few thoughts as a reminder on how this issue (of "generic words") has been dealt with in other forums. This is a long-established issue... 1) Trademark Manual of Examining Procedure, US Trademark Office: "Generic terms are incapable of functioning as marks denoting source, and are not registrable on the Principal Register under §2(f) or on the Supplemental Register." 807.14(e)(ii) 2) Our own Community Objection process reviewed and raised the same deep concerns for gTLDs in which the applicant (a competitor in a field) ICC New gTLD Community Objections determination: "The establishment of unrestricted, exclusive rights to a gTLD that is strongly associated with a certain community or communities, particularly where those communities are, or are likely to be, active in the Internet sphere seems to me inherently detrimental to those communities' interests." [Note: the "communities" being referred to here are commercial communities. The issue of a closed .MOBILE was raised by the CTIA which represents the US mobile wireless industry. 1-1316-6133 Best, Kathy _____ 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@icann.org <mailto:Gnso-newgtld-wg@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.

It also does not say that the "rules" of the last round should change. They perhaps should just be made more explicit, though I hesitate to start creating a list of what types of applications are acceptable. It was the better view then, and still now, that everything is acceptable unless its prohibited. That is The Rule, imho. Of course, cynics among us will point out that the Board can always later decide something else, as they repeatedly did last time and probably can't help themselves from doing next time. Mike Rodenbaugh RODENBAUGH LAW tel/fax: +1.415.738.8087 http://rodenbaugh.law On Tue, Feb 18, 2020 at 2:39 PM Marc Trachtenberg via Gnso-newgtld-wg < gnso-newgtld-wg@icann.org> wrote:

Alex,

Maybe I am missing something but where in *“…. will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” *does the Board clearly say that there is a SEVERE PROBLEM with closed generics?

Best regards,

*Marc H. Trachtenberg* Shareholder Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 Tel 312.456.1020

Mobile 773.677.3305

trac@gtlaw.com | www.gtlaw.com

[image: Greenberg Traurig]

*From:* Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] *On Behalf Of *Alexander Schubert *Sent:* Tuesday, February 18, 2020 4:10 PM *To:* gnso-newgtld-wg@icann.org *Subject:* Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

**EXTERNAL TO GT**

Dear Group,

Here from the June 2015 board meeting resolutions (these are quotes directly from the ICANN.org website):

https://www.icann.org/resources/board-material/resolutions-new-gtld-2015-06-... <https://urldefense.com/v3/__https://www.icann.org/resources/board-material/r...>

*Advise Exclusive Generic Applicants for non-contended strings, or Exclusive Generic Applicants prevailing in contention resolution that they must elect within a reasonably limited time to either:*

* submit a change request to no longer be an exclusive generic TLD, and sign the current form of the New gTLD Registry Agreement;*

* maintain their plan to operate an exclusive generic TLD. As a result, their application **will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs**; or*

* withdraw their application for a refund consistent with the refund schedule in the Applicant Guidebook.*

I would like to draw emphasis to:

*“…. will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….”*

The board clearly states that there is a SEVERE PROBLEM, that it denies closed generic applications, that those REMAIN ineligible UNTIL the GNSO has “developed advice concerning exclusive generic gTLDs”. Hairsplitters could argue that this is only true for the 2012 roster. But hey: come on.

This is in striking contrast to the assentation that the ineligibility where to be restricted to the 2012 round only. The board INSTRUCTED the gNSO to “develop policy advice concerning exclusive generic TLD”, so in absence of a consensus around such policy advice it is self-evident that the board’s concerns aren’t addressed at all; and their “ban” stays active (or we force them to activate it yet again)

We run the risk to look incompetent if we run into this knife yet again: if we (like suggested by some here) maintain that our 2007 PDP was “flawless” – and that we have to repeat this obvious mistake (allowing closed generics) again; then here what will happen:

- GAC will point out the same as it has done in the 2012 round: asking the board to deny closed generics! - The board will note that the gNSO has denied their explicit request to develop new policy advice; and as a result will deny closed generics AGAIN! - This creates MASSIVE confusion for applicants; something that we should allow

I assume it would be best if we abide by the Board request to “develop policy advice concerning exclusive generic TLD”. A subgroup was initiated last year – I am in there; but the group was inactive so far. We simply should create policy advice. If there is a consensus around under what set of circumstances allowing closed generics: fine! Then we allow them. If there is no consensus: then I guess we have established just that: No consensus to allow closed generics.

Here a bit more from the June 2015 board resolutions:

*A Policy Development Process with respect to operating exclusive generic strings in the "public interest" should be undertaken by the community. Policy issues on "closed generic" TLDs should be resolved through the multistakeholder process.*

*The public interest goal requirement as stated is too general and requires greater specificity for enforceability**. The NGPC should add relevant meaning to the "public interest" concept by applying the GNSO rationales regarding the promotion of competition, consumer choice, market differentiation, and geographical and service provider diversity as standards for such affirmative objective showings and findings.*

* Safeguards are important when applicants have chosen to apply for closed control of a generic term designating a particular industry where the applicant is engaged in the conduct of business activities in that industry.*

* Requiring applicants to demonstrate some additional public interest goal in the context of exclusive registry access for generic strings would reverse the deliberate choices made by the ICANN community in its bottom-up process and impose new evaluation criteria.*

* The status quo as set out in the Applicant Guidebook should apply so that **both "open" and "closed" registry access for generic strings should continue to be allowed in this first application round, but both should be subject to significant scrutiny after launch by ICANN to ensure that the interests of rights owners and consumers are protected**.*

So to say that the board decision was only pertaining the first round – but the 2nd round would be “open season for anything” is ignoring the board’s very clear advice. Board resolutions are our “safety valve” – we should try to establish our policies in a way that doesn’t require the board to issue them.

And while we are at it:

Submitting a generic term based gTLD application, trying to “prove public interest” by implementing clear launch phases (e.g. Sunrise), then never living up to such commitment: Should result in the denial of contract renewal after 10 years – at least for the 2nd round participants. If you prove your public interest through public availability (via defined launch periods) – but do not enact any: you have failed to serve the public interest. Why should ICANN renew your contract? It shouldn’t! As always: Exceptions might apply under extraordinary circumstances (Istanbul based .kurds denied to launch via court order for example).

Thanks,

Alexander

*From:* Mike Rodenbaugh [mailto:mike@rodenbaugh.com <mike@rodenbaugh.com>]

*Sent:* Dienstag, 18. Februar 2020 16:10 *To:* Alexander Schubert <alexander@schubert.berlin> *Cc:* gnso-newgtld-wg@icann.org *Subject:* Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

So-called Closed Generics (however anyone may define them) were allowed in 2012, as a Consensus Policy insofar they were very heavily debated by the GNSO for many years, including the same arguments and many of the same participants in today's debate. And Closed Generics were neither defined nor prohibited in the GNSO Consensus Policy adopted by the Board and then implemented by Staff and GNSO in the AGB. Thus, Closed Generics were essentially, explicitly allowed -- and unsurprisingly then there was some number of applicants for strings that the Board later unilaterally defined as Closed Generics.

The Board then made a variance to one small part of that Consensus Policy, only as to a specifically defined subset of 2012 applications that the GAC and some others objected to. The Board specifically said that resolution had no bearing on future GNSO policy work. That resolution was never discussed or debated by the GNSO, until this PDP. So, neither the GNSO nor the Board have ever changed the 2012 Consensus Policy that allowed what some call "Closed Generics". To change it now will require consensus of this WG, which seems unlikely to happen.

Mike Rodenbaugh

RODENBAUGH LAW

tel/fax: +1.415.738.8087

http://rodenbaugh.law <https://urldefense.com/v3/__http:/rodenbaugh.law__;!!DUT_TFPxUQ!TJdk660_rz8Q...>

On Tue, Feb 18, 2020 at 12:26 PM Alexander Schubert < alexander@schubert.berlin> wrote:

Anne,

This is a contradiction. If the board denied “closed generics” (gTLD applications for generic keyword based strings) in 2012 then they did for a REASON. Unless the board specified a “conditional aspect” for that reason then the rationale for that decision hasn’t changed just because a decade went by. So the “ground rule” would be to keep the application rules as they were in 2012 – namely denying closed generics. UNLESS the gNSO develops new recommendations – which then need a new board approval.

Some might argue that in 2012 the “problem” with closed generics wasn’t that bad: only a few dozen generic terms where taken by industry leaders (apparently mostly to just block off the entire vertical). So why bothering?

Well: In 2012 the COST for a new gTLD was enormous! Application writing and submission wasn’t yet streamlined and expensive. Consulting (partly due to a steep “learning curve”) was expensive. Application fees alone where almost US $200k. By definition in 2012 there was no PRECEDENCE that industry leaders would snag up entire category defining killer keyword based gTLDs. The entire “new gTLD” issue was “murky”.

All of this will have DRASTICALLY changed by 2022:

· There will be a DECADE of public experience and exposure of the new gTLD program and new gTLDs

· The consulting and application submission related fees will be DRASTICALLY lower – some consultants already offer packages lower than US $30k – which includes application writing, submission, contracting and testing!

· The application fee will likely be low, too. Some already fabulize about US $25k fee floors – or even BELOW!

· The “myth” that leading industry giants are massively hoarding “their” verticals (industry defining category killer generic terms) ain’t a “myth” anymore: it’s a viable truth – proven by the 2012 application roster.

· Consultants will swarm out to big corporations who have ample marketing budgets and inflated egos: “If YOU are not securing ‘.CategoryDefiningKeyword’ then your competition will: be clever and have at minimum a horse in the race: let us apply for it on your behalf”. Image how incredibly STUPID the head of digital marketing of a Multi-Billion corporation looks if their smaller competitor controls “their” category keyword gTLD: this could cost him his head. In comparison for the price of a half page New York Times ad he could play hero and showcase to his board how “farsighted” he is.

So if anything then the underlying “problem” that lead the board in 2012 to deny “closed generics” only got worse – MUCH worse: Lower “fees & overall cost” combined with established precedence = disaster!

And while we have an obligation to keep harm away from the Internet community by continuing to deny “closed generics” that logically implies that we also make sure that in the 2nd round there will be no possibility for “effectively closed generics”: namely generic term based open applications that prove their “public interest” by promising launch periods (e.g. the Sunrise period) – but then never EXECUTE the Sunrise period – but rather are closed to the public and still allow the applicant to run 100 domains. If you have a Sunrise period in your application then you ought to execute that in a reasonable frame of time – or else you render the gTLD “closed”. I suggest we provide 12 month (extendable by another 12 month if reasons are provided for the delay) to launch your Sunrise (if you have one in your application) – but at BARE MINUMUM ICANN should be crystal clear that for registries that have a Sunrise in their application any “contract renewal expectation” will only apply if such Sunrise has been executed. Otherwise industry giants will simply snag up category defining keyword based gTLDs – and leave them inactive – just to make sure they “control the namespace”. Or they use their 100 domains and effectively run it as closed generic.

If the general public (or Congress for that matter) would get wind of how sloppy we are protecting the public interest here: they would go bananas.

Thanks,

Alexander

*From:* Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] *On Behalf Of *Aikman-Scalese, Anne *Sent:* Dienstag, 18. Februar 2020 12:16 *To:* Kathy Kleiman <kathy@kathykleiman.com>; gnso-newgtld-wg@icann.org *Subject:* Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

HI Kathy,

I do think it’s important for the WG to understand what Jeff’s position is procedurally on this topic. It appears to me that Paul is correct that there was no policy against Closed Generics in 2012 and that the Board resolution is limited to the 2012 round. So if we stick with the “ground rules” of the PDP, it appears that the next round will be “open season” for Closed Generic applications. This is especially important to consider now that the Working Group has taken a “rough consensus” position (with some of us dissenting) that going forward, if a string is applied for in the next round, that application will act as a complete bar to applications for the same string in any subsequent round.

I would strongly advocate for skipping this topic in the next call and scheduling it for the F2F meeting.

Anne

*From:* Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> *On Behalf Of *Kathy Kleiman *Sent:* Tuesday, February 18, 2020 8:36 AM *To:* gnso-newgtld-wg@icann.org *Subject:* [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

*[EXTERNAL]* ------------------------------

As we revisit the topic of Closed Generics, I would like to share a few thoughts as a reminder on how this issue (of "generic words") has been dealt with in other forums. This is a long-established issue...

1) Trademark Manual of Examining Procedure, US Trademark Office:

"Generic terms are incapable of functioning as marks denoting source, and are not registrable on the Principal Register under §2(f) or on the Supplemental Register." 807.14(e)(ii)

2) Our own Community Objection process reviewed and raised the same deep concerns for gTLDs in which the applicant (a competitor in a field)

ICC New gTLD Community Objections determination: "The establishment of unrestricted, exclusive rights to a gTLD that is strongly associated with a certain community or communities, particularly where those communities are, or are likely to be, active in the Internet sphere *seems to me inherently detrimental to those communities' interests." [Note: the "communities" being referred to here are commercial communities. The issue of a closed .MOBILE was raised by the CTIA which represents the US mobile wireless industry. *1-1316-6133

Best, Kathy

------------------------------

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@icann.org https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg <https://urldefense.com/v3/__https:/mm.icann.org/mailman/listinfo/gnso-newgtl...> _______________________________________________ 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:/www.icann.org/privacy/policy__;!!DUT_TFPx...>) and the website Terms of Service (https://www.icann.org/privacy/tos <https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!DUT_TFPxUQ!...>). 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.

------------------------------ If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster@gtlaw.com, and do not use or disseminate the information. _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg@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.

Without expressing any view on the substance I think it is hard to describe the board’s action in 2012 as adoption of “consensus policy.” The board cannot create policy, but it can reject gnso policy recommendations on public interest grounds. So the board either rejected a policy permitting open generics or it rejected the absence of an articulated gnso policy - I don’t know the facts enough to say which. Becky Burr Sent from my iPhone

On Feb 18, 2020, at 17:48, Aikman-Scalese, Anne <AAikman@lrrc.com> wrote:

 in the 2012 AGB, the Board reserved the right to refuse any application it deems “not in the public interest”. I doubt that is going to change in the next AGB no matter what we do.

Agree with Marc that we can’t determine application of the Neuman Rule on a case-by-case basis. If we need to add a corollary to the Rule, and if the full Board itself did not act, it should probably depend on whether the New gTLD Program Committee endorsed the practice because the Board delegated full authority to them. Anne

From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> On Behalf Of Mike Rodenbaugh Sent: Tuesday, February 18, 2020 3:43 PM To: Marc H. Trachtenberg <trachtenbergm@gtlaw.com> Cc: gnso-newgtld-wg@icann.org Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

[EXTERNAL] It also does not say that the "rules" of the last round should change. They perhaps should just be made more explicit, though I hesitate to start creating a list of what types of applications are acceptable. It was the better view then, and still now, that everything is acceptable unless its prohibited. That is The Rule, imho. Of course, cynics among us will point out that the Board can always later decide something else, as they repeatedly did last time and probably can't help themselves from doing next time.

Mike Rodenbaugh RODENBAUGH LAW tel/fax: +1.415.738.8087 http://rodenbaugh.law

On Tue, Feb 18, 2020 at 2:39 PM Marc Trachtenberg via Gnso-newgtld-wg <gnso-newgtld-wg@icann.org> wrote: Alex,

Maybe I am missing something but where in “…. will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” does the Board clearly say that there is a SEVERE PROBLEM with closed generics?

Best regards,

Marc H. Trachtenberg Shareholder Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 Tel 312.456.1020 Mobile 773.677.3305 trac@gtlaw.com | www.gtlaw.com

<image001.jpg>

From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Alexander Schubert Sent: Tuesday, February 18, 2020 4:10 PM To: gnso-newgtld-wg@icann.org Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

*EXTERNAL TO GT*

Dear Group,

Here from the June 2015 board meeting resolutions (these are quotes directly from the ICANN.org website): https://www.icann.org/resources/board-material/resolutions-new-gtld-2015-06-...

Advise Exclusive Generic Applicants for non-contended strings, or Exclusive Generic Applicants prevailing in contention resolution that they must elect within a reasonably limited time to either:

submit a change request to no longer be an exclusive generic TLD, and sign the current form of the New gTLD Registry Agreement;

maintain their plan to operate an exclusive generic TLD. As a result, their application will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs; or

withdraw their application for a refund consistent with the refund schedule in the Applicant Guidebook.

I would like to draw emphasis to:

“…. will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….”

The board clearly states that there is a SEVERE PROBLEM, that it denies closed generic applications, that those REMAIN ineligible UNTIL the GNSO has “developed advice concerning exclusive generic gTLDs”. Hairsplitters could argue that this is only true for the 2012 roster. But hey: come on.

This is in striking contrast to the assentation that the ineligibility where to be restricted to the 2012 round only. The board INSTRUCTED the gNSO to “develop policy advice concerning exclusive generic TLD”, so in absence of a consensus around such policy advice it is self-evident that the board’s concerns aren’t addressed at all; and their “ban” stays active (or we force them to activate it yet again)

We run the risk to look incompetent if we run into this knife yet again: if we (like suggested by some here) maintain that our 2007 PDP was “flawless” – and that we have to repeat this obvious mistake (allowing closed generics) again; then here what will happen: GAC will point out the same as it has done in the 2012 round: asking the board to deny closed generics! The board will note that the gNSO has denied their explicit request to develop new policy advice; and as a result will deny closed generics AGAIN! This creates MASSIVE confusion for applicants; something that we should allow

I assume it would be best if we abide by the Board request to “develop policy advice concerning exclusive generic TLD”. A subgroup was initiated last year – I am in there; but the group was inactive so far. We simply should create policy advice. If there is a consensus around under what set of circumstances allowing closed generics: fine! Then we allow them. If there is no consensus: then I guess we have established just that: No consensus to allow closed generics.

Here a bit more from the June 2015 board resolutions:

A Policy Development Process with respect to operating exclusive generic strings in the "public interest" should be undertaken by the community. Policy issues on "closed generic" TLDs should be resolved through the multistakeholder process.

The public interest goal requirement as stated is too general and requires greater specificity for enforceability. The NGPC should add relevant meaning to the "public interest" concept by applying the GNSO rationales regarding the promotion of competition, consumer choice, market differentiation, and geographical and service provider diversity as standards for such affirmative objective showings and findings.

Safeguards are important when applicants have chosen to apply for closed control of a generic term designating a particular industry where the applicant is engaged in the conduct of business activities in that industry.

Requiring applicants to demonstrate some additional public interest goal in the context of exclusive registry access for generic strings would reverse the deliberate choices made by the ICANN community in its bottom-up process and impose new evaluation criteria.

The status quo as set out in the Applicant Guidebook should apply so that both "open" and "closed" registry access for generic strings should continue to be allowed in this first application round, but both should be subject to significant scrutiny after launch by ICANN to ensure that the interests of rights owners and consumers are protected.

So to say that the board decision was only pertaining the first round – but the 2nd round would be “open season for anything” is ignoring the board’s very clear advice. Board resolutions are our “safety valve” – we should try to establish our policies in a way that doesn’t require the board to issue them.

And while we are at it: Submitting a generic term based gTLD application, trying to “prove public interest” by implementing clear launch phases (e.g. Sunrise), then never living up to such commitment: Should result in the denial of contract renewal after 10 years – at least for the 2nd round participants. If you prove your public interest through public availability (via defined launch periods) – but do not enact any: you have failed to serve the public interest. Why should ICANN renew your contract? It shouldn’t! As always: Exceptions might apply under extraordinary circumstances (Istanbul based .kurds denied to launch via court order for example).

Thanks,

Alexander

From: Mike Rodenbaugh [mailto:mike@rodenbaugh.com] Sent: Dienstag, 18. Februar 2020 16:10 To: Alexander Schubert <alexander@schubert.berlin> Cc: gnso-newgtld-wg@icann.org Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

So-called Closed Generics (however anyone may define them) were allowed in 2012, as a Consensus Policy insofar they were very heavily debated by the GNSO for many years, including the same arguments and many of the same participants in today's debate. And Closed Generics were neither defined nor prohibited in the GNSO Consensus Policy adopted by the Board and then implemented by Staff and GNSO in the AGB. Thus, Closed Generics were essentially, explicitly allowed -- and unsurprisingly then there was some number of applicants for strings that the Board later unilaterally defined as Closed Generics.

The Board then made a variance to one small part of that Consensus Policy, only as to a specifically defined subset of 2012 applications that the GAC and some others objected to. The Board specifically said that resolution had no bearing on future GNSO policy work. That resolution was never discussed or debated by the GNSO, until this PDP. So, neither the GNSO nor the Board have ever changed the 2012 Consensus Policy that allowed what some call "Closed Generics". To change it now will require consensus of this WG, which seems unlikely to happen.

Mike Rodenbaugh RODENBAUGH LAW tel/fax: +1.415.738.8087 http://rodenbaugh.law

On Tue, Feb 18, 2020 at 12:26 PM Alexander Schubert <alexander@schubert.berlin> wrote: Anne,

This is a contradiction. If the board denied “closed generics” (gTLD applications for generic keyword based strings) in 2012 then they did for a REASON. Unless the board specified a “conditional aspect” for that reason then the rationale for that decision hasn’t changed just because a decade went by. So the “ground rule” would be to keep the application rules as they were in 2012 – namely denying closed generics. UNLESS the gNSO develops new recommendations – which then need a new board approval.

Some might argue that in 2012 the “problem” with closed generics wasn’t that bad: only a few dozen generic terms where taken by industry leaders (apparently mostly to just block off the entire vertical). So why bothering?

Well: In 2012 the COST for a new gTLD was enormous! Application writing and submission wasn’t yet streamlined and expensive. Consulting (partly due to a steep “learning curve”) was expensive. Application fees alone where almost US $200k. By definition in 2012 there was no PRECEDENCE that industry leaders would snag up entire category defining killer keyword based gTLDs. The entire “new gTLD” issue was “murky”.

All of this will have DRASTICALLY changed by 2022: · There will be a DECADE of public experience and exposure of the new gTLD program and new gTLDs

· The consulting and application submission related fees will be DRASTICALLY lower – some consultants already offer packages lower than US $30k – which includes application writing, submission, contracting and testing!

· The application fee will likely be low, too. Some already fabulize about US $25k fee floors – or even BELOW!

· The “myth” that leading industry giants are massively hoarding “their” verticals (industry defining category killer generic terms) ain’t a “myth” anymore: it’s a viable truth – proven by the 2012 application roster.

· Consultants will swarm out to big corporations who have ample marketing budgets and inflated egos: “If YOU are not securing ‘.CategoryDefiningKeyword’ then your competition will: be clever and have at minimum a horse in the race: let us apply for it on your behalf”. Image how incredibly STUPID the head of digital marketing of a Multi-Billion corporation looks if their smaller competitor controls “their” category keyword gTLD: this could cost him his head. In comparison for the price of a half page New York Times ad he could play hero and showcase to his board how “farsighted” he is.

So if anything then the underlying “problem” that lead the board in 2012 to deny “closed generics” only got worse – MUCH worse: Lower “fees & overall cost” combined with established precedence = disaster!

And while we have an obligation to keep harm away from the Internet community by continuing to deny “closed generics” that logically implies that we also make sure that in the 2nd round there will be no possibility for “effectively closed generics”: namely generic term based open applications that prove their “public interest” by promising launch periods (e.g. the Sunrise period) – but then never EXECUTE the Sunrise period – but rather are closed to the public and still allow the applicant to run 100 domains. If you have a Sunrise period in your application then you ought to execute that in a reasonable frame of time – or else you render the gTLD “closed”. I suggest we provide 12 month (extendable by another 12 month if reasons are provided for the delay) to launch your Sunrise (if you have one in your application) – but at BARE MINUMUM ICANN should be crystal clear that for registries that have a Sunrise in their application any “contract renewal expectation” will only apply if such Sunrise has been executed. Otherwise industry giants will simply snag up category defining keyword based gTLDs – and leave them inactive – just to make sure they “control the namespace”. Or they use their 100 domains and effectively run it as closed generic.

If the general public (or Congress for that matter) would get wind of how sloppy we are protecting the public interest here: they would go bananas.

Thanks,

Alexander

From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Aikman-Scalese, Anne Sent: Dienstag, 18. Februar 2020 12:16 To: Kathy Kleiman <kathy@kathykleiman.com>; gnso-newgtld-wg@icann.org Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

HI Kathy, I do think it’s important for the WG to understand what Jeff’s position is procedurally on this topic. It appears to me that Paul is correct that there was no policy against Closed Generics in 2012 and that the Board resolution is limited to the 2012 round. So if we stick with the “ground rules” of the PDP, it appears that the next round will be “open season” for Closed Generic applications. This is especially important to consider now that the Working Group has taken a “rough consensus” position (with some of us dissenting) that going forward, if a string is applied for in the next round, that application will act as a complete bar to applications for the same string in any subsequent round.

I would strongly advocate for skipping this topic in the next call and scheduling it for the F2F meeting.

Anne

From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org> On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 8:36 AM To: gnso-newgtld-wg@icann.org Subject: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

[EXTERNAL] As we revisit the topic of Closed Generics, I would like to share a few thoughts as a reminder on how this issue (of "generic words") has been dealt with in other forums. This is a long-established issue...

1) Trademark Manual of Examining Procedure, US Trademark Office:

"Generic terms are incapable of functioning as marks denoting source, and are not registrable on the Principal Register under §2(f) or on the Supplemental Register." 807.14(e)(ii)

2) Our own Community Objection process reviewed and raised the same deep concerns for gTLDs in which the applicant (a competitor in a field)

ICC New gTLD Community Objections determination: "The establishment of unrestricted, exclusive rights to a gTLD that is strongly associated with a certain community or communities, particularly where those communities are, or are likely to be, active in the Internet sphere seems to me inherently detrimental to those communities' interests." [Note: the "communities" being referred to here are commercial communities. The issue of a closed .MOBILE was raised by the CTIA which represents the US mobile wireless industry. 1-1316-6133

Best, Kathy

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@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. If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster@gtlaw.com, and do not use or disseminate the information. _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg@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@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.

Or, we could discuss each issue trying to reach a consensus instead of thinking what happens if we don't. Rubens

Em 19 de fev de 2020, à(s) 13:35:000, Aikman-Scalese, Anne <AAikman@lrrc.com> escreveu:

Thanks Becky. This is helpful. I think the WG is still struggling with what constitutes the “fallback” where there is No Consensus in the WG. This procedural point has to be worked out in order to arrive at a document for public comment. Jeff’s point re Closed Generics is that the Board resolution was limited to the 2012 round and the Board stated an expectation that GNSO would make policy. So far the WG has not succeeded in making a new policy re Closed Generics. Hopefully we will be able to discuss Alan’s proposal in the F2F meeting.

The general issue of how to express the WG conclusion re items that are still outstanding as to which there is “No Consensus” still stands, e.g. as to idns and how idn policy/implementation evolved in the 2012 round. In addition to the fact that the “Neuman Rule” has been the operating assumption of all WG members for years, I believe consistent application of governance principles would require the WG, in cases where No Consensus is reached, to determine whether the Board (or the new gTLD Program Committee as the non-conflicted subset of Board members who were delegated total authority over the program by the Board) acted on the particular issue. If that is the case, then that is the only practical “fallback” for the WG in cases of No Consensus. This view is “issue neutral” and based on consistent application of a principle rather than on specific issue outcomes. The issues that will be affected by the approach taken are numerous.

If we don’t develop a principle for consistent application of the “Neuman Rule”, we will incur greater delay as either (a) the WG will argue each issue based on selective interests and/or (b) there will be significant gaps in policy that will delay the next round and force the Board to (i) determine an approach in the public interest or (ii) send the issue back to the GNSO and say “you haven’t finished your work”.

Anne

From: Becky Burr <becky.burr@board.icann.org <mailto:becky.burr@board.icann.org>> Sent: Tuesday, February 18, 2020 7:00 PM To: Aikman-Scalese, Anne <AAikman@lrrc.com <mailto:AAikman@lrrc.com>> Cc: Mike Rodenbaugh <mike@rodenbaugh.com <mailto:mike@rodenbaugh.com>>; Marc H. Trachtenberg <trachtenbergm@gtlaw.com <mailto:trachtenbergm@gtlaw.com>>; gnso-newgtld-wg@icann.org <mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

[EXTERNAL] Without expressing any view on the substance I think it is hard to describe the board’s action in 2012 as adoption of “consensus policy.” The board cannot create policy, but it can reject gnso policy recommendations on public interest grounds. So the board either rejected a policy permitting open generics or it rejected the absence of an articulated gnso policy - I don’t know the facts enough to say which.

Becky Burr Sent from my iPhone

On Feb 18, 2020, at 17:48, Aikman-Scalese, Anne <AAikman@lrrc.com <mailto:AAikman@lrrc.com>> wrote:

 in the 2012 AGB, the Board reserved the right to refuse any application it deems “not in the public interest”. I doubt that is going to change in the next AGB no matter what we do.

Agree with Marc that we can’t determine application of the Neuman Rule on a case-by-case basis. If we need to add a corollary to the Rule, and if the full Board itself did not act, it should probably depend on whether the New gTLD Program Committee endorsed the practice because the Board delegated full authority to them. Anne

From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org <mailto:gnso-newgtld-wg-bounces@icann.org>> On Behalf Of Mike Rodenbaugh Sent: Tuesday, February 18, 2020 3:43 PM To: Marc H. Trachtenberg <trachtenbergm@gtlaw.com <mailto:trachtenbergm@gtlaw.com>> Cc: gnso-newgtld-wg@icann.org <mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

[EXTERNAL] It also does not say that the "rules" of the last round should change. They perhaps should just be made more explicit, though I hesitate to start creating a list of what types of applications are acceptable. It was the better view then, and still now, that everything is acceptable unless its prohibited. That is The Rule, imho. Of course, cynics among us will point out that the Board can always later decide something else, as they repeatedly did last time and probably can't help themselves from doing next time.

Mike Rodenbaugh RODENBAUGH LAW tel/fax: +1.415.738.8087 http://rodenbaugh.law <http://rodenbaugh.law/>

On Tue, Feb 18, 2020 at 2:39 PM Marc Trachtenberg via Gnso-newgtld-wg <gnso-newgtld-wg@icann.org <mailto:gnso-newgtld-wg@icann.org>> wrote: Alex, <>

Maybe I am missing something but where in “…. will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” does the Board clearly say that there is a SEVERE PROBLEM with closed generics?

Best regards,

Marc H. Trachtenberg Shareholder Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 Tel 312.456.1020 Mobile 773.677.3305 trac@gtlaw.com <mailto:trac@gtlaw.com> | www.gtlaw.com <http://www.gtlaw.com/>

<image001.jpg>

From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org <mailto:gnso-newgtld-wg-bounces@icann.org>] On Behalf Of Alexander Schubert Sent: Tuesday, February 18, 2020 4:10 PM To: gnso-newgtld-wg@icann.org <mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

*EXTERNAL TO GT*

Dear Group,

Here from the June 2015 board meeting resolutions (these are quotes directly from the ICANN.org website): https://www.icann.org/resources/board-material/resolutions-new-gtld-2015-06-... <https://urldefense.com/v3/__https:/www.icann.org/resources/board-material/re...>

Advise Exclusive Generic Applicants for non-contended strings, or Exclusive Generic Applicants prevailing in contention resolution that they must elect within a reasonably limited time to either:

submit a change request to no longer be an exclusive generic TLD, and sign the current form of the New gTLD Registry Agreement;

maintain their plan to operate an exclusive generic TLD. As a result, their application will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs; or

withdraw their application for a refund consistent with the refund schedule in the Applicant Guidebook.

I would like to draw emphasis to:

“…. will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….”

The board clearly states that there is a SEVERE PROBLEM, that it denies closed generic applications, that those REMAIN ineligible UNTIL the GNSO has “developed advice concerning exclusive generic gTLDs”. Hairsplitters could argue that this is only true for the 2012 roster. But hey: come on.

This is in striking contrast to the assentation that the ineligibility where to be restricted to the 2012 round only. The board INSTRUCTED the gNSO to “develop policy advice concerning exclusive generic TLD”, so in absence of a consensus around such policy advice it is self-evident that the board’s concerns aren’t addressed at all; and their “ban” stays active (or we force them to activate it yet again)

We run the risk to look incompetent if we run into this knife yet again: if we (like suggested by some here) maintain that our 2007 PDP was “flawless” – and that we have to repeat this obvious mistake (allowing closed generics) again; then here what will happen: GAC will point out the same as it has done in the 2012 round: asking the board to deny closed generics! The board will note that the gNSO has denied their explicit request to develop new policy advice; and as a result will deny closed generics AGAIN! This creates MASSIVE confusion for applicants; something that we should allow

I assume it would be best if we abide by the Board request to “develop policy advice concerning exclusive generic TLD”. A subgroup was initiated last year – I am in there; but the group was inactive so far. We simply should create policy advice. If there is a consensus around under what set of circumstances allowing closed generics: fine! Then we allow them. If there is no consensus: then I guess we have established just that: No consensus to allow closed generics.

Here a bit more from the June 2015 board resolutions:

A Policy Development Process with respect to operating exclusive generic strings in the "public interest" should be undertaken by the community. Policy issues on "closed generic" TLDs should be resolved through the multistakeholder process.

The public interest goal requirement as stated is too general and requires greater specificity for enforceability. The NGPC should add relevant meaning to the "public interest" concept by applying the GNSO rationales regarding the promotion of competition, consumer choice, market differentiation, and geographical and service provider diversity as standards for such affirmative objective showings and findings.

Safeguards are important when applicants have chosen to apply for closed control of a generic term designating a particular industry where the applicant is engaged in the conduct of business activities in that industry.

Requiring applicants to demonstrate some additional public interest goal in the context of exclusive registry access for generic strings would reverse the deliberate choices made by the ICANN community in its bottom-up process and impose new evaluation criteria.

The status quo as set out in the Applicant Guidebook should apply so that both "open" and "closed" registry access for generic strings should continue to be allowed in this first application round, but both should be subject to significant scrutiny after launch by ICANN to ensure that the interests of rights owners and consumers are protected.

So to say that the board decision was only pertaining the first round – but the 2nd round would be “open season for anything” is ignoring the board’s very clear advice. Board resolutions are our “safety valve” – we should try to establish our policies in a way that doesn’t require the board to issue them.

And while we are at it: Submitting a generic term based gTLD application, trying to “prove public interest” by implementing clear launch phases (e.g. Sunrise), then never living up to such commitment: Should result in the denial of contract renewal after 10 years – at least for the 2nd round participants. If you prove your public interest through public availability (via defined launch periods) – but do not enact any: you have failed to serve the public interest. Why should ICANN renew your contract? It shouldn’t! As always: Exceptions might apply under extraordinary circumstances (Istanbul based .kurds denied to launch via court order for example).

Thanks,

Alexander

From: Mike Rodenbaugh [mailto:mike@rodenbaugh.com <mailto:mike@rodenbaugh.com>] Sent: Dienstag, 18. Februar 2020 16:10 To: Alexander Schubert <alexander@schubert.berlin <mailto:alexander@schubert.berlin>> Cc: gnso-newgtld-wg@icann.org <mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

So-called Closed Generics (however anyone may define them) were allowed in 2012, as a Consensus Policy insofar they were very heavily debated by the GNSO for many years, including the same arguments and many of the same participants in today's debate. And Closed Generics were neither defined nor prohibited in the GNSO Consensus Policy adopted by the Board and then implemented by Staff and GNSO in the AGB. Thus, Closed Generics were essentially, explicitly allowed -- and unsurprisingly then there was some number of applicants for strings that the Board later unilaterally defined as Closed Generics.

The Board then made a variance to one small part of that Consensus Policy, only as to a specifically defined subset of 2012 applications that the GAC and some others objected to. The Board specifically said that resolution had no bearing on future GNSO policy work. That resolution was never discussed or debated by the GNSO, until this PDP. So, neither the GNSO nor the Board have ever changed the 2012 Consensus Policy that allowed what some call "Closed Generics". To change it now will require consensus of this WG, which seems unlikely to happen.

Mike Rodenbaugh RODENBAUGH LAW tel/fax: +1.415.738.8087 http://rodenbaugh.law <https://urldefense.com/v3/__http:/rodenbaugh.law__;!!DUT_TFPxUQ!TJdk660_rz8Q...>

On Tue, Feb 18, 2020 at 12:26 PM Alexander Schubert <alexander@schubert.berlin <mailto:alexander@schubert.berlin>> wrote: Anne,

This is a contradiction. If the board denied “closed generics” (gTLD applications for generic keyword based strings) in 2012 then they did for a REASON. Unless the board specified a “conditional aspect” for that reason then the rationale for that decision hasn’t changed just because a decade went by. So the “ground rule” would be to keep the application rules as they were in 2012 – namely denying closed generics. UNLESS the gNSO develops new recommendations – which then need a new board approval.

Some might argue that in 2012 the “problem” with closed generics wasn’t that bad: only a few dozen generic terms where taken by industry leaders (apparently mostly to just block off the entire vertical). So why bothering?

Well: In 2012 the COST for a new gTLD was enormous! Application writing and submission wasn’t yet streamlined and expensive. Consulting (partly due to a steep “learning curve”) was expensive. Application fees alone where almost US $200k. By definition in 2012 there was no PRECEDENCE that industry leaders would snag up entire category defining killer keyword based gTLDs. The entire “new gTLD” issue was “murky”.

All of this will have DRASTICALLY changed by 2022: · There will be a DECADE of public experience and exposure of the new gTLD program and new gTLDs

· The consulting and application submission related fees will be DRASTICALLY lower – some consultants already offer packages lower than US $30k – which includes application writing, submission, contracting and testing!

· The application fee will likely be low, too. Some already fabulize about US $25k fee floors – or even BELOW!

· The “myth” that leading industry giants are massively hoarding “their” verticals (industry defining category killer generic terms) ain’t a “myth” anymore: it’s a viable truth – proven by the 2012 application roster.

· Consultants will swarm out to big corporations who have ample marketing budgets and inflated egos: “If YOU are not securing ‘.CategoryDefiningKeyword’ then your competition will: be clever and have at minimum a horse in the race: let us apply for it on your behalf”. Image how incredibly STUPID the head of digital marketing of a Multi-Billion corporation looks if their smaller competitor controls “their” category keyword gTLD: this could cost him his head. In comparison for the price of a half page New York Times ad he could play hero and showcase to his board how “farsighted” he is.

So if anything then the underlying “problem” that lead the board in 2012 to deny “closed generics” only got worse – MUCH worse: Lower “fees & overall cost” combined with established precedence = disaster!

And while we have an obligation to keep harm away from the Internet community by continuing to deny “closed generics” that logically implies that we also make sure that in the 2nd round there will be no possibility for “effectively closed generics”: namely generic term based open applications that prove their “public interest” by promising launch periods (e.g. the Sunrise period) – but then never EXECUTE the Sunrise period – but rather are closed to the public and still allow the applicant to run 100 domains. If you have a Sunrise period in your application then you ought to execute that in a reasonable frame of time – or else you render the gTLD “closed”. I suggest we provide 12 month (extendable by another 12 month if reasons are provided for the delay) to launch your Sunrise (if you have one in your application) – but at BARE MINUMUM ICANN should be crystal clear that for registries that have a Sunrise in their application any “contract renewal expectation” will only apply if such Sunrise has been executed. Otherwise industry giants will simply snag up category defining keyword based gTLDs – and leave them inactive – just to make sure they “control the namespace”. Or they use their 100 domains and effectively run it as closed generic.

If the general public (or Congress for that matter) would get wind of how sloppy we are protecting the public interest here: they would go bananas.

Thanks,

Alexander

  <> From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org <mailto:gnso-newgtld-wg-bounces@icann.org>] On Behalf Of Aikman-Scalese, Anne Sent: Dienstag, 18. Februar 2020 12:16 To: Kathy Kleiman <kathy@kathykleiman.com <mailto:kathy@kathykleiman.com>>; gnso-newgtld-wg@icann.org <mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

HI Kathy, I do think it’s important for the WG to understand what Jeff’s position is procedurally on this topic. It appears to me that Paul is correct that there was no policy against Closed Generics in 2012 and that the Board resolution is limited to the 2012 round. So if we stick with the “ground rules” of the PDP, it appears that the next round will be “open season” for Closed Generic applications. This is especially important to consider now that the Working Group has taken a “rough consensus” position (with some of us dissenting) that going forward, if a string is applied for in the next round, that application will act as a complete bar to applications for the same string in any subsequent round.

I would strongly advocate for skipping this topic in the next call and scheduling it for the F2F meeting.

Anne

From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org <mailto:gnso-newgtld-wg-bounces@icann.org>> On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 8:36 AM To: gnso-newgtld-wg@icann.org <mailto:gnso-newgtld-wg@icann.org> Subject: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry

[EXTERNAL] As we revisit the topic of Closed Generics, I would like to share a few thoughts as a reminder on how this issue (of "generic words") has been dealt with in other forums. This is a long-established issue...

1) Trademark Manual of Examining Procedure, US Trademark Office:

"Generic terms are incapable of functioning as marks denoting source, and are not registrable on the Principal Register under §2(f) or on the Supplemental Register." 807.14(e)(ii)

2) Our own Community Objection process reviewed and raised the same deep concerns for gTLDs in which the applicant (a competitor in a field)

ICC New gTLD Community Objections determination: "The establishment of unrestricted, exclusive rights to a gTLD that is strongly associated with a certain community or communities, particularly where those communities are, or are likely to be, active in the Internet sphere seems to me inherently detrimental to those communities' interests." [Note: the "communities" being referred to here are commercial communities. The issue of a closed .MOBILE was raised by the CTIA which represents the US mobile wireless industry. 1-1316-6133

Best, Kathy

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@icann.org <mailto:Gnso-newgtld-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg <https://urldefense.com/v3/__https:/mm.icann.org/mailman/listinfo/gnso-newgtl...> _______________________________________________ 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:/www.icann.org/privacy/policy__;!!DUT_TFPx...>) and the website Terms of Service (https://www.icann.org/privacy/tos <https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!DUT_TFPxUQ!...>). 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. If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster@gtlaw.com <mailto:postmaster@gtlaw.com>, and do not use or disseminate the information. _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg@icann.org <mailto:Gnso-newgtld-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg <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@icann.org <mailto:Gnso-newgtld-wg@icann.org> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg <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@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.

Alex, Your point is completely manufactured and not based in any fact or the language that you cite. The Board did decide after the applications were submitted to not permit closed generics. You assert that this was because the issue was so problematic, that it will force applicants to either withdraw, or revert to open applications and present this as if it is a fact as opposed to just your conclusion that supports your view that every TLD and every domain name should be available to everyone as if it is a natural right. Your characterization of the Board’s action as “DRASTIC” is just that – your characterization. That Board has made many about faces and questionable decisions – are they all “DRASTIC”? Can the Board only make unexpected and questionable decisions when there is a “severe problem”? Then there must be “severe problems” all the time. Putting the drastic in CAPS does not make your assertion any more true. And what is the purpose of your repeated use of quotation marks – are you quoting yourself? As for the portion you direct us to concentrate on - “….. subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” - you again boldly mischaracterize it. This does not mean we are stuck with the status quo (assuming that no closed generics is the status quo as opposed to just applying to the first round which is another assertion you present as fact) and the Board did not make clear what the status quo ought to be despite your attempt to present it that way regardless of what the language says. In fact, if anything is clear from the language you cite, it is that the Board did not intend for no generics to be the status quo because they specifically directed (or at least contemplated) the GNSO to develop policy advice on this issue. It is also the purpose of this working group to consider procedures from the first round and whether they are appropriate for the second round. If this group had to just accept everything from the first round, Board-decided or otherwise – the group would have no purpose. And if anything is clear, it’s that this group has questioned virtually everything from the first round. Finally, your assertion that “At the very bare minimum the applicant would have to prove that their application serves the Public Interest (e.g. the .disaster example); and then the community would have to be called to decide whether the claim holds water”, this is also just your opinion and not based on anything else. To be clear, I don’t begrudge your opinion. Everyone has a right to their opinions and should have the ability to express those opinions productively in this working group as I think many in this group do, regardless if I agree with them. My opinion on closed generics happens to differ from yours but I don’t know that either view is right – they are just views. In fact, many people I like and respect share your view. What I do object to, and find offensive, is your repeated presentation of opinions and views as facts and mischaracterization of Board and community action and language in an attempt to support those views and I would ask you to stop. Best regards, Marc H. Trachtenberg Shareholder Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 Tel 312.456.1020 Mobile 773.677.3305 trac@gtlaw.com<mailto:trac@gtlaw.com> | http://www.gtlaw.com<http://www.gtlaw.com/> [Greenberg Traurig] From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Alexander Schubert Sent: Tuesday, February 18, 2020 7:35 PM To: gnso-newgtld-wg@icann.org Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry Marc, The gNSO discussed and then decided to NOT create policy around “closed generics” during the 2007 PDP. This resulted in a substantial number of applications for “closed” category defining generic term based new gTLDs. The board decided AFTER THESE APPLICATIONS WHERE SUBMITTED that the issue was so problematic, that it will force applicants to either withdraw, or revert to open applications. I would consider such measure as being “DRASTIC”. The board would have not applied such drastic measure in absence of a “severe problem”. But better concentrate on this portion: “….. subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” In absence of the development of such “rules” (which hasn’t occurred yet) we are stuck with the status quo – and the board has made very clear what that status quo ought to be: NO CLOSED GENERICS. At the very bare minimum the applicant would have to prove that their application serves the Public Interest (e.g. the .disaster example); and then the community would have to be called to decide whether the claim holds water. Thanks, Alexander From: trachtenbergm@gtlaw.com<mailto:trachtenbergm@gtlaw.com> [mailto:trachtenbergm@gtlaw.com] Sent: Dienstag, 18. Februar 2020 17:39 To: alexander@schubert.berlin<mailto:alexander@schubert.berlin>; gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry Alex, Maybe I am missing something but where in “…. will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” does the Board clearly say that there is a SEVERE PROBLEM with closed generics? Best regards, Marc H. Trachtenberg Shareholder Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 Tel 312.456.1020 Mobile 773.677.3305 trac@gtlaw.com<mailto:trac@gtlaw.com> | http://www.gtlaw.com<http://www.gtlaw.com/> [Greenberg Traurig] From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Alexander Schubert Sent: Tuesday, February 18, 2020 4:10 PM To: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry *EXTERNAL TO GT* Dear Group, Here from the June 2015 board meeting resolutions (these are quotes directly from the https://urldefense.com/v3/__http://ICANN.org__;!!DUT_TFPxUQ!X6V37iHtmn1xJuEN... website): https://urldefense.com/v3/__https://www.icann.org/resources/board-material/r... <https://urldefense.com/v3/__https:/www.icann.org/resources/board-material/re...> Advise Exclusive Generic Applicants for non-contended strings, or Exclusive Generic Applicants prevailing in contention resolution that they must elect within a reasonably limited time to either: submit a change request to no longer be an exclusive generic TLD, and sign the current form of the New gTLD Registry Agreement; maintain their plan to operate an exclusive generic TLD. As a result, their application will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs; or withdraw their application for a refund consistent with the refund schedule in the Applicant Guidebook. I would like to draw emphasis to: “…. will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” The board clearly states that there is a SEVERE PROBLEM, that it denies closed generic applications, that those REMAIN ineligible UNTIL the GNSO has “developed advice concerning exclusive generic gTLDs”. Hairsplitters could argue that this is only true for the 2012 roster. But hey: come on. This is in striking contrast to the assentation that the ineligibility where to be restricted to the 2012 round only. The board INSTRUCTED the gNSO to “develop policy advice concerning exclusive generic TLD”, so in absence of a consensus around such policy advice it is self-evident that the board’s concerns aren’t addressed at all; and their “ban” stays active (or we force them to activate it yet again) We run the risk to look incompetent if we run into this knife yet again: if we (like suggested by some here) maintain that our 2007 PDP was “flawless” – and that we have to repeat this obvious mistake (allowing closed generics) again; then here what will happen: * GAC will point out the same as it has done in the 2012 round: asking the board to deny closed generics! * The board will note that the gNSO has denied their explicit request to develop new policy advice; and as a result will deny closed generics AGAIN! * This creates MASSIVE confusion for applicants; something that we should allow I assume it would be best if we abide by the Board request to “develop policy advice concerning exclusive generic TLD”. A subgroup was initiated last year – I am in there; but the group was inactive so far. We simply should create policy advice. If there is a consensus around under what set of circumstances allowing closed generics: fine! Then we allow them. If there is no consensus: then I guess we have established just that: No consensus to allow closed generics. Here a bit more from the June 2015 board resolutions: A Policy Development Process with respect to operating exclusive generic strings in the "public interest" should be undertaken by the community. Policy issues on "closed generic" TLDs should be resolved through the multistakeholder process. The public interest goal requirement as stated is too general and requires greater specificity for enforceability. The NGPC should add relevant meaning to the "public interest" concept by applying the GNSO rationales regarding the promotion of competition, consumer choice, market differentiation, and geographical and service provider diversity as standards for such affirmative objective showings and findings. Safeguards are important when applicants have chosen to apply for closed control of a generic term designating a particular industry where the applicant is engaged in the conduct of business activities in that industry. Requiring applicants to demonstrate some additional public interest goal in the context of exclusive registry access for generic strings would reverse the deliberate choices made by the ICANN community in its bottom-up process and impose new evaluation criteria. The status quo as set out in the Applicant Guidebook should apply so that both "open" and "closed" registry access for generic strings should continue to be allowed in this first application round, but both should be subject to significant scrutiny after launch by ICANN to ensure that the interests of rights owners and consumers are protected. So to say that the board decision was only pertaining the first round – but the 2nd round would be “open season for anything” is ignoring the board’s very clear advice. Board resolutions are our “safety valve” – we should try to establish our policies in a way that doesn’t require the board to issue them. And while we are at it: Submitting a generic term based gTLD application, trying to “prove public interest” by implementing clear launch phases (e.g. Sunrise), then never living up to such commitment: Should result in the denial of contract renewal after 10 years – at least for the 2nd round participants. If you prove your public interest through public availability (via defined launch periods) – but do not enact any: you have failed to serve the public interest. Why should ICANN renew your contract? It shouldn’t! As always: Exceptions might apply under extraordinary circumstances (Istanbul based .kurds denied to launch via court order for example). Thanks, Alexander From: Mike Rodenbaugh [mailto:mike@rodenbaugh.com] Sent: Dienstag, 18. Februar 2020 16:10 To: Alexander Schubert <alexander@schubert.berlin<mailto:alexander@schubert.berlin>> Cc: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry So-called Closed Generics (however anyone may define them) were allowed in 2012, as a Consensus Policy insofar they were very heavily debated by the GNSO for many years, including the same arguments and many of the same participants in today's debate. And Closed Generics were neither defined nor prohibited in the GNSO Consensus Policy adopted by the Board and then implemented by Staff and GNSO in the AGB. Thus, Closed Generics were essentially, explicitly allowed -- and unsurprisingly then there was some number of applicants for strings that the Board later unilaterally defined as Closed Generics. The Board then made a variance to one small part of that Consensus Policy, only as to a specifically defined subset of 2012 applications that the GAC and some others objected to. The Board specifically said that resolution had no bearing on future GNSO policy work. That resolution was never discussed or debated by the GNSO, until this PDP. So, neither the GNSO nor the Board have ever changed the 2012 Consensus Policy that allowed what some call "Closed Generics". To change it now will require consensus of this WG, which seems unlikely to happen. Mike Rodenbaugh RODENBAUGH LAW tel/fax: +1.415.738.8087 https://urldefense.com/v3/__http://rodenbaugh.law__;!!DUT_TFPxUQ!X6V37iHtmn1... <https://urldefense.com/v3/__http:/rodenbaugh.law__;!!DUT_TFPxUQ!TJdk660_rz8Q...> On Tue, Feb 18, 2020 at 12:26 PM Alexander Schubert <alexander@schubert.berlin<mailto:alexander@schubert.berlin>> wrote: Anne, This is a contradiction. If the board denied “closed generics” (gTLD applications for generic keyword based strings) in 2012 then they did for a REASON. Unless the board specified a “conditional aspect” for that reason then the rationale for that decision hasn’t changed just because a decade went by. So the “ground rule” would be to keep the application rules as they were in 2012 – namely denying closed generics. UNLESS the gNSO develops new recommendations – which then need a new board approval. Some might argue that in 2012 the “problem” with closed generics wasn’t that bad: only a few dozen generic terms where taken by industry leaders (apparently mostly to just block off the entire vertical). So why bothering? Well: In 2012 the COST for a new gTLD was enormous! Application writing and submission wasn’t yet streamlined and expensive. Consulting (partly due to a steep “learning curve”) was expensive. Application fees alone where almost US $200k. By definition in 2012 there was no PRECEDENCE that industry leaders would snag up entire category defining killer keyword based gTLDs. The entire “new gTLD” issue was “murky”. All of this will have DRASTICALLY changed by 2022: • There will be a DECADE of public experience and exposure of the new gTLD program and new gTLDs • The consulting and application submission related fees will be DRASTICALLY lower – some consultants already offer packages lower than US $30k – which includes application writing, submission, contracting and testing! • The application fee will likely be low, too. Some already fabulize about US $25k fee floors – or even BELOW! • The “myth” that leading industry giants are massively hoarding “their” verticals (industry defining category killer generic terms) ain’t a “myth” anymore: it’s a viable truth – proven by the 2012 application roster. • Consultants will swarm out to big corporations who have ample marketing budgets and inflated egos: “If YOU are not securing ‘.CategoryDefiningKeyword’ then your competition will: be clever and have at minimum a horse in the race: let us apply for it on your behalf”. Image how incredibly STUPID the head of digital marketing of a Multi-Billion corporation looks if their smaller competitor controls “their” category keyword gTLD: this could cost him his head. In comparison for the price of a half page New York Times ad he could play hero and showcase to his board how “farsighted” he is. So if anything then the underlying “problem” that lead the board in 2012 to deny “closed generics” only got worse – MUCH worse: Lower “fees & overall cost” combined with established precedence = disaster! And while we have an obligation to keep harm away from the Internet community by continuing to deny “closed generics” that logically implies that we also make sure that in the 2nd round there will be no possibility for “effectively closed generics”: namely generic term based open applications that prove their “public interest” by promising launch periods (e.g. the Sunrise period) – but then never EXECUTE the Sunrise period – but rather are closed to the public and still allow the applicant to run 100 domains. If you have a Sunrise period in your application then you ought to execute that in a reasonable frame of time – or else you render the gTLD “closed”. I suggest we provide 12 month (extendable by another 12 month if reasons are provided for the delay) to launch your Sunrise (if you have one in your application) – but at BARE MINUMUM ICANN should be crystal clear that for registries that have a Sunrise in their application any “contract renewal expectation” will only apply if such Sunrise has been executed. Otherwise industry giants will simply snag up category defining keyword based gTLDs – and leave them inactive – just to make sure they “control the namespace”. Or they use their 100 domains and effectively run it as closed generic. If the general public (or Congress for that matter) would get wind of how sloppy we are protecting the public interest here: they would go bananas. Thanks, Alexander From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>] On Behalf Of Aikman-Scalese, Anne Sent: Dienstag, 18. Februar 2020 12:16 To: Kathy Kleiman <kathy@kathykleiman.com<mailto:kathy@kathykleiman.com>>; gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry HI Kathy, I do think it’s important for the WG to understand what Jeff’s position is procedurally on this topic. It appears to me that Paul is correct that there was no policy against Closed Generics in 2012 and that the Board resolution is limited to the 2012 round. So if we stick with the “ground rules” of the PDP, it appears that the next round will be “open season” for Closed Generic applications. This is especially important to consider now that the Working Group has taken a “rough consensus” position (with some of us dissenting) that going forward, if a string is applied for in the next round, that application will act as a complete bar to applications for the same string in any subsequent round. I would strongly advocate for skipping this topic in the next call and scheduling it for the F2F meeting. Anne From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 8:36 AM To: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry [EXTERNAL] ________________________________ As we revisit the topic of Closed Generics, I would like to share a few thoughts as a reminder on how this issue (of "generic words") has been dealt with in other forums. This is a long-established issue... 1) Trademark Manual of Examining Procedure, US Trademark Office: "Generic terms are incapable of functioning as marks denoting source, and are not registrable on the Principal Register under §2(f) or on the Supplemental Register." 807.14(e)(ii) 2) Our own Community Objection process reviewed and raised the same deep concerns for gTLDs in which the applicant (a competitor in a field) ICC New gTLD Community Objections determination: "The establishment of unrestricted, exclusive rights to a gTLD that is strongly associated with a certain community or communities, particularly where those communities are, or are likely to be, active in the Internet sphere seems to me inherently detrimental to those communities' interests." [Note: the "communities" being referred to here are commercial communities. The issue of a closed .MOBILE was raised by the CTIA which represents the US mobile wireless industry. 1-1316-6133 Best, Kathy ________________________________ 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@icann.org<mailto:Gnso-newgtld-wg@icann.org> https://urldefense.com/v3/__https://mm.icann.org/mailman/listinfo/gnso-newgt... <https://urldefense.com/v3/__https:/mm.icann.org/mailman/listinfo/gnso-newgtl...> _______________________________________________ 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://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!DUT_TFP... <https://urldefense.com/v3/__https:/www.icann.org/privacy/policy__;!!DUT_TFPx...>) and the website Terms of Service (https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!DUT_TFPxUQ... <https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!DUT_TFPxUQ!...>). 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. ________________________________ If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster@gtlaw.com<mailto:postmaster@gtlaw.com>, and do not use or disseminate the information.

Kathy, As you know if you read the thread below, I was not quoting only a portion of the proposal. Rather I was responding to an assertion that Alex made with respect to a specific sentence – that it clear demonstrated that the Board viewed closed generics as a SEVER PROBLEM. I agree with you that the Board reacted to concerns expressed by the GAC and some public comments. However, your assertion that the Board acted because there was a severe problem is nothing more than your conjecture. In my view, if the problem truly was so severe or the Board viewed it as so severe, the Board would have taken permanent and decisive action to permanently ban closed generics. But that is not what the Board did. Instead the Board prohibited closed generics in the first found and asked the GNSO to create policy regarding closed generics in subsequent rounds. In my opinion the Board did this because it wanted to play it safe and not fight with the GAC and fall on the sword over this issue. It chose instead to kick the can down the line and let the GNSO deal with this issue later. Finally, that dozens of gTLD applicants changed their application and .CLOUD, .SEARCH, .BLOG, .BOOK and others are open because of the Board decision is indeed a fact. But this fact doesn’t establish anything other than that the applicants did this because they had no other choice but to do so if they wanted their applications to proceed. There is no basis to impute anything else from this. Best regards, Marc H. Trachtenberg Shareholder Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 Tel 312.456.1020 Mobile 773.677.3305 trac@gtlaw.com<mailto:trac@gtlaw.com> | http://www.gtlaw.com<http://www.gtlaw.com/> [Greenberg Traurig] From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Kathy Kleiman Sent: Wednesday, February 19, 2020 10:44 PM To: gnso-newgtld-wg@icann.org Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry Marc, As you know, you are only quoting a portion of the proposal. The Board acted because there was a severe problem. It heard concerns from the GAC - dozens of Early Warnings against Closed Generics - and then held a public comment process in which comments flooded in from organizations, associations, small businesses and entrepreneurs all over the world. There were editorials written in newspapers around the world. There was very strong basis for the global concerns raised about Closed Generics and the action the Board Governance Committee took. What's being cited below is only a small part of the overall resolution. Also, we know the result: dozens of gTLD applicants changed their application and .CLOUD, .SEARCH, .BLOG, .BOOK and others are open because of these changes. Facts. Best, Kathy On 2/18/2020 9:18 PM, Marc Trachtenberg via Gnso-newgtld-wg wrote: Alex, Your point is completely manufactured and not based in any fact or the language that you cite. The Board did decide after the applications were submitted to not permit closed generics. You assert that this was because the issue was so problematic, that it will force applicants to either withdraw, or revert to open applications and present this as if it is a fact as opposed to just your conclusion that supports your view that every TLD and every domain name should be available to everyone as if it is a natural right. Your characterization of the Board’s action as “DRASTIC” is just that – your characterization. That Board has made many about faces and questionable decisions – are they all “DRASTIC”? Can the Board only make unexpected and questionable decisions when there is a “severe problem”? Then there must be “severe problems” all the time. Putting the drastic in CAPS does not make your assertion any more true. And what is the purpose of your repeated use of quotation marks – are you quoting yourself? As for the portion you direct us to concentrate on - “….. subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” - you again boldly mischaracterize it. This does not mean we are stuck with the status quo (assuming that no closed generics is the status quo as opposed to just applying to the first round which is another assertion you present as fact) and the Board did not make clear what the status quo ought to be despite your attempt to present it that way regardless of what the language says. In fact, if anything is clear from the language you cite, it is that the Board did not intend for no generics to be the status quo because they specifically directed (or at least contemplated) the GNSO to develop policy advice on this issue. It is also the purpose of this working group to consider procedures from the first round and whether they are appropriate for the second round. If this group had to just accept everything from the first round, Board-decided or otherwise – the group would have no purpose. And if anything is clear, it’s that this group has questioned virtually everything from the first round. Finally, your assertion that “At the very bare minimum the applicant would have to prove that their application serves the Public Interest (e.g. the .disaster example); and then the community would have to be called to decide whether the claim holds water”, this is also just your opinion and not based on anything else. To be clear, I don’t begrudge your opinion. Everyone has a right to their opinions and should have the ability to express those opinions productively in this working group as I think many in this group do, regardless if I agree with them. My opinion on closed generics happens to differ from yours but I don’t know that either view is right – they are just views. In fact, many people I like and respect share your view. What I do object to, and find offensive, is your repeated presentation of opinions and views as facts and mischaracterization of Board and community action and language in an attempt to support those views and I would ask you to stop. Best regards, Marc H. Trachtenberg Shareholder Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 Tel 312.456.1020 Mobile 773.677.3305 trac@gtlaw.com<mailto:trac@gtlaw.com> | http://www.gtlaw.com<http://www.gtlaw.com/> [Greenberg Traurig] From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Alexander Schubert Sent: Tuesday, February 18, 2020 7:35 PM To: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry Marc, The gNSO discussed and then decided to NOT create policy around “closed generics” during the 2007 PDP. This resulted in a substantial number of applications for “closed” category defining generic term based new gTLDs. The board decided AFTER THESE APPLICATIONS WHERE SUBMITTED that the issue was so problematic, that it will force applicants to either withdraw, or revert to open applications. I would consider such measure as being “DRASTIC”. The board would have not applied such drastic measure in absence of a “severe problem”. But better concentrate on this portion: “….. subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” In absence of the development of such “rules” (which hasn’t occurred yet) we are stuck with the status quo – and the board has made very clear what that status quo ought to be: NO CLOSED GENERICS. At the very bare minimum the applicant would have to prove that their application serves the Public Interest (e.g. the .disaster example); and then the community would have to be called to decide whether the claim holds water. Thanks, Alexander From: trachtenbergm@gtlaw.com<mailto:trachtenbergm@gtlaw.com> [mailto:trachtenbergm@gtlaw.com] Sent: Dienstag, 18. Februar 2020 17:39 To: alexander@schubert.berlin<mailto:alexander@schubert.berlin>; gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: RE: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry Alex, Maybe I am missing something but where in “…. will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” does the Board clearly say that there is a SEVERE PROBLEM with closed generics? Best regards, Marc H. Trachtenberg Shareholder Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601 Tel 312.456.1020 Mobile 773.677.3305 trac@gtlaw.com<mailto:trac@gtlaw.com> | http://www.gtlaw.com<http://www.gtlaw.com/> [Greenberg Traurig] From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org] On Behalf Of Alexander Schubert Sent: Tuesday, February 18, 2020 4:10 PM To: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry *EXTERNAL TO GT* Dear Group, Here from the June 2015 board meeting resolutions (these are quotes directly from the https://urldefense.com/v3/__http://ICANN.org__;!!DUT_TFPxUQ!TM_qJEYezYnoW85Q... website): https://urldefense.com/v3/__https://www.icann.org/resources/board-material/r... <https://urldefense.com/v3/__https:/www.icann.org/resources/board-material/re...> Advise Exclusive Generic Applicants for non-contended strings, or Exclusive Generic Applicants prevailing in contention resolution that they must elect within a reasonably limited time to either: submit a change request to no longer be an exclusive generic TLD, and sign the current form of the New gTLD Registry Agreement; maintain their plan to operate an exclusive generic TLD. As a result, their application will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs; or withdraw their application for a refund consistent with the refund schedule in the Applicant Guidebook. I would like to draw emphasis to: “…. will be deferred to the next round of the New gTLD Program, subject to rules developed for the next round, to allow time for the GNSO to develop policy advice concerning exclusive generic TLDs ….” The board clearly states that there is a SEVERE PROBLEM, that it denies closed generic applications, that those REMAIN ineligible UNTIL the GNSO has “developed advice concerning exclusive generic gTLDs”. Hairsplitters could argue that this is only true for the 2012 roster. But hey: come on. This is in striking contrast to the assentation that the ineligibility where to be restricted to the 2012 round only. The board INSTRUCTED the gNSO to “develop policy advice concerning exclusive generic TLD”, so in absence of a consensus around such policy advice it is self-evident that the board’s concerns aren’t addressed at all; and their “ban” stays active (or we force them to activate it yet again) We run the risk to look incompetent if we run into this knife yet again: if we (like suggested by some here) maintain that our 2007 PDP was “flawless” – and that we have to repeat this obvious mistake (allowing closed generics) again; then here what will happen: * GAC will point out the same as it has done in the 2012 round: asking the board to deny closed generics! * The board will note that the gNSO has denied their explicit request to develop new policy advice; and as a result will deny closed generics AGAIN! * This creates MASSIVE confusion for applicants; something that we should allow I assume it would be best if we abide by the Board request to “develop policy advice concerning exclusive generic TLD”. A subgroup was initiated last year – I am in there; but the group was inactive so far. We simply should create policy advice. If there is a consensus around under what set of circumstances allowing closed generics: fine! Then we allow them. If there is no consensus: then I guess we have established just that: No consensus to allow closed generics. Here a bit more from the June 2015 board resolutions: A Policy Development Process with respect to operating exclusive generic strings in the "public interest" should be undertaken by the community. Policy issues on "closed generic" TLDs should be resolved through the multistakeholder process. The public interest goal requirement as stated is too general and requires greater specificity for enforceability. The NGPC should add relevant meaning to the "public interest" concept by applying the GNSO rationales regarding the promotion of competition, consumer choice, market differentiation, and geographical and service provider diversity as standards for such affirmative objective showings and findings. Safeguards are important when applicants have chosen to apply for closed control of a generic term designating a particular industry where the applicant is engaged in the conduct of business activities in that industry. Requiring applicants to demonstrate some additional public interest goal in the context of exclusive registry access for generic strings would reverse the deliberate choices made by the ICANN community in its bottom-up process and impose new evaluation criteria. The status quo as set out in the Applicant Guidebook should apply so that both "open" and "closed" registry access for generic strings should continue to be allowed in this first application round, but both should be subject to significant scrutiny after launch by ICANN to ensure that the interests of rights owners and consumers are protected. So to say that the board decision was only pertaining the first round – but the 2nd round would be “open season for anything” is ignoring the board’s very clear advice. Board resolutions are our “safety valve” – we should try to establish our policies in a way that doesn’t require the board to issue them. And while we are at it: Submitting a generic term based gTLD application, trying to “prove public interest” by implementing clear launch phases (e.g. Sunrise), then never living up to such commitment: Should result in the denial of contract renewal after 10 years – at least for the 2nd round participants. If you prove your public interest through public availability (via defined launch periods) – but do not enact any: you have failed to serve the public interest. Why should ICANN renew your contract? It shouldn’t! As always: Exceptions might apply under extraordinary circumstances (Istanbul based .kurds denied to launch via court order for example). Thanks, Alexander From: Mike Rodenbaugh [mailto:mike@rodenbaugh.com] Sent: Dienstag, 18. Februar 2020 16:10 To: Alexander Schubert <alexander@schubert.berlin<mailto:alexander@schubert.berlin>> Cc: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry So-called Closed Generics (however anyone may define them) were allowed in 2012, as a Consensus Policy insofar they were very heavily debated by the GNSO for many years, including the same arguments and many of the same participants in today's debate. And Closed Generics were neither defined nor prohibited in the GNSO Consensus Policy adopted by the Board and then implemented by Staff and GNSO in the AGB. Thus, Closed Generics were essentially, explicitly allowed -- and unsurprisingly then there was some number of applicants for strings that the Board later unilaterally defined as Closed Generics. The Board then made a variance to one small part of that Consensus Policy, only as to a specifically defined subset of 2012 applications that the GAC and some others objected to. The Board specifically said that resolution had no bearing on future GNSO policy work. That resolution was never discussed or debated by the GNSO, until this PDP. So, neither the GNSO nor the Board have ever changed the 2012 Consensus Policy that allowed what some call "Closed Generics". To change it now will require consensus of this WG, which seems unlikely to happen. Mike Rodenbaugh RODENBAUGH LAW tel/fax: +1.415.738.8087 https://urldefense.com/v3/__http://rodenbaugh.law__;!!DUT_TFPxUQ!TM_qJEYezYn... <https://urldefense.com/v3/__http:/rodenbaugh.law__;!!DUT_TFPxUQ!TJdk660_rz8Q...> On Tue, Feb 18, 2020 at 12:26 PM Alexander Schubert <alexander@schubert.berlin<mailto:alexander@schubert.berlin>> wrote: Anne, This is a contradiction. If the board denied “closed generics” (gTLD applications for generic keyword based strings) in 2012 then they did for a REASON. Unless the board specified a “conditional aspect” for that reason then the rationale for that decision hasn’t changed just because a decade went by. So the “ground rule” would be to keep the application rules as they were in 2012 – namely denying closed generics. UNLESS the gNSO develops new recommendations – which then need a new board approval. Some might argue that in 2012 the “problem” with closed generics wasn’t that bad: only a few dozen generic terms where taken by industry leaders (apparently mostly to just block off the entire vertical). So why bothering? Well: In 2012 the COST for a new gTLD was enormous! Application writing and submission wasn’t yet streamlined and expensive. Consulting (partly due to a steep “learning curve”) was expensive. Application fees alone where almost US $200k. By definition in 2012 there was no PRECEDENCE that industry leaders would snag up entire category defining killer keyword based gTLDs. The entire “new gTLD” issue was “murky”. All of this will have DRASTICALLY changed by 2022: • There will be a DECADE of public experience and exposure of the new gTLD program and new gTLDs • The consulting and application submission related fees will be DRASTICALLY lower – some consultants already offer packages lower than US $30k – which includes application writing, submission, contracting and testing! • The application fee will likely be low, too. Some already fabulize about US $25k fee floors – or even BELOW! • The “myth” that leading industry giants are massively hoarding “their” verticals (industry defining category killer generic terms) ain’t a “myth” anymore: it’s a viable truth – proven by the 2012 application roster. • Consultants will swarm out to big corporations who have ample marketing budgets and inflated egos: “If YOU are not securing ‘.CategoryDefiningKeyword’ then your competition will: be clever and have at minimum a horse in the race: let us apply for it on your behalf”. Image how incredibly STUPID the head of digital marketing of a Multi-Billion corporation looks if their smaller competitor controls “their” category keyword gTLD: this could cost him his head. In comparison for the price of a half page New York Times ad he could play hero and showcase to his board how “farsighted” he is. So if anything then the underlying “problem” that lead the board in 2012 to deny “closed generics” only got worse – MUCH worse: Lower “fees & overall cost” combined with established precedence = disaster! And while we have an obligation to keep harm away from the Internet community by continuing to deny “closed generics” that logically implies that we also make sure that in the 2nd round there will be no possibility for “effectively closed generics”: namely generic term based open applications that prove their “public interest” by promising launch periods (e.g. the Sunrise period) – but then never EXECUTE the Sunrise period – but rather are closed to the public and still allow the applicant to run 100 domains. If you have a Sunrise period in your application then you ought to execute that in a reasonable frame of time – or else you render the gTLD “closed”. I suggest we provide 12 month (extendable by another 12 month if reasons are provided for the delay) to launch your Sunrise (if you have one in your application) – but at BARE MINUMUM ICANN should be crystal clear that for registries that have a Sunrise in their application any “contract renewal expectation” will only apply if such Sunrise has been executed. Otherwise industry giants will simply snag up category defining keyword based gTLDs – and leave them inactive – just to make sure they “control the namespace”. Or they use their 100 domains and effectively run it as closed generic. If the general public (or Congress for that matter) would get wind of how sloppy we are protecting the public interest here: they would go bananas. Thanks, Alexander From: Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>] On Behalf Of Aikman-Scalese, Anne Sent: Dienstag, 18. Februar 2020 12:16 To: Kathy Kleiman <kathy@kathykleiman.com<mailto:kathy@kathykleiman.com>>; gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry HI Kathy, I do think it’s important for the WG to understand what Jeff’s position is procedurally on this topic. It appears to me that Paul is correct that there was no policy against Closed Generics in 2012 and that the Board resolution is limited to the 2012 round. So if we stick with the “ground rules” of the PDP, it appears that the next round will be “open season” for Closed Generic applications. This is especially important to consider now that the Working Group has taken a “rough consensus” position (with some of us dissenting) that going forward, if a string is applied for in the next round, that application will act as a complete bar to applications for the same string in any subsequent round. I would strongly advocate for skipping this topic in the next call and scheduling it for the F2F meeting. Anne From: Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org<mailto:gnso-newgtld-wg-bounces@icann.org>> On Behalf Of Kathy Kleiman Sent: Tuesday, February 18, 2020 8:36 AM To: gnso-newgtld-wg@icann.org<mailto:gnso-newgtld-wg@icann.org> Subject: [Gnso-newgtld-wg] Generic words belong to everyone in a business or industry [EXTERNAL] ________________________________ As we revisit the topic of Closed Generics, I would like to share a few thoughts as a reminder on how this issue (of "generic words") has been dealt with in other forums. This is a long-established issue... 1) Trademark Manual of Examining Procedure, US Trademark Office: "Generic terms are incapable of functioning as marks denoting source, and are not registrable on the Principal Register under §2(f) or on the Supplemental Register." 807.14(e)(ii) 2) Our own Community Objection process reviewed and raised the same deep concerns for gTLDs in which the applicant (a competitor in a field) ICC New gTLD Community Objections determination: "The establishment of unrestricted, exclusive rights to a gTLD that is strongly associated with a certain community or communities, particularly where those communities are, or are likely to be, active in the Internet sphere seems to me inherently detrimental to those communities' interests." [Note: the "communities" being referred to here are commercial communities. The issue of a closed .MOBILE was raised by the CTIA which represents the US mobile wireless industry. 1-1316-6133 Best, Kathy ________________________________ 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@icann.org<mailto:Gnso-newgtld-wg@icann.org> https://urldefense.com/v3/__https://mm.icann.org/mailman/listinfo/gnso-newgt... <https://urldefense.com/v3/__https:/mm.icann.org/mailman/listinfo/gnso-newgtl...> _______________________________________________ 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://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!DUT_TFP... <https://urldefense.com/v3/__https:/www.icann.org/privacy/policy__;!!DUT_TFPx...>) and the website Terms of Service (https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!DUT_TFPxUQ... <https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!DUT_TFPxUQ!...>). 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. ________________________________ If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at postmaster@gtlaw.com<mailto:postmaster@gtlaw.com>, and do not use or disseminate the information. _______________________________________________ Gnso-newgtld-wg mailing list Gnso-newgtld-wg@icann.org<mailto:Gnso-newgtld-wg@icann.org> https://urldefense.com/v3/__https://mm.icann.org/mailman/listinfo/gnso-newgt... <https://urldefense.com/v3/__https:/mm.icann.org/mailman/listinfo/gnso-newgtl...> _______________________________________________ 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://urldefense.com/v3/__https://www.icann.org/privacy/policy__;!!DUT_TFP... <https://urldefense.com/v3/__https:/www.icann.org/privacy/policy__;!!DUT_TFPx...>) and the website Terms of Service (https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!DUT_TFPxUQ... <https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!DUT_TFPxUQ!...>). 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.