Thanks Lars, for bringing us up-to-date on the status of Board Resolutions re Sub Pro policy recommendations. This section of the ByLaws may be helpful to promote understanding as to how Supplemental Recommendations are developed and approved where Board "non-adoption" applies (see 9. d. below) Section 9. *Board Approval Processes* The Board will meet to discuss the GNSO Council recommendation as soon as feasible, but preferably not later than the second meeting after receipt of the Board Report from the Staff Manager. Board deliberation on the PDP Recommendations contained within the Recommendations Report shall proceed as follows: 1. Any PDP Recommendations approved by a GNSO Supermajority Vote shall be adopted by the Board unless, by a vote of more than two-thirds (2/3) of the Board, the Board determines that such policy is not in the best interests of the ICANN community or ICANN. If the GNSO Council recommendation was approved by less than a GNSO Supermajority Vote, a majority vote of the Board will be sufficient to determine that such policy is not in the best interests of the ICANN community or ICANN. 2. In the event that the Board determines, in accordance with paragraph a above, that the policy recommended by a GNSO Supermajority Vote or less than a GNSO Supermajority vote is not in the best interests of the ICANN community or ICANN (the Corporation), the Board shall (i) articulate the reasons for its determination in a report to the Council (the "*Board Statement*"); and (ii) submit the Board Statement to the Council. 3. The Council shall review the Board Statement for discussion with the Board as soon as feasible after the Council's receipt of the Board Statement. The Board shall determine the method (e.g., by teleconference, e-mail, or otherwise) by which the Council and Board will discuss the Board Statement. 4. At the conclusion of the Council and Board discussions, the Council shall meet to affirm or modify its recommendation, and communicate that conclusion (the "*Supplemental Recommendation*") to the Board, including an explanation for the then-current recommendation. In the event that the Council is able to reach a GNSO Supermajority Vote on the Supplemental Recommendation, the Board shall adopt the recommendation unless more than two-thirds (2/3) of the Board determines that such policy is not in the interests of the ICANN community or ICANN. For any Supplemental Recommendation approved by less than a GNSO Supermajority Vote, a majority vote of the Board shall be sufficient to determine that the policy in the Supplemental Recommendation is not in the best interest of the ICANN community or ICANN. Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2024 anneicanngnso@gmail.com On Wed, Sep 13, 2023 at 6:58 AM Next Round Policy Implementation < NextRound_PolicyImplementation@icann.org> wrote:
Dear IRT members,
During the meeting tomorrow, 14 September 2023 at 13:00 UTC, we will discuss *String Similarity Evaluations*. The proposed language is published on the drive <https://docs.google.com/document/d/13vao2hJOtY6szZZRma4QVaLP750v9ftNHI7VmNC7...> and on the meeting page <https://community.icann.org/x/WwCWDw>.
------------------------------
*Please note**:*
- Some of the language reflects section *2.2.1.1 String Similarity Review* of the 2012 Applicant Guidebook <https://newgtlds.icann.org/sites/default/files/guidebook-full-04jun12-en.pdf>.
- This document includes details that are based on draft recommendations from Phase 1 report of IDN EPDP <https://itp.cdn.icann.org/en/files/internationalized-domain-names-idn/phase-...>. These sections should be considered as 'placeholder drafts' until the recommendations are finalized and approved by the Board. In other words, *the text in this document remains subject to the outcome of the IDN EPDP* and the text will be updated as appropriate once the EPDP concludes and the Board resolves on its recommendations. - This document is based on the 10 September 2023 Board Resolution <https://www.icann.org/en/board-activities-and-meetings/materials/approved-re...> that did not adopt recommendations 24.3 and 24.5. Relevant sections will be updated should the GNSO Council decide to issue supplemental recommendations, as per Bylaws Annex A <https://www.icann.org/resources/pages/governance/bylaws-en/#annexA> or PDP Manual Section 16 <https://gnso.icann.org/sites/default/files/file/field-file-attach/annex-2-pd...>, once those recommendations are adopted by the Board.
------------------------------
In addition, the *Universal Acceptance* language was updated to reflect the IRT inputs from the meeting <https://community.icann.org/x/fJOZDg> on 5 September 2023. Since no additional feedback was received, we are not planning to take the language back to the IRT until the final review before public comment. You may consult the updated language on the drive <https://docs.google.com/document/d/1quYak65EI8zeF4eQzyuz-w80OJ9CIoZG7JnlxNOv...> and on the Implementation & Policy Documents page <https://community.icann.org/pages/viewpage.action?pageId=238617525>.
Finally, for your information, the Board Resolutions <https://www.icann.org/en/board-activities-and-meetings/materials/approved-re...> from the Board Meeting on 10 September 2023, in which the Board adopted the September 2023 Scorecard <https://www.icann.org/en/system/files/files/scorecard-subpro-pdp-board-actio...>, were published. You will note that the Board resolved to adopt 18 recommendations, to not adopt 7 recommendations, and to maintain 13 recommendations as ‘pending’.
Looking forward to the meeting tomorrow!
Best regards,
Elisa
_______________________________________________ SubPro-IRT mailing list SubPro-IRT@icann.org https://mm.icann.org/mailman/listinfo/subpro-irt
_______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.