Hello all, The notes, recordings and transcripts for the WP2 Meeting #4 - 30 March will be available <https://community.icann.org/pages/viewpage.action?pageId=52894975> here. Action Items ACTION: Malcolm to revise text, based on gathering like issues together. With clarity on what is/is not being changed Notes: WP-2 Compactmission Discussion on IRP and Mission/Core Values issues post Istanbul Meeting - 30 March This call will be recorded Chat sessions are being archived and follow the ICANN Expected Standards of Behavior: http://www.icann.org/en/news/in-focus/accountability/expected-standards These high-level notes were prepared to help you navigate through content of the call and do not substitute in any way the transcript. NOTES: Roll call: all present in the AC room Mission and Core Values from Istanbul. Updated text and accepted suggestions regarding formatting and proposed changed Proposed language: new, is in red text. With notes and comment in the right column. As the process moves on, suggested that this column can be used to consider questions for the Public Comment/ Need to add the roles of names, numbers, protocols and port parameters and evolution of the DNS root/ To provide more specificity, added new language around names RIR/IETF may have specific language they wish to use to describe their role. Language new from Istanbul on limiting ICANN mission. The right column includes relevant language from the AoC and from the new gTLD agreement (Spec 1) Group should consider how Spec 1 becomes durable. Coordination of administration. Coordination of operation. Coordination of policy development and implementation If someone were to make a challenge that some activity were outside the text, could the challenge be easily upheld? Theoretical stress tests: Some of what ICANN does in administering community consensus might be considered as regulating content (e.g. the new gTLD app guidebook). Need to take care that new "rules" do not prevent desirable actions. Theoretical stress tests: Time zone database. Does it fit under protocol parameters? But it does not fit under the current contract. Endorsement of least the change principle. Future rationalization may be needed. IETF discussion about use of TLDs for other uses. ICANN not exclusive, and this needs to be reflected. There is language that may address these concerns. AoC for WHOIS - language in AoC broken from the beginning and would not wish to see it extended, but revised. Revision should take place outside of the transition process. Reconciliation - fundamental commitments and core values, or between core values. It has to meet a high bar of public interest goals, and be narrowly tailored and necessary. CCWG conference call - for consultation and to raise questions. Fundamental Rights. Bylaws provisions that talk if 11 core values. The mission describes what ICANN does. The fundamental rights talk about how ICANN accomplishes its mission. Core values 8 and section 3 of the bylaws mention non-discriminatory treatment. Changes made reflect Istanbul discussion, the sources of language being proposed will be noted. References in the right column where these are picked up in the AoC. Also discussion about ICANN's competition mission: two ways to look at this, as affirmatively of promoting competition, or acting in ways that does not impede competition. Para 6. While remaining rooted in the private sector... taking into account govt advice, etc A discussion about how the group feels about this issue. How to continue to treat GAC advice, when it may conflict with core values. Consideration needed of reconciling GAC advice which is inconsistent with ICANN's own bylaws. In the explanatory language, note that the policies are under review END