<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Poppins SemiBold";
panose-1:0 0 7 0 0 0 0 0 0 0;}
@font-face
{font-family:"Poppins Light";
panose-1:0 0 4 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Arial",sans-serif;
color:black;
font-weight:normal;
font-style:normal;}
.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;}
--></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-GB" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US">Thanks for circulating this, and thanks to colleagues for the comments so far. I wanted to add a couple:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US">Improvement #3<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US">I agree with Anne that this looks solid and attainable, and I’m not opposing the proposal of effectively trialling this with the IGO Curative
Rights, but I am a little concerned that this may just be another step that builds-in delay. If I understand correctly, the final report on IGO Curative Rights was adopted by Council in June, sent to the Board in July, followed by an invitation meet, but
that as at late October this meeting has not actually taken place or been scheduled, is that correct? Adding in steps which then generate scheduling delays does not seem like an improvement to the process.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US">Improvement #9<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US">Without wishing to overly complicate things, I do think the wider community should be offered some opportunity to provide feedback on the
two ODPs to date. I don’t think this necessarily needs to be a community survey, it could be as simple as a call for input to run alongside the more formal feedback being sought from the liaisons and Council small teams. I am participating in the Prioritization
Framework exercise at present, and the existence of an ODP has a clear impact on that process in terms of what is considered to be eligible to be prioritised (recommendations must have been board-approved). Community feedback from other work efforts which
are affected by the ODP process needs to be captured.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US">Thanks<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US">Susan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Poppins SemiBold";color:black">Susan Payne
<br>
</span><span style="font-size:9.0pt;font-family:"Poppins Light";color:#950734">Head of Legal Policy
</span><span style="font-size:9.0pt;font-family:"Poppins SemiBold";color:black"><br>
Com Laude<br>
</span><b><span style="font-size:9.0pt;font-family:"Poppins Light";color:#950734">T</span></b><span style="font-size:9.0pt;font-family:"Poppins Light";color:black"> +44 (0) 20 7421 8250<br>
</span><b><span style="font-size:9.0pt;font-family:"Poppins Light";color:#950734">Ext</span></b><span style="font-size:9.0pt;font-family:"Poppins Light";color:black"> 255</span><span style="font-size:9.0pt;font-family:"Poppins SemiBold";color:black"><br>
<br>
</span><a href="https://comlaude.com/"><span style="font-size:9.0pt;font-family:"Poppins SemiBold";color:blue;text-decoration:none"><img border="0" width="60" height="82" style="width:.625in;height:.8583in" id="_x0000_i1025" src="cid:image001.png@01D8E95B.297EC820"></span></a><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-US"><o:p></o:p></span></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt">From:</span></b><span lang="EN-US" style="font-size:11.0pt"> council <council-bounces@gnso.icann.org>
<b>On Behalf Of </b>Marika Konings via council<br>
<b>Sent:</b> 25 October 2022 11:10<br>
<b>To:</b> Demetriou, Samantha <sdemetriou@verisign.com>; Ashley Heineman <aheineman@godaddy.com>; Johan Helsingius <julf@Julf.com>; M Cole <MCole@perkinscoie.com>; Lori Schulman <lschulman@inta.org>; wuknoben@gmail.com; Benjamin Akinmoyeje <benakin@gmail.com>;
Raoul Plommer <plommer@gmail.com>; council@gnso.icann.org<br>
<b>Cc:</b> Andrea Glandon <andrea.glandon@icann.org>; Brenda Brewer <brenda.brewer@icann.org><br>
<b>Subject:</b> [council] GNSO Council & SC/G Chairs call: PDP Improvements & Next Steps Standing Committee on SCBO<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><i><span lang="EN-US" style="color:black">Sent on behalf of Sebastien Ducos</span></i><span style="font-size:13.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">****************</span><span style="font-size:13.5pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="color:black">Dear All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Based on the </span>
<a href="https://community.icann.org/download/attachments/206144128/PDP%20Improvements%20-%20Survey%20Report%20-%2016%20September%202022.pdf?version=1&modificationDate=1663427586000&api=v2"><span style="font-size:12.0pt">survey results</span></a><span style="font-size:12.0pt;color:black">
and the subsequent discussion during the ICANN75 session, the Council leadership team is recommending moving forward with the following PDP Improvements as outlined in the table below. Please note that the proposed next steps represent an incremental step
– once this step has been implemented, there will be another opportunity for the GNSO community to consider how to proceed. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">For the upcoming meeting, Council leadership suggests focusing on those next steps that Council or SG/C Chairs do not support so we can focus on those during the meeting and start moving forward
with items that do not raise any concerns. As such, please flag in advance of the meeting which items you would like to discuss further. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">As a reminder, the meeting is scheduled for Wednesday 25 October at 19.00 UTC. The first half of the meeting will be dedicated to the PDP Improvements discussion, the second half will focus on
the next steps concerning the Standing Committee on ICANN Budget and Operations (SCBO).</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">On behalf of Council leadership,</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Sebastien</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse">
<thead>
<tr>
<td valign="top" style="border:solid black 1.0pt;background:#E7E6E6;padding:0cm 5.4pt 0cm 5.4pt">
<p align="center" style="margin:0cm;text-align:center"><b><span style="font-size:12.0pt;color:black">Improvement</span><o:p></o:p></b></p>
</td>
<td valign="top" style="border:solid black 1.0pt;border-left:none;background:#E7E6E6;padding:0cm 5.4pt 0cm 5.4pt">
<p align="center" style="margin:0cm;text-align:center"><b><span style="font-size:12.0pt;color:black">Next Step</span><o:p></o:p></b></p>
</td>
<td valign="top" style="border:solid black 1.0pt;border-left:none;background:#E7E6E6;padding:0cm 5.4pt 0cm 5.4pt">
<p align="center" style="margin:0cm;text-align:center"><b><span style="font-size:12.0pt;color:black">Who is responsible for next step</span><o:p></o:p></b></p>
</td>
</tr>
</thead>
<tbody>
<tr>
<td valign="top" style="border:solid black 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">#1 - Enable a process during the PDP to share relevant information and analysis on potential impacts to existing policies, to support consideration by PDP working groups (define this process as
part of the GDS liaison role)</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Council to review Guidelines for GDS Liaisons to PDPs and determine whether anything further is needed to consider this improvement complete</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">GNSO Council</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign="top" style="border:solid black 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">#2 - The Council should consider sharing with the ICANN Board when certain items are expected to move from Council to Board to facilitate advance planning by the ICANN Board</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Derive from the project list and ADR items expected to be delivered to the ICANN Board in the coming year.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">In combination with sharing its SPS report, the Council communicates to the Board which items are expected to be forwarded to the ICANN Board for its consideration during that year to allow the
ICANN Board to anticipate as part of its planning when it may need to consider GNSO policy recommendations.</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">GNSO Staff Support Team</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<span style="color:black">GNSO Council</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign="top" style="border:solid black 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">#3 - Following adoption of a PDP Final Report by the GNSO Council, schedule a</span><o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">meeting with the ICANN Board to allow the GNSO Council, with the assistance of the PDP Chair(s), to present the Final Report and recommendations to the ICANN Board and allow for Q & A.</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">An invitation has been sent to the ICANN Board to provide a briefing on the IGO Curative Rights EPDP recommendations. Proposed presentation / slides are to be shared in advance of the meeting
with the Board to ensure that it is a neutral representation of the results and does not interfere with independent review. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Following meeting, debrief with Council & GNSO appointed Board members to determine if this was helpful and/or whether it should be continued</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<br>
<span style="color:black">Council & GNSO Appointed Board members</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign="top" style="border:solid black 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">#4 - Add to the charter template a general or</span><o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">specific provision / question regarding consideration of impact on existing</span><o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">consensus policies</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Staff support team to create for Council review proposed addition for charter template that would highlight the expectation that a PDP WG is to consider the impact of its recommendation on existing</span><o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">consensus policies. </span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Review proposed addition (note, the template can always be modified as needed to ensure that it is fit for purpose,</span><o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">including calling out specific existing policies that should be factored in)</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">GNSO Staff Support Team</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<span style="color:black">GNSO Council</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign="top" style="border:solid black 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">#5 - Include in the Final Report template a section to address any direct or indirect implications for existing policies, to support full consideration by the PDP working groups and the GNSO Council.
This may include</span><o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">implementation guidance where appropriate.</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Staff support team to include in the Final Report template a section to address any direct or indirect implications for existing</span><o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Policies. Inclusion of this section by a PDP Team will be linked to any charter requirement in this regard.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Review proposed addition to Final Report template </span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Staff Support Team</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<span style="color:black">GNSO Council </span><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign="top" style="border:solid black 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">#6 - Consider if/how the role of the Board liaison of a PDP can contribute to more</span><o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">effective communication. This could, for example, be done by communicating clearly at the outset of a PDP the expected role of the Board liaison.</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Include link to Board Liaison guidelines in charter template so that if Board liaison is included as part of the charter, the role and expectations can be considered in the context of the review
of the charter</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Review proposed update to charter template</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">GNSO Staff Support Team</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<span style="color:black">GNSO Council</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign="top" style="border:solid black 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">#7 - Update CPIF to note that as part of implementing a new policy, ICANN org and the IRT review updates to other policies and incorporate as part of the implementation plan</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Requests GDS to provide an indication of possible timing & consultation of such updates to the CPIF (note, last round of</span><o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">updates were made in 2018 and involved consultation with the GNSO Council / community – the communication should confirm that the expectation is that the same approach would be used). </span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Council Leadership</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign="top" style="border:solid black 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">#8 - Review of Policy & Implementation Recommendations</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Provide further detail on what a policy status review (PSR) would be expected to cover and confirm that a PSR does not mean that a review is initiated but it allows Council to consider whether
or not a review is appropriate, and what should be considered as part of a review, if initiated.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Review PSR details and decide if/how to proceed.</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">GNSO Staff Support</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<span style="color:black">GNSO Council</span><o:p></o:p></p>
</td>
</tr>
<tr>
<td valign="top" style="border:solid black 1.0pt;border-top:none;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">#9 – Review of the Operational Design Phase</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Develop straightforward survey that can be used to solicit input from the GNSO Council liaison to the SSAD ODP as well as the small team that was tasked to review the ODP to document its findings
so that these can be shared when the review takes place after the second ODP completes.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Review proposed survey.</span><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Notify the Council Liaison to the SubPro ODP that there will be the expectation to provide input on the experience with the ODP so that he can prepare and document his findings accordingly.</span><o:p></o:p></p>
</td>
<td valign="top" style="border-top:none;border-left:none;border-bottom:solid black 1.0pt;border-right:solid black 1.0pt;padding:0cm 5.4pt 0cm 5.4pt;overflow-wrap:break-word;overflow:hidden">
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">GNSO Staff Support Team</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<span style="color:black">GNSO Council</span><o:p></o:p></p>
<p style="margin:0cm"><span style="font-size:12.0pt;color:black">Council Leadership</span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</div>
<hr>
The contents of this email and any attachments are confidential to the intended recipient. They may not be disclosed, used by or copied in any way by anyone other than the intended recipient. If you have received this message in error, please return it to the
sender (deleting the body of the email and attachments in your reply) and immediately and permanently delete it. Please note that Com Laude Group Limited (the “Com Laude Group”) does not accept any responsibility for viruses and it is your responsibility to
scan or otherwise check this email and any attachments. The Com Laude Group does not accept liability for statements which are clearly the sender's own and not made on behalf of the group or one of its member entities. The Com Laude Group is a limited company
registered in England and Wales with company number 10689074 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England. The Com Laude Group includes Nom-IQ Limited t/a Com Laude, a company registered in England and Wales with company number
5047655 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England; Valideus Limited, a company registered in England and Wales with company number 6181291 and registered office at 28-30 Little Russell Street, London, WC1A 2HN England;
Demys Limited, a company registered in Scotland with company number SC197176 and registered office at 15 William Street, South West Lane, Edinburgh, EH3 7LL Scotland; Consonum, Inc. dba Com Laude USA and Valideus USA, a corporation incorporated in the State
of Washington and principal office address at Suite 332, Securities Building, 1904 Third Ave, Seattle, WA 98101; Com Laude (Japan) Corporation, a company registered in Japan with company number 0100-01-190853 and registered office at 1-3-21 Shinkawa, Chuo-ku,
Tokyo, 104-0033, Japan; Com Laude Domain ESP S.L.U., a company registered in Spain and registered office address at Calle Barcas 2, 2, Valencia, 46002, Spain. For further information see
<a href="https://comlaude.com" target="_blank">www.comlaude.com</a>
</body>
</html>