<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{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:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Thanks Marika. I’m fine with the change in the template that asks for specific identification of whether or not a Board liaison should be appointed to the WG and whether or not a GDS liaison should be appointed.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regarding the identification of the impact on existing policies, and as previously expressed in our meeting on this specific topic, it is not workable to require the WG to identify all existing consensus policies that will be affected by
its work. In this regard, the draft language referring to “such as” is very problematic.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">These are volunteers and the responsibility for identifying ICANN consensus policies that may be affected by the work of the Working Group should rest with staff initially in the Charter and then on an ongoing basis should rest with the
ICANN Global Domains liaison. The language that has been drafted is far too broad and puts the onus on the WG and its Chairs, who, again, are not being paid to conduct this work and are not the experts on all existing consensus policies.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I believe that when I raised this in our meeting, Kurt Pritz also expressed some concern for the possible implications. The drafting would have to be significantly revised to reflect this concern. Here is the redline for full consideration
by all Councilors, followed by a “purple line” showing my suggested revisions:<o:p></o:p></p>
<p class="MsoNormal">, <span style="color:#C00000">the WG is expected to consider the potential impact of any recommendations it may put forward on existing policies such as [<span style="background:#FFF2CC">TO BE COMPLETED BY CHARTER DRAFTING TEAM: indicate
if specific policies are expected to be impacted – see list of existing consensus policies here
<a href="https://www.icann.org/resources/pages/registrars/consensus-policies-en">
<span style="color:#C00000;text-decoration:none">https://www.icann.org/resources/pages/registrars/consensus-policies-en</span></a>]</span>. If an impact is identified, the WG is expected to be explicit in its recommendations about how this impact is expected
to be addressed, to facilitate the subsequent implementation process. Note that any GDS Liaison to the WG is also tasked to prepare and provide analysis of the impact of policy recommendations on existing policies, as needed.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#C00000"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="color:#C00000">Below are my recommended revisions to the draft text:<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="color:#C00000"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#C00000">the WG is expected to consider the potential impact of any recommendations it may put forward on existing policies
</span><span style="color:#7030A0">that are identified in this Working Group Charter and/or raised during the course of WG deliberations by ICANN Staff or the GDS Liaison</span><span style="color:#C00000"> [<span style="background:#FFF2CC">TO BE COMPLETED BY
CHARTER DRAFTING TEAM: indicate if specific policies are expected to be impacted – see list of existing consensus policies here
<a href="https://www.icann.org/resources/pages/registrars/consensus-policies-en">
<span style="color:#C00000;text-decoration:none">https://www.icann.org/resources/pages/registrars/consensus-policies-en</span></a>]</span>. If an impact is identified, the WG is expected to be explicit in its recommendations about how this impact
</span><span style="color:#7030A0">might</span><span style="color:#C00000"> be addressed
</span><span style="color:#7030A0">by the Council or an IRT</span><span style="color:#C00000">,
</span><span style="color:#7030A0">in order </span><span style="color:#C00000">to facilitate the subsequent implementation process. Note that any GDS Liaison to the WG is also tasked to prepare and provide
</span><span style="color:#7030A0">timely </span><span style="color:#C00000">analysis of the
</span><span style="color:#7030A0">potential </span><span style="color:#C00000">impact of policy recommendations on existing policies, as needed
</span><span style="color:#7030A0">during the course of WG deliberations</span><span style="color:#C00000">.
</span><span style="color:#7030A0">In the event that the GDS liaison or the WG Chairs perceive a need for amendment of the Charter of the Working Group to address specific aspects of existing consensus policy, this concern will be promptly raised with the Council
liaison to the WG for discussion at the Council level.</span><span style="color:#C00000">
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#C00000"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<tbody>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="line-height:105%"><b><span style="font-family:"Trebuchet MS",sans-serif;color:#323232">Anne E. Aikman-Scalese</span></b><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:3.0pt;line-height:105%"><span style="font-family:"Trebuchet MS",sans-serif;color:#323232">Of Counsel</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:3.0pt;line-height:105%"><span style="font-family:"Trebuchet MS",sans-serif;color:#323232"><img border="0" width="17" height="7" style="width:.1736in;height:.0694in" id="Picture_x0020_2" src="cid:image001.png@01D9058A.76DAD960"></span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="line-height:105%"><a href="mailto:AAikman@lewisroca.com" target="_new" title="Email User"><span style="font-size:10.0pt;line-height:105%;font-family:"Trebuchet MS",sans-serif;color:#323232">AAikman@lewisroca.com</span></a><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:.25in;line-height:105%"><span style="font-size:10.0pt;line-height:105%;font-family:"Trebuchet MS",sans-serif;color:#323232">D. 520.629.4428</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt">
<p class="MsoNormal" style="margin-bottom:.25in;line-height:105%"><span style="font-size:10.0pt;line-height:105%;font-family:"Trebuchet MS",sans-serif"><img border="0" width="160" height="22" style="width:1.6666in;height:.2291in" id="Picture_x0020_1" src="cid:image002.png@01D9058A.76DAD960"></span><o:p></o:p></p>
</td>
</tr>
<tr>
<td width="336" valign="top" style="width:3.5in;padding:0in 5.4pt 0in 5.4pt"></td>
</tr>
</tbody>
</table>
</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> council <<a href="mailto:council-bounces@gnso.icann.org">council-bounces@gnso.icann.org</a>>
<b>On Behalf Of </b>Marika Konings via council<br>
<b>Sent:</b> Thursday, December 1, 2022 4:01 AM<br>
<b>To:</b> <a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a><br>
<b>Subject:</b> [council] PDP Improvements #4 and #6 - updated GNSO Charter Template for your review<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",sans-serif;color:black">[EXTERNAL]</span></strong><span style="font-size:9.0pt;font-family:"Helvetica",sans-serif;color:black"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="1" width="100%" align="center">
</div>
</div>
<p class="MsoNormal">Dear All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In line with the proposed next steps for PDP improvements #4 and #6 (see
<a href="https://community.icann.org/x/e4OLD">https://community.icann.org/x/e4OLD</a>), the staff support team has gone ahead and included proposed additions to the GNSO Charter template – see sections II and IV. You can review these in redline format in the
attached document. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">If you have any suggestions or concerns about these proposed additions, please share these with the Council mailing list by 23 December at the latest. Depending on the feedback received, we’ll either plan for further review/discussion or
post the updated version on the GNSO Procedures web-site. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Marika<o:p></o:p></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message
or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying
to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.
<br>
</font>
</body>
</html>