- GNSO-CCOICI - lists.icann.org

GNSO Council approval of motion to extend the GNSO Framework for Continuous Improvement Pilot Project
by Olga Cavalli 23 Mar '22

23 Mar '22

Dear All, As you are aware, the GNSO Council extended our mandate and has requested that we review a number of WS2 items that are Council specific. The staff support team has been requested to prepare a background briefing on the items identified that will help inform our deliberations and development of an approach and project plan. The resolution also asks the CCOICI to reach out to the GNSO SG/Cs to identify WS2 experts that may be in a position to advise the CCOICI in our tasks. As we await the background briefing, I would like to ask all of you to reach out to your respective groups to see if there are any WS2 experts that would be willing and available to assist us in this task. Unless they would be interested, I don’t anticipate that they would need to partake in all our meetings but we may want to call on them at the outset of our deliberations to better understand the original intent of these recommendations so that this can be factored into the CCOICI’s review of these specific WS2 items. As a reminder, these are the WS2 items that have been assigned to the CCOICI: 1. Review the staff assessment of GNSO Council’s implementation status of Recommendation 2 Guidelines for Good Faith Conduct (2.1, 2.2) and Recommendation 6 SO/AC Accountability (6.1-6.5); 2. Recommendation 1 Diversity – revisit Council’s initial prioritization and carry out implementation for applicable sub recommendations, if any; 3. Recommendation 3 Human Rights Framework – carry out implementation from GNSO Council’s perspective; 4. Recommendation 6.1.5 (non-mandatory) – discuss whether the GNSO Council wishes to implement, and if so, how to implement; 5. Rank Recommendations 1, 2.3 and 3 from Council’s perspective to help inform the prioritization by the Community Coordination Group. I’ve requested the GNSO Secretariat to schedule our next meeting for *Wednesday 30 March at 12.00 UTC* so we can start considering our assignment. I hope this works for everyone. If not, please let gnso-secs know off-list. Best regards, Olga Cavalli Chair CCOICI

2 1

Meeting Invitation | CCOICI Meeting | Wednesday, 30 March 2022 at 12:00 UTC
by Nathalie Peregrine 11 Mar '22

11 Mar '22

Dear all, The next CCOICI meeting is scheduled on Wednesday, 30 March 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/v4FZCw * Check your time zone: https://tinyurl.com/3mc8zy7w Thank you, Kind regards, Nathalie

1 0

CCOICI meeting
by ICANN Policy Calendar 11 Mar '22

11 Mar '22

Meeting: CCOICI meeting Date: Wednesday, 30 March 2022 Time: 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/v4FZCw * Check your time zone: https://tinyurl.com/3mc8zy7w

1 0

Reminder: ICANN Zoom room requirements: Zoom Logins: First & Last Name/ Surname Only
by Nathalie Peregrine 09 Mar '22

09 Mar '22

Dear all, To ensure transparency of participation in ICANN’s multistakeholder model, please remember to sign in to Zoom sessions using your full name (e.g. First Name + Last Name/Surname). If you are in a session using the webinar format, you will need to first exit the Zoom room prior to rejoining. Please reach out to your support staff if you have any difficulties joining a Zoom session. To rename in a regular Zoom room: 1. Join the meeting. 2. Tap Participants. 3. Hover over your name on the participants list. 4. Click More. 5. Click Rename. 6. Enter the name you desire then click Rename. 7. Your name has now been changed within the meeting. To rename in a webinar Zoom room: 1. BEFORE entering the meeting, and during the login phase, update your Zoom name here: [cid:image001.png@01D83300.B8213430] 1. If you forget to do so, you can always log out of the webinar Zoom room and edit your name upon re-entering. Please contact your support staff if you run into any issues. Thank you! Kind regards, Nathalie

1 0

ICANN Zoom room requirements: Zoom Logins: First & Last Name/ Surname Only
by Nathalie Peregrine 08 Mar '22

08 Mar '22

Dear all, To ensure transparency of participation in ICANN’s multistakeholder model, please remember to sign in to Zoom sessions using your full name (e.g. First Name + Last Name/Surname). If you are in a session using the webinar format, you will need to first exit the Zoom room prior to rejoining. Please reach out to your support staff if you have any difficulties joining a Zoom session. To rename in a regular Zoom room: 1. Join the meeting. 2. Tap Participants. 3. Hover over your name on the participants list. 4. Click More. 5. Click Rename. 6. Enter the name you desire then click Rename. 7. Your name has now been changed within the meeting. To rename in a webinar Zoom room: 1. BEFORE entering the meeting, and during the login phase, update your Zoom name here: [cid:image001.png@01D83300.B8213430] 1. If you forget to do so, you can always log out of the webinar Zoom room and edit your name upon re-entering. Please contact your support staff if you run into any issues. Thank you! Kind regards, Nathalie

1 0

IMPORTANT - Session change ICANN73: New gTLD Subsequent Procedures: Operational Design Phase
by Julie Bisland 03 Mar '22

03 Mar '22

Dear all, ⚠️ Due to scheduling conflicts the ICANN73 session New gTLD Subsequent Procedures: Operational Design Phase will take place at a different time and date. ⚠️ Previously scheduled for Wednesday 9 March 2022 at 09:00 am local time (13:00 UTC), it will now take place on Monday 7 March 2022 at 12:30 local time (16:30 UTC). To update your calendars please follow the below steps: 1. Remove the entry for New gTLD Subsequent Procedures: Operational Design Phase on Wednesday 9 March 2022 09:00 am local time. 2. If you had already selected the new gTLD Subsequent Procedures: Operational Design Phase entry in your “My Agenda” on the ICANN73 website, you will not need to re-select it. You will however need to export that session once again to your own calendar. 3. Please refer to the attached “How to Get Organised” email to refresh your memories on how to download sessions! Please reach out to gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> if you have any questions. Kind regards, Nathalie

1 0

ICANN73 Virtual Community Forum | Guidelines for Speakers
by Devan Reed 01 Mar '22

01 Mar '22

Dear all, As we are just a week away from the ICANN73 Virtual Community Forum, the ICANN Language Services Team has created a document to serve as a guideline for speakers. As a reminder, GNSO-supported ICANN meetings do not use interpretation services. However, the reminders and pointers included are useful for all. Thank you! Kind regards, Devan

1 0

Please read! | ICANN73 GNSO Policy Briefing & ICANN73 Policy Outlook Report Available for Download
by Julie Bisland 17 Feb '22

17 Feb '22

Dear All, Please find the GNSO Policy Briefing and Policy Outlook Report links below for ICANN73. GNSO Policy Briefing ICANN73 Edition: http://go.icann.org/gnsobriefing [go.icann.org]<https://urldefense.com/v3/__http:/go.icann.org/gnsobriefing__;!!PtGJab4!uV0…> ICANN73 Policy Outlook Report: https://go.icann.org/outlook73 [go.icann.org]<https://urldefense.com/v3/__https:/go.icann.org/outlook73__;!!PtGJab4!uV0zw…> Thank you. With kind regards, Julie -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

ICANN73 GNSO Sessions - How to Get Organized / Remote Participation Details
by Julie Bisland 11 Feb '22

11 Feb '22

Dear all, Now is the moment to prepare your schedules for ICANN73! 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. Please read the below points for a seamless ICANN73! YOU MUST REGISTER FOR ICANN73 INFORMATION * Sign into your ICANN Account, or create an account here [account.icann.org]<https://urldefense.com/v3/__https:/account.icann.org/login__;!!PtGJab4!r0Vr…>. * Register for ICANN73 by clicking in the ICANN SERVICES menu and selecting Meeting Registration and click on the ICANN73 Registration link. Click here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…> for detailed instructions. Access the ICANN73 Schedule * ICANN73 schedule: https://73.schedule.icann.org/ [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/__;!!PtGJab4!r0Vro…> For security purposes, participation links will be posted 24-hours prior to the session start times. * ICANN73 GNSO Sessions have been grouped on the ICANN73 GNSO wiki page<https://community.icann.org/x/Fc0GCw>. Create your own schedule: * The ICANN Meeting website allows you to download all GNSO-related meetings to your inbox calendar in one go. For detailed instructions on how to create your personalized ICANN73 schedule and import your schedule to your calendar, click here [gnso.icann.org]<https://urldefense.com/v3/__https:/gnso.icann.org/sites/default/files/polic…>. Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior on the ICANN73 Meeting Schedule [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/__;!!PtGJab4!r0Vro…>. * Visit the Participation Tools page [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/participation-tool…> for links to download the latest version of Zoom for access to the ICANN73 sessions. * Please see the ICANN Meeting Virtual Participation How-To Guide [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/attend__;!!PtGJab4…> for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN73 Meeting Schedule [73.schedule.icann.org]<https://urldefense.com/v3/__https:/73.schedule.icann.org/__;!!PtGJab4!r0Vro…> GNSO ICANN73 Wiki Page<https://community.icann.org/x/Fc0GCw> GNSO Session agendas<https://community.icann.org/x/EM0GCw> 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 -- Julie Bisland Policy Operations Sr. Coordinator (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype ID: 79613b691cb8a6c1 Find out more about the GNSO by visiting: https://learn.icann.org/<https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

For your review - updates made to reflect today's discussion
by Marika Konings 10 Feb '22

10 Feb '22

Dear All, Please note that the staff support team has included a number of edits in the document to reflect today’s discussion regarding confidentiality of responses (see https://docs.google.com/document/d/1BIYQNao380XIWSG357Cq6Fw6dfFkn71T/edit) You can find these edits on pages 4, 5, 11, 12 and 16 (edits marked as made by Emily Barabas and Marika Konings). Please note that with regards to the references to information that is included in the summary report and how it is distributed, this reflects current practice. If the group wants to suggest changes to the current practice, please note so in your comments. Please review these revisions and provide any you input you may have on these revisions as well as any other sections of the document by Friday 4 February at the latest. Based on the input received, we’ll confirm whether the meeting on 9 February is necessary or not. Best regards, Emily, Julie and Marika From: GNSO-CCOICI <gnso-ccoici-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Wednesday, 26 January 2022 at 14:56 To: "gnso-ccoici(a)icann.org" <gnso-ccoici(a)icann.org> Subject: [GNSO-CCOICI] Action Items and Notes: CCOICI Meeting 26 Jan 2022 at 13:00 UTC Dear members of the CCOICI, Please see below the action items and brief notes for the meeting of the Committee on Wednesday, 26 January 2022 at 13.00 UTC. Please see the relevant materials which can be found on the wiki page: https://community.icann.org/x/JYMZCg. The next meeting will be scheduled for Wednesday, 09 February 2022 at 13.00 UTC. Kind regards, Marika & Julie Action Items: 1. Staff to produce a revised version of the Working Group Self-Assessment to clarify points relating to the confidentiality of personal data. 2. Committee members to review the revised Working Group Self-Assessment prior to the meeting on 09 February. 3. Staff to ask for volunteers for the role of the Council Committee liaison to the GNSO SOI Task Force. Notes: 1. Welcome a. Appointment of Council Committee liaison to GNSO SOI Task Force * We finished our work with the review of the assignment of the work to the Statement of Interest Task Force. * The Task Force is now formed and ready to begin work. * The Task Force will need a liaison from the Council Committee. * This is not a liaison in the tradition sense, as in from the GNSO Council to another group. * This is a liaison from the Council Committee (CCOICI), which has oversight of the Task Force. The liaison has the direct linkage to the Committee in case there are questions or concerns, and to provide updates on the progress of the Task Force to the Committee. * The liaison should be in place when the first Task Force meeting is scheduled. ACTION ITEM: Staff to ask for volunteers for the role of the Council Committee liaison to the GNSO SOI Task Force. 2. Working Group Self-Assessment – proposed updates and additions to relevant WGSA documents (see https://docs.google.com/document/d/1BIYQNao380XIWSG357Cq6Fw6dfFkn71T/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1BIYQNao380XI…>) a. Review input received from CCOICI members * Only comments from Flip and Desiree. The comments from Desiree on the issue of technical requirements relating confidentiality of personal data. Flip had an editorial suggestion. * We will need to address the issue of confidentiality of responses. * Asking whether members need more time to review, or whether the document is fine in its current version. There was general agreement that the document did not require further review, but we will allow 1 more week for those who have missed today’s meeting. b. Address outstanding questions: * Confidentiality of responses – what is the expectation from respondents as well as those reviewing the responses? * Will need to update the document based on the Committee’s determination. * Currently WG members get a general link and they provide their names when completing the survey, but only staff see the names. The results are anonymized. Summary report is distributed and published. * Questions: Should we continue in the same manner? The same for both the mid-cycle survey and the end-of-cycle survey? Who should see the raw data? What are the expectations of responses and reviewers? * Could we use technology to anonymize responses – that is, to provide a unique URL to each respondent? This would eliminate the ability for anyone to see the personal data of respondents. * Not sure whether this is possible in the survey tool. * Could suggest language emphasizing that access to personal data should be restricted and technological solutions should be considered. * We would still want to ask for affiliation so we understand the balance of the responses over the participating groups. * The current language makes it clear what data is collected and what is done with that data. * Could get better feedback if responses are anonymous. * Some people may want to provide their names, which is possible. Could be an optional field, or provided in comments. But then depending on the size of the group one may be able to determine who are the other respondents. * Currently we do not publish the names of respondents. * Is the intent that ICANN Org staff will not see the personal identification? Or just that it not be published? * Should be as specific as possible with our requirements for confidentiality since ICANN is currently evaluating tools. * Public comment – proposal to bundle with possible changes that result from GNSO SOI TF * Changes to GNSO Operating Procedures have to be put out for public comment before taking effect. Consider the timing for this step. * There is also the work of the SOI Task Force, which may result in changes. Consider whether to wait and put all changes out for public comment, depending on the timing of the work of the Task Force. * If we hold for later publication, suggest that the Committee shares the document with the Council along with an update. * Question: Do we have any idea how long the work of the Task Force will take? Answer: In the assignment form the timeframe was 6-9 months. It is a small and focused group with a focused topic so this seems reasonable. There will be outreach to other groups, but that is considered in the timeframe estimate. * The Task Force also could decide that no changes are needed to the Operational Procedures. * The Task Force also is expected to develop a work plan with milestones to share with the Committee. If the work looks like it will take too long to complete the Committee could decide to go forward with the public comment. * The responses from the public comment will be reviewed by the Task Force for the SOI and by the Committee for the WG self-assessment. c. Confirm next steps * Proposed next step: Staff will provide revised text based on this discussion to make clear that providing names is optional and to consider tools allow for the provision of a unique ULR. * Once the revised document is finalized, Olga can provide it with an update to the GNSO Council while noting that it will still go out for public comment, and explaining issues of timing relating to possible changes arising from the work of the SOI Task Force. * The Committee will review the responses received from the public comment. * There are currently no further assignments for the Committee, but the GNSO Council could determine further activities. ACTION ITEMS: 1. Staff to produce a revised version of the Working Group Self-Assessment to clarify points relating to the confidentiality of personal data. 2. Committee members to review the revised Working Group Self-Assessment prior to the meeting on 09 February. 3. Confirm action items & next meeting (Wednesday 9 February at 13.00 UTC) * The meeting on 09 February will be scheduled, but if there are no further comments on the Working Group Self-Assessment the meeting could be canceled.

3 6