Hello all, The notes, recordings and transcripts for the CCWG ACCT WP1 Meeting#12 - 11 June will be available here: https://community.icann.org/pages/viewpage.action?pageId=53777766 A copy of the notes and action items may be found below. Thank you Best regards, Kim ACTION Items ACTION ITEMS - Ensure Legal link is available for comment 223 ACTION ITEMS - Call notes to be circulated to Counsel in addition to CCWG Notes NOTES & ACTION ITEMS: These high-level notes are designed to help you navigate through content of the call and do not substitute in any way the transcript. Working methods - analyses PC - summary and impression test, analysis of content, action steps and what might be published Recap on wp2 approach. Looking for themes that wasn't thought of. Once we had done granular analysis, we need to produce a summary, similar to what WP2 is creating. Example will be circulated. Do a thematic summary. Further work on summary. Overall summary box will be added to the gdoc - New edits will be made on shared Google doc. Jurisdiction is recurring theme - whether or not new issue. Proportionality must be discussed WP1 - using: agreement, concerns, confusion, divergence - for each comment - Avri briefed group approach wp2 is taking. Looking for trends, teams assigned to each trending topics...trends that were already known like 8b, jurisdiction, have teams looking at these already. Then will go comment to comment. Suggested to use the same approach as WP2 to make understanding more concise. Be concise in allocating, be specific - so not to be accused of being biased, also why more than one person is used to evaluate. Encouraged to look at document to add precision, accuracy and neutralize any comments that you feel are not fair - so we have the most accurate record -- Summaries will be addressed during next couple calls, but by working through some of the specifics give us a sense of how it's working and if we want to make any changes. Avri will discuss comments she has already started 373 - marked as "confusion" "divergence" disagrees with idn being incorporated in us, did come up in the aoc - comingles issues, like 8b (trending), jurisdiction and incorporation, wants inclusion of 8b in bylaws, Jurisdiction and incorporation - will be taking up in WS2, add to fundamental bylaws, actions - covering its trending. What is the "Theme" whether ICANN should not be US, or issue of location of idn in bylaws or fundamental bylaws? Is it a concern by mostly govts? Etc. 8b isn't even on the table, not addressed. Article 18 of bylaws states company shall have headquarters in California. Question is fundamental or non-fundamental. New idea, not WS1. Merit not addressed at this time. 374 375 are similar and have been given similar answer. 374 - Govts given appropriate representation in an ATRT. AoC does not get into the proportion of representation. Moving proportionality into Bylaws of these Review Teams. Our view is that all SOs and ACs should be represented in the AOC reviews as set out in para 305 of our Public Comment report. The CCWG will consider how to incorporate this matter more specifically in the next version of the proposal. Is there any other area of government concern? This will be determined after review and summaries will be posted. Perhaps this needs to be specified in the bylaws as it was in setting up ICANN implementation of the reviews All reviews will be conducted by a volunteer community review team comprised of representatives of the relevant Advisory Committees, Supporting Organizations, Stakeholder Groups, and the chair of the ICANN Board. The group must be as diverse as possible. Proportionality has not been completely addressed? Be specific on numbers? 375. Response - thank you 376 - WS2 to review as a longer term process. Doing so now seems less so, but folding them into the bylaws does seem important, especially if we want to dissolve the AOC. 377 - Agreement - response thank you 378 - Agreement - response thank you 379 - (Govt of Spain) more detail, a plan needs to be put into place, looking for detailed time scale on termination of aoc. Trend: govt saying headquarters is an issue) AoC states ICANN should be HQd in US, do not believe this should be incorporated into a fundamental bylaw of ICANN subj to Cal law is not fundamental to the global internet community, - question of how much detail to include in bylaw. Suggested that - Not really a trending issue. Spain is just answering our question about Article 18 as a Fundamental Bylaw. They prefer it not be. Just record the answer. Opposing view whether it's a fundamental or not. Need more attention than to just answer the question; cover carefully. WP1 went through assessments of comments and suggested actions and did live editing. Splitting larger comments will occur at a later time. Working method, and how to categorized - read details, so when summaries are complete, people with different takes, perspectives have all worked through and feel the summary is fair. 380 - Agrees with enshrining accountability. Concern of inconsistencies, Agrees with putting in ATRT, Flexibility of reviews. WHOIS work stream 1 or 2? Was RySG agreeing with ability to sunset including WHOIS? Accountability and Transparency Reviews must be incorporated. - We recommended that the ATRT team could recommend sunset of reviews like WHOIS. Keith to confirm whether it's the ability to call for sunset vs an explicit call for sun setting. 381 Unreasonable to incorporate all principles of AOC into Bylaws (US incorporation). Issue of implement ability is important. IRP either confirms or mitigates decision. Put some appropriate principles of AOC into ICANN Bylaws would enhance ICANN's accountability. Calls for re write. Consider vs forcing. Can use IRP. Strongly explain rationale without being dismissive. Coupled with powerful mechanisms to challenge. - 382 support for it to become fundamental bylaw, believes article 18 should be designated a fundamental bylaw, so it would require 75% community voting approval for change; hopes to rely upon statutory powers to recall the Board and other actions, as necessary, to ensure that the ICANN Board and staff remain accountable to the community. 383 - Agreement - thanks - although believes, the processes are slow, greedy on volunteers' time and cumbersome -384 supports inclusion fund bylaws, however the words "if appropriate" could be viewed as divergence. Para 269: The proposed text for insertion in the bylaws is "where feasible, and appropriate, depending on market mechanisms....." We feel that there is a large range of opinions on the role of the market. The AoC, however, is stronger in its support of the marketplace, so we would suggest deleting the words "and appropriate" - does not recommend deleting any words, look further at marketplace demands. Disagree with recommended edits. -385 - Support, response thank you - 386 Binding AoC into Bylaws. It's not appropriate to refer to AoC into Bylaws (Bilateral agreement) Instead of writing that ICANN will be committed to them. Instead of writing what is in the AoC in the Bylaws and producing duplicate description in two different documents, they suggest referencing relevant section of the aoc in the bylaws and bind reference sections by the bylaws. Proposing several enhancements to the AOC. Because OAC is a bilateral agreement, it is not appropriate for it to be referred to in the bylaws after the transition. Allows the affirmation to sunset. Something to be considered in next version of proposal. 387 - We understand the incorporation of a review system defined in AOC, and ability to start a new one. Response - yes 388 Explain our rationale rather change. This is incomplete, just first couple bullets completed. 8b trending issue, representation issue - ask to consider so/ac but to consider constituencies and by reference stakeholder groups. Representation issue at the bylaws level, up to each of the so /ac to house their internal apportionment. Clarification on 338 Batched round - guidebook is prepared, solicitation, non-batched round open, continuous round, but constant application. In the proposal on page 59, 338 The Board shall cause a review of ICANN's execution of this commitment after any batched round of new gTLDs have been in operation for one year. Used batched rounds on purpose. Requirement after at least every 5 years or after a batched round. --- 223 - Membership model is suitable, but that individual membership was suitable in a Swiss jurisdiction ideally. Mostly in agreement. Prefers individual membership (as in members of SO's and AC's) are the members of ICANN; Swiss jurisdiction; membership preferred to designator No action required. Pull out memo language to address this. Ensure link is included. Legal analysis on the Swiss framework indicates there are no significant advantages to such a model. ACTION ITEMS - Ensure Legal link is available for comment 223 ACTION ITEMS - Call notes to be circulated to Counsel in addition to CCWG --- 224 - Correlating the community with ICANN structure, ability to change preserved, the issue of how mechanism participants are held accountable to their appointing circles and how to avoid insider capture. (Insider capture - theme) -relevant name - More work on accountability for mechanism participants - Insider capture - comes up in a number of places, work as group. ST12 will be expanded to address insider capture and new stress test will be created to address rogue voting SO/AC representative. --- There needs to be a second phase of work to draw out comment themes and summarize at each top of section. Call for volunteers. Second phase, pattern recognition, draw out themes and summarize at top of section. AOC in bylaws have been given to ST. Community mechanism - Q7 and two related questions (13 pages): Jordan Carter, Matthew Shears, Robin Gross & Roelof Meijer Veto budget - Q8 (2.5 pages): Robin Gross Changes to bylaws - Q9 (~1 page): Keith Drazek Approve fundamental bylaws changes - Q10 (1 page): Keith Drazek Removing individual directors - Q11 (2 pages): Fiona Asonga Recalling the entire Board - Q12 (2 pages): Fiona Asonga Incorporating AOC in bylaws - Q13 and 14 (4 pages): Steve del Bianco & Avri Doria Work Approach: Go through summary materials to identify themes and determine how we will discuss these themes in BA Keep looking through document and add edits, proposed thoughts to make responses/summaries as fair-minded as possible. On the next calls, go through summary materials. Next call: Saturday, 13 June 2015 from 05:00- 07:00 (AM) UTC - custom is to have 12 hours to review material. Document freeze at 1700 UTC on the 12th. Jordan will circulate pdf, but edits can still be made on Gdocs. WP2 You can go into original comments - make it more possible - work issue by issue. Read comments in a structured fashion