14,952
edits
Changes
Jump to navigation
Jump to search
Line 43:
Line 43: − + + + − + −
no edit summary
*A team of [[Registrar]] and [[Registry]] representatives are negotiating changes to the [[RAA]] and [[Registry Agreement]] (RA) with [[:Category:ICANN Staff|ICANN Staff]]. The revised contractual language will be published for comment by June 2023 (ICANN 77)<ref>[https://opensrs.com/blog/icann76-recap/ ICANN76 Recap, OPENSRS]</ref>
*A team of [[Registrar]] and [[Registry]] representatives are negotiating changes to the [[RAA]] and [[Registry Agreement]] (RA) with [[:Category:ICANN Staff|ICANN Staff]]. The revised contractual language will be published for comment by June 2023 (ICANN 77)<ref>[https://opensrs.com/blog/icann76-recap/ ICANN76 Recap, OPENSRS]</ref>
*the ALAC, BC, and IPC sent a joint letter seeking consultation on the DNS abuse negotiations with the Contracted Parties (precedent from 2009 and 2013). ICANN Board said Contracted Parties entered DNS abuse negotiations with a specific scope with ICANN Contractual Compliance for more enforcement tools. ICANN Board will consider conducting a listening session with the ICANN community.
*the ALAC, BC, and IPC sent a joint letter seeking consultation on the DNS abuse negotiations with the Contracted Parties (precedent from 2009 and 2013). ICANN Board said Contracted Parties entered DNS abuse negotiations with a specific scope with ICANN Contractual Compliance for more enforcement tools. ICANN Board will consider conducting a listening session with the ICANN community.
===Curative Rights===
===Curative Rights===
The GAC Consensus Advice on the [[EPDP for Specific Curative Rights Protections for IGOs]] aka "curative rights" called for a permanent pre-registration notification system. The ICANN Board does not support that approach and proposed an alternative post-registration notification system. The ICANN organization was remiss in delivering that alternative system and the board will consult with the GAC to determine if its curative rights are still consistent.<ref>ICANN76 policy outcome report, published 10 Apr 2023, pgs7-8</ref>
The GAC Consensus Advice on the [[EPDP for Specific Curative Rights Protections for IGOs]] aka "curative rights" called for a permanent pre-registration notification system. The ICANN Board does not support that approach and proposed an alternative post-registration notification system. The ICANN organization was remiss in delivering that alternative system and the board will consult with the GAC to determine if its curative rights are still consistent.<ref>ICANN76 policy outcome report, published 10 Apr 2023, pgs7-8</ref>
===Process Improvements===
===Process Improvements===
===Volunteer Burnout==
The [[ALAC]] and [[ICANN Board]] grappled with the ICANN-wide issue of volunteer burnout and how to help volunteers feel appreciated and heard. Ideas included: emeritus status for leaders to ensure support going to newcomers; tools to make engagement in ICANN more accessible and sustainable; and recognizing contributions through travel support tied to emeritus status. ALAC explained that it is having trouble retaining newcomers, despite their use of the [[ICANN Fellowship]] Program and subscription features on the ICANN [[Information Transparency Initiative]] Platform. [[ICANN CEO]] [[Sally Costerton]] proposed focused, topic-based engagement on issue tracks. [[RALO]]s and the regional [[GE|Global Stakeholder Engagement]] are also trying to work better together.<ref>ICANN76 policy outcome report, published 10 Apr 2023, pgs15</ref>
====[[PDP]]====
====[[PDP]]====
The ICANN Board asked the CSG about how to balance agility in policy development with accountability and transparency, to which they responded:
The ICANN Board asked the CSG about how to balance agility in policy development with accountability and transparency, to which they responded that they should allow the GNSO Guidance Process to work through applicant support first and then evaluate it as a mechanism, form expert working groups for specific problems, create Rapid Response Teams, and rely on limited scopes and small teams.
allow the GNSO Guidance Process to work through applicant support first and then evaluate it as a mechanism, form expert working groups for specific problems, create Rapid Response Teams, and rely on limited scopes and small teams.
====SOIs====
====SOIs====