From mesumbeslin at gmail.com Sun Feb 12 14:06:40 2023 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sun, 12 Feb 2023 23:06:40 +1100 Subject: [NCSG-PC] Fwd: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 16 February 2023 at 05:00 UTC In-Reply-To: <38BFC001-0A78-4C06-A9CC-0160E9A66D55@icann.org> References: <38BFC001-0A78-4C06-A9CC-0160E9A66D55@icann.org> Message-ID: Hi all, Here is the draft agenda for this month's council meeting. We will be walking through it during our policy meeting on Monday. Warmly, Tomslin ---------- Forwarded message --------- From: Terri Agnew via council Date: Tue, 7 Feb 2023 at 08:48 Subject: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 16 February 2023 at 05:00 UTC To: council at gnso.icann.org , liaison6c at gnso.icann.org Cc: gnso-secs at icann.org Dear all, Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/zwOBDQ. This agenda was established according to the GNSO Operating Procedures v3.5, updated on 24 October 2019. For convenience: - An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. - An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda. GNSO Council meeting on Thursday, 16 February 2023 at 05:00 UTC: https://tinyurl.com/2mx8bt8t. (Wednesday) 21:00 Los Angeles; (Thursday) 00:00 Washington DC; 05:00 London; 06:00 Paris; 08:00 Moscow; 16:00 Melbourne *GNSO Council Meeting Remote Participation:* *https://icann.zoom.us/j/97891627902?pwd=RURCTitiNEVwd2UySEk1QkRESmlFZz09* Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call. ___________________________________ *Item 1: Administrative Matters (10 minutes)* 1.1 - Roll Call 1.2 - Updates to Statements of Interest 1.3 - Review / Amend Agenda 1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures: Minutes of the GNSO Council meeting on 15 December 2022 were posted on 03 January 2023. Minutes of the GNSO Council meeting on 19 January 2023 were posted on 02 February 2023. *Item 2: Opening Remarks / Review of Projects & Action List (0 minutes)* 2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List and Action Item List. *Item 3: Consent Agenda (5 minutes) * - Nomination of a Mentor for the ICANN Fellowship Selection Committee - Taiwo Peter Akinremi - Motion for the Adoption of the Revised Charter for the Budget and Operations Townhall *Item 4: COUNCIL VOTE - Adoption of the Amended Charter for the Transfer Policy Review PDP and Approval of the Policy Change Request (20 Minutes)* The Council initiated the two-phased Transfer Policy Review PDP in February 2021. Since it began meeting in May 2021, the WG has made steady progress on its Phase 1 charter questions, including publishing its Phase 1A Initial Report for public comment. The WG conducted preliminary deliberations on Phase 1B topics during the Phase 1A Initial Report public comment period, then reviewed public comments on the Phase 1A Initial Report, and is now completing revisions to preliminary recommendations, taking into account public comment received. In the course of Phase 1 work conducted to date, the WG discovered that certain Phase 2 topics must be addressed before Phase 1 recommendations can be fully developed. As a result, the leadership team prepared a Policy Change Request (PCR ) to update its work plan to consolidate all work into a single phase and change the order in which topics are considered. This will impact the timeline for key deliverables. In order to ensure that Council fully understood the potential changes prior to being asked to accept the Project Change Request (PCR), the changes and potential implications were shared with the Council and reviewed during the January meeting. Because the PDP was initially chartered in two phases, as a consequence of the PCR, the charter requires minor revisions to remove references to phases. Here, the Council will approve the amended Charter and approve the PCR for the Transfer Policy Review PDP. 4.1 ? Presentation of motion - (Osvaldo Novoa, GNSO Council Liaison, Transfer Policy Review PDP) 4.2 ? Council discussion 4.3 ? Council vote (voting threshold: simple majority) *Taking this action is within the GNSO?s remit as outlined in ICANN?s Bylaws as the GNSO ?shall be responsible for developing and recommending to the Board substantive policies relating to generic top-level domains and other responsibilities of the GNSO as set forth in these Bylaws? (Art.11.1). Furthermore, this action complies with the requirements set out in Annex A: GNSO Policy Development Process of the ICANN Bylaws.* *Item 5: COUNCIL DISCUSSION - Update on the Council Committee for Overseeing and Implementing Continuous Improvements (CCOICI)?s Working Group Self-Assessment Recommendations Report and Update from the Statement of Interest (SOI) Task Force (20 minutes)* The GNSO Council resolved on 16 June 2021 to initiate the Council Committee for Overseeing and Implementing Continuous Improvements (CCOICI) as a pilot, which included the review of the Working Group Self-Assessment as one of the two areas of focus. The CCOICI started the Working Group Self-Assessment assignment in October 2021 and concluded its work on this assignment in February 2022. However, the CCOICI deferred conducting the public comment until it could be combined with recommendations related to the GNSO Statement of Interest (SOI). The consolidated public comment proceeding on Proposed Updates to the GNSO Operating Procedures was initiated on 09 September 2022 and closed on 14 November 2022. The CCOICI integrated public comments as appropriate and submitted its Recommendations Report to the Council on 5 January 2023. Here, the Council will receive an update on both the CCOICI?s Working Group Self-Assessment Recommendations Report. In addition, an update will be provided on the work of the the GNSO SOI Task Force (TF). 5.1 ? Introduction of topic (Manju Chen, Chair of the CCOICI) 5.2 ? Council discussion 5.3 - Next steps *Item 6: COUNCIL DISCUSSION - ICANN76 Meeting Planning (15 minutes)* The ICANN76 Community Forum is scheduled from 11-16 March 2023. With the meeting quickly approaching, the GNSO Council has a number of sessions that require advance planning. The Draft ICANN76 Schedule was shared on 20 January 2023 and the various GNSO Council related sessions were briefly discussed. Those sessions include: - PDP/EPDP meetings on Saturday. - The GNSO working sessions (3) are scheduled for Sunday. - The joint meeting with the ccNSO on Monday. - The joint meeting with the ICANN Board on Tuesday. - The public Council meeting on Wednesday. - The GNSO Council wrap-up on Thursday. Here, the Council will discuss and prepare for the various Council-related sessions scheduled during ICANN76. 6.1 ? Introduction of topic (Council leadership) 6.2 ? Council discussion 6.3 - Next steps *Item 7: COUNCIL DISCUSSION - PDP Improvements item #8 (Review of the Policy & Implementation recommendations) (15 minutes)* The GNSO Council established a PDP Improvements Tracker in order to provide an aggregated view of the various proposed improvements that have been identified from a number of different initiatives., which include: - Council Strategic Planning Session (SPS) Action Item ? how to improve support for and follow up on policy recommendations post-Council adoption - Operational Design Phase - Modifying Consensus Policies - PDP 3.0 Parking Lot Items - Review of Policy & Implementation Recommendations For item #8 (Review of the Policy & Implementation recommendations) and the agreed next step (?Staff support team to provide further detail on what a policy status report (PSR) would be expected to cover?), staff circulated a background note on a possible PSR on the Policy & Implementation Recommendations on 20 January 2023. Here, the Council will discuss the background note and consider next steps. 7.1 ? Introduction of topic (Council leadership) 7.2 ? Council discussion 7.3 - Next steps *Item 8: COUNCIL DISCUSSION - Uniform Domain Name Dispute Resolution Policy (UDRP) Review Next Steps (15 minutes)* After the approval of the Phase 1 Final Report of the GNSO Policy Development Process (PDP) on the Review of All Rights Protection Mechanisms (RPMs) in All gTLDs in January 2021, the Council discussed the need to review the RPMs charter in advance of launching Phase 2 of the PDP. The Council determined that a Policy Status Report (PSR) should be requested from ICANN org, in order to better understand if new issues or information has emerged that would be relevant to a comprehensive review of the policy. ICANN org?s Global Domains and Strategy (GDS) team completed the draft PSR and published it for public comment on 3 March 2022; the revised PSR was shared with the Council on 18 July 2022 and the Council then received a briefing from GDS during the July meeting. During this meeting and subsequent meetings, there seemed to be support from the Council to delay next steps based on a number of reasons, primarily though because of the amount of competing work. The Council agreed during its November meeting that because of the launch of the Phase 1 RPMs Implementation Review Team (IRT), which would likely have overlapping community support with a Phase 2 PDP, that the delay for next steps should be tied to the completion or key milestones for the IRT Here, the Council will receive an update from the Council?s liaison to the RPMs IRT to better understand precise timing for delaying Phase 2 next steps. 8.1 ? Introduction of topic (John McElwaine, GNSO Council liaison to the Rights Protection Mechanisms IRT) 8.2 ? Council discussion 8.3 - Next steps *Item 9: ANY OTHER BUSINESS (5 minutes)* 9.1 - Standing Selection Committee (SSC) process feedback 9.2 - Update on Closed Generics Facilitated Dialogue _______________________________ Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i)) See https://www.icann.org/resources/pages/governance/bylaws-en/#article11. Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4) See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedures-30jan18-en.pdf *References for Coordinated Universal Time of 05:00 UTC* Local time between November and March in the NORTHERN hemisphere ---------------------------------------------------------------------------- California, USA (PST) UTC-8 (Wednesday) 21:00 San Jos?, Costa Rica (CST) UTC-6 (Wednesday) 23:00 New York/Washington DC, USA (EST) UTC-5 (Thursday) 00:00 Buenos Aires, Argentina (ART) UTC-3 02:00 Rio de Janeiro, Brazil (BRT) UTC-3 02:00 London, United Kingdom (GMT) UTC+0 05:00 Kinshasa, Democratic Republic of Congo (WAT) UTC+1 06:00 Paris, France (CET) UTC+1 06:00 Moscow, Russia (MSK) UTC+3 08:00 Singapore (SGT) UTC+8 13:00 Melbourne, Australia (AEDT) UTC+11 16:00 ---------------------------------------------------------------------------- DST starts on Sunday 26 March 2023, 2:00 or 3:00 local time (with exceptions) for EU countries and on Sunday 12 March 2023 for the U.S. DST ends on Sunday 29 October 2023 for EU countries, and on Sunday 05 November 2023 for the US. ---------------------------------------------------------------------- For other places see http://www.timeanddate.com and https://tinyurl.com/2mx8bt8t. _______________________________________________ council mailing list council at gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -------------- next part -------------- An HTML attachment was scrubbed... URL: From PolicyCalendar at icann.org Sun Feb 12 22:28:17 2023 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Sun, 12 Feb 2023 20:28:17 +0000 Subject: [NCSG-PC] REMINDER: NCSG Policy Call | 13 February at 11:30 UTC Message-ID: Please join the NCSG Monthly Policy call on Monday, 13 February at 11:30 UTC. Additional time zone support here. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 WANT US TO CALL YOU? Please send dial-out request and apologies to brenda.brewer at icann.org. One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) PHONE ONLY DETAILS: Find your local number: https://icann.zoom.us/u/ayKmeftWg Meeting ID: 988 7818 9584 Phone only Passcode: 7740925615 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2684 bytes Desc: not available URL: From brenda.brewer at icann.org Sun Feb 12 22:45:59 2023 From: brenda.brewer at icann.org (Brenda Brewer) Date: Sun, 12 Feb 2023 20:45:59 +0000 Subject: [NCSG-PC] REMINDER: NCSG Policy Call | 13 February at 11:30 UTC Message-ID: <5FF58CAC-FE31-4932-BE88-DF4509CE1371@icann.org> Good day all, Please join the NCSG Monthly Policy call on Monday, 13 February at 11:30 UTC. Additional time zone support here. The join details are attached and noted below for your convenience. Thank you. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) Kind regards, Andrea and Brenda -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: REMINDER- NCSG Policy Call 13 February at 11-30 UTC.ics Type: text/calendar Size: 2695 bytes Desc: REMINDER- NCSG Policy Call 13 February at 11-30 UTC.ics URL: -------------- next part -------------- An embedded message was scrubbed... From: Tomslin Samme-Nlar Subject: [Ext] [NCSG-PC] Fwd: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 16 February 2023 at 05:00 UTC Date: Sun, 12 Feb 2023 23:06:40 +1100 Size: 58454 URL: From PolicyCalendar at icann.org Mon Feb 13 13:15:21 2023 From: PolicyCalendar at icann.org (ICANN Policy Calendar) Date: Mon, 13 Feb 2023 11:15:21 +0000 Subject: [NCSG-PC] 15-minute REMINDER: NCSG Policy Call | 13 February at 11:30 UTC Message-ID: Please join the NCSG Monthly Policy call on Monday, 13 February at 11:30 UTC. Additional time zone support here. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 WANT US TO CALL YOU? Please send dial-out request and apologies to brenda.brewer at icann.org. One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) PHONE ONLY DETAILS: Find your local number: https://icann.zoom.us/u/ayKmeftWg Meeting ID: 988 7818 9584 Phone only Passcode: 7740925615 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2694 bytes Desc: not available URL: From brenda.brewer at icann.org Mon Feb 13 13:24:53 2023 From: brenda.brewer at icann.org (Brenda Brewer) Date: Mon, 13 Feb 2023 11:24:53 +0000 Subject: [NCSG-PC] FW: 5-minute REMINDER: NCSG Policy Call | 13 February at 11:30 UTC Message-ID: <4249512B-14AA-44C7-8D86-AC742EB953FA@icann.org> Good day all, Please join the NCSG Monthly Policy call on Monday, 13 February at 11:30 UTC. Additional time zone support here. Join details are attached and noted below for your convenience. Thank you. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 Best, Brenda From: Brenda Brewer Date: Sunday, February 12, 2023 at 2:45 PM To: "ncsg-pc at lists.ncsg.is" , NCSG List Cc: Brenda Brewer , Daniel Gluck Subject: REMINDER: NCSG Policy Call | 13 February at 11:30 UTC Good day all, Please join the NCSG Monthly Policy call on Monday, 13 February at 11:30 UTC. Additional time zone support here. The join details are attached and noted below for your convenience. Thank you. Join Zoom Meeting: https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 Meeting ID: 988 7818 9584 Passcode: i!y7.qx+11 One tap mobile +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) Kind regards, Andrea and Brenda -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: REMINDER- NCSG Policy Call 13 February at 11-30 UTC.ics Type: text/calendar Size: 2695 bytes Desc: REMINDER- NCSG Policy Call 13 February at 11-30 UTC.ics URL: -------------- next part -------------- An embedded message was scrubbed... From: Tomslin Samme-Nlar Subject: [Ext] [NCSG-PC] Fwd: [council] Proposed Agenda | GNSO Council Meeting | Thursday, 16 February 2023 at 05:00 UTC Date: Sun, 12 Feb 2023 23:06:40 +1100 Size: 58454 URL: From compsoftnet at gmail.com Mon Feb 13 15:34:10 2023 From: compsoftnet at gmail.com (Akinremi Peter Taiwo) Date: Mon, 13 Feb 2023 14:34:10 +0100 Subject: [NCSG-PC] FW: 5-minute REMINDER: NCSG Policy Call | 13 February at 11:30 UTC In-Reply-To: <4249512B-14AA-44C7-8D86-AC742EB953FA@icann.org> References: <4249512B-14AA-44C7-8D86-AC742EB953FA@icann.org> Message-ID: My apologies for not being able to attend the meeting. Regards On Mon, Feb 13, 2023 at 12:25 PM Brenda Brewer wrote: > Good day all, > > > > Please join the NCSG Monthly Policy call on Monday, 13 February at 11:30 > UTC. Additional time zone support here > > . > > > > Join details are attached and noted below for your convenience. Thank you. > > > > Join Zoom Meeting: > https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 > > > Meeting ID: 988 7818 9584 > > Passcode: i!y7.qx+11 > > > > Best, > > Brenda > > > > *From: *Brenda Brewer > *Date: *Sunday, February 12, 2023 at 2:45 PM > *To: *"ncsg-pc at lists.ncsg.is" , NCSG List < > NCSG-DISCUSS at LISTSERV.SYR.EDU> > *Cc: *Brenda Brewer , Daniel Gluck < > daniel.gluck at icann.org> > *Subject: *REMINDER: NCSG Policy Call | 13 February at 11:30 UTC > > > > Good day all, > > > > Please join the NCSG Monthly Policy call on Monday, 13 February at 11:30 > UTC. Additional time zone support here > > . > > > > The join details are attached and noted below for your convenience. Thank > you. > > > > Join Zoom Meeting: > https://icann.zoom.us/j/98878189584?pwd=ZVpkSVVuaXVqeGRMelNEWW1LMkxQUT09 > > > Meeting ID: 988 7818 9584 > > Passcode: i!y7.qx+11 > > > > One tap mobile > > +16699006833,,98878189584#,,,,,,0#,,7740925615# US (San Jose) > > +12532158782,,98878189584#,,,,,,0#,,7740925615# US (Tacoma) > > > > Kind regards, > > Andrea and Brenda > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -- Best regards *Taiwo Peter Akinremi* ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ ------ *Policy Advisory | Data Governance and Privacy Consultant | Information Security & Cybersecurity | Certified Salesforce Administrator* *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo *Email:* compsoftnet at gmail.com, peterexecute at gmail.com ___________________________________________ -------------- next part -------------- An HTML attachment was scrubbed... URL: From brenda.brewer at icann.org Mon Feb 13 23:59:29 2023 From: brenda.brewer at icann.org (Brenda Brewer) Date: Mon, 13 Feb 2023 21:59:29 +0000 Subject: [NCSG-PC] NCSG Policy Call - attendees & replay - 13 February 2023 Message-ID: Good day all, Please find attendees and replay links for the NCSG Monthly Policy call on Monday, 13 February at 11:30 UTC. The transcript will be sent upon completion. Thank you! Kind regards, Andrea and Brenda ATTENDEES: * Members: Amin Hacha, Annett Bonuke, ASUS, Avri Doria, Benjamin Akinmoyeje, Bolutife Adisa, Bruna Martins dos Santos, Ephraim Percy Kenyanito, Frank Anati, Jahangir Hossain, Jean F. Queralt, Julf Helsingius, Ken Herman, Lena Herbst, Manju Chen, Mubashir Sargana, Muhammad Shabbir, Namra Naseer, Olivier Kouami, Pascal Bekono, Pedro de Perdig?o Lana, Rafik Dammak, Raymond Mamattah, Razoana Moslam, Rudi Daniel, Shah Rahman, Stephen Dakyi, | Apologies: Andrea Glandon, Emmanuel Vitus, Tomslin Samme-Nlar | ICANN org: Brenda Brewer, Carlos Reyes, Daniel Gluck * ZOOM Replay Link with Chat: HERE * ZOOM Audio Link with Chat: HERE -------------- next part -------------- An HTML attachment was scrubbed... URL: From manju at nii.org.tw Thu Feb 16 13:12:13 2023 From: manju at nii.org.tw (=?UTF-8?B?6Zmz5pu86Iy5IE1hbmp1IENoZW4=?=) Date: Thu, 16 Feb 2023 19:12:13 +0800 Subject: [NCSG-PC] Fwd: [GNSO-SOI-TF] Please respond - TF follow up questions In-Reply-To: <8EC9D7DA-2216-4813-BD6A-FB51381507CC@icann.org> References: <8EC9D7DA-2216-4813-BD6A-FB51381507CC@icann.org> Message-ID: Hi NCSG members, The Statement of Interest Task Force (SOI-TF) commissioned by the GNSO Council Committee for Overseeing and Implementing Continuous Improvement (CCOICI) was assigned to review the current SOI used inside of GNSO and recommend improvements if needed. The Task Force published its recommendation report last year for public comments. You can find the report here: https://itp.cdn.icann.org/en/files/generic-names-supporting-organization-council-gnso-council/gnso-statement-interest-task-force-review-soi-requirements-09-09-2022-en.pdf In the report, the TF recommends dividing the current SOI into 2 parts, namely: 1. General Statement of Interest which contains general information about a participant to understand their background and motivation for participating in GNSO activities. 2. Activity Specific Statement of Interest which is information that is provided specific to the activity a participant has requested to participate in. For example, what is their motivation for participation in that activity as well as possible impact on the individual and/or their employer of the outcomes of the process. The Task Force has reached a stalemate recently regarding the Activity Specific SOI. It is about the exemption language for when WG members are prevented from revealing specific information of who exactly they represent/are paid to participate by professional ethical obligations such as attorney-client agreement. The staff has helped draft the exemption language: https://docs.google.com/document/d/1aFuwubJUiIbXjui9mT6M9n1iSd-N_puL/edit?usp=sharing&ouid=100305727513678344340&rtpof=true&sd=true IPC is in favor of the exemption, while RySG and RrSG are strongly against, arguing that exemption will render the SOI meaningless. Other SG/Cs on the Task Force have not voiced their position regarding this issue. Now they're asked to due to the stalemate. While I'm not the NCSG representative on this Task Force (I'm the CCOICI liaison), I thought I'd bring this to your attention so we can have a position for our representative to bring back to the Task Force. I'm also attaching the most recent email from staff for the SOI-TF for your reference. Best, Manju ---------- Forwarded message --------- From: Marika Konings Date: Thu, Feb 16, 2023 at 4:31 PM Subject: [GNSO-SOI-TF] Please respond - TF follow up questions To: gnso-soi-tf at icann.org Hi All, Following up on yesterday?s conversation, here are some further details on the different suggestions with specific questions for the TF to provide your feedback on: 1. *Position on exemption language*: We?ve heard the views of the IPC, RySG and RrSG representatives in relation to the exemption language (see https://docs.google.com/document/d/1aFuwubJUiIbXjui9mT6M9n1iSd-N_puL/edit?pli=1). *Question for the ISPCP, BC, NCSG/NCUC reps*: Please share your groups view with the mailing list. Would you be in favor of keeping the exemption language as proposed in the google doc, or removing it (the part that starts with ?If professional ethical obligations prevent you?.?)? 1. *Possible SOI pilot:* During today?s SOI Task Force meeting, the staff support team suggested that before finalizing the report and recommendations, the Task Force could consider conducting a pilot in which it would ask the participants of one or two of the current PDPs (IDNs and Transfers) to complete the SOI as proposed by the SOI Task Force, including the latest exemption language. This may provide the Task Force with further insights into how the SOI would be filled out in practice and whether the exemption would be invoked by many of the participants. Although it may not address all the concerns expressed, the practical experience may provide further insights that could help move the deliberations of the TF forward. If there is support for this approach, we would like to suggest the following steps: 1. Request Manju in her capacity as CCOICI chair and liaison to the TF to communicate to the Council the remaining issue that the TF is aiming to resolve and the proposal to pilot the new SOI with the two ongoing PDPs to gather further information and insights that may help inform the TF?s deliberations. 2. If there is no objection from the Council for following this approach, staff support team to work with the Council liaisons to these PDPs to explain the pilot and request participation. As part of the pilot, respondents would also be asked to share their feedback on the new SOI as proposed. 3. TF to review the SOI entries and consider if/how the responses and feedback provided impact the TF?s view. 4. TF to finalize report for submission to CCOICI/GNSO Council. *Question for the TF*: Do you agree that conducting a pilot may be helpful in gathering further information that could help resolve the current stalemate on the exemption language? If not, do you have other suggestions for how to break the stalemate, or should the TF finalize its report and outline the different positions on this particular issue so that the CCOICI/Council can consider if/how to resolve it? 1. *Possible question to ICANN Legal * It was suggested during the meeting that input from ICANN legal may help further inform the discussion. The following question was put forward as a suggestion: ?"Is there a case where under international or local law where a lawyer or consultant is prohibited from obtaining an informed consent of their client to disclose their representation in a given GNSO effort?" However, it was pointed out that this question may be overly broad if it would be expected to cover local laws in all countries across the world. Similarly, the IPC reps have expressed previously that one concern with this approach (informed consent) is that if consent is not be provided, it would effectively exclude someone from participating. *Question to the TF*: What input could ICANN legal provide that you expect would help inform the TF?s discussion on the exemption language? *Please provide your feedback on these questions as soon as possible, but no later than Friday 24 February* so we can plan accordingly for the next meeting which is scheduled for Wednesday 1 March at 14.00 UTC. Thanks, Julie and Marika _______________________________________________ GNSO-SOI-TF mailing list GNSO-SOI-TF at icann.org https://mm.icann.org/mailman/listinfo/gnso-soi-tf _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Fri Feb 17 15:39:17 2023 From: julf at Julf.com (Johan Helsingius) Date: Fri, 17 Feb 2023 14:39:17 +0100 Subject: [NCSG-PC] NCSG representatives Message-ID: Hi all, Just wondering... Do we track the activity and attendance of the representatives we appoint to working groups, committees and task forces in any way to know if they are doing their job? Julf From Kathy at KathyKleiman.com Fri Feb 17 16:22:57 2023 From: Kathy at KathyKleiman.com (Kathy Kleiman) Date: Fri, 17 Feb 2023 09:22:57 -0500 Subject: [NCSG-PC] NCSG representatives In-Reply-To: References: Message-ID: <8ddc8976-73d4-231c-d188-bc43adb6d311@KathyKleiman.com> Hi Julf, I think this? is a great idea.? I'm been mulling over another one. /How about if we ask each of our Councilors to take responsibility for one issue on the Council agenda before the NCSG monthly PC meeting? / Each Council could/should take one issue coming up at the Council meeting, and before the NCSG PC meeting, read the documents, know the history, think about NCSG issues/concerns, and prepare for NCSG questions that might arise during our monthly PC meeting. He/she could also present that agenda item at our monthly PC meeting. If NCSG members have good questions, or concerns, in the PC meeting, then the Councilor could help find answers and raise issues/questions/concerns in the Council meetings (along with our other Councilors, of course)! Council agendas are now pretty big for one person to brief on all the topics, and with new gTLDs, WHOIS and other issues, issues coming fast, agendas will get bigger and deeper. I think it would help the NCSG, the PC and our Councilors for each Councilor to be the lead one issue on the Council agenda each month at our PC meeting. What do you think? Best and tx, Kathy On 2/17/2023 8:39 AM, Johan Helsingius wrote: > Hi all, > > Just wondering... > > Do we track the activity and attendance of the representatives > we appoint to working groups, committees and task forces in any way > to know if they are doing their job? > > ????Julf > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Fri Feb 17 16:44:11 2023 From: julf at Julf.com (Johan Helsingius) Date: Fri, 17 Feb 2023 15:44:11 +0100 Subject: [NCSG-PC] NCSG representatives In-Reply-To: <8ddc8976-73d4-231c-d188-bc43adb6d311@KathyKleiman.com> References: <8ddc8976-73d4-231c-d188-bc43adb6d311@KathyKleiman.com> Message-ID: Hi Kathy, > Each Council could/should take one issue coming up at the Council > meeting, and before the NCSG PC meeting, read the documents, know the > history, think about NCSG issues/concerns, and prepare for NCSG > questions that might arise during our monthly PC meeting. He/she could > also present that agenda item at our monthly PC meeting. I really like that idea! Julf From julf at Julf.com Fri Feb 17 16:48:38 2023 From: julf at Julf.com (Johan Helsingius) Date: Fri, 17 Feb 2023 15:48:38 +0100 Subject: [NCSG-PC] ICANN76 Board Questions/Topics In-Reply-To: <4BA8915F-74D6-476F-A26F-D08019A7616A@icann.org> References: <4BA8915F-74D6-476F-A26F-D08019A7616A@icann.org> Message-ID: Dear NCSG, It is time to decide what we want to take up in our meeting with the Board in Cancun. The Board has asked the SO/AC:s one question: "The ICANN Board would like to explore how to combine the efficiencies of an agile approach to problem solving, like the Council?s small teams, with the need for accountability and transparency, to make progress on policy conversations. When would such an approach be most appropriate and how can we ensure that it does not circumvent required steps in a policy development process?" What are our thoughts? As to our questions to the board, here are our questions from the previous meeting (as a reminder): - What is the Board?s take on the phenomenon of ICANN recycling veterans for leadership positions. Does the Board think it?s beneficial for the community to have the usual suspects rotating between leadership roles of different stakeholder groups? How do we fix this if we agree this is a problem? How does the Board imagine its role in assisting the community to recruit more new blood? - Is there a possibility of rebalancing the NomCom? - What efforts are channeled to keep the people in the community from volunteer fatigue? Julf From bruna.mrtns at gmail.com Fri Feb 17 16:53:48 2023 From: bruna.mrtns at gmail.com (Bruna Martins dos Santos) Date: Fri, 17 Feb 2023 15:53:48 +0100 Subject: [NCSG-PC] [NCSG-EC] ICANN76 Board Questions/Topics In-Reply-To: References: <4BA8915F-74D6-476F-A26F-D08019A7616A@icann.org> Message-ID: Heya, Julf, I'm not sure whether we had another meeting with the board since I left the chair position but the questions we asked at ICANN75 were the following (a bit different than the ones you mentioned): PDPs Effectiveness and Volunteer fatigue 1. NCSG would like to discuss Board Approval, implementation by ICANN org and delays of several PDPs - something we have already discussed with you in previous occasions. If we look at processes such as the EPDP related ones I think we can find a good example due to the fact that even despite the fact that the board didn't yet approve phase 2 recommendation, which were submitted in 2020, there is talk about the design paper of SSAD light. And in the past years, I guess we started gathering more examples of where the development process drags on for far too long and the implementation becomes the place de facto to redo policy recommendations. ? So NCSG would like to request the board for comments about the current speed or even how do you plan to work together with GNSO and its groups on possible improvements to the PDPs timeline and so on. What efforts are channeled to keep the people in the community from volunteer fatigue? Whois Disclosure System 1. The recently published Whois Disclosure System design paper mentioned a risk that the system might not provide actionable data for use to answer questions raised by the SSAD ODA and this makes us a little concerned about the EPDP recommendations. The direction this work is going seems to point towards the intention to throw away the EPDP recommendations related to SSAD. I'll like to know what the board thinks about this concern. NomCom 1. NCSG has been talking for a long time about the lack of proper representation at the NomCom, the current state of things is that this part of the community only holds one seat at the group - currently held by NCUC - and we trust this configuration is not really representative of the diversity of stakeholders within GNSO or even proportional if we consider that other SGs hold more than just one seat. Therefore we have a very simple question: is there a possibility of rebalancing the NomCom? Extra one 1. We recently submitted a letter to the board with a CCWP-HR Human Rights Impact Assessment for ICANN?s System for Standardized Access/Disclosure (SSAD) and Operational Design Assessment (ODA) Recommendations. And in light of that we were wondering that the last ORG wide HRIA was done in 2019 so we have a few questions: what's the stake of recommendation implementation ? Is there going to be another one ? If so, when ? Best, Bruna On Fri, Feb 17, 2023 at 3:48 PM Johan Helsingius via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Dear NCSG, > > It is time to decide what we want to take up in our meeting with the > Board in Cancun. The Board has asked the SO/AC:s one question: > > "The ICANN Board would like to explore how to combine the efficiencies > of an agile approach to problem solving, like the Council?s small teams, > with the need for accountability and transparency, to make progress on > policy conversations. When would such an approach be most appropriate > and how can we ensure that it does not circumvent required steps in a > policy development process?" > > What are our thoughts? > > As to our questions to the board, here are our questions from the > previous meeting (as a reminder): > > - What is the Board?s take on the phenomenon of ICANN recycling veterans > for leadership positions. Does the Board think it?s beneficial for the > community to have the usual suspects rotating between leadership roles > of different stakeholder groups? How do we fix this if we agree this > is a problem? How does the Board imagine its role in assisting the > community to recruit more new blood? > > - Is there a possibility of rebalancing the NomCom? > > - What efforts are channeled to keep the people in the community from > volunteer fatigue? > > Julf > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -- *Bruna Martins dos Santos * German Chancellor Fellow 21' (Bundeskanzler-Stipendiatin) | Alexander von Humboldt Foundation Member | Coaliz?o Direitos na Rede Co-Coordinator | Internet Governance Caucus Twitter: @boomartins // Skype: bruna.martinsantos Email: bruna.mrtns at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Fri Feb 17 17:02:51 2023 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sat, 18 Feb 2023 00:02:51 +0900 Subject: [NCSG-PC] NCSG representatives In-Reply-To: References: Message-ID: Hi Julf, There is a page listing NCSG representatives to working groups but it seems not to have been updated for a while https://community.icann.org/pages/viewpage.action?pageId=90769701. That can be fixed easily by going through every active GNSO working groups list and check list of representatives. > know if they are doing their job? I have a little bit of an issue with this phrasing as it might imply that representatives are not doing their work but I want to assume that is not the case. I assume NCSG calls are good timing to share updates in particular if there is a related topic in the council meeting agenda or adding an agenda item of NCSG call for policy updates. It is also good to share updates to the mailing list as it can be easy for many to read written updates. Best, Rafik Le ven. 17 f?vr. 2023 ? 22:39, Johan Helsingius a ?crit : > Hi all, > > Just wondering... > > Do we track the activity and attendance of the representatives > we appoint to working groups, committees and task forces in any way > to know if they are doing their job? > > Julf > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rafik.dammak at gmail.com Fri Feb 17 17:12:12 2023 From: rafik.dammak at gmail.com (Rafik Dammak) Date: Sat, 18 Feb 2023 00:12:12 +0900 Subject: [NCSG-PC] ICANN76 Board Questions/Topics In-Reply-To: References: <4BA8915F-74D6-476F-A26F-D08019A7616A@icann.org> Message-ID: Hi Julf, I have a feeling of deja-vu as it seems like rehashing the idea of Multistakeholder model effectiveness that was launched in the Barcelona meeting. I have a concern about appropriating the term agile approach which comes from the software engineering space and it is related to a different context than ICANN. It looks like agile is translated as bypassing processes or undermining in practice the role of GNSO or weakening consensus-based approach for sake of getting quick results. GNSO council is delegating a lot to small teams and there are some concerns that can disengage councillors from participating actively in all discussions and make amendments to small team deliverables more challenging. The GNSO council is continuously having this topic of policy process improvements and I don't really believe that is the role of the ICANN board to be involved. Best, Rafik Le ven. 17 f?vr. 2023 ? 23:48, Johan Helsingius a ?crit : > Dear NCSG, > > It is time to decide what we want to take up in our meeting with the > Board in Cancun. The Board has asked the SO/AC:s one question: > > "The ICANN Board would like to explore how to combine the efficiencies > of an agile approach to problem solving, like the Council?s small teams, > with the need for accountability and transparency, to make progress on > policy conversations. When would such an approach be most appropriate > and how can we ensure that it does not circumvent required steps in a > policy development process?" > > What are our thoughts? > > As to our questions to the board, here are our questions from the > previous meeting (as a reminder): > > - What is the Board?s take on the phenomenon of ICANN recycling veterans > for leadership positions. Does the Board think it?s beneficial for the > community to have the usual suspects rotating between leadership roles > of different stakeholder groups? How do we fix this if we agree this > is a problem? How does the Board imagine its role in assisting the > community to recruit more new blood? > > - Is there a possibility of rebalancing the NomCom? > > - What efforts are channeled to keep the people in the community from > volunteer fatigue? > > Julf > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Fri Feb 17 18:21:20 2023 From: julf at Julf.com (Johan Helsingius) Date: Fri, 17 Feb 2023 17:21:20 +0100 Subject: [NCSG-PC] NCSG representatives In-Reply-To: References:

Message-ID: <27a60850-76b3-18dc-6576-110fc78f8e44@Julf.com> Hi Rafik, > There is a page listing NCSG representatives to working groups but it > seems not to have?been?updated for a while Thanks! > That can be fixed easily by going through? every active GNSO working > groups list and check list of representatives. Indeed. I am in the process of doing that right now. > >? know if they are doing their job? > I have a little bit of an issue with this phrasing as it might imply > that representatives are not doing their work but I want to assume that > is not the case. I get your point, I might have sounded a tad too suspicious/accusatory. More a case of "trust but verify". Julf From julf at Julf.com Fri Feb 17 18:28:19 2023 From: julf at Julf.com (Johan Helsingius) Date: Fri, 17 Feb 2023 17:28:19 +0100 Subject: [NCSG-PC] ICANN76 Board Questions/Topics In-Reply-To: References: <4BA8915F-74D6-476F-A26F-D08019A7616A@icann.org> Message-ID: Hi again Rafik, > It looks like agile is translated as bypassing processes or undermining > in practice the role of GNSO or weakening consensus-based approach for > sake of getting quick results. Indeed. And just like in software development, it carries a connotation of "surely you can't be one of those bureaucratical stick-to-the-procedures dinosaurs who stand in the way of solving problems". > The GNSO council is continuously > having this topic of policy process improvements and I don't really > believe that is the role of the ICANN board to be involved. Indeed, but it is soooo easy to give in to the constant "haven't you gotten this solved yet?" pressure. Julf From mesumbeslin at gmail.com Fri Feb 17 21:34:08 2023 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sat, 18 Feb 2023 06:34:08 +1100 Subject: [NCSG-PC] NCSG representatives In-Reply-To: References:

Message-ID: Hi all, I have now updated the page with active groups and our reps. https://community.icann.org/pages/viewpage.action?pageId=90769701 Warmly, Tomslin @LinkedIn: https://www.linkedin.com/in/tomslin/ On Sat, 18 Feb 2023 at 02:03, Rafik Dammak wrote: > Hi Julf, > > There is a page listing NCSG representatives to working groups but it > seems not to have been updated for a while > https://community.icann.org/pages/viewpage.action?pageId=90769701. That > can be fixed easily by going through every active GNSO working groups list > and check list of representatives. > > know if they are doing their job? > I have a little bit of an issue with this phrasing as it might imply that > representatives are not doing their work but I want to assume that is not > the case. > I assume NCSG calls are good timing to share updates in particular if > there is a related topic in the council meeting agenda or adding an > agenda item of NCSG call for policy updates. It is also good to share > updates to the mailing list as it can be easy for many to read written > updates. > > Best, > > Rafik > > Le ven. 17 f?vr. 2023 ? 22:39, Johan Helsingius a ?crit : > >> Hi all, >> >> Just wondering... >> >> Do we track the activity and attendance of the representatives >> we appoint to working groups, committees and task forces in any way >> to know if they are doing their job? >> >> Julf >> >> _______________________________________________ >> NCSG-PC mailing list >> NCSG-PC at lists.ncsg.is >> https://lists.ncsg.is/mailman/listinfo/ncsg-pc >> > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Fri Feb 17 21:43:07 2023 From: julf at Julf.com (Johan Helsingius) Date: Fri, 17 Feb 2023 20:43:07 +0100 Subject: [NCSG-PC] NCSG representatives In-Reply-To: References:

Message-ID: <85e4f95c-92c6-53a1-54e3-80b4f44acc5e@Julf.com> Great! Thanks! Julf On 17/02/2023 20:34, Tomslin Samme-Nlar wrote: > Hi all, > > I have now updated the page with active groups and our reps. > https://community.icann.org/pages/viewpage.action?pageId=90769701 > > > Warmly, > Tomslin > @LinkedIn: https://www.linkedin.com/in/tomslin/ > > > > On Sat, 18 Feb 2023 at 02:03, Rafik Dammak > wrote: > > Hi Julf, > > There is a page listing NCSG representatives to working groups but > it seems not to have?been?updated for a while > https://community.icann.org/pages/viewpage.action?pageId=90769701 > .? That can be fixed easily by going through? every active GNSO working groups list and check list of representatives. > >? know if they are doing their job? > I have a little bit of an issue with this phrasing as it might imply > that representatives are not doing their work but I want to assume > that is not the case. > I assume NCSG calls are good timing to share updates in particular > if there is a related topic in the council meeting agenda or adding > an agenda?item of NCSG call for policy updates. It is also good to > share updates to the mailing list as it can be easy for many to read > written updates. > > Best, > > Rafik > > Le?ven. 17 f?vr. 2023 ??22:39, Johan Helsingius > a ?crit?: > > Hi all, > > Just wondering... > > Do we track the activity and attendance of the representatives > we appoint to working groups, committees and task forces in any way > to know if they are doing their job? > > ? ? ? ? Julf > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > > _______________________________________________ > NCSG-PC mailing list > NCSG-PC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-pc > > From julf at Julf.com Sat Feb 18 20:05:50 2023 From: julf at Julf.com (Johan Helsingius) Date: Sat, 18 Feb 2023 19:05:50 +0100 Subject: [NCSG-PC] ICANN76 Stakeholders/Board sessions In-Reply-To: References: Message-ID: <051f0598-756e-82a3-691c-d7936ec2cfe5@Julf.com> Hi, I note that Paul is specifically asking for someone from Non-commercial (and Contracted Parties). I guess it has to be a council member... Julf -------- Forwarded Message -------- Subject: Re: [council] [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Date: Sat, 18 Feb 2023 12:13:53 +0000 From: Paul McGrady via council Reply-To: Paul McGrady To: Mark W. Datysgeld , Steve Chan , Sebastien at registry.godaddy , COUNCIL at GNSO.ICANN.ORG , GNSO-Chairs , gnso-secs at icann.org *Disclaimers:* *Subject to a final greenlight from Council Leadership to proceed.* *Written early in the morning on a Saturday ? forgive typos*. Thanks Mark! All, it would be great to have 1 or 2 more so that we are sure to get a full range of eyes on this, especially helpful if they were Non-commercial and Contracted Parties voices to round us out.? Special request that Jeff join the team as this is a question from the GAC.? Also, if you don?t have time to participate on the bespoke small team but have thoughts on Tripti?s question, please do put your comments into the document (diamonds in the rough welcome ? the team can polish later). Best, Paul *From:* Mark W. Datysgeld *Sent:* Friday, February 17, 2023 11:22 PM *To:* Paul McGrady ; Steve Chan ; Sebastien at registry.godaddy; COUNCIL at GNSO.ICANN.ORG; GNSO-Chairs ; gnso-secs at icann.org *Subject:* Re: [council] [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Since I have been been banging the drum about Council-Board interaction, I think I should step up for this team. Lead us to greatness, Paul. --- Mark W. Datysgeld Director at Governance Primer ICANN GNSO Councilor ------------------------------------------------------------------------ *From:* Paul McGrady via council > *Sent:* Friday, February 17, 2023 18:37 *To:* Steve Chan; Sebastien at registry.godaddy ; COUNCIL at GNSO.ICANN.ORG ; GNSO-Chairs; gnso-secs at icann.org *Subject:* Re: [council] [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Thanks Steve!? The document looks great.? I?ll await the final greenlight from Seb that the bespoke small team is the final plan and then the resulting flood of volunteers.? Once we are at that point, I hope Staff will send around a Doodle to help us get our kickoff meeting scheduled. Best, Paul *From:* Steve Chan > *Sent:* Friday, February 17, 2023 1:14 PM *To:* Sebastien at registry.godaddy ; Paul McGrady >; COUNCIL at GNSO.ICANN.ORG ; GNSO-Chairs >; gnso-secs at icann.org *Subject:* Re: [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Dear Councilors, Please find a Google doc created for this exercise. Permissions are currently set to allow for comments, but once we know who will be taking part in the effort besides Paul, we will provide Editor rights: https://docs.google.com/document/d/1igtbNSUBMc3cIFlR7-zTyg5epNwfm7ImkxaP_K-8Uw8/edit?usp=sharing Note that in the Google document, we have also included the potential questions to the ICANN Board as by shared by Sebastien. We are assuming that similar planning will be needed once the topics are agreed to by the Council. It sounds like the Councilors will organize themselves, but if you need any assistance from support staff, just let us know. Best, Steve *From: *Gnso-chairs > on behalf of Sebastien--- via Gnso-chairs > *Reply-To: *"Sebastien at registry.godaddy " > *Date: *Friday, February 17, 2023 at 1:48 AM *To: *Paul McGrady >, "COUNCIL at GNSO.ICANN.ORG " >, GNSO-Chairs >, "gnso-secs at icann.org " > *Subject: *Re: [gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Hi Paul, Thank you for raising your hand for this, it is much appreciated. I think that in the past we would have taken this to the mailing list, but I must admit it is not my favorite medium: I tend to get quickly lost in the sub-threads (I am probably showing my age). The current thinking should lead us to a small team setup, but given the short timelines I wouldn?t want to waste any of it haggling over how to form it. Could I suggest that: 1. We initiate immediately a bespoke small team headed by Paul McGrady + eventually a single co-lead from the other house should anyone volunteer. 2. Membership to open to all Councillors. Should any Councillor need external input, he/she can seek it but remains the small team sole member. 3. Staff to create a bespoke Google Doc with the Board?s questions. 4. The small team takes it from there with the aim of gathering our thoughts by March 3rd. Council colleagues: Thoughts? Comments? Kindly, *Sebastien Ducos* GoDaddy Registry | Senior Client Services Manager signature_1287335570 +33612284445 France & Australia sebastien at registry.godaddy *From: *Paul McGrady > *Date: *Thursday, 16 February 2023 at 4:32 pm *To: *Sebastien Ducos >, COUNCIL at GNSO.ICANN.ORG >, GNSO-Chairs >, gnso-secs at icann.org

> *Subject: *RE: PLEASE READ - ICANN76 Stakeholders/Board sessions You don't often get email from paul at elstermcgrady.com . Learn why this is important [aka.ms] Caution:This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad at . Thanks Seb!? I think our questions to the Board proposed below look great and touch on important concerns. As for Tripti?s question, what will be our mechanism to respond? Should we (1) start a shared document that folks can contribute to, (2) do we want to run a short-lived small team to develop a draft for the broader Council to review (I?m happy to lead that effort if you like), (3) do we send ideas to the mailing list and have staff compile them and then we all edit the compilation, (4) something else? Also, we need to have milestone deadlines so that we aren?t scrambling and doing this on airplanes to Cancun.? Thanks! Best, Paul *From:* council > *On Behalf Of *Sebastien--- via council *Sent:* Thursday, February 16, 2023 9:01 AM *To:* COUNCIL at GNSO.ICANN.ORG ; GNSO-Chairs >; gnso-secs at icann.org *Subject:* Re: [council] PLEASE READ - ICANN76 Stakeholders/Board sessions Dear Council Colleagues, A short note to correct my previous email: While the Board would like us to prepare our response to their question ahead of our meeting, the March 1^st deadline if for us to submit our questions to them. Here are some questions already floated: * *Ensuring Board and ICANN org input to PDP processes* How do we minimize the need for an ODP and minimize its impact when it is needed? What further information or details should the GNSO integrate into a PDP Final Report to ensure it delivers Board-ready recommendations? * *Getting to the next round of new gTLDs* What in the Boards view would be required of the GNSO Council and Community to secure a Next Round Launch Date by the 2023 AGM? * *WHOIS Disclosure System* The Council?s recommendations were delivered 3 months ago which corresponds to ICANN Org?s ramp up requirement; has the development been initiated? What assistance can the Council and its small team offer to ensure initial timelines are met? Kindly, *Sebastien Ducos* GoDaddy Registry | Senior Client Services Manager signature_3093328915 +33612284445 France & Australia sebastien at registry.godaddy *From: *council > on behalf of Sebastien--- via council > *Date: *Thursday, 16 February 2023 at 2:00 pm *To: *COUNCIL at GNSO.ICANN.ORG >, GNSO-Chairs >, gnso-secs at icann.org

> *Subject: *[council] FW: PLEASE READ - ICANN76 Stakeholders/Board sessions Caution:This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad at . Dear Council Colleagues, Please find below a letter from Tripti Sinha on behalf of the Board regarding our session in Cancun. In particular the Board would like for us to respond to the following by March 1^st : *The final SupPro report assigns resolution of many, potentially complex issues to the Implementation Review Team (IRT).? IRTs can - and sometimes have - become bottlenecks, for example, in connection with efforts to relitigate policy outcomes or where there are gaps in the policy being implemented.? What concrete steps can the board, org, or community (or all 3 collectively) take to improve the IRT process?? Please be as concrete as possible.* Please note that as per our discussion with Becky today, I also expect we will receive a list of clarifying questions on the SubPro Recommendations themselves. Kindly, *Sebastien Ducos* GoDaddy Registry | Senior Client Services Manager signature_1469584128 +33612284445 France & Australia sebastien at registry.godaddy *From: *Gnso-chairs > on behalf of Vinciane Koenigsfeld via Gnso-chairs > *Date: *Tuesday, 14 February 2023 at 7:23 pm *To: *gnso-chairs at icann.org

> *Cc: *becky.burr at board.icann.org >, matthew.shears at board.icann.org > *Subject: *[gnso-chairs] PLEASE READ - ICANN76 Stakeholders/Board sessions Caution:This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad at . /Sent on behalf of Tripti Sinha, Chair, ICANN Board of Directors/ // Dear Generic Names Supporting OrganizationCouncil Leaders, **Please reply no later than Wednesday 1 March 2023** The Board and I very much look forward to welcoming and meeting with you during ICANN76 in Canc?n, between 11-16 March. It is with great pleasure and excitement that we are finally going to Mexic?, after having had to cancel the in-person component of both ICANN67 and ICANN70. We are grateful to our friends and stakeholders in Latin America for their patience and understanding in the process, and delighted to say?Canc?n aqu? vamos! (Canc?n, here we are!). The last three years have certainly proven eventful for all of us, but in unison with ICANN organization, we are moredetermined than ever to work closely with you to make 2023 and the many years after that, productive and successful. This time in particular, the Board proposes a slight change in the approach to our bilateral sessions. We understood that there was an appetite for questions more tailored to each stakeholder group?s needs. Therefore, we will not be sending the same question from the Board to all of you. Having said this, to maintain our commitment to transparency, all of the questions the Board to sends to each group will be published in the Community Digest. The second improvement that we are putting in place starting at ICANN76, is to provide you with a summary of what we heard from you during these bilateral sessions. This summary will be in two forms: 1.A blog highlighting key take aways from ICANN76 (and every ICANN meeting after that) 2.Summaries of bilateral sessions will be included in the?Policy Outcomes Report we publish after each ICANN meeting These are only initial steps, and we will continue to discuss with you ways improve the way we interact moving forward. In the meantime, please find herewith the questions we would like to ask_your_Group ahead of our joint session in Canc?n: *The final SupPro report assigns resolution of many, potentially complex issues to the Implementation Review Team (IRT).? IRTs can - and sometimes have - become bottlenecks, for example, in connection with efforts to relitigate policy outcomes or where there are gaps in the policy being implemented.? What concrete steps can the board, org, or community (or all 3 collectively) take to improve the IRT process?? Please be as concrete as possible.* ** We look forward to hearing your thoughts on this soon. We would be grateful if you could send to Board Operations (board-ops-team at icann.org ) ?the questions you would like the Board to address during our face-to-face meetings.?Given the finite time available for these meetings, please list your questions in order of priority.We would also appreciate getting your questions no later than *_Wednesday 1 March, 2023_*. We thank you in?advance for your time on this matter. Best regards, Tripti Sinha Chair, ICANN Board of Directors -------------- next part -------------- _______________________________________________ council mailing list council at gnso.icann.org https://mm.icann.org/mailman/listinfo/council _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. From mesumbeslin at gmail.com Fri Feb 24 07:51:10 2023 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Fri, 24 Feb 2023 16:51:10 +1100 Subject: [NCSG-PC] NCSG PC meeting in Cancun Message-ID: Hi all, I am developing an agenda for our meeting. Is there any topics you would like to see discussed? Warmly, Tomslin -------------- next part -------------- An HTML attachment was scrubbed... URL: From mesumbeslin at gmail.com Sat Feb 25 22:06:47 2023 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Sun, 26 Feb 2023 07:06:47 +1100 Subject: [NCSG-PC] NCSG PC meeting in Cancun In-Reply-To: References: Message-ID: Hi again, Thought I should share the Google doc Andrea had created for drafting the PC meeting agenda NCSG Policy: https://docs.google.com/document/d/1bmYVSjk-Qpsw9W98beS7cx9kQ805KvaqMEt4SR_dYpE/edit?usp=sharing . Please add/modify. Warmly, Tomslin On Fri, 24 Feb 2023 at 16:51, Tomslin Samme-Nlar wrote: > Hi all, > > I am developing an agenda for our meeting. Is there any topics you would > like to see discussed? > > Warmly, > Tomslin > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julf at Julf.com Tue Feb 28 10:34:13 2023 From: julf at Julf.com (Johan Helsingius) Date: Tue, 28 Feb 2023 09:34:13 +0100 Subject: [NCSG-PC] Fwd: Board Seat 14 Nomination Procedures and Timeline In-Reply-To: References: Message-ID: First sent to EC, but PC needs to be involved too. So - CSG won't support Matthew. Julf -------- Forwarded Message -------- Subject: Board Seat 14 Nomination Procedures and Timeline Date: Mon, 27 Feb 2023 18:38:30 +0000 From: Lori Schulman To: Johan Helsingius CC: Cole, Mason (Perkins Coie) , Tim Smith , csg-excomm at ICANN.org , Mohr, Susan , 'Brian King' , philippe.fouquart at orange.com Dear Julf, Thank you for the very productive call.? This is the first of 2 emails that I will send confirming our conversation.? The second will focus on the ?building bridges? aspect of our conversation, NCPH common priorities and a proposal for a virtual intersessional sometime between April and July of this year.? Below, is the link to the agreed upon Board selection process.? This is the formalized document from 2018.? Also, below is the timeline for Board selection. We did not do background checks on the candidates.? I think it makes more sense to agree on the nominee and then ask ICANN for the check as it will save time and money. The 2018 procedures do not envision alternating nominating responsibilities for each side of our house.? However, my understanding is that an informal agreement was made in 2020 to renew Matthew Shears based on the agreement that the CSG would be responsible for the 2023 nominee.? This is because, initially, there was no consensus on renewing Matthew.? CSG agreed to the renewal in order to give Matthew a change to improve and grow even if we had reservations about his performance.? ??I was not on the CSG ExComm in 2020 so I do not have any direct knowledge or emails to this effect.? However, I do remember the issue being discussed with the IPC membership at the time.? We agreed that to keep in peace in the house, we would give Matthew a second chance. Matthew made promises that he did not fulfill and, to his credit, admitted so in our interview process this year.? CSG does not support Matthew for renewal in 2023. CSG offers Mark Datysgeld and Damon Ashcraft as an alternate slate of candidates for Board Seat 14.? CSG supports both candidates strongly as they are proven ICANN leaders and consensus builders.? Both bring considerable skills to the table.? Mark is a young entrepreneur, sitting GNSO counselor and deeply committed to GNSO policy work.? Mark represents the population that ICANN is trying to reach to ensure its future.? Damon has had leadership positions on NomCom and has received outstanding 360 reviews.? Damon is a natural leader, consensus builder and consistent ICANN volunteer.? He is committed to civil society engagement through his community volunteering, numerous board positions and pro bono work.? Both are excellent options.? We wanted NCSG to have a fair choice.? We believe that we are offering one.? We do not wish to reach stalemate as that does not serve either side well. As a point of information, CSG interviewed 5 candidates and asked all of them the same questions.? A copy of those questions is attached.? The CSG ExCom met on 2 calls to discuss rankings and overall results and came to our conclusion as to the proposed slate.? Once that process was completed, I reached out to you as Chair of CSG. The candidates that were in considered in alphabetical order were: Damon Ashcraft Mark Datysgeld Heather Forrest (withdrawn) Matthew Shears Christine Willett In order to improve the process moving forward CSG proposes amending the 2018 procedure to include a review and nominating process that makes more sense for our mutual interests.? Below is a framework which we would like to implement for 2026 and moving forward. ??It provides for a review of the sitting Board 14 member and more balanced process for nominations which should minimize stalemate. _Proposal for selecting a Seat 14 Board Candidate in 2026 and Beyond_ __ This proposal would serve as an Amendment to the 2018 agreement referenced here: https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-7-ncph-election-procedures-seat-14-24oct19-en.pdf and provide a more fair way of picking candidates including reviewing the performance of the incumbent.? We happy to discuss with NCSG as part of an intersessional __ * Align on selection and performance criteria for the Seat 14 Board position. o Selection criteria could include background, ICANN experience, Board experience, etc. o Performance criteria could include regular engagement with the CSG and NCSG, understanding of CSG and NCSG priorities, ability to advance these priorities while also considering the overall priorities of the Board, etc. * Conduct annual reviews of the current Seat 14 Board member?s performance ? provide feedback to the Board member.?? The NomCom model for performance reviews could be considered or a modification thereof. * Meet 3 months in advance of 3-year Seat 14 election to reach majority/consensus on whether the current Seat 14 Board member?s performance supports re-election to a 2^nd or 3^rd term (what is the preferred standard ? majority or consensus or something else?) o When the /consensus/majority/ conclusion is that the current Seat 14 Board member /is performing well /based on objective criteria, the current member will be the candidate for another term unless they are termed out. o When the /consensus/majority/ conclusion is that the current Seat 14 Board member is /not performing/ and an alternative should be selected, then selection of alternative candidates will rotate between the CSG and NCSG.? All alternative candidates proposed will be interviewed by both the CSG and NCSG ex comm.? The CSG and NCSG will nominate a final candidate based on a consensus/majority outcome. * When Board members are termed out, the selection of proposed candidates by either the CSG or NCSG will depend on which group last selected a candidate. * The Secretariat will keep a record of performance review outcomes and the candidate selection ?turn? of the CSG and NCSG. With kind regards, Lori S. Schulman Senior Director, Internet Policy *International Trademark Association (INTA)* +1-202-704-0408, Skype:? LSSchulman lschulman at inta.org , www.inta.org *From:*Nathalie Peregrine *Sent:* Thursday, November 3, 2022 6:17 PM *To:* Johan Helsingius ; Benjamin Akinmoyeje ; Raoul Plommer ; philippe.fouquart at orange.com; Lori Schulman ; Cole, Mason (Perkins Coie) *Cc:* gnso-secs at icann.org; Brenda Brewer ; Andrea Glandon *Subject:* Board Seat 14 timeline Dear Non Contracted Party House Chairs, As per theICANN Bylaws[icann.org] , Section 7.8.d. ?At least six months before the date specified for the commencement of the term as specified in _Section 7.8(a)(iv)_?through _Section 7.8(a)(vi)_?above, any?Supporting Organization?or the At-Large Community entitled to nominate a Director for a Seat with a term beginning that year shall give the?EC?Administration (with a copy to the Secretary?and the Decisional Participants) written notice of its nomination of Directors for seats with terms beginning at the conclusion of the annual meeting, and the?EC?Administration shall promptly provide the Secretary (with a copy to the Decisional Participants) with written notice of the designation of those Directors. All such notices shall be posted promptly to the Website.? With that in mind, staff has prepared a tentative Board Seat 14 election timeline below in accordance with the GNSO Operating Procedures 2.4.2. Please note this has been produced taking into account maximum duration possible for each time slot.*Election results need therefore to be communicated _before the _**_29^th March 2023 for the results to be confirmed during the April 2023 GNSO Council meeting_. * *Board seat 14 timeline*** *Deadline:*** *Not Later Than:*** *Activity Commences:*** *Maximum Duration:*** 26 December 2022 T ? 4 Months Call for Nominations 1 Month 26 January 2023 T ? 3 Months Candidate Interviews 2 Weeks 15 February 2023 T ? 10 Weeks First Round of Voting 2 Weeks 1 March 2023 T ? 8 Weeks Second Round of Voting (if needed) 2 Weeks 15 March 2023 T ? 6 Weeks Third Round of Voting (if needed) 2 Weeks 29 March 2023 T ? 4 Weeks GNSO Secretariat Reports Election Results 3 Days 20 April 2023 Next Council Meeting Confirmation of Election 3 Days 26 April 2023 T _GNSO Chair Notifies Empowered Community Administration with a copy to the Secretary of the election results as prescribed by Section 7.25 of the ICANN Bylaw s. _ 3 Days -------------- next part -------------- A non-text attachment was scrubbed... Name: Board Seat 14 Qs.docx Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document Size: 15077 bytes Desc: not available URL: From julf at Julf.com Tue Feb 28 10:35:01 2023 From: julf at Julf.com (Johan Helsingius) Date: Tue, 28 Feb 2023 09:35:01 +0100 Subject: [NCSG-PC] Fwd: Concerning the Board seat In-Reply-To: References: Message-ID: <265a0893-c0bf-54b2-ace0-ae8cf9b91fd3@Julf.com> -------- Forwarded Message -------- Subject: Concerning the Board seat Date: Tue, 28 Feb 2023 02:32:22 -0300 From: Mark W. Datysgeld To: Johan Helsingius Julf, hope you are doing well. Briefly: given the result of the discussions carried out within the CSG regarding the Board seat, I'd like to make myself available to talk and answer questions from both the NCSG excomm and the group's general membership. I don't have things to hide and I've been fighting for greater unity between commercials and non-commercials for a long time now, so hearing more of the group's ideas would be helpful anyway. Let me know. Best, --- Mark W. Datysgeld Director at Governance Primer ICANN GNSO Councilor From julf at Julf.com Tue Feb 28 10:35:49 2023 From: julf at Julf.com (Johan Helsingius) Date: Tue, 28 Feb 2023 09:35:49 +0100 Subject: [NCSG-PC] Fwd: Building Bridges in NCPH/Common Goals/Virtual Intersessional In-Reply-To: References: Message-ID: <20fde0d6-56aa-fd8c-0b9c-93a7c8eb12b8@Julf.com> -------- Forwarded Message -------- Subject: Building Bridges in NCPH/Common Goals/Virtual Intersessional Date: Mon, 27 Feb 2023 19:32:31 +0000 From: Lori Schulman To: Johan Helsingius CC: Cole, Mason (Perkins Coie) , Tim Smith , csg-excomm at ICANN.org , Mohr, Susan , 'Brian King' , philippe.fouquart at orange.com Dear Julf, As promised, here is Part II of my follow up email. ?CSG is very pleased to engage with NCSG on building bridges within our house.? It has been too long since we have sat down as a united group in common interest. To that end, we propose several steps. 1. Provide more clarity and predictability on the filling of Board Seat 14.? This issue was addressed in my first email which is attached for your reference. We shouldn?t have to rely on memory and undocumented understandings. 2. Our ExComms to meet and agree on common goals in order properly guide our Board member(s). 3. Work together on common policy issues when feasible. 4. Plan an intersessional to discuss the NCPH in general and how, given that we may have alignment on some fundamental issues, to form an agenda and action plan for progress. We briefly discussed 4 areas in which may have common ground in terms of providing guidance to our Board member and input on policy processes: 1. Implementation of Policy Recommendations (unclog the pipes) 2. Implement a well-defined holistic review including examining the GNSO framework and whether it makes sense 3. Implementing reasonable and well documented DNS Abuse mitigation procedures 4. Addressing volunteer workload and burnout We welcome more thoughts and suggestions.?? This is a transitional time at ICANN and we look forward to working together to make sensible progress and ensure that our concerns are heard and acted upon. We look forward to hearing from you. With kind regards, Lori S. Schulman Senior Director, Internet Policy *International Trademark Association (INTA)* +1-202-704-0408, Skype:? LSSchulman lschulman at inta.org , www.inta.org -------------- next part -------------- An embedded message was scrubbed... From: Lori Schulman via Csg-excomm Subject: [Csg-excomm] Board Seat 14 Nomination Procedures and Timeline Date: Mon, 27 Feb 2023 18:38:30 +0000 Size: 87352 URL: From julf at Julf.com Tue Feb 28 18:52:17 2023 From: julf at Julf.com (Johan Helsingius) Date: Tue, 28 Feb 2023 17:52:17 +0100 Subject: [NCSG-PC] Questions for the Board - due tomorrow (march 1) Message-ID: <9cdd09c2-c6e1-52a0-04c8-07dd8efe9de0@Julf.com> Title says it all... Julf From julf at Julf.com Tue Feb 28 22:34:33 2023 From: julf at Julf.com (Johan Helsingius) Date: Tue, 28 Feb 2023 21:34:33 +0100 Subject: [NCSG-PC] Fwd: Request for Early Input - GNSO Transfer Policy Review PDP In-Reply-To: References: Message-ID: <961a1da2-bb33-b18f-bb8f-a0bf2f80152f@Julf.com> -------- Forwarded Message -------- Subject: Request for Early Input - GNSO Transfer Policy Review PDP Date: Tue, 28 Feb 2023 20:26:53 +0000 From: Devan Reed To: julf at julf.com , Andrea Glandon CC: gnso-secs at icann.org , Emily Barabas , Berry Cobb , Julie Hedlund , Caitlin Tubergen Dear Julf, Please find attached a request from the GNSO Transfer Policy Review Policy Development Process Working Group forinputfrom your group on Group 2 topics within the PDP?s charter. Responses are requested by 4 April 2023 and may be sent tognso-secs at icann.org . Kind regards, Devan *Devan Reed* Policy Development Support - TEMP Internet Corporation for Assigned Names and Numbers (ICANN) www.icann.org cidimage001.png at 01D4E0C6.320C4B80 -------------- next part -------------- A non-text attachment was scrubbed... Name: Transfer Policy Review PDP - Request for Early Input on Group 2 Topics .pdf Type: application/pdf Size: 184982 bytes Desc: not available URL: From mesumbeslin at gmail.com Tue Feb 28 22:48:03 2023 From: mesumbeslin at gmail.com (Tomslin Samme-Nlar) Date: Wed, 1 Mar 2023 07:48:03 +1100 Subject: [NCSG-PC] [NCSG-EC] ICANN76 Board Questions/Topics In-Reply-To: References: <4BA8915F-74D6-476F-A26F-D08019A7616A@icann.org> Message-ID: Hi Julf, I am wondering if we could ask the board the following: The GNSO Statement of Interest (SOI) Task Force has recommended that participants must disclose the identities of their clients or the employers they represent as a condition to participating in a working group. We believe this should be done without exception to enhance transparency and prevent group take-overs. What are the board's thoughts on this? Warmly, Tomslin On Sat, 18 Feb 2023 at 01:48, Johan Helsingius via NCSG-EC < ncsg-ec at lists.ncsg.is> wrote: > Dear NCSG, > > It is time to decide what we want to take up in our meeting with the > Board in Cancun. The Board has asked the SO/AC:s one question: > > "The ICANN Board would like to explore how to combine the efficiencies > of an agile approach to problem solving, like the Council?s small teams, > with the need for accountability and transparency, to make progress on > policy conversations. When would such an approach be most appropriate > and how can we ensure that it does not circumvent required steps in a > policy development process?" > > What are our thoughts? > > As to our questions to the board, here are our questions from the > previous meeting (as a reminder): > > - What is the Board?s take on the phenomenon of ICANN recycling veterans > for leadership positions. Does the Board think it?s beneficial for the > community to have the usual suspects rotating between leadership roles > of different stakeholder groups? How do we fix this if we agree this > is a problem? How does the Board imagine its role in assisting the > community to recruit more new blood? > > - Is there a possibility of rebalancing the NomCom? > > - What efforts are channeled to keep the people in the community from > volunteer fatigue? > > Julf > > _______________________________________________ > NCSG-EC mailing list > NCSG-EC at lists.ncsg.is > https://lists.ncsg.is/mailman/listinfo/ncsg-ec > -------------- next part -------------- An HTML attachment was scrubbed... URL: