<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Alex,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Where in the ICANN mission or principles does it say anything about ensuring that every possible string be available as TLD for public registration? This is your mission,
not ICANN’s.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards,</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:#003359">Marc H. Trachtenberg</span></b><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:black"><br>
Shareholder </span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><br>
</span><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:black">Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601<br>
Tel 312.456.1020 <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:black">Mobile 773.677.3305<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:black"><a href="mailto:trachtenbergm@gtlaw.com"><span style="color:#003359">trachtenbergm@gtlaw.com</span></a> |
<a href="http://www.gtlaw.com/"><span style="color:#003359">www.gtlaw.com</span></a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><img border="0" width="185" height="30" style="width:1.927in;height:.3125in" id="_x0000_i1039" src="cid:image001.jpg@01D55E4F.0AFB8220" alt="Greenberg Traurig"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Gnso-newgtld-wg [mailto:gnso-newgtld-wg-bounces@icann.org]
<b>On Behalf Of </b>Alexander Schubert<br>
<b>Sent:</b> Thursday, August 29, 2019 6:16 AM<br>
<b>To:</b> gnso-newgtld-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Closed Generics and the 2012 Round<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Maxim,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks for bringing this up. Well: CURRENTLY there are only a few “cases”. So let these few brands continue to operate their gTLDs effectively as “closed generic”.<br>
<br>
That doesn’t mean we shouldn’t shut down the loophole for future rounds. We would open the floodgates if we wouldn’t.<br>
<br>
So if “closed generics” remain unavailable (which the “small group” is sorting out right now) ICANN should incorporate in the RA (registry agreement) clear provisions regarding the rollout timeline – and penalties for failing to roll out within a specific period;
including but not limited to cancel the contract. If an applicant is the only registrant within its gTLD – and that over a prolonged period of time – he is (inadvertently) meeting the definition of a “closed generic” (as defined by the community). The “rollout
grace period” could be several years long. But when somebody doesn’t roll out and offer no concrete plans how to do so MANY YEARS after delegation? They would need to provide extraordinary circumstances to get an extension. They applied for the gTLD in order
to provide registrations to the public. If they do not provide registrations to the public: how does that benefit the public? How does that meet the ICANN mission? It doesn’t. We need to make that a “breach of contract”.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Alexander<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Maxim Alzoba [<a href="mailto:m.alzoba@gmail.com">mailto:m.alzoba@gmail.com</a>]
<br>
<b>Sent:</b> Thursday, August 29, 2019 1:51 PM<br>
<b>To:</b> <a href="mailto:alexander@schubert.berlin">alexander@schubert.berlin</a><br>
<b>Cc:</b> <a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Closed Generics and the 2012 Round<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Alexander, <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Formally, that definition is not included in any form into the RA or obligatory policies, or RFCs Registry has to follow, <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">and it means that we might like it or not, but there are no grounds to revoke the TLD.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:8.5pt;color:black">Sincerely Yours,<br>
<br>
Maxim Alzoba<br>
Special projects manager,<br>
International Relations Department,<br>
FAITID<br>
<br>
m. +7 916 6761580(+whatsapp)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:8.5pt;color:black">skype oldfrogger<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:8.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:8.5pt;color:black">Current UTC offset: +3.00 (.Moscow)<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 29 Aug 2019, at 17:42, Alexander Schubert <<a href="mailto:alexander@schubert.berlin">alexander@schubert.berlin</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Marc,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In 2013 ICANN “defined” (rather the understanding of the community was) that:</span><o:p></o:p></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><b><i><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#2E75B6">“…….a ‘closed generic’ TLD as a TLD string that is a generic term and is proposed to be operated by a participant exclusively for its own benefit.”</span></i></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The 2012 AGB did not provide for “closed generics” – the PDP never introduced such animal – hence the board denied applicants to operate a generic term based gTLD as “closed
generic”.<br>
<br>
Obviously for a short time between delegation of the string and the Sunrise phase there is a period where EVERY gTLD is inadvertently matching the definition of a “closed generic”: They are forced to operate the domain name “nic.gtld” – hence they are a single
registrant and operate the string “exclusively for its own benefit.”. It is the burden and responsibility of the APPLICANT (rather by now: registry operator) to keep such period within a reasonable scope of time. Most operators will try to start up ASAP. Some
might need a few more month to sort themselves out. If the period is longer than a year – I think that’s already reason to question what’s going on. But MORE THAN THREE FULL YEARS? That’s not a “reasonable period” at all.<span class="apple-converted-space"> </span><br>
<br>
Right now since 3 years the .beauty gTLD meets the ICANN definition of “closed generic”. The board has clearly DENIED such option. And you are telling me that there is no problem – and this charade should be allowed to go on “forever”? I do not think that outside
of the “Brand-Cloud” ANYBODY would share your opinion. You do not “buy” a gTLD: you apply at ICANN to OPERATE IT: for the benefit of the entire Internet. gTLDs aren’t an “asset” – they are a responsibility. And right now L’Oreal is not meeting their responsibilities.<span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
Am I the only person here who is concerned that brands snag up generic category-killer keywords (the main defining dictionary keywords of their vertical; e.g. .beauty, -hair and .skin for L’Oreal) – seemingly with the goal to prevent competitors to snag those
strings up, with no real plan how to use them, then simply not use them at all thus precisely meeting the definition of “closed generic”? Brand consultants will run around and tell their clients: “Hey, you GOT to do what L’Oreal did: snag up a couple of your
most import verticals of your industry – shut them down; or risk that a competitor is running these strings in some way that would harm you”! If we were to lower the application fee floor to US $25k – then for a mere quarter Million USD a brand could snag
up 10 generic keywords. Man: Good business for brand consultants – but horrific for the Internet Community: I see literally THOUSANDS of dictionary terms being “grounded”. Do we really want this to happen?<br>
<br>
Applying for a generic term based gTLD – never starting it up: That’s a loophole brands are exploiting. We need to shut down all these loopholes, and fast. The Board clearly directed that closed generics are BANNED. We now have the task to explore how many
years of running such gTLD effectively as “closed gTLD” (even if just inadvertently) should lead to a cancelation of the contract – and release of the string into the pool of available ones.<br>
<br>
In my opinion 3 years is already way too long. Here a suggestion for a policy to keep operators compliant with the mission of the new gTLD extension:</span><o:p></o:p></p>
</div>
<div style="margin-left:.5in">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">A year after delegation the applicant should provide a detailed explanation why they have NOT made domains available to the public (which is the entire foundation of their
contract with ICANN: making domains available to registrants). The applicant should lay out a detailed timeline of the intended rollout. If another year goes by without startup: The contract should be canceled (unless extraordinary circumstances lay the foundation
for a proprietary extension of the grace period; maybe even including a public comment period).<span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This policy “draft” is a shot in the blue – but I think we need SOME policy to avoid that brands deny the public registrations in “their “ gTLDs
– thus effectively operating their gTLD as “closed generic”.<span class="apple-converted-space"> </span><br>
<br>
Thoughts?<br>
<br>
Alexander<br>
<br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span class="apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:trachtenbergm@gtlaw.com"><span style="color:purple">trachtenbergm@gtlaw.com</span></a><span class="apple-converted-space"> </span>[<a href="mailto:trachtenbergm@gtlaw.com"><span style="color:purple">mailto:trachtenbergm@gtlaw.com</span></a>]<span class="apple-converted-space"> </span><br>
<b>Sent:</b><span class="apple-converted-space"> </span>Thursday, August 29, 2019 12:52 AM<br>
<b>To:</b><span class="apple-converted-space"> </span><a href="mailto:alexander@schubert.berlin"><span style="color:purple">alexander@schubert.berlin</span></a>;<span class="apple-converted-space"> </span><a href="mailto:gnso-newgtld-wg@icann.org"><span style="color:purple">gnso-newgtld-wg@icann.org</span></a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>RE: [Gnso-newgtld-wg] Closed Generics and the 2012 Round</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">You should be patient as long as the RO is compliant with its RA, even if forever. There is no innate right (or need) to have every word phrase or combination of characters
available as a TLD. If the RO was the only one to apply for the string or won it at auction then they can wait as long as they want to do something with it or never do anything with it other than have a nic page. <span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:#003359">Marc H. Trachtenberg</span></b><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif"><br>
Shareholder<span class="apple-converted-space"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><br>
</span><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif">Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601<br>
Tel 312.456.1020<span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif">Mobile 773.677.3305</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif"><a href="mailto:trachtenbergm@gtlaw.com"><span style="color:#003359">trachtenbergm@gtlaw.com</span></a><span class="apple-converted-space"> </span>|<span class="apple-converted-space"> </span><a href="http://www.gtlaw.com/"><span style="color:#003359">www.gtlaw.com</span></a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><img border="0" width="185" height="30" style="width:1.927in;height:.3125in" id="_x0000_i1025" src="cid:image001.jpg@01D55E4F.0AFB8220" alt="Greenberg Traurig"></span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span class="apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Gnso-newgtld-wg
[<a href="mailto:gnso-newgtld-wg-bounces@icann.org"><span style="color:purple">mailto:gnso-newgtld-wg-bounces@icann.org</span></a>]<span class="apple-converted-space"> </span><b>On Behalf Of<span class="apple-converted-space"> </span></b>Alexander Schubert<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Wednesday, August 28, 2019 4:44 PM<br>
<b>To:</b><span class="apple-converted-space"> </span><a href="mailto:gnso-newgtld-wg@icann.org"><span style="color:purple">gnso-newgtld-wg@icann.org</span></a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [Gnso-newgtld-wg] Closed Generics and the 2012 Round</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Marc,<br>
<br>
Re “no closed gTLDs in the next round”: I thought for THIS audience it is self-evident that my assumption is what it is: an assumption! But yes you are right; I could have said “I certainly hope that …..”!<span class="apple-converted-space"> </span><br>
<br>
Regarding the non-use of a TLD 3 years after delegation (closed gTLD):<br>
In this case (.beauty) all domain names (which is 1 domain name: nic) are registered by the applicant – which is the EXACT definition of a closed gTLD. A closed gTLD is a TLD where the applicant is single registrant. So until they open it up – it is closed.
How is this inaccurate? Arguably ALL gTLDs are for a short time “closed gTLDs” – until they admit sunrise regs.<span class="apple-converted-space"> </span><br>
<br>
How long should we be patient that somebody reverts his “closed gTLD” (all domains registered by the applicant) to an open one? Should we wait 1 year? 3 years? 5 years? A decade? Then renew their contract and wait a bit more?<span class="apple-converted-space"> </span><br>
<br>
<br>
Thanks,<br>
<br>
Alexander<br>
<br>
<br>
<br>
<br>
</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span class="apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><a href="mailto:trachtenbergm@gtlaw.com"><span style="color:purple">trachtenbergm@gtlaw.com</span></a><span class="apple-converted-space"> </span>[<a href="mailto:trachtenbergm@gtlaw.com"><span style="color:purple">mailto:trachtenbergm@gtlaw.com</span></a>]<span class="apple-converted-space"> </span><br>
<b>Sent:</b><span class="apple-converted-space"> </span>Wednesday, August 28, 2019 11:57 PM<br>
<b>To:</b><span class="apple-converted-space"> </span><a href="mailto:alexander@schubert.berlin"><span style="color:purple">alexander@schubert.berlin</span></a>;<span class="apple-converted-space"> </span><a href="mailto:gnso-newgtld-wg@icann.org"><span style="color:purple">gnso-newgtld-wg@icann.org</span></a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>RE: [Gnso-newgtld-wg] Closed Generics and the 2012 Round</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Alex,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There not being closed generics in the next round and closed generics being a violation of the ICANN mission is your opinion. Please do not present it as a fact. Similarly,
a registry operator no launching their TLD is not a closed TLD by definition – at least not in the way understood by anyone who has discussed closed TLDs. It is not helpful to conflate terms.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif;color:#003359">Marc H. Trachtenberg</span></b><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif"><br>
Shareholder<span class="apple-converted-space"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><br>
</span><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif">Greenberg Traurig, LLP | 77 West Wacker Drive | Suite 3100 | Chicago, IL 60601<br>
Tel 312.456.1020<span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif">Mobile 773.677.3305</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Trebuchet MS",sans-serif"><a href="mailto:trachtenbergm@gtlaw.com"><span style="color:#003359">trachtenbergm@gtlaw.com</span></a><span class="apple-converted-space"> </span>|<span class="apple-converted-space"> </span><a href="http://www.gtlaw.com/"><span style="color:#003359">www.gtlaw.com</span></a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><img border="0" width="185" height="30" style="width:1.927in;height:.3125in" id="Picture_x0020_1" src="cid:image001.jpg@01D55E4F.0AFB8220" alt="Greenberg Traurig"></span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span class="apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Gnso-newgtld-wg
[<a href="mailto:gnso-newgtld-wg-bounces@icann.org"><span style="color:purple">mailto:gnso-newgtld-wg-bounces@icann.org</span></a>]<span class="apple-converted-space"> </span><b>On Behalf Of<span class="apple-converted-space"> </span></b>Alexander Schubert<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Wednesday, August 28, 2019 3:48 PM<br>
<b>To:</b><span class="apple-converted-space"> </span><a href="mailto:gnso-newgtld-wg@icann.org"><span style="color:purple">gnso-newgtld-wg@icann.org</span></a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [Gnso-newgtld-wg] Closed Generics and the 2012 Round</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#0E0E3F">*EXTERNAL TO GT*</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Anne,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">They routed the SLD “nic”, not the third-level-domain “www”! So there is a website at<span class="apple-converted-space"> </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__nic.beauty&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=Ks8DhrChiD1tWn59vOwUurVBcMhGXUxzsUq0GyjrcxA&e="><span style="color:purple">http://nic.beauty</span></a>;
and at<span class="apple-converted-space"> </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__webwhois.nic.beauty&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=TUfmNYz1xJ0sogHJkwYNOA1aFvseCQmmK_FbsFdWwAA&e="><span style="color:purple">http://webwhois.nic.beauty</span></a><span class="apple-converted-space"> </span><br>
<br>
But the TLD doesn’t seem to have been launched. There is only ONE domain in the zone – “nic.beauty”!<br>
<br>
And what do any potential next round gTLDs have to do with .beauty? Where is the connection? I don’t get it.<br>
<br>
There won’t be “closed generics” in the next round – it’s a violation of the ICANN mission and would construe a land grab. And .beauty will likely be available soon again: if you do not make a public DNS resource available to the public; then your contract
won’t get extended (or so I hope very much). Actually the question is: Why not making “.beauty” available for the coming round? The TLD is delegated since July 2016 – that’s more than 3 years; plus they had a full 7 years of time after application submission
to “make a plan”. So I say: If nothing happens there till 2021: just delete it from the zone. Because “non-use” is BY DEFINITION a “closed” TLD: and they were not allowed to do that. They asked to operate .beauty in order to further the evolution of the DNS
– they never delivered. So just delete this string from the zone and make it available again.<span class="apple-converted-space"> </span><br>
<br>
Thanks,<br>
<br>
Alexander</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span><o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span class="apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Gnso-newgtld-wg
[<a href="mailto:gnso-newgtld-wg-bounces@icann.org"><span style="color:purple">mailto:gnso-newgtld-wg-bounces@icann.org</span></a>]<span class="apple-converted-space"> </span><b>On Behalf Of<span class="apple-converted-space"> </span></b>Aikman-Scalese, Anne<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Wednesday, August 28, 2019 10:52 PM<br>
<b>To:</b><span class="apple-converted-space"> </span>Heather Forrest <<a href="mailto:haforrestesq@gmail.com"><span style="color:purple">haforrestesq@gmail.com</span></a>>; Maxim Alzoba <<a href="mailto:m.alzoba@gmail.com"><span style="color:purple">m.alzoba@gmail.com</span></a>><br>
<b>Cc:</b><span class="apple-converted-space"> </span><a href="mailto:gnso-newgtld-wg@icann.org"><span style="color:purple">gnso-newgtld-wg@icann.org</span></a><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [Gnso-newgtld-wg] Closed Generics and the 2012 Round</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Hi Heather,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">There is no prohibition on a registry seeking a reasonable contract modification from ICANN in light of all circumstances. It’s codified in Consensus Policy as the<span class="apple-converted-space"> </span><b>RSEP<span class="apple-converted-space"> </span></b>process.
An unreasonable denial of that RSEP request for contract modification is fertile ground for a Request for Reconsideration, Independent Review Process, all the way up to and including a lawsuit. <span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">See <span class="apple-converted-space"> </span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_rsep-2D2014-2D02-2D19-2Den&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=a0k1oNzQ2OdxeRJJXOG0HjMe6ANnsFwcVhNT00X2LXQ&e="><span style="color:purple">https://www.icann.org/resources/pages/rsep-2014-02-19-en</span></a>
and note the legitimate purpose to “modify” or “remove” an existing Registry service.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Let’s take the real life example of .BEAUTY – originally proposed as closed –now delegated as “open” and NOT launched (at least according to ICANN Sunrise records at the link provided by Rubens and I don’t see
anything at<span class="apple-converted-space"> </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.nic.beauty&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=8LXrfIrkOyrPz-FMTAvuupvcGaz1z04oxWXN5MurB0w&e="><span style="color:purple">www.nic.beauty</span></a>.
Are we really saying that if L’Oreal’s competitor applies for and gets .PRETTY as a Closed Generic based on a 2022 application, it doesn’t matter and L’Oreal is stuck with remaining an open generic even if they have not launched? (I don’t represent L’Oreal
or any other beauty industry client.) Keep in mind that there was absolutely nothing in the 2012 AGB that prohibited an application for a Closed Generic. (Sounds vaguely familiar to another IRP proceeding.)</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Maybe out of scope for Sub Pro, but GNSO Council will have to deal with this if they don’t want a “logjam” at the Board level as to any new Closed Generic policy that may be developed. <span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Anne</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span class="apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Heather
Forrest <</span><a href="mailto:haforrestesq@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:purple">haforrestesq@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">><span class="apple-converted-space"> </span><br>
<b>Sent:</b><span class="apple-converted-space"> </span>Tuesday, August 27, 2019 8:44 PM<br>
<b>To:</b><span class="apple-converted-space"> </span>Maxim Alzoba <</span><a href="mailto:m.alzoba@gmail.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:purple">m.alzoba@gmail.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">><br>
<b>Cc:</b><span class="apple-converted-space"> </span>Aikman-Scalese, Anne <</span><a href="mailto:AAikman@lrrc.com"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:purple">AAikman@lrrc.com</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;<span class="apple-converted-space"> </span></span><a href="mailto:gnso-newgtld-wg@icann.org"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:purple">gnso-newgtld-wg@icann.org</span></a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [Gnso-newgtld-wg] Closed Generics and the 2012 Round</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">[EXTERNAL]</span></strong><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
</div>
<div>
<p class="MsoNormal">Thanks, Maxim - I understand that, but amendments to an in-force contract are not the same as repudiating a contract and asking for a new contract to apply. The terms of the RA (clause 7.6(a) re "Special Amendment") and the AGB expressly
provided for amendments to both.<o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">AGB Module 6, cl 14: "ICANN reserves the right to make reasonable updates and changes to this applicant guidebook and to the application process, including the process for withdrawal of applications, at any time by posting notice of such
updates and changes to the ICANN website, including as the possible result of new policies that might be adopted or advice to ICANN from ICANN advisory committees during the course of the application process. Applicant acknowledges that ICANN may make such
updates and changes and agrees that its application will be subject to any such updates and changes. In the event that Applicant has completed and submitted its application prior to such updates or changes and Applicant can demonstrate to ICANN that compliance
with such updates or changes would present a material hardship to Applicant, then ICANN will work with Applicant in good faith to attempt to make reasonable accommodations in order to mitigate any negative consequences for Applicant to the extent possible
consistent with ICANN's mission to ensure the stable and secure operation of the Internet's unique identifier systems." <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">I can anticipate here that someone will say: "But Module 6 cl 14 expressly anticipates changes to the AGB and gives the 2012 applicant a right to demonstrate material hardship caused by the 'new' AGB being on more favourable terms!" I don't
think that will be consistent with standard contract law interpretation in US courts, as only the 2012 applicants agreed to be contractually bound by the 2012 AGB, while new round applicants will only have the option of agreeing to whatever the AGB (or whatever
name it has) is at that time, not a choice between old AGB or new AGB. A strict interpretation of "changes to<span class="apple-converted-space"> </span><i>this applicant guidebook</i>" logically suggests that the 2012 AGB binds applicants who applied in 2012,
because by applying, they consented to the application of the 2012 AGB. A new AGB, even if technically an amended version of the prior document, would apply to new applicants in the "next" round, whenever that is. Articulated another way, I think Jeff's point
to now is that the charter of SubPro PDP instructs us to develop the rules that will apply to applicants in this "next" round, not to unsuccessful or any other applicants of the 2012 round (who already contractually agreed to a set of rules when they submitted
their application to the TAS). The question of whether the new AGB/RA that results from SubPro PDP, RPM PDP, CCT Review, etc is to be applied to 2012 applicants is not within our PDP's scope. That's the question that would have to go to Council.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Best wishes,<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Heather<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">.<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Best wishes,<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Heather<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">On Wed, Aug 28, 2019 at 11:51 AM Maxim Alzoba <<a href="mailto:m.alzoba@gmail.com"><span style="color:purple">m.alzoba@gmail.com</span></a>> wrote:<o:p></o:p></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Heather,<span class="apple-converted-space"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Formally ICANN changed AGB and RAin 2012 (Pic spec, for example), after the fees were paid.<span class="apple-converted-space"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">But anyway, we should not mix rules from the different sets.<span class="apple-converted-space"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">Maxim Alzoba<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">On 28 Aug 2019, at 08:35, Heather Forrest <<a href="mailto:haforrestesq@gmail.com" target="_blank"><span style="color:purple">haforrestesq@gmail.com</span></a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Anne, all,<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">It seems to me that basic principles of contract law apply here to keep us out of the weeds. ICANN's legal framework depends, in its entirety, on contract after all. Applicants who applied in 2012 under the AGB contractually agreed, by
submitting an application, to the AGB and the base RA that was incorporated in it. Those applicants did not apply under a future AGB, or a future RA to reflect that future AGB. <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Whether a party on a 2012-era contract can adopt (in the case of those not yet contracted) the new RA or rescind current RA and adopt new RA (for those already completed contracting) is a separate question. I agree with Jeff that this separate
question is not within the scope of the SubPro charter.<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Best wishes,<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal">Heather<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal">On Tue, Aug 27, 2019 at 5:50 AM Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com" target="_blank"><span style="color:purple">AAikman@lrrc.com</span></a>> wrote:<o:p></o:p></p>
</div>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class="MsoNormal"><span style="color:#993366">Hi Jeff – Do we have Susan’s draft language on your first point yet? (You may recall that there were even discussions about PROHIBITING new applications for the same string as some still pending from 2012 –that
was not agreed so Susan is working on a statement that 2012 string application processing must be complete before any new application for that string would be considered. HOWEVER – again here is the “rub” – When you say 2012 string applications have to be
“completed”, what are you saying about the policy that applies to those? What if the pending strings from 2012 don’t meet current new gTLD policy but they did not violate that policy as of the time of application? We can only skirt this issue for so long.
Are 2012 strings going to be allowed to update to current gTLD policy in order to get authorization to proceed or not? Or are you saying GNSO Council will have to launch another PDP for that purpose?</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#993366"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span class="apple-converted-space"><span style="font-size:11.0pt"> </span></span><span style="font-size:11.0pt">Jeff Neuman <</span><a href="mailto:jeff.neuman@comlaude.com" target="_blank"><span style="font-size:11.0pt;color:purple">jeff.neuman@comlaude.com</span></a><span style="font-size:11.0pt">><span class="apple-converted-space"> </span><br>
<b>Sent:</b><span class="apple-converted-space"> </span>Monday, August 26, 2019 12:43 PM<br>
<b>To:</b><span class="apple-converted-space"> </span>Aikman-Scalese, Anne <</span><a href="mailto:AAikman@lrrc.com" target="_blank"><span style="font-size:11.0pt;color:purple">AAikman@lrrc.com</span></a><span style="font-size:11.0pt">>;<span class="apple-converted-space"> </span></span><a href="mailto:gnso-newgtld-wg@icann.org" target="_blank"><span style="font-size:11.0pt;color:purple">gnso-newgtld-wg@icann.org</span></a><span style="font-size:11.0pt"><br>
<b>Subject:</b><span class="apple-converted-space"> </span>RE: Closed Generics and the 2012 Round</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">[EXTERNAL]</span></strong><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Anne,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Where has it been proposed that applications from 2012 get priority? I am not aware of any recommendation that we have made that gives “priority” to any applicants from 2012. We did recommend that any applications
that were still outstanding for a string that is applied from in a subsequent round be completed. <span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">With respect to Exclusive Generics, the Board resolution on this matter stated that any applications that wanted to maintain their “exclusive generic” status would be “deferred to the next round of the New
gTLD Program, subject to rules developed for the next round…” They did not state that any of those applications would get priority. However, there were no applications that were deferred from the last round.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">If we did allow some form of Exclusive Generic in the next round, then those rules would only apply to new applicants for TLDs. Discussing what happens to TLDs from 2012 that wanted to be Exclusive Generics,
but ended up opening their TLDs because of the Board Resolution is not within the topics contained within our Charter. So yes if we wanted to discuss that issue we would need an amendment to our charter to allow us to tackle that subject. The GNSO could
then either grant our request or farm that issue out to a separate group. That is within their discretion. <span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">This is no different than any other changes we recommend where applicants from the past round would want the same things. For example, if we accept changes to the code of conduct, the COI, reserved names,
agreement, etc., the existing registries would not get the benefit of those changes unless the changes go through a PDP that has jurisdiction over those issues. All Applications / TLDs are treated according the to rules for the round in which they applied.
This is true regardless of whether they have launched yet or not.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">I hope this clears things up.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Jeff Neuman</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Senior Vice President </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Com Laude | Valideus</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">D: +1.703.635.7514</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">E:<span class="apple-converted-space"> </span></span><a href="mailto:jeff.neuman@comlaude.com" target="_blank"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:purple">jeff.neuman@comlaude.com</span></a><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span class="apple-converted-space"><span style="font-size:11.0pt"> </span></span><span style="font-size:11.0pt">Aikman-Scalese, Anne <</span><a href="mailto:AAikman@lrrc.com" target="_blank"><span style="font-size:11.0pt;color:purple">AAikman@lrrc.com</span></a><span style="font-size:11.0pt">><span class="apple-converted-space"> </span><br>
<b>Sent:</b><span class="apple-converted-space"> </span>Monday, August 26, 2019 2:55 PM<br>
<b>To:</b><span class="apple-converted-space"> </span>Jeff Neuman <</span><a href="mailto:jeff.neuman@comlaude.com" target="_blank"><span style="font-size:11.0pt;color:purple">jeff.neuman@comlaude.com</span></a><span style="font-size:11.0pt">>;<span class="apple-converted-space"> </span></span><a href="mailto:gnso-newgtld-wg@icann.org" target="_blank"><span style="font-size:11.0pt;color:purple">gnso-newgtld-wg@icann.org</span></a><span style="font-size:11.0pt"><br>
<b>Subject:</b><span class="apple-converted-space"> </span>RE: Closed Generics and the 2012 Round</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Thanks Jeff. Your reasoning below is not consistent with what has been proposed in relation to giving priority to applications from the 2012 round that have not been withdrawn. (How is it that this “priority”
is in scope for our WG but nothing else re 2012 applicants is in scope? AND if I applied for a Closed Generic and didn’t get it in 2012, why should I have to require another PDP authorization from GNSO Council in order to be treated similarly to new applicants
and convert to a Closed Generic? (I believe some open registries that won contention sets in 2012 may not have not have actually launched yet. Why would we say that whether or not they can launch as a Closed Generic is up to GNSO Council?)</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Thank you,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D">Anne</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span class="apple-converted-space"><span style="font-size:11.0pt"> </span></span><span style="font-size:11.0pt">Gnso-newgtld-wg <</span><a href="mailto:gnso-newgtld-wg-bounces@icann.org" target="_blank"><span style="font-size:11.0pt;color:purple">gnso-newgtld-wg-bounces@icann.org</span></a><span style="font-size:11.0pt">><span class="apple-converted-space"> </span><b>On
Behalf Of<span class="apple-converted-space"> </span></b>Jeff Neuman<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Monday, August 26, 2019 5:27 AM<br>
<b>To:</b><span class="apple-converted-space"> </span>Jeff Neuman <</span><a href="mailto:jeff.neuman@comlaude.com" target="_blank"><span style="font-size:11.0pt;color:purple">jeff.neuman@comlaude.com</span></a><span style="font-size:11.0pt">>;<span class="apple-converted-space"> </span></span><a href="mailto:gnso-newgtld-wg@icann.org" target="_blank"><span style="font-size:11.0pt;color:purple">gnso-newgtld-wg@icann.org</span></a><span style="font-size:11.0pt"><br>
<b>Subject:</b><span class="apple-converted-space"> </span>Re: [Gnso-newgtld-wg] Closed Generics and the 2012 Round</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">[EXTERNAL]</span></strong><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="1" width="100%" align="center">
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Thanks all. We have already got a number of people signed up for the group. I expect substantive discussions on this topic to start this week. So, it is not too late to join. But remember that if you join,
the expectation is that we will attempt to find a compromise solution that we all can live with (if possible).</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">You can view the member list for the small group here: <span class="apple-converted-space"> </span></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_display_NGSPP_Members-2BNew-2BgTLD-2B-253A-2BTopic-2Bof-2BClosed-2BGenerics&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=H2utbrEOw_NamdeHDwVf6dEH3mHdiE-f-Ay-9gKVkPM&e=" target="_blank"><span style="font-size:11.0pt;color:purple">https://community.icann.org/display/NGSPP/Members+New+gTLD+%3A+Topic+of+Closed+Generics</span></a><span style="font-size:11.0pt">
Please allow a day or two to pass before seeing your name on the list if you just volunteered over the weekend or today. <span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">We will not be talking about Closed Generics in our next meeting tomorrow (late tonight for some of us).</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Jeff Neuman</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Senior Vice President </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Com Laude | Valideus</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">D: +1.703.635.7514</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">E:<span class="apple-converted-space"> </span></span><a href="mailto:jeff.neuman@comlaude.com" target="_blank"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:purple">jeff.neuman@comlaude.com</span></a><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span class="apple-converted-space"><span style="font-size:11.0pt"> </span></span><span style="font-size:11.0pt">Gnso-newgtld-wg <</span><a href="mailto:gnso-newgtld-wg-bounces@icann.org" target="_blank"><span style="font-size:11.0pt;color:purple">gnso-newgtld-wg-bounces@icann.org</span></a><span style="font-size:11.0pt">><span class="apple-converted-space"> </span><b>On
Behalf Of<span class="apple-converted-space"> </span></b>Jeff Neuman<br>
<b>Sent:</b><span class="apple-converted-space"> </span>Friday, August 23, 2019 11:01 AM<br>
<b>To:</b><span class="apple-converted-space"> </span></span><a href="mailto:gnso-newgtld-wg@icann.org" target="_blank"><span style="font-size:11.0pt;color:purple">gnso-newgtld-wg@icann.org</span></a><span style="font-size:11.0pt"><br>
<b>Subject:</b><span class="apple-converted-space"> </span>[Gnso-newgtld-wg] Closed Generics and the 2012 Round</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">All,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
There has been a lot of discussion in the past 24 hours or so on the applicability of our work on the 2012 applications. Some have expressed concerns about the “fairness” of establishing a policy or new procedures for subsequent rounds when Closed Generics
were not allowed in 2012. <span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">The applicable Board Resolution covering Closed Generics required the 2012 applicants for Closed Generics to do one of three things. Applicants could have withdrawn their applications completely, signed the
then-current Registry Agreement which did not allow Closed Generics, or could have deferred their applications for consideration in a subsequent round. As we covered on the call on Thursday, all of the applicants chose either to convert their applications
to open TLDs or withdraw their applications completely. There were NO applicants that elected to defer their applications to any future round. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Therefore, although in theory we could have had some issues that we needed to address involving applicants in the 2012 round, the reality is that we do not have any such issues. To address the arguments about
fairness of any new policy recommendations on applicants from the previous round, all we can say is that we need to focus on what the right policy should be first without the consideration of the fairness or unfairness to previous applicants from having different
rules. If we as a group determine that the right policy is something other than what happened in 2012, then it will by up to the GNSO Council to either set up a new group to deal with that issue or to refer the issue to this group at a later date. But for
now, as some have stated, that issue is out of scope for our group. <span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">The reality is that there are many things that this group is considering which could produce results that may treat new applicants differently than previous round applicants. Some of those changes may be
favorable to the new applicants and some less favorable. The same is true with respect to previous applicants. If we did not make any changes to policy or implementation for fear of the impact on previous or new applicants, no changes would ever be made.
The point is that we need to decide what is the right thing to do, point out to the GNSO Council the potential impacts, and then leave it to the Council on what the next steps should be.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Finally, all requests for data or information from ICANN staff or any outside third party should go through the Working Group Leadership team. No working group members should request information directly without
Leadership’s review. Leadership reviews all outstanding action items, including requests for information, and makes a decision on what is necessary and what is feasible. We consider all of these requests seriously and weigh the pros and cons of getting that
data, including time, resources and cost.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
Thanks for your cooperation and let us know if you have any comments or questions. <span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Jeff Neuman</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Senior Vice President </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"> </span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Com Laude | Valideus<br>
</span></b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">1751 Pinnacle Drive<span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">Suite 600, McLean</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">VA 22102, USA</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><br>
M: +1.202.549.5079</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">D: +1.703.635.7514</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif">E:<span class="apple-converted-space"> </span></span><a href="mailto:jeff.neuman@comlaude.com" target="_blank"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:purple">jeff.neuman@comlaude.com</span></a><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif"><br>
</span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.comlaude.com_&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=zLaGJGEf-8oBaC3AfnSvVo4y8MflBPzQD7CgGjBdYzg&e=" target="_blank"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:purple">www.comlaude.com</span></a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt">
<hr size="1" width="100%" align="center">
</span></div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received
this message in error, please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your
responsibility to scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group
includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company
number 06181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland;
Consonum, Inc. dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo,
104-0033, Japan. For further information see<span class="apple-converted-space"> </span></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__comlaude.com&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=yYYJEyktdwZnFCNFpNFQyI8L3rOhFoeCxa2LCDPMDxs&e=" target="_blank"><span style="font-size:11.0pt;color:purple">www.comlaude.com</span></a><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="1" width="100%" align="center">
</div>
<div>
<p class="MsoNormal">The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error,
please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan
or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited
t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and
registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc.
dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan.
For further information see<span class="apple-converted-space"> </span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__comlaude.com&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=yYYJEyktdwZnFCNFpNFQyI8L3rOhFoeCxa2LCDPMDxs&e=" target="_blank"><span style="color:purple">www.comlaude.com</span></a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt">
<hr size="2" width="100%" align="center">
</span></div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><br>
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.<span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<div>
<p class="MsoNormal">The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error,
please return it to the sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that the Com Laude Group does not accept any responsibility for viruses and it is your responsibility to scan
or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group includes Nom-IQ Limited
t/a Com Laude, a company registered in England and Wales with company number 5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 06181291 and
registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Demys Limited, a company registered in Scotland with company number SC197176, having its registered office at 33 Melville Street, Edinburgh, Lothian, EH3 7JF Scotland; Consonum, Inc.
dba Com Laude USA and Valideus USA, headquartered at 1751 Pinnacle Drive, Suite 600, McLean, VA 22102, USA; Com Laude (Japan) Corporation, a company registered in Japan having its registered office at Suite 319,1-3-21 Shinkawa, Chuo-ku, Tokyo, 104-0033, Japan.
For further information see<span class="apple-converted-space"> </span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__comlaude.com&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=yYYJEyktdwZnFCNFpNFQyI8L3rOhFoeCxa2LCDPMDxs&e=" target="_blank"><span style="color:purple">www.comlaude.com</span></a><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><br>
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.<span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">_______________________________________________<br>
Gnso-newgtld-wg mailing list<br>
<a href="mailto:Gnso-newgtld-wg@icann.org" target="_blank"><span style="color:purple">Gnso-newgtld-wg@icann.org</span></a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Dnewgtld-2Dwg&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=-aJrv6kHxrRfqYXCiHRNd34VNYmHXUg0pDYPqDSXKhs&e=" target="_blank"><span style="color:purple">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</span></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://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=iG6qe_goCt4aWXtpuBXIp6Sb3ClH3eLTXFox4Gbj0Aw&e=" target="_blank"><span style="color:purple">https://www.icann.org/privacy/policy</span></a>)
and the website Terms of Service (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=59iexN4kzVbepD9JuY8jXVhaufwdudN7FwX-18NJN9g&e=" target="_blank"><span style="color:purple">https://www.icann.org/privacy/tos</span></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.<o:p></o:p></p>
</div>
</blockquote>
</div>
<pre style="text-align:center"><hr size="2" width="100%" align="center"></pre>
<pre><br>Gnso-newgtld-wg mailing list<br><a href="mailto:Gnso-newgtld-wg@icann.org" target="_blank"><span style="color:purple">Gnso-newgtld-wg@icann.org</span></a><br><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Dnewgtld-2Dwg&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=-aJrv6kHxrRfqYXCiHRNd34VNYmHXUg0pDYPqDSXKhs&e=" target="_blank"><span style="color:purple">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</span></a><o:p></o:p></pre>
<pre style="text-align:center"><hr size="2" width="100%" align="center"></pre>
<pre><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://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=iG6qe_goCt4aWXtpuBXIp6Sb3ClH3eLTXFox4Gbj0Aw&e=" target="_blank"><span style="color:purple">https://www.icann.org/privacy/policy</span></a>) and the website Terms of Service (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=bWlrvG0e9GOVlor1_dA4dFLdn6MSWnd3nWwZNCNMdE4&s=59iexN4kzVbepD9JuY8jXVhaufwdudN7FwX-18NJN9g&e=" target="_blank"><span style="color:purple">https://www.icann.org/privacy/tos</span></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.<o:p></o:p></pre>
</blockquote>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:gray"><br>
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.<span class="apple-converted-space"> </span></span><o:p></o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<div>
<p class="MsoNormal">If you are not an intended recipient of confidential and privileged information in this email, please delete it, notify us immediately at<span class="apple-converted-space"> </span><a href="mailto:postmaster@gtlaw.com"><span style="color:purple">postmaster@gtlaw.com</span></a>,
and do not use or disseminate the information.<o:p></o:p></p>
</div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">_______________________________________________<br>
Gnso-newgtld-wg mailing list<br>
</span><a href="mailto:Gnso-newgtld-wg@icann.org"><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:purple">Gnso-newgtld-wg@icann.org</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><br>
</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Dnewgtld-2Dwg&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=7TSWqBw-2mFTkPdDlbZGVlqM_rvzAH8ViKZ8P1TLHoY&s=9rOgiu-R66apQEiqGcBbT9lknBfGaywE0SSC4VpjKz0&e="><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:purple">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif"><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 (</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=7TSWqBw-2mFTkPdDlbZGVlqM_rvzAH8ViKZ8P1TLHoY&s=OuFfD2zsEVL96T5XlLojTXe4I5aS8eITGBqAQc2Zclg&e="><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:purple">https://www.icann.org/privacy/policy</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">)
and the website Terms of Service (</span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMFaQ&c=2s2mvbfY0UoSKkl6_Ol9wg&r=L7MB7eHT-UoCXD4iA3c7Sm3JrKXt7T1dG3NjBzCxm1c&m=7TSWqBw-2mFTkPdDlbZGVlqM_rvzAH8ViKZ8P1TLHoY&s=N6P2USZxKipeMKS_QtQawlpsID_tyIRrzjkEqitoTvA&e="><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:purple">https://www.icann.org/privacy/tos</span></a><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif">).
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><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>