Cross Community Working Group (CCWG) Accountability Update 8 October 2015.

Slides:



Advertisements
Similar presentations
STAFF Implement Proposed action STAFF – Assess (initial AND revisions based on feedback) Implementation change? Policy guidance needed? Admin/error update?
Advertisements

Governance & Nominating Committee (GNC) Report WECC Board Meeting – December 6-7, 2007.
1 Establishing Performance Indicators in Support of The Illinois Commitment Presented to the Illinois Board of Higher Education December 11, 2001.
Text CCWG on Enhancing ICANN Accountability Charter.
Agenda CWG-Stewardship Meeting - 27 March, 2015 in Istanbul 09:00 – 09:15 Introduction / overview of agenda 09:15 – 09:45 Further questions on legal 09:45.
MSP course 2007 Phase 0 – Setting up Kumasi, Ghana 2008 Wageningen International.
Draft compilation of major trends in the CWG Public Consultation 25 May 2015.
Transition of U.S. Commerce Department’s National Telecommunications and Information Administration (NTIA) Stewardship of the IANA Functions to the Global.
Emerging Latino Communities Initiative Webinar Series 2011 June 22, 2011 Presenter: Janet Hernandez, Capacity-Building Coordinator.
Transition of U.S. Commerce Department’s National Telecommunications and Information Administration (NTIA) Stewardship of the IANA Functions to the Global.
Cross Community Working Group (CCWG) Accountability 2nd Draft Proposal for Public Comment Visual Summary Cross Community Working Group (CCWG) Accountability.
Atlanta Public Schools Project Management Framework Proposed to the Atlanta Board of Education to Complete AdvancED/SACS “Required Actions” January 24,
European Commission, DG Competition Fifth Annual Conference on Competition Enforcement in the CCE Member States 21 February 2014, Bratislava 1 Due Process.
Enhancing ICANN Accountability. | 2 CCWG-Accountability Scope  During discussions around the IANA functions stewardship transition the community raised.
Division I Governance Review Jackie Campbell and Kris Richardson 2014 Regional Rules Seminar.
NRO update LACNIC23, May 2015 Lima Peru To be the flagship and global leader for collaborative Internet number resource management as a central element.
ALAC Comment (Submitted) on CCWG-Accountability 2nd Draft Proposal on Work Stream 1 Recommendations Alan Greenberg 28 September 2015.
IANA Stewardship Transition Cross Community Working Group (CWG) on Naming Related Functions.
 Cross Community Working Group to Develop an IANA Stewardship Transition Proposal on Naming Related Functions (CWG) DRAFT TRANSITION PROPOSAL.
Taking stock and next steps CCWG F2F, 23 March 2015.
IANA Functions Stewardship Transition Patrik Fältström.
1 Standard Setting for Nonpublic Entities Activities of the FAF/FASB  2006-FASB created Private Company Financial Reporting Committee (PCFRC)  2008-FAF.
Text #ICANN51 13 October 2014 Cross Community Working Groups.
Central Kitsap School District SHARED DECISION MAKING Central Kitsap High School March 2, 2006.
The ASO is a supporting organization of ICANN Number Resource Policy Development Process Alan Barrett ICANN ASO Address Council ICANN 46 Beijing April.
IANA Stewardship and ICANN Accountability ALAC Positions Capacity Building Webinar – 28 September 2015.
SCORECARD Cross Community Working Group (CCWG) Accountability 15 October 2015.
IANA Stewardship Transition & Enhancing ICANN Accountability Presenter | Event | Date.
Text #ICANN51. Text #ICANN51 GNSO Briefing on Key Strategic Initiatives 12 October 2014.
Requirements 1 NTIA Support and enhance the multistakeholder model Maintain the security, stability and resiliency of the Internet DNS Meet the needs.
ST18 subgroup report 23 november ST 18 subgroup The ST18 subgroup, convened by the co-chairs, to: – Assess existing options, areas of agreement.
East Hudson Regional Trail Council August 10, 2015.
NRO update RIPE 71, November 2015 Bucharest, Romania To be the flagship and global leader for collaborative Internet number resource management.
NRO update ARIN 36, 8-9 October 2015 Montreal, Canada To be the flagship and global leader for collaborative Internet number resource management as a central.
Review of CCWG-Acct 3 rd Proposal and ALAC Issues Alan Greenberg 04 December 2015.
IANA Stewardship Transition: High-Level Project Plans 3 December 2015 DRAFT for Discussion.
Requirements 1 NTIA Support and enhance the multistakeholder model Maintain the security, stability and resiliency of the Internet DNS Meet the needs.
CCWG on enhancing ICANN’s Accountability Los Angeles, July 2015.
Draft compilation of major trends in the CWG Public Consultation 21 May 2015.
CCWG on Enhancing ICANN’s Accountability Paris, July 2015.
Taking stock and next steps CCWG F2F, 23 March 2015.
Draft Trends in CCWG-Accountability 2 nd Draft Proposal public comment input 15 September 2015.
Transition Implementation Status Reporting 21 January 2016.
CCWG-Accountability Update APRICOT 2016 Auckland, February 2016 Jordan Carter 1.
On My Way To L.A. Actually „our“ way!. Four suggested areas of preparation 1. Let’s have a comparison chart 2. Double-check requirements list 3. Identify.
IANA Stewardship Transition Process 09 March 2016.
IANA Stewardship Transition & Enhancing ICANN Accountability Panel and Audience discussion | WSIS Forum | 5 May 2016.
CHB Conference 2007 Planning for and Promoting Healthy Communities Roles and Responsibilities of Community Health Boards Presented by Carla Anglehart Director,
Review of CCWG-Acct 3 rd Proposal and ALAC Issues Alan Greenberg 11 December 2015.
Transition Implementation Status Reporting 04 February 2016.
How to resolve the pending issues? Three categories of input: ★ Issues for discussion ★ “uncontested” comments ★ Questions from our group 1.
Empowered Community Overview of Procedures | XX March 2017.
Charter for the CCWG on the Use of New gTLD Auction Proceeds
Transition Implementation Status Reporting
Introduction to PTI Elise Gerich | ICANN 57 | November 2016.
Cross Community Working Group
Transition Implementation Status Reporting
Transition Implementation Status Reporting
ccNSO Guidelines – Rejection Actions and Approval Actions
CWG-Stewardship Update
The Empowered Community: What it means…
Action Request (Advice) Registry
ccNSO CWG-Stewardship Update
IANA transition Milton Mueller
Updates and Next Steps on Enhancing ICANN Accountability
Legal cost control mechanisms
CCWG Accountability Recommendations
CCWG-Accountability ICANN56 26 June 2016
CCWG WS 2 SO/AC Accountability UPDATE
Presentation transcript:

Cross Community Working Group (CCWG) Accountability Update 8 October 2015

The Two-Track Parallel Process 2 Since the National Telecommunications and Information Administration (NTIA) announced their intent to transition stewardship of the IANA functions, the ICANN community has been working in a two-track parallel process. The ICG has finalized its Interim Draft IANA Stewardship Transition Proposal, and the CCWG- Accountability has finalized its 2nd Draft Proposal for Work Stream 1. NTIA Announcement & Criteria ICANN CCWG -Accountability Enhancing ICANN Accountability ICG IANA Stewardship Transition CCWG Proposal ICANN BOARD NTIA ICG Proposal CWG Stewardship Linkage CRISP IANAPLA N

Overview Goal The CCWG-Accountability is expected to deliver proposals that would enhance ICANN’s accountability towards all its stakeholders. Scope Work Stream 1 - Focuses on mechanisms enhancing ICANN’s accountability that must be in place or committed to within the time frame of the IANA Stewardship Transition. Work Stream 2 - Focuses on addressing accountability topics for which a timeline for developing solutions and full implementation may extend beyond the IANA Stewardship Transition. 3 The ICANN Community & Board of Directors The ICANN Community is organized in three Supporting Organizations (SOs) and four Advisory Committees (ACs), each represents key stakeholders. While the ICANN Board has the ultimate authority to approve or reject policy recommendations, Supporting Organizations are responsible for developing and making policy recommendations to the Board. Advisory Committees formally advise the ICANN Board on particular issues or policy areas. Most of the CCWG-Accountability’s efforts are focused on ensuring accountability of the Board of Directors (and ICANN staff) toward these stakeholders, but the question of accountability of the community was also worked on.

Proposed Enhanced Accountability Mechanisms Cross Community Working Group (CCWG) Accountability 2nd Draft Proposal for Public Comment4 The CCWG-Accountability has identified enhancements required to those building blocks that would form the accountability mechanisms required to improve ICANN’s accountability. ACSOACSOACSOAC The Principles guarantee the core mission, commitments and values of ICANN through its Bylaws (i.e. the Constitution). Independent Appeals Mechanisms confers the power to review and provide redress, as needed (i.e. the Judiciary). The Empowered Community refers to the powers that allow the community SOs & ACs to take action should ICANN breach the principles (i.e. the People). ICANN Board has the ultimate authority to approve or reject policy recommendations, developed by the SOs. ACs formally advise the ICANN Board on particular issues or policy areas (i.e. the Executive) BUDGET STRATEGY/OPS PLAN BYLAWS REVIEW / REJECT REMOVE / RECALL NEW IRP 7+ MEMBER STANDING PANEL STRUCTURAL REVIEW As Community accountability Fundamental Bylaws Existing + New mechanisms + AoC Reviews BYLAWS NEW

Community Mechanism as Sole Member Model 5 Many corporate structures and legal mechanisms have been thoroughly explored for organizing the community and enabling it to have enforceable powers, which generally requires “legal personhood” in any jurisdiction. The CCWG-Accountability is recommending the Community Mechanism as Sole Member Model. BOARD THE COMMUNITY Community disagrees? No recourse… Board Decision or Action ACSOACSOACSOAC Make Policies (SOs) Advise (ACs) Representation on the Board BOARD THE EMPOWERED COMMUNITY Community disagrees? Board Decision or Action ACSOACSOACSOAC Make Policies (SOs) Advise (ACs) Representation on the Board Community Mechanism As Sole Member Powers Recourse! The Community Mechanism in which SOs/ACs participate jointly to exercise their community powers would be built into ICANN’s Bylaws and be the Sole Member of ICANN. Decisions of the SOs/ACs per the Community Mechanism would directly determine exercise of the rights of the Community Mechanism as Sole Member (CMSM). Current Proposed If the community disagrees with a Board decision or action, they have no recourse to challenge it. If the community disagrees with a Board decision or action, they can challenge it exercising their powers through the CMSM. 5

The Empowered Community’s Powers 6 The CCWG-Accountability recommends the ICANN community be empowered with five distinct powers. 1. Reconsider/reject Budget or Strategy/Operating Plan This power would give the community the ability to consider strategic/operating plans and budgets after they are approved by the Board (but before they come into effect) and reject them. 2. Reconsider/reject changes to ICANN “Standard” Bylaws This power would give the community the ability to reject proposed Bylaws changes after they are approved by the Board but before they come into effect. 3. Approve changes to “Fundamental” Bylaws This power would form part of the process set out for agreeing any changes of the “Fundamental” Bylaws. It requires that the community would have to give positive assent to any change, a co-decision process between the Board and the community and that such changes would require a higher vote. 4. Remove individual ICANN Board Directors The community organization that appointed a given director could end their term and trigger a replacement process. The general approach, consistent with the law, is that the appointing body is the removing body. 5. Recall entire ICANN Board This power would allow the community to cause the removal of the entire ICANN Board. (expected to be used only in exceptional circumstances). 6

CMSM Model: Exercising Powers 7 How does the community exercise its powers? The exercising of different community powers may include unique steps relevant to a given power, but the general process is as follows. 123 PETITIONDISCUSSIONDECISION OUTCOMECAUSE ICANN Board or Board Member action causing significant concern to members of the community. ICANN Board acts in accordance with the community’s decision. A petition by at least one SO or AC (depending on the power) starts the formal discussion and decision-making about whether to exercise a community power. The whole community – all SOs and ACs – discusses the proposed use of the power, online and/or through a proposed ICANN community forum. SOs and ACs that have voting rights in the Community Mechanism cast their votes to decide whether the power is used or not. Notable exceptions to this three-step process are for the powers to remove an ICANN director appointed by an SO/AC (where there is an initiating trigger vote in the SO/AC to start consideration of the process) or to co-approve changes to Fundamental Bylaws (where its use is automatically triggered by any proposal for changes to Fundamental Bylaws). To Recall the Entire ICANN Board requires two SOs or ACs (at least one of which is an SO) to sign a petition. Generally a maximum period of fifteen days from the announcement of the decision that might trigger the power’s use. This Discussion Period lasts for fifteen days, starting the day after a valid petition has been received. This Decision Period lasts for fifteen days, starting the day after the conclusion of the discussion period.

Current key issues Level of enforceability Especially for budget and separation powers This drives the « model » discussion Decision making for the community Concerns regarding weights and opt-in / opt-out Consensus decision making investigated SO and AC accountability to the global Internet community New requirement - core reason for Board concerns Very few concrete suggestions so far Could there be a 2 steps approach ? 1st phase with powers and low level of enforceability Governance review with « iron clad » guarantees

Timeline : Solid orange bordering on red

Keys for a successful Dublin meeting Expected outcome  Find new common ground for consensus  Assess initial support within SO/Acs  Decide whether extra public comment is needed  Clarify role of the Icann Board in the process How can you help ?  Have clear view of your core requirements and expectations  Active listening and open mind  Dedicate any available time to the heavy lifting tasks of reviewing public comments or drafting