Dear Jeff,Let me start by highlighting your good stewardship in this group. I am amazed how you lead us - and how you orbit around all aspects of this PDP. Very good job.Regarding the ".disaster" example:That's the problem with examples; they initially make sense - but when diving into details: they might turn out not so good. In the case of the Red Cross applying for any generic term based new gTLD: just because their work is so extraordinary humanitarian doesn't mean any potential generic gTLD is deemed to be worthy to be taken by them. So when people poked holes in this example then less as to prove no example can be given - but more to prevent having an insufficient example in our WG report.Thanks,Alexander Sent from my Samsung device -------- Original message -------- From: Jeff Neuman <jeff@jjnsolutions.com> Date: 7/12/20 18:36 (GMT+02:00) To: George Sadowsky <george.sadowsky@gmail.com> Cc: gnso-newgtld-wg@icann.org Subject: Re: [Gnso-newgtld-wg] Latest Version of Compromise Closed Generic Text Thanks George for keeping the dialogue going and I think this is very helpful. So, I presented an example before (and in) the initial report that I came up with. The example was an application for .disaster by the International Red Cross. The application (made up by me) was to have second level names given to specific disasters to serve as the official Red Cross fund raiser for these events. Examples include HurricaineMaria.disaster, covid19VA.disaster, covid19UK.disaster, etc. Users would know that if they went to these sites and donated, that the money would actually be going to the official Red Cross and to official sources. The goal would be to drastically reduce the amount of fraud to end users from fake fundraising campaigns. Those that opposed closed generics did not agree that this would be good enough. They argued that generic words should be open to all “competitors” and why should the Red Cross monopolize a word/string. They come from the very traditional view that second level domains should be available to all (with restrictions). It is a view of end users being the registrants of domains as opposed to end users being those that use the Internet in general. Opponents argued “why couldn’t they just apply for .redcross” or “why cant they just make it open”? So essentially it became a debate about words and generic ness and who has a right to them as opposed to looking at the application itself to see if it served a public interest goal. When it became apparent that even in this humanitarian extreme example that members of the working group were unwilling to consider the application that we decided to end the discussion because it was clear that no example would satisfy the “serving a public interest goal” to members of the group. I hope that helps explain a little bit more how we got here and that we have indeed tried to discuss some examples. Get Outlook for iOS From: George Sadowsky <george.sadowsky@gmail.com> Sent: Sunday, July 12, 2020 9:35:12 AM To: Jeff Neuman <jeff@jjnsolutions.com> Cc: Kleiman Kathy <kathy@kathykleiman.com>; gnso-newgtld-wg@icann.org <gnso-newgtld-wg@icann.org> Subject: Re: [Gnso-newgtld-wg] Latest Version of Compromise Closed Generic Text Thanks, Jeff, for a thorough and and balanced response. I have several comments and suggestions, interspersed in the text below. On Jul 11, 2020, at 11:50 PM, Jeff Neuman <jeff@jjnsolutions.com> wrote: Thanks George. This is helpful, but I am not sure that any part of the Board resolution or rationale necessarily supports the notion that the default position be an outright ban. In reading the resolution and rationale again, one could read that as meaning that the board was not looking to ban closed generics altogether, but was looking for guidance as to how applications for closed generics could be evaluated as “serving a public interest goal.”