<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi All, <br>
</p>
<p>To borrow and modify a phrase from Anne -- please keep in mind
that that was absolutely nothing in the 2012 AGB that provided for
.BRAND protection (Specification 13 dates back to special action
by the Board in 2014).</p>
<p>In response to widespread calls, we clarified that Closed
Generics would be banned and created a balance in allowing .BRANDS
to be closed. I am assuming that all of this post-2012 work is
being put up for review and re-evalaution...</p>
<p>Best, Kathy<br>
</p>
<p>On 8/28/2019 3:51 PM, Aikman-Scalese, Anne wrote:</p>
<blockquote type="cite"
cite="mid:e5e45c25214741b9be1cd51a11864df3@lrrc.com">
<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: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";}
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:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi Heather,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<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
<b>RSEP </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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">See <a
href="https://www.icann.org/resources/pages/rsep-2014-02-19-en"
moz-do-not-send="true">
https://www.icann.org/resources/pages/rsep-2014-02-19-en</a>
and note the legitimate purpose to “modify” or “remove” an
existing Registry service.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<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 <a
href="http://www.nic.beauty" moz-do-not-send="true">www.nic.beauty</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.)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<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.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Anne<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<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">
Heather Forrest <</span><a
href="mailto:haforrestesq@gmail.com" moz-do-not-send="true"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">haforrestesq@gmail.com</span></a><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">>
<br>
<b>Sent:</b> Tuesday, August 27, 2019 8:44 PM<br>
<b>To:</b> Maxim Alzoba <</span><a
href="mailto:m.alzoba@gmail.com" moz-do-not-send="true"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">m.alzoba@gmail.com</span></a><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">><br>
<b>Cc:</b> Aikman-Scalese, Anne <</span><a
href="mailto:AAikman@lrrc.com" moz-do-not-send="true"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">AAikman@lrrc.com</span></a><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">>;
</span><a href="mailto:gnso-newgtld-wg@icann.org"
moz-do-not-send="true"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif">gnso-newgtld-wg@icann.org</span></a><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif"><br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Closed Generics and
the 2012 Round<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal"><strong><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">[EXTERNAL]</span></strong><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
<div class="MsoNormal" style="text-align:center"
align="center">
<hr width="100%" size="2" align="center">
</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>
<p class="MsoNormal"><o:p> </o:p></p>
</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>
<p class="MsoNormal"><o:p> </o:p></p>
</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
<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>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best wishes,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Heather<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best wishes,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Heather<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, Aug 28, 2019 at 11:51 AM Maxim
Alzoba <<a href="mailto:m.alzoba@gmail.com"
moz-do-not-send="true">m.alzoba@gmail.com</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" style="margin-bottom:12.0pt">Heather,
<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.
<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.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Maxim Alzoba<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">On 28 Aug 2019, at 08:35, Heather
Forrest <<a href="mailto:haforrestesq@gmail.com"
target="_blank" moz-do-not-send="true">haforrestesq@gmail.com</a>>
wrote:<o:p></o:p></p>
<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>
<p class="MsoNormal">Anne, all,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</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>
<p class="MsoNormal"><o:p> </o:p></p>
</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>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Best wishes,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Heather<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<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"
moz-do-not-send="true">AAikman@lrrc.com</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"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#993366"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:11.0pt">From:</span></b><span
style="font-size:11.0pt"> Jeff Neuman <</span><a
href="mailto:jeff.neuman@comlaude.com"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">jeff.neuman@comlaude.com</span></a><span
style="font-size:11.0pt">>
<br>
<b>Sent:</b> Monday, August 26, 2019 12:43
PM<br>
<b>To:</b> Aikman-Scalese, Anne <</span><a
href="mailto:AAikman@lrrc.com"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">AAikman@lrrc.com</span></a><span
style="font-size:11.0pt">>;
</span><a
href="mailto:gnso-newgtld-wg@icann.org"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">gnso-newgtld-wg@icann.org</span></a><span
style="font-size:11.0pt"><br>
<b>Subject:</b> RE: Closed Generics and
the 2012 Round</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><strong><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">[EXTERNAL]</span></strong><o:p></o:p></p>
<div class="MsoNormal"
style="text-align:center" align="center">
<hr width="100%" size="2" align="center">
</div>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt">Anne,</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt">I hope this
clears things up.</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Jeff Neuman</span></b><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Senior Vice President </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Com Laude | Valideus</span></b><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">D: +1.703.635.7514</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">E:
</span><a
href="mailto:jeff.neuman@comlaude.com"
target="_blank" moz-do-not-send="true"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif"
lang="EN-GB">jeff.neuman@comlaude.com</span></a><o:p></o:p></p>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid
#E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:11.0pt">From:</span></b><span
style="font-size:11.0pt">
Aikman-Scalese, Anne <</span><a
href="mailto:AAikman@lrrc.com"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">AAikman@lrrc.com</span></a><span
style="font-size:11.0pt">>
<br>
<b>Sent:</b> Monday, August 26, 2019
2:55 PM<br>
<b>To:</b> Jeff Neuman <</span><a
href="mailto:jeff.neuman@comlaude.com"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">jeff.neuman@comlaude.com</span></a><span
style="font-size:11.0pt">>;
</span><a
href="mailto:gnso-newgtld-wg@icann.org"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">gnso-newgtld-wg@icann.org</span></a><span
style="font-size:11.0pt"><br>
<b>Subject:</b> RE: Closed Generics
and the 2012 Round</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">Thank you,</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D">Anne</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:11.0pt">From:</span></b><span
style="font-size:11.0pt"> Gnso-newgtld-wg
<</span><a
href="mailto:gnso-newgtld-wg-bounces@icann.org"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">gnso-newgtld-wg-bounces@icann.org</span></a><span
style="font-size:11.0pt">>
<b>On Behalf Of </b>Jeff Neuman<br>
<b>Sent:</b> Monday, August 26, 2019 5:27
AM<br>
<b>To:</b> Jeff Neuman <</span><a
href="mailto:jeff.neuman@comlaude.com"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">jeff.neuman@comlaude.com</span></a><span
style="font-size:11.0pt">>;
</span><a
href="mailto:gnso-newgtld-wg@icann.org"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">gnso-newgtld-wg@icann.org</span></a><span
style="font-size:11.0pt"><br>
<b>Subject:</b> Re: [Gnso-newgtld-wg]
Closed Generics and the 2012 Round</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><strong><span
style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black">[EXTERNAL]</span></strong><o:p></o:p></p>
<div class="MsoNormal"
style="text-align:center" align="center">
<hr width="100%" size="1" align="center">
</div>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt">You can view the
member list for the small group here:
</span><a
href="https://community.icann.org/display/NGSPP/Members+New+gTLD+%3A+Topic+of+Closed+Generics"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">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><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Jeff Neuman</span></b><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Senior Vice President </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Com Laude | Valideus</span></b><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">D: +1.703.635.7514</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">E:
</span><a
href="mailto:jeff.neuman@comlaude.com"
target="_blank" moz-do-not-send="true"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif"
lang="EN-GB">jeff.neuman@comlaude.com</span></a><o:p></o:p></p>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid
#E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:11.0pt">From:</span></b><span
style="font-size:11.0pt">
Gnso-newgtld-wg <</span><a
href="mailto:gnso-newgtld-wg-bounces@icann.org"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">gnso-newgtld-wg-bounces@icann.org</span></a><span
style="font-size:11.0pt">>
<b>On Behalf Of </b>Jeff Neuman<br>
<b>Sent:</b> Friday, August 23, 2019
11:01 AM<br>
<b>To:</b> </span><a
href="mailto:gnso-newgtld-wg@icann.org"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">gnso-newgtld-wg@icann.org</span></a><span
style="font-size:11.0pt"><br>
<b>Subject:</b> [Gnso-newgtld-wg]
Closed Generics and the 2012 Round</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt">All,</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"><br>
Thanks for your cooperation and let us
know if you have any comments or
questions.
</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Jeff Neuman</span></b><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Senior Vice President </span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB"> </span></b><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Com Laude | Valideus<br>
</span></b><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">1751 Pinnacle Drive
</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">Suite 600, McLean</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">VA 22102, USA</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB"><br>
M: +1.202.549.5079</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">D: +1.703.635.7514</span><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB">E:
</span><a
href="mailto:jeff.neuman@comlaude.com"
target="_blank" moz-do-not-send="true"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif"
lang="EN-GB">jeff.neuman@comlaude.com</span></a><span
style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"
lang="EN-GB"><br>
</span><a href="http://www.comlaude.com/"
target="_blank" moz-do-not-send="true"><span
style="font-size:9.0pt;font-family:"Arial",sans-serif"
lang="EN-GB">www.comlaude.com</span></a><o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><o:p> </o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<div class="MsoNormal"
style="text-align:center" align="center"><span
style="font-size:11.0pt">
<hr width="100%" size="1" align="center">
</span></div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><a href="https://comlaude.com"
target="_blank" moz-do-not-send="true"><span
style="font-size:11.0pt">www.comlaude.com</span></a><span
style="font-size:11.0pt">
</span><o:p></o:p></p>
<div class="MsoNormal"
style="text-align:center" align="center">
<hr width="100%" size="1" align="center">
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">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
<a href="https://comlaude.com"
target="_blank" moz-do-not-send="true">
www.comlaude.com</a> <o:p></o:p></p>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
style="font-size:11.0pt"> </span><o:p></o:p></p>
<div class="MsoNormal"
style="text-align:center" align="center"><span
style="font-size:11.0pt">
<hr width="100%" size="2" align="center">
</span></div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><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><o:p></o:p></p>
<div class="MsoNormal"
style="text-align:center" align="center">
<hr width="100%" size="2" align="center">
</div>
<p class="MsoNormal"
style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">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
<a href="https://comlaude.com"
target="_blank" moz-do-not-send="true">
www.comlaude.com</a> <o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" style="text-align:center"
align="center">
<hr width="100%" size="2" align="center">
</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><o:p></o:p></p>
</div>
<p class="MsoNormal">_______________________________________________<br>
Gnso-newgtld-wg mailing list<br>
<a href="mailto:Gnso-newgtld-wg@icann.org"
target="_blank" moz-do-not-send="true">Gnso-newgtld-wg@icann.org</a><br>
<a
href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg"
target="_blank" moz-do-not-send="true">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"
target="_blank" moz-do-not-send="true">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a
href="https://www.icann.org/privacy/tos"
target="_blank" moz-do-not-send="true">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.<o:p></o:p></p>
</blockquote>
</div>
<pre style="text-align:center"><hr width="100%" size="2" align="center"></pre>
<pre>
Gnso-newgtld-wg mailing list
<a href="mailto:Gnso-newgtld-wg@icann.org" target="_blank" moz-do-not-send="true">Gnso-newgtld-wg@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg" target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a><o:p></o:p></pre>
<pre style="text-align:center"><hr width="100%" size="2" align="center"></pre>
<pre>
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" target="_blank" moz-do-not-send="true">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank" moz-do-not-send="true">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.<o:p></o:p></pre>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
<br>
<hr>
<font size="1" face="Arial" 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.
<br>
</font>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Gnso-newgtld-wg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-newgtld-wg@icann.org">Gnso-newgtld-wg@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg">https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg</a>
_______________________________________________
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 class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" 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.</pre>
</blockquote>
</body>
</html>