- Ssr2-review - lists.icann.org

Re: [Ssr2-review] [EXT] Re: Please prepare for the plenary call on Thursday
by Barrett, Kerry-Ann Nov. 5, 2018

Nov. 5, 2018

HI Alain Unfortunately for me, it was difficult to follow which text was yours and which was previously written because of the text format. But I did understand your concerns from previous emails. What I think will happen is when we start to compile the final report we will be able to record what areas we think we were not able to do a sufficient review and maybe recommend follow up by the next SSR 3 (if the issue is still current/relevant). We will also be able to fine tune as well the language of our conclusions. I think we could also flag your email as a reference to ensure we addressed concerns raised below as well (which I have been following in previous and this email thread). Kerry-Ann Barrett Cybersecurity Program Officer Secretariat of the Inter-American Committee against Terrorism (CICTE) Secretariat for Multidimensional Security (SMS) Organization of American States 1889 F Street NW Washington D.C. 20006 (202) 370 4675 - (202) 458 3857 www.oas.org/cyber @KerryOAS| @OEA_Cyber Register to our distribution list here! -----Original Message----- From: Ssr2-review [mailto:ssr2-review-bounces@icann.org] On Behalf Of ALAIN AINA Sent: Monday, November 5, 2018 6:02 AM To: ICANN SSR2 <SSR2-review(a)icann.org> Subject: [EXT] Re: [Ssr2-review] Please prepare for the plenary call on Thursday Hello, > On 1 Nov 2018, at 23:39, Russ Housley <housley(a)vigilsec.com> wrote: > > >> On Nov 1, 2018, at 4:36 AM, ALAIN AINA <aalain(a)trstech.net> wrote: >> >> I still think the methodology we used for the assessment of the implementation of the 28 recommendations is not very suitable. We ended the following conclusions: >> >> 1- most of the recommendations are vague and not measurable and sometimes not implementable >> 2- we have not seen evidence of implementation and effect, and so the recommendation has not been fully implemented, effect can’t be measured, etc... >> >> on 1) we will have at some point, to review the board actions on the 28 recommendations and respond to certain aspects in our assessment. >> >> https://www.icann.org/resources/board-material/resolutions-2012-10-18-en#1.e >> >> On 2) we have not agreed on all documents or evidences required for our assessment. We shall also factor in the fact that the organisation has evolved over the years. The recommendations were issued on 2012, and implemented throughout up to 2017 and we are reviewing the impact in 2017/2018. >> >> the SSR framework and the implementation of some of the recommendations have influenced the Strategic plan and Operation plan and the 5 years operating plan regularly updated, have KPIs for programs to y19 and y20 which are SSR related. >> >> >> Most of the impact of the implementation in my opinion are to be investigated in strategic objectives and their implementation through activities portfolio throughout the years. We shall measure the impact from the KPI and deliverable in the OP, Annual report and also how SSR inputs and influences the strategic/ operation plannings and the prioritisation of the activities and projects. Engage with Staff, board and any other affected parties or constituencies by the recommendations. >> >> >> On the specifics. >> >> For example we claimed that definition of security in the registry agreement differs from the one published in the SSR framework, added to the ICANN glossary and supposed to be used in all materials. >> >> But, section 7.3 of the registry agreement does not define “security”, or “stability” but define what “effect on them mean or refer to" >> >> ====== >> >> (a) For the purposes of this Agreement, an effect on “Security” shall mean >> >> (1) the unauthorized disclosure, alteration, insertion or destruction of registry data, or (2) the unauthorized access to or disclosure of information or resources on the Internet by systems operating in accordance with all applicable standards. >> >> >> (b) For purposes of this Agreement, an effect on “Stability” shall refer to >> >> (1) lack of compliance with applicable relevant standards that are authoritative and published by a well-established and recognized Internet standards body, such as the >> >> ======= >> So using this example to justify a breach in the implementation of the recommendation is not appropriate in my opinion. > > Alain: > > The Bylaws say: > > (iv) The SSR Review Team shall also assess the extent to which > prior SSR Review recommendations have been implemented and the extent > to which implementation of such recommendations has resulted in the > intended effect. > > I think we have done what the Bylaws require. We are in full agreement on the task list as per the bylaws, especially on the SSR1 recommendations. I assumed it is still work in progress as you asked for comments/discussions. > > Some actions were taken to implement each of the recommendations. The write-up summarizes those actions. We concluded that some recommendations were not fully implemented, while staff concluded that they were all fully implemented. This would call for reviewing board/staff understanding of the recommendations, the implementation plan and actions taken to implement to eventually determine where the gap is. > > We made an assessment regarding whether those actions "resulted in the intended effect.” my main concern in this thread is about how this assessment was made. It needs a more structured approach than going through responses to some questions to staff and through some random documentation. > > In some cases, we have follow-on recommendations. > > We agreed that the wording of many SSR1 recommendations were not measurable, SSR1 like SSR2 is an “review” and i would say a ”high level review”, from which recommendations may not be directly measurable, as they affect strategic thinking/planning and operations of the organisation and/or the ecosystem. This is my last communication of the topic and as Boban suggested, would be good to hear what the team’s thoughts are about these points. Thanks —Alain > and we agreed to two things: > 1) Include some text regarding the situation. Your words above seem like a good strawman. > 2) When we write our recommendations, we will make sure that they are measurable. > > Russ > _______________________________________________ Ssr2-review mailing list Ssr2-review(a)icann.org https://mm.icann.org/mailman/listinfo/ssr2-review

1 0

Findings & recs template
by Jennifer Bryce Nov. 3, 2018

Nov. 3, 2018

Dear all, Here is the template for findings and recommendations that other specific review teams have used. As discussed on the call today, if you have any objections to adopting this template, please raise these within 24 hours of this email distribution. Best, Jennifer -- Jennifer Bryce Senior Reviews Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

4 3

Call summary: SSR2 1 November
by Jennifer Bryce Nov. 2, 2018

Nov. 2, 2018

Dear SSR2 RT members, Please find attached the plenary call report for SSR2 meeting #49, 1 November at 14:00 UTC. These high-level notes are designed to help SSR2 Review Team members navigate through the content of the call. They are not meant to be a substitute for the recording or transcript, which are posted on the wiki at: https://community.icann.org/x/awC8BQ. The transcript usually becomes available 5 - 7 business days after the meeting. Best, Jennifer -- Jennifer Bryce Senior Reviews Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

1 0

Re: [Ssr2-review] [EXT] Findings & recs template
by Barrett, Kerry-Ann Nov. 1, 2018

Nov. 1, 2018

Thanks Jen No objection from me. Only thought is if we can agree that as we use the template if we find ways to improve it we have flexibility to raise this with the team (I think this was raised during the call if I’m not mistaken). [OAS.org]<http://www.oas.org/> Kerry-Ann Barrett Cybersecurity Program Officer Secretariat of the Inter-American Committee against Terrorism (CICTE) Secretariat for Multidimensional Security (SMS) Organization of American States 1889 F Street NW Washington D.C. 20006 [http://www.oas.org/en/sms/signature_images/phone.png] (202) 370 4675 - [http://www.oas.org/en/sms/signature_images/fax.png] (202) 458 3857 www.oas.org/cyber<http://www.oas.org/cyber> @KerryOAS<https://twitter.com/KerryOAS>| @OEA_Cyber<https://twitter.com/OEA_Cyber> Register to our distribution list here!<http://oas.us11.list-manage.com/subscribe?u=353ff0663258ae5a775d460db&id=10…> From: Ssr2-review [mailto:ssr2-review-bounces@icann.org] On Behalf Of Jennifer Bryce Sent: Thursday, November 1, 2018 11:11 AM To: SSR2 <ssr2-review(a)icann.org> Subject: [EXT] [Ssr2-review] Findings & recs template Dear all, Here is the template for findings and recommendations that other specific review teams have used. As discussed on the call today, if you have any objections to adopting this template, please raise these within 24 hours of this email distribution. Best, Jennifer -- Jennifer Bryce Senior Reviews Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org<mailto:jennifer.bryce@icann.org> Skype: jennifer.bryce.icann www.icann.org<http://www.icann.org>

1 0

Re: [Ssr2-review] SSR2 Review Team Plenary Call | Thursdays @ 14:00 UTC
by Boban Krsic Nov. 1, 2018

Nov. 1, 2018

Dear all, Unfortunately, I am still in a parallel meeting and cannot participate in today's confcall. My apologies. BR, Boban. On 30.10.18 18:29, MSSI Secretariat wrote: > > > > SSR2 Review Team Plenary Call | Thursdays @ 14:00 UTC > > 08.11.2018 - > (Wiederkehrend) > > > Boban Krsic > > > > > Vorsitzender: > mssi-secretariat(a)icann.org > > > > "MSSI Secretariat" <mssi-secretariat(a)icann.org> > > Ort: > https://participate.icann.org/ssrreview/; tel://1-605-475-5619,*,,3134284787# > > > > > > > > > > > > > > > > > > > > > > > > > > aalain(a)trstech.net, Boban Krsic/Denic, denisemichel(a)fb.com, lists(a)osterweil.net, eric(a)osterweil.net, jaberamatogoro(a)gmail.com, > kaveh.ranjbar(a)board.icann.org, kc(a)caida.org, KABarrett(a)oas.org, kerryann.barrett(a)gmail.com, laurin.weissinger(a)yale.edu, > mahasbini(a)mahasbini.org, amin.hasbini(a)kaspersky.com, ma(a)mahasbini.org, norm(a)webcatcher.ca, ameen(a)cert-in.org.in, > noorul.ameen(a)meity.gov.in, ramkrishna(a)isoc.org.np, naveedbinrais(a)gmail.com, housley(a)vigilsec.com, smccormick(a)hackerone.com, > zarko.kecic(a)rnids.rs, karen.mulberry(a)icann.org, charla.shambley(a)icann.org, daniel.halloran(a)icann.org, david.conrad(a)icann.org, > jennifer.bryce(a)icann.org, john.crain(a)icann.org, laena.rahim(a)icann.org, larisa.gurnick(a)icann.org, negar.farzinnia(a)icann.org, > steve.conte(a)icann.org, brenda.brewer(a)icann.org, yvette.guigneaux(a)icann.org > Wiederkehrend: > > 'Datumsangaben anzeigen' einblenden Datumsangaben anzeigen > Zeitzonen: > Dieser Eintrag wurde in einer anderen Zeitzone erstellt. Die Zeit in dieser Zeitzone ist: 08.11.2018 > > > > > > Location: Adobe Connect via this link: https://participate.icann.org/ssrreview > > > > For audio - primary mobile: tel://1-605-475-5619,*,,3134284787#<tel://1-605-475-5619,*,,3134284787/> > > > > US (Toll Free): 1-866-546-3377 - dial number, enter passcode: 3134284787, then hit # > > (For International Numbers, click > here<file:///C:/Users/yvette.guigneaux/Desktop/ADOBE%20CONNECT/SSR2/REVIEW%20TEAM/International%20Number%20List.docx> or see below) > > > > > > Dear SSR2 Review Team, > > Plenary call will be weekly on Thursdays @ 14:00 UTC<https://community.icann.org/x/hyFyB> for 60 minutes. > > > > > For additional local times click here<https://www.timeanddate.com/worldclock/fixedtime.html?msg=SSR2+Plenary+Call…>. > > > For Dial Out requests: please email your phone number of preference to mssi-secretariat(a)icann.org<mailto:mssi-secretariat@icann.org> at least 24 > hours prior to the call and we’ll gladly dial you in. > > > > Please join the meeting via Adobe Connect via this link: https://participate.icann.org/ssrreview > > > * Upon logging into Adobe Connect, a pop up window will provide you the option to Dial Out to your Phone. > > * Enter your Phone Number* (Remember to change the Country Code if needed). > > * After joining the call, as a courtesy to others and the presenters, please MUTE your phone. > > * This can be done by selecting *6 on your keypad. To UNMUTE select *6 again. > > If you are unable to log into Adobe Connect and can only join via phone, > > You can join by dialing one of the access numbers below… > > Mobile: > tel://1-605-475-5619,*,,3134284787#<tel://1-605-475-5619,*,,3134284787/> > > Phone Only Controls: > https://go.conferencinghub.com/2kfp9 > > Primary Access Number: > 1-605-475-5619 > > Guest Passcode: > 313 428 4787 > > Additional Access: > > USA > 1-605-475-5619 > > USA > 1-712-770-4218 > > Canada, Calgary > +1 403 407 5801 > > Canada, Montreal > +1 514 669 5926 > > Canada, Toronto > +1 647 426 9175 > > Canada, Vancouver > +1 604 224 6903 > > Argentina, Buenos Aires > +54 (0) 11 5172 6020 > > Argentina (toll free) > 0800 800 1252 > > Australia, Sydney > +61 (0) 2 8017 5796 > > Australia, Melbourne > +61 (0) 3 8687 0554 > > Australia, Brisbane > +61 (0) 7 3015 0544 > > Australia (toll free) > 1 800 448 693 > > Austria, Vienna > +43 (0) 1 25302 1786 > > Austria (toll free) > 0800 8866 3414 > > Bahrain, Manama > +973 1619 8750 > > Bahrain (toll free) > 800 81231 > > Belarus (toll free) > 8 820 0011 0342 > > Belgium, Brussels > +32 (0) 2 400 6929 > > Belgium (toll free) > 0800 39280 > > Brazil, Sao Paulo > +55 11 4935 7170 > > Brazil, Rio de Janeiro > +55 21 4560 0071 > > Brazil (toll free) > 0800 887 0244 > > Bulgaria, Sofia > +359 (0) 2 491 6054 > > Bulgaria (toll free) > 00800 111 4951 > > Cambodia, Phnom Penh > +855 23 962 580 > > Canada (toll free) > 1 855 950 3725 > > Chile, Santiago > +56 (0) 2 2666 0712 > > Chile (toll free) > 171 800 835 945 > > China (national) > +400 613 8105 > > China, Beijing > +86 10 5667 0006 > > China, Shanghai > +86 21 2039 7083 > > Colombia, Bogota > +57 1 508 8125 > > Colombia (toll free) > 01 800 755 0054 > > Costa Rica (toll free) > 800 542 5351 > > Croatia (toll free) > 0800 222 836 > > Cyprus (toll free) > 800 97429 > > Czech Republic, Prague > +420 225 986 566 > > Czech Republic (toll free) > 800 701 533 > > Denmark, Copenhagen > +45 32 72 78 11 > > Denmark (toll free) > 80 70 35 87 > > Egypt (toll free) > 0800 000 0541 > > Estonia, Tallinn > +372 622 6569 > > Estonia (toll free) > 800 011 1577 > > Fiji (toll free) > 00800 3329 > > Finland, Helsinki > +358 (0) 9 2310 1676 > > Finland (toll free) > 0800 772 237 > > France, Paris > +33 (0) 1 70 37 16 57 > > France (toll free) > 0800 946 532 > > France (national) > 0811 655 102 > > France (national) > 0821 231 688 > > Germany, Frankfurt > +49 (0) 69 2222 10613 > > Germany, Munich > +49 (0) 89 2030 31208 > > Germany (national) > 01801 000 891 > > Germany (toll free) > 0800 588 9171 > > Greece, Athens > +30 211 181 3825 > > Greece (toll free) > 00800 128 906 > > Hong Kong > +852 3018 9119 > > Hong Kong (toll free) > 800 901 914 > > Hungary, Budapest > +36 1408 8968 > > Hungary (toll free) > 068 001 9675 > > Iceland (toll free) > 800 9004 > > India, Delhi > +91 (0) 11 6641 1393 > > India, Bangalore > +91 (0) 80 6127 6713 > > India, Mumbai MIME-Version: 1.0 > > +91 (0)22 6187 5029 > > India, Chennai > +91 (0)44 6688 6069 > > India (toll free) > 1800 200 9472 > > Indonesia, Jakarta > +62 21 2188 9094 > > Indonesia (toll free) > 007 803 321 8918 > > Ireland, Dublin > +353 (0) 1 526 9422 > > Ireland (national) > 0818 270 288 > > Ireland (toll free) > 1800 937 650 > > Ireland (national) > 1890 907 631 > > Israel, Tel Aviv > +972 (0)3 721 7954 > > Israel (toll free) > 1809 213 173 > > Italy, Milan > +39 02 3600 8007 > > Italy, Rome > +39 06 8750 0677 > > Italy (toll free) > 800 146 095 > > Japan, Tokyo > +81 (0) 3 4588 9606 > > Japan, Osaka > +81 (0) 6 4560 2417 > > Japan (mobile) > 0120 538 611 > > Japan (toll free) > 0120 759 200 > > Japan (national) > 0570 063 744 > > Kazakhstan (toll free) > 8800 333 7556 > > Kenya, Nairobi > +254 (0)20 529 3597 > > South Korea, Seoul > +82 (0) 2 6007 0087 > > South Korea (toll free) > 00798 6136 1526 > > Latvia, Riga > +371 6601 3641 > > Latvia (toll free) > 8000 4412 > > Lithuania, Vilnius > +370 5205 5486 > > Lithuania (toll free) > 8800 31443 > > Luxembourg > +352 2088 1910 > > Luxembourg (toll free) > 800 28437 > > Malaysia,Kuala Lumpur > +60 (0) 3 7724 8003 > > Malaysia (toll free) > 1 800 816 165 > > Mexico, Guadalajara > +52 33 4162 3995 > > Mexico, Mexico City > +52 55 8421 0858 > > Mexico, Monterrey > +52 81 4162 3851 > > Mexico (toll free) > 01 800 283 3131 > > Morocco, Casablanca > +212 (0) 520 48 0023 > > Morocco (toll free) > 0800 091 297 > > Netherlands, Amsterdam > +31 (0) 20 716 8346 > > Netherlands (toll free) > 0800 020 2598 > > New Zealand, Christchurch > +64 (0) 3 974 2592 > > New Zealand, Wellington > +64 (0) 4 909 4679 > > New Zealand, Auckland > +64 (0) 9 929 1832 > > New Zealand (toll free) > 0800 440 096 > > Nigeria, Lagos > +234 1 277 3948 > > Norway, Oslo > +47 21 00 48 16 > > Norway (toll free) > 800 56082 > > Oman (toll free) > 800 77243 > > Panama, Panama City > +507 8 339 783 > > Panama (toll free) > 00800 223 1431 > > Peru, Lima > +51 (0) 1 700 9588 > > Peru (toll free) > 0800 78127 > > Philippines, Manila > +63 (0)2 395 3435 > > Philippines (toll free) > 1 800 111 014 18 > > Poland, Warsaw > +48 22 295 3584 > > Poland (toll free) > 00 800 121 4357 > > Portugal, Lisbon > +351 21 424 5134 > > Portugal (toll free) > 800 784 443 > > Qatar (toll free) > 00 800 100 501 > > Romania, Bucharest > +40 (0) 21 529 1307 > > Romania (toll free) > 0800 801 036 > > Russia, Moscow > +7 495 705 9452 > > Russia (toll free) > 8 800 500 9272 > > Saudi Arabia (toll free) > 800 844 9140 > > Saudi Arabia (toll free) > 800 850 0228 > > Serbia (toll free) > 0800 190 700 > > Singapore > +65 6622 1799 > > Singapore (toll free) > 800 616 3193 > > Slovakia, Bratislava > +421 (0)2 3321 5508 > > Slovakia (toll free) > 0800 002 003 > > Slovenia (toll free) > 0800 80594 > > Slovenia, Ljubljana > 1 888 8200 > > South Africa, Johannesburg > +27 (0)11 589 8334 > > South Africa (toll free) > 0800 999 598 > > Spain, Madrid > +34 91 114 6654 > > Spain, Barcelona > +34 93 800 1947 > > Spain (toll free) > 900 828 036 > > Sri Lanka, Sri Lanka > +94 720 910 349 > > Sweden, Stockholm > +46 (0) 8 5065 3957 > > Sweden (toll free) > 0200 125 589 > > Switzerland, Geneva > +41 (0) 22 595 4796 > > Switzerland, Zurich > +41 (0) 44 580 7208 > > Switzerland (toll free) > 0800 740 361 > > Taiwan, Taipei > +886 (0) 2 2650 7322 > > Taiwan (toll free) > 00 801 615 190 > > Thailand, Bangkok > +66 (0) 2104 0766 > > Thailand (toll free) > 001 800 6136 1530 > > Turkey, Istanbul > +90 212 375 5032 > > Turkey (toll free) > 00 800 448829138 > > Ukraine (toll free) > 0800 500 923 > > UAE (toll free) > 8000 3570 2658 > > UK (03) > +44 (0)330 336 6011 > > UK (toll free) > 0800 358 6387 > > UK (national) > 0844 473 5018 > > UK (national) > 0845 545 0016 > > USA /Canada (toll free) > 1-866-546-3377 > > Uruguay (toll free) > 0004 019 0305 > > Venezuela, Caracas > +58 212 720 2580 > > Venezuela (toll free) > 0 800 100 8373 > > Vietnam, Hanoi > +84 4 4458 3324 > > Vietnam, Ho Chi Minh > +84 8 4458 1334 > > Vietnam (toll free) > 1201 1444 > > > > > MIME-Version: 1.0 > > > > > > > > > > > > > > > > -- Boban Kršić Chief Information Security Officer DENIC eG, Kaiserstraße 75-77, 60329 Frankfurt am Main, GERMANY E-Mail: krsic(a)denic.de, Fon: +49 69 272 35-120, Fax: -248 Mobil: +49 172 67 61 671 https://www.denic.de PGP Key-ID: 0x43C89BA9 Fingerprint: B974 E725 FEF7 CB3A E452 BEE0 5B80 73E9 43C8 9BA9 Angaben nach § 25a Absatz 1 GenG: DENIC eG (Sitz: Frankfurt am Main) Vorstand: Helga Krüger, Martin Küchenthal, Andreas Musielak, Dr. Jörg Schweiger Vorsitzender des Aufsichtsrats: Thomas Keller Eingetragen unter Nr. 770 im Genossenschaftsregister, Amtsgericht Frankfurt am Main

1 0

SSR1 Q&A update
by Jennifer Bryce Nov. 1, 2018

Nov. 1, 2018

Dear all, For your info, the latest table of SSR1 questions and answers is attached and posted to the wiki on this page<https://community.icann.org/x/girwAw>. * 3 questions require clarification from the RT, noted below. * 7 questions have a due date for 2 November. We expect answers to these questions by the end of day tomorrow. * 7 questions have a revised due date for week of 5 November, with latest delivery of answers to all questions by 9 November. In these cases, SMEs have asked for more time to be able to provide a complete and accurate answer to the question. Questions that require clarification from the RT are below, asked by either Denise or Noorul. Recommendation 4: ICANN should document and clearly define the nature of the SSR relationships it has within the ICANN Community in order to provide a single focal point for understanding the interdependencies between organizations. Question: What accounts for the inconsistencies between the different documents on the ICANN website that describe the nature of the SSR relationships it has within the ICANN community? Asked by: Denise, via email<https://mm.icann.org/pipermail/ssr2-review/2017-August/000564.html> Clarification requested: Could you please provide some concrete examples of discrepancies? Recommendation 11: ICANN should finalize and implement measures of success for new gTLDs and IDN fast track that expressly relate to its SSR-related program objectives, including measurements for the effectiveness of mechanisms to mitigate domain name abuse. Question: Within the area of recommendation 11 & 12 activities for which ICANN can be a facilitator or convener – is there more information on the steps that ICANN took over the past five years to facilitate activities that involve other entities that had primary ownership or responsibility on related activities? Asked by: Denise during briefing<https://community.icann.org/x/jXHwAw> Clarification requested: We’re not clear on what the question is asking. Ops & Finance briefing Question: There are many challenges in IDN WHOIS lookups. How do we get an accurate IDN WHOIS database for the Incident Handling process? Asked by: Noorul as follow-up to briefing<https://community.icann.org/pages/viewpage.action?pageId=64949767&preview=/…> Clarification requested: Can you please: * Clarify what is meant by "IDN WHOIS database" and by "Incident Handling process”? * Clarify the context in which this question pertains to SSR? -- Jennifer Bryce Senior Reviews Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

1 0

SSR2 1 Nov agenda and f2f action items
by Jennifer Bryce Oct. 31, 2018

Oct. 31, 2018

Dear SSR2 RT members, It was good to see some of you in person last week in Barcelona - I hope your travels home or onwards were uneventful. Below, please find the agenda for tomorrow’s SSR2 plenary meeting, and the draft action items from the face-to-face meeting at ICANN63. Agenda: Thursday 1 November at 14:00 UTC 1. Welcome, roll call, SOI updates * Staff to provide update to team regarding the Jan/Feb 2019 face-to-face meeting 2. Work plan<https://docs.google.com/spreadsheets/d/1as7wZJ215HhNSmwEhXEPTWg_8AjlU7OOtzI…> - approve the updated work plan ready to go to the Board 3. Update on SSR1 recommendations<https://docs.google.com/document/d/1qUxV4L-gS5xHmC4QQPGRk81MgQuhQvsbnEU7xxe…> work to date and outstanding 4. Internal SSR - team to sign up to topics<https://docs.google.com/document/d/1Eaj92r_ZbGBqO-2t3-tJv4Teqtix20Dly7C14XK…> and needed information 5. Review External SSR topics (KC working on document). 6. AOB 7. Confirm action items / decisions reached Draft action items: 21 & 24 October 2018 SSR2 face-to-face meeting, ICANN63 Barcelona (also attached) A record of the meeting can be found on the wiki here: https://community.icann.org/x/6Qy8BQ Day 1 - Sunday 21 October 2018 * ACTION ITEM: Staff to update and finalize Engagement Session slides based on RT comments (COMPLETE) * ACTION ITEM: Staff to re-circulate to list any questions requiring clarification from RT and continue to pursue answers to outstanding questions/update delivery dates as required. * ACTION ITEM: Scott to send question regarding recommendation 15 to staff via email (COMPLETE) * ACTION ITEM: Review Team members to complete text in Google doc for each SSR1 recommendation ahead of Wednesday 24 October meeting (COMPLETE) * ACTION ITEM: Staff to update Wednesday 24 October meeting agenda and circulate to RT along with background materials (COMPLETE) Day 2 – Wednesday 24 October 2018 * ACTION ITEM: Staff to provide all RT members with access to Trello and remove RT members who have resigned (COMPLETE). * ACTION ITEM: Staff to circulate CCT briefing slides to the SSR2 RT (COMPLETE). * ACTION ITEM: KC, Eric and any other volunteers to work on moving topics from DNS SSR topics<https://docs.google.com/document/d/1KWvdcZ2g8hBxUzvzPqgzVmsT4RZ5CbIo-N2IpUU…> document to SSR2 work steam topics<https://docs.google.com/document/d/1Eaj92r_ZbGBqO-2t3-tJv4Teqtix20Dly7C14XK…> document. * ACTION ITEM: Review Team to determine next steps for work stream 4 (future challenges). Team discussed including moving relevant topics to other work streams, or shortening the list of items to address and rebranding the work steam. * ACTION ITEM: Staff to research options for RT to book-end the ICANN64 meeting in Kobe with face-to-face meetings. * ACTION ITEM: Staff to research options for the RT to have a face-to-face meeting in late January or February 2019, and circulate a Doodle poll to RT with options. * ACTION ITEM: Staff to update work plan based on RT notes in the Google sheet and circulate to RT. * ACTION ITEM: Staff to create first draft of SSR2 post-ICANN63 blog and share with leadership for initial edits. * ACTION ITEM: Staff to send a note to the Review Team notifying them to the end of daylight savings time and impact on call time. Review Team members to advise any objections to keeping the call at 14:00 UTC by Friday 26 October EOD (COMPLETE). Best, Jennifer -- Jennifer Bryce Senior Reviews Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

1 0

SSR2 Plenary calls remain at 14:00 UTC with Standard Time change
by MSSI Secretariat Oct. 24, 2018

Oct. 24, 2018

Hello SSR2 Review Team! This note is to advise everyone that during the Face to Face meeting today, a conversation took place regarding the upcoming time change back to Standard Time. The members in attendance agreed to keep the plenary calls at 14:00 UTC. Depending on your location in the world, this might mean Thursday plenary calls will be one hour earlier for those who recognize Standard Daylight Time. Please advise of any objections to continuing the plenary calls at 14:00 UTC by EOB on Friday, 26 October. Also, everyone should have calendar invites for the next plenary on Thursday, 1 November 14:00 UTC. Thank you! With kind regards, Brenda --- Brenda Brewer, Projects & Operations Assistant Multistakeholder Strategy & Strategic Initiatives (MSSI) Internet Corporation for Assigned Names and Numbers (ICANN) Skype: brenda.brewer.icann

1 0

CCT briefing slides
by Jennifer Bryce Oct. 24, 2018

Oct. 24, 2018

Dear SSR2 RT, The slides from the CCT presentation have been posted to the wiki briefing materials page here<https://community.icann.org/display/SSR/Briefing+Materials>. Direct links below: * Briefing slides for SSR2: https://community.icann.org/display/SSR/Briefing+Materials?preview=/9076859… * Background slides containing all CCT recommendations: https://community.icann.org/display/SSR/Briefing+Materials?preview=/9076859… Best, Jennifer -- Jennifer Bryce Senior Reviews Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

1 0

Work items doc
by Jennifer Bryce Oct. 24, 2018

Oct. 24, 2018

Work items google doc: https://docs.google.com/document/d/1Eaj92r_ZbGBqO-2t3-tJv4Teqtix20Dly7C14XK… -- Jennifer Bryce Senior Reviews Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

1 0