<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:Verdana;
panose-1:2 11 6 4 3 5 4 4 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;}
p
{mso-style-priority:99;
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;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
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.EmailStyle19
{mso-style-type:personal;
font-family:"Times New Roman",serif;
color:black;
font-weight:normal;
font-style:normal;}
span.EmailStyle21
{mso-style-type:personal-reply;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Paul – I think you forgot one section, though I understand you agreed to this language as well:<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">From Justine’s email:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt">To this end, I support Anne's proposed compromise language to be applied towards the original recommendation
<u>in full</u>, which I now suggest should be condensed to read as,<o:p></o:p></p>
<p class="MsoNormal">"<i>Recommendation xx: To the extent that the GAC provides GAC Consensus Advice (as defined in the ICANN Bylaws) in the future on categories of TLDs, the GAC should provide this Advice prior to the finalization of the next Applicant Guidebook.
<b>In the event that GAC Consensus Advice is issued after the application period has begun and
<u><span style="color:blue">whether</span></u> the GAC Consensus Advice applies to categories, groups or classes of applications or string types,
<u><span style="color:blue">or to a particular string,</span></u> the ICANN Board should take into account the circumstances resulting in such timing and the
<u>possible</u> detrimental effect of such timing <u>in determining whether to accept or override such GAC Consensus Advice as provided in the Bylaws</u>.</b></i><b>" </b><o:p></o:p></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>
<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"> McGrady, Paul D. <PMcGrady@taftlaw.com>
<br>
<b>Sent:</b> Tuesday, May 5, 2020 1:45 PM<br>
<b>To:</b> Justine Chew <justine.chew@gmail.com>; gnso-newgtld-wg@icann.org; Aikman-Scalese, Anne <AAikman@lrrc.com>; Jeff Neuman <jeff.neuman@comlaude.com><br>
<b>Subject:</b> RE: [Gnso-newgtld-wg] Revisions to sections on GAC Advice - Current Status?<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<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" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
</div>
<p class="MsoNormal"><span style="color:black">Anne, Justine, All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Thank you so much for the spirit of collaboration that you brought to this discussion. I know everyone’s time is valuable, so I especially appreciate your investing your time into finding a solution. While I
would have liked a more strict approach, I fully understand your concerns and I also fully understand that part of this WG process is not always getting everything you want . I believe the formulation that Anne produced and that Justine agreed with is probably
the best we are going to get in this review and I support it. Thanks again!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Jeff/Staff, can you please bring forward the Anne/Justine/Paul version for discussion on tomorrow’s call? Here it is again from Justine’s email below:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><i>"Section 3.1 of the 2012 Applicant Guidebook states that GAC Advice “will create a strong presumption for the ICANN Board that the application should not be approved.”
<b><u>Noting that this language does not have a basis in the current version of the ICANN Bylaws</u></b><u>, the Working Group recommends omitting this language in future versions of the Applicant Guidebook to bring the Applicant Guidebook in line with the
Bylaws language</u>. The Working Group further notes that the language may have the
<u>unintended consequence of hampering the ability for applicants, ICANN org, and the GAC to mitigate concerns and reach a mutually acceptable solution as described in the relevant Bylaws language, which could allow an application to proceed</u>.</i>"<o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Thanks all!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">Paul<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black"><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"> Gnso-newgtld-wg <<a href="mailto:gnso-newgtld-wg-bounces@icann.org">gnso-newgtld-wg-bounces@icann.org</a>>
<b>On Behalf Of </b>Justine Chew<br>
<b>Sent:</b> Saturday, May 2, 2020 1:10 AM<br>
<b>To:</b> <a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Revisions to sections on GAC Advice - Current Status?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Paul, <br>
<br>
Thank you for noting my rejection to your original proposed text on Recommendation xx in the googledoc.<br>
<br>
Along with others in this thread, I cannot accept your proposed amended text of "...
<b><u><span style="font-family:"Arial",sans-serif">which should result in a strong presumption against the Board adopting such late GAC Consensus Advice</span></u></b><span style="font-family:"Arial",sans-serif">.]</span> " either.<br>
<br>
<br>
All,<br>
<br>
Anne has pointed out what I wanted to say in addition, but I will raise one further rationale for my rejection.<br>
<br>
Given the current Bylaws, Recommendation xx (rationale 3) seeks to remove from the AGB "a strong presumption" in favour of GAC Advice and I quote, as proposed,<o:p></o:p></p>
<blockquote style="margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal"><i>"Section 3.1 of the 2012 Applicant Guidebook states that GAC Advice “will create a strong presumption for the ICANN Board that the application should not be approved.”
<b><u>Noting that this language does not have a basis in the current version of the ICANN Bylaws</u></b><u>, the Working Group recommends omitting this language in future versions of the Applicant Guidebook to bring the Applicant Guidebook in line with the
Bylaws language</u>. The Working Group further notes that the language may have the
<u>unintended consequence of hampering the ability for applicants, ICANN org, and the GAC to mitigate concerns and reach a mutually acceptable solution as described in the relevant Bylaws language, which could allow an application to proceed</u>.</i>"<o:p></o:p></p>
</blockquote>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Since we are noting that such a strong presumption in favour of GAC Advice does not have a basis in the current version of the Bylaws, I cannot in the same breath accept your (amended) proposal which provides for another strong presumption to arise, albeit
against GAC Advice this time. The same would apply whether the GAC Advice pertains to applications for categories, groups or classes of applications or string types
<u>or for a particular string,</u> IMO - recalling that "any new gTLD application or string" was the subject of the WG's questions on the role of GAC Advice in the Initial Report. <br>
<br>
Thus, I would like to address the proposed recommendation in question in totality, for completeness sake.<br>
<br>
To this end, I support Anne's proposed compromise language to be applied towards the original recommendation
<u>in full</u>, which I now suggest should be condensed to read as,<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<blockquote style="margin-left:30.0pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">"<i>Recommendation xx: To the extent that the GAC provides GAC Consensus Advice (as defined in the ICANN Bylaws) in the future on categories of TLDs, the GAC should provide this Advice prior to the finalization of the next Applicant Guidebook.
<b>In the event that GAC Consensus Advice is issued after the application period has begun and
<u><span style="color:blue">whether</span></u> the GAC Consensus Advice applies to categories, groups or classes of applications or string types,
<u><span style="color:blue">or to a particular string,</span></u> the ICANN Board should take into account the circumstances resulting in such timing and the
<u>possible</u> detrimental effect of such timing <u>in determining whether to accept or override such GAC Consensus Advice as provided in the Bylaws</u>.</b></i><b>" </b><o:p></o:p></p>
</div>
</blockquote>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
Justine<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal">On Sat, 2 May 2020 at 04:44, Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com" target="_blank">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:#002060">Hi Paul,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#002060">I have two issues with the recommended change to the language:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#002060"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#002060">1. It does not adequately warn applicants who are not already part of the ICANN system that the ByLaws accord a certain status to GAC Consensus Advice,
i.e. it takes 11 directors to override it. In this regard, we need to let potential applicants know how that advice might affect their chances of proceeding. </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#002060"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#002060">2. Your proposed language still looks like an attempted change in the standard that is applicable (via the ByLaws) to GAC Consensus Advice As you know,
that was all reviewed and decided upon in all the work that was done in Accountability Workstream 2 . (We don’t want to propose language or standards that the Board is going to reject or that would require a Fundamental ByLaws Amendment in order for them
to accept. As you know, there are lots of triggers related to Empowered Community procedures for proposed amendments to the ByLaws.)</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#002060"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#002060">So I want to suggest a compromise as follows.</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-family:"Arial",sans-serif;color:#222222">In the event that GAC Consensus Advice is issued after the application period has begun and the GAC Consensus Advice
applies to categories, groups or classes of applications or string types, the ICANN Board should take into account the circumstances resulting in such timing and the
<u>possible</u> detrimental effect of such timing <u>in determining whether to accept or override such GAC Consensus Advice as provided in the ByLaws.</u></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-family:"Arial",sans-serif;color:#222222"> </span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Arial",sans-serif;color:#002060">Anne</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="color:#1F497D"> </span></b><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;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> McGrady, Paul D. <<a href="mailto:PMcGrady@taftlaw.com" target="_blank">PMcGrady@taftlaw.com</a>>
<br>
<b>Sent:</b> Friday, May 1, 2020 4:57 AM<br>
<b>To:</b> Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>>; Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com" target="_blank">AAikman@lrrc.com</a>>; Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com" target="_blank">jeff.neuman@comlaude.com</a>>;
Cheryl Langdon-Orr (<a href="mailto:cheryl@hovtek.com.au" target="_blank">cheryl@hovtek.com.au</a>) <<a href="mailto:cheryl@hovtek.com.au" target="_blank">cheryl@hovtek.com.au</a>>;
<a href="mailto:gnso-newgtld-wg@icann.org" target="_blank">gnso-newgtld-wg@icann.org</a><br>
<b>Subject:</b> RE: Revisions to sections on GAC Advice - Current Status?</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>
<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" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Hi All,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">I have not been able to connect with Greg on this as hoped. Even so, I submit the following change which I believes deals with concerns some have raised
that we cannot tie the ICANN Board’s hands but at the same time want to create a sense of urgency-leading-to-predictability in relationship to when the GAC gives advice:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><u><span style="font-family:"Arial",sans-serif;color:#222222"> </span></u><span style="font-family:"Arial",sans-serif;color:#222222">[ In the event that GAC Consensus Advice is
issued after the application period has begun and the GAC Consensus Advice applies to categories, groups or classes of applications or string types, the ICANN Board should take into account the circumstances resulting in such timing and the detrimental effect
of such timing when considering such<u> </u>GAC Consensus Advice <b><u>which should result in a strong presumption against the Board adopting such late GAC Consensus Advice</u></b>.]<u> </u></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">I hope this balance is acceptable to the WG. This is an area of failure for the community in the last round and I think it would be really unfortunate
if we set ourselves up for failure again by not addressing it in the new AGB.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black;background:yellow">Jeff/Cheryl</span><span style="color:black">, will one of you please confirm receipt and that this will be on our agenda for discussion
in the appropriate WG call? Thanks!</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Best,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Paul</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </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>
<p><span style="font-family:"Arial",sans-serif;color:#97999B">To receive regular COVID-19 updates from Taft, </span><span style="font-family:"Arial",sans-serif;color:#A22831"><a href="https://www.taftlaw.com/general/subscribe" target="_blank"><span style="color:#A22831">subscribe
here</span></a></span><span style="font-family:"Arial",sans-serif;color:#97999B">. For additional resources, visit Taft's COVID-19
</span><span style="font-family:"Arial",sans-serif;color:#A22831"><a href="https://www.taftlaw.com/general/coronavirus-covid-19-resource-toolkit" target="_blank"><span style="color:#A22831">Resource Toolkit</span></a></span><span style="font-family:"Arial",sans-serif;color:#97999B">.</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#97999B"><br>
<br>
This message may contain information that is attorney-client privileged, attorney work product or otherwise confidential. If you are not an intended recipient, use and disclosure of this message are prohibited. If you received this transmission in error, please
notify the sender by reply e-mail and delete the message and any attachments.</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;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Greg Shatan <<a href="mailto:gregshatanipc@gmail.com" target="_blank">gregshatanipc@gmail.com</a>>
<br>
<b>Sent:</b> Tuesday, April 28, 2020 4:37 PM<br>
<b>To:</b> Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com" target="_blank">AAikman@lrrc.com</a>><br>
<b>Cc:</b> Jeff Neuman <<a href="mailto:jeff.neuman@comlaude.com" target="_blank">jeff.neuman@comlaude.com</a>>; Cheryl Langdon-Orr (<a href="mailto:cheryl@hovtek.com.au" target="_blank">cheryl@hovtek.com.au</a>) <<a href="mailto:cheryl@hovtek.com.au" target="_blank">cheryl@hovtek.com.au</a>>;
<a href="mailto:gnso-newgtld-wg@icann.org" target="_blank">gnso-newgtld-wg@icann.org</a>; McGrady, Paul D. <<a href="mailto:PMcGrady@taftlaw.com" target="_blank">PMcGrady@taftlaw.com</a>><br>
<b>Subject:</b> Re: Revisions to sections on GAC Advice - Current Status?</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>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Verdana",sans-serif">Sorry to have missed last night's witching hour call and sorry this is not done. You can blame me, not Paul. i will look at the
last bit of language in play this evening and hammer something out with Paul.</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>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On Tue, Apr 28, 2020 at 5:03 PM Aikman-Scalese, Anne <<a href="mailto:AAikman@lrrc.com" target="_blank">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>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><img border="0" width="31" height="31" style="width:.3229in;height:.3229in" id="m_-6594625084860747657m_3176221930272278164gmail-m_-444658838676738239_x005f_x0000_i1026" src="cid:image001.gif@01D622E3.FE469F10"><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Jeff and Cheryl (and Paul McGrady),<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Jeff, you said that if there were any proposed changes to the GAC Advice language, we should get those in by May 1.
<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">However, the last time the WG looked at this, Paul had inserted a number of redline changes into the document. So which version are you expecting us to use when you ask for proposals
to be made no later than May 1? And are these alternate proposals supposed to come in the form of redlines to the WG document in the same manner that Paul used?<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">I had understood that Paul was doing some redrafting of his numerous edits. Or was there another small group that was supposed to be convened on this point?<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">I don’t see any way we can cancel the discussion on the language covering GAC Advice, even though you suggested at the top of the last call that we might.<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">Thank you,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Anne<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"> <o:p></o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<b><span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#AF272F">Anne E. Aikman-Scalese</span></b><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#323232">Of Counsel</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#323232">520.629.4428 office</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#323232">520.879.4725 fax</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif"><a href="mailto:AAikman@lrrc.com" target="_blank" title="Email User"><span style="color:#AF272F">AAikman@lrrc.com</span></a></span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#323232">_____________________________</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif"><img border="0" width="115" height="46" style="width:1.1979in;height:.4791in" id="m_-6594625084860747657m_3176221930272278164gmail-m_-444658838676738239gmail-m_5847846078526167064Picture_x0020_1" src="cid:image002.png@01D622E3.FE469F10"></span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#323232">Lewis Roca Rothgerber Christie LLP</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#323232">One South Church Avenue, Suite 2000</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#323232">Tucson, Arizona 85701-1611</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif"><a href="http://lrrc.com/" target="_blank" title="Lewis Roca Rothgerber Christie Webpage"><span style="color:#AF272F">lrrc.com</span></a></span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-top:2.0pt;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:9.0pt;line-height:105%;font-family:"Arial",sans-serif"><img border="0" width="120" height="39" style="width:1.25in;height:.4062in" id="m_-6594625084860747657m_3176221930272278164gmail-m_-444658838676738239gmail-m_5847846078526167064Picture_x0020_2" src="cid:image003.jpg@01D622E3.FE469F10"></span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-top:2.0pt;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:10.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#323232">Because what matters</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:105%">
<span style="font-size:10.0pt;line-height:105%;font-family:"Arial",sans-serif;color:#323232">to you, matters to us.™</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt"></td>
</tr>
</tbody>
</table>
<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"> <o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" align="center">
</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>
</blockquote>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"> <o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="3" width="100%" 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">Gnso-newgtld-wg@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/gnso-newgtld-wg" target="_blank">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">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" target="_blank">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>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><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>
</body>
</html>