<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Title content=""><meta name=Keywords content=""><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle19
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Calibri;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle26
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle29
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle30
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle32
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle33
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle34
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle35
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle36
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle37
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle38
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle39
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle40
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle41
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle42
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle43
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle44
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle45
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle46
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle47
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle48
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle49
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle50
{mso-style-type:personal;
font-family:Calibri;
color:windowtext;}
span.EmailStyle51
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:1417092502;
mso-list-type:hybrid;
mso-list-template-ids:-957862642 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1
{mso-list-id:1946618421;
mso-list-template-ids:1744603976;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>Dear GNSO Review Working Group members,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>Please see below the notes and action items from the meeting on 30 March. Per the action items revised charters are attached with redlines to show changes from the previous versions. These have been loaded into the Adobe Connect room for discussion during tomorrow’s call: Thursday, 13 April at 1200 UTC. Please also see the draft agenda for tomorrow’s call as follows:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> <o:p></o:p></span></p><ol style='margin-top:0in' start=1 type=1><li class=MsoNormal style='mso-list:l1 level1 lfo3'><span style='font-size:11.0pt;font-family:Calibri'>Review agenda <o:p></o:p></span></li><li class=MsoNormal style='mso-list:l1 level1 lfo3'><span style='font-size:11.0pt;font-family:Calibri'>SOIs <o:p></o:p></span></li><li class=MsoNormal style='mso-list:l1 level1 lfo3'><span style='font-size:11.0pt;font-family:Calibri'>Flow chart of work<o:p></o:p></span></li><li class=MsoNormal style='mso-list:l1 level1 lfo3'><span style='font-size:11.0pt;font-family:Calibri'>Review revised draft charters based on actions at 30 March meeting<o:p></o:p></span></li><li class=MsoNormal style='mso-list:l1 level1 lfo3'><span style='font-size:11.0pt;font-family:Calibri'>Meeting Schedule: Next meeting 27 April<o:p></o:p></span></li><li class=MsoNormal style='mso-list:l1 level1 lfo3'><span style='font-size:11.0pt;font-family:Calibri'>AOB<o:p></o:p></span></li></ol><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>Julie<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>Julie Hedlund, Policy Director<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Action Items/Discussion Notes 30 March</span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Action Items:</span></b><o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>1.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><span style='font-size:10.5pt;font-family:Calibri'>Staff will send a Doodle Poll to confirm the timing of the next call that will be in two weeks on Thursday, 13 April.</span><o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>2.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><span style='font-size:10.5pt;font-family:Calibri'>Recommendation 8: Include in the solution section a link to the IRT Principles. Amend the KPIs that it is up to the future establishment of the WG to make them aware of the IRT requirements and principles.</span><o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>3.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><span style='font-size:10.5pt;font-family:Calibri'>Recommendations 14 & 15: Combine recommendations 14 and 15 on timing and phasing and suggest possible language.</span><o:p></o:p></p><p class=MsoListParagraph style='text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='mso-list:Ignore'>4.<span style='font:7.0pt "Times New Roman"'> </span></span><![endif]><span style='font-size:10.5pt;font-family:Calibri'>Recommendations 16 & 18: Staff will provide context and background for Recommendation 18 and circulate them on the list.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt;font-family:Calibri'>Discussion Notes:</span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:10.5pt;font-family:Calibri'>Review revised draft charters based on actions from ICANN 58:</span></u><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><i><span style='font-size:10.5pt;font-family:Calibri'>Recommendation 8:</span></i><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Staff perspective that implementation of GNSO Policy and Implementation WG recommendations addresses this recommendation from the GNSO Review.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- General comment on recommendation charters regarding KPIs: Not clear what appropriate KPIs would be, if implementation measures are not measurable (example: if implementation involves changes in language to GNSO PDP Manual or GNSO WG Guidelines)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- There was the requirement that the WG members should join the IRT. Question: How is that incorporated in the solution? Should we be more precise under #2?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- KPIs: Up to the future establishment of the WG to make them aware and that could be enough.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>From the chat:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Marika Konings: The IRT Principles address composition so maybe it is worth referring to those as well? This is what the IRT Principles say: "The call for IRT volunteers should at a minimum be sent to all members of thePDP working group that was responsible for developing the policy recommendations. The call for volunteers may need to reach beyond the working group members to ensure broad participation by parties directly impacted by the implementation and parties with specialized expertise needed for implementation. In some cases, additional outreach at the start or at a later stageof the IRT may be necessary to ensure that appropriate expertise is available and that directly affected parties are involved in the IRT."</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><i><span style='font-size:10.5pt;font-family:Calibri'>Recommendation 15:</span></i><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Makes sense to include it as part of the assessment process.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- How to cycle that into future PDPs?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Every PDP is ideosyncratic. Do we want to continue to have completely open PDPs? Do we want size limitations?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Phasing could be a way to mitigate size. Smaller groups addressing work simultaneously.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- A plenary might be a good way to go.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>From the chat:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Marika Konings: Could that be part of the WG assessment? Ask a question on if/how the PDP could have moved faster? And then those ideas could be shared / discussed? @Julie - I think it is a link. The GOP refer to it, but do not dictate the questions as far as I am aware.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Amr Elsadr: One previous measure taken during a staff exercise for improving PDPs was including PDP WG charters in preliminary issues reports. This was meant to save time used to form charter drafting teams, draft the charters, submitting for public comments and having Council adopt them. This is now included in the process to accept issues report..</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Lori Schulman: Does broad participation necessarily mean high numbers vs. having many interests represented? Each PDP could be sized according to needs. I think that idea of phasing.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Marika Konings: good point Lori - I guess the question is though how and who do you assess whether different interests are represented? would it be feasible to have each SG/C to appoint 3-4 reps representing those different interests? </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Amr Elsadr: @Lori: Public comment periods is one way to participate? Also during early PDP WG outreach to SOs/ACs?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Marika Konings: there may also be other models - it may be worth exploring similar organizations to see how they conduct similar activities?</span><o:p></o:p></p><p class=MsoNormal style='text-indent:.5in'><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><i><span style='font-size:10.5pt;font-family:Calibri'>Recommendations 16 & 18:</span></i><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>-- Question: Recommendation 18 points to policy effectiveness -- could have a wider frame than the PIA. That the goals of the policy process have been achieved? Or could the policy process be improved?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>From the chat:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Amr Elsadr: Does the WG also wish to address the distinction between periodic vs. ongoing post-implementation policy effectiveness evaluation? Implementation of ongoing evaluations also need to be considered.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Wolf-Ulrich Knoben: Has "effectiveness" been defined in more detail in the report?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'>Amr Elsadr: @WUK: I don't believe it has. This would be dependent on how the DMPM recs are implemented?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:Calibri'> </span><o:p></o:p></p></div></body></html>