CCWG-Accountability Work Stream 2: Difference between revisions
m added Category:Non-Policy Recommendations using HotCat |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
===Implementation=== | ===Implementation=== | ||
====ICANN Org==== | |||
Implementing WS2 was included as a priority for fiscal years 2022 and 2023. By the end of Q1 of 2022, ICANN Org had completed 13 recommendations for ICANN org were complete, leaving 39 recommendations still in progress. By the end of Q4, it had completed 20, including a communications plan to raise awareness of ICANN Organization Employee Practices and Resources.<ref>[https://www.icann.org/employee-practices-resources-en Employee Practices and Resources, ICANN Org]</ref> The org expects to complete implementing the guidance on ICANN Board deliberation transparency (Recommendation 8.3), enhancing staff accountability mechanisms, publishing service level targets (Recommendations 7.1-7.3), and developing a web page on ICANN's human rights efforts (Recommendation 3.1).<ref>[https://www.icann.org/en/blogs/details/update-on-icann-work-stream-2-implementation-02-05-2022-en Update on ICANN Work Stream 2 Implementation, End of 2022 Q1, ICANN Blogs]</ref> By the end of Q1 2023, the org had completed 66% of its recommendations, reaching between 90 and 100 percent of its improvements in or development of a Human Rights Framework of Interpretation, Staff accountability, [[DIDP]], interactions with governments, and an anonymous hotline. It has the most work left to do in the areas of the [[Ombudsman]] and [[SO]]/[[AC]] accountability.<ref>[https://www.icann.org/en/system/files/files/ws2-implementation-quarterly-report-31mar23-en.pdf WS2 Implementation, Q1 2023, ICANN Files]</ref> | Implementing WS2 was included as a priority for fiscal years 2022 and 2023. By the end of Q1 of 2022, ICANN Org had completed 13 recommendations for ICANN org were complete, leaving 39 recommendations still in progress. By the end of Q4, it had completed 20, including a communications plan to raise awareness of ICANN Organization Employee Practices and Resources.<ref>[https://www.icann.org/employee-practices-resources-en Employee Practices and Resources, ICANN Org]</ref> The org expects to complete implementing the guidance on ICANN Board deliberation transparency (Recommendation 8.3), enhancing staff accountability mechanisms, publishing service level targets (Recommendations 7.1-7.3), and developing a web page on ICANN's human rights efforts (Recommendation 3.1).<ref>[https://www.icann.org/en/blogs/details/update-on-icann-work-stream-2-implementation-02-05-2022-en Update on ICANN Work Stream 2 Implementation, End of 2022 Q1, ICANN Blogs]</ref> By the end of Q1 2023, the org had completed 66% of its recommendations, reaching between 90 and 100 percent of its improvements in or development of a Human Rights Framework of Interpretation, Staff accountability, [[DIDP]], interactions with governments, and an anonymous hotline. It has the most work left to do in the areas of the [[Ombudsman]] and [[SO]]/[[AC]] accountability.<ref>[https://www.icann.org/en/system/files/files/ws2-implementation-quarterly-report-31mar23-en.pdf WS2 Implementation, Q1 2023, ICANN Files]</ref> | ||
====ICANN Community==== | |||
The WS2 Community Coordination Group (CCG) was formed in February 2022 to serve as a forum for coordinating, prioritizing, updating, and reporting on each individual group's implementation progress. The community is working on 92% of its recommendations (and hasn't started the other 8%). Some community groups have completed some of the recommendations but a given recommendation is not marked "Complete" until all 21 individual ICANN Community groups have signed off on it in their respective structures. | |||
==Areas for Improvement== | ==Areas for Improvement== | ||
| Line 13: | Line 16: | ||
* ICANN and SO/ACs should define, measure, promote, and support diversity.<ref>[https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-24jun18-en.pdf CCWG-ACCT Final Report pgs. 18-19]</ref> Toward this end, [[ICANN Organization]] began its search for a diversity SME in December 2021 to be hired by April 2022.<ref>[https://www.icann.org/en/blogs/details/update-sharing-recent-icann-work-stream-2-implementation-progress-22-12-2021-en Update on WS2 Implementation December 2021, ICANN Blogs]</ref> | * ICANN and SO/ACs should define, measure, promote, and support diversity.<ref>[https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-24jun18-en.pdf CCWG-ACCT Final Report pgs. 18-19]</ref> Toward this end, [[ICANN Organization]] began its search for a diversity SME in December 2021 to be hired by April 2022.<ref>[https://www.icann.org/en/blogs/details/update-sharing-recent-icann-work-stream-2-implementation-progress-22-12-2021-en Update on WS2 Implementation December 2021, ICANN Blogs]</ref> | ||
===Guidelines for Good Faith=== | ===Guidelines for Good Faith=== | ||
* The Guidelines for Standards of Conduct Presumed to be in Good Faith Associated with Exercising Removal of Individual ICANN Board Directors outline the procedures for petitioning and carrying out a review and vote to remove a board member.<ref>[https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-24jun18-en.pdf CCWG-ACCT Final Report pgs. 20-21]</ref> | * The Guidelines for Standards of Conduct Presumed to be in Good Faith Associated with Exercising Removal of Individual ICANN Board Directors outline the procedures for petitioning and carrying out a review and vote to remove a board member.<ref>[https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-24jun18-en.pdf CCWG-ACCT Final Report pgs. 20-21]</ref> They support the [[ICANN Empowered Community]]’s power to remove an individual and take a minimalist approach so that SOs/ACs are free to follow their own processes. However, implementing Recommendation 2.3, which requires community coordination and prioritization given its cross-community nature, will take substantial effort and not begin until each community group has completed its work on Recommendations 2.1 and 2.2.<ref>[https://www.icann.org/en/system/files/files/ws2-implementation-quarterly-report-31mar23-en.pdf WS2 Implementation, Q1 2023, ICANN Files]</ref> | ||
===Human Rights Framework of Interpretation=== | ===Human Rights Framework of Interpretation=== | ||
* The team recommended a Framework of Interpretation for the ICANN Bylaw on Human Rights.<ref>[https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-24jun18-en.pdf CCWG-ACCT Final Report pgs. 82-88]</ref> | * The team recommended a Framework of Interpretation for the ICANN Bylaw on Human Rights.<ref>[https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-24jun18-en.pdf CCWG-ACCT Final Report pgs. 82-88]</ref> With the implementation of [[CCWG-Accountability Work Stream 1]], in 2016, a human rights core value was added to the [[ICANN Bylaws]]. The implementation of WS2 includes the consideration of the Human Rights Framework, consistent with international human rights law and norms, ensure that ICANN upholds and respects human rights. It is expected to be implemented by the seven SOs and ACs. Some have already delegated this work to committees or working groups. GNSO Council adopted a report on this recommendation in December 2022,<ref>[https://gnso.icann.org/sites/default/files/policy/2022/draft/draft-ccoici-ws2-recommendations-report-final-02nov22.en_.pdf CCOICI WS2 Final Report, GNSO]</ref> and the GAC Working Group on Human Rights and International Law is discussing it. | ||
===Jurisdiction=== | ===Jurisdiction=== | ||
* ICANN should be required to apply for and secure an OFAC license if the other party is otherwise qualified to be a registrar (and is not individually subject to sanctions). During the licensing process, ICANN should be helpful and transparent in the licensing process and communication with the potential registrar. | * ICANN should be required to apply for and secure an OFAC license if the other party is otherwise qualified to be a registrar (and is not individually subject to sanctions). During the licensing process, ICANN should be helpful and transparent in the licensing process and communication with the potential registrar. | ||
| Line 48: | Line 53: | ||
# improve its Documentary Information Disclosure Policy (DIDP), | # improve its Documentary Information Disclosure Policy (DIDP), | ||
# document and report on its interactions with governments, | # document and report on its interactions with governments, | ||
#* ICANN Org began publishing Analytical Reports on 28 Feb 2020<ref>[https://www.icann.org/en/government-engagement/publications GE Publications, ICANN]</ref> and now includes Government Engagement Strategies in the annual ICANN Operating and Financial Plans. | |||
# improve the transparency of Board deliberations, and | # improve the transparency of Board deliberations, and | ||
# improve ICANN’s Anonymous Hotline (Whistleblower Protection).<ref>[https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-24jun18-en.pdf CCWG-ACCT Final Report pgs. 348-351]</ref> | # improve ICANN’s Anonymous Hotline (Whistleblower Protection). | ||
#* ICANN org selected a third-party vendor to review its Hotline Policy and Procedures based on best practices and identify areas for improvement. The review began in Q4 2022 and ended in Q1 2023.<ref>[https://www.icann.org/en/system/files/files/ccwg-acct-ws2-final-24jun18-en.pdf CCWG-ACCT Final Report pgs. 348-351]</ref> | |||
==References== | ==References== | ||
[[Category:Non-Policy Recommendations]] | |||