For our upcoming call, agenda items 2-3 are to review suggestions from our first reading at the 10-Mar CCWG plenary meeting in Copenhagen, and consider whether to revise our report prior to second reading on 29-Mar. So I’ve attached a PDF of notes from Copenhagen reading, and pasted it below. — Update: here in Copenhagen I met with 18 leaders of GNSO constituencies and stakeholder groups and asked what they though about the mutual accountability roundtable suggestions floated at the plenary (repeated here from my Friday notes below): Prior to each Annual General Meeting (AGM), ICANN staff should ask the chairs of all AC/SOs whether they want to hold a Mutual Accountability Roundtable to discuss SO/AC accountability with respect to activities within ICANN’s scope. If a majority of AC/SO chairs agree to hold the Mutual Accountability Roundtable: ICANN staff would schedule a 90-minute open session at the next AGM, open to all AC/SO/Group chairs, and joined by ICANN CEO and Board Chair. The ICANN board chair would designate a moderator for the session. GNSO leaders were not in favor of this idea. They feel it is not a good use of their time, or the time of meeting attendees. Some points: It would be like when AC/SO chairs give “reports” at ICANN meetings. If each AC/SO takes 5 minutes, that’s 35 minutes. It’s over an hour when all GNSO groups are allowed to participate. That is not a good use of time. Discussion would just be a "kumbaya" session, instead of tough questions to other AC/Sos Michele Neylon suggested AC/SO/groups do annual reports on accountability, and anyone can read them online and ask questions via email. I immediately told him about Farsi’s best practice suggestion for “Annual Reports”. From: Steve DelBianco <sdelbianco@netchoice.org<mailto:sdelbianco@netchoice.org>> Date: Friday, March 10, 2017 at 5:08 PM Subject: Summary of SOAC-Accountability discussion at CCWG Plenary We had a 1-hour discussion with the CCWG plenary today in Copenhagen. Here’s our summary of feedback received during first reading of our draft report: Track 1: Best Practices First reading revealed no objections to our recommendations, but some possible changes: Our draft Exec Summary says we “recommend best practices that should be considered …”. Speakers offered alternatives such as “we urge adoption of these best practices..” or “we encourage implementation of …” -- ASO reminded us to clarify we are only talking about AC/SO accountability "within the scope of ICANN activities”, since NRO and IETF exist outside of ICANN, too. -- Outreach and Participation: consider adding diversity dimension to best practices. Perhaps we suggest incorporating recommendations anticipated from the Diversity group of WS2. -- Transparency Recc #4: add appropriate reasons for an AC/SO meeting to be “closed” to members: (list provided by Michael Karanicolas) * discussion of trade secrets or sensitive commercial information whose disclosure would cause harm to a person or organization's legitimate commercial or financial interests or competitive position. * discussion of internal strategic planning whose disclosure would likely compromise the efficacy of the the chosen course. * discussion of information whose disclosure would constitute an invasion of personal privacy, such as medical records. * discussion of information whose disclosure has the potential to harm the security and stability of the Internet. * discussion of information that, if disclosed, would be likely to endanger the life, health, or safety of any individual or materially prejudice the administration of justice. — Finn Peterson noted that Transparency Recc 5 and Participation Recc 4 both address minutes of member meetings, and should be more consistent. Transparency Recc 5: Minutes for all membership meetings should be published. Participation Recc 4: For any meetings, be they closed to members only or open to anyone, the members have to be able to access minutes and/or recordings, subject to exceptions for confidential matters. — Jan Sholte and several others noted that we could recommend something stronger than just to "consider” these best practices. We answered that our group was not likely to recommend these best practices be placed into ICANN bylaws. Moreover, our 2017 list of best practices would become outdated before long. No decision on what to do here. — Some commenters want to see a continued focus on SOAC Accountability after the CCWG concludes. Indeed, on page 2 of our draft report we noted Recommendation 10 of the CCWG Final Proposal (link<https://community.icann.org/pages/viewpage.action?pageId=58723827&preview=/5...>): In Work Stream 2: Include the subject of SO and AC accountability as part of the work on the Accountability and Transparency Review process We could amend our report to recommend that future ATRTs examine SO/AC accountability, transparency, participation, and outreach. This could be a new item in the Bylaws<https://www.icann.org/resources/pages/governance/bylaws-en>, at Sec 4.6 b, where potential ATRT issues are listed. Or, we could recommend that ICANN staff add this item to the procedures for ATRT, which would not require a bylaws change. Note that we would not refer future ATRTs back to our 2017 list of best practices. Instead, we’d expect that future ATRTs would undertake a review and develop recommendations similar to what our group did in 2016-17. Track 2: Mutual Accountability Roundtable (page 31) First reading revealed significant objection to our recommendation on MARs. Several speakers prefer a formal discussion of SOAC accountability, at least once each year. We could amend our report to recommend something like this: Prior to each Annual General Meeting (AGM), ICANN staff should ask the chairs of all AC/SOs whether they want to hold a Mutual Accountability Roundtable to discuss SO/AC accountability with respect to activities within ICANN’s scope. If a majority of AC/SO chairs agree to hold the Mutual Accountability Roundtable: ICANN staff would schedule a 90-minute open session at the next AGM, open to all AC/SO/Group chairs, and joined by ICANN CEO and Board Chair. The ICANN board chair would designate a moderator for the session. Track 3: IRP (page 32) First reading revealed no objections or changes to Track 3 recommendations. Avri agrees we should mention the Ombudsman as an alternative, but says we should not recommend that the new ICANN Complaints Officer is an alternative to IRP. Regards, Steve DelBianco, Cheryl Langdon-Orr, and Farzaneh Badii Co-Rapporteurs, SOAC Accountability Group, CCWG WS2 From: Cheryl Langdon-Orr <langdonorr@gmail.com<mailto:langdonorr@gmail.com>> Date: Wednesday, March 22, 2017 at 6:55 AM To: "ws2-so_ac@icann.org<mailto:ws2-so_ac@icann.org>" <ws2-so_ac@icann.org<mailto:ws2-so_ac@icann.org>>, Thomas Rickert <thomas@rickert.net<mailto:thomas@rickert.net>>, Steve DelBianco <sdelbianco@netchoice.org<mailto:sdelbianco@netchoice.org>>, farzaneh badii <farzaneh.badii@gmail.com<mailto:farzaneh.badii@gmail.com>>, Brenda Brewer <mssi-secretariat@icann.org<mailto:mssi-secretariat@icann.org>> Subject: Agenda for SOAC Accountability Subgroup Meeting #25 on Thursday, 23rd February @ 05:00 UTC. Please join the Work Stream 2 - SOAC Accountability Subgroup Meeting #25 on Thursday, 23rd February @ 05:00 UTC. CALL DETAILS: Link to Adobe Connect: https://participate.icann.org/mssi-projects Mobile: tel://1-719-867-0497,*,,5263384535# Agenda: 0. Call Administration (2 min CLO) 1. Review of AI's from call #23 on March 2nd (2 min) CLO) https://community.icann.org/x/3qDRAw 2. Update from Plenary Meeting March 10th (#24). (5 min CLO ) 3. Discussion, current (draft 1.32) documentation updates, readings and review. (45 min CLO/SDB) * Review and discuss updates to our draft documentation - the Consolidated Draft Report after its 1st reading and Plenary discussion, see emails to our list and CCWG pre and post our recent meeting CPH. 4. Next Meeting and future Meeting schedule (2 min CLO) · none currently listed for April onwards. To be discussed. Master Schedule is here https://docs.google.com/spreadsheets/d/1qwr41BesyvDQBnqF_gBQlHfJlRkOGrjHa26i... 5. AOB and review of any AI's. (3 min CLO)