July 2023 - GNSO-CCOICI - lists.icann.org

REMINDER: CCOICI Action item - please complete google doc with your group's position
by Marika Konings 01 Aug '23

01 Aug '23

Reminder – so far, no input has been provided. Please provide your group’s position in advance of Wednesday’s meeting: https://docs.google.com/document/d/1dRxPmBjPWEoNwe-UwSeQnLi2GcXLQj4w/edit. Best regards, Julie & Marika From: GNSO-CCOICI <gnso-ccoici-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Wednesday, 19 July 2023 at 15:18 To: "gnso-ccoici(a)icann.org" <gnso-ccoici(a)icann.org> Subject: [GNSO-CCOICI] CCOICI Action item: please complete google doc with your group's position Dear All, Per the action item below, please find hereby the google doc to document your group’s positions: https://docs.google.com/document/d/1dRxPmBjPWEoNwe-UwSeQnLi2GcXLQj4w/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1dRxPmBjPWEoN…>. As requested during the meeting, please complete this document as soon as you have confirmed your group’s position so that others have a chance to review this in advance of the next meeting which is scheduled for Wednesday 2 August at 12.00 UTC. Best regards, Julie & Marika From: GNSO-CCOICI <gnso-ccoici-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Wednesday, 19 July 2023 at 14:43 To: "gnso-ccoici(a)icann.org" <gnso-ccoici(a)icann.org> Subject: [GNSO-CCOICI] Action Items and Notes | CCOICI Meeting | Wednesday 19 July at 1200 UTC Dear CCOICI members, Please find below the notes and action items from today’s CCOICI meeting on Wednesday 19 July at 1200 UTC. Please see the relevant materials which can be found on the wiki page: https://community.icann.org/x/DRR1Cw. Best regards, Julie and Marika HOMEWORK/ACTION ITEMS: 1. Staff to provide a Google doc with the original exemption language and the suggested revision, along with the options for reporting to Council for CCOICI members to circulate to their groups and then to fill out with their positions. 2. Staff to schedule a meeting in two weeks on Wednesday, 02 August at 1200 UTC. Notes: 1. Welcome 2. Feedback on updated language on page 8 of the recommendations report * Juan Manuel, NCSG: NCSG has discussed the new language. We are against the addition – we are okay with the original language. * Marie, BC: Fine with the new language. * Thomas, INSERT: Did not have a chance to socialize. * Sebastien, RySG: Didn’t get any major feedback so assuming they are okay with it. Is it possible to understand the opposition to the new language from NCSG? * Manju, NCSG: If you add the text you may as well not have the exemption language at all – new text renders it useless. * Antonia, RrSG: Circulated and there are some debates still so no decision yet. Could we have a few more days? * Manju, NCSG: We don’t have a final decision since some groups need more time. But if we can’t get consensus on this text what is the next step? If we are not agreeing on this it seems like the whole SOI is not useful. Or we don’t deliver the report? * Marika, staff: Group seems to have agreement on most of what is in this report except for this section. One challenge is that the charter doesn’t specify the decision making methodology for the CCOICI. Can report positions or not deliver a report. Or could say it has reached agreement on everything except this section, so defaults to the status quo, which wouldn’t be very satisfactory. If everyone else can live with it, would the NCSG accept it? * Antonia, RrSG: We know there is an exemption in the current SOI, does that stay if we don’t have a decision? * Manju, NCSG: Yes the status quo would stay. How to proceed? Maybe groups need more time? * Sebastien, RySG: In the next few days hoping to come back with a point of view. * Antonia, RrSG: We have a meeting on Monday. * Thomas, ISPCP: Will check with my group. * Marika, staff: Staff can summarize the current situation and next steps, and you can consult with your groups. * Manju, NCSG: Ask if they are okay with the new language, and ask if they want to revert to existing language. * Marie, BC: We are okay with the new language. If people have a big change of view it will be helpful if they could indicate their position on email. * Manju, NCSG: Good idea. * Marika, staff: Circulate the new language with the old – make it clear that if they can’t live with the new language then can they accept the original language. Also provide the options for reporting to the Council. * Manju, NCSG: So fill in the Google form with our positions? * Marika, staff: That would be the expectation. * Manju, NCSG: Also ask if we deliver the report without the revision to the exemption language, or not report. 3. Confirm next steps 1. Staff to provide a Google doc with the original exemption language and the suggested revision, along with the options for reporting to Council for CCOICI members to circulate to their groups and then to fill out with their positions. 2. Staff to schedule a meeting in two weeks on Wednesday, 02 August at 1200 UTC.

3 2

CCOICI Action item: please complete google doc with your group's position
by Marika Konings 19 Jul '23

19 Jul '23

Dear All, Per the action item below, please find hereby the google doc to document your group’s positions: https://docs.google.com/document/d/1dRxPmBjPWEoNwe-UwSeQnLi2GcXLQj4w/edit. As requested during the meeting, please complete this document as soon as you have confirmed your group’s position so that others have a chance to review this in advance of the next meeting which is scheduled for Wednesday 2 August at 12.00 UTC. Best regards, Julie & Marika From: GNSO-CCOICI <gnso-ccoici-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Wednesday, 19 July 2023 at 14:43 To: "gnso-ccoici(a)icann.org" <gnso-ccoici(a)icann.org> Subject: [GNSO-CCOICI] Action Items and Notes | CCOICI Meeting | Wednesday 19 July at 1200 UTC Dear CCOICI members, Please find below the notes and action items from today’s CCOICI meeting on Wednesday 19 July at 1200 UTC. Please see the relevant materials which can be found on the wiki page: https://community.icann.org/x/DRR1Cw. Best regards, Julie and Marika HOMEWORK/ACTION ITEMS: 1. Staff to provide a Google doc with the original exemption language and the suggested revision, along with the options for reporting to Council for CCOICI members to circulate to their groups and then to fill out with their positions. 2. Staff to schedule a meeting in two weeks on Wednesday, 02 August at 1200 UTC. Notes: 1. Welcome 2. Feedback on updated language on page 8 of the recommendations report * Juan Manuel, NCSG: NCSG has discussed the new language. We are against the addition – we are okay with the original language. * Marie, BC: Fine with the new language. * Thomas, INSERT: Did not have a chance to socialize. * Sebastien, RySG: Didn’t get any major feedback so assuming they are okay with it. Is it possible to understand the opposition to the new language from NCSG? * Manju, NCSG: If you add the text you may as well not have the exemption language at all – new text renders it useless. * Antonia, RrSG: Circulated and there are some debates still so no decision yet. Could we have a few more days? * Manju, NCSG: We don’t have a final decision since some groups need more time. But if we can’t get consensus on this text what is the next step? If we are not agreeing on this it seems like the whole SOI is not useful. Or we don’t deliver the report? * Marika, staff: Group seems to have agreement on most of what is in this report except for this section. One challenge is that the charter doesn’t specify the decision making methodology for the CCOICI. Can report positions or not deliver a report. Or could say it has reached agreement on everything except this section, so defaults to the status quo, which wouldn’t be very satisfactory. If everyone else can live with it, would the NCSG accept it? * Antonia, RrSG: We know there is an exemption in the current SOI, does that stay if we don’t have a decision? * Manju, NCSG: Yes the status quo would stay. How to proceed? Maybe groups need more time? * Sebastien, RySG: In the next few days hoping to come back with a point of view. * Antonia, RrSG: We have a meeting on Monday. * Thomas, ISPCP: Will check with my group. * Marika, staff: Staff can summarize the current situation and next steps, and you can consult with your groups. * Manju, NCSG: Ask if they are okay with the new language, and ask if they want to revert to existing language. * Marie, BC: We are okay with the new language. If people have a big change of view it will be helpful if they could indicate their position on email. * Manju, NCSG: Good idea. * Marika, staff: Circulate the new language with the old – make it clear that if they can’t live with the new language then can they accept the original language. Also provide the options for reporting to the Council. * Manju, NCSG: So fill in the Google form with our positions? * Marika, staff: That would be the expectation. * Manju, NCSG: Also ask if we deliver the report without the revision to the exemption language, or not report. 3. Confirm next steps 1. Staff to provide a Google doc with the original exemption language and the suggested revision, along with the options for reporting to Council for CCOICI members to circulate to their groups and then to fill out with their positions. 2. Staff to schedule a meeting in two weeks on Wednesday, 02 August at 1200 UTC.

1 0

Post Call | CCOICI call | Wednesday, 19 July 2023
by Terri Agnew 19 Jul '23

19 Jul '23

Dear all, All recordings for the Council Committee for Overseeing and Implementing Continuous Improvement call held on Wednesday, 19 July 2023 at 12:00 UTC can be found on the agenda wiki page<https://community.icann.org/x/3JWZDg> (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 recording (including chat, 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 Terri

1 0

Action Items and Notes | CCOICI Meeting | Wednesday 19 July at 1200 UTC
by Julie Hedlund 19 Jul '23

19 Jul '23

Dear CCOICI members, Please find below the notes and action items from today’s CCOICI meeting on Wednesday 19 July at 1200 UTC. Please see the relevant materials which can be found on the wiki page: https://community.icann.org/x/DRR1Cw. Best regards, Julie and Marika HOMEWORK/ACTION ITEMS: 1. Staff to provide a Google doc with the original exemption language and the suggested revision, along with the options for reporting to Council for CCOICI members to circulate to their groups and then to fill out with their positions. 2. Staff to schedule a meeting in two weeks on Wednesday, 02 August at 1200 UTC. Notes: 1. Welcome 2. Feedback on updated language on page 8 of the recommendations report * Juan Manuel, NCSG: NCSG has discussed the new language. We are against the addition – we are okay with the original language. * Marie, BC: Fine with the new language. * Thomas, INSERT: Did not have a chance to socialize. * Sebastien, RySG: Didn’t get any major feedback so assuming they are okay with it. Is it possible to understand the opposition to the new language from NCSG? * Manju, NCSG: If you add the text you may as well not have the exemption language at all – new text renders it useless. * Antonia, RrSG: Circulated and there are some debates still so no decision yet. Could we have a few more days? * Manju, NCSG: We don’t have a final decision since some groups need more time. But if we can’t get consensus on this text what is the next step? If we are not agreeing on this it seems like the whole SOI is not useful. Or we don’t deliver the report? * Marika, staff: Group seems to have agreement on most of what is in this report except for this section. One challenge is that the charter doesn’t specify the decision making methodology for the CCOICI. Can report positions or not deliver a report. Or could say it has reached agreement on everything except this section, so defaults to the status quo, which wouldn’t be very satisfactory. If everyone else can live with it, would the NCSG accept it? * Antonia, RrSG: We know there is an exemption in the current SOI, does that stay if we don’t have a decision? * Manju, NCSG: Yes the status quo would stay. How to proceed? Maybe groups need more time? * Sebastien, RySG: In the next few days hoping to come back with a point of view. * Antonia, RrSG: We have a meeting on Monday. * Thomas, ISPCP: Will check with my group. * Marika, staff: Staff can summarize the current situation and next steps, and you can consult with your groups. * Manju, NCSG: Ask if they are okay with the new language, and ask if they want to revert to existing language. * Marie, BC: We are okay with the new language. If people have a big change of view it will be helpful if they could indicate their position on email. * Manju, NCSG: Good idea. * Marika, staff: Circulate the new language with the old – make it clear that if they can’t live with the new language then can they accept the original language. Also provide the options for reporting to the Council. * Manju, NCSG: So fill in the Google form with our positions? * Marika, staff: That would be the expectation. * Manju, NCSG: Also ask if we deliver the report without the revision to the exemption language, or not report. 3. Confirm next steps 1. Staff to provide a Google doc with the original exemption language and the suggested revision, along with the options for reporting to Council for CCOICI members to circulate to their groups and then to fill out with their positions. 2. Staff to schedule a meeting in two weeks on Wednesday, 02 August at 1200 UTC.

1 0

Meeting Invitation | CCOICI Meeting | Wednesday, 02 August 2023 at 12:00 UTC
by Terri Agnew 19 Jul '23

19 Jul '23

Dear all, The meeting of the CCOICI team will take place on Wednesday, 02 August 2023 at 12:00 UTC for 1 hour. 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 apologies and 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/9oTxDg * Check your time zone: https://tinyurl.com/yextrh4s Thank you, Kind regards, Terri

1 0

CCOICI team
by ICANN Policy Calendar 19 Jul '23

19 Jul '23

Meeting: CCOICI team Date/time: Wednesday, 02 August 2023 at 12:00 UTC for 1 hour 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<mailto:.&@z%5ezfSL1> 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 apologies and 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/9oTxDg * Check your time zone: https://tinyurl.com/yextrh4s

1 0

**Starting in 15 minutes | Meeting Invitation | CCOICI Meeting | Wednesday, 19 July 2023 at 12:00 UTC
by Terri Agnew 19 Jul '23

19 Jul '23

**Starting in 15 minutes Dear all, The meeting of the CCOICI team will take place on Wednesday, 19 July 2023 at 12:00 UTC for 1 hour. 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 apologies and 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/3JWZDg * Check your time zone: https://tinyurl.com/288fhw5h <https://urldefense.com/v3/__https:/tinyurl.com/288fhw5h__;!!PtGJab4!96zcogk…> Thank you, Kind regards, Terri

1 0

Reminder - please review and socialise updated exemption language
by Marika Konings 19 Jul '23

19 Jul '23

Dear All, A reminder to please review the updated language on page 8 that was developed following input from the RySG. For your convenience you find it reproduced here (in red the sentence that has been added): 1. Are you participating in the GNSO policy process as a representative of any individual or entity, whether paid or unpaid? The term “representative” in this context means that you are acting on behalf of a third party, whether it is a legal or a natural person (the ‘Represented Party’) by whom you have been appointed, specifically for this activity or to a role that encompasses this activity, to represented and/or advocate for the Represented Party’s interests, views and positions. If the answer is “Yes,” please provide the name of the represented individual or entity. (If professional ethical obligations prevent you from disclosing this information, you must provide details on which ethical obligations prevent you from disclosing and must provide a high level description of the entity that you are representing without disclosing its name as well as declare whether, to the best of your knowledge, that entity is actively participating or being represented in other GNSO SG/Cs/SO/Acs,, for example “I represent a Registry client who is also actively participating in the RySG”, “I am representing a governmental entity, who is also actively participating in the GAC” or “I represent a large brand holder in the entertainment sector who, to the best of my knowledge, is not actively participating or being represented in other ICANN groups”. If you are not able to provide these details or high-level description, you are assumed to participate on your own behalf or on behalf of the entity you listed as your current employer). Please share your group’s feedback no later than the meeting that has been scheduled for 19 July. Best regards, Julie and Marika From: GNSO-CCOICI <gnso-ccoici-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, 6 July 2023 at 15:10 To: "gnso-ccoici(a)icann.org" <gnso-ccoici(a)icann.org> Subject: [GNSO-CCOICI] Action Items and Notes | CCOICI Meeting | Thursday 06 July at 1200 UTC Dear CCOICI members, Please find below the notes and action items from today’s CCOICI meeting on Thursday, 06 July at 1200 UTC. Please see the relevant materials which can be found on the wiki page: https://community.icann.org/x/DRR1Cw. Best regards, Julie and Marika HOMEWORK/ACTION ITEMS: 1. Staff to update the report to 1) delete the language about not participating in consensus calls (page 6); and 2) to insert the new language about only representing yourself/employer (page 8) – DONE: See attached. 2. CCOICI members to review pages 6 and 8 of the revised report (attached) and provide feedback to the group on the list not later than the meeting on 19 July. Notes: 1. Welcome 2. Feedback from SG/Cs on compromise proposal * Sebastien: RySG is not willing to budge. Chris Disspain’s view also was to counter the two assertions: 1) that by demanding transparency we would be limiting people from joining – we aren’t asking lawyers to disclose their clients as such, people can still participate as themselves (in their own name); more targeting an insider who is represented by several people in the room. In the specific case of new applicants not wanting to disclose their own name, that is an edge case and we shouldn’t be building policy on it. * Manju, NCSG/Chair: If RySG isn’t willing to budge that means going back to the status quo? * Seb, RySG: We would like that removed – so no option to say “private”. * Manju, NCSG/Chair: So they are representing themselves. Is it possible to put this into text? * Seb, RySG: Can share the spirit of our proposal in a suggested text. * Manju, NCSG/Chair: What do others think? * Marie, BC: Can’t really comment until I’ve seen it written down. The BC has tried to seek compromise. Looking at the stats the entire use of the exemption is an edge case. Confused how this would work in practice, but it seems like you wouldn’t have to disclose your client at all. * Seb, RySG: Edge case was new applicants not disclosing. The other issue is if we ask people to speak in their own capacity then you can’t be changing positions. * Susan, IPC: Seems that this takes us back to the status quo. Don’t see how this delivers more transparency. Don’t see how this is better than the compromise. * Marika, staff: I think in the text, it would look something like this: “If the answer is “Yes,” please provide the name of the represented individual or entity. (If professional ethical obligations prevent you from disclosing this information, you are assumed to participate on your own behalf or on behalf of the entity you listed as your current employer).” We can incorporate the text in the report. * Manju, NCSG/Chair: We could still keep the whole request for disclosure and then add this text. * Marika, staff: You would still ask them to describe and if they don’t then they are participating on behalf of yourself and your employer. * Desiree, NomCom: How would we track if someone keeps changing his or her position? * Marie, BC: Also a bit confused as to the idea if you're there for the mythical big player you'd change your mind in every meeting - wouldn't you in fact be more likely to be solid in your line then? * Seb, RySG: Imagine a big player – if they don’t want to disclose then their position would have to be their own/employer – not whom they represent. * Manju, NCSG/Chair: We can share this text with our groups since we are missing some people today. * Marika, staff: Would we keep in the language about people not participating in consensus calls if they don’t disclose? * Seb, RySG: We wouldn’t include it – hard to say who would make that ruling and what would be the guidelines? * Manju, NCSG/Chair: Confirm that you would delete the language about not participating in consensus calls? * Seb, RySG: For the registries, yes. * Manju: We still have to go back to our groups to consider – perhaps for two weeks. We’ll schedule on the 19th of July at the same time. 3. Next Steps * Schedule a call for Wednesday, 19 July at 1200 UTC. * After the CCOICI finishes this work since this was a pilot project the Council will ask the CCOICI how the work can be improved. ACTION ITEMS: 1. Staff to update the report to 1) delete the language about not participating in consensus calls (page 6); and 2) to insert the new language about only representing yourself/employer (page 8) – DONE: See attached. 2. CCOICI members to review pages 6 and 8 of the revised report (attached) and provide feedback to the group on the list not later than the meeting on 19 July.

4 3

Proposed Agenda - CCOICI meeting on Wednesday 19 July at 12.00 UTC
by Marika Konings 19 Jul '23

19 Jul '23

Dear All, Hereby the proposed agenda for the upcoming CCOICI meeting (Wednesday 19 July at 12.00 UTC): 1. Welcome 2. Feedback on updated language on page 8 of the recommendations report 3. Confirm next steps Best regards, Julie & Marika From: GNSO-CCOICI <gnso-ccoici-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Tuesday, 11 July 2023 at 13:16 To: "gnso-ccoici(a)icann.org" <gnso-ccoici(a)icann.org> Subject: [GNSO-CCOICI] Reminder - please review and socialise updated exemption language Dear All, A reminder to please review the updated language on page 8 that was developed following input from the RySG. For your convenience you find it reproduced here (in red the sentence that has been added): 1. Are you participating in the GNSO policy process as a representative of any individual or entity, whether paid or unpaid? The term “representative” in this context means that you are acting on behalf of a third party, whether it is a legal or a natural person (the ‘Represented Party’) by whom you have been appointed, specifically for this activity or to a role that encompasses this activity, to represented and/or advocate for the Represented Party’s interests, views and positions. If the answer is “Yes,” please provide the name of the represented individual or entity. (If professional ethical obligations prevent you from disclosing this information, you must provide details on which ethical obligations prevent you from disclosing and must provide a high level description of the entity that you are representing without disclosing its name as well as declare whether, to the best of your knowledge, that entity is actively participating or being represented in other GNSO SG/Cs/SO/Acs,, for example “I represent a Registry client who is also actively participating in the RySG”, “I am representing a governmental entity, who is also actively participating in the GAC” or “I represent a large brand holder in the entertainment sector who, to the best of my knowledge, is not actively participating or being represented in other ICANN groups”. If you are not able to provide these details or high-level description, you are assumed to participate on your own behalf or on behalf of the entity you listed as your current employer). Please share your group’s feedback no later than the meeting that has been scheduled for 19 July. Best regards, Julie and Marika From: GNSO-CCOICI <gnso-ccoici-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Thursday, 6 July 2023 at 15:10 To: "gnso-ccoici(a)icann.org" <gnso-ccoici(a)icann.org> Subject: [GNSO-CCOICI] Action Items and Notes | CCOICI Meeting | Thursday 06 July at 1200 UTC Dear CCOICI members, Please find below the notes and action items from today’s CCOICI meeting on Thursday, 06 July at 1200 UTC. Please see the relevant materials which can be found on the wiki page: https://community.icann.org/x/DRR1Cw. Best regards, Julie and Marika HOMEWORK/ACTION ITEMS: 1. Staff to update the report to 1) delete the language about not participating in consensus calls (page 6); and 2) to insert the new language about only representing yourself/employer (page 8) – DONE: See attached. 2. CCOICI members to review pages 6 and 8 of the revised report (attached) and provide feedback to the group on the list not later than the meeting on 19 July. Notes: 1. Welcome 2. Feedback from SG/Cs on compromise proposal * Sebastien: RySG is not willing to budge. Chris Disspain’s view also was to counter the two assertions: 1) that by demanding transparency we would be limiting people from joining – we aren’t asking lawyers to disclose their clients as such, people can still participate as themselves (in their own name); more targeting an insider who is represented by several people in the room. In the specific case of new applicants not wanting to disclose their own name, that is an edge case and we shouldn’t be building policy on it. * Manju, NCSG/Chair: If RySG isn’t willing to budge that means going back to the status quo? * Seb, RySG: We would like that removed – so no option to say “private”. * Manju, NCSG/Chair: So they are representing themselves. Is it possible to put this into text? * Seb, RySG: Can share the spirit of our proposal in a suggested text. * Manju, NCSG/Chair: What do others think? * Marie, BC: Can’t really comment until I’ve seen it written down. The BC has tried to seek compromise. Looking at the stats the entire use of the exemption is an edge case. Confused how this would work in practice, but it seems like you wouldn’t have to disclose your client at all. * Seb, RySG: Edge case was new applicants not disclosing. The other issue is if we ask people to speak in their own capacity then you can’t be changing positions. * Susan, IPC: Seems that this takes us back to the status quo. Don’t see how this delivers more transparency. Don’t see how this is better than the compromise. * Marika, staff: I think in the text, it would look something like this: “If the answer is “Yes,” please provide the name of the represented individual or entity. (If professional ethical obligations prevent you from disclosing this information, you are assumed to participate on your own behalf or on behalf of the entity you listed as your current employer).” We can incorporate the text in the report. * Manju, NCSG/Chair: We could still keep the whole request for disclosure and then add this text. * Marika, staff: You would still ask them to describe and if they don’t then they are participating on behalf of yourself and your employer. * Desiree, NomCom: How would we track if someone keeps changing his or her position? * Marie, BC: Also a bit confused as to the idea if you're there for the mythical big player you'd change your mind in every meeting - wouldn't you in fact be more likely to be solid in your line then? * Seb, RySG: Imagine a big player – if they don’t want to disclose then their position would have to be their own/employer – not whom they represent. * Manju, NCSG/Chair: We can share this text with our groups since we are missing some people today. * Marika, staff: Would we keep in the language about people not participating in consensus calls if they don’t disclose? * Seb, RySG: We wouldn’t include it – hard to say who would make that ruling and what would be the guidelines? * Manju, NCSG/Chair: Confirm that you would delete the language about not participating in consensus calls? * Seb, RySG: For the registries, yes. * Manju: We still have to go back to our groups to consider – perhaps for two weeks. We’ll schedule on the 19th of July at the same time. 3. Next Steps * Schedule a call for Wednesday, 19 July at 1200 UTC. * After the CCOICI finishes this work since this was a pilot project the Council will ask the CCOICI how the work can be improved. ACTION ITEMS: 1. Staff to update the report to 1) delete the language about not participating in consensus calls (page 6); and 2) to insert the new language about only representing yourself/employer (page 8) – DONE: See attached. 2. CCOICI members to review pages 6 and 8 of the revised report (attached) and provide feedback to the group on the list not later than the meeting on 19 July.

1 0

REMINDER | Meeting Invitation | CCOICI Meeting | Wednesday, 19 July 2023 at 12:00 UTC
by Devan Reed 18 Jul '23

18 Jul '23

Dear all, The meeting of the CCOICI team will take place on Wednesday, 19 July 2023 at 12:00 UTC for 1 hour. 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 apologies and 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/3JWZDg * Check your time zone: https://tinyurl.com/288fhw5h <https://urldefense.com/v3/__https:/tinyurl.com/288fhw5h__;!!PtGJab4!96zcogk…> Thank you, Kind regards, Terri

1 0