On 9 March 2018, the Cross Community Working Group on Enhancing ICANN Accountability (CCWG-Accountability) held a face-to-face meeting in San Juan, Puerto Rico, to further its discussions on Work Stream 2. Sixty-two members and participants attended in-person & remotely using the virtual meeting room.
As a part of Work Stream 1, the CCWG-Accountability defined areas where further accountability discussions needed to take place. These discussions, called Work Stream 2, have been underway since June 2016. The purpose of Work Stream 2 is to disseminate the new accountability principles into several key parts of ICANN’s day-to-day operations & to develop a culture of accountability across the ICANN Community, Organization, & Board.
During the meeting the CCWG-Accountability:
- Approved the second reading of the final recommendations on Diversity.
- Approved the second reading of the final recommendations on Jurisdiction.
- Approved the second reading of the final recommendations on the Office of the Ombudsman.
- Approved the second reading of the final recommendations on Staff Accountability.
- Approved recommending the establishment of a small implementation oversight team (IOT) consisting of the Co-Chairs & the rapporteurs for the eight sub-groups, to assist ICANN & the community to ensure the implementation plan preserves the spirit of the recommendations & provide any interpretation advice as required.
- Committed to having the draft final WS2 report published for public consultation by the end of March 2018.
- Confirmed its schedule of plenary meetings to ICANN 62.
With these approvals all sub-groups have submitted final recommendations for their topics as per the schedule agreed to in May 2017.
It is important to note that the IRP IOT was included as part of WS2 for administrative simplicity but is in fact independent of WS21. Current expectations are that the IRP IOT will continue beyond the scheduled completion date for WS2 of June 2018.
The CCWG-Accountability Co-Chairs recognize the outstanding dedication of its volunteers, & express gratitude to ICANN staff for their diligent & skilled support. For more information on the CCWG-Accountability, or to view meeting archives and draft documents, please refer to their dedicated wiki page.
About the CCWG-Accountability
The CCWG-Accountability was established in 2014 as a part of the IANA stewardship transition. The group’s goal is to ensure that ICANN’s accountability and transparency commitments to the worldwide Internet community are maintained & enhanced in the absence of the IANA functions contract with the U.S. Government.
The group divided its work into two Work Streams:
- Work Stream 1 was focused on identifying mechanisms to enhance ICANN’s accountability that must be in place or committed to within the timeframe of the IANA stewardship transition.
- Work Stream 2 is focused on addressing accountability topics for which a timeline for developing solutions & full implementation may extend beyond the IANA stewardship transition.
The CCWG-Accountability proposed 12 recommendations to enhance ICANN’s accountability as a part of the IANA stewardship transition. The consensus Work Stream 1 proposal was approved and transmitted by the ICANN Board to the U.S. National Telecommunications & Information Administration on 10 March 2016. On 1 October 2016, the IANA functions contract lapsed, and CCWG-Accountability’s Work Stream 1 recommendations went into effect.
The CCWG-Accountability is comprised of 227 people, organized as members appointed by & accountable to Chartering Organizations; individual participants; one ICANN Board liaison; one ICANN staff representative; & one former ATRT member who serves as a liaison. The group also has over 130 mailing list observers.
The CCWG-Accountability is an open group. Anyone interested in the work of the CCWG-Accountability can join as a participant or observer. For more information about how to join the CCWG-Accountability, please send an email to email@example.com.
Jordan Carter, Tijani Ben Jemaa, Thomas Rickert
1 WS2 was mandated by WS1 Recommendation 12, whereas the IRP IOT was mandated in WS1 Recommendation 7.