<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:"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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
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:11.0pt;
font-family:"Calibri",sans-serif;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle24
{mso-style-type:personal-compose;
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.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:100345933;
mso-list-template-ids:-2057908754;}
@list l1
{mso-list-id:208032889;
mso-list-template-ids:332666890;}
@list l1:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:258173437;
mso-list-template-ids:-769769376;}
@list l2:level1
{mso-level-start-at:3;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Anne and all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I spent some time <a href="https://docs.google.com/spreadsheets/d/1oGyha09-e9T8CQyfMcm0ch0Tq8jP4AxR1PXDiWakQsU/edit?usp=sharing">
documenting the differences</a> between the IRT Principles and the SPIRT outline we have. You will see that we did not “pick and choose” which elements to apply and which we should not. In fact, to the extent that it was applicable, we took the language as
is. I think you are now really asking us whether we have copies all of the Working Group guidelines as well as the IRT Principles into the current outline and we have not. Not because we don’t believe it applies, but rather because we were just drafting
an outline and leaving the rest of the details to the IRT. If we want to state that the Working Group guidelines apply, we can state that as well.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To see the comparison, please go here: <a href="https://docs.google.com/spreadsheets/d/1oGyha09-e9T8CQyfMcm0ch0Tq8jP4AxR1PXDiWakQsU/edit?usp=sharing">
https://docs.google.com/spreadsheets/d/1oGyha09-e9T8CQyfMcm0ch0Tq8jP4AxR1PXDiWakQsU/edit?usp=sharing</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The GNSO is “<span style="font-size:12.0pt;color:#333333;background:white">responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the </span>GNSO<span style="font-size:12.0pt;color:#333333;background:white"> as
set forth in these Bylaws". Operational issues and non-policy issues are not set forth as the jurisdiction of the GNSO in the Bylaws. Therefore, by definition, if an issue is operational, it is not an issue for the GNSO. We may want things to be different,
but that is the fact. And that being the case means that if there is agreement that an issue falls into A, B or C, the GNSO Council cannot have the final call.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#333333;background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#333333;background:white">Therefore, if an issue falls into A, B or C, technically, without any other rules set forth, ICANN has the authority to decide without any input at all. However, we are saying
that to the extent that any of these changes has a material impact on applicants or the community, there should be additional predictability checks including the involvement of the SPIRT (as set forth in the outline).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#333333;background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><u><span style="font-size:12.0pt;color:#333333;background:white">Why did we want a Chair as opposed to a GDD Project Manager?</span></u><span style="font-size:12.0pt;color:#333333;background:white"> We discussed previously having a Chair,
because unlike an “IRT” which operates for a limited period of time, this is a Standing Committee which is permanent. Project managers at ICANN come and go depending on the “project”. It made sense from a continuity standpoint to have a Chair and Vice Chairs.
There was also previous discussion in the Working Group that they did not want it to be an ICANN person because there could be bias in having it chaired by ICANN especially in classifying issues as operational or policy, etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#333333;background:white"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:#333333;background:white">Hope this helps.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Jeff Neuman</span></b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Senior Vice President <o:p></o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Com Laude | Valideus</span></b><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">D: +1.703.635.7514<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">E:
</span><u><span lang="EN-GB" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#0563C1"><a href="mailto:jeff.neuman@comlaude.com"><span style="color:blue">jeff.neuman@comlaude.com</span></a><o:p></o:p></span></u></p>
</div>
<p class="MsoNormal"><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"><b>From:</b> Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org>
<b>On Behalf Of </b>Aikman-Scalese, Anne<br>
<b>Sent:</b> Thursday, May 21, 2020 3:12 PM<br>
<b>To:</b> Steve Chan <steve.chan@icann.org>; Julie Hedlund <julie.hedlund@icann.org>; gnso-newgtld-wg@icann.org<br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Proposed Agenda - New gTLD Subsequent Procedures PDP WG - Thursday, 21 May at 03:00 UTC for 90 Minutes<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Jeff, Cheryl, Steve et al,<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">Regarding the process chart, and as discussed on last night’s call, the language in the middle of the chart does not seem accurate. It says that issues “identified” as fitting in A or B are expected to be
<u>decided</u> by ICANN staff. The issue raised in the call last night was who gets to “identify” what bucket the issue falls in. I see staff working with the SPIRT to make those recommendations. SPIRT may agree with staff that an issue falls into A or B,
but Staff should not itself have the final call if there’s an issue. In all cases, buckets A, B, C, D, and E, GNSO Council has the FINAL call. SPIRT is there to discuss and try to classify which bucket the issue goes in and NOT to make policy if it believes
that a policy issue is involved. It’s not at all workable to have one person on the SPIRT be able to kick an issue up to GNSO as policy if the majority believe it can be handled by staff or handled with GNSO Input or Guidance (rather than through policy-making).
(Remember that any GNSO action always takes precedence over the SPIRT .)<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">This “sorting into buckets” function is why it is so important for the SPIRT to have members from all parts of the community (which is supposed to be the case for regular IRTs as per the section I pasted in
chat last night – see Section C of IRT Recruitment in the attachment). It Is clearly NOT working at all to pick and choose different parts of the IRT Guidelines to try to structure the SPIRT as we have done in the current draft. When you do that, you get
“the SPIRT may not be representative” and you leave out FOUNDATIONAL language like “SPIRT recruiting must be very broad and invitations should go to all former regular attending members of the PDP Working Group” which is in Item C of the IRT Guidelines. For
some reason, the draft we have now says the SPIRT team should include at least ONE member of the PDP WG. Why would there be such emphasis on getting just ONE member of the PDP for this Standing IRT? And why do we want to emphasize that the SPIRT may not
be representative rather than emphasizing that recruitment should be broad as shown in the attached IRT Principles and Guidelines?<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">(Last night Paul asked to see the IRT Guidelines. They are attached for your consideration before the next call.)<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">Donna mentioned that staff runs the IRT process. The Guidelines for IRTs state that the staff member is the GDD Project Manager. Every IRT appoints among its members a GNSO Council Liaison. I’m not sure why
we have to call the person heading the SPIRT team a “Chair”. What is wrong with GNSO Council Liaison? THE SPIRIT DOES NOT DECIDE ANYTHING, IT SHOULD CONSIDER ANY ISSUE WITH STAFF AND RECOMMEND WHICH BUCKET THE ISSUE BELONGS IN – A, B, C, D, or E. Staff
should not be telling the SPIRT that something that comes up as an issue in the implementation phase will not be coming to the SPIRT because staff believes it fits in A or B. Staff should be bringing that issue to the SPIRT to see whether the SPIRT agrees
that it is in Bucket A or B.<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">Similarly, Issues that the SPIRT believes fall in C, D, or E, are opportunities for the SPIRT to<u> identify</u> issues, recommend a method of resolving, e.g. use GNSO Input, GNSO Guidance, GNSO EPDP, or even
GNSO PDP and <b>send that recommendation to the GNSO Council</b>. The SPIRT DOES NOT MAKE POLICY. It’s a Standing IRT. It works with staff to make recommendations to process issues in an efficient manner within GNSO guidelines and processes. All IRT Principles
and Guidelines should apply unless there is a clear reason to deviate and so far, I don’t see why we are trying to create a different animal when the Public Comment was – yes, give us a Standing IRT because we know issues arise at later stages.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thank you,<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>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Gnso-newgtld-wg <<a href="mailto:gnso-newgtld-wg-bounces@icann.org">gnso-newgtld-wg-bounces@icann.org</a>>
<b>On Behalf Of </b>Steve Chan<br>
<b>Sent:</b> Wednesday, May 20, 2020 2:07 PM<br>
<b>To:</b> Julie Hedlund <<a href="mailto:julie.hedlund@icann.org">julie.hedlund@icann.org</a>>;
<a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-newgtld-wg] Proposed Agenda - New gTLD Subsequent Procedures PDP WG - Thursday, 21 May at 03:00 UTC for 90 Minutes<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Dear WG Members,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">One of the action items from the 18 May WG call was to develop a process flow chart to help illustrate how the SPIRT may operate. Attached, please find a draft prepared by staff and WG leadership. Note, we try to share documents at a minimum,
24 hours ahead of the call, but there was a short turnaround between calls in this instance. Hopefully this document is still helpful to the discussions for the upcoming call.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best.<o:p></o:p></p>
<p class="MsoNormal">Steve<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Gnso-newgtld-wg <<a href="mailto:gnso-newgtld-wg-bounces@icann.org">gnso-newgtld-wg-bounces@icann.org</a>> on behalf of Julie Hedlund
<<a href="mailto:julie.hedlund@icann.org">julie.hedlund@icann.org</a>><br>
<b>Date: </b>Tuesday, May 19, 2020 at 10:46 AM<br>
<b>To: </b>"<a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a>" <<a href="mailto:gnso-newgtld-wg@icann.org">gnso-newgtld-wg@icann.org</a>><br>
<b>Subject: </b>[Gnso-newgtld-wg] Proposed Agenda - New gTLD Subsequent Procedures PDP WG - Thursday, 21 May at 03:00 UTC for 90 Minutes<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="color:black">Dear all,</span><o:p></o:p></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">Please find below the proposed agenda for the call on </span><b>Thursday, 21 May
<span style="color:black">2020 at </span>03<span style="color:black">:00 UTC </span></b><span style="color:black">for<span class="apple-converted-space"> </span></span><b>90<span style="color:red">
</span><span style="color:black">minutes.</span></b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b><span style="color:black">Proposed Agenda:</span></b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3">Review Agenda/Updates to Statements of Interest<o:p></o:p></li><li class="MsoNormal" style="mso-list:l1 level1 lfo3"><span style="color:black">Discussion of Final Report Topics</span>:
<o:p></o:p></li><ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo3">2.2.2 Predictability:
<a href="https://docs.google.com/document/d/1vBckhFQCCQ-zyvfGGcDB3NWQhodVsffdqbyb6kTwXL4/edit?usp=sharing">
https://docs.google.com/document/d/1vBckhFQCCQ-zyvfGGcDB3NWQhodVsffdqbyb6kTwXL4/edit?usp=sharing</a>, start at page 10<o:p></o:p></li><li class="MsoListParagraph" style="margin-left:0in;mso-list:l1 level2 lfo3">Review "Can't Live With" comments on packages 1-3, time permitting:
<a href="https://docs.google.com/document/d/1Hh8Wj3IwXvi91Am1k4Zoooct2zmPOmVe1pLmjQLuQuo/edit?usp=sharing">
https://docs.google.com/document/d/1Hh8Wj3IwXvi91Am1k4Zoooct2zmPOmVe1pLmjQLuQuo/edit?usp=sharing</a>
<o:p></o:p></li></ol>
<li class="MsoNormal" style="color:black;mso-list:l1 level1 lfo3">AOB<o:p></o:p></li></ol>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">If you need a dial out or would like to submit an apology, please email </span><a href="mailto:gnso-secs@icann.org" title="mailto:gnso-secs@icann.org">gnso-secs@icann.org</a><span style="color:black">.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:black">Kind regards,</span><o:p></o:p></p>
<p class="MsoNormal">Julie<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" 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>
<hr>
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">www.comlaude.com</a>
</body>
</html>