HI Greg and Farzaneh, Thank you both, we will get the motions wiki page updated shortly: https://icann-community.atlassian.net/wiki/x/JKifBg. All the best, Terri From: farzaneh badii via council <council@icann.org> Reply-To: farzaneh badii <farzaneh.badii@gmail.com> Date: Tuesday, April 1, 2025 at 4:27 PM To: "DiBiase, Gregory" <dibiase@amazon.com> Cc: "Council@icann.org" <council@icann.org> Subject: [council] Re: Motion re: Billing Contact Hi Anne and Greg I find Anne’s amendment friendly too and it should be accepted. Farzaneh On Tue, Apr 1, 2025 at 4:37 PM DiBiase, Gregory <dibiase@amazon.com<mailto:dibiase@amazon.com>> wrote: Thank you Anne. I accept the amendment as friendly. Thanks, Greg From: Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> Sent: Monday, March 31, 2025 10:46 AM To: Paul McGrady <paul@elstermcgrady.com<mailto:paul@elstermcgrady.com>> Cc: farzaneh badii <farzaneh.badii@gmail.com<mailto:farzaneh.badii@gmail.com>>; DiBiase, Gregory <dibiase@amazon.com<mailto:dibiase@amazon.com>>; Council@icann.org<mailto:Council@icann.org> Subject: RE: [EXTERNAL] [council] Re: Motion re: Billing Contact CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Actually, this language from Paragraph 21 should probably appear as a RESOLVED clause rather than background: RESOLVED, The GNSO Council confirms and commits that, going forward, it will be specified in Working Group Charters that if Working Groups intend to modify a requirement within the Registry Agreement, Registrar Accreditation Agreement, or Consensus Policy via Consensus Policy recommendations, the policy recommendations must explicitly and specifically identify which requirements are intended to be modified and how such requirements are recommended to be modified per their Consensus Policy recommendations. Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Mon, Mar 31, 2025 at 10:25 AM Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> wrote: P.S. the language below in red is a proposed friendly amendment that would need to be accepted by the maker of the Motion (and probably the seconder as well?). Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Mon, Mar 31, 2025 at 10:23 AM Anne ICANN <anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com>> wrote: Regarding Paragraph 21, I think it's a good summary as to procedure but I think it needs to be much more specific as to a requirement in future WG Charters in relation to the following sentence. The GNSO Council confirms and commits that, going forward, it will be specified in Working Group Charters that if Working Groups intend to modify a requirement within the Registry Agreement, Registrar Accreditation Agreement, or Consensus Policy via Consensus Policy recommendations, the policy recommendations must explicitly and specifically identify which requirements are intended to be modified and how such requirements are recommended to be modified per their Consensus Policy recommendations. Thank you, Anne Anne Aikman-Scalese GNSO Councilor NomCom Non-Voting 2022-2026 anneicanngnso@gmail.com<mailto:anneicanngnso@gmail.com> On Fri, Mar 28, 2025 at 8:42 AM Paul McGrady via council <council@icann.org<mailto:council@icann.org>> wrote: +1 The last sentence of paragraph 21 addresses concerns going forward. Thank you leadership! Much appreciated. Best, Paul From: farzaneh badii via council <council@icann.org<mailto:council@icann.org>> Sent: Friday, March 28, 2025 10:35 AM To: DiBiase, Gregory <dibiase@amazon.com<mailto:dibiase@amazon.com>> Cc: Council@icann.org<mailto:Council@icann.org> Subject: [council] Re: Motion re: Billing Contact Thank you Greg and the leadership team. I second the motion. Farzaneh On Fri, Mar 28, 2025 at 11:24 AM DiBiase, Gregory via council <council@icann.org<mailto:council@icann.org>> wrote: * Attachment protected by Amazon: * Billing Contact Motion.docx [us-west-2.secure-attach.amazon.com]<https://urldefense.com/v3/__https:/us-west-2.secure-attach.amazon.com/780ad4...> Amazon has replaced the attachment in this email with a download link. Downloads will be available until April 27, 2025, 15:24 (UTC+00:00). Tell us what you think [amazonexteu.qualtrics.com]<https://urldefense.com/v3/__https:/amazonexteu.qualtrics.com/jfe/form/SV_ehu...> For more information click here [docs.secure-attach.amazon.com]<https://urldefense.com/v3/__https:/docs.secure-attach.amazon.com/guide__;!!P...> Hello All, Please see the attached motion in which the GNSO Council would confirm to ICANN that the EPDP Team did intend to modify the current Registrar Accreditation Agreement requirements related to billing contact, and that the current RAA requirements for the collection, retention, and escrow of billing contact have been eliminated by the Registration Data Policy. We have added language noting the exceptional circumstances surrounding this issue. We are also cognizant that several Councilors preferred a different approach to resolving this issue. We appreciate this perspective, however, given the amount of discussion to date, Leadership believes a putting this matter to vote is the appropriate next step. We appreciate everyone’s thoughtful comments on this matter and hope we can resolve at April’s meeting. Thanks, Greg _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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. This email originated from outside the firm. Please use caution. _______________________________________________ council mailing list -- council@icann.org<mailto:council@icann.org> To unsubscribe send an email to council-leave@icann.org<mailto: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.