<div dir="ltr">It may be important to refer to a standard for assessing the public interest if this is going to be incorporated into the Charter template. This is because WG members have no personal obligation to act in the public interest and are often acting on behalf of certain interest groups. If the WG is going to be required to deliberate on the public interest, then I think we have to assume we are making that relevant and that a "where relevant" provision may not be appropriate since the Board itself is always expected to act in the public interest. In this regard, I would suggest that if this is to be incorporated per Justine's recommendation, the Charter should make specific reference not only to the ByLaws, but also "in light of ICANN's then-current Global Public Interest Framework as the same may be modified from time to time." I don't know how else the Chairs of a WG will be able to focus the relevant discussion in a productive manner.<div><br></div><div>Anne<br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><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 Mon, Mar 13, 2023 at 4:50 AM Paul McGrady 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 class="msg-6112240692492750977">
<div lang="EN-US" style="overflow-wrap: break-word;">
<div class="m_-6112240692492750977WordSection1">
<p class="MsoNormal">Thanks Justine. Yes, I think clearly tying it to a known ICANN process (with all the explanatory documents that go along with it) will be useful. Otherwise, we could run into a problem of folks saying the public interest inquiry required
is broader than those required in the Bylaws. <u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Best,<u></u><u></u></p>
<p class="MsoNormal">Paul<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> Justine Chew <<a href="mailto:justine.chew.icann@gmail.com" target="_blank">justine.chew.icann@gmail.com</a>> <br>
<b>Sent:</b> Monday, March 13, 2023 2:34 AM<br>
<b>To:</b> Paul McGrady <<a href="mailto:paul@elstermcgrady.com" target="_blank">paul@elstermcgrady.com</a>><br>
<b>Cc:</b> GNSO Council List <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>><br>
<b>Subject:</b> Re: [council] PDP Improvements - status update<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">Hi Paul, <u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks for your input and apologies for my late reply. <br>
<br>
The SubPro ODA said, "<i>ICANN org’s GPI pilot framework mapping results show that more than three-quarters (78%) of the topics reference GPI framework terms and could therefore carry GPI considerations".
</i>Clearly, the ICANN Board's GPIF comes into play during the Board's deliberations of GNSO Policy recommendations, which made me wonder why the PDP Charter Template doesn't make some explicit mention of "public interest considerations, where relevant". It
just seems logical to have it since firstly, it could only aid in the Board's deliberation of GNSO Policy recommendations and secondly, it would put into practice what may otherwise be done merely on an incidental basis.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Perhaps, a reference to something along the lines of "Global Public Interest (GPI) considerations in context of the ICANN Bylaws and where relevant" might be a good start? Do you think we/staff could work on some redline text based on this
basis?<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Regards, <u></u><u></u></p>
<div>
<p class="MsoNormal">Justine<br>
------<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal">On Thu, 9 Mar 2023, 21:33 Paul McGrady, <<a href="mailto:paul@elstermcgrady.com" target="_blank">paul@elstermcgrady.com</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal">Thanks Justine.<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Indefinite terms in charters is a leading cause of PDPs taking forever. I think “consideration of the public interest where relevant" falls into that category. Is there any way
the Council can tighten up the text of the assignment so that a WG knows what to do? Is it merely that public interest needs to be discussed or is it something more?
<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Best,<u></u><u></u></p>
<p class="MsoNormal">Paul<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<div style="border-right:none;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> council <<a href="mailto:council-bounces@gnso.icann.org" target="_blank">council-bounces@gnso.icann.org</a>>
<b>On Behalf Of </b>Justine Chew via council<br>
<b>Sent:</b> Thursday, March 9, 2023 7:36 PM<br>
<b>To:</b> Anne ICANN <<a href="mailto:anneicanngnso@gmail.com" target="_blank">anneicanngnso@gmail.com</a>><br>
<b>Cc:</b> <a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a><br>
<b>Subject:</b> Re: [council] PDP Improvements - status update<u></u><u></u></p>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<p class="MsoNormal">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">
<u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><br>
<span style="color:black">Kind regards,</span><br>
<span style="color:black">Justine</span><u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">On Wed, 8 Mar 2023 at 09:39, Anne ICANN via council <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0in 5pt 4.8pt">
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Thank you,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Anne<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<u></u><u></u></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Anne Aikman-Scalese<u></u><u></u></p>
</div>
<p class="MsoNormal">GNSO Councilor<u></u><u></u></p>
<div>
<p class="MsoNormal">NomCom Non-Voting 2022-2024<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:anneicanngnso@gmail.com" target="_blank">anneicanngnso@gmail.com</a><u></u><u></u></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<div>
<p class="MsoNormal">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:<u></u><u></u></p>
</div>
<blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0in 5pt 4.8pt">
<div>
<p class="MsoNormal">Hi All:
<u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">With regard to the recommended change to the PDP Charter template: <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<blockquote style="margin:5pt 0in 5pt 30pt">
<div>
<p class="MsoNormal">2.5 Impact on Existing Consensus Policies<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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.<u></u><u></u></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">I am not for the wording and (I think) the intended spirit of this amendment: <u></u><u></u></p>
</div>
<div>
<ul type="disc">
<li class="MsoNormal">
It could markedly increase the time and complexity of PDPs at a time we are trying to streamline them,<u></u><u></u></li><li class="MsoNormal">
It requires expertise that the PDP team is unlikely to have.<u></u><u></u></li></ul>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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.)<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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. <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">I’d be something along the lines of: <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<blockquote style="margin:5pt 0in 5pt 30pt">
<div>
<div>
<div>
<p class="MsoNormal">2.5 Impact on Existing Consensus Policies<u></u><u></u></p>
</div>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal">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. <u></u><u></u></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</blockquote>
<p class="MsoNormal">That way, the Council has a heads-up without imposing additional burdens on the PDP.
<u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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. <u></u><u></u></p>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Regards,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Kurt <u></u><u></u></p>
<div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12pt"><u></u> <u></u></p>
<blockquote style="margin-top:5pt;margin-bottom:5pt">
<div>
<p class="MsoNormal">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:<u></u><u></u></p>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
<div>
<div>
<div>
<p class="MsoNormal">Dear All,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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" target="_blank"><span style="color:rgb(5,99,193)">https://community.icann.org/x/e4OLD</span></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 (“Build meeting between ICANN Board and GNSO Council to present
PDP Final Report into the project plan for ongoing PDPs so that a meeting between ICANN Board and Council can be scheduled well ahead of time”).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">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" target="_blank"><span style="color:rgb(5,99,193)">https://gnso.icann.org/en/council/procedures</span></a>).<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Best regards,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Marika<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><Revised PDP WG Initial Report Template - 23 February 2023.docx><span style="font-size:9pt;font-family:Helvetica,sans-serif">_______________________________________________<br>
council mailing list<br>
</span><a href="mailto:council@gnso.icann.org" target="_blank"><span style="font-size:9pt;font-family:Helvetica,sans-serif;color:rgb(5,99,193)">council@gnso.icann.org</span></a><span style="font-size:9pt;font-family:Helvetica,sans-serif"><br>
</span><a href="https://mm.icann.org/mailman/listinfo/council" target="_blank"><span style="font-size:9pt;font-family:Helvetica,sans-serif;color:rgb(5,99,193)">https://mm.icann.org/mailman/listinfo/council</span></a><span style="font-size:9pt;font-family:Helvetica,sans-serif"><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 (</span><a href="https://www.icann.org/privacy/policy" target="_blank"><span style="font-size:9pt;font-family:Helvetica,sans-serif;color:rgb(5,99,193)">https://www.icann.org/privacy/policy</span></a><span style="font-size:9pt;font-family:Helvetica,sans-serif">)
and the website Terms of Service (</span><a href="https://www.icann.org/privacy/tos" target="_blank"><span style="font-size:9pt;font-family:Helvetica,sans-serif;color:rgb(5,99,193)">https://www.icann.org/privacy/tos</span></a><span style="font-size:9pt;font-family:Helvetica,sans-serif">).
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><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<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" 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" 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.<u></u><u></u></p>
</blockquote>
</div>
<p class="MsoNormal">_______________________________________________<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" 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" 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.<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</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.</div></blockquote></div>