April 2024 - rssac-caucus - lists.icann.org

Observing RSSAC Monthly Meetings
by Ozan Sahin July 26, 2024

July 26, 2024

Dear RSSAC Caucus members, RSSAC Admin Committee would like to remind you that regular RSSAC meetings, typically held on the first Tuesday of each month, are default open for observation, but portions of the meeting can be closed to the public at the discretion of the RSSAC Chair. To observe an RSSAC meeting, please contact rssac-staff(a)icann.org<mailto:rssac-staff@icann.org>. Please note that remote participation information is not posted on the RSSAC web page to minimize the risk of security incidents. Unlike invited guests, observers will not have the opportunity to speak or interact using the Zoom features such as chat pod during regular RSSAC meetings. As customary, RSSAC meeting minutes are posted on the RSSAC Meetings page once they have been approved by the RSSAC: https://www.icann.org/resources/pages/rssac-meetings-2014-05-06-en RSSAC leadership would also like to understand the level of interest from RSSAC Caucus to observe regular RSSAC meetings. Therefore, if you are interested in observing RSSAC monthly meetings on a regular basis, please let us know by completing this form by Tuesday, 30 April 2024: https://forms.gle/SZmU9MbNjP9yxf2f8. RSSAC Caucus members who respond to the survey and indicate that they are “always” interested in observing RSSAC monthly meetings will receive remote participation information on a monthly basis without having to contact rssac-staff(a)icann.org<mailto:rssac-staff@icann.org> separately. Please also find the draft agenda below for the next RSSAC monthly meeting to be held on Tuesday, 7 May 2024 at 14:00 UTC. Best, Ozan Sahin on behalf of RSSAC Admin Committee RSSAC Teleconference Tuesday, 7 May 2024 | 14:00-15:30 UTC Draft Agenda (* = Vote) 1. Call to Order (Jeff Osborn) 2. Roll Call (Jeff Osborn) 3. Agenda Review (Jeff Osborn) 4. Administration * Draft Minutes from 2 April 2024 Meeting* (Ozan Sahin) * RSSAC Caucus Membership Committee Update (Jeff Osborn) i. Recommendation of Candidate*: * RSSAC Delegate to the 2025 ICANN Nominating Committee Election* (Jeff Osborn) 1. ICANN80 Planning (Ozan Sahin) * RSSAC ICANN80 Schedule 2. Work Items * RSS Security Incident Reporting Work Party Update (Ken Renard) * RSS Messaging (Jeff Osborn) * Guidelines for Changing Root Server Addresses (TBC) * RSSAC047v2: RSSAC Advisory on Metrics for the DNS Root Servers and the Root Server System Update (Andrew McConachie) * Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) (Ken Renard) 3. Reports * Chair/Vice Chair (Jeff Osborn and Ken Renard) * Liaison to the ICANN Board (Wes Hardaker) * Liaison to the CSC (Ken Renard) * Liaison to the IFR2 (Lars-Johan Liman) * Liaison to the RZERC (Daniel Migault) * Liaison from the IAB (Daniel Migault) * Liaison from the SSAC (Russ Mundy) * Liaison from the IANA Functions Operator (James Mitchell) * Liaison from the Root Zone Maintainer (Duane Wessels) * RSS GWG report (All) 4. Any Other Business (Jeff Osborn) * Next meeting: Wednesday, 12 June 2024 at 13:30 UTC at ICANN80 5. Adjournment (Jeff Osborn)

2 3

Doodle | Due by 2 May | Guidelines for Changing Root Server Addresses Work Party
by Ozan Sahin May 3, 2024

May 3, 2024

Dear RSSAC Caucus Members, The RSSAC has approved the attached Statement of Work (SoW) for Guidelines for Changing Root Server Addresses. This SoW calls for the creation of an RSSAC Caucus Work Party. We are organizing a kickoff teleconference which will be followed by an RSSAC Caucus work session at ICANN80 in June: * Week of 13 May – Kickoff Teleconference (Chair selection, review scope of work, wp management, discuss assignments) * 11 June 2024 - Second Teleconference/Meeting (RSSAC Caucus work session at ICANN80) If you would like to join the Guidelines for Changing Root Server Addresses Work Party, please indicate your availability for the kickoff teleconference by completing this doodle poll by Thursday, 2 May 2024: https://doodle.com/meeting/participate/id/dwRrPpJb For more information on RSSAC Caucus work parties please read section 2.6 in RSSAC000v8. <https://www.icann.org/en/system/files/files/rssac-000-op-procedures-15jan24…> Best, Ozan Sahin Policy Development Support Senior Specialist Internet Corporation for Assigned Names and Numbers (ICANN)

1 1

Security Incident Reporting Work Party Update
by Andrew McConachie April 30, 2024

April 30, 2024

Dear RSSAC Caucus Members, Robert and I met yesterday to work on the document. https://docs.google.com/document/d/1NvSw7PoLGYhXPuMEjiBgqjCtp_khTGGEh0DaHkN… After the mail I sent to the list on April 22 we received no feedback. So as agreed on the April 22nd work party call Section 6 was deleted and Section Y was renamed to Section 6. Also, we added 3 bullets in the new Section 6. Bullets 3, 4, and 5 are new and will be discussed on our next call. Finally, we cleaned up the document by merging grammar changes and added more references back to the Statement of Work in brackets []. Our next work party call is scheduled for May 6 at 15:00 UTC. Thanks, Andrew

1 0

RSSAC Caucus Travel Support for IETF 120 Vancouver, BC, Canada
by Ozan Sahin April 24, 2024

April 24, 2024

Dear RSSAC Caucus members, IETF 120 will take place in Vancouver, BC, Canada from 20 - 26 July 2024. There is travel support for up to four (4) RSSAC Caucus Members to attend IETF 120 including economy class airfare, accommodation, registration, and per diem. In 2019, RSSAC approved guidelines for RSSAC Caucus members requesting travel support to attend even-numbered IETF meetings. RSSAC updated these guidelines in April 2024. Please see the updated RSSAC Caucus IETF Supported Travelers Funding Guidelines attached. Depending on how many requests we receive, the RSSAC Administrative Committee may need to make the selection based on the selection criteria outlined in the guidelines. You may also find ICANN Community Travel Guidelines here: https://www.icann.org/resources/pages/travel-support-2012-02-25-en#guidelin… If you would like to apply and be considered for travel support, please complete the following form by Monday, 15 April 2024: https://forms.gle/rzGmab3s1F8mz33KA Best, Ozan Sahin Policy Development Support Senior Specialist Internet Corporation for Assigned Names and Numbers (ICANN) Mobile: +90 533 641 0007 Skype: ozan.sahin.icann www.icann.org<applewebdata://021EB1F1-F6B6-443A-908F-419605BF3A61/www.icann.org>

1 1

Closing in One Week | Nomination Period: RSSAC Delegate to the ICANN Nominating Committee
by Ozan Sahin April 22, 2024

April 22, 2024

Dear RSSAC Caucus Members, This is a reminder about the nomination period for the RSSAC Delegate to the 2025 ICANN Nominating Committee (NomCom). We have received one self-nomination from Erum Welling so far. Robert Story provided a second for Erum’s nomination. The nomination period will close at 23:59 UTC on Monday, 29 April 2024. If you would like to be considered for appointment, please indicate your interest on the RSSAC Caucus mailing list before the deadline. Best, Ozan Sahin Policy Development Support Senior Specialist Internet Corporation for Assigned Names and Numbers (ICANN) From: Ozan Sahin <ozan.sahin(a)icann.org> Date: 2 April 2024 Tuesday 13:26 To: "rssac-caucus(a)icann.org" <rssac-caucus(a)icann.org> Subject: Nomination Period: RSSAC Delegate to the ICANN Nominating Committee Dear RSSAC Caucus members, It is time to begin the selection process for the RSSAC Delegate to the 2025 ICANN Nominating Committee (NomCom). The role is a one-year term beginning at the conclusion of the Annual General Meeting to be held during ICANN81 in November 2024. Please refer to this page<https://www.icann.org/nomcom2024> for more information about the Nominating Committee. I have also copied below the relevant sections from “RSSAC000v8: Operational Procedures” for your reference. With this notice, a four-week nomination period via this distribution list is now open. Nominations or self-nominations will be accepted and require a second. Nominees must then accept or decline their nomination and may provide a statement with more context for their decision. The nomination period will close at 23:59 UTC on Monday, 29 April 2024. The RSSAC will then consider the slate of candidates during its May teleconference. As you may recall, ICANN Board approved some of the recommendations coming from the second organizational review of the ICANN NomCom and updated the ICANN Bylaws in October 2023. As a result, RSSAC appointee to the 2025 NomCom will be a voting delegate. In addition, NomCom delegates will serve two-year terms moving forward; however, RSSAC is among the groups that will start with a one-year term in 2025 NomCom for the purposes of staggering delegate terms - see section 27.5(a)<https://www.icann.org/resources/pages/governance/bylaws-en/#article27>. Finally, according to the Section 27.5(d) of ICANN Bylaws, “no person who served either or both of the two prior Nominating Committees (with terms ending at the ICANN Annual General Meeting in 2023 and 2024) is eligible for appointment to the Nominating Committee term commencing at the conclusion of the ICANN Annual General Meeting in 2024.” RSSAC appointed Hiro Hotta and Naveed bin Rais to 2023 and 2024 ICANN NomCom, respectively. Naveed’s one-year term will conclude by ICANN81, the Annual General Meeting. The RSSAC Leadership appreciates your consideration. Please do not hesitate to contact the RSSAC Chair and Vice Chair or support staff with any questions or concerns. Best, Ozan Sahin on behalf of Jeff Osborn, RSSAC Chair and Ken Renard, RSSAC Vice Chair 1.2.7.6 Outgoing RSSAC Delegate to the ICANN Nominating Committee The outgoing RSSAC Delegate to the ICANN Nominating Committee is specified in the ICANN Bylaws. The term for the outgoing RSSAC Liaison to the ICANN Nominating Committee shall be two years. No individual may serve as a delegate for more than two terms. In addition, no individual may serve in consecutive terms. An individual will only be eligible to serve a second term as a delegate on the Nominating Committee if a minimum of two years has elapsed between the end of their term and the beginning of the term for which they are being selected. The RSSAC must elect the outgoing RSSAC Liaison to the ICANN Nominating Committee according to the outgoing RSSAC liaisons election procedure (Section 1.2.7.9) from the members of the RSSAC Caucus. The outgoing RSSAC Liaison to the ICANN Nominating Committee acts as a conduit between the RSSAC and the ICANN Nominating Committee reporting on matters that need to be coordinated or communicated between the two bodies. The role requires discretion, management skills, and considerable time commitment. 1.2.7.9 Outgoing RSSAC Liaison Election Procedure One month prior to each election, nominations will be accepted for the outgoing liaison position and announced on the RSSAC distribution list. During the meeting that includes election of an outgoing liaison position on its announced agenda, additional nominations will be accepted, and all nominees will indicate their intentions: to accept or to decline their nomination. The RSSAC uses ranked choice voting, as outlined in Section 1.4.3 for electing outgoing liaison positions. In the event that only one candidate is standing for election, the RSSAC may elect the new outgoing liaison by acclamation. The RSSAC Chair will forward the name of the outgoing liaison-elect to the reciprocating body. If a vacancy exists in an outgoing liaison role, the RSSAC will elect a new outgoing liaison through this process.

1 0

Security Incident Reporting Work Party Update
by Andrew McConachie April 22, 2024

April 22, 2024

Dear RSSAC Caucus Members, The Security Incident Reporting Work Party held a meeting today. Below are two proposed deletions and two topics identified as needing more text. Please respond to this mail or add comments into the document by this Friday April 26 if you disagree with either of the deletions proposed below. (deadline April 26) -There is a new Section Y meant to replace Section 6. Unless anyone objects Section 6 will be deleted and Section Y will take its place. -Section Y contains an 8 point bulleted list. It is proposed to delete bullet point 8. Additionally, the work party went through the Statement of Work and identified two points that still need to be covered in the document. -Section 4 of the SoW, "How would incident reporting work?" generally requires more coverage in the working document. -Point 3.c in the SoW, "What are the roles of the RSS GS and RSOs with respect to reporting?" was also identified as needing more coverage. Specifically, the role of RSOs not yet sufficiently described in the working document. https://docs.google.com/document/d/1NvSw7PoLGYhXPuMEjiBgqjCtp_khTGGEh0DaHkN… Thanks, Andrew

1 0

Security Incident Reporting Work Party Update
by Andrew McConachie April 22, 2024

April 22, 2024

Dear RSSAC Caucus Members, Ken, Robert S and I met yesterday to work on the document. https://docs.google.com/document/d/1NvSw7PoLGYhXPuMEjiBgqjCtp_khTGGEh0DaHkN… Below are some changes we made to the document that we can discuss on our next work party call. -In Section 4.5 we reduced the number of categories from 5 to 3 by removing Catastrophic and Informational. The remaining incident categories are Low, Medium and Major. We also renamed the section "Incident Severity Guidelines". -Deleted the table in Section 4.5. It was originally Suggested for deletion during the meeting of March 25. -Created a new Section Y immediately before Section 6. The intention of Section Y is to eventually replace Section 6. It incorporates elements from Robert's Section X, that we discusssed on the last work party call, and Section 6. It's more high-level and less proscriptive than the current Section 6. -Deleted Section X and incorporated it's content into Section Y. -We started adding links back to the Statement of Work in brackets []. We want to be able to track where we are addressing the different elements in the SoW in the document. This bracketed text will be deleted prior to publishing the document. Please add any Suggestions into the document prior to our next work party call on April 22nd 15:00 UTC. Thanks, Andrew

4 4

REMINDER: RSSAC Caucus RSS Security Incident Reporting WP Teleconference | Every 2 weeks on Monday | 15:00-16:00 UTC
by ICANN Policy Calendar April 19, 2024

April 19, 2024

***REMINDER*** Ozan Sahin - ICANN Org is inviting you to a scheduled Zoom meeting. Topic: RSSAC Caucus RSS Security Incident Reporting WP Teleconference Work party wiki space: https://community.icann.org/x/5pWZDg Statement of work: https://docs.google.com/document/d/1qgzEAqmMHTwmZ23EH0vuE1SE-AWVK_NAddgv-3C… Working document: https://docs.google.com/document/d/1NvSw7PoLGYhXPuMEjiBgqjCtp_khTGGEh0DaHkN… Agenda: TBD Time: Mar 25, 2024 03:00 PM Universal Time UTC Every 2 weeks on Mon, until Jun 3, 2024, 6 occurrence(s) Mar 25, 2024 03:00 PM Apr 8, 2024 03:00 PM Apr 22, 2024 03:00 PM May 6, 2024 03:00 PM May 20, 2024 03:00 PM Jun 3, 2024 03:00 PM Please download and import the following iCalendar (.ics) files to your calendar system. Weekly: https://icann.zoom.us/meeting/tJIld-CurDwtGdF_gUUdTtfo6ds0cStgibLh/ics?icsT… Join Zoom Meeting https://icann.zoom.us/j/96809627735?pwd=LzdNWUNEYTUrVHVtRW9GcFNRYVpFdz09 Meeting ID: 968 0962 7735 Passcode: p.^gf2mWFA --- One tap mobile +13017158592,,96809627735#,,,,*5769317453# US (Washington DC) +13126266799,,96809627735#,,,,*5769317453# US (Chicago) --- Dial by your location • +1 301 715 8592 US (Washington DC) • +1 312 626 6799 US (Chicago) • +1 346 248 7799 US (Houston) • +1 669 900 6833 US (San Jose) • +1 929 436 2866 US (New York) • +1 253 215 8782 US (Tacoma) • 833 548 0282 US Toll-free • 877 853 5247 US Toll-free • 888 788 0099 US Toll-free • 833 548 0276 US Toll-free • +61 2 8015 6011 Australia • +61 3 7018 2005 Australia • +61 7 3185 3730 Australia • +61 8 6119 3900 Australia • +61 8 7150 1149 Australia • 1800 893 423 Australia Toll-free • 1800 945 157 Australia Toll-free • 1800 317 562 Australia Toll-free • +1 438 809 7799 Canada • +1 587 328 1099 Canada • +1 647 374 4685 Canada • +1 647 558 0588 Canada • +1 778 907 2071 Canada • +1 204 272 7920 Canada • 855 703 8985 Canada Toll-free • +81 3 4579 0545 Japan • +81 363 628 317 Japan • +81 3 4578 1488 Japan • 0 120 836 177 Japan Toll-free • 00 663 381 4092 Japan Toll-free • 0 800 100 5040 Japan Toll-free • 0 120 829 768 Japan Toll-free • +31 20 794 0854 Netherlands • +31 20 794 6519 Netherlands • +31 20 794 6520 Netherlands • +31 20 794 7345 Netherlands • +31 707 006 526 Netherlands • +31 20 241 0288 Netherlands • 0 800 025 0113 Netherlands Toll-free • 0 800 220 0040 Netherlands Toll-free • 0 800 022 1954 Netherlands Toll-free • +46 8 5016 3827 Sweden • +46 8 5050 0828 Sweden • +46 8 5050 0829 Sweden • +46 8 5052 0017 Sweden • +46 850 539 728 Sweden • +46 8 4468 2488 Sweden • 0 200 123 720 Sweden Toll-free • 0 201 604 329 Sweden Toll-free • 0 200 123 514 Sweden Toll-free Meeting ID: 968 0962 7735 Passcode: 5769317453 Find your local number: https://icann.zoom.us/u/absPrMkEEw

1 0

Nomination Period: RSSAC Delegate to the ICANN Nominating Committee
by Ozan Sahin April 9, 2024

April 9, 2024

Dear RSSAC Caucus members, It is time to begin the selection process for the RSSAC Delegate to the 2025 ICANN Nominating Committee (NomCom). The role is a one-year term beginning at the conclusion of the Annual General Meeting to be held during ICANN81 in November 2024. Please refer to this page<https://www.icann.org/nomcom2024> for more information about the Nominating Committee. I have also copied below the relevant sections from “RSSAC000v8: Operational Procedures” for your reference. With this notice, a four-week nomination period via this distribution list is now open. Nominations or self-nominations will be accepted and require a second. Nominees must then accept or decline their nomination and may provide a statement with more context for their decision. The nomination period will close at 23:59 UTC on Monday, 29 April 2024. The RSSAC will then consider the slate of candidates during its May teleconference. As you may recall, ICANN Board approved some of the recommendations coming from the second organizational review of the ICANN NomCom and updated the ICANN Bylaws in October 2023. As a result, RSSAC appointee to the 2025 NomCom will be a voting delegate. In addition, NomCom delegates will serve two-year terms moving forward; however, RSSAC is among the groups that will start with a one-year term in 2025 NomCom for the purposes of staggering delegate terms - see section 27.5(a)<https://www.icann.org/resources/pages/governance/bylaws-en/#article27>. Finally, according to the Section 27.5(d) of ICANN Bylaws, “no person who served either or both of the two prior Nominating Committees (with terms ending at the ICANN Annual General Meeting in 2023 and 2024) is eligible for appointment to the Nominating Committee term commencing at the conclusion of the ICANN Annual General Meeting in 2024.” RSSAC appointed Hiro Hotta and Naveed bin Rais to 2023 and 2024 ICANN NomCom, respectively. Naveed’s one-year term will conclude by ICANN81, the Annual General Meeting. The RSSAC Leadership appreciates your consideration. Please do not hesitate to contact the RSSAC Chair and Vice Chair or support staff with any questions or concerns. Best, Ozan Sahin on behalf of Jeff Osborn, RSSAC Chair and Ken Renard, RSSAC Vice Chair 1.2.7.6 Outgoing RSSAC Delegate to the ICANN Nominating Committee The outgoing RSSAC Delegate to the ICANN Nominating Committee is specified in the ICANN Bylaws. The term for the outgoing RSSAC Liaison to the ICANN Nominating Committee shall be two years. No individual may serve as a delegate for more than two terms. In addition, no individual may serve in consecutive terms. An individual will only be eligible to serve a second term as a delegate on the Nominating Committee if a minimum of two years has elapsed between the end of their term and the beginning of the term for which they are being selected. The RSSAC must elect the outgoing RSSAC Liaison to the ICANN Nominating Committee according to the outgoing RSSAC liaisons election procedure (Section 1.2.7.9) from the members of the RSSAC Caucus. The outgoing RSSAC Liaison to the ICANN Nominating Committee acts as a conduit between the RSSAC and the ICANN Nominating Committee reporting on matters that need to be coordinated or communicated between the two bodies. The role requires discretion, management skills, and considerable time commitment. 1.2.7.9 Outgoing RSSAC Liaison Election Procedure One month prior to each election, nominations will be accepted for the outgoing liaison position and announced on the RSSAC distribution list. During the meeting that includes election of an outgoing liaison position on its announced agenda, additional nominations will be accepted, and all nominees will indicate their intentions: to accept or to decline their nomination. The RSSAC uses ranked choice voting, as outlined in Section 1.4.3 for electing outgoing liaison positions. In the event that only one candidate is standing for election, the RSSAC may elect the new outgoing liaison by acclamation. The RSSAC Chair will forward the name of the outgoing liaison-elect to the reciprocating body. If a vacancy exists in an outgoing liaison role, the RSSAC will elect a new outgoing liaison through this process.

13 15

REMINDER: RSSAC Caucus RSS Security Incident Reporting WP Teleconference | Every 2 weeks on Monday | 15:00-16:00 UTC
by ICANN Policy Calendar April 5, 2024

April 5, 2024

***REMINDER*** Ozan Sahin - ICANN Org is inviting you to a scheduled Zoom meeting. Topic: RSSAC Caucus RSS Security Incident Reporting WP Teleconference Work party wiki space: https://community.icann.org/x/5pWZDg Statement of work: https://docs.google.com/document/d/1qgzEAqmMHTwmZ23EH0vuE1SE-AWVK_NAddgv-3C… Working document: https://docs.google.com/document/d/1NvSw7PoLGYhXPuMEjiBgqjCtp_khTGGEh0DaHkN… Agenda: TBD Time: Mar 25, 2024 03:00 PM Universal Time UTC Every 2 weeks on Mon, until Jun 3, 2024, 6 occurrence(s) Mar 25, 2024 03:00 PM Apr 8, 2024 03:00 PM Apr 22, 2024 03:00 PM May 6, 2024 03:00 PM May 20, 2024 03:00 PM Jun 3, 2024 03:00 PM Please download and import the following iCalendar (.ics) files to your calendar system. Weekly: https://icann.zoom.us/meeting/tJIld-CurDwtGdF_gUUdTtfo6ds0cStgibLh/ics?icsT… Join Zoom Meeting https://icann.zoom.us/j/96809627735?pwd=LzdNWUNEYTUrVHVtRW9GcFNRYVpFdz09 Meeting ID: 968 0962 7735 Passcode: p.^gf2mWFA --- One tap mobile +13017158592,,96809627735#,,,,*5769317453# US (Washington DC) +13126266799,,96809627735#,,,,*5769317453# US (Chicago) --- Dial by your location • +1 301 715 8592 US (Washington DC) • +1 312 626 6799 US (Chicago) • +1 346 248 7799 US (Houston) • +1 669 900 6833 US (San Jose) • +1 929 436 2866 US (New York) • +1 253 215 8782 US (Tacoma) • 833 548 0282 US Toll-free • 877 853 5247 US Toll-free • 888 788 0099 US Toll-free • 833 548 0276 US Toll-free • +61 2 8015 6011 Australia • +61 3 7018 2005 Australia • +61 7 3185 3730 Australia • +61 8 6119 3900 Australia • +61 8 7150 1149 Australia • 1800 893 423 Australia Toll-free • 1800 945 157 Australia Toll-free • 1800 317 562 Australia Toll-free • +1 438 809 7799 Canada • +1 587 328 1099 Canada • +1 647 374 4685 Canada • +1 647 558 0588 Canada • +1 778 907 2071 Canada • +1 204 272 7920 Canada • 855 703 8985 Canada Toll-free • +81 3 4579 0545 Japan • +81 363 628 317 Japan • +81 3 4578 1488 Japan • 0 120 836 177 Japan Toll-free • 00 663 381 4092 Japan Toll-free • 0 800 100 5040 Japan Toll-free • 0 120 829 768 Japan Toll-free • +31 20 794 0854 Netherlands • +31 20 794 6519 Netherlands • +31 20 794 6520 Netherlands • +31 20 794 7345 Netherlands • +31 707 006 526 Netherlands • +31 20 241 0288 Netherlands • 0 800 025 0113 Netherlands Toll-free • 0 800 220 0040 Netherlands Toll-free • 0 800 022 1954 Netherlands Toll-free • +46 8 5016 3827 Sweden • +46 8 5050 0828 Sweden • +46 8 5050 0829 Sweden • +46 8 5052 0017 Sweden • +46 850 539 728 Sweden • +46 8 4468 2488 Sweden • 0 200 123 720 Sweden Toll-free • 0 201 604 329 Sweden Toll-free • 0 200 123 514 Sweden Toll-free Meeting ID: 968 0962 7735 Passcode: 5769317453 Find your local number: https://icann.zoom.us/u/absPrMkEEw

1 0