Echoing my blog released on 5 November 2021, I would like to provide an update on recent progress the ICANN organization (org) has made in addressing Work Stream 2 (WS2) implementation.
WS2 of the Cross-Community Working Group on Enhancing ICANN Accountability (CCWG-ACCT) is a fiscal year 2022 (FY22) priority. It represents over 100 accountability and transparency-related recommendations, directed at the org, ICANN Board, and the ICANN community, which serve to ensure ICANN remains accountable to the multistakeholder community.
I am pleased to report that functions across the org are working steadily towards implementation milestones. Highlights since the org published the recent summary of implementation progress (dated 28 October 2021) include:
- ICANN's Anonymous Hotline Policy, also known as whistleblower policy, was published, increasing the total amount of complete recommendations to 10.
- Between October and December 2021, ICANN org held a Public Comment proceeding on proposed updates to ICANN's Documentary Information Disclosure Policy (DIDP). This is to address recommendations 8.1.1 through 8.1.15 and 8.1.17 through 8.1.21.
- Implementation of six additional recommendations (1.1, 1.6, 1.8, 3.1. 7.2.1, 7.3) recently began bringing us to a total of 34 recommendations for which implementation is underway. This notably includes recommendation 1.1 related to reaching agreement on key elements of diversity. The org has launched the process to hire the diversity expert who will assist ICANN org in supporting the community consultation on this effort and anticipates having the expert start tentatively in April 2022. Completion of recommendation 1.1 is a dependency to unlock the launch, or execution in some instances, of recommendations 1.2, 1.3, 1,4, 1.5, 1.6. This, as a result, is an important undertaking that has begun.
- ICANN org is preparing to begin implementation of seven recommendations and is actively looking for ways to address and, where possible and appropriate, remove dependencies.
- The ICANN community continues to discuss the formation of a WS2 Community Coordination Group which will function as a forum for utilizing best practices and leveraging lessons learned and other relevant information as each group progresses through WS2 implementation. The WS2 Community Coordination Group is also intended to be the mechanism for identifying and addressing specific WS2 recommendations for which implementation may require or benefit from a uniform community-wide approach. ICANN org has indicated that it will provide appropriate staff support to the WS2 Community Coordination Group when it is officially convened.
I look forward to sharing additional WS2 implementation updates with you as our work evolves and additional milestones are met.