Changes

==Board Action and Implementation Planning==

==Board Action and Implementation Planning==

The board addressed the topic of the final report at its regular meeting on July 22, 2021.<ref name="bdreso">[https://www.icann.org/resources/board-material/resolutions-2021-07-22-en#2.a Resolutions of the Board, July 22, 2021</ref><ref name="dashboard" /> In keeping with its updated processes, the board issued a scorecard<ref name="scorecard">[https://www.icann.org/en/system/files/files/ssr2-scorecard-22jul21-en.pdf ICANN.org Archive - SSR2 Scorecard], July 22, 2021</ref> categorizing the recommendations contained in the report under six headings. The board attached a 53-page rationale for its decisions.<ref>[[https://www.icann.org/en/system/files/bm/rationale-ssr2-22jul21-en.pdf ICANN.org Archive - Rationale for Resolutions regarding the SSR2 Final Report], July 22, 2021</ref> The six categories in the scorecard were each tied to either approval, rejection, or the placing of recommendations in pending status:

The board addressed the topic of the final report at its regular meeting on July 22, 2021.<ref name="bdreso">[https://www.icann.org/resources/board-material/resolutions-2021-07-22-en#2.a Resolutions of the Board, July 22, 2021</ref><ref name="dashboard" /> In keeping with its updated processes, the board issued a scorecard<ref name="scorecard">[https://www.icann.org/en/system/files/files/ssr2-scorecard-22jul21-en.pdf ICANN.org Archive - SSR2 Scorecard], July 22, 2021</ref> categorizing the recommendations contained in the report under six headings. The board attached a 53-page rationale for its decisions.<ref>[[https://www.icann.org/en/system/files/bm/rationale-ssr2-22jul21-en.pdf ICANN.org Archive - Rationale for Resolutions regarding the SSR2 Final Report], July 22, 2021</ref> The six categories in the scorecard were each tied to either approval, rejection, or the placing of recommendations in pending status:

# Recommendations the Board approves, subject to prioritization, risk assessment and mitigation, costing and implementation considerations; and recommendations that the Board approves with the understanding that they are already fully implemented;

* Recommendations the Board approves, subject to prioritization, risk assessment and mitigation, costing and implementation considerations; and recommendations that the Board approves with the understanding that they are already fully implemented;

# Recommendations the Board rejects because they cannot be approved in full; Maarten Botterman, in his blog post announcing the Board's action on the final report, explains:

* Recommendations the Board rejects because they cannot be approved in full; Maarten Botterman, in his blog post announcing the Board's action on the final report, explains:

<blockquote>The Board does not have the option to selectively approve or reject parts of a single, indivisible community recommendation; they must act on a recommendation as written and not as interpreted by ICANN org or the Board. The Board notes that part of the community intent in incorporating Specific Reviews into the ICANN Bylaws in 2016 was to require the Board to act on recommendations as written, not as interpreted by ICANN org or Board.<ref name="frblog">[https://www.icann.org/en/blogs/details/board-action-and-next-steps-on-the-ssr2-review-26-7-2021-en ICANN.org Blog - Board Action and Next Steps on the SSR 2 Review>, July 26, 2021</ref></blockquote>

<blockquote>The Board does not have the option to selectively approve or reject parts of a single, indivisible community recommendation; they must act on a recommendation as written and not as interpreted by ICANN org or the Board. The Board notes that part of the community intent in incorporating Specific Reviews into the ICANN Bylaws in 2016 was to require the Board to act on recommendations as written, not as interpreted by ICANN org or Board.<ref name="frblog">[https://www.icann.org/en/blogs/details/board-action-and-next-steps-on-the-ssr2-review-26-7-2021-en ICANN.org Blog - Board Action and Next Steps on the SSR 2 Review>, July 26, 2021</ref></blockquote>

# Recommendations the Board rejects; Although ten recommendations were rejected, those recommendations were clustered around three top-level recommendations: the creation of a CSO position with ICANN org; the creation of a [[temporary specification]] requiring all contracted parties to keep domains with reported DNS abuse activity below a certain percentage threshold; and an [[Expedited Policy Development Process]] to define and implement an anti-abuse policy.<ref name="scorecard" />

* Recommendations the Board rejects; Although ten recommendations were rejected, those recommendations were clustered around three top-level recommendations: the creation of a CSO position with ICANN org; the creation of a [[temporary specification]] requiring all contracted parties to keep domains with reported DNS abuse activity below a certain percentage threshold; and an [[Expedited Policy Development Process]] to define and implement an anti-abuse policy.<ref name="scorecard" />

# Recommendations the Board determines to be pending, likely to be approved once further information is gathered to enable approval;

* Recommendations the Board determines to be pending, likely to be approved once further information is gathered to enable approval;

# Recommendations that the Board determines to be pending, holding to seek clarity or further information; and

* Recommendations that the Board determines to be pending, holding to seek clarity or further information; and

# Recommendations the Board determines to be pending, likely to be rejected unless additional information shows implementation is feasible.<ref name="scorecard" />

* Recommendations the Board determines to be pending, likely to be rejected unless additional information shows implementation is feasible.<ref name="scorecard" />

==References==

==References==