NOTES | Council prep meeting | 12 October 2023 (noon UTC)
NOTES | Council prep meeting | 12 October 2023 (noon UTC) Bart: rapporteur for the various sessions. You are kindly requested to participate in the session assigned in your name. We will have a google document, where the rapporteurs can note down anything that is valuable input to Council, regarding those sessions. Kim: bookmark this link. All will be included here. https://docs.google.com/document/d/1c4gTDL6DeT49tTneXbbxNTQici00nWhULbJZpXSm... Chris: exchange of liaisons. Would like to raise it during the Council workshop. Bart: ok, first 10 min. Linked to Roles and Responsibilities Alejandra: ok. Chris: PSWG is not an official interface. GAC is trying to remove all DNS Abuse discussions away from the PSWG, to the full GAC. Not appropriate for ccNSO to have individual meetings. RySG is rapidly trying to move away from interaction with the PSWG. Bart: GAC was looking at best practices. Staff made it clear there are no best practices. Too many variants. There are good practices. Regarding the survey results, tools and measurements are a follow-up. Nick: avoid parallel discussions to the same constituency Chris: last PSWG with CPH at GNSO. The Japanese GAC rep was on a mission to protect manga art. GAC said that this needs to be discussed by GAC, not PSWG. We should be careful. Nick: what DASC was created to do, is providing resources, sharing experiences, etc. GNSO has a bright line for content. Not so clear for ccTLDs. Complicated topic. Let me think about what we can present to PSWG. Bart: no presentation to PSWG. Just a discussion in setting expectations right. This is not a presentation, this is a prep meeting. Mismatch between expectations by PSWG and how they want to influence GAC discussions on DNS Abuse. To avoid this surfaces during the meeting itself, have this coordination meeting. Set expectations on what you will present. Nick: good to have something in writing. I do not want to be quoted out of context. Bart: I will be around. I can do the same intro as i did now. Coordination to set expectations right. From both sides. Initiative from staff. Prep for 30 min in parallel with a joint meeting between ccNSO and GNSO Council. Alejandra: timing of the prep avoiding joint meeting with Council. Bart: not possible Alejandra: if we have concerns, joint session with full GAC to explain what the DASC is doing. Bart: That is the Wednesday session. Full GAC.
joint session with GNSO council
Irina: update activities. Current or future? Alejandra: this session conflicts with prep for GAC. Also refer to methodology for collecting community input. Nick: see if we can cancel prep with PSWG Bart: prioritization method. Raise it as a point, and schedule it in a future meeting Irina: 10 min speaking time
Questions FOR Board * Topic 2: Alejandra Questions TO Board * Topic 2: Chris/Pablo Alejandra: our interaction with the Board. We do not want them to read scripted responses. Chris: agree. But that would be for us to do. Not sure it is relevant. Deliver a clear message to the board, not discuss with them. Bart: This question assumes some expectations. What are those expectations? The rest flows from it. A scripted session does not meet the goals. Start with the high level. What does the Board want to get out of it? And what does Council want to get out of it? Joke Braeken joke.braeken@icann.org<mailto:joke.braeken@icann.org> ICANN78: Links to bookmark now ccNSO Schedule https://community.icann.org/x/doDxDg ccNSO Session Highlights https://community.icann.org/x/K4LxDg
Hi all Thanks for these notes Joke and again my apols to not join, as it conflicted with IGF requirements. Should we use this schedule document as the same place to keep notes? Just checking, my assumption is the answer is 'yes'. On the meeting with the GNSO in terms of WSIS etc, is there any Council line here, or do I have a free hand (and of course will say they are personal views)? Cheers Jordan From: Ccnso-council <ccnso-council-bounces@icann.org> On Behalf Of Joke Braeken via Ccnso-council Sent: Thursday, October 12, 2023 11:54 PM To: ccnso-council <ccnso-council@icann.org> Subject: [EXTERNAL] - [ccnso-council] NOTES | Council prep meeting | 12 October 2023 (noon UTC) NOTES | Council prep meeting | 12 October 2023 (noon UTC) Bart: rapporteur for the various sessions. You are kindly requested to participate in the session assigned in your name. We will have a google document, where the rapporteurs can note down anything that is valuable input to Council, regarding those sessions. Kim: bookmark this link. All will be included here. https://docs.google.com/document/d/1c4gTDL6DeT49tTneXbbxNTQici00nWhULbJZpXSm... Chris: exchange of liaisons. Would like to raise it during the Council workshop. Bart: ok, first 10 min. Linked to Roles and Responsibilities Alejandra: ok. Chris: PSWG is not an official interface. GAC is trying to remove all DNS Abuse discussions away from the PSWG, to the full GAC. Not appropriate for ccNSO to have individual meetings. RySG is rapidly trying to move away from interaction with the PSWG. Bart: GAC was looking at best practices. Staff made it clear there are no best practices. Too many variants. There are good practices. Regarding the survey results, tools and measurements are a follow-up. Nick: avoid parallel discussions to the same constituency Chris: last PSWG with CPH at GNSO. The Japanese GAC rep was on a mission to protect manga art. GAC said that this needs to be discussed by GAC, not PSWG. We should be careful. Nick: what DASC was created to do, is providing resources, sharing experiences, etc. GNSO has a bright line for content. Not so clear for ccTLDs. Complicated topic. Let me think about what we can present to PSWG. Bart: no presentation to PSWG. Just a discussion in setting expectations right. This is not a presentation, this is a prep meeting. Mismatch between expectations by PSWG and how they want to influence GAC discussions on DNS Abuse. To avoid this surfaces during the meeting itself, have this coordination meeting. Set expectations on what you will present. Nick: good to have something in writing. I do not want to be quoted out of context. Bart: I will be around. I can do the same intro as i did now. Coordination to set expectations right. From both sides. Initiative from staff. Prep for 30 min in parallel with a joint meeting between ccNSO and GNSO Council. Alejandra: timing of the prep avoiding joint meeting with Council. Bart: not possible Alejandra: if we have concerns, joint session with full GAC to explain what the DASC is doing. Bart: That is the Wednesday session. Full GAC.
joint session with GNSO council
Irina: update activities. Current or future? Alejandra: this session conflicts with prep for GAC. Also refer to methodology for collecting community input. Nick: see if we can cancel prep with PSWG Bart: prioritization method. Raise it as a point, and schedule it in a future meeting Irina: 10 min speaking time
Questions FOR Board * Topic 2: Alejandra Questions TO Board * Topic 2: Chris/Pablo Alejandra: our interaction with the Board. We do not want them to read scripted responses. Chris: agree. But that would be for us to do. Not sure it is relevant. Deliver a clear message to the board, not discuss with them. Bart: This question assumes some expectations. What are those expectations? The rest flows from it. A scripted session does not meet the goals. Start with the high level. What does the Board want to get out of it? And what does Council want to get out of it? Joke Braeken joke.braeken@icann.org<mailto:joke.braeken@icann.org> ICANN78: Links to bookmark now ccNSO Schedule https://community.icann.org/x/doDxDg ccNSO Session Highlights https://community.icann.org/x/K4LxDg
Hi Jordan Yes, we use the schedule document to keep the notes. Regarding the WSIS topic, we didn't discuss any specific line we want to follow. What do you have in mind? To kick start the conversation I was thinking of following a similar approach to what we will discuss with the Board. This is now a CEO Goal, what roles are expected from the SO/ACs? We could also provide a summary of the WSIS+20 ccNSO session that will take place later in the week. Best, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Mon, Oct 16, 2023 at 1:48 AM Jordan Carter via Ccnso-council < ccnso-council@icann.org> wrote:
Hi all
Thanks for these notes Joke and again my apols to not join, as it conflicted with IGF requirements.
Should we use this schedule document as the same place to keep notes? Just checking, my assumption is the answer is ‘yes’.
On the meeting with the GNSO in terms of WSIS etc, is there any Council line here, or do I have a free hand (and of course will say they are personal views)?
Cheers
Jordan
*From:* Ccnso-council <ccnso-council-bounces@icann.org> *On Behalf Of *Joke Braeken via Ccnso-council *Sent:* Thursday, October 12, 2023 11:54 PM *To:* ccnso-council <ccnso-council@icann.org> *Subject:* [EXTERNAL] - [ccnso-council] NOTES | Council prep meeting | 12 October 2023 (noon UTC)
NOTES | Council prep meeting | 12 October 2023 (noon UTC)
Bart: rapporteur for the various sessions. You are kindly requested to participate in the session assigned in your name. We will have a google document, where the rapporteurs can note down anything that is valuable input to Council, regarding those sessions.
Kim: bookmark this link. All will be included here.
https://docs.google.com/document/d/1c4gTDL6DeT49tTneXbbxNTQici00nWhULbJZpXSm...
Chris: exchange of liaisons. Would like to raise it during the Council workshop.
Bart: ok, first 10 min. Linked to Roles and Responsibilities
Alejandra: ok.
Chris: PSWG is not an official interface. GAC is trying to remove all DNS Abuse discussions away from the PSWG, to the full GAC. Not appropriate for ccNSO to have individual meetings. RySG is rapidly trying to move away from interaction with the PSWG.
Bart: GAC was looking at best practices. Staff made it clear there are no best practices. Too many variants. There are good practices. Regarding the survey results, tools and measurements are a follow-up.
Nick: avoid parallel discussions to the same constituency
Chris: last PSWG with CPH at GNSO. The Japanese GAC rep was on a mission to protect manga art. GAC said that this needs to be discussed by GAC, not PSWG. We should be careful.
Nick: what DASC was created to do, is providing resources, sharing experiences, etc. GNSO has a bright line for content. Not so clear for ccTLDs. Complicated topic. Let me think about what we can present to PSWG.
Bart: no presentation to PSWG. Just a discussion in setting expectations right. This is not a presentation, this is a prep meeting. Mismatch between expectations by PSWG and how they want to influence GAC discussions on DNS Abuse. To avoid this surfaces during the meeting itself, have this coordination meeting. Set expectations on what you will present.
Nick: good to have something in writing. I do not want to be quoted out of context.
Bart: I will be around. I can do the same intro as i did now. Coordination to set expectations right. From both sides. Initiative from staff.
Prep for 30 min in parallel with a joint meeting between ccNSO and GNSO Council.
Alejandra: timing of the prep avoiding joint meeting with Council.
Bart: not possible
Alejandra: if we have concerns, joint session with full GAC to explain what the DASC is doing.
Bart: That is the Wednesday session. Full GAC.
joint session with GNSO council
Irina: update activities. Current or future?
Alejandra: this session conflicts with prep for GAC. Also refer to methodology for collecting community input.
Nick: see if we can cancel prep with PSWG
Bart: prioritization method. Raise it as a point, and schedule it in a future meeting
Irina: 10 min speaking time
Questions FOR Board
- Topic 2: Alejandra
Questions TO Board
- Topic 2: Chris/Pablo
Alejandra: our interaction with the Board. We do not want them to read scripted responses.
Chris: agree. But that would be for us to do. Not sure it is relevant. Deliver a clear message to the board, not discuss with them.
Bart: This question assumes some expectations. What are those expectations? The rest flows from it. A scripted session does not meet the goals. Start with the high level. What does the Board want to get out of it? And what does Council want to get out of it?
Joke Braeken
joke.braeken@icann.org
*ICANN78**: **Links to bookmark now*
ccNSO Schedule
https://community.icann.org/x/doDxDg
ccNSO Session Highlights
https://community.icann.org/x/K4LxDg
_______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org https://mm.icann.org/mailman/listinfo/ccnso-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.
Hi Alejandra This sounds like a good approach, happy to go with that flow. I didn’t have anything in particular in mind. Cheers Jordan From: Alejandra Reynoso Barral <alejandra.reynoso@gmail.com> Sent: Monday, October 16, 2023 9:35 PM To: Jordan Carter <jordan.carter@auda.org.au> Cc: Joke Braeken <joke.braeken@icann.org>; ccnso-council <ccnso-council@icann.org> Subject: Re: [ccnso-council] [EXTERNAL] - NOTES | Council prep meeting | 12 October 2023 (noon UTC) Hi Jordan Yes, we use the schedule document to keep the notes. Regarding the WSIS topic, we didn't discuss any specific line we want to follow. What do you have in mind? To kick start the conversation I was thinking of following a similar approach to what we will discuss with the Board. This is now a CEO Goal, what roles are expected from the SO/ACs? We could also provide a summary of the WSIS+20 ccNSO session that will take place later in the week. Best, Alejandra ******************************************* Work like you don't need the money. Love like you've never been hurt. Dance like nobody's watching. Sing like nobody's listening. And live like it's Heaven on Earth. ******************************************* On Mon, Oct 16, 2023 at 1:48 AM Jordan Carter via Ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> wrote: Hi all Thanks for these notes Joke and again my apols to not join, as it conflicted with IGF requirements. Should we use this schedule document as the same place to keep notes? Just checking, my assumption is the answer is ‘yes’. On the meeting with the GNSO in terms of WSIS etc, is there any Council line here, or do I have a free hand (and of course will say they are personal views)? Cheers Jordan From: Ccnso-council <ccnso-council-bounces@icann.org<mailto:ccnso-council-bounces@icann.org>> On Behalf Of Joke Braeken via Ccnso-council Sent: Thursday, October 12, 2023 11:54 PM To: ccnso-council <ccnso-council@icann.org<mailto:ccnso-council@icann.org>> Subject: [EXTERNAL] - [ccnso-council] NOTES | Council prep meeting | 12 October 2023 (noon UTC) NOTES | Council prep meeting | 12 October 2023 (noon UTC) Bart: rapporteur for the various sessions. You are kindly requested to participate in the session assigned in your name. We will have a google document, where the rapporteurs can note down anything that is valuable input to Council, regarding those sessions. Kim: bookmark this link. All will be included here. https://docs.google.com/document/d/1c4gTDL6DeT49tTneXbbxNTQici00nWhULbJZpXSm... Chris: exchange of liaisons. Would like to raise it during the Council workshop. Bart: ok, first 10 min. Linked to Roles and Responsibilities Alejandra: ok. Chris: PSWG is not an official interface. GAC is trying to remove all DNS Abuse discussions away from the PSWG, to the full GAC. Not appropriate for ccNSO to have individual meetings. RySG is rapidly trying to move away from interaction with the PSWG. Bart: GAC was looking at best practices. Staff made it clear there are no best practices. Too many variants. There are good practices. Regarding the survey results, tools and measurements are a follow-up. Nick: avoid parallel discussions to the same constituency Chris: last PSWG with CPH at GNSO. The Japanese GAC rep was on a mission to protect manga art. GAC said that this needs to be discussed by GAC, not PSWG. We should be careful. Nick: what DASC was created to do, is providing resources, sharing experiences, etc. GNSO has a bright line for content. Not so clear for ccTLDs. Complicated topic. Let me think about what we can present to PSWG. Bart: no presentation to PSWG. Just a discussion in setting expectations right. This is not a presentation, this is a prep meeting. Mismatch between expectations by PSWG and how they want to influence GAC discussions on DNS Abuse. To avoid this surfaces during the meeting itself, have this coordination meeting. Set expectations on what you will present. Nick: good to have something in writing. I do not want to be quoted out of context. Bart: I will be around. I can do the same intro as i did now. Coordination to set expectations right. From both sides. Initiative from staff. Prep for 30 min in parallel with a joint meeting between ccNSO and GNSO Council. Alejandra: timing of the prep avoiding joint meeting with Council. Bart: not possible Alejandra: if we have concerns, joint session with full GAC to explain what the DASC is doing. Bart: That is the Wednesday session. Full GAC.
joint session with GNSO council
Irina: update activities. Current or future? Alejandra: this session conflicts with prep for GAC. Also refer to methodology for collecting community input. Nick: see if we can cancel prep with PSWG Bart: prioritization method. Raise it as a point, and schedule it in a future meeting Irina: 10 min speaking time
Questions FOR Board * Topic 2: Alejandra Questions TO Board * Topic 2: Chris/Pablo Alejandra: our interaction with the Board. We do not want them to read scripted responses. Chris: agree. But that would be for us to do. Not sure it is relevant. Deliver a clear message to the board, not discuss with them. Bart: This question assumes some expectations. What are those expectations? The rest flows from it. A scripted session does not meet the goals. Start with the high level. What does the Board want to get out of it? And what does Council want to get out of it? Joke Braeken joke.braeken@icann.org<mailto:joke.braeken@icann.org> ICANN78: Links to bookmark now ccNSO Schedule https://community.icann.org/x/doDxDg ccNSO Session Highlights https://community.icann.org/x/K4LxDg _______________________________________________ Ccnso-council mailing list Ccnso-council@icann.org<mailto:Ccnso-council@icann.org> https://mm.icann.org/mailman/listinfo/ccnso-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.
participants (3)
-
Alejandra Reynoso Barral -
Joke Braeken -
Jordan Carter