<html 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 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:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
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:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
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:139615145;
mso-list-type:hybrid;
mso-list-template-ids:2054967854 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:1087535471;
mso-list-template-ids:-1103712432;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body bgcolor=white lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:10.5pt'>Dear GNSO Review Working Group members,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>This is a Consensus Call for the GNSO Review Implementation Charter for Recommendation 34.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>As noted in the attached charter, this is the recommendation for implementation: “That PDP Working Groups rotate the start time of their meetings in order not to disadvantage people who wish to participate from anywhere in the world.”<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>The charter reflects the revisions agreed to at the Working Group meeting on 18 January (see notes below).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>Staff is circulating the revised version of the charter for a three-week Consensus Call to end on <u>Thursday, 08 February 2018</u>. If there are no objections the recommendation will be deemed to have been implemented by Full Consensus.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>Julie<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'>Julie Hedlund, Policy Director<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt'> </span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Notes & Action Items GNSO Review Working Group Meeting on Thursday, 18 January 2018 at 13:00 UTC </span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Action Items: </span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt'> </span></b><o:p></o:p></p><ol style='margin-top:0in' start=1 type=1><li class=MsoNormal style='margin-left:0in;mso-list:l0 level1 lfo3'><u><span style='font-size:10.5pt'>Discussion of the revised implementation charter for recommendation 34</span></u><span style='font-size:10.5pt'>: Staff will send the implementation charter out for 3-week consensus call. Consensus calls are typically two weeks, but the deadline will be extended due to community meetings taking place the week of 29 January.</span><o:p></o:p></li><li class=MsoNormal style='margin-left:0in;mso-list:l0 level1 lfo3'><u><span style='font-size:10.5pt'>Discussion of the revised implementation charter for recommendation 22</span></u><span style='font-size:10.5pt'>: Staff will clarify in the charter text the connection between the recommendation and the implementation of that framework through the existing training. This revision will be sent out by one week before the 8 February meeting, giving members time to review the text in advance of the meeting. The WG will aim to finalize this charter on the next call.</span><o:p></o:p></li><li class=MsoNormal style='margin-left:0in;mso-list:l0 level1 lfo3'><u><span style='font-size:10.5pt'>Discussion of the implementation charter for recommendations 1, 2, & 3</span></u><span style='font-size:10.5pt'>: 1) Staff will correct title on this charter document and change it to "GNSO Outreach and Working Group Participation." 2) Staff will research Stakeholder Group and Constituency (SG/C) activities related to outreach, evaluation mechanisms and metrics these existing programs have in place, the Stakeholder Journey project, and evaluation underway on the Fellowship program. Staff may also consider adding text linking the outreach taking place at the SG/C level with participation in Working Groups and other initiatives within the GNSO. 4) Staff will add suggestions for methods to gather additional metrics, and points to aid discussion on the sufficiency of current programs, as well as how to address cost barriers. Staff will circulate edits one week in advance of the 8 February meeting to give members time to review before the meeting. </span><o:p></o:p></li></ol><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Notes:</span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>1. Review agenda/SOIs: No updates.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>2. Discussion of the revised implementation charter for recommendation 34:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Text added to final paragraph before Working Group Determination clarifying that there is no mandate or rule regarding meeting rotation, and the decision about whether to rotate is left to the Working Group. The Working Group Determination also includes new text clarifying that the Working Group does not believe that it is necessary to create a mandate or rule regarding meeting rotation.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Issue raised - underwhelming participation in the discussion about the charters. Do members need to make further efforts to engage the community in discussion about these charters? Maybe by extending the deadline, we can socialize the revisions more extensively. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Response: A lot of this material has already been vetted and we are currently in the implementation phase. This may be why we are not getting a lot of feedback at this point. It does not hurt to socialize further, but some community members may feel that additional vetting is not necessary.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Time has passed since the recommendations came out. A number of process improvements have already taken place since the Review came out. We want to give the community time to review our work, but we have a small dedicated core of volunteers who are actively engaged. Perhaps it makes sense to move more quickly with this smaller group given this background.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>3. Discussion of the revised implementation charter for recommendation 22:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- New content: Background was added clarifying the term "competency-based framework" drawing on explanations from the assessment report of the GNSO Review Working Party and the Final Report of the Independent Examiner. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Question: This background means that there are two parts of skills to be developed - 1. procedural skills (PDP process, manual); 2. technical knowledge related to the specific work that the particular group is doing (as opposed to general technical knowledge). Is the additional text regarding general technical training responding to the element regarding technical training?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Staff response: The intent of the technical modules discussed in the text is to provide information to the GNSO community regarding DNS infrastructure. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>From the chat: </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Lori Schulman: yes, I was confused too. Technical training could also means using ICANN's technology to enable the work.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Sara Bockey: Could technical training also be for staff - to have a better understanding of Ry / Rr techincal issues</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- ICANN Learn contains training materials on ICANN's technology to enable the work.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Staff receives training to have a better understanding of Ry/Rr technical issues</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Thinking about how this is going to be implemented - we have been asked to provide a framework. What does this mean? It is simply a list of resources or is it a broader framework? Looking at the list of technical materials listed in the charter, are we implying that we should be providing training on the items listed in the charter?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- If we decide that framework means a conceptual way of approaching the problem, how do we go about doing that? Would it be a curriculum? Is this group in a position to develop such a framework?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- We could develop a list of topics that would be useful to cover in general and/or for specific working teams. We could share this with the Council to consider and implement as needed on a case-by-case basis.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- There is a lot of material available, but there may be a lack of a conceptual frame or a clear path for an individual to develop the knowledge they need to be successful in a role, such as on the Council or in a Working Group. Perhaps it would be helpful to have a clearer connection between the training that is available and the needs for specific roles. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>From the chat: </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Sara Bockey: I think ICANN topics are complex and the history related to issues too deep to really be effectively addressed in brief classes. Perhaps something that does a deeper dive over a longer period of time, like a semester say, would be helpful. I've done a good bit of this training with varying degrees of feeling like I took something away from it</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- If we leave the charter as it is, we should be clear what is going to happen with this. The items on the list are already institutionalized. Is the connection between a request for some training and the implementation that is already done included in the charter? If so, our work on this charter may be done.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Perhaps what is missing is a clearer connection to the implementation of the recommendations. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>4. Discussion of the implementation charter for recommendations 1, 2, & 3:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- This charter does not appear to be one that is already implemented. It appears that there would be additional steps to take if the WG agrees to follow the recommended approach to the charter. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- The first recommendation is on the development and monitoring of metrics. Staff found a number of programs related to this recommendation, but it is not clear that there is a set of metrics that the GNSO is using to evaluate these programs. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- For recommendation 2, the group may determine that existing programs are sufficient. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- For recommendation 3, staff is working with Language Services to determine costs associated with recommendations 7 and 12. This might be a way to reduce/remove cost barriers to participation. Staff may be able to identify existing measures to reduce cost barriers, such as free or low-cost telecommunication services. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Staff will circulate edits one week in advance of the 8 February meeting to give members time to review before the meeting. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>From the chat: </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Marika Konings: the WG may need to define what current cost barriers are as policy development is largely done through online means (which do cost time and effort, but no other costs as there are usually free dial in numbers or otherwise dial outs provided)</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- In the solution section, Current Outreach Strategies and Pilot Programs are listed. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Marika Konings: Challenge is that many of these programs do not have a specific GNSO focus or criteria. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Marika Konings: what may be missing from the list is SG/C specific outreach programs?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Marika Konings: I guess that would fall under other activities?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Marika Konings: but it may be worth getting more details on those as these are presumbably specifically focused on GNSO</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Lori Schulman: I like the idea of outreach. Agree with Marika.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Sara Bockey: I've never heard of the stakeholder journey project. Is there a link to that?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Pascal Bekono: Good point Marika </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Marika Konings: I believe there are also discussions on conducting a community wide review of the fellowship program</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Items to be discussed in the solutions section: Metrics to develop and monitor to evaluate ongoing effectiveness of current outreach strategies and pilot programs; Whether to develop and fund more targeted programs, beyond those already offered; How to best reduce or remove cost barriers to volunteer participation on WGs and policy development.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- In addition to gathering information about metrics for evaluating individual programs, it may be helpful to discuss if it would be helpful to have a more holistic evaluation of the effectiveness of these programs.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Outreach appears to be done on the SG/C level within the GNSO. Each has a distinct target audience. Perhaps this could be summarized in the charter text. Remaining question - how do we evaluate success? It might be helpful to provide context about the relationship between outreach at the SG/C level and participation in Working Groups. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Question - what does the Working Group think would be helpful to use in terms of metrics? </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>From the chat: </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Sara Bockey: I'm not sure re metrics. what exactly are the metrics looking at?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Pascal Bekono: Metrics can be done through a survey ?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- The group will gather some additional information and then circle back to discuss further. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- For recommendation 2, the group may determine that existing programs are sufficient.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- For recommendation 3, staff is working with Language Services to determine costs associated with recommendations 7 and 12. This might be a way to reduce/remove cost barriers to participation. Staff may be able to identify existing measures to reduce cost barriers, such as free or low cost telecommunication services.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>5. Next Meeting: 08 February 1300 UTC.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p></div></body></html>