February 2019 - Ssr2-review

Questions from previous round
by Russ Housley Feb. 15, 2019

Feb. 15, 2019

There are five questions related to SSR1 that have not been closed. Are these questions still relevant? Would the response cause the team to revisit that portion of the report? If so, we need to clarify the first three questions and push for responses to the last two question. If not, we need to mark them as "resolved" in some fashion. Russ = = = = = = = = = = Clarifications requested from RT: Topic: SSR1 recommendation 4 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. Clarification requested (28 September & 1 November): Could you please provide some concrete examples of discrepancies? Topic: SSR1 recommendation 11 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. Clarification requested (28 September & 1 November): We’re not clear on what the question is asking. Topic: IDNs 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. Clarification requested (28 September & 1 November): 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? Questions outstanding from staff: Topic: SSR1 recommendation 11 The SSR1 review team called out a number of activities that were operational and within staff’s purview and contained in the SSR framework and called for implementation of measurements and metrics. Was that work done and is it captured anywhere? To clarify, as part of the SSR1 report related to rec 11, the SSR1 review team noted ICANN administration of the new gTLD Program, IDN program, significant SSR related issues that are in the framework. They called for more specific goals, measurements and impact assessment. Was that work done and is it captured somewhere else? What measurements exist, and are used, for the effectiveness of mechanisms to mitigate domain name abuse, as required in recommendation 11?

2 1

SSR2 Review Team Vacancy - GAC
by Robert Hoggarth Feb. 14, 2019

Feb. 14, 2019

Dear Russ and Jennifer, Thank you very much for recently sharing with the GAC the opportunity to name a replacement for Mohamad Amin Hasbini on the SSR2 Review Team. The GAC Leadership has asked me to advise you that the GAC will not be naming a replacement for Mr. Hasbini at this time. The committee will continue to follow your efforts and appreciates the recent update you shared on your work. Best regards, Rob --- Robert Hoggarth VP – Policy Development and GAC Relations Washington, D.C. +1 424 558 4805 From: gac-leadership <gac-leadership-bounces(a)icann.org> on behalf of Jennifer Bryce <jennifer.bryce(a)icann.org> Date: Thursday, January 24, 2019 at 10:40 AM To: GACLEADERSHIP <gac-leadership(a)icann.org> Cc: Katrina Sataki <katrina(a)nic.lv>, 'KEITH DRAZEK' <kdrazek(a)verisign.com>, "ssr2-review(a)icann.org" <ssr2-review(a)icann.org>, Heidi Ullrich <Heidi.Ullrich(a)icann.org>, GACSTAFF <gac-staff(a)icann.org>, Bart Boswinkel <bart.boswinkel(a)icann.org>, "fred(a)isc.org" <fred(a)isc.org>, Marika Konings <marika.konings(a)icann.org>, Carlos Reyes <carlos.reyes(a)icann.org>, Maureen Hilyard <maureen.hilyard(a)gmail.com>, Steve Sheng <steve.sheng(a)icann.org>, "bverd(a)verisign.com" <bverd(a)verisign.com>, Rod Rasmussen <rod(a)rodrasmussen.com>, "Aftab.siddiqui(a)gmail.com" <Aftab.siddiqui(a)gmail.com> Subject: [Gac-leadership] SSR2 Review Team vacancy Message sent on behalf of Russ Housley, Chair, SSR2 Review Team Dear GAC leadership, I’m writing on behalf of the SSR2 Review Team<https://community.icann.org/x/AE6AAw> regarding GAC-nominated member Mohamad Amin Hasbini’s resignation. Please note the SO/AC Chairs and the SSR2 Review Team are copied on this email for their information. Mr. Hasbini announced his resignation<https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_pipermail…> from the SSR2 Review Team on 16 January 2019. Operating Standards [icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2…> required by the ICANN Bylaws for reviews have not been completed and adopted by the Board, so we don’t have a formal process to follow regarding resignations from the SSR2 Review. Ultimately, since Mr. Hasbini is a GAC appointment, it is our understanding that the decision on whether or not to replace him rests with the GAC. The SSR2 Review Team would, of course, welcome any new members appointed by the community. The SSR2 currently is working on<https://community.icann.org/display/SSR/Work+Plan?preview=/64075835/1021394…> a draft report for public comment. The SSR2 Review Team leadership requests that SOs/ACs that are considering appointing new members at this juncture in the team’s work ensure that appointees have the knowledge and time to contribute to the SSR2 Review Team’s work in progress. I suspect that anyone joining the team today would have need to be very diligent to catch up with the rest of the team. Please let me know if I can provide more information, or if you would like to discuss. Kind regards, Russ Housley Chair, SSR2 Review Team -- 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

2 1

Call summary: SSR2 14 Feb
by Jennifer Bryce Feb. 14, 2019

Feb. 14, 2019

Dear SSR2 RT members, Please find attached the plenary call report for SSR2 meeting #60, 14 February 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 at: https://community.icann.org/x/GKAWBg. 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

SSR2 agenda 14 February
by Jennifer Bryce Feb. 13, 2019

Feb. 13, 2019

Dear SSR2 RT members, Below is the draft agenda for the next plenary meeting on Thursday 14 February at 15:00 UTC. 1. Welcome, roll call, SOI updates * May face-to-face meeting location * Kobe meeting dates reminder 2. Future challenges workstream discussion 3. AOB 4. Confirm action items / decisions reached 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

2 1

Update from the SSR2 Review Team
by Jennifer Bryce Feb. 13, 2019

Feb. 13, 2019

Sent on behalf of the Second Security, Stability, and Resiliency (SSR2) Review Team leadership team Dear Board Members and SO/AC/SG/C leaders: We are writing to share an update from the second Security, Stability, and Resiliency (SSR2<https://community.icann.org/x/AE6AAw>) Review Team’s recent meeting in Los Angeles. During the meeting, we completed our assessment of ICANN’s implementation of SSR1 recommendations from 2012, and we detailed the scope items for our remaining areas of focus, as guided by ICANN’s Bylaws (see Article 4, Section 4.6<https://www.icann.org/resources/pages/governance/bylaws-en/#article4.6>): * ICANN’s key security, stability, and resiliency activities. * Activities that impact the SSR of the Domain Name System (that ICANN contributes to/facilitates). * Challenges to the secure and resilient operation of the unique identifiers system. As part of the scoping exercise, we also identified additional information needed to advance our work and documented questions for the ICANN organization on each topic. The answers to the questions will help us to develop findings and eventually recommendations. On the third and final day of the meeting, we revisited our workplan<https://community.icann.org/display/SSR/Work+Plan?preview=/64075835/1042359…> and spent some time looking ahead to our next face-to-face meeting, which will be at ICANN64<https://meetings.icann.org/en/kobe64> in Kobe. While we hoped to have draft recommendations to present to the community in Kobe, we will instead use the face-to-face meeting time to reach consensus on the findings for the remaining three workstreams of our review, and advance the drafting of our report. At ICANN64 we also will hold an engagement session with the community where we will discuss our work to date. We expect to share our draft findings and recommendations with the community at ICANN65 in Marrakech, with a view to publishing our draft final report in August 2019, and then presenting our final report in November 2019 at ICANN66 in Montreal. Meet with us at ICANN64 Let us know via our mailing list at input-to-ssr2rt(a)icann.org<mailto:input-to-ssr2rt@icann.org> (publicly archived) if you would like to set up a consultation with us in Kobe, separate from our general engagement session. The SSR2 Review Team encourages everyone to share their views throughout our work, either in person or via our mailing list. Russ Housley (Chair) Denise Michel (Vice-Chair) Eric Osterweil (Vice-Chair) Laurin Weissinger (Vice-Chair) -- 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

ICANN SSR answers FAO Kerry-Ann, Denise
by Jennifer Bryce Feb. 13, 2019

Feb. 13, 2019

Dear SSR2 RT members, As answers to questions from the LA meeting are received, they will be shared on list and to the Q&A document of the relevant workstream (found on the wiki page here<https://community.icann.org/x/WLnRAw>). RT members who volunteered for the topic will be highlighted, so that they are aware questions have been answered. See below for answers to 2 questions. Review Team volunteers: Kerry-Ann and Denise Workstream: ICANN SSR Topic 7: Perform an assessment how effectively ICANN has implemented its processes to ensure compliance regarding registrar agreements and the consensus policies Q: Please provide details on outreach or other efforts, and training, to inform or improve uptake among new gTLD registries, legacy gTLDs and ccTLDs, for DNSSEC and DNS operations. A: ICANN provides extensive outreach with the technical community, regional TLD organizations, both gTLD and ccTLD managers on DNSSEC and DNS issues. For some examples, see * this blog from August 2018 (https://www.icann.org/news/blog/icann-and-nsrc-collaborate-on-training-even…) * these reports by OCTO (https://www.icann.org/octo and https://www.icann.org/news/blog/office-of-the-cto-activities-brief-january-…, * ICANN IDS 2018: https://www.icann.org/ids-2018 * ICANN IDS 2017: https://www.icann.org/ids-2017 * DNSSEC session at APRICOT 2018 in Kathmandu * DNSSEC train-the-trainer event in Ankara, Turkey in April 2018 * Regional DNSSEC trainings with ccTLD managers, ISPs, government representatives * Regional DNS abuse trainings with public safety entities * Autumn School on Internet Governance, CSUC Barcelona, https://www.ibei.org/en/introduction_108857 (several technical sessions) * Extensive community outreach on root KSK rollover and DNSSEC preparedness over past 18+ months, https://www.icann.org/resources/pages/ksk-rollover Q: Do you provide such specific training (not high level info session) at ICANN and other related industry events? A: As noted above, ICANN provides specific training at DNS ecosystem events, either in collaboration with regional partners, ccTLD managers, or other Internet organizations. At ICANN meetings, these run from How It Works sessions on Internet identifiers and the root server system to DNS abuse mitigation with the Public Safety Working Group. ICANN also delivers the long-running DNSSEC Workshops and Tech Day sessions, which provide current research on DNS technical topics. Examples include: * How It Works DNS Fundamentals Barcelona: https://63.schedule.icann.org/meetings/901660 (How It Works sessions were repeated during ICANN 63) * How It Works DNS Abuse Barcelona: https://63.schedule.icann.org/meetings/901661 * How It Works Internet Networking: https://63.schedule.icann.org/meetings/901685 * How it Works Root Server Operations: https://63.schedule.icann.org/meetings/901686 * ccNSO TLD-Ops Disaster Recover Workshop Barcelona * GAC Technical Seminar on WHOIS and Data Protection/Privacy Issues * Tech Day Barcelona https://63.schedule.icann.org/meetings/901669 * DNSSEC Workshop Barcelona (example https://63.schedule.icann.org/meetings/901549 ) * Identifier Technology Health Indicators session https://63.schedule.icann.org/meetings/901638 * Domain Abuse Activity Reporting session https://63.schedule.icann.org/meetings/901700 * Other regional DNS training such as hands-on DNS abuse mitigation workshop in Uganda in January 2019 with AFRINIC; DNS training at PACNOG, BTNOG, LKNOG, SANOG, DNSSEC training with TWNOG, Mongolia, Kuwait, Brunei, Philippines, India, Bhutan * DNS abuse at African Forum on Cybercrime 2018 * DNS abuse training with Interpol, Europol -- 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

Wiki page of SSR2 documents
by Jennifer Bryce Feb. 11, 2019

Feb. 11, 2019

Dear SSR2 RT members, For your information, please note this page on the wiki, which has been updated to list all of the Review Team’s current documents by workstream: https://community.icann.org/x/WLnRAw. Please let me know if you see anything amiss or have questions. 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

SSR1 Recommendations, Overview Section
by Weissinger, Laurin Feb. 10, 2019

Feb. 10, 2019

Dear all, As agreed in LA, I added an “overview” section on page 4 of the SSR1 recommendations document, summarising findings and the general comments we discussed: https://docs.google.com/document/d/1WwzmsBDEtI0uvrxqSIs7zaBZRalZkC-TwO1VE_p… Please review this section by end of day (Pacific), Wednesday 13th of February. Please use the “comment” feature. Many thanks and all the best Laurin

1 0

Questions From SSR2 Coming Soon
by Russ Housley Feb. 5, 2019

Feb. 5, 2019

David: SSR2 will be sending two batches of questions. The first should arrive in the next few days, and the second should arrive in a week. I am writing to ask for prompt answers. As you know, SSR2 has not gone smoothly, but the whole SSR2 Review Team is striving to produce a quality report in a timely manner. To do that, we need your help. In the pat, the bulk of our questions have been answered by OCTO, so I am wring to you. We recognize that some of the questions may require coordination with other parts of ICANN Org. In the past, some of our questions have taken many months to receive responses. Worse, in some cases, it has taken months to be told that the question was not understood. Delay like this will put the SSR2 schedule in jeopardy. If you look at the SSR2 Work Plan, you will see that we have a very tight schedule. For the team to meet the schedule, I ask the following: 1) If clarifications are needed to understand a question, please get back to the team in a few days after receiving the question. 2) Most of the questions can be answered with a pointer to a document or web page. For these questions, please respond to the team in one week. 3) A small number of the questions will require gathering information. For these questions, please respond to the team in two weeks. The SSR2 Review Team understands that you and your staff are busy, but we cannot produce a quality report on schedule without your assistance in gathering this information. Thanks in advance, Russ

2 2

SSR2 updated workplan
by Jennifer Bryce Feb. 5, 2019

Feb. 5, 2019

Dear all, The attached workplan reflects the discussion during last week’s plenary meeting. Each workstream has been updated to include the following rows: Conduct further information gathering and/or interviews as appropriate Get follow-up questions answered Please share any further edits on-list by 23:59 UTC on Wednesday 6 February. After this time, the workplan will be posted to the wiki, and shared with the community via the team’s post-LA meeting blog, once this is published. 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