April 2022 - GNSO-SOI-TF - lists.icann.org

Post Call | Statement of Interest Task Force | Monday, 25 April 2022
by Devan Reed April 25, 2022

April 25, 2022

Dear all, All recordings for the Statement of Interest Task Force call held on Monday, 25 April 2022 at 20:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/UgkiCw> (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) For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-soi-tf/> and the main wiki page.<https://community.icann.org/x/yYXOCg> Thank you. Kind regards Devan

1 0

Action Items & Notes: SOI TF Meeting 25 April 2022 20:00 UTC
by Julie Hedlund April 25, 2022

April 25, 2022

Dear All, Please see below the action items and brief notes from today’s SOI Task Force meeting on Monday, 25 April 2022 at 20:00 UTC. These also are posted to the wiki at: https://community.icann.org/x/yYXOCg. Kind regards, Marika and Julie SOI Task Force Meeting #6 Monday, 25 April 2022 at 20:00 UTC Action Items: ACTION ITEM: TF members to review the Draft SOI Recommendations at: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit and provide comments/suggestions by Thursday, 05 May 2022. Notes: 1. Welcome a. Reminder – encourage participation in the outreach survey (https://engage.clicktools.com/v2/kakajko1rvzr#page1 [engage.clicktools.com]<https://urldefense.com/v3/__https:/engage.clicktools.com/v2/kakajko1rvzr*pa…> – deadline for input 4 May) * Staff to reach out to Policy colleague supporting non-GNSO groups to encourage input. * Call for input was published in the community digest. 2. Continue review of mind map (see attached) Overview: * Separate the SOI into two parts: general and activity specific. * General SOI would be the parent and activity specific SOI would be the child. * The questions would largely remain as they are, but separated into two SOI. * Helpful to develop specific use cases so people understand what we are looking for. * Explore whether there is an annual reminder for the general SOI; for the activity specific it would need to be updated if participation in the activity changes. Discussion: * Question: We should make a distinction in the activity specific statements of interest – there is also a component where we would say you would also not comment on the perspective of other constituencies other than your own/declared for specific statement of interest – is there more work to be done for the activity specific SOI? Answer: Some groups have started using Statements of Participation; people also sometimes switch hats, but that should be documented. If the group thinks that this should be covered in the activity specific SOI, what would the question be or how to ensure that this is announced. * If it's an open WG someone could absolutely be wearing multiple hats. * think it’s more problematic in representative WGs, but I think it should be discouraged generally. * Could try to flesh this out a bit more. If we could have some guidance/use case to reference for the activity specific SOI. * We also need to start giving more concrete guidance when the groups are set up what are the expectations. Sometimes not communicated clearly to the rep from their SG/C. Someone might think they are participating as an individual, not as a representative. * Could be put into the instructions for when the requests for membership go out. * The representative model is more vulnerable to this type of problem. Should be considered in bad form to participate as a rep from one group, but then speak on behalf of another group. * Totally agree that it's communication - it's just something I would think would head off potential problems when you get to the SOI itself. * I do think there's a big distinction between a rep model, where you are supposed to speak for your group and a PDP where anyone can join and some people may well have more than one perspective. Karen's a brand owner and you cannot expect her to only represent her dotBrand interest and not her brand owner interest - provided the SOI explains adequately. * Could also be guidance for the chair to watch out for this. * Instructions should make crystal clear to speak only on behalf of the group you are representing. * This is a problem that lies with the SG/C. In some groups it’s very clear, for others it is really hard to get a position from the rep. * FAQs and recommended practices it could be helpful. But not sure it is on point for this TF. 3. Draft of Suggested SOI Recommendations: * Should align with what we’ve discussed thus far. * Attempt to document what the TF has discussed. The current Statement of Interest template is divided into two parts, namely: * General Statement of Interest which contains general information about a participant to understand their background and motivation for participating in GNSO activities. * Activity Specific Statement of Interest which is information that is provided specific to the activity a participant has requested to participate in. For example, what is their motivation for participation in that activity as well as possible impact on the individual and/or their employer of the outcomes of the process. General SOI questions: * Who you are, where you reside, who you work for, etc. * Consider whether a yearly reminder should be sent. * Should be able to delete their SOI if no longer applicable. Wouldn’t want to expand this beyond the SOI. May need to ask if this is something we need to provide. * Trying to avoid some future scenario where an old transcript or mailing list is redacted to the point where it is no longer a complete record of previous work. * Maybe allow people to request a deletion and to have that request reviewed. Activity Specific SOI: * Might not want this information to be deleted as it’s helpful as a matter of record. * Completed for each activity. * Working with the original list of question. Questions to consider: * #5a: Do you believe you are participating in the GNSO policy process as a representative of any individual or entity, whether paid or unpaid? Question: it was originally suggested that the Activity Specific Statement of Interest could also include a question that would ask about what the desired outcome and/or describing the possible impacts of such outcome. Is that something to be added? * #5b(i): Do you have any type of material interest in ICANN GNSO policy development processes and outcomes? Question: Should this be updated to say “you, your employer or your client(s)”? * #5b(ii): Are there any arrangements/agreements between you and any other group, constituency or person(s) regarding your participation as a work team member? Question: Question: Should “client” be added here to make specific that if there is an arrangement with a client it should be called out here? * #9: The GNSO SOI Task Force recommends that prior to these recommendations being adopted, a test run is conducted from which feedback is gathered by the SOI TF to determine whether updates need to be considered. Question: could such a test run also be carried out with a PDP that is already underway – with a request for volunteers to complete the new SOI from the perspective of the effort they are participating in and sharing their feedback on whether the proposed updates are deemed helpful? * Once the TF has agreed on the details of the recommendations, we can begin the revision to the SOI section of the GNSO Operating Procedures. * Once we’ve gone through this exercise we will look at enforcement. 4. Confirm next steps & next meeting (Monday 9 May at 13.00 UTC) Next Steps: * Staff to post draft recommendations as a Google document. * TF members to comment/suggest further details to include, questions, etc. * Next meeting, hope to have the results of the survey to review. ACTION ITEM: TF members to review the Draft SOI Recommendations at: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit and provide comments/suggestions by Thursday, 05 May 2022.

1 0

Meeting Invitation | SOI Taskforce Meeting | Monday, 09 May 2022 at 13:00 UTC
by Devan Reed April 25, 2022

April 25, 2022

Dear all, The next SOI Taskforce meeting is scheduled on Monday, 09 May 2022 at 13:00 UTC for 60 minutes. Join Zoom Meeting: https://icann.zoom.us/j/94092604895?pwd=Q2xoaEZwb1ZaUTkxdVJWdGJJZm1OQT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94092604895?pwd=Q2xoaEZw…> Meeting ID: 940 9260 4895 Passcode: tgV%6&8Sky One tap mobile +13126266799,,94092604895#,,,,*6566177428# US (Chicago) +19294362866,,94092604895#,,,,*6566177428# US (New York) Meeting ID: 940 9260 4895 Passcode: 6566177428 Find your local number: https://icann.zoom.us/u/aeinfg0MP7 <https://urldefense.com/v3/__https:/icann.zoom.us/u/aeinfg0MP7__;!!PtGJab4!p…> 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/jBV1Cw * Check your time zone: https://tinyurl.com/2p9saazz Thank you, Kind regards, Devan

1 0

15 MINUTES**REMINDER | Meeting Invitation | SOI Taskforce Meeting | Monday, 25 April 2022 at 20:00 UTC
by Devan Reed April 25, 2022

April 25, 2022

Dear all, The next SOI Taskforce meeting is scheduled on Monday, 25 April 2022 at 20:00 UTC for 60 minutes. Join Zoom Meeting: https://icann.zoom.us/j/94092604895?pwd=Q2xoaEZwb1ZaUTkxdVJWdGJJZm1OQT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94092604895?pwd=Q2xoaEZw…> Meeting ID: 940 9260 4895 Passcode: tgV%6&8Sky One tap mobile +13126266799,,94092604895#,,,,*6566177428# US (Chicago) +19294362866,,94092604895#,,,,*6566177428# US (New York) Meeting ID: 940 9260 4895 Passcode: 6566177428 Find your local number: https://icann.zoom.us/u/aeinfg0MP7 <https://urldefense.com/v3/__https:/icann.zoom.us/u/aeinfg0MP7__;!!PtGJab4!p…> 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/UgkiCw * Check your time zone: https://tinyurl.com/ycksv6t7<https://urldefense.com/v3/__https:/tinyurl.com/ycksv6t7__;!!PtGJab4!pzAH8zY…> Thank you, Kind regards, Devan

1 0

Proposed Agenda - SOI TF Meeting on Monday 25 April at 20.00 UTC
by Marika Konings April 24, 2022

April 24, 2022

Dear All, Hereby the proposed agenda for the next meeting which is scheduled for Monday 25 April at 20.00 UTC: 1. Welcome * Reminder – encourage participation in the outreach survey (https://engage.clicktools.com/v2/kakajko1rvzr#page1 – deadline for input 4 May) 2. Continue review of mind map (see attached) * Characteristics * Types of questions * Practical application * Other 3. Confirm next steps & next meeting (Monday 9 May at 13.00 UTC) Best regards, Julie and Marika From: Marika Konings <marika.konings(a)icann.org> Date: Thursday, 21 April 2022 at 15:12 To: "gnso-soi-tf(a)icann.org" <gnso-soi-tf(a)icann.org> Subject: Reminder: Re: [GNSO-SOI-TF] Updated mind map - Re: Action Items & Notes: SOI TF Meeting 11 April 2022 13:00 UTC Reminder, please review the mind map and provide comments and suggestions on characteristics, types of questions, practical application, and any other thoughts in preparation for the next meeting which is scheduled for Monday 25 April at 20.00 UTC. Thanks, Julie & Marika From: GNSO-SOI-TF <gnso-soi-tf-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Monday, 11 April 2022 at 16:50 To: Julie Hedlund <julie.hedlund(a)icann.org>, "gnso-soi-tf(a)icann.org" <gnso-soi-tf(a)icann.org> Subject: [GNSO-SOI-TF] Updated mind map - Re: Action Items & Notes: SOI TF Meeting 11 April 2022 13:00 UTC Dear All, For action item #2, please use the updated mind map that is attached here that aims to incorporate the feedback and suggestions made during today’s conversation. If you have further ideas or suggestions, please feel free to share this in advance of the next meeting with the mailing list. Thanks, Julie & Marika From: GNSO-SOI-TF <gnso-soi-tf-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Monday, 11 April 2022 at 16:09 To: "gnso-soi-tf(a)icann.org" <gnso-soi-tf(a)icann.org> Subject: [GNSO-SOI-TF] Action Items & Notes: SOI TF Meeting 11 April 2022 13:00 UTC Dear All, Please see below the action items and brief notes from today’s SOI Task Force meeting on Monday, 11 April 2022 at 13:00 UTC. These also are posted to the wiki at: https://community.icann.org/x/yYXOCg. Kind regards, Marika and Julie SOI Task Force Meeting Monday, 11 April 2022 at 13:00 UTC Action Items: 1. TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April. 2. TF members to review the mind map and provide comments and suggestions on characteristics, types of questions, practical application, and any other thoughts in preparation for the next meeting. 3. Staff to check with TF members about the days/timing of meetings to confirm participation. Notes: 1. Welcome/SOI Updates: * Susan Payne: Update to SOI<https://community.icann.org/display/gnsosoi/Susan+Payne+SOI>. * Need to reconfirm participation at the meeting times as attendance has been very light. * Sent out the request for input via the survey in the newsletter that goes to the SO/AC chairs. No responses yet. Reminder for TF members to alert the members of their groups of the request for input. Staff will also reach out to the support staff for the SOs/ACs. 2. Review of proposed timeline (see attached) * High-level timeline of steps. * A month for input on the SOIs, followed by the TF reviewing the input – timing will depend on responses received. * Factors in potential updates to the SOI. * Goal is to have a set of recommendations by end of June. * Any changes to the SOI in the GNSO Council Operating Procedures would need to go out for public comment, currently anticipated for July. Also alert the Council to the changes. * The proposed timeline is not set in stone and can be updated as necessary. * Not anticipated for the TF to meet in the Hague with priority to policy work and room restrictions. * TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April, following which the timeline will be shared with the CCOICI for reference. ACTION ITEM: TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April. 3. Continue consideration of assignment questions (see https://docs.google.com/document/d/1-mVupfkJF3e6S53oJb13XtyrqNuSt_8m/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1-mVupfkJF3e6…>) a. Consider any further input received on draft responses to question #1 and ideas / suggestions in response to question #2 Question #1: Is the original objective of the SOI, as stated in the BGC WG Report*, still valid? If not, why not and what should the current objective be? * Question #1 – purpose remains valid but updates may be needed. * Reminder: Action item for TF members to add questions to be posed to ICANN Legal. * Background on Declaration of Interest – was briefly a temporary procedure but was abandoned as being too complicated/onerous and did not serve its purpose. Could be useful to consider that experience when considering changes to the SOI. b. Brainstorm two types of SOI concept (see mind map attached) * On the left-hand side, an SOI that is activity specific to be filled out when undertaking a new activity; right-hand side is a general SOI that is static. * Define the draft characteristics for each type of SOI; TF members are requested to review these. * TF members to discuss how these two types of SOIs could be practically implemented once the TF has settled on the characteristics and questions. Discussion: * How would this translate into technical requirements to change the existing form. TF members should think about the types of use cases. What would this look like in the real world. Examples: in currently working groups – would the questions be answered differently for different groups – RPMs Phase 1 PDP, SubPro PDP, EPDP? How often would the group anticipate the SOIs would change from one person’s participation across a variety of policy topics. * Do think there would be differences in how people would respond. Examples: If you have a brand owner who sends a rep/employee, there would be some circumstances when they would be wearing the registry operator hat (such as on SubPro), but other times when they would be wearing their brand owner/protection hat, such as in RPMs Phase 1 PDP. Increasingly people are participating in multiple ways. * Multiple types of participation/hats could argue for having two types of SOIs, but need to think about what the questions would be for an activity-specific SOI. * Do think that if there are more targeted SOIs that starts to help; perhaps some tweaking to language is needed, but could provide guidance that goes along with the questions. There is a range of understanding of how much detail needs to be provided to the questions. People in similar circumstances may respond differently, based on their understanding. There is a lack of shared understanding concerning what is expected in answer to the questions. * Could have a modified template that provides a couple of scenarios as examples and expectations. * Education/guidance is a path to consider. In theory, the way the questions are of a general nature and the responses are free-form text, you could provide statements/details for each one of the policy initiatives in which you are participating – so using one form but allowing for responses for multiple activities – such as for RPMs, SubPro, etc. General = parent, specific = child. * The other use case to think about is if a community member goes from being a registry to registrar, that could change the dynamics in the participation – so updating both the general information as well as the specific. Could be the potential for increased amount of overhead. * Could be an automatic notification that if the general (parent) statement is changed then one is prodded to review the specific (child) statements for updates. * Provide guidance on expectations for detail as well as for changes to general versus specific statements. c. Confirm next steps ACTION ITEM: TF members to review the mind map and provide comments and suggestions on characteristics, types of questions, practical application, and any other thoughts in preparation for the next meeting. 4. Confirm next meeting – Monday 25 April at 20.00 UTC ACTION ITEM: Staff to check with TF members about the days/timing of meetings to confirm participation.

1 0

REMINDER | Meeting Invitation | SOI Taskforce Meeting | Monday, 25 April 2022 at 20:00 UTC
by Devan Reed April 22, 2022

April 22, 2022

Dear all, The next SOI Taskforce meeting is scheduled on Monday, 25 April 2022 at 20:00 UTC for 60 minutes. Join Zoom Meeting: https://icann.zoom.us/j/94092604895?pwd=Q2xoaEZwb1ZaUTkxdVJWdGJJZm1OQT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94092604895?pwd=Q2xoaEZw…> Meeting ID: 940 9260 4895 Passcode: tgV%6&8Sky One tap mobile +13126266799,,94092604895#,,,,*6566177428# US (Chicago) +19294362866,,94092604895#,,,,*6566177428# US (New York) Meeting ID: 940 9260 4895 Passcode: 6566177428 Find your local number: https://icann.zoom.us/u/aeinfg0MP7 <https://urldefense.com/v3/__https:/icann.zoom.us/u/aeinfg0MP7__;!!PtGJab4!p…> 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/UgkiCw * Check your time zone: https://tinyurl.com/ycksv6t7<https://urldefense.com/v3/__https:/tinyurl.com/ycksv6t7__;!!PtGJab4!pzAH8zY…> Thank you, Kind regards, Devan

1 0

Reminder: Re: Updated mind map - Re: Action Items & Notes: SOI TF Meeting 11 April 2022 13:00 UTC
by Marika Konings April 21, 2022

April 21, 2022

Reminder, please review the mind map and provide comments and suggestions on characteristics, types of questions, practical application, and any other thoughts in preparation for the next meeting which is scheduled for Monday 25 April at 20.00 UTC. Thanks, Julie & Marika From: GNSO-SOI-TF <gnso-soi-tf-bounces(a)icann.org> on behalf of Marika Konings <marika.konings(a)icann.org> Date: Monday, 11 April 2022 at 16:50 To: Julie Hedlund <julie.hedlund(a)icann.org>, "gnso-soi-tf(a)icann.org" <gnso-soi-tf(a)icann.org> Subject: [GNSO-SOI-TF] Updated mind map - Re: Action Items & Notes: SOI TF Meeting 11 April 2022 13:00 UTC Dear All, For action item #2, please use the updated mind map that is attached here that aims to incorporate the feedback and suggestions made during today’s conversation. If you have further ideas or suggestions, please feel free to share this in advance of the next meeting with the mailing list. Thanks, Julie & Marika From: GNSO-SOI-TF <gnso-soi-tf-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Monday, 11 April 2022 at 16:09 To: "gnso-soi-tf(a)icann.org" <gnso-soi-tf(a)icann.org> Subject: [GNSO-SOI-TF] Action Items & Notes: SOI TF Meeting 11 April 2022 13:00 UTC Dear All, Please see below the action items and brief notes from today’s SOI Task Force meeting on Monday, 11 April 2022 at 13:00 UTC. These also are posted to the wiki at: https://community.icann.org/x/yYXOCg. Kind regards, Marika and Julie SOI Task Force Meeting Monday, 11 April 2022 at 13:00 UTC Action Items: 1. TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April. 2. TF members to review the mind map and provide comments and suggestions on characteristics, types of questions, practical application, and any other thoughts in preparation for the next meeting. 3. Staff to check with TF members about the days/timing of meetings to confirm participation. Notes: 1. Welcome/SOI Updates: * Susan Payne: Update to SOI<https://community.icann.org/display/gnsosoi/Susan+Payne+SOI>. * Need to reconfirm participation at the meeting times as attendance has been very light. * Sent out the request for input via the survey in the newsletter that goes to the SO/AC chairs. No responses yet. Reminder for TF members to alert the members of their groups of the request for input. Staff will also reach out to the support staff for the SOs/ACs. 2. Review of proposed timeline (see attached) * High-level timeline of steps. * A month for input on the SOIs, followed by the TF reviewing the input – timing will depend on responses received. * Factors in potential updates to the SOI. * Goal is to have a set of recommendations by end of June. * Any changes to the SOI in the GNSO Council Operating Procedures would need to go out for public comment, currently anticipated for July. Also alert the Council to the changes. * The proposed timeline is not set in stone and can be updated as necessary. * Not anticipated for the TF to meet in the Hague with priority to policy work and room restrictions. * TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April, following which the timeline will be shared with the CCOICI for reference. ACTION ITEM: TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April. 3. Continue consideration of assignment questions (see https://docs.google.com/document/d/1-mVupfkJF3e6S53oJb13XtyrqNuSt_8m/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1-mVupfkJF3e6…>) a. Consider any further input received on draft responses to question #1 and ideas / suggestions in response to question #2 Question #1: Is the original objective of the SOI, as stated in the BGC WG Report*, still valid? If not, why not and what should the current objective be? * Question #1 – purpose remains valid but updates may be needed. * Reminder: Action item for TF members to add questions to be posed to ICANN Legal. * Background on Declaration of Interest – was briefly a temporary procedure but was abandoned as being too complicated/onerous and did not serve its purpose. Could be useful to consider that experience when considering changes to the SOI. b. Brainstorm two types of SOI concept (see mind map attached) * On the left-hand side, an SOI that is activity specific to be filled out when undertaking a new activity; right-hand side is a general SOI that is static. * Define the draft characteristics for each type of SOI; TF members are requested to review these. * TF members to discuss how these two types of SOIs could be practically implemented once the TF has settled on the characteristics and questions. Discussion: * How would this translate into technical requirements to change the existing form. TF members should think about the types of use cases. What would this look like in the real world. Examples: in currently working groups – would the questions be answered differently for different groups – RPMs Phase 1 PDP, SubPro PDP, EPDP? How often would the group anticipate the SOIs would change from one person’s participation across a variety of policy topics. * Do think there would be differences in how people would respond. Examples: If you have a brand owner who sends a rep/employee, there would be some circumstances when they would be wearing the registry operator hat (such as on SubPro), but other times when they would be wearing their brand owner/protection hat, such as in RPMs Phase 1 PDP. Increasingly people are participating in multiple ways. * Multiple types of participation/hats could argue for having two types of SOIs, but need to think about what the questions would be for an activity-specific SOI. * Do think that if there are more targeted SOIs that starts to help; perhaps some tweaking to language is needed, but could provide guidance that goes along with the questions. There is a range of understanding of how much detail needs to be provided to the questions. People in similar circumstances may respond differently, based on their understanding. There is a lack of shared understanding concerning what is expected in answer to the questions. * Could have a modified template that provides a couple of scenarios as examples and expectations. * Education/guidance is a path to consider. In theory, the way the questions are of a general nature and the responses are free-form text, you could provide statements/details for each one of the policy initiatives in which you are participating – so using one form but allowing for responses for multiple activities – such as for RPMs, SubPro, etc. General = parent, specific = child. * The other use case to think about is if a community member goes from being a registry to registrar, that could change the dynamics in the participation – so updating both the general information as well as the specific. Could be the potential for increased amount of overhead. * Could be an automatic notification that if the general (parent) statement is changed then one is prodded to review the specific (child) statements for updates. * Provide guidance on expectations for detail as well as for changes to general versus specific statements. c. Confirm next steps ACTION ITEM: TF members to review the mind map and provide comments and suggestions on characteristics, types of questions, practical application, and any other thoughts in preparation for the next meeting. 4. Confirm next meeting – Monday 25 April at 20.00 UTC ACTION ITEM: Staff to check with TF members about the days/timing of meetings to confirm participation.

1 0

SOI Task Force meeting
by ICANN Policy Calendar April 11, 2022

April 11, 2022

Meeting: SOI Task Force meeting Date: Monday, 06 June 2022 at 13:00 UTC for 60 minutes Join Zoom Meeting: https://icann.zoom.us/j/94092604895?pwd=Q2xoaEZwb1ZaUTkxdVJWdGJJZm1OQT09 Meeting ID: 940 9260 4895 Passcode: tgV%6&8SKy One tap mobile +13126266799,,94092604895#,,,,*6566177428# US (Chicago) +19294362866,,94092604895#,,,,*6566177428# US (New York) Meeting ID: 940 9260 4895 Passcode: 6566177428 Find your local number: https://icann.zoom.us/u/aeinfg0MP7 <https://urldefense.com/v3/__https:/icann.zoom.us/u/aeinfg0MP7__;!!PtGJab4!u…> 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…> 11 April at 13:00 UTC Wiki Agenda Page: https://community.icann.org/x/kBV1Cw Check your time zone: https://tinyurl.com/5b6ynsx9

1 0

SOI Task Force meeting
by ICANN Policy Calendar April 11, 2022

April 11, 2022

Meeting: SOI Task Force meeting Date: Monday, 23 May 2022 at 20:00 UTC for 60 minutes Join Zoom Meeting: https://icann.zoom.us/j/94092604895?pwd=Q2xoaEZwb1ZaUTkxdVJWdGJJZm1OQT09 Meeting ID: 940 9260 4895 Passcode: tgV%6&8SKy One tap mobile +13126266799,,94092604895#,,,,*6566177428# US (Chicago) +19294362866,,94092604895#,,,,*6566177428# US (New York) Meeting ID: 940 9260 4895 Passcode: 6566177428 Find your local number: https://icann.zoom.us/u/aeinfg0MP7 <https://urldefense.com/v3/__https:/icann.zoom.us/u/aeinfg0MP7__;!!PtGJab4!u…> 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…> 25 April at 20:00 UTC Wiki Agenda Page: https://community.icann.org/x/jhV1Cw Check your time zone: https://tinyurl.com/2ef7w45j

1 0

SOI Task Force meeting
by ICANN Policy Calendar April 11, 2022

April 11, 2022

Meeting: SOI Task Force meeting Date: Monday, 09 May 2022 at 13:00 UTC for 60 minutes Join Zoom Meeting: https://icann.zoom.us/j/94092604895?pwd=Q2xoaEZwb1ZaUTkxdVJWdGJJZm1OQT09 Meeting ID: 940 9260 4895 Passcode: tgV%6&8SKy One tap mobile +13126266799,,94092604895#,,,,*6566177428# US (Chicago) +19294362866,,94092604895#,,,,*6566177428# US (New York) Meeting ID: 940 9260 4895 Passcode: 6566177428 Find your local number: https://icann.zoom.us/u/aeinfg0MP7 <https://urldefense.com/v3/__https:/icann.zoom.us/u/aeinfg0MP7__;!!PtGJab4!u…> 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…> 11 April at 13:00 UTC Wiki Agenda Page: https://community.icann.org/x/jBV1Cw Check your time zone: https://tinyurl.com/2p9saazz

1 0

Updated mind map - Re: Action Items & Notes: SOI TF Meeting 11 April 2022 13:00 UTC
by Marika Konings April 11, 2022

April 11, 2022

Dear All, For action item #2, please use the updated mind map that is attached here that aims to incorporate the feedback and suggestions made during today’s conversation. If you have further ideas or suggestions, please feel free to share this in advance of the next meeting with the mailing list. Thanks, Julie & Marika From: GNSO-SOI-TF <gnso-soi-tf-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Monday, 11 April 2022 at 16:09 To: "gnso-soi-tf(a)icann.org" <gnso-soi-tf(a)icann.org> Subject: [GNSO-SOI-TF] Action Items & Notes: SOI TF Meeting 11 April 2022 13:00 UTC Dear All, Please see below the action items and brief notes from today’s SOI Task Force meeting on Monday, 11 April 2022 at 13:00 UTC. These also are posted to the wiki at: https://community.icann.org/x/yYXOCg. Kind regards, Marika and Julie SOI Task Force Meeting Monday, 11 April 2022 at 13:00 UTC Action Items: 1. TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April. 2. TF members to review the mind map and provide comments and suggestions on characteristics, types of questions, practical application, and any other thoughts in preparation for the next meeting. 3. Staff to check with TF members about the days/timing of meetings to confirm participation. Notes: 1. Welcome/SOI Updates: * Susan Payne: Update to SOI<https://community.icann.org/display/gnsosoi/Susan+Payne+SOI>. * Need to reconfirm participation at the meeting times as attendance has been very light. * Sent out the request for input via the survey in the newsletter that goes to the SO/AC chairs. No responses yet. Reminder for TF members to alert the members of their groups of the request for input. Staff will also reach out to the support staff for the SOs/ACs. 2. Review of proposed timeline (see attached) * High-level timeline of steps. * A month for input on the SOIs, followed by the TF reviewing the input – timing will depend on responses received. * Factors in potential updates to the SOI. * Goal is to have a set of recommendations by end of June. * Any changes to the SOI in the GNSO Council Operating Procedures would need to go out for public comment, currently anticipated for July. Also alert the Council to the changes. * The proposed timeline is not set in stone and can be updated as necessary. * Not anticipated for the TF to meet in the Hague with priority to policy work and room restrictions. * TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April, following which the timeline will be shared with the CCOICI for reference. ACTION ITEM: TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April. 3. Continue consideration of assignment questions (see https://docs.google.com/document/d/1-mVupfkJF3e6S53oJb13XtyrqNuSt_8m/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1-mVupfkJF3e6…>) a. Consider any further input received on draft responses to question #1 and ideas / suggestions in response to question #2 Question #1: Is the original objective of the SOI, as stated in the BGC WG Report*, still valid? If not, why not and what should the current objective be? * Question #1 – purpose remains valid but updates may be needed. * Reminder: Action item for TF members to add questions to be posed to ICANN Legal. * Background on Declaration of Interest – was briefly a temporary procedure but was abandoned as being too complicated/onerous and did not serve its purpose. Could be useful to consider that experience when considering changes to the SOI. b. Brainstorm two types of SOI concept (see mind map attached) * On the left-hand side, an SOI that is activity specific to be filled out when undertaking a new activity; right-hand side is a general SOI that is static. * Define the draft characteristics for each type of SOI; TF members are requested to review these. * TF members to discuss how these two types of SOIs could be practically implemented once the TF has settled on the characteristics and questions. Discussion: * How would this translate into technical requirements to change the existing form. TF members should think about the types of use cases. What would this look like in the real world. Examples: in currently working groups – would the questions be answered differently for different groups – RPMs Phase 1 PDP, SubPro PDP, EPDP? How often would the group anticipate the SOIs would change from one person’s participation across a variety of policy topics. * Do think there would be differences in how people would respond. Examples: If you have a brand owner who sends a rep/employee, there would be some circumstances when they would be wearing the registry operator hat (such as on SubPro), but other times when they would be wearing their brand owner/protection hat, such as in RPMs Phase 1 PDP. Increasingly people are participating in multiple ways. * Multiple types of participation/hats could argue for having two types of SOIs, but need to think about what the questions would be for an activity-specific SOI. * Do think that if there are more targeted SOIs that starts to help; perhaps some tweaking to language is needed, but could provide guidance that goes along with the questions. There is a range of understanding of how much detail needs to be provided to the questions. People in similar circumstances may respond differently, based on their understanding. There is a lack of shared understanding concerning what is expected in answer to the questions. * Could have a modified template that provides a couple of scenarios as examples and expectations. * Education/guidance is a path to consider. In theory, the way the questions are of a general nature and the responses are free-form text, you could provide statements/details for each one of the policy initiatives in which you are participating – so using one form but allowing for responses for multiple activities – such as for RPMs, SubPro, etc. General = parent, specific = child. * The other use case to think about is if a community member goes from being a registry to registrar, that could change the dynamics in the participation – so updating both the general information as well as the specific. Could be the potential for increased amount of overhead. * Could be an automatic notification that if the general (parent) statement is changed then one is prodded to review the specific (child) statements for updates. * Provide guidance on expectations for detail as well as for changes to general versus specific statements. c. Confirm next steps ACTION ITEM: TF members to review the mind map and provide comments and suggestions on characteristics, types of questions, practical application, and any other thoughts in preparation for the next meeting. 4. Confirm next meeting – Monday 25 April at 20.00 UTC ACTION ITEM: Staff to check with TF members about the days/timing of meetings to confirm participation.

1 0

Post Call | Statement of Interest Task Force | Monday, 11 April 2022
by Devan Reed April 11, 2022

April 11, 2022

Dear all, All recordings for the Statement of Interest Task Force call held on Monday, 11 April 2022 at 13:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/UAkiCw> (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) For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/gnso-soi-tf/> and the main wiki page.<https://community.icann.org/x/yYXOCg> Thank you. Kind regards Devan

1 0

Meeting Invitation | SOI Taskforce Meeting | Monday, 25 April 2022 at 20:00 UTC
by Devan Reed April 11, 2022

April 11, 2022

Dear all, The next SOI Taskforce meeting is scheduled on Monday, 25 April 2022 at 20:00 UTC for 60 minutes. Join Zoom Meeting: https://icann.zoom.us/j/94092604895?pwd=Q2xoaEZwb1ZaUTkxdVJWdGJJZm1OQT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94092604895?pwd=Q2xoaEZw…> Meeting ID: 940 9260 4895 Passcode: tgV%6&8Sky One tap mobile +13126266799,,94092604895#,,,,*6566177428# US (Chicago) +19294362866,,94092604895#,,,,*6566177428# US (New York) Meeting ID: 940 9260 4895 Passcode: 6566177428 Find your local number: https://icann.zoom.us/u/aeinfg0MP7 <https://urldefense.com/v3/__https:/icann.zoom.us/u/aeinfg0MP7__;!!PtGJab4!p…> 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/UgkiCw * Check your time zone: https://tinyurl.com/ycksv6t7 Thank you, Kind regards, Devan

1 0

Action Items & Notes: SOI TF Meeting 11 April 2022 13:00 UTC
by Julie Hedlund April 11, 2022

April 11, 2022

Dear All, Please see below the action items and brief notes from today’s SOI Task Force meeting on Monday, 11 April 2022 at 13:00 UTC. These also are posted to the wiki at: https://community.icann.org/x/yYXOCg. Kind regards, Marika and Julie SOI Task Force Meeting Monday, 11 April 2022 at 13:00 UTC Action Items: 1. TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April. 2. TF members to review the mind map and provide comments and suggestions on characteristics, types of questions, practical application, and any other thoughts in preparation for the next meeting. 3. Staff to check with TF members about the days/timing of meetings to confirm participation. Notes: 1. Welcome/SOI Updates: * Susan Payne: Update to SOI<https://community.icann.org/display/gnsosoi/Susan+Payne+SOI>. * Need to reconfirm participation at the meeting times as attendance has been very light. * Sent out the request for input via the survey in the newsletter that goes to the SO/AC chairs. No responses yet. Reminder for TF members to alert the members of their groups of the request for input. Staff will also reach out to the support staff for the SOs/ACs. 2. Review of proposed timeline (see attached) * High-level timeline of steps. * A month for input on the SOIs, followed by the TF reviewing the input – timing will depend on responses received. * Factors in potential updates to the SOI. * Goal is to have a set of recommendations by end of June. * Any changes to the SOI in the GNSO Council Operating Procedures would need to go out for public comment, currently anticipated for July. Also alert the Council to the changes. * The proposed timeline is not set in stone and can be updated as necessary. * Not anticipated for the TF to meet in the Hague with priority to policy work and room restrictions. * TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April, following which the timeline will be shared with the CCOICI for reference. ACTION ITEM: TF members to review the proposed timeline and provide comments, if any, by Friday, 15 April. 3. Continue consideration of assignment questions (see https://docs.google.com/document/d/1-mVupfkJF3e6S53oJb13XtyrqNuSt_8m/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1-mVupfkJF3e6…>) a. Consider any further input received on draft responses to question #1 and ideas / suggestions in response to question #2 Question #1: Is the original objective of the SOI, as stated in the BGC WG Report*, still valid? If not, why not and what should the current objective be? * Question #1 – purpose remains valid but updates may be needed. * Reminder: Action item for TF members to add questions to be posed to ICANN Legal. * Background on Declaration of Interest – was briefly a temporary procedure but was abandoned as being too complicated/onerous and did not serve its purpose. Could be useful to consider that experience when considering changes to the SOI. b. Brainstorm two types of SOI concept (see mind map attached) * On the left-hand side, an SOI that is activity specific to be filled out when undertaking a new activity; right-hand side is a general SOI that is static. * Define the draft characteristics for each type of SOI; TF members are requested to review these. * TF members to discuss how these two types of SOIs could be practically implemented once the TF has settled on the characteristics and questions. Discussion: * How would this translate into technical requirements to change the existing form. TF members should think about the types of use cases. What would this look like in the real world. Examples: in currently working groups – would the questions be answered differently for different groups – RPMs Phase 1 PDP, SubPro PDP, EPDP? How often would the group anticipate the SOIs would change from one person’s participation across a variety of policy topics. * Do think there would be differences in how people would respond. Examples: If you have a brand owner who sends a rep/employee, there would be some circumstances when they would be wearing the registry operator hat (such as on SubPro), but other times when they would be wearing their brand owner/protection hat, such as in RPMs Phase 1 PDP. Increasingly people are participating in multiple ways. * Multiple types of participation/hats could argue for having two types of SOIs, but need to think about what the questions would be for an activity-specific SOI. * Do think that if there are more targeted SOIs that starts to help; perhaps some tweaking to language is needed, but could provide guidance that goes along with the questions. There is a range of understanding of how much detail needs to be provided to the questions. People in similar circumstances may respond differently, based on their understanding. There is a lack of shared understanding concerning what is expected in answer to the questions. * Could have a modified template that provides a couple of scenarios as examples and expectations. * Education/guidance is a path to consider. In theory, the way the questions are of a general nature and the responses are free-form text, you could provide statements/details for each one of the policy initiatives in which you are participating – so using one form but allowing for responses for multiple activities – such as for RPMs, SubPro, etc. General = parent, specific = child. * The other use case to think about is if a community member goes from being a registry to registrar, that could change the dynamics in the participation – so updating both the general information as well as the specific. Could be the potential for increased amount of overhead. * Could be an automatic notification that if the general (parent) statement is changed then one is prodded to review the specific (child) statements for updates. * Provide guidance on expectations for detail as well as for changes to general versus specific statements. c. Confirm next steps ACTION ITEM: TF members to review the mind map and provide comments and suggestions on characteristics, types of questions, practical application, and any other thoughts in preparation for the next meeting. 4. Confirm next meeting – Monday 25 April at 20.00 UTC ACTION ITEM: Staff to check with TF members about the days/timing of meetings to confirm participation.

1 0

15 MINUTES **REMINDER** Meeting Invitation | SOI Taskforce Meeting | Monday, 11 April 2022 at 13:00 UTC
by Devan Reed April 11, 2022

April 11, 2022

Dear all, The next SOI Taskforce meeting is scheduled on Monday, 11 April 2022 at 13:00 UTC for 60 minutes. Join Zoom Meeting: https://icann.zoom.us/j/94092604895?pwd=Q2xoaEZwb1ZaUTkxdVJWdGJJZm1OQT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94092604895?pwd=Q2xoaEZw…> Meeting ID: 940 9260 4895 Passcode: tgV%6&8Sky One tap mobile +13126266799,,94092604895#,,,,*6566177428# US (Chicago) +19294362866,,94092604895#,,,,*6566177428# US (New York) Meeting ID: 940 9260 4895 Passcode: 6566177428 Find your local number: https://icann.zoom.us/u/aeinfg0MP7 <https://urldefense.com/v3/__https:/icann.zoom.us/u/aeinfg0MP7__;!!PtGJab4!p…> 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/UAkiCw * Check your time zone: https://tinyurl.com/2p94924k [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2p94924k__;!!PtGJab4!u-exuQk…> Thank you, Kind regards, Devan

1 0

**REMINDER** Meeting Invitation | SOI Taskforce Meeting | Monday, 11 April 2022 at 13:00 UTC
by Julie Bisland April 8, 2022

April 8, 2022

Dear all, The next SOI Taskforce meeting is scheduled on Monday, 11 April 2022 at 13:00 UTC for 60 minutes. Join Zoom Meeting: https://icann.zoom.us/j/94092604895?pwd=Q2xoaEZwb1ZaUTkxdVJWdGJJZm1OQT09 <https://urldefense.com/v3/__https:/icann.zoom.us/j/94092604895?pwd=Q2xoaEZw…> Meeting ID: 940 9260 4895 Passcode: tgV%6&8Sky One tap mobile +13126266799,,94092604895#,,,,*6566177428# US (Chicago) +19294362866,,94092604895#,,,,*6566177428# US (New York) Meeting ID: 940 9260 4895 Passcode: 6566177428 Find your local number: https://icann.zoom.us/u/aeinfg0MP7 <https://urldefense.com/v3/__https:/icann.zoom.us/u/aeinfg0MP7__;!!PtGJab4!p…> 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/UAkiCw * Check your time zone: https://tinyurl.com/2p94924k [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2p94924k__;!!PtGJab4!u-exuQk…> Thank you, Kind regards, Devan

1 0

Proposed Agenda - GNSO SOI TF meeting on Monday 10 April at 13.00 UTC
by Marika Konings April 8, 2022

April 8, 2022

Dear All, Hereby the proposed agenda and materials for Monday’s SOI TF meeting. Please note that for agenda item 3b you will find attached a mind map that is intended to facilitate the discussion on a possible two types of SOI approach that has been suggested. At the moment, the mind map uses the questions of the current SOI but of course, it is up to the group to decide if/how these are to be modified and/or what other questions should be added. If you already have any specific ideas or suggestions, please feel free to share those in advance of the meeting. Proposed Agenda - GNSO SOI TF Meeting on Monday 10 April at 13.00 UTC 1. Welcome 2. Review of proposed timeline (see attached) 3. Continue consideration of assignment questions (see https://docs.google.com/document/d/1-mVupfkJF3e6S53oJb13XtyrqNuSt_8m/edit) * Consider any further input received on draft response to question #1 and ideas / suggestions in response to question #2 * Brainstorm two types of SOI concept (see mind map attached) * Confirm next steps 4. Confirm next meeting – Monday 25 April at 20.00 UTC If you have any edits or suggestions for the agenda, please feel free to share those. Best regards, Julie and Marika

1 0

Reminder - Action Items & Notes: SOI TF Meeting 28 March 2022 20:00 UTC
by Marika Konings April 6, 2022

April 6, 2022

Reminder, especially for those that were not able to make the last meeting, please review the google doc (see https://docs.google.com/document/d/1-mVupfkJF3e6S53oJb13XtyrqNuSt_8m/edit) and in particular the text highlighted in yellow to see if it aligns with the discussions to date and the direction the SOI TF should pursue further. Feel free to add any comments you may have. Note that on page 4 you also have the ability to add further legal questions for consideration. Best regards, Julie and Marika From: GNSO-SOI-TF <gnso-soi-tf-bounces(a)icann.org> on behalf of Julie Hedlund <julie.hedlund(a)icann.org> Date: Monday, 28 March 2022 at 23:04 To: "gnso-soi-tf(a)icann.org" <gnso-soi-tf(a)icann.org> Subject: [GNSO-SOI-TF] Action Items & Notes: SOI TF Meeting 28 March 2022 20:00 UTC Dear All, Please see below the action items and brief notes from today’s SOI Task Force meeting on Monday, 28 March 2022 at 20:00 UTC. These also are posted to the wiki at: https://community.icann.org/x/yYXOCg. Kind regards, Marika and Julie SOI Task Force Meeting Monday, 28 March 2022 at 20:00 UTC Action Items: Proposed Outreach Letter: 1. TF members to review the google doc of the outreach letter/questions at https://docs.google.com/document/d/1XWMzLILrfdjNE1jgUaOQ5Nc0f34GHdBS/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1XWMzLILrfdjN…> and provide comments and suggestions. 2. Staff to turn the outreach inquiry into a survey preview with open-ended text boxes for SOI TF members to review. TF Assignment questions (https://docs.google.com/document/d/1-mVupfkJF3e6S53oJb13XtyrqNuSt_8m/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1-mVupfkJF3e6…> 1. TF members to review the google doc of the TF Assignment questions at https://docs.google.com/document/d/1-mVupfkJF3e6S53oJb13XtyrqNuSt_8m/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1-mVupfkJF3e6…> and provide comments and suggestions. 2. Staff to draft a timeline for the assignment. 3. Staff to create a Google doc for TF members to contribute to a list of questions to pose to ICANN Org Legal staff. Notes: 1. Welcome 2. Proposed outreach letter (see https://docs.google.com/document/d/1XWMzLILrfdjNE1jgUaOQ5Nc0f34GHdBS/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1XWMzLILrfdjN…>) a. TF input & comments * As part of the assignment the group has been asked to reach out to other groups who may use the SOI for their own processes or for GNSO groups in which they participate. * Start out with some general information. Discussion/Comments: * This this is too broad -- think there are other reasons than financial and being affected. We might want to provide some specifics in the form of bullet points. Specifically this, “either directly in the sense that the person conducts business which could be affected by GNSO policy decisions or indirectly as a representative of a group that could be affected). Wonder if there are other reasons other than financial. * Note that the text in parentheses above is directly pasted from the BGC report, but the group can make the questions more specific. We’ll probably need to write out what this report is and provide a link to make clear where it comes from. * Maybe when we start looking at the questions about how the SOI can be revised, such as with specific examples. Specifically to get information on interests that might be related to a specific outcome. Not sure how to translate that into questions for outreach. May be additional questions that need to be identified. * For the outreach we are focusing on what we want the outreach responses to focus on. * We are also asking how revising the SOI might impact their own groups. Some use the SOI for their own purposes. Particularly those who are not in the GNSO. * One suggestion staff had was to turn this into a survey format. Staff could do that and share with the group to review. * We aren’t looking for formal SO/AC responses. * Prefer the idea of this being a survey, but recommend that we leave some open-ended text boxes. * On the timeline, not sure what our timeframe is. Sooner is better. * There is no set timeframe; it really depends on the time the group puts in and the progress made. * Staff can set out a general timeline. * Check to see if this is suitable for the Community Digest. * Allow more time for the TF members to review. b. Confirm next steps ACTION ITEM: TF members to review the google doc of the outreach letter/questions and provide comments and suggestions. ACTION ITEM: Staff to turn the outreach inquiry into a survey preview with open-ended text boxes for SOI TF members to review. 3. Continue consideration of TF Assignment questions (https://docs.google.com/document/d/1-mVupfkJF3e6S53oJb13XtyrqNuSt_8m/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1-mVupfkJF3e6…>) Question #2: Based on the response to question 1), is the requested information** to be provided as part of the SOI still fit for purpose? If not, why not, and what would need to be changed to make it fit for purpose? * Created a placeholder for additional questions. * Potential questions to be addressed: * If/how can a community member be compelled to disclose clients, especially in the case where there might be an NDA and/or client-attorney type of relationship? * [TF to identify additional questions] * May be ways around an NDA in the way the questions are presented; the TF would have to address that. * Addressed the issue of two types of Statements of Interest, including research a short-lived option for a Declaration of Interest. Ended up being very cumbersome, complex, and time-consuming so the requirement was eliminated from the final version of the GNSO Operating Procedures. * Given the above history and the usefulness of having a trial run of processes, staff suggests that the SOI TF could consider recommending testing draft SOI procedures on a set of volunteers acting as WG members, and then seeing whether the responses are useful/expected. * Would be good to have more information in an SOI on specific interests in a WG, such as tying it to charter questions. What outcomes they are seeking. * Something to think about is what the new environment looks like, and what are the current requirements and how do they need to be updated. ACTION ITEM: TF members to review the google doc of the TF Assignment questions at https://docs.google.com/document/d/1-mVupfkJF3e6S53oJb13XtyrqNuSt_8m/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1-mVupfkJF3e6…> and provide comments and suggestions. ACTION ITEM: Staff to draft a timeline for the assignment. 4. Confirm next steps & next meeting (11 April at 13.00 UTC)

1 0

FW: [Ext] Monday, 4 April 2022 | 📣 Register for the ICANN74 Policy Forum in The Hague, Netherlands 📣
by Marika Konings April 4, 2022

April 4, 2022

FYI, the request for input on the GNSO SOI has been included in today’s Community Digest. You are also encouraged to share the survey link with your respective groups as there may be further input that may help inform the TF’s deliberations. Best regards, Julie and Marika From: David Olive <david.olive(a)icann.org> Reply to: "policyinfo(a)icann.org" <policyinfo(a)icann.org> Date: Monday, 4 April 2022 at 17:02 To: Marika Konings <marika.konings(a)icann.org> Subject: [Ext] Monday, 4 April 2022 | 📣 Register for the ICANN74 Policy Forum in The Hague, Netherlands 📣 [https://r20.rs6.net/on.jsp?ca=8d4e8b40-a5a5-445c-9ff1-fc37a6eb3ca8&a=112202…] Monday, 4 April 2022 ICANN Community Digest [https://files.constantcontact.com/304b3fd3501/31f30ab5-1445-45c3-aef7-c0ea4…] The ICANN org Policy Development Support function publishes this twice-weekly digest to help ICANN community leaders track requests and follow updates. How Domain Name System Policy is Developed, and How You Can Get Involved [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> Table of Contents ICANN74 · NEW: Design/Translation/Print Deadlines · NEW: Registration for ICANN74 Policy Forum in The Hague, Netherlands is Now Open Webinars · NEXT WEEK: ICANN Hosts Webinar on UN and ITU Discussions Affecting the Internet Information Sharing · NEW: Request for Input-GNSO's Statement of Interest · REMINDER: ICANN's 2022 Middle East DNS Forum to Take Place Virtually in May Public Comment · Policy Status Report: Uniform Domain Name Dispute Resolution Policy (UDRP) · Root Zone Update Process Study · Root Zone Label Generation Rules Version 5 (RZ-LGR-5) ICANN74 Resources NEW: Design/Translation/Print Deadlines FRIDAY, 8 APRIL 2022: DESIGN DEADLINE. If you require design assistance for your publication, you need to provide all the text, images, layout, and publication type/size requirements (i.e. newsletter vs. 1-pager vs. trifold, etc.). You will receive a maximum of 2 iterations of the publication. Please provide everything by Friday, 8 April. Due to budget constraints, please keep in mind that all materials, new or updated, need to be evergreen. FRIDAY, 29 APRIL 2022: TRANSLATION DEADLINE. If your publication requires translation, please provide the final material(s) by Friday, 29 April. This ensures that there is enough time to translate the publication by the below print deadline. If your materials require design assistance (outlined above), please note that the final materials will have to be complete, including the edit/approval process, by this deadline in order to be translated. FRIDAY, 6 MAY 2022: PRINT DEADLINE ONLY. If you only need your publication printed, meaning your publication is ready to send directly to the printer and needs no translation or design/layout modifications, please provide the file to us along with the quantity you want printed and dimensions of the publication by Friday, 6 May. Please send materials to chantelle.doerksen(a)icann.org<mailto:chantelle.doerksen@icann.org>. NEW: Registration for ICANN74 Policy Forum in The Hague, Netherlands is Now Open Registration [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> for ICANN74 (13-16 June 2022) in The Hague, Netherlands is now open. ICANN74 will take place as a hybrid event to accommodate both in-person and virtual participation. While the ICANN74 Policy Forum [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> presents the first opportunity for the community to come together in more than two years, the health and safety of all community members and staff continues to be ICANN's key priority. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…>Read more [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…>. Webinars NEXT WEEK: ICANN Hosts Webinar on UN and ITU Discussions Affecting the Internet ICANN has announced that it will hold a webinar on issues impacting the Internet that are being discussed at the United Nations (U.N.) and the International Telecommunication Union (ITU). The event will take place on Tuesday, 12 April 2022 at 20:00 UTC. Please register [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> for the webinar. Information Sharing NEW: Request for Input-GNSO's Statement of Interest The GNSO Council has recently embarked on a review of its Statement of Interest (SOI) requirements to determine whether these are still fit for purpose, and if not, what updates should be considered. To this end, the GNSO SOI Task Force (TF) was formed. As part of its assignment, the TF is reaching out to the ICANN community to solicit input on the current use and experience with SOIs as well as suggestions for possible improvements. We understand that some of you may use the SOI, either in its current form or a modified format, for your own purposes. We would be interested to hear about those experiences as well as any lessons learned that may help inform our recommendations. You are encouraged to share this information with your respective groups. To provide input, please complete the following survey [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> by 4 May at the latest. Your input will be much appreciated! REMINDER: ICANN's 2022 Middle East DNS Forum to Take Place Virtually in May ICANN org's eighth Middle East Domain Name System (DNS) Forum will take place virtually from Monday-Wednesday, 16-18 May 2022 and will offer a closer look at the evolving DNS ecosystem from a technical and policy perspective. It will have a special focus on regional challenges and opportunities for growth. Read more. [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> Public Comment Policy Status Report: Uniform Domain Name Dispute Resolution Policy (UDRP) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> Open for Submissions Date: Thursday, 03 March 2022 Closed for Submissions Date: Tuesday, 19 April 2022 Root Zone Update Process Study [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> Open for Submissions Date: Monday, 14 March 2022 Closed for Submissions Date: Monday, 25 April 2022 Root Zone Label Generation Rules Version 5 (RZ-LGR-5) [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> Open for Submissions Date: Thursday, 24 March 2022 Closed for Submissions Date: Thursday, 05 May 2022 See upcoming proceedings [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…>. See other public consultations [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…>. Volume 4, Issue 25 | Archive [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> | Next Issue: Thursday, 7 April 2022 STAY INFORMED: Subscribe here [r20.rs6.net]<https://urldefense.com/v3/__https:/r20.rs6.net/tn.jsp?f=001416spojESJ3NtIdO…> ICANN | 12025 Waterfront Drive, Suite 300, Los Angeles, CA 90094-2536 Unsubscribe marika.konings(a)icann.org [visitor.constantcontact.com]<https://urldefense.com/v3/__https:/visitor.constantcontact.com/do?p=un&m=00…> Update Profile [visitor.constantcontact.com]<https://urldefense.com/v3/__https:/visitor.constantcontact.com/do?p=oo&m=00…> | Constant Contact Data Notice [constantcontact.com]<https://urldefense.com/v3/__https:/www.constantcontact.com/legal/customer-c…> Sent by david.olive(a)icann.org<mailto:david.olive@icann.org> powered by [Trusted Email from Constant Contact - Try it FREE today.][constantcontact.com]<https://urldefense.com/v3/__http:/www.constantcontact.com/index.jsp?cc=nge&…> Try email marketing for free today! [constantcontact.com]<https://urldefense.com/v3/__http:/www.constantcontact.com/index.jsp?cc=nge&…>

1 0