<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
The bottom line at this point is that the only reason to include anything other than what the Board actually resolved is to add commentary supporting a particular point of view on whether closed generics should be allowed and if so, when. The only thing we
can agree upon is that we can't agree. So let the Board speak for itself and people who read the report can interpret it as they will. <br>
<br>
<div dir="ltr">
<div><br>
</div>
<div>Best Regards,</div>
<b>
<div><b><br>
</b></div>
Marc H.Trachtenberg</b>
<div>
<div>Shareholder</div>
<div>Greenberg Traurig, LLP</div>
<div>77 West Wacker Drive</div>
<div>Chicago, IL 60601</div>
<div>Office (312) 456-1020</div>
<div>Mobile (773) 677-3305</div>
</div>
</div>
<div dir="ltr"><br>
<blockquote type="cite">On Jul 12, 2020, at 4:29 PM, Alexander Schubert <alexander@schubert.berlin> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div><font color="#0e0e3f"><b>*EXTERNAL TO GT*</b><br>
<br>
</font></div>
<div>Dear Jeff,</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Regarding the ".disaster" example:</div>
<div>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.</div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Alexander </div>
<div><br>
</div>
<div><br>
</div>
<div id="composer_signature">
<div style="font-size:88%;color:#364f67" dir="auto">Sent from my Samsung device</div>
</div>
<br>
<br>
-------- Original message --------<br>
From: Jeff Neuman <jeff@jjnsolutions.com> <br>
Date: 7/12/20 18:36 (GMT+02:00) <br>
To: George Sadowsky <george.sadowsky@gmail.com> <br>
Cc: gnso-newgtld-wg@icann.org <br>
Subject: Re: [Gnso-newgtld-wg] Latest Version of Compromise Closed Generic Text <br>
<br>
<div>
<div>
<div style="direction: ltr;">Thanks George for keeping the dialogue going and I think this is very helpful.</div>
<div><br>
</div>
<div style="direction: ltr;">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.</div>
<div><br>
</div>
<div style="direction: ltr;">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. </div>
<div><br>
</div>
<div style="direction: ltr;">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. </div>
<div style="direction: ltr;"><span id="ms-outlook-ios-cursor"></span></div>
<div style="direction: ltr;">I hope that helps explain a little bit more how we got here and that we have indeed tried to discuss some examples.
</div>
</div>
<div><br>
</div>
<div class="ms-outlook-ios-signature">Get <a href="https://urldefense.com/v3/__https://aka.ms/o0ukef__;!!DUT_TFPxUQ!VFYmMUj6rLqzvQYxqjU02Kinys6WMsx-qvncEa1LBXK4V3G66AraAqvp5U1t0bOOWF0$">
Outlook for iOS</a></div>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> George Sadowsky <george.sadowsky@gmail.com><br>
<b>Sent:</b> Sunday, July 12, 2020 9:35:12 AM<br>
<b>To:</b> Jeff Neuman <jeff@jjnsolutions.com><br>
<b>Cc:</b> Kleiman Kathy <kathy@kathykleiman.com>; gnso-newgtld-wg@icann.org <gnso-newgtld-wg@icann.org><br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Latest Version of Compromise Closed Generic Text</font>
<div> </div>
</div>
<div class="" style="word-wrap:break-word; line-break:after-white-space">Thanks, Jeff, for a thorough and and balanced response. I have several comments and suggestions, interspersed in the text below.<br class="">
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Jul 11, 2020, at 11:50 PM, Jeff Neuman <<a href="mailto:jeff@jjnsolutions.com" class="">jeff@jjnsolutions.com</a>> wrote:</div>
<br class="x_Apple-interchange-newline">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="" style="direction:ltr">Thanks George. </div>
<div class=""><br class="">
</div>
<div class="" style="direction:ltr">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.”</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<span>_______________________________________________</span><br>
<span>Gnso-newgtld-wg mailing list</span><br>
<span>Gnso-newgtld-wg@icann.org</span><br>
<span>https://urldefense.com/v3/__https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg__;!!DUT_TFPxUQ!VFYmMUj6rLqzvQYxqjU02Kinys6WMsx-qvncEa1LBXK4V3G66AraAqvp5U1tDn1BScM$
</span><br>
<span>_______________________________________________</span><br>
<span>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_TFPxUQ!VFYmMUj6rLqzvQYxqjU02Kinys6WMsx-qvncEa1LBXK4V3G66AraAqvp5U1t79nX2yM$
) and the website Terms of Service (https://urldefense.com/v3/__https://www.icann.org/privacy/tos__;!!DUT_TFPxUQ!VFYmMUj6rLqzvQYxqjU02Kinys6WMsx-qvncEa1LBXK4V3G66AraAqvp5U1t5yO8t_M$ ). 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.</span></div>
</blockquote>
<HR>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.<BR>
</body>
</html>