May 2022 - GNSO-CCOICI - lists.icann.org

Meeting Invitation | CCOICI Meeting | Wednesday, 8 June 2022 at 12:00 UTC
by Nathalie Peregrine 25 May '22

25 May '22

Dear all, The next CCOICI meeting is scheduled on Wednesday, 8 June 2022 at 12:00 UTC for 60 minutes. Join Zoom Meeting: https://icann.zoom.us/j/96269931065?pwd=c0VKWkpMZHdNSlNSQkYrSG5MZmxQUT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/96269931065?pwd=c0VKWkpM…> Meeting ID: 962 6993 1065 Passcode: .&@z^zfSL1 One tap mobile +13126266799,,96269931065#,,,,*0702315261# US (Chicago) +19294362866,,96269931065#,,,,*0702315261# US (New York) Meeting ID: 962 6993 1065 Passcode: 0702315261 Find your local number: https://icann.zoom.us/u/ad6GAsKCUM <https://urldefense.com/v3/__https:/icann.zoom.us/u/ad6GAsKCUM__;!!PtGJab4!o…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Wiki agenda page: https://community.icann.org/pages/viewpage.action?pageId=192222225 * Check your time zone: https://tinyurl.com/57ss4xzh Thank you, Kind regards, Nathalie

1 0

Post Call | Council Committee for Overseeing and Implementing Continuous Improvement | Wednesday 25 May 2022
by Nathalie Peregrine 25 May '22

25 May '22

Dear all, All recordings for the Council Committee for Overseeing and Implementing Continuous Improvement call held on Wednesday 25 May 2022 at 12:00 UTC can be found on the agenda wiki page <https://community.icann.org/pages/viewpage.action?pageId=192222223> (attendance included) and the GNSO Master Calendar <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> . These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom Chat * Zoom recording (including audio, visual, rough transcript) * Transcript For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-ccoici/> and the main wiki page<https://community.icann.org/x/JYMZCg>. Thank you. Kind regards Nathalie

1 0

Notes and AIs from CCOICI meeting on Wednesday 25 May at 12.00 UTC
by Julie Hedlund 25 May '22

25 May '22

Dear All, Please find below the notes and action items from today’s CCOICI meeting. Please see the relevant materials which can be found on the wiki page: https://community.icann.org/x/DRR1Cw. Best regards, Ariel, Julie and Marika CCOICI Meeting on Wednesday 25 May at 12.00 UTC Action items: 1. Recommendation 2.1.2: Staff notes that the Committee members agree with the staff’s assessment of the status as “Implementation Planned”, and staff suggested Options 1 and 2, and will alert the Council accordingly. 2. Recommendations 2.2.1, 2.2.2, 2.2.3, and 2.2.4: Staff notes that the Committee agrees with the staff’s assessment of the status as “Complete” and staff will notify the Council accordingly. 3. GNSO Secretariat staff to send the invite for the meeting on 08 June at 12.00 UTC. Notes: 1. Welcome a. Work plan status: https://docs.google.com/spreadsheets/d/1h38SgFeOdwumE7fUjLu4mB0CcXnwoncUpIC… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1h38SgFeO…> b. Reminder – status designations: * "Complete": Recommended action/decision is completed by the GNSO Council * "Partially Complete": Recommended action/decision is partially completed by the GNSO Council, further implementation may or may not be within scope to be addressed by the GNSO Council * "Action/Decision Required": GNSO Council needs to make a decision on whether the recommended action/decision is applicable for action by the GNSO Council and assign an appropriate implementation status in this list * "Not applicable for action": Recommended action/decision and its respective implementation is not within scope to be addressed by the GNSO Council * "Implementation Planned": GNSO Council is planning to implement the recommended action/decision * "Implementation Ongoing": GNSO Council’s implementation on the recommended action/decision is ongoing * "Won't be Implemented": Recommended action/decision is within scope to be addressed by the GNSO Council, but GNSO Council chooses not to implement (this may apply to the non-mandatory recommendations) 2. Continue review of Recommendation #2 – Guidelines for Good Faith Conduct (see https://docs.google.com/document/d/1zuQVN4zbz4zBYlZM4Mtfac7lj2j2dlna/edit#[…<https://urldefense.com/v3/__https:/docs.google.com/document/d/1zuQVN4zbz4zB…> and background – Empowered Community & Guidelines for GNSO Council (see https://docs.google.com/presentation/d/1FK4jb068gTi-2WtMXjkj9RElnp7_CwMuwjr… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/presentation/d/1FK4jb068…>) a. Consider recommendations 2.1.2, 2.2.1 – 2.2.4 WS2 Recommendation 2.1.2: 2.1.2 Must: 2.1.2.1 Be believed by the Indemnified Party to be true. 2.1.2.2 Be in writing. 2.1.2.3 Contain sufficient detail to verify facts; if verifiable facts are asserted. 2.1.2.4 Supply supporting evidence if available/applicable. 2.1.2.5 Include references to applicable by-laws and/or procedures if the assertion is that a specific by-law or procedure has been breached. 2.1.2.6 Be respectful and professional in tone. The NomCom Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-n…> and SO/AC Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-s…> are not in conflict with the requirements from WS2 Recommendation 2.1.2. Staff notes that: * Section 4.2.2 of these two Guidelines includes the phrase “...shall include at least the following” with respect to the requirements for such petitions. This phrase offers wide discretion for inclusion of other requirements, criteria, or material to be provided by the petitioner. Further, there is no restrictive language anywhere in the Guidelines to say that additional requirements for the petitions are prohibited or will not be considered. In other words, there is nothing preventing the petitioner from satisfying the WS2 requirements when following the process as outlined in the Guidelines. Staff Assessment of 2.1.2 “Implementation Planned” Rationale: The NomCom Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-n…> and SO/AC Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-s…> are not in conflict with WS2 Rec 2.1.2. * Offers wide discretion for inclusion of other requirements, criteria, or material to be provided by the petitioner. * There is no restrictive language to say that additional requirements for the petitions are prohibited or will not be considered. * Nothing prevents the petitioner from satisfying the WS2 requirements when following the process as outlined in the Guidelines. However, guidelines should draw specific and explicit attention to the additional mandatory requirements as outlined in WS2 Rec 2.1.2. * GNSO Council requested that relevant Guidelines be reviewed after an action of the GNSO as a DP has been completed, or on an annual basis if no action is initiated. * GNSO Council is expected to have an opportunity to update the Guidelines as an outcome of such review or as needed, including to satisfy the mandatory WS2 requirements. * Staff believes it is necessary to draw attention to the mandatory requirements as outlines in WS2 Rec 2.1.2. * Opportunity to update the guidelines as the result of a review. Staff Suggestion for Completing Implementation of 2.1.2 * CCOICI may wish to ask the GNSO Council to consider the following approaches, including but not limited to: * Option 1: Update Section 4.2.2 of the NomCom Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-n…> and SO/AC Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-s…> by inserting the following phrase between “...the Petition shall” and “...include at least the following” in the first paragraph: “in addition to satisfying the requirements set out in Recommendation 2.1.2 of the WS2 Final Report<https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-27mar18-en.…>”. * Option 2: Update the GNSO webpage<https://gnso.icann.org/en/council/procedures> which contains all the Guidelines by including a note that petitioners utilizing the Board Director Removal related Guidelines should also refer to the mandatory requirements outlined in the Recommendation 2.1.2 of the WS2 Final Report<https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-27mar18-en.…>. * Committee could do one or both of the options or could decide on other options. * Support in the Committee for adopting both options. * Options 2 is simpler because we don’t have to update the guidelines. Changing the guidelines will require a decision from Council. * If we just update the website people may not notice it. For the sake of completeness it is best to do Options 1 and 2. * As this is unlikely to be controversial, the Council may consider this at the same time as it considers the status designations. * Staff will alert the Council of the Committee’s agreement with the status as “Implementation Planned” and the implementation of Options 1 and 2. The Council could approve a package of changes. WS2 Recommendation 2.2.1: 2.2 Recommendations for guidelines with respect to procedures for consideration of board removal notices by SO/ACs to include: 2.2.1 Reasonable time frames for investigation by SO/AC councils or the equivalent decision-making structures if the SO/AC deems that an investigation is required. Staff Assessment of 2.2.1 “Complete" * Section 4.2.4 and Section 4.2.5 of the NomCom Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-n…> and SO/AC Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-s…> satisfy the “investigation” requirement. Section 4.2.4 requires that the GNSO Council holds a dialogue between the Director subject to the petition, the Chair of the Board (or Vice Chair of the Board if the Chair is the affected Director), the Petitioner, and the GNSO Representative on the EC Administration. Section 4.2.5 states that GNSO Stakeholder Groups (SGs) and Constituencies (Cs) be asked to provide feedback, opinion, or comments on the merits of the petition, which will be reviewed by the GNSO Council. The dialogue and the GNSO community feedback should help the GNSO Council investigate the situation and decide whether to support such a petition. * Section 4.2.11 of the NomCom Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-n…> and Section 4.2.8 of the SO/AC Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-s…> satisfy the “reasonable time frames” requirement for investigation. The time tables in those sections set out the suggested deadlines for the GNSO Council to hold the dialogue (per Section 4.2.4) and to receive GNSO community feedback (per Section 4.2.5). The time tables were developed by following the timeline in the ICANN Bylaws with respect to the Director Removal Petition Period and taking into account other necessary administrative steps for processing the petition. * The GNSO Council also provides similar guidance with respect to a NomCom Director Removal petition initiated by another Decisional Participant. Section 4.3.3 of the NomCom Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-n…> states that during a three (3) day period directly following the receipt of the Petition Notice, GNSO Stakeholder Groups and Constituencies may provide their feedback, opinions or comments, which may help the GNSO Council decide whether it wishes to support such a petition. * The Committee agrees with the staff’s assessment of Recommendation 2.2.1 as “Complete”. Staff will notify the Council accordingly. WS2 Recommendation 2.2.2: 2.2.2 Period of review by the entire membership of the SO/AC provided the SO/AC organizational structure customarily provides review for individual members; otherwise, period of review by those empowered to represent the SO/AC in decisions of this nature Staff Assessment of 2.2.2 “Complete" * As mentioned above, Section 4.2.5 and Section 4.3.3 of the NomCom Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-n…>, as well as Section 4.2.5 of the SO/AC Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-s…> include the expectation and the suggested time period for the wider GNSO community to review the petition and provide feedback on its merits. The GNSO community feedback is intended to help the GNSO Council make an informed decision on whether to support such a petition. * The Committee agrees with the staff’s assessment of Recommendation 2.2.2 as “Complete”. Staff will notify the Council accordingly. WS2 Recommendation 2.2.3: 2.2.3 Consistent and transparent voting method for accepting or rejecting a petition; such voting maybe be by the entire membership or those empowered to represent the SO/AC in decisions of this nature. Staff Assessment of 2.2.3 “Complete" * Section 4.2.6 of the NomCom Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-n…> and SO/AC Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-s…> outline the method for the GNSO Council to decide whether to support or reject such a petition, as well as specifies the threshold needed to reach a decision in accordance with the ICANN Bylaws. * In addition, Section 4.3.4 of the NomCom Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-n…> includes similar guidance regarding the voting method for the GNSO Council to decide whether to support a petition initiated by another Decisional Participant. * The Committee agrees with the staff’s assessment of Recommendation 2.2.3 as “Complete”. Staff will notify the Council accordingly. WS2 Recommendation 2.2.4: 2.2.4 Documentation of the community process and how decisions are reached. Staff Assessment of 2.2.4 “Complete" * Section 4.2.7 of the NomCom Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-n…> and SO/AC Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-s…> outline the method for informing the community, the other Decisional Participants, and the EC Administration the GNSO Council decision on the petition. The guidelines specify the required information to be included in the Petition Notice, such as the GNSO Council decision and the rationale for the decision. * In addition, Section 4.3.5 the NomCom Director Removal Guideline<https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-d-n…> includes similar guidance regarding informing the ICANN org, the other Decisional Participants, and the EC Administration the GNSO Council’s decision whether to support a petition initiated by another Decisional Participant. The guidelines specify the required information to be included in a written notice. * The Committee agrees with the staff’s assessment of Recommendation 2.2.4 as “Complete”. Staff will notify the Council accordingly. b. Confirm status designation ACTION ITEM: Recommendation 2.1.2: Staff notes that the Committee members agree with the staff’s assessment of the status as “Implementation Planned”, and staff suggested Options 1 and 2, and will alert the Council accordingly. ACTION ITEM: Recommendations 2.2.1, 2.2.2, 2.2.3, and 2.2.4: Staff notes that the Committee agrees with the staff’s assessment of the status as “Complete” and staff will notify the Council accordingly. 3. Confirm next steps & next meeting (Wednesday 8 June at 12.00 UTC) * Schedule unless there are travel conflicts. * Haven’t scheduled for the week after ICANN74 yet. * There is not specific due date for the work and the Committee is making good progress. * Would be helpful to have the meeting on 08 June. Then the last item is on the human rights framework. ACTION ITEM: GNSO Secretariat staff to send the invite for the meeting on 08 June at 12.00 UTC.

1 0

At the top of the hour: Meeting Invitation | CCOICI Meeting | Wednesday, 25 May 2022 at 12:00 UTC
by Nathalie Peregrine 25 May '22

25 May '22

Dear all, The next CCOICI meeting is scheduled on Wednesday, 25 May 2022 at 12:00 UTC for 60 minutes. Join Zoom Meeting: https://icann.zoom.us/j/96269931065?pwd=c0VKWkpMZHdNSlNSQkYrSG5MZmxQUT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/96269931065?pwd=c0VKWkpM…> Meeting ID: 962 6993 1065 Passcode: .&@z^zfSL1 One tap mobile +13126266799,,96269931065#,,,,*0702315261# US (Chicago) +19294362866,,96269931065#,,,,*0702315261# US (New York) Meeting ID: 962 6993 1065 Passcode: 0702315261 Find your local number: https://icann.zoom.us/u/ad6GAsKCUM <https://urldefense.com/v3/__https:/icann.zoom.us/u/ad6GAsKCUM__;!!PtGJab4!o…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Wiki agenda page: https://community.icann.org/x/DxR1Cw * Check your time zone: https://tinyurl.com/3ydne8zz [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3ydne8zz__;!!PtGJab4!9ftWSPA…> Thank you, Kind regards, Nathalie

1 0

**REMINDER** Meeting Invitation | CCOICI Meeting | Wednesday, 25 May 2022 at 12:00 UTC
by Julie Bisland 24 May '22

24 May '22

Dear all, The next CCOICI meeting is scheduled on Wednesday, 25 May 2022 at 12:00 UTC for 60 minutes. Join Zoom Meeting: https://icann.zoom.us/j/96269931065?pwd=c0VKWkpMZHdNSlNSQkYrSG5MZmxQUT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/96269931065?pwd=c0VKWkpM…> Meeting ID: 962 6993 1065 Passcode: .&@z^zfSL1 One tap mobile +13126266799,,96269931065#,,,,*0702315261# US (Chicago) +19294362866,,96269931065#,,,,*0702315261# US (New York) Meeting ID: 962 6993 1065 Passcode: 0702315261 Find your local number: https://icann.zoom.us/u/ad6GAsKCUM <https://urldefense.com/v3/__https:/icann.zoom.us/u/ad6GAsKCUM__;!!PtGJab4!o…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Wiki agenda page: https://community.icann.org/x/DxR1Cw * Check your time zone: https://tinyurl.com/3ydne8zz [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/3ydne8zz__;!!PtGJab4!58vbuqL…> Thank you, Kind regards, Nathalie

1 0

Proposed Agenda - CCOICI meeting on Wednesday 25 May at 12.00 UTC
by Marika Konings 24 May '22

24 May '22

Dear All, Please find below the proposed agenda for the next meeting of the CCOICI which is scheduled for Wednesday 25 May at 12.00 UTC. Best regards, Ariel, Julie and Marika Proposed Agenda – CCOICI Meeting on Wednesday 25 May 2022 at 12.00 UTC 1. Welcome * Work plan status: https://docs.google.com/spreadsheets/d/1h38SgFeOdwumE7fUjLu4mB0CcXnwoncUpIC… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1h38SgFeO…> * Reminder – status designations: * "Complete": Recommended action/decision is completed by the GNSO Council * "Partially Complete": Recommended action/decision is partially completed by the GNSO Council, further implementation may or may not be within scope to be addressed by the GNSO Council * "Action/Decision Required": GNSO Council needs to make a decision on whether the recommended action/decision is applicable for action by the GNSO Council and assign an appropriate implementation status in this list * "Not applicable for action": Recommended action/decision and its respective implementation is not within scope to be addressed by the GNSO Council * "Implementation Planned": GNSO Council is planning to implement the recommended action/decision * "Implementation Ongoing": GNSO Council’s implementation on the recommended action/decision is ongoing * "Won't be Implemented": Recommended action/decision is within scope to be addressed by the GNSO Council, but GNSO Council chooses not to implement (this may apply to the non-mandatory recommendations) 1. Continue review of Recommendation #2 – Guidelines for Good Faith Conduct (see https://docs.google.com/document/d/1zuQVN4zbz4zBYlZM4Mtfac7lj2j2dlna/edit#<https://docs.google.com/document/d/1zuQVN4zbz4zBYlZM4Mtfac7lj2j2dlna/edit> and background – Empowered Community & Guidelines for GNSO Council (see https://docs.google.com/presentation/d/1FK4jb068gTi-2WtMXjkj9RElnp7_CwMuwjr…) * Consider recommendations 2.1.2, 2.2.1 – 2.2.4 * Confirm status designation 2. Confirm next steps & next meeting (Wednesday 8 June at 12.00 UTC)

1 0

ICANN74 schedule now published
by Terri Agnew 23 May '22

23 May '22

https://www.icann.org/en/announcements/details/schedule-for-icann74-policy-… Dear all, This is the first ever ICANN meeting in hybrid format. Whilst some steps will seem familiar, others are brand new, please read the below carefully before creating your schedule. I MUST REGISTER TODAY FOR ICANN74 INFORMATION Sign into my ICANN Account, or create an account here<https://account.icann.org/login>. Register for ICANN74 by clicking in the ICANN SERVICES menu and selecting Meeting Registration Click on the ICANN74 Registration link. Click here<https://gnso.icann.org/sites/default/files/policy/2021/presentation/instruc…> for detailed instructions. The deadline to register for in-person participation is 8 June 2022 at 23:59 UTC. Before creating my schedule I must read this page carefully, to understand what’s new in the hybrid meeting format: https://74.schedule.icann.org/attend IN-PERSON PRIORITY SEATING GNSO Councilors who confirmed they will be traveling to the Hague: · If you have registered on the ICANN74 Website<https://74.schedule.icann.org/>, you will see the indication that your GNSO Council sessions have already been added to your schedule. GNSO PDP/EPDP/ST/SG/C Members: · If you signed up via the google survey as an active PDP/EPDP/ST/SG/C member, you will automatically be signed up to that session. · If you have not yet signed up to attend ICANN74, have not responded to the surveys sent by gnso-secs, and you will be attending on-site, please only select sessions that you will be attending as an active member or participant CAN I CREATE MY MEETING SCHEDULE NOW? * Please choose carefully when signing up for sessions—seating space is limited and the goal is to prioritize the sessions you will actively participate in * Upon accessing the schedule, I will be asked to confirm whether I’m attending remotely or on-site. * If I’m participating remotely, all good, please proceed to access to the ICANN74 schedule: https://74.schedule.icann.org/. * If I’m participating on-site, I must only attend the sessions in which I am an active participant. Please read the https://74.schedule.icann.org/attend page if you are unsure. Please proceed to access to the ICANN74 schedule: https://74.schedule.icann.org/. * Please remember, for security purposes, participation links will be posted 24-hours prior to the session start times. There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to you, to your individual calendars Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior on the ICANN74 Meeting Schedule<https://74.schedule.icann.org/>. * Visit the Participation Tools page<https://74.schedule.icann.org/participation-tools> for links to download the latest version of Zoom for access to the ICANN74 sessions. * Please see the ICANN Meeting Virtual Participation How-To Guide<https://74.schedule.icann.org/attend> for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN74 Meeting Schedule<https://74.schedule.icann.org/> GNSO ICANN74 Wiki Page<https://community.icann.org/x/vhN1Cw> GNSO Session agendas<https://community.icann.org/x/vBN1Cw> For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team

1 0

Meeting Invitation | CCOICI Meeting | Wednesday, 25 May 2022 at 12:00 UTC
by Nathalie Peregrine 12 May '22

12 May '22

Dear all, The next CCOICI meeting is scheduled on Wednesday, 25 May 2022 at 12:00 UTC for 60 minutes. Join Zoom Meeting: https://icann.zoom.us/j/96269931065?pwd=c0VKWkpMZHdNSlNSQkYrSG5MZmxQUT09<https://urldefense.com/v3/__https:/icann.zoom.us/j/96269931065?pwd=c0VKWkpM…> Meeting ID: 962 6993 1065 Passcode: .&@z^zfSL1 One tap mobile +13126266799,,96269931065#,,,,*0702315261# US (Chicago) +19294362866,,96269931065#,,,,*0702315261# US (New York) Meeting ID: 962 6993 1065 Passcode: 0702315261 Find your local number: https://icann.zoom.us/u/ad6GAsKCUM <https://urldefense.com/v3/__https:/icann.zoom.us/u/ad6GAsKCUM__;!!PtGJab4!o…> If this is your first time with Zoom, please take a look here: Welcome to Zoom <https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> ALL: Before joining the call * Please send dial out requests to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> only * Please be sure you have read the ICANN Expected Standards of Behavior<https://urldefense.com/v3/__https:/www.icann.org/resources/pages/expected-s…> * Wiki agenda page: https://community.icann.org/x/DxR1Cw * Check your time zone: https://tinyurl.com/3ydne8zz Thank you, Kind regards, Nathalie

1 0

Post Call | Council Committee for Overseeing and Implementing Continuous Improvement | Thursday, 12 May 2022
by Nathalie Peregrine 12 May '22

12 May '22

Dear all, All recordings for the Council Committee for Overseeing and Implementing Continuous Improvement call held on Thursday, 12 May 2022 at 12:00 UTC can be found on the agenda wiki page <https://community.icann.org/pages/viewpage.action?pageId=192222221> (attendance included) and the GNSO Master Calendar <https://urldefense.com/v3/__https:/gnso.icann.org/en/group-activities/calen…> . These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom Chat * Zoom recording (including audio, visual, rough transcript) * Transcript For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-ccoici/> and the main wiki page<https://community.icann.org/x/JYMZCg>. Thank you. Kind regards Nathalie

1 0

Notes and AI from CCOICI meeting on Thursday 12 May at 12.00 UTC
by Marika Konings 12 May '22

12 May '22

Dear All, Please find below the notes and action item from today’s CCOICI meeting. Please see the relevant materials which can be found on the wiki page: https://community.icann.org/x/DRR1Cw. Best regards, Ariel, Julie and Marika CCOICI Meeting on Thursday 12 May at 12.00 UTC Notes Action item: 1. CCOICI to consider designation for 2.1.2 as well as options identified for completing the implementation of 2.1.2 and provide their feedback either on the mailing list and/or during the next meeting. 1. Welcome * For the work plan status, please see https://docs.google.com/spreadsheets/d/1h38SgFeOdwumE7fUjLu4mB0CcXnwoncUpIC… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/spreadsheets/d/1h38SgFeO…>. Good progress is being made. * Reminder – the group is expected to consider the status designations for the recommendations under review: * "Complete": Recommended action/decision is completed by the GNSO Council * "Partially Complete": Recommended action/decision is partially completed by the GNSO Council, further implementation may or may not be within scope to be addressed by the GNSO Council * "Action/Decision Required": GNSO Council needs to make a decision on whether the recommended action/decision is applicable for action by the GNSO Council and assign an appropriate implementation status in this list * "Not applicable for action": Recommended action/decision and its respective implementation is not within scope to be addressed by the GNSO Council * "Implementation Planned": GNSO Council is planning to implement the recommended action/decision * "Implementation Ongoing": GNSO Council’s implementation on the recommended action/decision is ongoing * "Won't be Implemented": Recommended action/decision is within scope to be addressed by the GNSO Council, but GNSO Council chooses not to implement (this may apply to the non-mandatory recommendations) 1. Commence review of Recommendation #2 – Guidelines for Good Faith Conduct (2.1) (see https://docs.google.com/document/d/1zuQVN4zbz4zBYlZM4Mtfac7lj2j2dlna/edit#[…<https://urldefense.com/v3/__https:/docs.google.com/document/d/1zuQVN4zbz4zB…>) * Background – Empowered Community & Guidelines for GNSO Council (see https://docs.google.com/presentation/d/1FK4jb068gTi-2WtMXjkj9RElnp7_CwMuwjr… [docs.google.com]<https://docs.google.com/presentation/d/1FK4jb068gTi-2WtMXjkj9RElnp7_CwMuwjr…>) * The staff support team walked the CCOICI through the relevant background information to assist the CCOICI to understand the context of the guidelines for good faith conduct recommendations. With specific focus on EC power to appoint and remove individual ICANN Board directors (other than the President) * To review all the guidelines and templates that help the GNSO fulfil its role and obligation as a Decision Participant, see https://gnso.icann.org/en/council/procedures * Consider recommendations 2.1.1 and 2.1.2 – Recommendations for Guidelines for Standards of Conduct presumed to be in Good Faith associated with exercising removal of individual ICANN Board Directors. * Rec 2.1 Petitions for removal of directors: * 2.1.1. May be for any reason * 2.1.2 Must: * Be believed by the Indemnified Party to be true * Be in writing * Contain sufficient detail to verify facts, if verifiable facts are asserted * Supply supporting if available / applicable * Include references to applicable by-law or procedure has been breached * Be respectful and professional in tone * The staff assessment for 2.1.1. is that it is complete as there is no restrictive language anywhere in the guidelines to say that such petitions must be for specific reasons, implying that the petitions for removal may be for any reason (see section 4.2.2 of the guidelines for the requirements for a Nominating Committee Director Removal petition as well as requirements for an SO/AC Director removal petition). * CCOICI agrees with the staff assessment and considers this recommendation “complete”. * WS2 Recommendation 2.1.2 – looking at the guidance for the petition, the language notes shall include ‘at least’ the following. Only requires 4 basic elements but not the details as 2.1.2 foresees. As such, the staff assessment is that the implementation of this recommendation is not complete yet, but it is planned. The guidance is currently not in conflict as it does not preclude further information to be provided. Provides discretion for other materials to be provided and is not restrictive. * However, guidelines should draw specific and explicit attention to the additional mandatory requirements. * GNSO Council requested that relevant guidelines be reviewed after an action of the GNSO as a DP has been completed, or on an annual basis if no action is initiated. * GNSO Council is expected to have an opportunity to update the Guidelines as an outcome of such review as needed, including to satisfy the mandatory WS2 requirements. * Staff suggestion for completing Implementation of 2.1.2: * CCOICI may wish to ask the GNSO Council to consider the following approaches, including, but not limited to: * Option 1: Update Section 4.2.2 of the two sets of guidelines by inserting the following phrase between “…the Petition shall” and “…include at least the following” in the first paragraph: “In addition to satisfying the requirement set out in Recommendation 2.1.2 of the WS2 Final Report”. * Update the GNSO webpage<https://gnso.icann.org/en/council/procedures> which contains all the Guidelines by including a note that petitioners utilizing the Board Director Removal related Guidelines should also refer to the mandatory requirements outlined in the Recommendation 2.1.2 of the WS2 Final Report<https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-27mar18-en.…>. Action item: CCOICI to consider designation for 2.1.2 as well as options identified for completing the implementation of 2.1.2 and provide their feedback either on the mailing list and/or during the next meeting. 1. Confirm next steps & next meeting (Wednesday 25 May at 12.00 UTC)

1 0