The updated draft of the ICANN Community Participant Code of Conduct Concerning Statements of Interest (the Code) has received both praise and critiques from the community, demonstrating ongoing efforts to refine its implementation and clarity.

Praises and Strengths:

Clarity and Practical Examples: The updated Code is commended for offering clearer guidance, particularly through the expanded use of practical examples that address the diverse nature of the ICANN community. This includes better definitions of what constitutes an "interest" beyond just attorney/client or large business relationships.

Defining Participation Thresholds: The document makes important distinctions between "participation" and "passive observation", which helps establish a practical threshold for when a Statement of Interest (SOI) is required. For instance, monitoring public proceedings does not require disclosure, but active participation (like joining working groups or making public comments) does.

Addressing Confidentiality: The Code demonstrates an awareness of complexities such as legal obligations or proprietary business interests, showing thoughtful handling of confidentiality concerns. However, it stipulates that if disclosure cannot be made due to such reasons, the participant must refrain from participating in discussions on that specific issue.

Enforcement Framework: The inclusion of a detailed enforcement framework is seen as a positive development. The Code empowers community chairs to address violations directly, including documented warnings and temporary removals, which is viewed as striking an appropriate balance between accountability and flexibility. It reaffirms ICANN's commitment to supporting community enforcement efforts.

Shared Responsibility: The Code acknowledges the role organizations play in ensuring ethical participation, encouraging them to verify that their representatives submit accurate and complete disclosures. This shared responsibility model is seen as safeguarding against inadvertent or intentional non-disclosure.

Evolutionary Approach: The Code is designed to be an evolving document, allowing for continued updates and refinement to address emerging issues in disclosure or enforcement after adoption.

Critiques and Areas for Improvement:

Training and Resources for Enforcement: A recurring suggestion from the community is the need for formal training and resources for leaders responsible for enforcement to ensure consistency and due process. ICANN agrees with this and plans to support training development after the Code's adoption.

Broader Education and Outreach: There is a call for ICANN to invest in education and outreach opportunities (e.g., webinars, onboarding sessions) to help all community members, especially new participants, understand their disclosure responsibilities.

Centralized SOI Management: To improve transparency and accessibility across ICANN's diverse discussion spaces, a centralized repository or tool that allows participants to maintain both general and issue-specific disclosures has been suggested.

Periodic Reviews and Transparency of Actions: The community encourages periodic reviews of the Code to adapt to changes in technology, industry practices, and ethical standards. It is also suggested that anonymized summaries of disclosure trends or enforcement actions could be published to further enhance transparency.

Unincorporated Suggestions: Some community suggestions, such as developing explicit exceptions to disclosure or including specific dollar amount thresholds for financial interests, have not been incorporated into the current updated draft. ICANN notes that information is not yet sufficient to define such exceptions and that the Code is intentionally broad to include non-monetary interests.

Concerns about Applicability and Enforceability: While generally supportive, some commenters previously expressed objection to the draft Code, questioning the documented need for it as a condition for participation and raising concerns that the proposed requirements might be unworkable, unenforceable, or even violate ICANN Bylaws. The public comment process seeks to further define enforcement paths.

My submission generally supports the updated ICANN Community Participant Code of Conduct Concerning Statements of Interest, recognizing it as a crucial step towards enhancing transparency and ethical participation within ICANN's unique multistakeholder model. The legitimacy of ICANN processes relies heavily on clear and full disclosure of interests influencing participation.

We commend the draft for its improved clarity and expanded practical examples, particularly in differentiating between passive monitoring and active participation, which helps set clear disclosure thresholds. The thoughtful consideration of confidentiality concerns while still requiring non-participation when disclosure is impossible is also appreciated. The inclusion of a detailed enforcement framework empowering community chairs, coupled with recognition of organizational responsibility, represents meaningful progress in accountability.

However, for the Code's effective implementation, we emphasize the critical need for formalized training and robust resources to ensure consistent and fair enforcement by community leaders. We also recommend comprehensive education and outreach for all participants, especially new ones, to foster a universal understanding of disclosure responsibilities. The development of a centralized tool or repository for Statements of Interest would significantly improve accessibility and streamline compliance. Furthermore, we suggest periodic reviews of the Code to ensure its ongoing relevance and the publication of anonymized summaries of disclosure trends or enforcement actions to enhance transparency and identify areas for future refinement. These recommendations aim to strengthen the Code's practical application and reinforce ICANN's commitment to accountability and inclusivity in Internet governance.