September 2017 - Gnso-review-wg

Recordings, Attendance & AC Chat from GNSO Review WG call on Thursday, 28 September 2017 at 12:00 UTC
by Julie Bisland Oct. 2, 2017

Oct. 2, 2017

Dear all, Please find the mp3, AC Recording, attendance and AC Chat below for the GNSO Review Working Group held on Thursday, 28 September 2017 at 12:00 UTC. Mp3: http://audio.icann.org/gnso/gnso-review-28sep17-en.mp3 AC Recording: https://participate.icann.org/p7o4s67prqc/<https://participate.icann.org/p7o4s67prqc/?OWASP_CSRFTOKEN=96c8662b94871fcc…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> Mailing list archives: http://mm.icann.org/pipermail/gnso-review-wg/ Wiki agenda page: https://community.icann.org/x/5oNEB Attendance Members: Sara Bockey (RrSG Alternate) Jennifer Wolfe (RySG Primary) Rafik Dammak (NCSG Primary) Wolf-Ulrich Knoben (ISPCP Primary) Lori Schulman (IPC Primary) Participants: n/a Apologies: none ICANN staff: Julie Hedlund Amr Elsadr Marika Konings Mary Wong Julie Bisland ** Please let me know if your name has been left off the list ** Thank you. Kind regards, Julie ------------------------------- Adobe Connect chat transcript for 28 September 2017 Julie Bisland:Welcome to the GNSO Review Working Group Meeting on Thursday, 28 September 2017 at 12:00 UTC Julie Bisland:Agenda wiki page: https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_… Sara Bockey:I believe Phoenix has a conference center that is big enough... :) Wolf-Ulrich Knoben:Hi all, I still have a 30 mins break here to attend the WG meeting Wolf-Ulrich Knoben:Yes, the meeting here shall start in 25 mins Wolf-Ulrich Knoben:her = Germany Lori Schulman:good morning Wolf-Ulrich Knoben:could we start with Rec 26-29??? Wolf-Ulrich Knoben:prior to OEC discussion? Wolf-Ulrich Knoben:thanks! Julie Bisland:Welcome Mary Wong! Marika Konings:maybe the question is as well what can be disclosed? Marika Konings:can it be stated that someone is participating on behalf of a client without stating who the client is or what their exact brief was? Lori Schulman:Yes, that is my question. Amr Elsadr:My impression is that this recommendation is not creating additional requirements for SOIs being posted, but only linking those that are required to be linked to the (centralized) membership lists. I think Wolf-Ulrich is saying the same thing. Julie Bisland:Rafik, please private chat me if you'd like a dialout Rafik:no idea why it is nort working Julie Bisland:looks like Rafik is going to try to reconnect. Marika Konings:Would it be more valuable to list actual leadership positions (with years held) as an accumulation may not be that helpful? Marika Konings:Could an interim solution be to add a field asking people to list previous leadership positions held? Marika Konings:and what is considered a leadership position, that may also require some definition? Marika Konings:for example, is being an appointee to Nom Com a leadership position? Julie Bisland:Rafik stated a dialout is not an option, and his AC line dropped again. Sara Bockey:Nothing to add Lori Schulman:nothing pops out Marika Konings:I'll already be on a plane on the 26th Sara Bockey:I will be in AB on the 26th.... not sure if I will be able to attend Sara Bockey:need to look at time shift Lori Schulman:I am in Geneva on the 26th at a conference. Lori Schulman:but time could work if European time is evening Lori Schulman:In Italy on 19th but if time is evening than OK Lori Schulman:speaking on a panel Lori Schulman:8 am in US is 2 am in Italy Lori Schulman:so I am unlikely to cover Amr Elsadr:Yes, Lori. Italy and Egypt are in the same timezone, and these calls are at 14:00 local time. Lori Schulman:thanks Amr Lori Schulman:I was counting the wrong way Lori Schulman:but I may be in another meeting Amr Elsadr:It happens. :) Marika Konings:Actually, Amr, you are one hour ahead of CET at the moment :-) Lori Schulman:i am good Sara Bockey:thanks all Lori Schulman:thanks

4 3

Actions/Discussion Notes for GNSO Review WG Meeting on 28 September
by Julie Hedlund Sept. 28, 2017

Sept. 28, 2017

Dear GNSO Review Working Group members, Please see below the action items and discussion notes captured by staff from the meeting on 28 September. 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/2017. Best regards, Julie Julie Hedlund, Policy Director Action Items/Discussion Notes 28 September Action Items: OEC/GNSO Council Report: Staff to provide a draft for review at the meeting on 12 October. Recommendation 6: Combine with charters for recommendations 33 and 36 that also are pending the recommendations from the Work Stream 2 Subgroup on Diversity. Determine if any aspects of the recommendations can be extracted and marked as completed. Recommendations 26, 27, 28, & 29: Rec 26: Staff (including ICANN Legal) to provide more input on what may be required for disclosure to fulfill the requirement in recommendation 26. Rec 27: Staff to investigate the feasibility of implementing this recommendation, and report back to the WG. Rec 28: Staff to review key clauses in section 6.1.2 of the GNSO Operating Procedures that may be necessary to understand changes necessary to implement this recommendation, and provide a draft markup to clarify what changes may be necessary Rec 29: Staff to provide a proposal on addition of a field in the SOI that lists past and current leadership positions, as well as a draft definition of "leadership position" - both to be reviewed by the WG. Meeting Schedule: The WG to meet on 12 and 19 October (with 12 October changed to 1400 UTC to avoid a conflict with the GNSO Council), and meeting on 26 October to be cancelled. Notes: 1. Update on Consensus Call on Charter for Recommendation 31 – Ended COB 25 September: -- No objections or comments submitted. The Charter is approved by consensus. 2. Status of Update to OEC/GNSO Council: -- Presentation to the OEC and the GNSO Council scheduled to take place at ICANN 60. -- Staff will provide a draft report to the WG within the next week. 3. Recommendations 26-29: Recommendation 26: -- If the questions on this recommendation concern whether or not to include SOIs for exec-com members, need to update this information on a yearly basis to match yearly exec-com elections in GNSO constituencies. -- Process to review policies under consideration is that they are discussed on GNSO PDP WGs, discussions take place within GNSO SGs/Cs, and the GNSO Council accepts WG recommendations - often, many of the required SOIs are already covered, but concern raised on formalizing a requirement for all the SOIs being updated. -- Not clear what is meant by a participant's interest or position being required to be disclosed - doesn't this take place anyway during WG deliberations? If a comment is being submitted on behalf of a client, this might need to be clarified. Language of the recommendation needs to be clearer on what is required for disclosure. >From the Chat Room: Marika Konings: Maybe the question is as well what can be disclosed? Can it be stated that someone is participating on behalf of a client without stating who the client is or what their exact brief was? Recommendation 27: -- Questions to the GNSO Review WG include where a centralized list of SGs/Cs membership needs to be maintained, and what SOIs are required to be associated with this membership list Is this recommendation creating additional requirements for SOIs to be posted, or is it only requiring that posted SOIs be linked to the centralized GNSO membership lists also being recommended? Recommendation 28: -- No comments from WG members on this recommendation Recommendation 29: >From the Chat Room: Marika Konings: -- Would it be more valuable to list actual leadership positions (with years held) as an accumulation may not be that helpful? -- Could an interim solution be to add a field asking people to list previous leadership positions held? and what is considered a leadership position, that may also require some definition? -- Suggestion to add a field that lists current and previous leadership positions, noting that a definition of leadership position needs to be agreed upon 4. Meeting Schedule: -- May be of value to hold a meeting on 19 October as well, to review any documents/reports that need to be submitted to the GNSO Council by the 10-day deadline to submit documents ahead of the 1 November public Council meeting. -- WG agreement: WG to meet on 12 and 19 October (with 12 October changed to 1400 UTC to avoid a conflict with the GNSO Council), and meeting on 26 October to be cancelled.

1 0

CLOSED - CONSENSUS CALL: Recommendation 31 Implementation Charter
by Julie Hedlund Sept. 26, 2017

Sept. 26, 2017

Dear GNSO Review Working Group members, This Consensus Call below closed on 25 September and no objections were received. As there were no objections the implementation of Recommendation 31 is 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-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Monday, September 18, 2017 at 8:43 AM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: [Gnso-review-wg] REMINDER - CONSENSUS CALL: Recommendation 31 Implementation Charter Dear GNSO Review Working Group members, This is a Consensus Call for the GNSO Review Implementation Charter for Recommendation 31. As noted in the attached charter, this is the recommendation for implementation: “That the GAC-GNSO Consultation Group on GAC Early Engagement in the GNSO Policy Development Process continue its two work streams as priority projects. As a part of its work it should consider how the GAC could appoint a non-binding, non-voting liaison to the Working Group of each relevant GNSO PDP as a means of providing timely input.” Previously, Working Group members were requested to review the revised charter by COB Friday, 08 September. No comments were received during the review period, so staff is circulating the final version of the charter for a two-week Consensus Call to end on Monday, 25 September. Best regards, Julie Julie Hedlund, Policy Director

1 0

Agenda and Materials for GNSO Review WG Call on 28 September 2017
by Julie Hedlund Sept. 25, 2017

Sept. 25, 2017

Dear GNSO Review Working Group members, Please see the draft agenda below and attached materials for the meeting on Thursday, 28 September at 1200 UTC. For the latest status see: https://community.icann.org/display/GRWG/Status+of+Draft+Documents+and+Cons…. Draft Agenda: Review agenda SOIs Update on Consensus Call on Charter for Recommendation 31 – Ended COB 25 September Status of Update to OEC/GNSO Council Begin discussion on Recommendations 26-29 Meeting Schedule: Next meeting 12 October AOB Best regards, Julie Julie Hedlund, Policy Director

1 0

REMINDER FOR REVIEW/DISCUSSION: Charter for Recommendations 26-29
by Julie Hedlund Sept. 25, 2017

Sept. 25, 2017

Dear GNSO Review Working Group members, This is a reminder. As noted in the action items below from our last call, please see the attached draft charter for recommendations 26-29 for review and discussion. Please also see below comments already received from Wolf-Ulrich Knoben. Please send your comments to the list to facilitate discussion. Best regards, Julie Julie Hedlund, Policy Director Comments from Wolf-Ulrich Knoben: With respect to Rec 26 it is suggested to include SG/C ExComm members in the definition of "Relevant Party". I wonder whether this is useful. The ExComms' function is of organisational character. There's no "policy development" task behind compared with the GNSO groups defined under 5.1.a. and b. Anyway it seems from your list that these SOIs are already provided by the respective groups and no additional administration may be required. If so - let it go. Rec. 27: The suggestion "Operating Principles and Participation Guidelines could be modified to include a requirement for Stakeholder Groups and Constituencies to provide access to ICANN to their membership lists for aggregating into a comprehensive central list" is sensitive and has to be discussed within the SG/Cs. The requirements for SOIs should strictly be oriented along the existing definitions. Rec. 29: It requires a yearly update of all SOIs which make reference to holding leadership positions. That would be administratively overloaded. Doesn't the SOI provide an original date of provision and updates? This would help to calculate the total years of leadership when the "present" duration is given. From: Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, September 14, 2017 at 2:24 PM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: Actions/Discussion Notes for GNSO Review WG Meeting on 14 September Dear GNSO Review Working Group members, Please see below the action items and discussion notes captured by staff from the meeting on 14 September. 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/2017. Best regards, Julie Julie Hedlund, Policy Director Action Items/Discussion Notes 24 September Action Items: Timeline: Add OEC and GNSO Council Updates to the calendar. (DONE – See attached.) OEC/GNSO Council Report: Staff to provide a draft for review at the meeting on 28 September. Recommendation 6: Combine with charters for recommendations 33 and 36 that also are pending the recommendations from the Work Stream 2 Subgroup on Diversity. Determine if any aspects of the recommendations can be extracted and marked as completed. Recommendations 26-29: Resend the charter to the list for review and discussion. Notes: 1. Update on Consensus Call on Charter for Recommendation 31 – Ends COB 25 September: Recommendation 31 was put for review for 1 week - no comments were submitted. Consensus call began on Monday, 11 September, and will run through until 25 September - no comments made so far. If no comments or objections are submitted, the charter for the implementation of Recommendation 31 will be considered approved by full consensus. 2. Timeline/Status and Update to OEC/GNSO Council: Updates to the GNSO Council and the Board OEC planned for ICANN 60. WG essentially complete with Phase 1, and beginning Phase 2 (high-priority recommendations). WG slightly behind expected/suggested timeline - timeline was meant to provide guidance, but was expected to not be met in the event that implementation delays arose. Some Phase 1 recommendations deferred to Phase 2. List of recommendations completed in Phase 1 listed on Timeline slide 1. Recommendation 18 deferred from Phase 1 to Phase 2 - awaiting advisory. Recommendation 33 is pending the results the WS2 Subgroup on Diversity Recommendations 25 - 29 all concern SOIs for community members, currently on the WG agenda. Updates to the Board OEC are meant to be provided twice/year - next one scheduled at, or immediately prior to ICANN60 - staff will prepare a draft report, which should be reviewed within the next week - reports should be ready by mid-October 2017, to be circulated to the OEC and GNSO Council prior to the updates at ICANN60. Same report drafted for the OEC can be used for the update to the GNSO Council, likely to take place at the GNSO Council public meeting at ICANN 60. OEC support staff has provided a template to be used to complete the update report - report is meant to indicate the extent to which progress has been made, and any budget considerations that are required, what items have not been completed + expected completion dates and budgetary implications. Information required in the update reports are already captured in the staff-prepared implementation plan - will input this information in the OEC template. Reports need to be thorough enough to provide the OEC and the GNSO Council with the information required for them to understand the progress of the WG so far, and expected timeline for completion of outstanding tasks. Details available on WG wiki - can be linked to in the update reports. Dependency of recommendations 10 and 11 on work done by new gTLD Sub-Pro on outcome/report of the facilitated session for that PDP at ICANN 59 - report is being reviewed by the PDP WG leadership, and once shared, will be available to the GNSO Review WG - expected within the next few weeks. 3. Begin discussion on Recommendation 6: Progress on this recommendation (similar to recommendation 6) is dependent on the progress made on the CCWG-ACCT WS2 Sub Group on Diversity, specifically, their recommendations. Data protection/privacy requirements by GDPR scheduled to take effect in May 2018 may play a role in what data being recommended for collection will be permissible for collection and publication. Diversity subgroup is going through a second reading of its recommendations in two weeks. If approved it will be moved to public comments. Includes recommendations about data collection, metrics, and SO/AC groups. It will apply to the GNSO if it is approved as recommended. Timeline: Second reading in CCWG and if approved then staff will prepare it for public consultation for 40 days. Depending on comments the Subgroup may revise the recommendations. Final is sent to the full CCWG, which has its own timeline to check the consistency among the subgroup. Possibly done by ICANN61. Link in the charter to the work of the subgroup and indicate a timeline for completion. Note also that the WG could adopt the recommendations and definition of diversity. As noted by staff, GNSO WGs already publish statistics on WG member participation in WGs - suggestions that elements on diversity in recommendations 6, 33 and others (26-29) could be consolidated to clarify dependencies on outcome of the CCWG-ACCT WS2 Sub Group on Diversity. Language exists in the recommendation 6 Charter on mentions of diversity in GSNO SG/C Charters/Bylaws - discussions in other groups, such as SSAC also exist, but different stakeholders recognize that there is ongoing work in WS2 CCWG-ACCT, and are also awaiting the outcomes there to not duplicate efforts.

1 0

REMINDER - CONSENSUS CALL: Recommendation 31 Implementation Charter
by Julie Hedlund Sept. 18, 2017

Sept. 18, 2017

Dear GNSO Review Working Group members, This is a Consensus Call for the GNSO Review Implementation Charter for Recommendation 31. As noted in the attached charter, this is the recommendation for implementation: “That the GAC-GNSO Consultation Group on GAC Early Engagement in the GNSO Policy Development Process continue its two work streams as priority projects. As a part of its work it should consider how the GAC could appoint a non-binding, non-voting liaison to the Working Group of each relevant GNSO PDP as a means of providing timely input.” Previously, Working Group members were requested to review the revised charter by COB Friday, 08 September. No comments were received during the review period, so staff is circulating the final version of the charter for a two-week Consensus Call to end on Monday, 25 September. Best regards, Julie Julie Hedlund, Policy Director

1 0

FOR REVIEW/DISCUSSION: Charter for Recommendations 26-29
by Julie Hedlund Sept. 14, 2017

Sept. 14, 2017

Dear GNSO Review Working Group members, As noted in the action items below from today’s call, please see the attached draft charter for recommendations 26-29 for review and discussion. Please also see below comments already received from Wolf-Ulrich Knoben. Please send your comments to the list to facilitate discussion. Best regards, Julie Julie Hedlund, Policy Director Comments from Wolf-Ulrich Knoben: With respect to Rec 26 it is suggested to include SG/C ExComm members in the definition of "Relevant Party". I wonder whether this is useful. The ExComms' function is of organisational character. There's no "policy development" task behind compared with the GNSO groups defined under 5.1.a. and b. Anyway it seems from your list that these SOIs are already provided by the respective groups and no additional administration may be required. If so - let it go. Rec. 27: The suggestion "Operating Principles and Participation Guidelines could be modified to include a requirement for Stakeholder Groups and Constituencies to provide access to ICANN to their membership lists for aggregating into a comprehensive central list" is sensitive and has to be discussed within the SG/Cs. The requirements for SOIs should strictly be oriented along the existing definitions. Rec. 29: It requires a yearly update of all SOIs which make reference to holding leadership positions. That would be administratively overloaded. Doesn't the SOI provide an original date of provision and updates? This would help to calculate the total years of leadership when the "present" duration is given. From: Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, September 14, 2017 at 2:24 PM To: "gnso-review-wg(a)icann.org" <gnso-review-wg(a)icann.org> Subject: Actions/Discussion Notes for GNSO Review WG Meeting on 14 September Dear GNSO Review Working Group members, Please see below the action items and discussion notes captured by staff from the meeting on 14 September. 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/2017. Best regards, Julie Julie Hedlund, Policy Director Action Items/Discussion Notes 24 September Action Items: Timeline: Add OEC and GNSO Council Updates to the calendar. (DONE – See attached.) OEC/GNSO Council Report: Staff to provide a draft for review at the meeting on 28 September. Recommendation 6: Combine with charters for recommendations 33 and 36 that also are pending the recommendations from the Work Stream 2 Subgroup on Diversity. Determine if any aspects of the recommendations can be extracted and marked as completed. Recommendations 26-29: Resend the charter to the list for review and discussion. Notes: 1. Update on Consensus Call on Charter for Recommendation 31 – Ends COB 25 September: Recommendation 31 was put for review for 1 week - no comments were submitted. Consensus call began on Monday, 11 September, and will run through until 25 September - no comments made so far. If no comments or objections are submitted, the charter for the implementation of Recommendation 31 will be considered approved by full consensus. 2. Timeline/Status and Update to OEC/GNSO Council: Updates to the GNSO Council and the Board OEC planned for ICANN 60. WG essentially complete with Phase 1, and beginning Phase 2 (high-priority recommendations). WG slightly behind expected/suggested timeline - timeline was meant to provide guidance, but was expected to not be met in the event that implementation delays arose. Some Phase 1 recommendations deferred to Phase 2. List of recommendations completed in Phase 1 listed on Timeline slide 1. Recommendation 18 deferred from Phase 1 to Phase 2 - awaiting advisory. Recommendation 33 is pending the results the WS2 Subgroup on Diversity Recommendations 25 - 29 all concern SOIs for community members, currently on the WG agenda. Updates to the Board OEC are meant to be provided twice/year - next one scheduled at, or immediately prior to ICANN60 - staff will prepare a draft report, which should be reviewed within the next week - reports should be ready by mid-October 2017, to be circulated to the OEC and GNSO Council prior to the updates at ICANN60. Same report drafted for the OEC can be used for the update to the GNSO Council, likely to take place at the GNSO Council public meeting at ICANN 60. OEC support staff has provided a template to be used to complete the update report - report is meant to indicate the extent to which progress has been made, and any budget considerations that are required, what items have not been completed + expected completion dates and budgetary implications. Information required in the update reports are already captured in the staff-prepared implementation plan - will input this information in the OEC template. Reports need to be thorough enough to provide the OEC and the GNSO Council with the information required for them to understand the progress of the WG so far, and expected timeline for completion of outstanding tasks. Details available on WG wiki - can be linked to in the update reports. Dependency of recommendations 10 and 11 on work done by new gTLD Sub-Pro on outcome/report of the facilitated session for that PDP at ICANN 59 - report is being reviewed by the PDP WG leadership, and once shared, will be available to the GNSO Review WG - expected within the next few weeks. 3. Begin discussion on Recommendation 6: Progress on this recommendation (similar to recommendation 6) is dependent on the progress made on the CCWG-ACCT WS2 Sub Group on Diversity, specifically, their recommendations. Data protection/privacy requirements by GDPR scheduled to take effect in May 2018 may play a role in what data being recommended for collection will be permissible for collection and publication. Diversity subgroup is going through a second reading of its recommendations in two weeks. If approved it will be moved to public comments. Includes recommendations about data collection, metrics, and SO/AC groups. It will apply to the GNSO if it is approved as recommended. Timeline: Second reading in CCWG and if approved then staff will prepare it for public consultation for 40 days. Depending on comments the Subgroup may revise the recommendations. Final is sent to the full CCWG, which has its own timeline to check the consistency among the subgroup. Possibly done by ICANN61. Link in the charter to the work of the subgroup and indicate a timeline for completion. Note also that the WG could adopt the recommendations and definition of diversity. As noted by staff, GNSO WGs already publish statistics on WG member participation in WGs - suggestions that elements on diversity in recommendations 6, 33 and others (26-29) could be consolidated to clarify dependencies on outcome of the CCWG-ACCT WS2 Sub Group on Diversity. Language exists in the recommendation 6 Charter on mentions of diversity in GSNO SG/C Charters/Bylaws - discussions in other groups, such as SSAC also exist, but different stakeholders recognize that there is ongoing work in WS2 CCWG-ACCT, and are also awaiting the outcomes there to not duplicate efforts.

1 0

Actions/Discussion Notes for GNSO Review WG Meeting on 14 September
by Julie Hedlund Sept. 14, 2017

Sept. 14, 2017

Dear GNSO Review Working Group members, Please see below the action items and discussion notes captured by staff from the meeting on 14 September. 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/2017. Best regards, Julie Julie Hedlund, Policy Director Action Items/Discussion Notes 24 September Action Items: Timeline: Add OEC and GNSO Council Updates to the calendar. (DONE – See attached.) OEC/GNSO Council Report: Staff to provide a draft for review at the meeting on 28 September. Recommendation 6: Combine with charters for recommendations 33 and 36 that also are pending the recommendations from the Work Stream 2 Subgroup on Diversity. Determine if any aspects of the recommendations can be extracted and marked as completed. Recommendations 26-29: Resend the charter to the list for review and discussion. Notes: 1. Update on Consensus Call on Charter for Recommendation 31 – Ends COB 25 September: Recommendation 31 was put for review for 1 week - no comments were submitted. Consensus call began on Monday, 11 September, and will run through until 25 September - no comments made so far. If no comments or objections are submitted, the charter for the implementation of Recommendation 31 will be considered approved by full consensus. 2. Timeline/Status and Update to OEC/GNSO Council: Updates to the GNSO Council and the Board OEC planned for ICANN 60. WG essentially complete with Phase 1, and beginning Phase 2 (high-priority recommendations). WG slightly behind expected/suggested timeline - timeline was meant to provide guidance, but was expected to not be met in the event that implementation delays arose. Some Phase 1 recommendations deferred to Phase 2. List of recommendations completed in Phase 1 listed on Timeline slide 1. Recommendation 18 deferred from Phase 1 to Phase 2 - awaiting advisory. Recommendation 33 is pending the results the WS2 Subgroup on Diversity Recommendations 25 - 29 all concern SOIs for community members, currently on the WG agenda. Updates to the Board OEC are meant to be provided twice/year - next one scheduled at, or immediately prior to ICANN60 - staff will prepare a draft report, which should be reviewed within the next week - reports should be ready by mid-October 2017, to be circulated to the OEC and GNSO Council prior to the updates at ICANN60. Same report drafted for the OEC can be used for the update to the GNSO Council, likely to take place at the GNSO Council public meeting at ICANN 60. OEC support staff has provided a template to be used to complete the update report - report is meant to indicate the extent to which progress has been made, and any budget considerations that are required, what items have not been completed + expected completion dates and budgetary implications. Information required in the update reports are already captured in the staff-prepared implementation plan - will input this information in the OEC template. Reports need to be thorough enough to provide the OEC and the GNSO Council with the information required for them to understand the progress of the WG so far, and expected timeline for completion of outstanding tasks. Details available on WG wiki - can be linked to in the update reports. Dependency of recommendations 10 and 11 on work done by new gTLD Sub-Pro on outcome/report of the facilitated session for that PDP at ICANN 59 - report is being reviewed by the PDP WG leadership, and once shared, will be available to the GNSO Review WG - expected within the next few weeks. 3. Begin discussion on Recommendation 6: Progress on this recommendation (similar to recommendation 6) is dependent on the progress made on the CCWG-ACCT WS2 Sub Group on Diversity, specifically, their recommendations. Data protection/privacy requirements by GDPR scheduled to take effect in May 2018 may play a role in what data being recommended for collection will be permissible for collection and publication. Diversity subgroup is going through a second reading of its recommendations in two weeks. If approved it will be moved to public comments. Includes recommendations about data collection, metrics, and SO/AC groups. It will apply to the GNSO if it is approved as recommended. Timeline: Second reading in CCWG and if approved then staff will prepare it for public consultation for 40 days. Depending on comments the Subgroup may revise the recommendations. Final is sent to the full CCWG, which has its own timeline to check the consistency among the subgroup. Possibly done by ICANN61. Link in the charter to the work of the subgroup and indicate a timeline for completion. Note also that the WG could adopt the recommendations and definition of diversity. As noted by staff, GNSO WGs already publish statistics on WG member participation in WGs - suggestions that elements on diversity in recommendations 6, 33 and others (26-29) could be consolidated to clarify dependencies on outcome of the CCWG-ACCT WS2 Sub Group on Diversity. Language exists in the recommendation 6 Charter on mentions of diversity in GSNO SG/C Charters/Bylaws - discussions in other groups, such as SSAC also exist, but different stakeholders recognize that there is ongoing work in WS2 CCWG-ACCT, and are also awaiting the outcomes there to not duplicate efforts.

1 0

Recordings, Attendance & AC Chat from GNSO Review WG call on Thursday, 14 September 2017 at 12:00 UTC
by Nathalie Peregrine Sept. 14, 2017

Sept. 14, 2017

Dear all, Please find the mp3, attendance and chat below for the GNSO Review Working Group held on Thursday, 14 September 2017 at 12:00 UTC. Mp3: http://audio.icann.org/gnso/gnso-review-14sep17-en.mp3 AC Recording: https://participate.icann.org/p7ohjjqbxn3/<https://participate.icann.org/p7ohjjqbxn3/?OWASP_CSRFTOKEN=896f95e112d5b2ad…> The recordings and transcriptions of the calls are posted on the GNSO Master Calendar page: http://gnso.icann.org/en/group-activities/calendar<https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_en_group…> Mailing list archives: http://mm.icann.org/pipermail/gnso-review-wg/ Wiki agenda page: https://community.icann.org/x/vAghB Attendance Members: Sara Bockey (RrSG Alternate) Rafik Dammak (NCSG Primary) Wolf-Ulrich Knoben (ISPCP Primary) Lawrence Olawale-Roberts (BC Primary) Participants: Kris Seeburn (NCUC – Participant) Apologies: Jennifer Wolfe (RySG Primary) ICANN staff: Julie Hedlund Amr Elsadr Marika Konings Nathalie Peregrine ** Please let me know if your name has been left off the list ** Thank you. Kind regards, Nathalie ------------------------------- Adobe Connect chat transcript for 14 September 2017 Terri Agnew: Welcome to the GNSO Review Working Group Meeting on Thursday, 14 September 2017 at 12:00 UTC for 60 minutes. Terri Agnew:agenda wiki page: https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_… Krishna Seeburn - Kris:i did get a plugin notice... Krishna Seeburn - Kris:yep Krishna Seeburn - Kris:me i did Sara Bockey:My plug in updated a few weeks ago Krishna Seeburn - Kris:just a question when do we need to complete them? Krishna Seeburn - Kris:it seems people are slowly losing interest and the most i've seen is on the new gtld consequent procedures..... Krishna Seeburn - Kris:totally agree Krishna Seeburn - Kris:it would help Nathalie Peregrine:Lawrence Owalale Roberts has joined the call. Krishna Seeburn - Kris:does the board need a detailed report or sumarrised one Lawrence:sorry for joining in late I was waiting for a dialout as my internet connection won't be stable as am on a trip Krishna Seeburn - Kris:ok thanks...very much Krishna Seeburn - Kris:very good Krishna Seeburn - Kris:i agree it might take time.... Amr Elsadr:May 2018 Sara Bockey:May 28,2018 Amr Elsadr:on GDPR. Krishna Seeburn - Kris:may 2018 Krishna Seeburn - Kris:personal and private information needs personal consensus and should clearly state what is the use for that information and who will have access any third aprties etc., Amr Elsadr:If I'm not mistaken, the WS2 Sub Group on Diversity working document also contains a draft definition for "diversity", which may be found to be helpful for this WG. Rafik:the report sent for CCWG https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_do… Rafik:it includes elemts of diversity Amr Elsadr:Right, Rafik. Thanks. Krishna Seeburn - Kris:Did we receive any views for the WG on GDPR? Amr Elsadr:Apologies, Kris..., not clear on what you are asking. Are you referring to this WG or the Next-Gen RDS? Rafik:CCWG will end by next june and all its recommendations should be ready before for chartering organizations approval Krishna Seeburn - Kris:@julie that would make sense and helpful to move things forward Krishna Seeburn - Kris:yes ALAC is also doing same true Krishna Seeburn - Kris:thnaks bye Rafik:bye all Sara Bockey:thanks

1 0

Agenda and Materials for GNSO Review WG Call on 14 September 2017
by Julie Hedlund Sept. 12, 2017

Sept. 12, 2017

Dear GNSO Review Working Group members, Please see the draft agenda below and attached materials for the meeting on Thursday, 14 September at 1200 UTC. For the latest status see: https://community.icann.org/display/GRWG/Status+of+Draft+Documents+and+Cons…. Draft Agenda: Review agenda SOIs Update on Consensus Call on Charter for Recommendation 31 – Ends COB 25 September Discuss Timeline/Status and Update to OEC/GNSO Council Begin discussion on Recommendation 6 Begin discussion on Recommendations 26-29, time permitting Meeting Schedule: Next meeting 28 September AOB Best regards, Julie Julie Hedlund, Policy Director

1 0