<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:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:0cm;
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;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle35
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle36
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle37
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle38
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle39
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle40
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle42
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle43
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle44
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle45
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle46
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle47
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle48
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle49
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle50
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle51
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle52
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle53
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle54
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle55
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle56
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle57
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle58
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle59
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle60
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle61
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle62
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle63
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle64
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle65
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle66
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle67
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle68
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle69
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle70
{mso-style-type:personal;
color:#1F497D;}
span.EmailStyle72
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1126317470;
mso-list-type:hybrid;
mso-list-template-ids:1648645868 -1023762440 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:23;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hi Anne,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks for your question. Minority views are discussed in Section 3.6. For ease of reference, here is an excerpt of the relevant language:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><i>Minority View - refers to a proposal where a small number of people support the recommendation. This can happen in response to a Consensus, Strong support but significant opposition, and No Consensus; or, it can happen in cases where
there is neither support nor opposition to a suggestion made by a small number of individuals.
<o:p></o:p></i></p>
<p class="MsoNormal"><i><o:p> </o:p></i></p>
<p class="MsoNormal"><i>In cases of Consensus, Strong support but significant opposition, and No Consensus, an effort should be made to document that variance in viewpoint and to present any Minority View recommendations that may have been made. Documentation
of Minority View recommendations normally depends on text offered by the proponent(s). In all cases of Divergence, the WG Chair should encourage the submission of minority viewpoint(s).<o:p></o:p></i></p>
<p class="MsoNormal"><o:p></o:p></p>
<p class="MsoNormal">Kind regards,<o:p></o:p></p>
<p class="MsoNormal">Emily<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 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">"Aikman-Scalese, Anne" <AAikman@lrrc.com><br>
<b>Date: </b>Tuesday, 7 January 2020 at 23:57<br>
<b>To: </b>Emily Barabas <emily.barabas@icann.org>, "gnso-newgtld-wg@icann.org" <gnso-newgtld-wg@icann.org><br>
<b>Subject: </b>[Ext] RE: Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 7 January 2020<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D">Thanks for these notes. Regarding the Action Item to distribute 3.6 of the Working Group guidelines re stating a rationale when Consensus is not achieved, I assume this provision will also cover the option for
Minority Statements. If for any reason 3.6 does not cover that option, I would ask that Leadership circulate the language from the WG guidelines that does cover Minority Statements.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Just can’t remember the specifics here.</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Thank you,</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D">Anne</span><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b>From:</b> Gnso-newgtld-wg <gnso-newgtld-wg-bounces@icann.org>
<b>On Behalf Of </b>Emily Barabas<br>
<b>Sent:</b> Tuesday, January 7, 2020 4:40 AM<br>
<b>To:</b> gnso-newgtld-wg@icann.org<br>
<b>Subject:</b> [Gnso-newgtld-wg] Notes and Action Items - New gTLD Subsequent Procedures PDP WG - 7 January 2020<o:p></o:p></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;color:black">[EXTERNAL]</span></strong><o:p></o:p></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman",serif">
<hr size="2" width="100%" align="center">
</span></div>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt">Dear </span>Working Group members,<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Please see below the notes from the meeting on 7 January 2020.
<b><i>These high-level notes are designed to help WG members navigate through the content of the call and are not a substitute for the recording, transcript, or the chat,</i></b> which will be posted at:
<a href="https://community.icann.org/display/NGSPP/2020-01-07+New+gTLD+Subsequent+Procedures+PDP">
https://community.icann.org/display/NGSPP/2020-01-07+New+gTLD+Subsequent+Procedures+PDP</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">As a follow-up to the first action item below, the Working Group discussed the principle that the SPIRT should be able to provide input regardless of the level of consensus achieved on recommendations. A Working Group member raised on the
call that a rationale should accompany the different perspectives within the SPIRT when there is a division of opinion within the group. Working Group members are encouraged to review the Standard Methodology for Making Decisions in Section 3.6 of the Working
Group Guidelines to see if there is sufficient guidance in Section 3.6 about documenting the rationale supporting different views. Section 3.6 is available on page 8 of the WG Guidelines:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_sites_default_files_file_field-2Dfile-2Dattach_annex-2D1-2Dgnso-2Dwg-2Dguidelines-2D24oct19-2Den.pdf&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=cZa8Ys7TFh5-vHgTE-inLGN0K3kCVe569TIMefSckWY&s=lxD95Af-MltNeihVTIQ2QiTyxqZDOAGW9z0_x4KgZcE&e=">
<span style="color:blue">https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-1-gnso-wg-guidelines-24oct19-en.pdf</span> [gnso.icann.org]</a><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal">Kind regards,<br>
Emily<o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>Notes and Action Items:</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><b>ACTION ITEM: Leadership will circulate Section 3.6 of the WG Guidelines to so that the group can review if it adequately addresses providing a rationale when opinion is divided and there is not consensus.</b><o:p></o:p></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><a name="OLE_LINK1"></a><a name="OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"><b>ACTION ITEM: Throughout the document, change “raised” an issue with the SPIRT to “forwarded.”</b><o:p></o:p></span></a></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"><b> </b><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"><b>Notes</b><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">1. Review Agenda/Statements of Interest<o:p></o:p></span></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormalCxSpLast" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">No updates to SOIs<o:p></o:p></span></span></li></ul>
<p class="MsoListParagraph"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">2. Work Plan<o:p></o:p></span></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">This will be discussed at a high level today. A more detailed work plan will be available at the end of this week or beginning
of next week.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Original plan was to hold a public comment period at the beginning of this year, with delivery of the Final Report by the
end of Q1. This plan will need to be revised. <o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Documents are under development on each of the topics in this PDP, narrowly focused on areas of agreement with the intent
to reach draft final recommendations.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">We will have another public comment period. The leadership team has been discussing how to structure this in line with
feedback received. <o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Leadership team recommends making all draft recs available during the public comment period, but seeking feedback on specific
areas that have not been out for public comment previously. We can’t stop people from making comments on other areas, but we will make clear that the focus will be on topics for which we are seeking input.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">In one of the upcoming meetings, we will go over one of the recommendations documents drafted on one of the “easier” topics
so everyone can review approach and format that will put forward for public comment.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Question – if the WG gets feedback from Board, GAC, SSAC or other groups on sections of the Report that we don’t request
feedback on, what are we going to do with that? The input could be important and valuable and we don’t want to disenfranchise anyone.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Answer – We will need to make a judgment call in these cases and determine whether the input needs to go through another
layer of analysis. <o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Auction Proceeds Proposed Final Report – this went out for public comment recently. There were three specific questions
that commenters were asked to focus on, but people can provide comments on other topics as well. This might be a model to use for SubPro.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Question – how do we distinguish between areas that are new and haven’t been covered (and therefore require public comment)
and those that have not? This sounds subjective. <o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Answer – For example, if the group concludes that we are going to do a series of fixed rounds, and someone puts in a comment
supporting first-come, first-served, we are going to respond that we have already considered this and the issue is closed. We don’t want to rehash what has already been reviewed where a decision has been made.
<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Some WG members supported making sure that new suggestions and ideas are considered.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">On areas that are new, like the predictability model or if we come up with something new for contention resolution, we
will ask focused questions and encouraging comments.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Staff clarification – draft policy recommendations documents will not all be discussion papers. Discussion papers have
been focused on those topics where there needs to be further discussion. For most topics, the intention is to develop draft policy recommendations with rationale, as well limited text on deliberations focused on issues raised since the last public comment.
These will follow the format of the WT5 Final Report.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Question – Will CCT-RT recs be discussed in the report with explanation of how the WG is addressing them?<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Chart that was reviewed by the group late last year includes state of the discussion on each recommendation and also includes
SubPro topics that are applicable to each recommendation. The CCT-RT recs will be addressed in the applicable sections of the final report.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">As we review draft recommendations, it’s important for everyone to review the materials in advance. If there are open issues
that are not included in the documents, it’s important to raise them on the mailing list before the call where the topic will be covered.<o:p></o:p></span></span></li></ul>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">3. Predictability Framework:<o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">a. Summary Document: </span></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_12-5Fx8zYR9r6zXqfA7dmoosSPH12NmcyJ-2D2FEjecGrBh4_edit-23heading-3Dh.7kd5yr7uelh2&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=cZa8Ys7TFh5-vHgTE-inLGN0K3kCVe569TIMefSckWY&s=0b6Nw0OQWLyY2RoXMWngF0SuMVZhzcH-Y1INc_dUkes&e="><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">https://docs.google.com/document/d/12_x8zYR9r6zXqfA7dmoosSPH12NmcyJ-2FEjecGrBh4/edit#heading=h.7kd5yr7uelh2
[docs.google.com]</span></span><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"></span></span></a><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"><o:p></o:p></span></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Review of the issue we are trying to address - How do we address changes after the launch of the next round of the New
gTLD Program? How do we deal with unanticipated issues?<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Review of policy goals - Regarding when the Predictability Framework commences, leadership team believes it should become
applicable once the AGB is finalized (as opposed to when the application window opens), but the WG needs to come to agreement on this.<o:p></o:p></span></span></li><li class="MsoNormalCxSpLast" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Review of the proposal – recommending the formation of a Standing Predictability Implementation Review Team to review potential
changes to the program.<o:p></o:p></span></span></li></ul>
<p class="MsoListParagraph"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">b. Proposed Answers to Open Questions: </span></span><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1xDaENKupUoHSfIQ20klw0NYZK1Qwm43l56EvISHJi7Q_edit-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mBQzlSaM6eYCHFBU-v48zs-QSrjHB0aWmHuE4X4drzI&m=cZa8Ys7TFh5-vHgTE-inLGN0K3kCVe569TIMefSckWY&s=cgAdcdi6a2qG8JVdQrfRy9tbffSol6-oVi7mqEEtn30&e="><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">https://docs.google.com/document/d/1xDaENKupUoHSfIQ20klw0NYZK1Qwm43l56EvISHJi7Q/edit?usp=sharing
[docs.google.com]</span></span><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"></span></span></a><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Review of proposed Role of the SPIRT – staff to correct text to note that the SPIRT comes into play after approval of the
AGB.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Staff note – the WG discussed that existing documents might be a basis for materials regarding the SPIRT. This document
attempts to pull elements from the IRT Guidelines, CSC and PDP charters, and IoT Guidelines that might be applicable to the SPIRT.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Review of role of the GNSO – Some agreement that the second bullet is redundant and can be removed.
<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Review of who can raise an issue to the SPIRT and rationale.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Question – does the GNSO Council have a mechanism in which it can provide feedback in a rapid fashion?<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Answer – this will be discussed under the next section: how can each of these groups raise an issue? The GNSO may need
to tailor some of its existing procedures. One of our recommendations could be that they develop that.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">No objections raised to Board and Org having the ability to raise issues.
<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Regarding the GNSO Council, there are different options of who can raise an issue. This will have an impact on timing.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">We shouldn’t develop process for the sake of developing processes.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Comment - There is nothing stopping a PDP or PDP leadership team from asking Council for input. This is a good starting
point. There is no reason for Council not to be able to be nimble in responding. The Council Liaison could be a tool that could be more extensively used as well.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Response - It might not be that someone from the SPIRT group is asking Council for input. It would likely be someone from
the community raising it to Council, and the issue is raised within Council. The question is about what the threshold will be for Council to take up the issue.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Some support for the fact that raising an issue within Council should be informal and could be raised by a single Councilor.
From this perspective, voting and a more formal mechanism is appropriate to determine how the issue is handled – SPIRT or other process/mechanism.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">We are starting with the assumption that if the GNSO Council wants to send something to the SPIRT team and determining
what happens next. This is the perspective we are coming from. <o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">From one perspective, we would need to state that Council has not elected to use other processes. It is important to be
clear about procedures.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">For item 5. Suggestion to rephrase the category: “How can each of these groups raise an issue to the SPIRT?”<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">There are difficult questions about the mechanism of how issues get raised to Council. We need to think about the relationship
between SG/Cs and Council, Council Members as representatives of the SG/Cs, etc. We could suggest an email address where community members can raise issues to Council. There is no halfway approach – either you leave it to Council to figure out how to handle
or you provide a detailed approach recommending how Council carries this out.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Reminder that the SPIRT is advisory in nature, which may make it less political.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Concern that allowing one Councilor to send an issue to the SPIRT might leave the SPIRT susceptible to lobbying.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Suggestion to pick and propose one of the options under section 5 and put it out for public comment.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Clarification regarding the options available – if a Constituency could raise an issue, the IPC alone could raise the issue
(for example). But if a Stakeholder Group is the minimum threshold, it would need to be the whole CSG that is raising the issue to Council.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Review of decision-making process of SPIRT – Clarification – this group should be able to report its advice regardless
of the level of support achieved. Text may need clarification. We may not only want to report the divisions of perspectives but also the rationales.
<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Leadership believes that this is largely covered in Section 3.6 of the Working Group Guidelines.
<o:p></o:p></span></span></li><li class="MsoNormalCxSpLast" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">This group is different, less formal than at WG. If the SPIRT group is divided, it needs to be clear why.<o:p></o:p></span></span></li></ul>
<p class="MsoListParagraph"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"><b>ACTION ITEM: Leadership will circulate Section 3.6 of the WG Guidelines to so that the group can review if it adequately addresses providing a rationale when opinion
is divided and there is not consensus.</b><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormalCxSpLast" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Section 7 – review of who receives Advice/Guidance issued by the SPIRT?<o:p></o:p></span></span></li></ul>
<p class="MsoListParagraph"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"><b>ACTION ITEM: Throughout the document, change “raised” an issue with the SPIRT to “forwarded.”</b><o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Comment regarding section 5 that there should be text that processes should be carried out expeditiously.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">The WG will start with section 8 on the next call.
<o:p></o:p></span></span></li></ul>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">c. Process Flow Chart (to be provided)<o:p></o:p></span></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormalCxSpLast" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Item deferred.
<o:p></o:p></span></span></li></ul>
<p class="MsoListParagraph"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">4. String Contention Mechanisms of Last Resort (time permitting): <o:p></o:p></span></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Item deferred.
<o:p></o:p></span></span></li></ul>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">5. AOB <o:p></o:p></span></span></p>
<p class="MsoNormal"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">a. Update from meeting of the ICANN Board/Senior ICANN org management/SubPro leadership/Council leadership<o:p></o:p></span></span></p>
<p class="MsoNormal" style="margin-left:72.0pt"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1"> <o:p></o:p></span></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">In attendance: Jeff and Cheryl from SubPro; Goran and Cyrus from ICANN org; Keith, Pam, Rafik from Council leadership;
Becky and Avri from the Board.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Board wants to be aware of particularly thorny issues that are coming their way and the timing of when issues will reach
the Board.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">The Board will likely be getting more letters from SO/ACs and other interested parties, and this is a way of opening up
communications between the PDP, Org, and Board on handling the issues raised.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">ICANN org has set up an executive team to start planning processes to implement next round.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">If, for example, the WG expects to put forward a recommendation that is in conflict with GAC Advice, the Board will want
to know this.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">The goal is to be in closer communication and flag an issues in advance.
<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">If anything of note comes up on these coordination calls in the future, the SubPro Co-Chairs will share with the WG.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">Board requested current thinking of the WG on the public comment period as letters from the GAC and ALAC went to the Board.
Co-Chairs said that they would talk with the WG and make sure there is agreement on the approach and then share this approach with the Board.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">The purpose is to avoid as many surprises as possible through early and regular communication.<o:p></o:p></span></span></li><li class="MsoNormalCxSpMiddle" style="mso-list:l0 level1 lfo2"><span style="mso-bookmark:OLE_LINK2"><span style="mso-bookmark:OLE_LINK1">GAC is interested in learning in advance how SubPro recommendations may deviate from their advice. This is not something
we have started working on but it has been requested.<o:p></o:p></span></span></li></ul>
<span style="mso-bookmark:OLE_LINK1"></span><span style="mso-bookmark:OLE_LINK2"></span>
<p class="MsoNormal"> <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="0" 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.
<br>
<br>
</span><o:p></o:p></p>
</div>
</body>
</html>