Hi Greg: 

That would be fine, although repetitive. (I understand that my recommendation noted that repetitiveness also). 

I think it is important to signal to the community that the GNSO intends to proactively pursue the discussion and confining that point to a Whereas clause might diminish its effectiveness. 

Once we are trying to explain, “no, no, no, see it is here in the Whereas clause,” we have already lost the debate. My opinion is that we should include it as a resolution, either instead of or in addition to the Whereas clause. 

In any case, I support the motion and will vote for whatever version Tomslin delivers as final. 

Hope this is helpful in some way.

Kurt

On 31 Jul 2024, at 11:26 am, DiBiase, Gregory <dibiase@amazon.com> wrote:

Thanks Kurt- I note there is a whereas clause with a similar theme:

Whereas, the GNSO Council recognizes the importance of Registration Data Accuracy to the ICANN community and commits to continue its discussion of how best to move forward on this topic.

 

Would it make sense to simply add this as a resolved clause as well?

 

 

From: kurt kjpritz.com via council <council@icann.org> 
Sent: Monday, July 29, 2024 4:59 PM
To: Tomslin Samme-Nlar <mesumbeslin@gmail.com>
Cc: GNSO Council List <council@gnso.icann.org>; Julie Bisland via Gnso-secs <gnso-secs@icann.org>
Subject: [EXTERNAL] [council] Re: Motion - Registration Data Accuracy Scoping Team Recommendations

 

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.

 

Thanks Tomslin:  

 

I will second this motion. 

 

You might consider a third resolution to the effect of: “The Council will continue to work with its constituent stakeholder groups to develop a methodology for advancing the Registration Data Accuracy discussion and to launch those approaches in the near term.”  

 

Or something like that - to make the point in the final Whereas clause clear. 

 

Whether you include the additional resolution or not, I second the motion. 

 

Thanks for putting this together, 

 

Kurt

 

 

On 29 Jul 2024, at 4:09 pm, Tomslin Samme-Nlar via council <council@icann.org> wrote:

 

Dear Councillors,

 

Please find attached the motion for the Registration Data Accuracy Scoping Team Recommendations, for our August meeting.

 

Warmly,

Tomslin 

 

<Motion - Registration Data Accuracy Scoping Team Recommendations.docx>_______________________________________________
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.