Dear Council Members, I would also add that whatever procedure we adopt to permit modification of a Board - adopted PDP Recommendation should also apply to a Board adopted CCWG Recommendation. (This was an issue in relation to Auction Proceeds.) In fact, there is also no procedure in the CCWG Working Group guidelines which specifies a need for the Board to communicate with the CCWG Chartering organizations when it does not want to accept a CCWG Final Recommendation. These gaps in procedure need to be addressed as to PDPs and as to CCWGs. Looking forward to this discussion in the Council meeting on the 13th! Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com On Sat, Feb 1, 2025 at 12:25 PM Anne ICANN <anneicanngnso@gmail.com> wrote:

Thanks Terri. Re Item 8, I think we need some specific focused discussion on how to develop an appropriate mechanism for Board-adopted Recommendations to be reversed or modified. As we know, this is not accounted for in the ByLaws or in the GNSO Operating Procedures, though the ByLaws provide a specific method for the Board and the GNSO to communicate where the Board does not adopt a Recommendation. This yields a possible Supplemental Recommendation process and that was used extensively in the Sub Pro Small Team Plus deliberations.

In my personal opinion, we are not "out of the woods" yet on all Sub Pro Recommendations adopted by the Board so it would be wise to get this work done quickly. (BTW I agree with Thomas that a ByLaws amendment applying the existing Supplemental Recommendation procedures to this fact scenario is the way to go from both an internal and a public-facing point of view.) To the best of my recollection, the reversal of Sub Pro Final Recommendation 20.6 (previously adopted by the Board) was not discussed with the GNSO until after the Board took action via Resolution to reverse its prior adoption.

Thank you, Anne

Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com

On Fri, Jan 31, 2025 at 11:06 AM Terri Agnew via council < council@icann.org> wrote:

...

Dear all,

Please find below the agenda for the GNSO Council Meeting on 13 February 2025 at 21:00 UTC This is posted on the agenda wiki page <https://community.icann.org/x/eQByG>.

Thank you.

Kind regards,

Terri

Policy Team Supporting the GNSO

*GNSO Council Agenda **13 February 2025*

Please note that all documents referenced in the agenda have been gathered on a Wiki page for convenience and easier access: https://community.icann.org/x/HgBbGQ

This agenda was established according to the GNSO Operating Procedures <https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedu...> v3.5, updated on 15 March 2023.

For convenience:

- An excerpt of the ICANN Bylaws defining the voting thresholds is provided in Appendix 1 at the end of this agenda. - An excerpt from the Council Operating Procedures defining the absentee voting procedures is provided in Appendix 2 at the end of this agenda.

GNSO Council meeting on Thursday, 13 February 2025 at 21:00 UTC: https://tinyurl.com/5zh8rb2v

13:00 Los Angeles; 16:00 Washington DC; 21:00 London; 22:00 Paris; 00:00 Moscow (Friday); 08:00 Melbourne (Friday)

*GNSO Council Meeting Remote Participation:** https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1 <https://icann.zoom.us/j/91048235847?pwd=bmEHjk0uYT3sR2DIoE0c0yw4HKbM6O.1>*

Councilors should notify the GNSO Secretariat in advance if they will not be able to attend and/or need a dial out call.

___________________________________

*Item 1: Administrative Matters (5 minutes)*

1.1 - Roll Call

1.2 - Updates to Statements of Interest

1.3 - Review / Amend Agenda

1.4 - Note the status of minutes for the previous Council meetings per the GNSO Operating Procedures:

Minutes <https://gnso.icann.org/sites/default/files/policy/2024/minutes/minutes-gnso-...> of the GNSO Council Meeting on 19 December were posted on 30 December 2024.

Minutes <https://gnso.icann.org/sites/default/files/policy/2025/minutes/minutes-gnso-...> of the GNSO Council Meeting on 09 January 2025 were posted on 26 January 2025.

*Item 2: Opening Remarks / Review of Projects & Action List (0 minutes)*

2.1 - Review focus areas and provide updates on specific key themes / topics, to include review of Projects List <https://gnso.icann.org/en/council/project> and Action Item List. <https://community.icann.org/x/RgZlAg>

*Item 3: Consent Agenda (5 minutes)*

- Confirm the GNSO-nominated ICANN Fellowship Program Mentor and Selection Committee Member positions - Mentor: Glen De Saint Géry - Selection Committee Member: Maud Adjeley Ashong Elliot - Confirm the Latin Script Diacritics PDP WG Chair - Michael Bauland

*Item 4: COUNCIL DISCUSSION - Update on ICANN’s Enforcement of DNS Abuse Mitigation Requirements - Six Month Progress Update (20 minutes)*

On 8 November 2024, ICANN announced the release of a six-month report, "ICANN's Enforcement of DNS Abuse Mitigation Requirements <https://www.icann.org/en/system/files/files/icann-enforcement-of-dns-abuse-m...>," detailing its enforcement actions under the new Domain Name System (DNS) Abuse mitigation requirements. The requirements, which became effective on 5 April 2024, require generic top-level domain registry operators (ROs) and registrars to take mitigation steps to address well-evidenced DNS Abuse, which, for the purposes of ICANN agreements, is limited to malware, botnets, phishing, pharming, and spam used as a vector for delivering the other forms of DNS Abuse.

During the initial six months of enforcement, from 5 April to 5 October 2024, ICANN's Contractual Compliance team launched 192 DNS Abuse investigations involving contracted parties. This enforcement effort led to impactful results, including:

· Issuing formal Notices of Breach to an RO and a registrar for noncompliance with DNS Abuse mitigation requirements.

· Resolving 154 cases that resulted in the suspension of over 2,700 abusive domain names and the disabling of more than 350 phishing websites.

The six-month report provides additional context and details about the specific actions taken to keep the ICANN community informed and enhance transparency around the enforcement of DNS Abuse requirements.

Here, the Council will hear an update from ICANN Compliance and have an opportunity to ask questions.

4.1 - Introduction of Topic (Leticia Castillo, ICANN org Compliance)

4.2 - Council Discussion

4.3 - Next Steps

*Item 5: COUNCIL DISCUSSION - Next Steps for Policy and Implementation Policy Status Report (10 minutes) *

ICANN org published a Policy Status Report (PSR) on the Policy and Implementation Working Group Final Report <https://gnso.icann.org/sites/default/files/filefield_47703/policy-implementa...> to support the GNSO Council in its assessment of the effectiveness of its recommendations in achieving their intention of supporting and improving the effectiveness of GNSO Policy Development and Implementation processes.

The PSR includes background on the Policy and Implementation Recommendations and their intended purpose, readily available data, staff observations and analysis, and performance against the stated objectives by the GNSO Council and the ICANN community. The PSR is intended to serve as input to the GNSO Council review of policy and implementation related efforts, notably in the assessment of the following GNSO processes introduced in light of the recommendations of the Final Report:

- The GNSO Expedited Policy Development Process (EPDP) - The GNSO Guidance Process (GGP) - The GNSO Input Process (GIP) - The Implementation Review Team (IRT) Principles & Guidelines, as well as the requirement to form an IRT following the adoption by the ICANN Board of GNSO Policy recommendations - The Consensus Policy Implementation Framework (CPIF)

In summary, the PSR finds that these processes have proved effective in supporting and enhancing GNSO Policy and Implementation efforts, but also identifies a number of caveats and possible improvements.

Here, the Council will hear an overview of the updated PSR and determine next steps for the recommendations in the Report.

5.1 - Introduction of Topic (Peter Eakin, ICANN org)

5.2 - Council Discussion

5.3 - Next Steps

*Item 6: COUNCIL DISCUSSION - EPDP Phase 1 on the Temporary Specification - Implementation Question re: Billing Contact (20 minutes)*

During the ICANN81 GNSO Council Wrap-Up <https://icann81.sched.com/event/1p2Gu/gnso-council-wrap-up>, Thomas Rickert provided an update regarding the implementation of EPDP Temp Spec Phase 1 recommendations. Thomas is the current GNSO Council Liaison to the EPDP Temp Spec Phase 1 Implementation Review Team (IRT). Thomas noted that the IRT expressed the view that the absence of a reference to billing contact data was a drafting error, and the EPDP Team intended for the collection of billing contact data to be optional and not mandatory.

The Registration Data Policy <https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en> was published on 21 February 2024, and the policy has an effective date of 21 August 2025. The EPDP Phase 1 policy recommendations <https://gnso.icann.org/sites/default/files/file/field-file-attach/epdp-gtld-...> do not reference billing contact data, and the Registration Data Policy <https://www.icann.org/resources/pages/registration-data-policy-2024-02-21-en> also makes no reference to billing contact data.

In the interest of transparency, Thomas requested that all Councilors consult with their respective groups to ensure that others are properly informed and agree with the interpretation raised by the registrars within the IRT. Accordingly, Councilors were asked to consult with their groups. The Council discussed this topic during its meeting on 19 December 2024 <https://icann.zoom.us/rec/play/wMLdawWw7g5mSvuAbgKmzJKUiRDCBU1sSYKHcwg3nb8Ob...> and asked for additional background information on the topic.

The Council is being asked to consider the questions below:

1. Does the Council confirm billing contact was in scope for the EPDP on the Temp Spec - Phase 1 Team? 2. Does the Council confirm:

a. the collection of billing contacts by registrars should continue to be required as per current RAA requirements because EPDP Phase 1, by being silent on this, did not mean to change this requirement, OR

b. the collection of billing contacts by registrars should become optional because EPDP Phase 1, by being silent on this, meant to change the RAA requirement?

Here, the Council will discuss the above questions and determine next steps.

6.1 - Introduction of Topic (Thomas Rickert, GNSO Council Liaison to the EPDP (Temp Spec) Phase 1 IRT)

6.2 - Council Discussion

6.3 - Next Steps

*Item 7: COUNCIL DISCUSSION: Final Report of the Transfer Policy Review PDP Working Group (40 minutes)*

On 18 February 2021, the GNSO Council <https://gnso.icann.org/en/council/resolutions/2021#202102>initiated <https://gnso.icann.org/en/council/resolutions/2020-current#20210218-2> a PDP to review the Transfer Policy <https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en>, the policy that governs the process of transferring a domain name from one registrar to another. This PDP is tasked to determine if changes to the policy are needed to improve the ease, security, and efficacy of inter-registrar and inter-registrant transfers.

The Transfer Policy Review (TPR) working group began meeting in May 2021, and while it initially divided its work into three distinct groups/phases, the working group ultimately agreed that the topics within its charter needed to be considered together due to overlapping dependencies. Accordingly, the working group worked toward a comprehensive Initial Report <https://community.icann.org/pages/viewpage.action?pageId=347734037&preview=/...>, which it published on 1 August 2024. The Initial Report covers all topics in the working group’s charter, including inter-registrar transfers, change of registrant, the Transfer Dispute Resolution Policy, ICANN-approved transfers, and others.

The TPR Working Group introduced a new format to its Initial and Final Report, where it endeavors to indicate the “Policy Impact Level” of each policy recommendation. The Policy Impact Indicator is a new feature to help the reader understand the degree of change being proposed by the Working Group, i.e., how much does this recommendation differ from the current Transfer Policy?

Here, the Chair of the TPR Working Group will present an overview of the forty-seven (47) policy recommendations to the Council.

7.1 - Introduction of Topic (Roger Carney, TPR Working Group Chair)

7.2 - Council Discussion

7.3 - Next Steps

*Item 8: COUNCIL DISCUSSION: Outcomes of Strategic Planning Session (15 minutes)*

Beginning in 2018, the GNSO Council has held an annual Strategic Planning Session (SPS). The SPS is the Council’s dedicated meeting designed to (i) understand and review the GNSO’s portfolio of work for the coming year, (ii) align on the GNSO’s work priorities for the coming year, (iii) consider whether the GNSO Council has the correct resources and tools to conduct its work as manager of the PDP efficiently, effectively, and comprehensively, and (iv) discuss how to best prepare for emerging and upcoming challenges the Council could face in the coming year and beyond. This year’s SPS was held in Washington, D.C. on 14-15 January 2025.

Here, the Council will review the outcomes of the SPS and discuss next steps.

8.1 - Introduction of Topic (Greg DiBiase, GNSO Chair)

8.2 - Council Discussion

8.3 - Next Steps

*Item 9: Any Other Business (5 minutes)*

9.1 - ICANN82 planning update

- Reminder: Pre-ICANN82 GNSO Council Webinar is mandatory for GNSO Council members - additional details will be provided when available.

_______________________________

Appendix 1: GNSO Council Voting Thresholds (ICANN Bylaws, Article 11, Section 11.3(i))

See https://www.icann.org/resources/pages/governance/bylaws-en/#article11 .

Appendix 2: GNSO Council Absentee Voting Procedures (GNSO Operating Procedures, Section 4.4)

See https://gnso.icann.org/sites/default/files/file/field-file-attach/op-procedu...

*References for Coordinated Universal Time of 21:00 UTC*

Local time between March and November in the NORTHERN hemisphere

See https://www.timeanddate.com/time/change/ for Dates for Daylight Saving Time and Clock Changes

----------------------------------------------------------------------------

California, USA (PDT) UTC-8 13:00

San José, Costa Rica (CST) UTC-6 15:00

New York/Washington DC, USA (EDT) UTC-5 16:00

Buenos Aires, Argentina (ART) UTC-3 18:00

Kinshasa, Democratic Republic of Congo (WAT) UTC+1 22:00

Paris, France (CEST) UTC+1 22:00

Moscow, Russia (MSK) UTC+3 00:00 (Friday)

Singapore (SGT) UTC+8 05:00 (Friday)

Melbourne, Australia (AEST) UTC+11 08:00 (Friday)

----------------------------------------------------------------------

For other places see http://www.timeanddate.com and https://tinyurl.com/5zh8rb2v

_______________________________________________ council mailing list -- council@icann.org To unsubscribe send an email to council-leave@icann.org

_______________________________________________ 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.