Dear all, Please find below a v1 draft of the discussion points raised during the ICANN58 engagement session, Sunday 12 March. They have also been posted on the wiki<https://community.icann.org/display/SSR/ICANN+58+-+Engagement+Session>. Please advise if you have any additional points to include. SSR2 Public Consultation: Discussion Points 12 March 2017 @ 13:45 DRAFT v1 Review team members present: * Geoff Huston * Eric Osterweil * Emily Taylor * Denise Michel * Mohamad Amin Hasbini * Žarko Kecić * Cathy Handley * Ram Krishna Pariyar * Jabhera Matogoro * Boban Krsic * Kaveh Ranjbar * Alain Aina * Don Blumenthal (remote) INTRO: * ET: The meaning of the words in ICANN’s bylaws (ICANN’s commitment to enhance operational stability, reliability, resiliency, security, global interoperability) are complex. Many of these words will need to be teased out and understood in more detail. * ET: What areas are you interested in having the SSR team focus on? OPEN FORUM: * (David Conrad, ICANN CTO): When the AOC was written, footnote 1 redefined the term DNS to refer to the DNS as well as IP addresses and protocol parameters. In Bylaws 4.6 it talks about unique identifiers but in C.iii it talks about DNS. Review Team should clarify, is that DNS in the traditional sense of DNS or the redefinition in the AOC? * ET: Team must define a scope that’s tractable and useful. * AA: Suggest when team publishes materials, need footnote if referring to AOC definition. * (Audience member): Will the review cover DNS software? * How will the review incorporate youth perspective? * Will compliance issues be addressed? * DM: New gTLDs were not launched at the time of SSR1. How has the domain name space has evolved and abuse mitigation issues surrounding that? IDNs, do these raise security and resiliency issues? * MH: ICANN 10 yrs ago is not ICANN today, more digital and connected – all using unique identifiers to communicate – hope to look into the security issues for the future, smart cities cannot afford to be disconnected. * AA: Unique identifiers evolving significantly. Some of the challenges involve stability. It will be good to see how ICANN is dealing with ensuring SSR of the unique identifiers. ICANN doesn’t have an operational role of the identifiers but it has talked to other entities and it will be good to look at how relationships work, etc. Since last review, it’s important to see how things have improved, including post-IANA transition. * CH: Need forward looking forward review – with changes coming changes (IOT, smart cities etc.). Changes will continue to speed up. Need to look at policies, how they are established/changing and how they affect the review that we do. * KR: I want to focus on 3 areas. 1. Scope (in terms of policy). Eg. How deep should ICANN go in policy making? 2. Consistency of policies (in terms of rationale behind) 3. Requirements for registering a name. 3. The only way to get registrant information is WHOIS, but if you can’t write your address in Latin, by policy you can’t have a domain name. These things need to be harmonized. * Audience member: How does this report interplay with subsequent procedures? * David Conrad: Recommendations should be actionable and easily understood. Clear action items and context. * Audience member: Consider the effectiveness of ICANN’s comms strategies and transparency as we move forward. Eg. has there been an instance of a major stability issue w operation of DNS or led to outage of root zone. In addition to the issue and what actions were taken, I’d be interested in how effective was the comms strategy, and how open/ clear was the reporting of such incidence. Within the context of ICANN’s role. * Audience member: Name collision and ICANN’s relationship w/ IETF around special use names * MH: Abuse of unique identifiers. Need to forecast what will be happening in the next few years. * EO: Privacy vs. the way threat intelligence is used with telemetry * ET: Should we look at block chain technologies? * EO: Review team should describe the ways the interdependencies make up the security and stability landscape. * MH: how much is SSR2 able to collect info from a legal enforcement perspective – those who are most involved in cyber warfare related issues. * Steve Conte, ICANN: Review team should set up dialogue with Public Safety Working Group. Best, Jennifer -- Jennifer Bryce Senior Reviews Coordinator Internet Corporation for Assigned Names and Numbers (ICANN) Email: jennifer.bryce@icann.org Skype: jennifer.bryce.icann www.icann.org