<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;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{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:426921263;
mso-list-template-ids:-1581502318;}
@list l1
{mso-list-id:1091925544;
mso-list-type:hybrid;
mso-list-template-ids:345543308 -352413720 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-weight:bold;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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:11.0pt'>Dear GNSO Review Working Group members,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>This Consensus Call below closed on 08 January 2018 and no objections were received. As there were no objections the implementation of Recommendations 5, 9, & 17 2018 is considered agreed by full consensus. See the latest status at: <a href="https://community.icann.org/display/GRWG/Status+of+Draft+Documents+and+Consensus+Calls">https://community.icann.org/display/GRWG/Status+of+Draft+Documents+and+Consensus+Calls</a>.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Julie<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'> <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Julie Hedlund, Policy Director<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='color:black'>From: </span></b><span style='color:black'>Gnso-review-wg <gnso-review-wg-bounces@icann.org> on behalf of Julie Hedlund <julie.hedlund@icann.org><br><b>Date: </b>Tuesday, January 2, 2018 at 9:53 AM<br><b>To: </b>"gnso-review-wg@icann.org" <gnso-review-wg@icann.org><br><b>Subject: </b>[Gnso-review-wg] REMINDER-CONSENSUS CALL: Recommendations 5, 9, & 17 Implementation Charter<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt'>Dear GNSO Review Working Group members,</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>This is a Consensus Call for the GNSO Review Implementation Charter for Recommendations 5, 9, & 17.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>As noted in the attached charter, these are the recommendations for implementation:</span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:11.0pt'>Recommendation 5</span></u><span style='font-size:11.0pt'>: That, during each Working Group self-assessment, new members be asked how their input has been solicited and considered.</span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:11.0pt'>Recommendation 9</span></u><span style='font-size:11.0pt'>: That a formal Working Group leadership assessment program be developed as part of the overall training and development program.</span><o:p></o:p></p><p class=MsoNormal><u><span style='font-size:11.0pt'>Recommendation 17</span></u><span style='font-size:11.0pt'>: That the practice of Working Group self-evaluation be incorporated into the PDP; and that these evaluations should be published and used as a basis for continual process improvement in the PDP. </span><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>The charter reflects the revisions agreed to at the Working Group meeting on 14 December (see notes below).</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>Staff is circulating the revised version of the charter for a three-week Consensus Call to end on <u>Monday, 08 January 2018</u>. If there are no objections the recommendations will be deemed to have been implemented by Full Consensus.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>Best regards,</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>Julie</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>Julie Hedlund, Policy Director</span><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'> </span></b><o:p></o:p></p><p class=MsoNormal><b><span style='font-size:10.5pt'>Action Items/Discussion Notes 14 December</span></b><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'>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:l1 level1 lfo3'><u><span style='font-size:10.5pt'>Implementation Charter for Recommendation 4</span></u><span style='font-size:10.5pt'>: 1) Staff will accept changes and send out final version for consensus call. Normally consensus calls last 2 weeks. Due to the holidays, staff suggests closing the consensus call on 8 January. 2) Staff will send out a reminder on 02 January.</span><o:p></o:p></li><li class=MsoNormal style='margin-left:0in;mso-list:l1 level1 lfo3'><u><span style='font-size:10.5pt'>Implementation Charter for Recommendation 34</span></u><span style='font-size:10.5pt'>: Staff will revise the charter based on the discussion on the call and send it out for review and for discussion on the call on 11 January.</span><o:p></o:p></li><li class=MsoNormal style='margin-left:0in;mso-list:l1 level1 lfo3'><u><span style='font-size:10.5pt'>Implementation Charter for Recommendations 5, 9, and 17</span></u><span style='font-size:10.5pt'>: 1) Staff will accept changes and send the charter out for a consensus call, closing 08 January. 2) Staff will send out a reminder on 02 January.</span><o:p></o:p></li><li class=MsoNormal style='margin-left:0in;mso-list:l1 level1 lfo3'><u><span style='font-size:10.5pt'>2018 Work Plan</span></u><span style='font-size:10.5pt'>: Staff will revise the Work Plan to include updated status as well as notes concerning where recommendations may have budget effects.</span><o:p></o:p></li><li class=MsoNormal style='margin-left:0in;mso-list:l1 level1 lfo3'><u><span style='font-size:10.5pt'>January 2018 Meetings</span></u><span style='font-size:10.5pt'>: The meetings will be rescheduled to occur on 11 and 18 January to avoid conflicts.</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 implementation charter for recommendation 4:</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'>-- Based on discussions during the last meeting, staff has added text to solution stating that the GNSO Council recognizes Working Group members for their contributions via a resolution thanking them for their work. Staff members are exploring other ways that recognition can provided to Working Group members and other community volunteers throughout out the year. These programs may be in place before the 2018 AGM. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- No additional suggestions.</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 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'>-- Recommendation 34 was also discussed during the last meeting and input on the charter was discussed.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Staff added text noting that there is an ongoing assessments by WGs and periodic assessments of attendance by leadership and that each WG is unique and has different member needs and composition. As the assessment is ongoing, staff recommends that this recommendation be considered implemented.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Definition of effectiveness in not included in the text, but this was taken into account in drafting the charter. Staff noted that it may not be appropriate or useful to have a single definition of effectiveness.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- All Working Groups should do what they need to do. But ICANN should look at a holistic level what is happening with these time shifts. Time shifting may not be as robust as intended for a given region. Sometimes there are other barriers to participation, such as language. This may be something that the organization should be tracking and taking into account.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- There are other recommendations that have not yet been discussed that deal with language. That topic will be handled in the future. This recommendation is quite limited. It only discusses the rotation of call start times.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- For WGs staff does an analysis of the composition of the group and the location of members in developing rotation. Attendance records are gathered, posted, and periodically assessed for patterns. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Communications regularly go out to the WG to see if the rotation needs to change. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Does this get to the question about whether there is robust measures in place to address rotation to encourage participation.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- There is a project in the pipeline for centralized onboarding and attendance tracking. This is in the pipeline, but there is not yet formal activity taking place. This tool touches on several recommendations addressed in this review. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Several platforms are currently used for sign-up and SOI completion. Current method for taking attendance is also seperate. With the proposed tool, all three of these elements would be combined and allow for more robust information about participation patterns.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Want to make sure that in any conclusions or reports that we're also noting that it part of a bigger puzzle. Want to make sure that time shifting is not viewed as a silver bullet. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Additional information could be added to this charter: 1) limitations to the way that data are now collected. Once the new tool is available, broader patterns in data can be analyzed. 2) Participation is not just an issue of time zones, other lifestyle factors and commitments also factor into a person's ability to participate.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Staff will revise the charter. If changes are acceptable, this charter will go out for a consensus call after the next 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'>Chat excerpts:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Krishna Seeburn - Kris: i'd like to propose that we keep track of a matrix to see effectiveness but it has been workable.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Berry Cobb: I'd also note that it is very challenging to get to the data to perform this analysis at a more broad level in that locations of WG members is not connected to attendance records. A centralized WG onboarding and attendance tool would help centralize this data for a more robust analysis on how community members participate.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>Sara Bockey: Definitely want to look at location but I would also suggest lifestyle/commitments would come into play. You may be in APAC but not able to attend during working hours or late evenings due to family matters. </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 implementation charter for recommendations 5, 9, and 17:</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'>-- Staff suggested several changes based on feedback from the last call. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Additional text focuses on confidentiality and clarifies that while the survey requires that respondents provide their name, the survey includes clear guidance about confidentiality and the treatment of personal information. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- The WG Self-Assessment Survey is also included as an attachment to the charter. </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. 2018 Work Plan:</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'>-- Review of Work Plan. Recommendations 26-29 are on hold. These related to SOIs and membership in SG/Cs. GDPR is likely to impact data gathering as part of these recommendations, these charters are on hold pending new information about ICANN's approach to responding to GDPR. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Recommendation 22 charter will be ready for the next call. Staff is looking into the current programs that are available to community members for training and development, such as ICANN Academy and ICANN Learn, as well as other tools and opportunities. Staff is analyzing which resources may be considered part of a competency-based framework.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Recommendations 1, 2, 3: Staff is analyzing current outreach activities to see how they address recommendations and looking at existing metrics that might be able to provide insight into effectiveness. Staff will try to have this analysis ready for the next call.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Recommendation 7 and 12 (recommendations addressing language and participation): Staff is gathering data on efforts underway, such as ALAC initiative on real-time transcription.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Recommendations 20 and 21: Staff has begun analysis of these recommendations to see if there are already efforts underway to review ICANN Strategic Objectives and analysis of New gLTDs. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Recommendations 6, 33, 35, and 36 related to diversity and are on hold because the CCWG-Accountability Work Stream 2 Sub-Team on Diversity will soon provide final recommendations, which can be analyzed against the GNSO Review recommendations. A public comment period is currently open. Once the public comment closes in early January, staff can begin analysis. The goal is for the final recommendations to be available by ICANN61, but it may take longer in updates are needed to the operating procedures.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Staff is projecting completion of all charters by June 2018.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- Do we have any idea whether there are some recommendations that will impact or be impacted by budget requirements for the future?</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- This would be useful to incorporate into the Work Plan where budget might be an issue. Recommendation 7 and 12 might have budget impacts, and in particular Recommendation 12. Real-time transcription could be quite expensive. Staff is aware that there are already real-time transcription services provided in specific circumstances, for example at certain types of meetings with broad attendance. ALAC is also experimenting with real-time transcription. Staff will collect information about the costs of these services and will attempt to project possible costs for expanding these services. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'>-- We would be looking at whether funds would need to be requested for FY19. That process will begin soon. We will consider this charter in January, which will allow any results to be considered in planning for FY19. </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'>6. January Meeting Schedule:</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'>-- Next meeting is currently scheduled for 4 January. Suggestion to hold meetings on 11 and 18 January instead. No opposition expressed. Following the meeting on the 18th, the schedule will begin meeting every other week again. </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.5pt'> </span><o:p></o:p></p></div></body></html>