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

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

July 25, 2022

Dear all, All recordings for the Statement of Interest Task Force call held on Monday, 25 July 2022 at 13:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/rQAVD> (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 July 2022 at 13:00 UTC
by Julie Hedlund July 25, 2022

July 25, 2022

Dear All, Please see below the action items and brief notes from today’s SOI Task Force meeting on Monday, 25 July 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 #11 Monday, 25 July 2022 at 13.00 UTC HOMEWORK/ACTION ITEMS: 1. TF members to contribute sample SOIs in the form at: https://docs.google.com/document/d/1-i7oTXv_7eRibJK8a8FQ8Df9CCClWuH_/edit. 2. Staff to turn the SOI sample form into a Google form. 3. Staff to check the timing of upcoming public comment periods to avoid overlap. 4. Staff to work with Olga Cavalli to provide an update to the CCOICI on the work of the TF and in particular the timing of the public forum. 5. Staff to schedule the next meeting for Monday, 22 August. Notes: 1. Welcome 2. Review proposed SOI samples (see https://docs.google.com/document/d/1-i7oTXv_7eRibJK8a8FQ8Df9CCClWuH_/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1-i7oTXv_7eRi…> - reminder, please provide your suggestions ahead of the meeting) * What we discussed following the last meeting that it might be helpful to produce sample SOIs based on the recommendations to have two SOIs – general and activity specific. * No one has provided a sample or samples yet. * May have more time if we decide to delay the public comment period. * Helpful to have as close to a near real-world example as possible to give community members enough context as to why these changes are being suggested. * Once we start filling this out we may come across pain points. * Also helpful to have feedback on the format as that will help in the design. For example, drop-down boxes could be a better format. * In parallel to the public comment period we will do a test by a group (perhaps this TF). * Karen Day and Susan Payne noted that they are interested in helping to develop examples. * Question: What is the timeline for community feedback and how does that line up with KL/ICANN75 – could we get feedback there? Answer: Good idea. Maybe we could turn this into a Google form that people could use to test and let people provide feedback. Think about the right timing for that. TF members could also take it back to their groups. Or put on the agendas of SGs and Cs meetings at KL, and/or ask for testing and comments as part of the public comment forum. ACTION ITEMS: 1. TF members to contribute sample SOIs in the form at: https://docs.google.com/document/d/1-i7oTXv_7eRibJK8a8FQ8Df9CCClWuH_/edit. 2. Staff to turn the SOI sample form into a Google form. 3. Review TF input on the Recommendations Report (see attached) * Must go for public comment because of changes to the GNSO Operating Procedures. * As noted above, consider whether to include testing and comments of the proposed SOI forms as part of the public comment forum. * How much time do TF members need to review the Recommendations Report and Public Comment forum text? What is the timing of the next meeting? 4. Review public comment forum (see attached) * Combine with changes resulting from the CCOICI’s review of the GNSO Working Group Self-Assessment, so as not to create confusion by having two comment periods on the same document. * Also includes some minor typographical or reference updates as part of the general updating of the GNSO Operating Procedures. * Helpful if TF members and their groups could review these documents and raise concerns or questions, if any. * Please note that in light of the significant number of public comment forums that is expected to open in August (see https://www.icann.org/en/public-comment/upcoming-proceedings) we would like to discuss with the Task Force whether there is any concern about waiting with launching the public comment forum until after ICANN75 to avoid having too many items for community input open at the same time. * Could use ICANN75 to provide an introduction to the community and then launch the public comment forum immediately following ICANN75. * Don’t think we’ll get as much of attention if published in August with multiple other open fora. Might consider opening the public comment period just prior to ICANN75 and extend it for longer to encourage feedback during the meeting. Staff should first check the timing of the other public comment periods. * This TF group does not have any concerns with moving the public comment period to September. ACTION ITEMS: 1. Staff to check the timing of upcoming public comment periods to avoid overlap. 2. Staff to work with Olga Cavalli to provide an update to the CCOICI on the work of the TF and in particular the timing of the public forum. 5. Confirm next steps & next meeting * Suggest to reconvene on 22 August. ACTION ITEM: Staff to schedule the next meeting for Monday, 22 August (DONE).

1 0

Meeting Invitation | SOI Taskforce Meeting | Monday, 22 August 2022 at 13:00 UTC
by Devan Reed July 25, 2022

July 25, 2022

Please note: The 08 August call was cancelled. Please remove it from your calendars. The next call will take place 22 August 2022 at 13:00 UTC. Dear all, The next SOI Taskforce meeting is scheduled on Monday, 22 August 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/vgAVD * Check your time zone: https://tinyurl.com/yre6as9d Thank you, Kind regards, Devan

1 0

Canceled: SOI Task Force meeting
by ICANN Policy Calendar July 25, 2022

July 25, 2022

Meeting: SOI Task Force meeting Date: Monday, 08 August 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…> 08 August 2022 at 20:00 UTC Wiki Agenda Page: https://community.icann.org/x/swAVD Check your time zone: https://tinyurl.com/2p9yd5kt 22 August 2022 at 13:00 UTC Wiki Agenda Page: https://community.icann.org/x/vgAVD Check your time zone: https://tinyurl.com/yre6as9d 05 September 2022 at 20:00 UTC Wiki Agenda Page: https://community.icann.org/x/xAAVD Check your time zone: https://tinyurl.com/4ce8s9b3

1 0

15 MINUTES | REMINDER | Meeting Invitation | SOI Taskforce Meeting | Monday, 25 July 2022 at 13:00 UTC
by Devan Reed July 25, 2022

July 25, 2022

Dear all, The next SOI Taskforce meeting is scheduled on Monday, 25 July 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/rQAVD * Check your time zone: https://tinyurl.com/2p889yau<https://urldefense.com/v3/__https:/tinyurl.com/2p889yau__;!!PtGJab4!7D05BOL…> Thank you, Kind regards, Devan

1 0

Re: [GNSO-SOI-TF] For your review - draft TF Recommendations Report & Public comment forum
by Marika Konings July 22, 2022

July 22, 2022

Dear All, Hereby the proposed agenda for the next meeting of the GNSO SOI Task Force which is scheduled for Monday 25 July at 13.00 UTC: 1. Welcome 2. Review proposed SOI samples (see https://docs.google.com/document/d/1-i7oTXv_7eRibJK8a8FQ8Df9CCClWuH_/edit - reminder, please provide your suggestions ahead of the meeting) 3. Review TF input on the Recommendations Report (see attached) 4. Review public comment forum (see attached) 5. Confirm next steps & next meeting Please note that in light of the significant number of public comment forums that is expected to open in August (see https://www.icann.org/en/public-comment/upcoming-proceedings) we would like to discuss with the Task Force whether there is any concern about waiting with launching the public comment forum until after ICANN75 to avoid having too many items for community input open at the same time. Best regards, 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, 18 July 2022 at 17:41 To: "gnso-soi-tf(a)icann.org" <gnso-soi-tf(a)icann.org> Subject: [GNSO-SOI-TF] For your review - draft TF Recommendations Report & Public comment forum Dear All, In preparation for next week’s SOI TF meeting, please find attached the following documents for your review: 1. Draft Task Force Recommendations Report – The staff support team has gone ahead and incorporated the proposed recommendations (see https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit?p… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ZrLZ5NSiSN35…>) in the attached report together with other relevant background information. 2. The draft public comment forum – as a reminder, the public comment forum for these recommendations will be combined with the changes that have been proposed by the CCOICI in relation to the Working Group Self-Assessment so that there is only one public comment forum that needs to be opened to consider proposed changes to the GNSO Operating Procedures. Following your review of both documents, we would like to request Olga, as the CCOICI liaison to the Task Force, to share these documents with the CCOICI for its information and review prior to opening of the public comment forum. As a reminder, please provide your input on the sample SOI that is intended to be used for the public comment forum to illustrate the information and detail that would be expected to be provided: https://docs.google.com/document/d/1-i7oTXv_7eRibJK8a8FQ8Df9CCClWuH_/edit [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1-i7oTXv_7eRi…>. Best regards, Julie & Marika

1 0

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

July 22, 2022

Dear all, The next SOI Taskforce meeting is scheduled on Monday, 25 July 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/rQAVD * Check your time zone: https://tinyurl.com/2p889yau [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/2p889yau__;!!PtGJab4!7D05BOL…> Thank you, Kind regards, Devan

1 0

For your review - draft TF Recommendations Report & Public comment forum
by Marika Konings July 18, 2022

July 18, 2022

Dear All, In preparation for next week’s SOI TF meeting, please find attached the following documents for your review: 1. Draft Task Force Recommendations Report – The staff support team has gone ahead and incorporated the proposed recommendations (see https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit?p…) in the attached report together with other relevant background information. 2. The draft public comment forum – as a reminder, the public comment forum for these recommendations will be combined with the changes that have been proposed by the CCOICI in relation to the Working Group Self-Assessment so that there is only one public comment forum that needs to be opened to consider proposed changes to the GNSO Operating Procedures. Following your review of both documents, we would like to request Olga, as the CCOICI liaison to the Task Force, to share these documents with the CCOICI for its information and review prior to opening of the public comment forum. As a reminder, please provide your input on the sample SOI that is intended to be used for the public comment forum to illustrate the information and detail that would be expected to be provided: https://docs.google.com/document/d/1-i7oTXv_7eRibJK8a8FQ8Df9CCClWuH_/edit. Best regards, Julie & Marika

1 0

Your input requested - SOI Samples
by Marika Konings July 12, 2022

July 12, 2022

Dear all, Per the action item from yesterday’s meeting, we’ve gone ahead and created a google doc that will allow you to put forward a sample SOI that may be used for the public comment period to illustrate the information and detail that would be expected to be provided: https://docs.google.com/document/d/1-i7oTXv_7eRibJK8a8FQ8Df9CCClWuH_/edit. There is current room for 3 samples each (of the general SOI and an activity SOI), but if more are needed, you can just copy paste a new table. As discussed, you can either choose to fill this out from your own perspective and use an ongoing GNSO effort for the activity specific one, or choose a fictional person (e.g. Jane Doe, working at registrar A). Please provide your suggestions prior to the next SOI TF meeting on 25 July so it can be considered in conjunction with the other public comment materials. 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 July 2022 at 23:17 To: "gnso-soi-tf(a)icann.org" <gnso-soi-tf(a)icann.org> Subject: [GNSO-SOI-TF] Action Items & Notes: SOI TF Meeting 11 July 2022 at 20:00 UTC Dear All, Please see below the action items and brief notes from today’s SOI Task Force meeting on Monday, 11 July 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 #10 Monday, 11 July 2022 at 20.00 UTC HOMEWORK/ACTION ITEMS: 1. Staff to develop a Google doc with the questions and TF members can provide examples with suggestions from staff. 2. Staff will develop the public comment materials for TF members to discuss during the meeting on 25 July. 3. TF members to review and provide comments, if any, on the implementation implications and updates to the GNSO Operating Procedures at: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit?p… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ZrLZ5NSiSN35…>. Notes: 1. Welcome 2. TF members to share feedback from their respective groups on the proposed recommendations * RySG: No additional feedback beyond what has already been shared. * Nothing new from the RrSG. * No concerns from the IPC. Talked internally about wanting more information about people’s activities, recognizing that it might be difficult to make that effective. * That is the balance we’ve been trying to find in the questions, but could be where the pilot will be helpful as WG members try out the questions and could suggest some guidance or minor changes. Helpful to have some use cases in conjunction with the public comment period. Could take one of the working groups that is active today. * There will be further opportunities once this goes for public comment. 3. Review implementation considerations – see: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit?p… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ZrLZ5NSiSN35…> Enforcement section: consider using “active” vs “inactive” terminology. Added section: “Implementation Guidance (for TF review) 1. ICANN org is expected to explore the technical options for implementing these recommendations and report back to the TF and/or GNSO Council on the available options as well as any possible limitations that may exist. 2. ICANN org will also review what, if any, safeguards need to be implemented, including appropriate disclaimers and retention policies to make sure that the implementation of these new SOI requirements is consistent with applicable data protection laws. Discussion: * Need to decide what happens to the old SOIs. * More research may be needed to make sure the implementation is applicable to data protection laws. * Make sure that retention is balanced with transparency and data protection requirements. * Question: Is there anything else that needs to be called out here? * Please share any concerns after this call too. * Think this is good and reflects where the WG landed. * Question: On the privacy implications of publishing these – while we appreciate the desire for transparency, we live in a different environment than 10 years ago. Don’t want this to be an inadvertent way to leak personal data. * The SOI could be accessible to the WG for a brief window, then re-secured. * Currently, you do not have to be logged into the wiki to view the SOIs. 4. Review proposed updates to GNSO Operating Procedures – see: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit?p… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ZrLZ5NSiSN35…>, page 3. Discussion: * Any changes to the GNSO Operating Procedures need to be put out for public comment and the Board has oversight. * Definitions: Added the distinction between general and specific SOIs. * Timeliness: Noting technical feasibility of moving to an automated function re: “active” vs “inactive” SOIs. Also noting that the Secretariat or the Chair requests changes to SOIs at each meeting. * Content: Describe in a more general way the type of information that is expected to be included with a reference to the specific questions. Allows for making changes without going through a public comment period. New language: “The detailed questions will be made publicly available and may be reviewed and revised by the GNSO Council from time to time using its relevant processes.” * Corrected some typos/errors in references to different sections. * Berry Cobb, Staff: When this comes into use, most understand that there is a fair amount of community members that actively participate in multiple groups, including formal memberships with other statements of interest. Many of our repeat participants could have multiple SOIs for each of the activities in which they participate, which could be challenging for the member to manage content. For example, a community member who changes jobs would need to update their parent SOI and 3-5 child SOIs. A valuable compliment would be an example or two to provide real-world context that this group could develop. This could help the community and help this group to provide a rationale for their recommended changes. This could be like a mini-SOI pilot. * Thought we talked about building this as modular, so that the basics would be in a high-level part A that then would attach to Part B, C, D, etc. for each specific group. Only the primary high-level part would need to be changed. * But an employer change might require changes to the parent SOI and the children. * If a group closes down, that child SOI will be marked “inactive”. * The child SOI should look different for each group/topic. If we don’t give examples of how these should look then people will probably do the same for each group. * Agree that it won’t be a lot of changes if we truly build it as a parent/child model. The employer is the same (in the parent SOI) regardless of what individual working groups in which the person participates (the children SOIs); if the client changes then the specific SOI would change (the child SOI), which is what we want for transparency. * Agree with the need for fulsome examples and happy to help with developing those for the areas of the community that TF members are familiar with. * For specific SOI changes, it could be a couple of clicks but not a lot of text to write/replace. * Could provide background/justification for the changes to accompany the public comment forum. ACTION ITEM: Staff to develop a Google doc with the questions and TF members can provide examples with suggestions from staff. ACTION ITEM: TF members to review and provide comments, if any, on the implementation implications and updates to the GNSO Operating Procedures at: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit?p… [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1ZrLZ5NSiSN35…>. 5. Discuss next steps: a. Final review of recommendations * How much additional time will TF members need for a final review by their groups – by next meeting on 25 July? * Note that for public comment text we will combine all updates to the Operating Procedures, including changes to the Working Group Assessment, as well as some minor corrections. b. Opening of public comment period * Consider publishing later to avoid clashing with other open public comment periods. See: https://www.icann.org/en/public-comment/upcoming-proceedings. ACTION ITEM: Staff will develop the public comment materials for TF members to discuss during the meeting on 25 July. c. SOI Pilot * TF members to consider how they want to participate and discuss at the meeting on 25 July. 6. Confirm next meeting – Monday 25 July at 13.00 UTC.

1 0

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

July 11, 2022

Dear all, All recordings for the Statement of Interest Task Force call held on Monday, 11 July 2022 at 13:00 UTC can be found on the agenda wiki page <https://community.icann.org/x/qgAVD> (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 11 July 2022 at 20:00 UTC
by Julie Hedlund July 11, 2022

July 11, 2022

Dear All, Please see below the action items and brief notes from today’s SOI Task Force meeting on Monday, 11 July 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 #10 Monday, 11 July 2022 at 20.00 UTC HOMEWORK/ACTION ITEMS: 1. Staff to develop a Google doc with the questions and TF members can provide examples with suggestions from staff. 2. Staff will develop the public comment materials for TF members to discuss during the meeting on 25 July. 3. TF members to review and provide comments, if any, on the implementation implications and updates to the GNSO Operating Procedures at: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit?p…. Notes: 1. Welcome 2. TF members to share feedback from their respective groups on the proposed recommendations * RySG: No additional feedback beyond what has already been shared. * Nothing new from the RrSG. * No concerns from the IPC. Talked internally about wanting more information about people’s activities, recognizing that it might be difficult to make that effective. * That is the balance we’ve been trying to find in the questions, but could be where the pilot will be helpful as WG members try out the questions and could suggest some guidance or minor changes. Helpful to have some use cases in conjunction with the public comment period. Could take one of the working groups that is active today. * There will be further opportunities once this goes for public comment. 3. Review implementation considerations – see: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit?p… Enforcement section: consider using “active” vs “inactive” terminology. Added section: “Implementation Guidance (for TF review) 1. ICANN org is expected to explore the technical options for implementing these recommendations and report back to the TF and/or GNSO Council on the available options as well as any possible limitations that may exist. 2. ICANN org will also review what, if any, safeguards need to be implemented, including appropriate disclaimers and retention policies to make sure that the implementation of these new SOI requirements is consistent with applicable data protection laws. Discussion: * Need to decide what happens to the old SOIs. * More research may be needed to make sure the implementation is applicable to data protection laws. * Make sure that retention is balanced with transparency and data protection requirements. * Question: Is there anything else that needs to be called out here? * Please share any concerns after this call too. * Think this is good and reflects where the WG landed. * Question: On the privacy implications of publishing these – while we appreciate the desire for transparency, we live in a different environment than 10 years ago. Don’t want this to be an inadvertent way to leak personal data. * The SOI could be accessible to the WG for a brief window, then re-secured. * Currently, you do not have to be logged into the wiki to view the SOIs. 4. Review proposed updates to GNSO Operating Procedures – see: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit?p…, page 3. Discussion: * Any changes to the GNSO Operating Procedures need to be put out for public comment and the Board has oversight. * Definitions: Added the distinction between general and specific SOIs. * Timeliness: Noting technical feasibility of moving to an automated function re: “active” vs “inactive” SOIs. Also noting that the Secretariat or the Chair requests changes to SOIs at each meeting. * Content: Describe in a more general way the type of information that is expected to be included with a reference to the specific questions. Allows for making changes without going through a public comment period. New language: “The detailed questions will be made publicly available and may be reviewed and revised by the GNSO Council from time to time using its relevant processes.” * Corrected some typos/errors in references to different sections. * Berry Cobb, Staff: When this comes into use, most understand that there is a fair amount of community members that actively participate in multiple groups, including formal memberships with other statements of interest. Many of our repeat participants could have multiple SOIs for each of the activities in which they participate, which could be challenging for the member to manage content. For example, a community member who changes jobs would need to update their parent SOI and 3-5 child SOIs. A valuable compliment would be an example or two to provide real-world context that this group could develop. This could help the community and help this group to provide a rationale for their recommended changes. This could be like a mini-SOI pilot. * Thought we talked about building this as modular, so that the basics would be in a high-level part A that then would attach to Part B, C, D, etc. for each specific group. Only the primary high-level part would need to be changed. * But an employer change might require changes to the parent SOI and the children. * If a group closes down, that child SOI will be marked “inactive”. * The child SOI should look different for each group/topic. If we don’t give examples of how these should look then people will probably do the same for each group. * Agree that it won’t be a lot of changes if we truly build it as a parent/child model. The employer is the same (in the parent SOI) regardless of what individual working groups in which the person participates (the children SOIs); if the client changes then the specific SOI would change (the child SOI), which is what we want for transparency. * Agree with the need for fulsome examples and happy to help with developing those for the areas of the community that TF members are familiar with. * For specific SOI changes, it could be a couple of clicks but not a lot of text to write/replace. * Could provide background/justification for the changes to accompany the public comment forum. ACTION ITEM: Staff to develop a Google doc with the questions and TF members can provide examples with suggestions from staff. ACTION ITEM: TF members to review and provide comments, if any, on the implementation implications and updates to the GNSO Operating Procedures at: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit?p…. 5. Discuss next steps: a. Final review of recommendations * How much additional time will TF members need for a final review by their groups – by next meeting on 25 July? * Note that for public comment text we will combine all updates to the Operating Procedures, including changes to the Working Group Assessment, as well as some minor corrections. b. Opening of public comment period * Consider publishing later to avoid clashing with other open public comment periods. See: https://www.icann.org/en/public-comment/upcoming-proceedings. ACTION ITEM: Staff will develop the public comment materials for TF members to discuss during the meeting on 25 July. c. SOI Pilot * TF members to consider how they want to participate and discuss at the meeting on 25 July. 6. Confirm next meeting – Monday 25 July at 13.00 UTC.

1 0

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

July 11, 2022

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

1 0

AT THE TOP OF THE HOUR | REMINDER - Meeting Invitation | SOI Taskforce Meeting | Monday, 11 July 2022 at 20:00 UTC
by Devan Reed July 11, 2022

July 11, 2022

Dear all, The next SOI Taskforce meeting is scheduled on Monday, 11 July 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/qgAVD * Check your time zone: https://tinyurl.com/yc7548re<https://urldefense.com/v3/__https:/tinyurl.com/yc7548re__;!!PtGJab4!5ol7xYr…> Thank you, Kind regards, Devan

1 0

REMINDER - Meeting Invitation | SOI Taskforce Meeting | Monday, 11 July 2022 at 20:00 UTC
by Julie Bisland July 8, 2022

July 8, 2022

Dear all, The next SOI Taskforce meeting is scheduled on Monday, 11 July 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/qgAVD * Check your time zone: https://tinyurl.com/yc7548re [tinyurl.com]<https://urldefense.com/v3/__https:/tinyurl.com/yc7548re__;!!PtGJab4!5ol7xYr…> Thank you, Kind regards, Devan

1 0

Items for review and proposed agenda for next meeting scheduled for Monday 11 July at 20.00 UTC
by Marika Konings July 7, 2022

July 7, 2022

Dear SOI Task Force members, As discussed during our last meeting on 6 June, the staff support team took a stab at translating the current set of draft recommendations into proposed updates to the GNSO Operating Procedures. In addition we have consulted with some of our colleagues in relation to implementation considerations both from a technical and legal perspective. To reflect that further consideration will need to be given to these aspects, we’ve added a proposed “implementation guidance” section to the recommendations document. To review both of these aspects (proposed updates to GNSO Operating Procedures as well as implementation guidance), please see from page 3 onwards in the recommendations document: https://docs.google.com/document/d/1ZrLZ5NSiSN35MeCYhxqQUP4G1v-Rzsty/edit?p…. We also wanted to remind you that per the action item, TF members were to review the Draft Recommendations with their respective groups and post comments/suggestions in the Google document for consideration by the TF prior to the next meeting on 11 July. As a result, the proposed agenda for the next meeting, which is scheduled for Monday 11 July at 20.00 UTC is as follows: 1. Welcome 2. TF members to share feedback from their respective groups on the proposed recommendations 3. Review implementation considerations 4. Review proposed updates to GNSO Operating Procedures 5. Discuss next steps: * Final review of recommendations * Opening of public comment period * SOI Pilot 6. Confirm next meeting – Monday 25 July at 13.00 UTC. If you have any comments and/or proposed changes to the agenda, please feel free to share those with the mailing list. Best regards, Julie and Marika

1 0