January 2020 - Ssr2-review - lists.icann.org

ACTION REQUESTED: Doodle for SSR2 Webinars
by MSSI Secretariat Jan. 29, 2020

Jan. 29, 2020

Dear SSR2 RT members, As discussed on the call we are sending this Doodle<https://doodle.com/poll/hrzv269ixctvte37> to understand team member availability to join a webinar on the SSR2 draft report. Please complete the poll to indicate which slots you could attend. We will schedule two 60-minute webinars during that week to accommodate for time zone differences. https://doodle.com/poll/hrzv269ixctvte37 Your speedy reply is greatly appreciated. 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

Call summary: SSR2 29 January 2020
by Jennifer Bryce Jan. 29, 2020

Jan. 29, 2020

Dear SSR2 RT members, Please find attached the plenary call report for SSR2 meeting #99, 29 January 2020 at 15: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 here: https://community.icann.org/x/KwJhBw. The transcript usually becomes available 5 - 7 business days after the meeting. Best, Jennifer -- Jennifer Bryce MSSI Associate Project Manager Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

1 0

The SSR1 Recommendation table
by Heather Flanagan Jan. 29, 2020

Jan. 29, 2020

Hello all, As discussed on today’s call, please add your name to the 1-2 items from the list that you’re willing to work on to add the text on how to measure the completion of that recommendation. https://docs.google.com/spreadsheets/d/16Vx5o0_s3UlCmCB2Ht1nGyOWt8Ri2e8sIx0… <https://docs.google.com/spreadsheets/d/16Vx5o0_s3UlCmCB2Ht1nGyOWt8Ri2e8sIx0…> Heather

1 0

Re: [Ssr2-review] [EXT] Re: SSR2 agenda 29 January 2020
by Barrett, Kerry-Ann Jan. 29, 2020

Jan. 29, 2020

Dear Apologies as well, we have a ministerial courtesy visit at the office and our boss just asked for technical support for the meeting. [OAS.org]<http://www.oas.org/> Sincerely 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 Norm Ritchie Sent: Tuesday, January 28, 2020 8:13 PM To: ssr2-review(a)icann.org Subject: [EXT] Re: [Ssr2-review] SSR2 agenda 29 January 2020 CAUTION: EXTERNAL SENDER My apologies for tomorrow, Jan 29. I’m on vacation this week. … Norm On Jan 28, 2020, at 5:54 AM, Jennifer Bryce <jennifer.bryce(a)icann.org<mailto:jennifer.bryce@icann.org>> wrote: Dear SSR2 RT members, Below is the agenda for the next SSR2 plenary call, scheduled for Wednesday 29 January at 15:00 UTC. 1. Welcome, roll call, SOI updates * Cancun meeting - team members to confirm they have heard from ICANN travel and are proceeding to book flights 1. SSR1 recommendation proposal - see the 27 January email<https://mm.icann.org/pipermail/ssr2-review/2020-January/002079.html> from Russ 2. Tracking potential changes to the report post Public Comment 3. Webinars on the draft report 4. AOB 5. Confirm action items, decisions reached Best, Jennifer -- Jennifer Bryce MSSI Associate Project Manager 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/> _______________________________________________ Ssr2-review mailing list Ssr2-review(a)icann.org<mailto:Ssr2-review@icann.org> https://mm.icann.org/mailman/listinfo/ssr2-review _______________________________________________ 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

Re: [Ssr2-review] [EXT] Re: Recommendation Number 1
by Barrett, Kerry-Ann Jan. 29, 2020

Jan. 29, 2020

Just a thought The exercise we spoke about - to have a matrix that links/cross reference all Inter-related recommendations- would that address any critique that we are duplicitous and non specific. I agree there is a need to be clear what we expect the outcome to be is without being prescriptive on how to do it and I think we can achieve it in the text. As I said just a thought Sincerely, Kerry-Ann Barrett Cybersecurity Policy Specialist Organization of American States > On Jan 28, 2020, at 1:04 PM, Denise Michel <denisemichel(a)fb.com> wrote: > > CAUTION: EXTERNAL SENDER > > > I think we should keep the construct we have and add implementation guidance to SSR1 recommendations found not fully implemented. > > Thanks. > Denise > > Denise Michel > denisemichel(a)fb.com > > > On 1/27/20, 10:59 PM, "Ssr2-review on behalf of k claffy" <ssr2-review-bounces(a)icann.org on behalf of kc(a)caida.org> wrote: > > > > It's too late not to re-open the appendix, as I went at it > with my fine-tooth comb that transmogrified into a pitchfork. > some of that text is simply indefensible and must be substantiated > or removed. i put my comments in the wrong google doc (the > marked up one instead of clean one) and heather offered to > move them to the right place during the calm between the storms. > > I'm right with you that we have to pull out exactly what we > recommend for all the SSR1-Incompletes, as our biggest > gripe about the SSR1 recs were how un-SMART they were. we > cannot follow that gripe with "btw, go finish all of them, and > go look in the appendix where we hide many additional > recommendations, but also generally do not provide any SMART > version of what we recommend, nor even use the word "recommend". > > But, rather than have 27 new subrecommendations under > Recommendation 1, a bunch of which just point to other > Recommendations, I think we need to pull any SSR1 work > out into new recommendations, or drop them. The document > is just spaghetti o/w. > > But I am all in favor of someone else undergoing the exercise > Russ suggests because it will illuminate the problem. > > grumpy. > k > > > >> On Mon, Jan 27, 2020 at 02:26:17PM -0500, Russ Housley wrote: >> >> I have been thinking about the SSR1-related discussion on the team call last week. To avoid opening the SSR1 appendix back up, I am thinking that we could change Recommendation 1 to be VERY specific. Yes, I am aware that this suggestion is at odds with the ICANN SME plea that we "over engineer" our recommendations. However, this suggestion does provide a clear way for SSR3 to measure our first recommendation. I suggest that we structure the recommendation like this: >> >> Finish implementing SSR1 recommendations by: >> >> - Rec 1: Do X >> - Rec 2: Do Y >> ... >> - Rec 9: See SSR2 Rec 2 >> - Rec 10: Do ... >> - Rec 11: Do ... >> - Rec 12: See SSR2 Rec 3 >> ... >> - Rec 20: See SSR2 Rec 4 >> ... >> - Rec 26: (No further action needed) >> - Rec 27: See SSR2 Rec 5 >> - Rec 28: Do Z >> >> >> This approach tells the ICANN staff what we looked for and did not find, yet it would avoid reopening the appendix. What do you think? >> >> Russ >> > >> _______________________________________________ >> Ssr2-review mailing list >> Ssr2-review(a)icann.org >> https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_l… >> >> _______________________________________________ >> 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_… ) and the website Terms of Service (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_… ). 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. > > _______________________________________________ > Ssr2-review mailing list > Ssr2-review(a)icann.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_l… > > _______________________________________________ > 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_… ) and the website Terms of Service (https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_… ). 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. > > > _______________________________________________ > Ssr2-review mailing list > Ssr2-review(a)icann.org > https://mm.icann.org/mailman/listinfo/ssr2-review > > _______________________________________________ > 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

Recommendation Number 1
by Russ Housley Jan. 29, 2020

Jan. 29, 2020

I have been thinking about the SSR1-related discussion on the team call last week. To avoid opening the SSR1 appendix back up, I am thinking that we could change Recommendation 1 to be VERY specific. Yes, I am aware that this suggestion is at odds with the ICANN SME plea that we "over engineer" our recommendations. However, this suggestion does provide a clear way for SSR3 to measure our first recommendation. I suggest that we structure the recommendation like this: Finish implementing SSR1 recommendations by: - Rec 1: Do X - Rec 2: Do Y ... - Rec 9: See SSR2 Rec 2 - Rec 10: Do ... - Rec 11: Do ... - Rec 12: See SSR2 Rec 3 ... - Rec 20: See SSR2 Rec 4 ... - Rec 26: (No further action needed) - Rec 27: See SSR2 Rec 5 - Rec 28: Do Z This approach tells the ICANN staff what we looked for and did not find, yet it would avoid reopening the appendix. What do you think? Russ

5 4

SSR2 agenda 29 January 2020
by Jennifer Bryce Jan. 29, 2020

Jan. 29, 2020

Dear SSR2 RT members, Below is the agenda for the next SSR2 plenary call, scheduled for Wednesday 29 January at 15:00 UTC. 1. Welcome, roll call, SOI updates * Cancun meeting - team members to confirm they have heard from ICANN travel and are proceeding to book flights 2. SSR1 recommendation proposal - see the 27 January email<https://mm.icann.org/pipermail/ssr2-review/2020-January/002079.html> from Russ 3. Tracking potential changes to the report post Public Comment 4. Webinars on the draft report 5. AOB 6. Confirm action items, decisions reached Best, Jennifer -- Jennifer Bryce MSSI Associate Project Manager Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

3 2

FYI - ICANN the target of Cybersquatting
by Denise Michel Jan. 28, 2020

Jan. 28, 2020

A “company” called “ICANN Domain Service” registered <icannservice[.]com> and is using the domain name in connection with a search engine submission scam. Fake notices have been received by numerous parties. The domain name, which appears to have been registered a few days ago through GoDaddy, uses GoDaddy’s privacy/proxy service, Domains By Proxy, LLC. Best, Denise Denise Michel denisemichel(a)fb.com

2 1

Agenda items
by Weissinger, Laurin Jan. 27, 2020

Jan. 27, 2020

Hi Jennifer, I would like to add to things to the agenda: registry/registrar locks and webinars / outreach. All the best Laurin

1 0

SSR2 draft report published for Public Comment
by Jennifer Bryce Jan. 24, 2020

Jan. 24, 2020

Dear SSR2 Review Team, The Public Comment proceeding for the SSR2 draft report has been published here: https://www.icann.org/public-comments/ssr2-rt-draft-report-2020-01-24-en. An announcement to icann.org will be published imminently. Best, Jennifer -- Jennifer Bryce MSSI Associate Project Manager Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce(a)icann.org Skype: jennifer.bryce.icann www.icann.org

2 1