<div dir="ltr">Thanks, Anne and Kurt, for reviving this thread.<br><br>I'd love to see a reference to "consideration of the public interest where relevant" mentioned in the PDP Charter Template, and wonder if Councilors might offer some input along this line.<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><br><font color="#000000">Kind regards,</font><br><font color="#000000">Justine</font><br><b><br></b></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 8 Mar 2023 at 09:39, Anne ICANN via council <<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I agree with Kurt and had made changes to the WG Charter template that addressed this very same issue.   Marika has those changes and acknowledged them in the SPS meeting in LA, indicating they would be made since no one on Council had objected.<div><br></div><div>Will staff please refer to the comments I made on the language in the proposed Charter template in order to modify this PDP language along the lines that Kurt has suggested?  That language included an obligation on the part of staff to raise issues both at the Charter stage and ongoing for  the  GDS staff liaison to raise those issues that may become apparent during the WG deliberations.  </div><div><br></div><div>An "umbrella" principle here is that staff should be better versed on existing ICANN policies than any volunteer Working Group Chair or member.  In addition, staff is compensated to perform this work whereas volunteers are not.  Agree with Kurt this shifts way too much responsibility to WG members.</div><div><br></div><div>Thank you,</div><div>Anne</div><div><br clear="all"><div><div dir="ltr"><div dir="ltr"><div>Anne Aikman-Scalese</div>GNSO Councilor<div>NomCom Non-Voting 2022-2024</div><div><a href="mailto:anneicanngnso@gmail.com" target="_blank">anneicanngnso@gmail.com</a></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Mar 7, 2023 at 11:19 PM kurt <a href="http://kjpritz.com" target="_blank">kjpritz.com</a> via council <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">



<div>
Hi All: 
<div><br>
</div>
<div>With regard to the recommended change to the PDP Charter template: </div>
<div><br>
</div>
<blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px">
<div>2.5 Impact on Existing Consensus Policies</div>
<div>If the WG concludes with any recommendations, the WG must consider any potential impact of these recommendations on existing consensus policies. If an impact is identified, the WG is expected to be explicit in this section about which consensus
 policies are impacted and how this impact is expected to be addressed, to facilitate the subsequent implementation process.</div>
</blockquote>
<div><br>
</div>
<div>I am not for the wording and (I think) the intended spirit of this amendment: </div>
<div>
<ul>
<li>It could markedly increase the time and complexity of PDPs at a time we are trying to streamline them,</li><li>It requires expertise that the PDP team is unlikely to have.</li></ul>
<div><br>
</div>
<div>My personal experience is from the Registration Data EPDP. There, the recommendations recognised that the Transfer Policy was rendered ineffective (it had been rendered ineffective for some time), and raised the question as to whether the Thick
 Whois Policy had been overturned. In the former case, the EPDP team did not have the necessary technical understanding of transfer requirements (and the Transfer Policy PDP is still at it, years later), and in the latter, it is not surprising that the EPDP
 team did not have the political will or consensus to make a call on the Thick Whois Policy. (I know there are nuances to these arguments, but I want to keep this short.)</div>
<div><br>
</div>
<div>If the new section 2.5 means some sort of lighter weight consideration, that is not clear. If it means that an allowable response is, “the PDP recognises this impact and expect the Council to address it," then it should explicitly allow that.
 In this lighter weight case though, I don’t see the value-add, as that already occurs. </div>
<div><br>
</div>
<div>I’d be something along the lines of: </div>
<div><br>
</div>
</div>
<blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px">
<div>
<div>
<div>2.5 Impact on Existing Consensus Policies</div>
</div>
</div>
<div>
<div>
<div>If the WG concludes with any recommendations, the WG must state whether it considered whether there is a potential impact of these recommendations on existing consensus policies. If an impact is identified, the WG should identify the Policies
 affected and whether there is consensus on how the impact is expected to be addressed. </div>
</div>
</div>
<div><br>
</div>
</blockquote>
That way, the Council has a heads-up without imposing additional burdens on the PDP. 
<div><br>
</div>
<div>I understand that some of my comments might be missing the intent of the new requirement. It is intended to start a discussion that might lead to a more specific, constructive outcome. <br>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Kurt <br>
<div>
<div><br>
</div>
<div><br>
<blockquote type="cite">
<div>On 23 Feb 2023, at 2:07 am, Marika Konings via council <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>> wrote:</div>
<br>
<div>
<div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<div style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang="EN-US">Dear All,<u></u><u></u></span></div>
<div style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang="EN-US"><u></u> <u></u></span></div>
<div style="margin:0cm;font-size:4pt;font-family:Helvetica"><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">Please note that an updated version of the PDP Improvements Tracker has been posted on the dedicated
 wiki page (see<a href="https://community.icann.org/x/e4OLD" style="color:rgb(5,99,193);text-decoration:underline" target="_blank">https://community.icann.org/x/e4OLD</a>) to reflect the current status of the different improvements. You’ll note that a couple
 of items have been completed and there is a proposed next step for improvement #3 for Council consideration (“</span><span style="font-size:11pt;font-family:Calibri,sans-serif">Build meeting between ICANN Board and GNSO Council to</span><span style="font-size:11pt;font-family:Calibri,sans-serif"><span> </span></span><span style="font-size:11pt;font-family:Calibri,sans-serif">present
 PDP Final Report into the project plan for ongoing</span><span style="font-size:11pt;font-family:Calibri,sans-serif"><span> </span></span><span style="font-size:11pt;font-family:Calibri,sans-serif">PDPs
 so that a meeting between ICANN Board and Council</span><span style="font-size:11pt;font-family:Calibri,sans-serif"><span> </span></span><span style="font-size:11pt;font-family:Calibri,sans-serif">can
 be scheduled well ahead of time</span><span lang="EN-US" style="font-size:11pt;font-family:Calibri,sans-serif">”)</span><span style="font-size:11pt;font-family:Calibri,sans-serif">.<u></u><u></u></span></div>
<div style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang="EN-US"><u></u> <u></u></span></div>
<div style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang="EN-US">In relation to improvement #5, please find attached the proposed updates to the Initial Report template to address any direct or indirect implications on existing Consensus Policies, in line with the recent updates to the Charter
 Template (see redline on page 10). Please note that although the proposed next step identified the Final Report template as needing to be updated, we’ve realized that there is no Final Report template but it is the Initial Report template that is updated to
 become the Final Report. If you have any comments or concerns about this update, please share this with the Council mailing list by 24 March. If there are no comments / concerns received by that date, we’ll go ahead and post this updated version with the other
 GNSO Work Product templates (see  <a href="https://gnso.icann.org/en/council/procedures" style="color:rgb(5,99,193);text-decoration:underline" target="_blank">https://gnso.icann.org/en/council/procedures</a>).<u></u><u></u></span></div>
<div style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang="EN-US"><u></u> <u></u></span></div>
<div style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang="EN-US">Best regards,<u></u><u></u></span></div>
<div style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang="EN-US"><u></u> <u></u></span></div>
<div style="margin:0cm;font-size:11pt;font-family:Calibri,sans-serif">
<span lang="EN-US">Marika<u></u><u></u></span></div>
</div>
<span id="m_-7277042053877643088m_-8104324527504869169cid:7F051D3DFBD90F4FAADB3318BACD771D@pexch112.icann.org"><Revised PDP WG Initial Report Template - 23 February 2023.docx></span><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">_______________________________________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">council
 mailing list</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<a href="mailto:council@gnso.icann.org" style="color:rgb(5,99,193);text-decoration:underline;font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">council@gnso.icann.org</a><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<a href="https://mm.icann.org/mailman/listinfo/council" style="color:rgb(5,99,193);text-decoration:underline;font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://mm.icann.org/mailman/listinfo/council</a><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">_______________________________________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">By
 submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (</span><a href="https://www.icann.org/privacy/policy" style="color:rgb(5,99,193);text-decoration:underline;font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://www.icann.org/privacy/policy</a><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">)
 and the website Terms of Service (</span><a href="https://www.icann.org/privacy/tos" style="color:rgb(5,99,193);text-decoration:underline;font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank">https://www.icann.org/privacy/tos</a><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">).
 You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</span></div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>

_______________________________________________<br>
council mailing list<br>
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/council" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/council</a><br>
<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" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" 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.</blockquote></div>
_______________________________________________<br>
council mailing list<br>
<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/council" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/council</a><br>
<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" rel="noreferrer" target="_blank">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a href="https://www.icann.org/privacy/tos" rel="noreferrer" 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.</blockquote></div>