- Ssr2-review - lists.icann.org

Re: [Ssr2-review] [EXT] Do we have full consensus?
by Barrett, Kerry-Ann Jan. 13, 2021

Jan. 13, 2021

Just a general feedback that I really like the restructuring and wanted to acknowledge the team members and Heather who really worked on making this readable and findings transparent and solid. I left a few minor comments and I know Heather may be looking at them as I write this ☺ [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 Russ Housley Sent: Tuesday, January 12, 2021 4:20 PM To: ICANN SSR2 <ssr2-review(a)icann.org> Subject: [EXT] [Ssr2-review] Do we have full consensus? CAUTION: EXTERNAL SENDER I would like to add a sentence to the final report: All of these recommendations have full consensus for the SSR2 Review Team. If you do not agree with that, please send a note to the mail list prior to the call on Thursday. Thanks, Russ On Jan 12, 2021, at 4:16 PM, 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 Thursday 14 January @ 15:00 - 17:00 UTC. Please note this is the last planned meeting. 1. Welcome, roll call, SOI updates 2. Determine consensus level on Final Report <https://docs.google.com/document/d/1rMdW1YCebe6Yj678OUrlc3TsACZsqmwuqN3yaIj…> * Note addition to the findings text on p41 1. Review and determine consensus level on public comment response spreadsheet<https://docs.google.com/spreadsheets/d/1DQpPA0aLDsW5IHLKgQqHtW-5860CKGCuTYI…>. Note the following (per Russ’s 8 January email<https://mm.icann.org/pipermail/ssr2-review/2021-January/002417.html>): * “ROW 40: The response includes the phrase: "The review team did reach out". I would like confirmation that the subteam took this action. If that did not happen, we need to correct the response text.” * “ROWS 235 and 326: We realized that the Abuse Subteam had agreed to say something about brand TLDs, but it did not make it into the document. Laurin and Heather have proposed some text for the report. The text appear in suggest mode on pages 40 and 41 of the report. The public comment response only makes sense if these small additions are added to the report. Please make sure you review these proposed changes. If these late changes are not acceptable to the whole RT, then we need to acknowledge that this comment fell through the cracks.” 1. Determine implementation shepherds 2. Next steps – timeline to submit the report to the Board, and possible community webinar 3. AOB 4. Confirm action items & decisions reached Best, Jennifer

1 0

SSR2 plenary agenda | 14 January 2021 @ 15:00 - 17:00 UTC
by Jennifer Bryce Jan. 12, 2021

Jan. 12, 2021

Dear SSR2 RT members, Below is the agenda for the next SSR2 plenary call, scheduled for Thursday 14 January @ 15:00 - 17:00 UTC. Please note this is the last planned meeting. 1. Welcome, roll call, SOI updates 2. Determine consensus level on Final Report <https://docs.google.com/document/d/1rMdW1YCebe6Yj678OUrlc3TsACZsqmwuqN3yaIj…> * Note addition to the findings text on p41 3. Review and determine consensus level on public comment response spreadsheet<https://docs.google.com/spreadsheets/d/1DQpPA0aLDsW5IHLKgQqHtW-5860CKGCuTYI…>. Note the following (per Russ’s 8 January email<https://mm.icann.org/pipermail/ssr2-review/2021-January/002417.html>): * “ROW 40: The response includes the phrase: "The review team did reach out". I would like confirmation that the subteam took this action. If that did not happen, we need to correct the response text.” * “ROWS 235 and 326: We realized that the Abuse Subteam had agreed to say something about brand TLDs, but it did not make it into the document. Laurin and Heather have proposed some text for the report. The text appear in suggest mode on pages 40 and 41 of the report. The public comment response only makes sense if these small additions are added to the report. Please make sure you review these proposed changes. If these late changes are not acceptable to the whole RT, then we need to acknowledge that this comment fell through the cracks.” 1. Determine implementation shepherds 2. Next steps – timeline to submit the report to the Board, and possible community webinar 3. AOB 4. Confirm action items & decisions reached Best, Jennifer -- Jennifer Bryce Project Manager, Review Support and Accountability Internet Corporation for Assigned Names and Numbers (ICANN) Skype: jennifer.bryce.icann Email: jennifer.bryce(a)icann.org

2 1

Public Comment Responses - Please Review
by Heather Flanagan Jan. 8, 2021

Jan. 8, 2021

Hello SSR2 Review Team, The proposed responses to the public comments are complete. Please take a moment and read through them on the second tab in the spreadsheet, “Proposed Responses." https://docs.google.com/spreadsheets/d/1DQpPA0aLDsW5IHLKgQqHtW-5860CKGCuTYI… The final report is available here: https://docs.google.com/document/d/1rMdW1YCebe6Yj678OUrlc3TsACZsqmwuqN3yaIj… Two points of note: 1. Regarding Line 40 and the comment from the NCSG, "#Recommendation 4 deals with Budget Transparency and Budgeting SSR in the new gTLDs. We suggest that the SSR2 team check how or whether this is related or could be integrated into the ongoing work of the new gTLDs PDP working group.” I do not have any information on whether the RT actually reached out to the new gTLD PDP working group, and so the pubic comment response needs to be verified by the RT. 2. Regarding Lines 235 and 326, both of which offer feedback on how brand TLDs should be handled in the CZDS, this resulted in a one-line change to the final report. See page 40-41; the change is highlighted via suggest mode. Thank you for this last bit of effort to wrap up this report, and I look forward to our call on the 14th! Heather Flanagan — Translator of Geek to Human https://sphericalcowconsulting.com

2 1

Time to get that final consensus call
by Russ Housley Dec. 21, 2020

Dec. 21, 2020

Dear SSR2 RT, This is the consensus all on the final report: https://docs.google.com/document/d/1rMdW1YCebe6Yj678OUrlc3TsACZsqmwuqN3yaIj… <https://docs.google.com/document/d/1rMdW1YCebe6Yj678OUrlc3TsACZsqmwuqN3yaIj…> If you see anything that needs further editorial attention in the report, please let Heather know. Please use suggest mode. Heather incorporated item discussed on the plenary call lat Thursday. Please review before the next call on January 14th. Please post any concerns about the report before that call. Alos, please let us know if you intent to include a dissenting opinion about anything. Happy holidays, Russ

1 0

Call summary: SSR2 Plenary - 17 December 2020
by Brenda Brewer Dec. 18, 2020

Dec. 18, 2020

Dear SSR2 RT members, Please find attached the plenary call report for SSR2 plenary #132, 17 December 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/DAENCQ. The transcript will be posted 5-7 days after call. With kind regards, Brenda --- Brenda Brewer Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

Thursday is the last call about SSR2 Report
by Russ Housley Dec. 17, 2020

Dec. 17, 2020

SSR2 Review Team: We are getting close to the end! Please read the report and have your comments and concerns ready for discussion on the two-hours team call on Thursday: https://docs.google.com/document/d/1myG9dtYYiL8lFd3ZOPXNUwKfr1yuAsNrwzod-J8… <https://docs.google.com/document/d/1myG9dtYYiL8lFd3ZOPXNUwKfr1yuAsNrwzod-J8…> Please put comments in the report in advance; use suggest mode. If you have any solutions to the few remaining questions asked by Heather, please offer suggested resolutions. Again, use suggest mode. Finally, by close of business, please complete the following survey: https://tufts.qualtrics.com/jfe/form/SV_eLm7NIjU8hmOvw9 The survey results will also be discussed on Thursday. The survey will determine what the report includes about priority Russ P.S. On January 14th, we will have a call about the public comment response. Hopefully, there will be no need to talk about the report on that call.

2 2

Call summary: SSR2 Plenary - 10 December 2020
by Brenda Brewer Dec. 15, 2020

Dec. 15, 2020

Dear SSR2 RT members, Please find attached the plenary call report for SSR2 plenary #131, 10 December 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/CgENCQ. With kind regards, Brenda --- Brenda Brewer Internet Corporation for Assigned Names and Numbers (ICANN)

1 0

SSR2 plenary agenda | 17 December 2020 @ 15:00 - 17:00 UTC
by Jennifer Bryce Dec. 15, 2020

Dec. 15, 2020

Dear SSR2 RT members, Below is the agenda for the next SSR2 plenary call, scheduled for Thursday 17 December @ 15:00 - 17:00 UTC. Please note this is the last planned meeting to discuss the report. 1. Welcome, roll call, SOI updates 2. Discuss comments/concerns regarding SSR2 Final Draft<https://docs.google.com/document/d/1myG9dtYYiL8lFd3ZOPXNUwKfr1yuAsNrwzod-J8…> Google document (please add comments to the document in advance of the call) 3. Discuss results of the prioritization survey (please complete the survey by EOD Wednesday 16 December – access here: https://tufts.qualtrics.com/jfe/form/SV_eLm7NIjU8hmOvw9) 4. Next steps * Next plenary meeting scheduled for Thursday 14th January (15:00 – 17:00 UTC) – purpose of this meeting is to discuss the public comment response spreadsheet 5. AOB 6. Confirm action items, decisions reached Best, Jennifer -- Jennifer Bryce Project Manager, Review Support and Accountability Internet Corporation for Assigned Names and Numbers (ICANN) Skype: jennifer.bryce.icann Email: jennifer.bryce(a)icann.org

1 0

SSR2 Report - Final Draft
by Heather Flanagan Dec. 13, 2020

Dec. 13, 2020

Hello SSR2 Review Team, The draft final report is available now for your review. I have not included a table with all the recommendations yet; I’d very much like you all to read the recommendations in context. I will build that table after the RT indicates acceptance of the draft. https://docs.google.com/document/d/1myG9dtYYiL8lFd3ZOPXNUwKfr1yuAsNrwzod-J8… A few notes: There are 13 questions/comments pending. I expect most are easily resolved, but I’d like to point to four areas in particular: 1. Logically speaking, the findings in support of the C-Suite position recommendation are the weakest in the report. If anyone has citable examples of how you determined that there is a "risk of communications failures around critical security matters and the potential for conflicts around the prioritization of the budget” as well as a citable example of how the lack of a C-Suite role "has led to the ineffective documentation and implementation of security control measures organization-wide” that would be fantastic. 2. I have gone ahead and removed the Baseline Security Practices recommendation. I have not heard back from Naveed with more specific text, based on our conversation during the last plenary call, this definitely seems like a good idea, but not one in response to a specific problem observed by the RT (which makes it fall outside the Operating Standards for Specific Reviews). 3. I believe that Recommendation 20.1 can be removed, but as we have not discussed that as a group, I have left that removal as a suggestion. 4. And last but not least, given how we’ve supported the document at this point, do we still want to have a table that links every recommendation to a strategic plan line item? I have not re-built that table, but am happy to do so if the RT thinks it still has value. Feedback is always welcome. And of course, if you want to make changes in the doc, please do it in suggest mode. Heather Flanagan — Translator of Geek to Human https://sphericalcowconsulting.com

1 0

A question regarding the decrease in delegation of new gTLDs
by Heather Flanagan Dec. 10, 2020

Dec. 10, 2020

Hello all, In the Name Collision section, the RT states the following: "However, it is important to note that decrease of traditional reporting mechanisms of name collisions may not be seen as absence of name collisions. Rather, the SSR2 Review Team believes that it could be because the nature of occurrence of name collisions might have been changed as well as the decrease in the delegation of new gTLDs in recent years." I’d like to point to something where a reader can verify that there has been a decrease in the delegation of new gTLDs in recent years. The original draft text did not include a pointer to anything that backs up this statement. I had thought to point to https://newgtlds.icann.org/en/program-status/statistics, but as far as I can tell, that site does not offer insight into the rate of delegation over time. The page is a rather strange combination of current data, updated monthly, and stats from 2012-2013, and nothing in between. Am I looking at the right place for this kind of data? Does anyone have any better data to cite? Heather Flanagan — Translator of Geek to Human https://sphericalcowconsulting.com

2 3