- Gnso-review-wg - lists.icann.org

REMINDER FOR REVIEW: Final Draft Implementation Charter for GNSO Review Recommendations 20 & 21
by Julie Hedlund May 3, 2018

May 3, 2018

Dear GNSO Review Working Group members, This is a reminder to review the attached materials per the message below. Best regards, Julie Julie Hedlund, Policy Director From: Gnso-review-wg <gnso-review-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, April 26, 2018 at 2:02 PM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: [Gnso-review-wg] FOR REVIEW: Final Draft Implementation Charter for GNSO Review Recommendations 20 & 21 Dear GNSO Review Working Group members, Per the action items and notes below from the call on 26 April, please review the attached final draft GNSO Review Implementation Charter for Recommendations 20 & 21 in Word and PDF. As noted in the attached charter, these are the recommendations for implementation: Recommendation 20: That the GNSO Council should review annually ICANN’s Strategic Objectives with a view to planning future policy development that strikes a balance between ICANN’s Strategic Objectives and the GNSO resources available for policy development.  Recommendation 21: That the GNSO Council should regularly undertake or commission analysis of trends in gTLDs in order to forecast likely requirements for policy and to ensure those affected are well- represented in the policy-making process. Working Group members are requested to respond to this review in two weeks, by COB Wednesday, 09 May. If no comments are received during the review period staff will accept the changes and circulate the final version of the charter for a two-week Consensus Call. Best regards, Julie Julie Hedlund, Policy Director Action Items and Notes GNSO Review Working Group Meeting on Thursday, 26 April 2018 at 13:00 UTC Action Items: Action Item 1: implementation charter for recommendations 7 & 12: Staff will correct typos identified by Wolf-Ulrich (see meeting notes for details). Action Item 2: revised implementation charter for recommendations 1, 2, & 3: Staff will circulate the revised text of this implementation charter on the mailing list. Any feedback raised on the mailing list will be discussed on the next call. Action Item 3: implementation charter for recommendations 20 and 21: Staff will circulate the text of this implementation charter on the mailing list. Any feedback raised on the mailing list will be discussed on the next call. Action Item 4: GNSO Council Update: Staff will circulate to the WG early next week draft slides for the GNSO Council presentation in May. Notes: 1. Review agenda/SOIs: -- This is a smaller group today. The call will proceed but no decisions will be made. -- No updates to SOIs. 2. Status of Consensus Call for revised implementation charter for recommendations 7 & 12 (closing 26 April): -- The consensus call closes today. There have been no comments or objections so far. If this continues to be the cases, the charter will be deemed to be accepted by full consensus. -- Wolf-Ulrich identified small typos to correct (headline says “1,2,3” and should say “7&12.” Number 3 “Translation of Documents” under “Solutions” – typos in first and second lines: “translatin” should be “translating” and “transition” should be “translation.” 3. Discussion of the revised implementation charter for recommendations 1, 2, & 3: -- Staff has completed changes suggested on the call two weeks ago (see redlined text). -- Staff suggests putting this text out for review by the group before completing a consensus call on this implementation charter. The WG can discuss any proposed changes raised on the mailing list during the call next week. 4. Continued discussion of the implementation charter for recommendations 20 and 21: -- Recommendation 20: The scope of the Standing Committee on ICANN’s Budget and Operations could be the structure through which the GNSO provides feedback on the strategic plan. This would complement existing activities associated with analyzing the budget. -- In the last WG meeting, it was suggested that the WG would update the Council during the May Council Meeting. This proposal to expand the SCBO charter could be raised. The status of recommendations related to GDPR and Diversity (especially CCWG-Accountability recommendations on Diversity) could also be included in this discussion. -- Recommendation 21: There are a number of initiatives underway to collect data. This section outlines the existing data sources and describes how the GNSO Council and Working Groups already access this data. It is not anticipated that an additional formal mechanism is needed for the GNSO to receive information about the efforts. -- Staff suggests circulating this charter for additional feedback by the WG. -- Regarding Recommendation 20: Rafik made a comment during the last meeting asking whether the SCBO is the right place to complete this review. Wolf-Ulrich is fine with the proposed approach, but would like to give everyone an opportunity to review and provide input. -- An alternative would be for the Council to take on this review itself and possibly create an additional Standing Committee. This can be part of the discussion with the GNSO Council on the May GNSO Council call. 5. Discussion of the April Work Plan and proposed update to the GNSO Council on 24 May: -- An additional item to discuss with the GNSO Council – any items with budget implications will need to be considered by the GNSO Council. -- Staff has begun reviewing the CCWG-Accountability recommendations and cross referencing them with GNSO Review recommendations 6, 33, 35, and 36. Staff will provide this analysis to the WG for the next WG meeting. -- The Board has not yet made a decision on the CCWG-Accountability recommendations. This must be taken into consideration in drafting implementation charters that reference CCWG-Accountability recommendations. If WG implementation charters are tied to implementation of CCWG-Accountability recommendations, the implementation will not be complete until Board approval. -- It is also possible that the WG can make recommendations that are complementary to, but not dependent on, the CCWG-Accountability recommendations. -- Chat from Marika Konings to All Participants: whether implementation is achieved for those recommendations may only be possible further in the future as Board consideration is still some time out? -- Staff will gather more information about implementation of steps by the ICANN Organization to address GDPR. Once additional information is available on the details of these measures, staff will update the appropriate implementation charters (26-29). -- Motions will potentially be needed for the GNSO Council to consider in the June meeting. 6. Next Meeting: 10 May 1300 UTC: -- In the next meeting, the WG should finalize the material it would like to present to Council. -- Staff will provide a draft update to the Council early next week for the WG to consider. The WG can review the slides and suggest changes in time for the document deadline for the May Council meeting. 7. AOB: None.

1 0

CLOSED-CONSENSUS CALL: Recommendations 7 & 12 Implementation Charter
by Julie Hedlund April 27, 2018

April 27, 2018

Dear GNSO Review Working Group members, This Consensus Call below closed on 26 April 2018 and no objections were received. As there were no objections the implementation of Recommendations 7 & 12 are considered agreed by full consensus. See the latest status at: https://community.icann.org/display/GRWG/Status+of+Draft+Documents+and+Cons…. Best regards, Julie Julie Hedlund, Policy Director From: Gnso-review-wg <gnso-review-wg-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Tuesday, April 24, 2018 at 5:05 PM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: [Gnso-review-wg] REMINDER-CONSENSUS CALL: Recommendations 7 & 12 Implementation Charter Dear GNSO Review Working Group members, REMINDER: This is a Consensus Call for the GNSO Review Implementation Charter for Recommendations 7 & 12, per the action items from the meeting on 12 April. The redlines in the Working Group Determination section of the document reflect the agreed-upon changes during the meeting. As noted in the attached charter, these are the recommendations for implementation: Recommendation 7: That Stakeholder Groups and Constituencies engage more deeply with community members whose first language is other than English, as a means to overcoming language barriers. Recommendation 12: That ICANN assess the feasibility of providing a real-time transcription service in audio conferences for Working Group meetings. Staff is circulating the revised version of the charter for a two-week Consensus Call to end on Thursday, 26 April 2018. If there are no objections the recommendation will be deemed to have been implemented by Full Consensus. Best regards, Julie Julie Hedlund, Policy Director

1 0

Revised GNSO Review Implementation Work Plan
by Julie Hedlund April 26, 2018

April 26, 2018

Dear GNSO Review Working Group members, Per the discussion on today’s call, 26 April, please see the attached revised Work Plan. This document also is posted to the wiki at: https://community.icann.org/display/GRWG/Status+of+Draft+Documents+and+Cons…. In this revision staff has provided more detailed agendas for the 10 and 24 May meetings, including the item for the WG members to review the slides for the update to the GNSO Council at its meeting on 24 May. Staff will provide a draft of slides for the WG to begin its review next week, followed by the discussion during the call on 10 May. Best regards, Julie Julie Hedlund, Policy Director

1 0

FOR REVIEW: Final Draft Implementation Charter for GNSO Review Recommendations 20 & 21
by Julie Hedlund April 26, 2018

April 26, 2018

Dear GNSO Review Working Group members, Per the action items and notes below from the call on 26 April, please review the attached final draft GNSO Review Implementation Charter for Recommendations 20 & 21 in Word and PDF. As noted in the attached charter, these are the recommendations for implementation: Recommendation 20: That the GNSO Council should review annually ICANN’s Strategic Objectives with a view to planning future policy development that strikes a balance between ICANN’s Strategic Objectives and the GNSO resources available for policy development.  Recommendation 21: That the GNSO Council should regularly undertake or commission analysis of trends in gTLDs in order to forecast likely requirements for policy and to ensure those affected are well- represented in the policy-making process. Working Group members are requested to respond to this review in two weeks, by COB Wednesday, 09 May. If no comments are received during the review period staff will accept the changes and circulate the final version of the charter for a two-week Consensus Call. Best regards, Julie Julie Hedlund, Policy Director Action Items and Notes GNSO Review Working Group Meeting on Thursday, 26 April 2018 at 13:00 UTC Action Items: Action Item 1: implementation charter for recommendations 7 & 12: Staff will correct typos identified by Wolf-Ulrich (see meeting notes for details). Action Item 2: revised implementation charter for recommendations 1, 2, & 3: Staff will circulate the revised text of this implementation charter on the mailing list. Any feedback raised on the mailing list will be discussed on the next call. Action Item 3: implementation charter for recommendations 20 and 21: Staff will circulate the text of this implementation charter on the mailing list. Any feedback raised on the mailing list will be discussed on the next call. Action Item 4: GNSO Council Update: Staff will circulate to the WG early next week draft slides for the GNSO Council presentation in May. Notes: 1. Review agenda/SOIs: -- This is a smaller group today. The call will proceed but no decisions will be made. -- No updates to SOIs. 2. Status of Consensus Call for revised implementation charter for recommendations 7 & 12 (closing 26 April): -- The consensus call closes today. There have been no comments or objections so far. If this continues to be the cases, the charter will be deemed to be accepted by full consensus. -- Wolf-Ulrich identified small typos to correct (headline says “1,2,3” and should say “7&12.” Number 3 “Translation of Documents” under “Solutions” – typos in first and second lines: “translatin” should be “translating” and “transition” should be “translation.” 3. Discussion of the revised implementation charter for recommendations 1, 2, & 3: -- Staff has completed changes suggested on the call two weeks ago (see redlined text). -- Staff suggests putting this text out for review by the group before completing a consensus call on this implementation charter. The WG can discuss any proposed changes raised on the mailing list during the call next week. 4. Continued discussion of the implementation charter for recommendations 20 and 21: -- Recommendation 20: The scope of the Standing Committee on ICANN’s Budget and Operations could be the structure through which the GNSO provides feedback on the strategic plan. This would complement existing activities associated with analyzing the budget. -- In the last WG meeting, it was suggested that the WG would update the Council during the May Council Meeting. This proposal to expand the SCBO charter could be raised. The status of recommendations related to GDPR and Diversity (especially CCWG-Accountability recommendations on Diversity) could also be included in this discussion. -- Recommendation 21: There are a number of initiatives underway to collect data. This section outlines the existing data sources and describes how the GNSO Council and Working Groups already access this data. It is not anticipated that an additional formal mechanism is needed for the GNSO to receive information about the efforts. -- Staff suggests circulating this charter for additional feedback by the WG. -- Regarding Recommendation 20: Rafik made a comment during the last meeting asking whether the SCBO is the right place to complete this review. Wolf-Ulrich is fine with the proposed approach, but would like to give everyone an opportunity to review and provide input. -- An alternative would be for the Council to take on this review itself and possibly create an additional Standing Committee. This can be part of the discussion with the GNSO Council on the May GNSO Council call. 5. Discussion of the April Work Plan and proposed update to the GNSO Council on 24 May: -- An additional item to discuss with the GNSO Council – any items with budget implications will need to be considered by the GNSO Council. -- Staff has begun reviewing the CCWG-Accountability recommendations and cross referencing them with GNSO Review recommendations 6, 33, 35, and 36. Staff will provide this analysis to the WG for the next WG meeting. -- The Board has not yet made a decision on the CCWG-Accountability recommendations. This must be taken into consideration in drafting implementation charters that reference CCWG-Accountability recommendations. If WG implementation charters are tied to implementation of CCWG-Accountability recommendations, the implementation will not be complete until Board approval. -- It is also possible that the WG can make recommendations that are complementary to, but not dependent on, the CCWG-Accountability recommendations. -- Chat from Marika Konings to All Participants: whether implementation is achieved for those recommendations may only be possible further in the future as Board consideration is still some time out? -- Staff will gather more information about implementation of steps by the ICANN Organization to address GDPR. Once additional information is available on the details of these measures, staff will update the appropriate implementation charters (26-29). -- Motions will potentially be needed for the GNSO Council to consider in the June meeting. 6. Next Meeting: 10 May 1300 UTC: -- In the next meeting, the WG should finalize the material it would like to present to Council. -- Staff will provide a draft update to the Council early next week for the WG to consider. The WG can review the slides and suggest changes in time for the document deadline for the May Council meeting. 7. AOB: None.

1 0

FOR REVIEW: Final Draft Implementation Charter for GNSO Review Recommendations 1, 2, & 3
by Julie Hedlund April 26, 2018

April 26, 2018

Dear GNSO Review Working Group members, Per the action items and notes below from the call on 26 April, please review the attached final draft GNSO Review Implementation Charter for Recommendations 1, 2, and 3 in Word and PDF. As noted in the attached charter, these are the recommendations for implementation: Recommendation 1: That the GNSO develop and monitor metrics to evaluate the ongoing effectiveness of current outreach strategies and pilot programs with regard to GNSO Working Groups. Recommendation 2: That the GNSO develop and fund more targeted programs to recruit volunteers and broaden participation in PDP Working Groups, given the vital role volunteers play in Working Groups and policy development. Recommendation 3: That the GNSO Council reduce or remove cost barriers to volunteer participation in Working Groups. Working Group members are requested to respond to this review in two weeks, by COB Wednesday, 09 May. If no comments are received during the review period staff will accept the changes and circulate the final version of the charter for a two-week Consensus Call. Best regards, Julie Julie Hedlund, Policy Director Action Items and Notes GNSO Review Working Group Meeting on Thursday, 26 April 2018 at 13:00 UTC Action Items: Action Item 1: implementation charter for recommendations 7 & 12: Staff will correct typos identified by Wolf-Ulrich (see meeting notes for details). Action Item 2: revised implementation charter for recommendations 1, 2, & 3: Staff will circulate the revised text of this implementation charter on the mailing list. Any feedback raised on the mailing list will be discussed on the next call. Action Item 3: implementation charter for recommendations 20 and 21: Staff will circulate the text of this implementation charter on the mailing list. Any feedback raised on the mailing list will be discussed on the next call. Action Item 4: GNSO Council Update: Staff will circulate to the WG early next week draft slides for the GNSO Council presentation in May. Notes: 1. Review agenda/SOIs: -- This is a smaller group today. The call will proceed but no decisions will be made. -- No updates to SOIs. 2. Status of Consensus Call for revised implementation charter for recommendations 7 & 12 (closing 26 April): -- The consensus call closes today. There have been no comments or objections so far. If this continues to be the cases, the charter will be deemed to be accepted by full consensus. -- Wolf-Ulrich identified small typos to correct (headline says “1,2,3” and should say “7&12.” Number 3 “Translation of Documents” under “Solutions” – typos in first and second lines: “translatin” should be “translating” and “transition” should be “translation.” 3. Discussion of the revised implementation charter for recommendations 1, 2, & 3: -- Staff has completed changes suggested on the call two weeks ago (see redlined text). -- Staff suggests putting this text out for review by the group before completing a consensus call on this implementation charter. The WG can discuss any proposed changes raised on the mailing list during the call next week. 4. Continued discussion of the implementation charter for recommendations 20 and 21: -- Recommendation 20: The scope of the Standing Committee on ICANN’s Budget and Operations could be the structure through which the GNSO provides feedback on the strategic plan. This would complement existing activities associated with analyzing the budget. -- In the last WG meeting, it was suggested that the WG would update the Council during the May Council Meeting. This proposal to expand the SCBO charter could be raised. The status of recommendations related to GDPR and Diversity (especially CCWG-Accountability recommendations on Diversity) could also be included in this discussion. -- Recommendation 21: There are a number of initiatives underway to collect data. This section outlines the existing data sources and describes how the GNSO Council and Working Groups already access this data. It is not anticipated that an additional formal mechanism is needed for the GNSO to receive information about the efforts. -- Staff suggests circulating this charter for additional feedback by the WG. -- Regarding Recommendation 20: Rafik made a comment during the last meeting asking whether the SCBO is the right place to complete this review. Wolf-Ulrich is fine with the proposed approach, but would like to give everyone an opportunity to review and provide input. -- An alternative would be for the Council to take on this review itself and possibly create an additional Standing Committee. This can be part of the discussion with the GNSO Council on the May GNSO Council call. 5. Discussion of the April Work Plan and proposed update to the GNSO Council on 24 May: -- An additional item to discuss with the GNSO Council – any items with budget implications will need to be considered by the GNSO Council. -- Staff has begun reviewing the CCWG-Accountability recommendations and cross referencing them with GNSO Review recommendations 6, 33, 35, and 36. Staff will provide this analysis to the WG for the next WG meeting. -- The Board has not yet made a decision on the CCWG-Accountability recommendations. This must be taken into consideration in drafting implementation charters that reference CCWG-Accountability recommendations. If WG implementation charters are tied to implementation of CCWG-Accountability recommendations, the implementation will not be complete until Board approval. -- It is also possible that the WG can make recommendations that are complementary to, but not dependent on, the CCWG-Accountability recommendations. -- Chat from Marika Konings to All Participants: whether implementation is achieved for those recommendations may only be possible further in the future as Board consideration is still some time out? -- Staff will gather more information about implementation of steps by the ICANN Organization to address GDPR. Once additional information is available on the details of these measures, staff will update the appropriate implementation charters (26-29). -- Motions will potentially be needed for the GNSO Council to consider in the June meeting. 6. Next Meeting: 10 May 1300 UTC: -- In the next meeting, the WG should finalize the material it would like to present to Council. -- Staff will provide a draft update to the Council early next week for the WG to consider. The WG can review the slides and suggest changes in time for the document deadline for the May Council meeting. 7. AOB: None.

1 0

Actions/Discussion Notes for GNSO Review WG Meeting on 26 April 2018
by Julie Hedlund April 26, 2018

April 26, 2018

Dear GNSO Review Working Group members, Please see below and attached the action items and discussion notes captured by staff from the meeting on 26 April 2018. These high-level notes are designed to help WG members navigate through the content of the call and are not meant to be a substitute for the recording or transcript, which are posted on the wiki at: https://community.icann.org/display/GRWG/2018. Please note that the next meeting will occur on 10 May at 1300 UTC. Best regards, Julie Julie Hedlund, Policy Director Action Items and Notes GNSO Review Working Group Meeting on Thursday, 26 April 2018 at 13:00 UTC Action Items: Action Item 1: implementation charter for recommendations 7 & 12: Staff will correct typos identified by Wolf-Ulrich (see meeting notes for details). Action Item 2: revised implementation charter for recommendations 1, 2, & 3: Staff will circulate the revised text of this implementation charter on the mailing list. Any feedback raised on the mailing list will be discussed on the next call. Action Item 3: implementation charter for recommendations 20 and 21: Staff will circulate the text of this implementation charter on the mailing list. Any feedback raised on the mailing list will be discussed on the next call. Action Item 4: GNSO Council Update: Staff will circulate to the WG early next week draft slides for the GNSO Council presentation in May. Notes: 1. Review agenda/SOIs: -- This is a smaller group today. The call will proceed but no decisions will be made. -- No updates to SOIs. 2. Status of Consensus Call for revised implementation charter for recommendations 7 & 12 (closing 26 April): -- The consensus call closes today. There have been no comments or objections so far. If this continues to be the cases, the charter will be deemed to be accepted by full consensus. -- Wolf-Ulrich identified small typos to correct (headline says “1,2,3” and should say “7&12.” Number 3 “Translation of Documents” under “Solutions” – typos in first and second lines: “translatin” should be “translating” and “transition” should be “translation.” 3. Discussion of the revised implementation charter for recommendations 1, 2, & 3: -- Staff has completed changes suggested on the call two weeks ago (see redlined text). -- Staff suggests putting this text out for review by the group before completing a consensus call on this implementation charter. The WG can discuss any proposed changes raised on the mailing list during the call next week. 4. Continued discussion of the implementation charter for recommendations 20 and 21: -- Recommendation 20: The scope of the Standing Committee on ICANN’s Budget and Operations could be the structure through which the GNSO provides feedback on the strategic plan. This would complement existing activities associated with analyzing the budget. -- In the last WG meeting, it was suggested that the WG would update the Council during the May Council Meeting. This proposal to expand the SCBO charter could be raised. The status of recommendations related to GDPR and Diversity (especially CCWG-Accountability recommendations on Diversity) could also be included in this discussion. -- Recommendation 21: There are a number of initiatives underway to collect data. This section outlines the existing data sources and describes how the GNSO Council and Working Groups already access this data. It is not anticipated that an additional formal mechanism is needed for the GNSO to receive information about the efforts. -- Staff suggests circulating this charter for additional feedback by the WG. -- Regarding Recommendation 20: Rafik made a comment during the last meeting asking whether the SCBO is the right place to complete this review. Wolf-Ulrich is fine with the proposed approach, but would like to give everyone an opportunity to review and provide input. -- An alternative would be for the Council to take on this review itself and possibly create an additional Standing Committee. This can be part of the discussion with the GNSO Council on the May GNSO Council call. 5. Discussion of the April Work Plan and proposed update to the GNSO Council on 24 May: -- An additional item to discuss with the GNSO Council – any items with budget implications will need to be considered by the GNSO Council. -- Staff has begun reviewing the CCWG-Accountability recommendations and cross referencing them with GNSO Review recommendations 6, 33, 35, and 36. Staff will provide this analysis to the WG for the next WG meeting. -- The Board has not yet made a decision on the CCWG-Accountability recommendations. This must be taken into consideration in drafting implementation charters that reference CCWG-Accountability recommendations. If WG implementation charters are tied to implementation of CCWG-Accountability recommendations, the implementation will not be complete until Board approval. -- It is also possible that the WG can make recommendations that are complementary to, but not dependent on, the CCWG-Accountability recommendations. -- Chat from Marika Konings to All Participants: whether implementation is achieved for those recommendations may only be possible further in the future as Board consideration is still some time out? -- Staff will gather more information about implementation of steps by the ICANN Organization to address GDPR. Once additional information is available on the details of these measures, staff will update the appropriate implementation charters (26-29). -- Motions will potentially be needed for the GNSO Council to consider in the June meeting. 6. Next Meeting: 10 May 1300 UTC: -- In the next meeting, the WG should finalize the material it would like to present to Council. -- Staff will provide a draft update to the Council early next week for the WG to consider. The WG can review the slides and suggest changes in time for the document deadline for the May Council meeting. 7. AOB: None.

1 0

Agenda and Materials for 26 April Meeting 13:00 UTC
by Julie Hedlund April 24, 2018

April 24, 2018

Dear GNSO Review Working Group members, Please see below the draft agenda for the meeting on Thursday, 26 April at 13:00 UTC. Please also see the attached materials and the action items below with updates from the previous meeting. Draft agenda: Review agenda/SOIs Status of Consensus Call for revised implementation charter for recommendations 7 & 12 (closing 26 April) Discussion of the revised implementation charter for recommendations 1, 2, & 3 Continued discussion of the implementation charter for recommendations 20 and 21 Discussion of the April Work Plan and proposed update to the GNSO Council on 24 May Next Meeting: 10 May 1300 UTC AOB Best regards, Julie Julie Hedlund, Policy Director Action Items & Updates: GNSO Review Working Group Meeting on Thursday, 12 April 2018 at 13:00 UTC Action Items: Status of actions items re: implementation charter for recommendations 1, 2, & 3: Staff will send out an email after this call with the links that were gathered regarding the fellowship program. (DONE) Staff will update the charter to point to data already being collected on CROP and the Fellowship Program. (DONE-Attached) Staff will update the determination part of the charter to state that there are existing metrics and point to those. (DONE-Attached) Staff will check with fellowship staff about whether data is self-reported from former fellows or confirmed by staff. (DONE) In referencing the GNSO Council comment on the fellowship program, Staff will note that the Council comment is focused on its role as manager of the PDP and does not necessarily incorporate more views of individual SG/Cs. SG/Cs submitted comments separately. (DONE-Attached) Staff will add a note in the determination that there are cost-effective solutions available, such as translation provided by technology rather than live human translators. Specifically, “The Working Group notes that a traditional RTT solution typically includes professional translators. Understanding that the costs for such translators may be prohibitive for some uses, other solutions may include automated services, volunteers or translations of executive summaries of transcripts after public meetings.” (DONE-Attached) Staff will put the revised charter out for consensus call and if it is approved, this item will be put on the next available Council meeting. (TBD following the 26 April Meeting) Action Item 9: Discussion of the implementation charter for recommendations 20 and 21: Staff notes that if the WG supports bringing the proposal to Council to expand the scope of the SCBO to include recommendation 20 this can also be raised in the update to Council. (DONE-See attached Work Plan)

1 0

REMINDER-CONSENSUS CALL: Recommendations 7 & 12 Implementation Charter
by Julie Hedlund April 24, 2018

April 24, 2018

Dear GNSO Review Working Group members, REMINDER: This is a Consensus Call for the GNSO Review Implementation Charter for Recommendations 7 & 12, per the action items from the meeting on 12 April. The redlines in the Working Group Determination section of the document reflect the agreed-upon changes during the meeting. As noted in the attached charter, these are the recommendations for implementation: Recommendation 7: That Stakeholder Groups and Constituencies engage more deeply with community members whose first language is other than English, as a means to overcoming language barriers. Recommendation 12: That ICANN assess the feasibility of providing a real-time transcription service in audio conferences for Working Group meetings. Staff is circulating the revised version of the charter for a two-week Consensus Call to end on Thursday, 26 April 2018. If there are no objections the recommendation will be deemed to have been implemented by Full Consensus. Best regards, Julie Julie Hedlund, Policy Director

1 0

ADOBE CONNECT – WHAT NEXT? - ICANN Blog By Ash Rangan
by Nathalie Peregrine April 20, 2018

April 20, 2018

Dear all: Please take a look at this blog on Adobe Connect. And note the request: Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here: RP-tool(a)icann.org<mailto:RP-tool@icann.org> Best regards, David https://www.icann.org/news/blog/adobe-connect-what-next[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> ADOBE CONNECT – WHAT NEXT? As you know, the ICANN organization took down its Adobe Connect service midway through the ICANN61 meeting in response to reported issues[icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_blo…> with this service. Concurrently, we began to conduct our own forensic analysis of the reported incident and began working with our Adobe cloud service provider, CoSo Cloud LLC, and through them with Adobe to learn more. Shortly thereafter, we rolled out instances of Zoom and WebEx for the community to support remote participation (RP) and collaboration. Here's where we are now: The Forensics Investigation With respect to our forensics work, we received application logfiles from CoSo Cloud, going back for a period of one year. ICANN Engineering and Security teams have examined these application log files and the results of our investigation clearly show "fingerprints of incursion" by the researcher who reported the issue. We were unable to find any other indication that anyone else either identified or exploited this issue. Thanks to the person who found the bug again. Working closely with CoSo Cloud, we were able to recreate the reported issue, and understand the conditions required to trigger it. This information has been communicated to Adobe, and Adobe is working on a software fix to address the root cause of the issue. We have also been working with CoSo on options to re-enable Adobe Connect in the shorter term. We have determined there are two viable paths to accomplish this goal. They are: 1. Deploy a hardened configuration to eliminate "man-in-the-middle" exploitations by encrypting relevant traffic, or 2. Implement a programmatic fix from CoSo Cloud to substantially reduce the window during which the issue can be exploited. With respect to the first option, we attempted to hack the hardened configuration in a test environment last week, and were not able to do so over the course of 7 hours. Separately, CoSo Cloud and Adobe conducted similar tests and confirmed that this configuration is protected from exploitation of the issue. Community Feedback and Next Steps For the last three weeks, we have been gathering limited feedback regarding users' experiences with WebEx and Zoom. So far, we have input from about 200 people, including ICANN org meeting organizers and the ICANN community. Our analysis of this feedback indicates a desire to revert back to an Adobe Connect, providing the security of the service is ensured. Accordingly, we would like to propose the following plan to the broader community for consideration: 1. We would like to restore Adobe Connect services with both the new hardened configuration and the programmatic fix discussed above. Our intent would be to restore service by 3 May. This would allow us to use Adobe Connect during several upcoming events including the Board Workshop, the GDD Industry Summit, and ICANN62. 2. Once Adobe releases a new version of the software with a fix for this issue from their perspective, and provides assurance the update has been adequately tested, we will move toward that release of Adobe Connect in a prudent manner, with the help of CoSo Cloud. We believe that this approach will ensure the security of our content, and of our community interactions, while also enabling our community to use the collaboration tools of their choice. Before we make these changes, we want to hear from you. What do you think? Please submit your thoughts on this contemplated move before May 2nd here: RP-tool(a)icann.org<mailto:RP-tool@icann.org> Meanwhile, we will continue to offer WebEx and Zoom for RP and collaboration purposes. We will also continue to follow industry developments, including the research ALAC is doing on the RP and collaboration space, to ensure we are using secure and cost-effective tools that are appropriate for our needs. I look forward to your comments! David A. Olive Senior Vice President Policy Development Support Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

GNSO Review Implementation: April Work Plan
by Julie Hedlund April 14, 2018

April 14, 2018

Dear GNSO Review Working Group members, Please see the attached Work Plan for April 2018 and the following months. In particular, as we discussed on today’s call there are two issues on which the WG agreed it would be useful to provide an update to the GNSO Council. However, as the next Council meeting is on 26 April, which means the document and motion deadline is this coming Monday, 16 April, there isn’t time to prepare an update and have it reviewed and discussed by the GNSO Review WG. Furthermore, one of the issues relates to the revised implementation charter for recommendations 7 & 12 and, specifically, the language that was included based on today’s discussion to bring to the Council’s attention any demand for language services that could have budget implications. As the charter for recommendations 7 & 12 has just gone out for a consensus call today for two weeks, we would not have the final language approved in time for the GNSO Council call. In addition, the second issue relates to recommendation 20 and the suggestion that the scope of the charter for the Standing Committee on Budget and Operations (SCBO) could be expanded, so that it is also responsible for annually reviewing ICANN’s Strategic Objectives and ensuring that the planning of future GNSO activities is in alignment with these Strategic Objectives. This would require approval by the Council, and hence would be helpful to have a discussion with the Council about this suggestion at one of its meetings. However, the GNSO Review WG only began discussion of the implementation charter for recommendations 20 and 21 during today’s meeting, and that discussion is anticipated to continue at the meeting on 26 April. So, the issue would not be ready to bring before the Council at its next meeting, but could be ready for the May meeting. Thus, in the attached Work Plan staff has suggested that an update would be prepared for review by the GNSO Review WG at its meetings on 26 April and 09 May, to be submitted by 14 May by the document and motion deadline for the Council meeting on 24 May. Furthermore, on the remaining recommendations relating to diversity (on hold pending the CCWG-Accountability diversity recommendations) and statements of interest (on hold pending GDPR) it is anticipated that the GNSO Review WG will be ready to provide an update to the GNSO Council at its 20 June meeting, so this also is noted in the Work Plan. Staff will determine if motions may be necessary for the implementation of those recommendations and will prepare them accordingly. Please let staff know if you have any questions concerning this Work Plan. Kind regards, Julie & Emily

2 3