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

Action Items & Notes: SOI TF Meeting 09 May 2022 13:00 UTC
by Julie Hedlund May 9, 2022

May 9, 2022

Dear All, Please see below the action items and brief notes from today’s SOI Task Force meeting on Monday, 09 May 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 #7 Monday, 09 May 2022 at 13:00 UTC Action Items: Outreach Survey (see attached document) and Review of draft recommendations (see https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ZrLZ5NSiSN35…>) 1. Outreach survey and draft recommendations -- TF members to review the comments/suggestions from the outreach survey as captured in the draft recommendations document and provide further comments/suggestions either in response to the outreach input or to any of the draft recommendations. 1. Question 2d-e -- Staff to propose edits – in particular to make it clear that people are not expected to identify only one group, but all the groups in which they participate, including SOs/ACs, but to indicate which is the primary group. Consider how to capture this in a template for form, for example “if you identified multiple groups please identify which is the one on whose behalf you will represent on the group.” 1. Question 2h -- Staff to provide Bylaws language and background on the context for the development of this question. 1. Question 4 -- Staff to suggest some language for a requirement / practice that at the start of an effort everyone is expected to walk through their activity specific SOI. 1. Question 5: 1. Staff to suggest language and TF members to consider further. 2. Staff to explore whether there is a way to see if this has been used. 1. Question 5bi-ii -- Staff to update to say “you, your employer or your client(s)”. Notes: 1. Welcome 2. Outreach survey (see attached document) a. High level overview * One of the first assignments was to reach out to other groups with a survey to ascertain how they are using the SOIs. * This was posted to the Digest as well as disseminated via the TF representatives’ groups. * We had 23 people responding to the survey. * This is just initial outreach. Any recommendations for changes to the SOI in the GNSO Operating Procedures will go out for public comment. * A lot of the comments seem to align with the comments from the SOI TF and from staff for potential updates. * Some good suggestions in line with what is already being discussed. * Some specific suggestions on questions being asked – could be more tailored, relevant, and easily understood. * Staff integrated the comments into the draft recommendations document. b. TF comments / considerations * Feel free to send them via email to the TF list or put them in the draft recommendations document. c. Confirm next steps * TF members should review comments from outreach survey in the draft recommendations document and provide their further comments and suggestions. See the relevant action item below. ACTION ITEM: TF members to review the comments/suggestions from the outreach survey as captured in the draft recommendations document and provide further comments/suggestions either in response to the outreach input or to any of the draft recommendations. 3. Continue review of draft recommendations (see https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ZrLZ5NSiSN35…>) a. Review comments / input Overview: * Hoped that we would have received input from the TF members; not sure if that means that people are comfortable with the draft. * Do you need more time to review and with your groups? Do you need more time? What would be a reasonable time frame? * Karen Day – haven’t had time to review with my group with the accelerated time frame for ICANN74 preparation. * Suggestion for today’s call is to focus on specific items and how to address the suggestions that were made. 2. The General Statement of Interest consists of the following (existing questions): d. Affiliation (if not covered by b or c) e. Please identify your current employer(s); * From Outreach Survey: "Listing merely one "affiliation" is not just disingenuous, it is false and potentially misleading. Many participants have ties to multiple groups, even if they only officially participate in one of them—each of these is important. Some people do not consider themselves "users", this is also important information. When completing SOIs, people should be encouraged to be expansive in their definitions of interest: not just who pays them, which has some import, but with whom their sympathies lie." * From Outreach Survey: "The objective of the SOI is being missed in many cases as just listing the organisation one is affiliated with does not usually provide the full picture. For example if a participant states he or she is representing the "Online fellowship of the greater good", that is not usually sufficient to understand whose interest that participant truly represents. The SOI should therefore be expanded by a register for the organisations represented as well, outlining their source of funding and memberships in and affiliations with other relevant organisations. The SOI should also include statements of who is paying for the time of the representative spent doing the work, e.g. who is paying the billable hours." * Is it important to ask for this information and how? Perhaps “please identify all the groups in which you participate and in particular those SGs/Cs in which you are a voting member.” * Seems to be a question where we all agree that there needs to be more input. We should also check back with our groups. * Think we need to broaden the language to ask them to list all stakeholder groups, affiliation, etc. Also guidance/use cases and definitions would be helpful. * What additional information should we request and how to integrate it into the form? * Conscious that we need to find a balance, but like the idea of providing a link to the organization/affiliation. 2e: Please identify your current employer(s); * From Outreach Survey: "I would include current and former employers as well as any affiliation the completer believes would be important if they were reading someone else's SOI." * Add something about previous employer? Not sure how that would be relevant for an SOI. * Could continue to thing about this one and whether there is a situation in which previous employer would be relevant. * There is already a section that asks about additional information that might be relevant. ACTION ITEM: Question 2d-e -- Staff to propose edits – in particular to make it clear that people are not expected to identify only one group, but all the groups in which they participate, including SOs/ACs, but to indicate which is the primary group. Consider how to capture this in a template for form, for example “if you identified multiple groups please identify which is the one on whose behalf you will represent on the group.” 2h: Please identify your declared country of primary residence (e.g., country to which you pay taxes): * From Outreach Survey: "The language in #2 "Please identify your declared country of primary residence (which may be the country to which you pay taxes)."differs from that in the ICANN Bylaws. It should be modified to make it consistent." * Maybe come back to this. * The primary use of this field is very helpful to the Secretariat support team when we start a new group when monitoring for diversity by location and use the field to set up the cadence of calls. ACTION ITEM: Question 2h -- Staff to provide Bylaws language and background on the context for the development of this question. 2k. Additional information (optional) * From Outreach Survey: "SOI should permit "EDIT" mode and provide space for "Any Other Pertinent Declarations or Disclosures"" * Could be more specific and also provide use cases. Template may already have this – but could provide more context. 4. The Activity Specific Statement of Interest is to be completed for each GNSO activity a participant signs up for. * From staff: Should there also be a requirement / practice that at the start of an effort everyone is expected to walk through their activity specific SOI? * Having these introductions at the beginning of a call provides transparency and may reduce the need for enforcement if there are questions about an SOI at a later time. * Seems to be support for that approach. ACTION ITEM: Question 4 -- Staff to suggest some language for a requirement / practice that at the start of an effort everyone is expected to walk through their activity specific SOI. 5. The Activity Specific Statement of Interest consists of the following (existing questions): a. Do you believe you are participating in the GNSO policy process as a representative of any individual or entity, whether paid or unpaid? 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, please enter "Private"): * 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? * Seems to be supported by the Consensus Playbook recommendations. Could help focus the conversations. * Is this something that you think should be included? * Come back to this one for further discussion. * From Outreach Survey: "The language in 5 "If professional ethical obligations prevent you from disclosing this information, please so state." is problematic as it creates a "loophole" for some to hide behind such relationship. I would urge the SOI Task Force to see if there is a way to turn this around to make sure non-disclosure is only allowed under exceptional circumstances." * Any thoughts on this one? Let us know if you would like to take this back to our legal colleagues. * This has come up a couple of times in previous meetings. If there are ethical obligations preventing the disclosure, maybe we could ask a different question to get some idea of why someone is at a meeting? * Maybe could ask which professional ethical obligations are preventing you. Maybe use cases can be more specific. Ask if there are professional or ethical obligations that would be prevent this from being disclosed. * Group should think further about this suggestion, particularly concerning alternate questions. * Is there a way we can see how often people use this exception? ACTION ITEMS – Question 5: 1. Staff to suggest language and TF members to consider further. 2. Staff to explore whether there is a way to see if this has been used. b. Please identify any other relevant arrangements, interests, or benefits as requested in the following two questions: i. Do you have any type of material interest in ICANN GNSO policy development processes and outcomes? If the answer is “yes,” please describe the material interest in ICANN GNSO policy development processes and outcomes: ii. Are there any arrangements/agreements between you and any other group, constituency or person(s) regarding your participation as a work team member? If the answer is “yes,” please describe the arrangements/agreements and the name of the group, constituency, or person(s): * Question: Should this be updated to say “you, your employer or your client(s)”? ACTION ITEM: Question 5bi-ii -- Staff to update to say “you, your employer or your client(s)”. 8. A number of use cases have been developed [to be completed] by the TF that will serve as example / instructions for those completing the templates to provide the appropriate level of detail / information. * From Outreach Survey: "Guidance to the level of detail required would also assist as currently there is a range in the level of detail given across SOIs which all, apparently, are acceptable" 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? * Sounds like an excellent suggestion. Enforcement / Escalation Outreach Survey Input for consideration: * Several suggestions from the survey. * TF members to add their comments/suggestions. b. Confirm next steps * Identify which areas require further discussion. * Staff to update based on today’s meeting. * TF members are requested to review again and provide comments/suggestions in advance of the next meeting. (See action item above.) 4. Wrap up & confirmation of next meeting (Monday 23 May at 20.00 UTC)

1 0

Post Call | Statement of Interest Task Force | Monday, 09 May 2022
by Devan Reed May 9, 2022

May 9, 2022

Dear all, All recordings for the Statement of Interest Task Force call held on Monday, 09 May 2022 at 13:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/jBV1Cw> (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, 23 May 2022 at 20:00 UTC
by Devan Reed May 9, 2022

May 9, 2022

Dear all, The next SOI Taskforce meeting is scheduled on Monday, 23 May 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/jhV1Cw * Check your time zone: https://tinyurl.com/2ef7w45j Thank you, Kind regards, Devan

1 0

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

May 9, 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 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2p9saazz__;!!PtGJab4!pGelnPR…> Thank you, Kind regards, Devan

1 0

Re: [GNSO-SOI-TF] [gnso-secs] **REMINDER** Meeting Invitation | SOI Taskforce Meeting | Monday, 09 May 2022 at 13:00 UTC
by Devan Reed May 6, 2022

May 6, 2022

Hi James, Your apologies are noted. Safe travels! Thank you! Kind regards, Devan From: Gnso-secs <gnso-secs-bounces(a)icann.org> on behalf of "James M. Bladel via Gnso-secs" <gnso-secs(a)icann.org> Reply-To: "James M. Bladel" <jbladel(a)godaddy.com> Date: Friday, May 6, 2022 at 11:02 AM To: Julie Bisland <julie.bisland(a)icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org>, "gnso-soi-tf(a)icann.org" <gnso-soi-tf(a)icann.org> Subject: Re: [gnso-secs] [GNSO-SOI-TF] **REMINDER** Meeting Invitation | SOI Taskforce Meeting | Monday, 09 May 2022 at 13:00 UTC Hi folks. I’ll be in the air during this time, so please accept my apologies. J. On May 6, 2022, at 06:02, Julie Bisland <julie.bisland(a)icann.org> wrote: Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@. 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 [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> 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 [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> If this is your first time with Zoom, please take a look here: Welcome to Zoom [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> 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 [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> * Wiki agenda page: https://community.icann.org/x/jBV1Cw [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> * Check your time zone: https://tinyurl.com/2p9saazz [tinyurl.com] [nam10.safelinks.protection.outlook.com]<https://urldefense.com/v3/__https:/nam10.safelinks.protection.outlook.com/?…> Thank you, Kind regards, Devan _______________________________________________ GNSO-SOI-TF mailing list GNSO-SOI-TF(a)icann.org https://mm.icann.org/mailman/listinfo/gnso-soi-tf _______________________________________________ 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.

1 0

**REMINDER** Meeting Invitation | SOI Taskforce Meeting | Monday, 09 May 2022 at 13:00 UTC
by Julie Bisland May 6, 2022

May 6, 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 [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2p9saazz__;!!PtGJab4!pGelnPR…> Thank you, Kind regards, Devan

2 1

Proposed agenda for GNSO SOI TF Meeting on Monday 9 May at 13.00 UTC
by Marika Konings May 6, 2022

May 6, 2022

Dear All, Please find hereby the proposed agenda for the next meeting of the GNSO SOI Task Force which is scheduled for Monday 9 May at 13.00 UTC. Attached you will find the results of the outreach survey. Responses were received from 23 community members. The staff support team has gone ahead and added specific suggestions to the google doc with draft recommendations so that the TF can consider these further. Of course, if there is other input that you think the group should consider, feel free to add accordingly. Proposed Agenda – GNSO SOI Task Force – Monday 9 May at 13.00 UTC 1. Welcome 2. Outreach survey * High level overview * TF comments / considerations * Confirm next steps 3. Continue review of draft recommendations (see https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit) * Review comments / input * Confirm next steps 4. Wrap up & confirmation of next meeting (Monday 23 May at 20.00 UTC) Best regards, Julie and Marika

1 0

Reminder - please review draft SOI Recommendations by Thursday 5 May 2022
by Marika Konings May 5, 2022

May 5, 2022

Reminder: ACTION ITEM: TF members to review the Draft SOI Recommendations at: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ZrLZ5NSiSN35…> and provide comments/suggestions by Thursday, 05 May 2022. 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, 25 April 2022 at 22:57 To: "gnso-soi-tf(a)icann.org" <gnso-soi-tf(a)icann.org> Subject: [GNSO-SOI-TF] Action Items & Notes: SOI TF Meeting 25 April 2022 20:00 UTC 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 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ZrLZ5NSiSN35…> 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 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ZrLZ5NSiSN35…> and provide comments/suggestions by Thursday, 05 May 2022.

1 0