<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><blockquote type="cite">Good evening: I would follow Alan's advice in principle, but in this case I would recommend waiting for a week or two and publish the outcome. (Some of us haven't had time to read all 11 pp. yet)</blockquote><p>CW<br><br>PS: @Linkedin. (a) I did not know there was such a Linkedin group<br> (b) my Linkedin account suffered a gross security breach followed by DNS abuse, such that I have closed my Linkedin account that I opened in Harvard in 1982.</p><p><br></p><p><br></p><p><br></p><p><br></p><p><br></p><p><br></p><p><br></p><p><br></p><p><br></p><p><br></p><blockquote type="cite"> </blockquote><p><br></p><p><br></p><p><br></p><p><br></p><p><br></p><p><br></p><blockquote type="cite"> … de 2020 a las 19:30 Alan Greenberg <alan.greenberg@mcgill.ca> escribió: <br> The proposal was sent to this list which is public. So you can forward it anywhere (presumably being clear on the context that is is a prposal, nothing more at this time). <br> <br> Alan <br> <br> At 2020-07-21 01:10 PM, Jean Guillon wrote: <br><blockquote type="cite">Can I publish this proposal to the new gTLD group on LinkedIn ? <br> I think it makes sense for all those who don't know how things happen at ICANN. <br> <br> Feed back appreciated. <br> <br> On Tue, Jul 21, 2020 at 4:55 PM Greg Shatan < <a href="mailto:gregshatanipc@gmail.com">gregshatanipc@gmail.com</a> > wrote: <br><dl><dd>Jeff, <br> <br></dd><dd>This is meant to be a proposal for a closed TLD, and not an open restricted TLD. There would be no third party registrants. It's possible that in the press of time, and drafting by committee, we were not sufficiently clear. Can you point to some specific places where this jumps out at you? I did a final scrub last night and made some changes meant to clarify this, but I clearly did not catch them all. <br> <br></dd><dd>We can revise and either recirculate or hold this draft for further comments. Either way, we want this point to be completely clear and unambiguous. <br> <br></dd><dd>Best regards. <br> <br></dd><dd>Greg <br> <br></dd><dd>On Tue, Jul 21, 2020 at 9:38 AM Jeff Neuman < <a href="mailto:jeff@jjnsolutions.com">jeff@jjnsolutions.com</a>> wrote: <br><br><dl><dd>Thanks for this proposal George and the team. The major item that jumps out at me is that the TLD structure you describe is not really a “closed†TLD, but rather is akin an “open restricted†TLD. <br> <br></dd><dd> <br> <br></dd><dd>Anyone can already apply for an “open restricted†TLD without any of the restrictions you have set forth in this paper. This is like .bank, .pharmacy or others that have third party registrants who agree to very strict validation requirements. So, if I can apply for a .earthquake (your example) as an “open restricted†TLD without any of the restrictions that are contained within your paper, why would I apply for your “PICgTLD†and agree up front to (a) no expectancy of renewal; (b) restrictions on transfers; (c) obligations of a Council, (d) approval by the board, etc.? What is the benefit for me to do that when I can achieve the same thing without agreeing to any of that? <br> <br></dd><dd> <br> <br></dd><dd>Now if we stated that all of the registrations are “owned†by the Registry itself for use in connection with itself and its members, then perhaps that gets closer to the closed TLD. Thus, the registry could “license†registrations to third parties (not transfer ownership) so long as the registry itself always maintains ownership of the names and can control the type of content on the sites. <br> <br></dd><dd>Thanks for kicking off the discussion. <br> <br></dd><dd> <br> <br></dd><dd><img src="cid:7.1.0.9.2.20200721132917.0b061028@mcgill.ca.2" id="7.1.0.9.2.20200721132917.0b061028@mcgill.ca.2" width="300" height="3" alt="[]" style="width: 300px; height: 3px;"> <br> <br></dd><dd> <br> <br></dd><dd><img src="cid:7.1.0.9.2.20200721132917.0b061028@mcgill.ca.3" id="7.1.0.9.2.20200721132917.0b061028@mcgill.ca.3" width="219" height="123" alt="[]" style="width: 219px; height: 123px;"> <br> <br></dd><dd>Jeffrey J. Neuman <br> <br></dd><dd>Founder & CEO <br> <br></dd><dd>JJN Solutions, LLC <br> <br></dd><dd>p: +1.202.549.5079 <br> <br></dd><dd>E: <a href="mailto:jeff@jjnsolutions.com">jeff@jjnsolutions.com</a> <br> <br></dd><dd><a href="http://jjnsolutions.com/"> http://jjnsolutions.com</a> <br> <br></dd><dd> <br> <br></dd><dd> <br> <br></dd><dd>From: Gnso-newgtld-wg < <a href="mailto:gnso-newgtld-wg-bounces@icann.org"> gnso-newgtld-wg-bounces@icann.org</a>> On Behalf Of George Sadowsky <br></dd><dd>Sent: Tuesday, July 21, 2020 7:03 AM <br></dd><dd>To: <a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a> <br></dd><dd>Subject: [Gnso-newgtld-wg] Proposal for introducing new public interest generic gTLDs <br> <br></dd><dd> <br> <br></dd><dd>All, <br> <br></dd><dd> <br> <br></dd><dd>As promised, attached is our proposed method of implementing the use of new closed generic top level domains in the public interest within the DNS. It has been formulated by Alan Greenberg, Kathy Kleiman, Greg Shatan and me. We believe that it has merit and deserves consideration by both the working group and the broader ICANN community, and we welcome the opportunity to present it for comment, discussion and criticism. We believe that while there are improvements can be made, the approach of creating such a category of TLDs, trusted and protected to serve a public interest, is a goal that can be achieved. <br> <br></dd><dd> <br> <br></dd><dd>We hope that the proposal and the approach that it takes to implementing such a new class of gTLDs will receive serious consideration and criticism by the community. <br> <br></dd><dd> <br> <br></dd><dd>Regards, <br> <br></dd><dd> <br> <br></dd><dd>George <br> <br></dd><dd> <br> <br></dd><dd> <br> <br></dd><dd> <br> <br></dd><dd> <br> <br></dd><dd> <br> <br></dd><dd> <br> <br></dd><dd> <br> <br></dd><dd> <br> <br></dd><dd> <br></dd><dd>_______________________________________________ <br></dd><dd>Gnso-newgtld-wg mailing list <br></dd><dd><a href="mailto:Gnso-newgtld-wg@icann.org"> Gnso-newgtld-wg@icann.org</a> <br></dd><dd><a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg"> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a> <br></dd><dd>_______________________________________________ <br></dd><dd>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 ( <a href="https://www.icann.org/privacy/policy"> https://www.icann.org/privacy/policy</a>) and the website Terms of Service ( <a href="https://www.icann.org/privacy/tos"> https://www.icann.org/privacy/tos</a>). 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. <br> <br></dd></dl></dd><dd>_______________________________________________ <br></dd><dd>Gnso-newgtld-wg mailing list <br></dd><dd><a href="mailto:Gnso-newgtld-wg@icann.org"> Gnso-newgtld-wg@icann.org</a> <br></dd><dd><a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg"> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a> <br></dd><dd>_______________________________________________ <br></dd><dd>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 ( <a href="https://www.icann.org/privacy/policy"> https://www.icann.org/privacy/policy</a>) and the website Terms of Service ( <a href="https://www.icann.org/privacy/tos"> https://www.icann.org/privacy/tos</a>). 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. <br> <br></dd></dl>Content-Type: image/png; name="image001.png" <br> Content-Disposition: inline; filename="image001.png" <br> Content-ID: <17371daa6db4cff311> <br> X-Attachment-Id: 17371daa6db4cff311 <br> <br> Content-Type: image/png; name="image002.png" <br> Content-Disposition: inline; filename="image002.png" <br> Content-ID: <17371daa6db5b16b22> <br> X-Attachment-Id: 17371daa6db5b16b22 <br> <br> <br> _______________________________________________ <br> Gnso-newgtld-wg mailing list <br> Gnso-newgtld-wg@icann.org <br> <a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg"> https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a> <br> _______________________________________________ <br> 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 ( <a href="https://www.icann.org/privacy/policy"> https://www.icann.org/privacy/policy</a>) and the website Terms of Service ( <a href="https://www.icann.org/privacy/tos"> https://www.icann.org/privacy/tos</a>). 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.</blockquote></blockquote><p class="default-style"><br> </p><blockquote type="cite">_______________________________________________ <br>Gnso-newgtld-wg mailing list <br>Gnso-newgtld-wg@icann.org <br>https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg <br>_______________________________________________ <br>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.</blockquote><p class="default-style"><br> </p></body></html>