Hi Anne,

 

Thank you for your response to my message.

 

You are correct, the Council is not modifying the SSAD EPDP recommendations at this point, but the Council is directing the ICANN Board to move forward with the implementation of the Whois Disclosure System. Per the small teams recommendations (and previous Council guidance), the consideration of the SSAD EPDP recommendations would remain paused for the duration of the Whois Disclosure System (up to 2 years) following which an informed decision is expected to be taken on how to proceed with the SSAD EPDP recommendations. 

 

To clarify, there would be no vote on the actual letter, but the letter would be the vehicle to confirm the Council’s support for the EPDP Phase 2 small team recommendations as documented in the addendum that will be shared with the Council shortly. As such, the question is about how the Council would express this support – either through its discussion during the upcoming Council meeting or through a vote on the motion.

Noting the clarity a vote and a motion brings, as previously indicated, this would be my preferred approach and to that extent I just sent to the list the motion I already shared a month ago along with the final version of the addendum. 

 

In relation to your other questions, the addendum provides more information in relation to the expected duration of the Whois Disclosure System as well as the reporting requirements. In relation to the UDRP, as the Whois Disclosure System is voluntary, if there is no value identified by UDRP Providers and/or registrars to manage requests through the system, it would not be used for this purpose.   

 

I hope this is helpful.

 

Kindly,

 

 

Sebastien Ducos

GoDaddy Registry | Senior Client Services Manager

signature_2439627859

+33612284445

France & Australia

sebastien@registry.godaddy

 

 

From: Aikman-Scalese, Anne <AAikman@lewisroca.com>
Date: Thursday, 3 November 2022 at 8:50 pm
To: Devan Reed <devan.reed@icann.org>, council@gnso.icann.org <council@gnso.icann.org>, Sebastien Ducos <Sebastien@registry.godaddy>
Cc: gnso-secs@icann.org <gnso-secs@icann.org>
Subject: RE: Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC

Caution: This email is from an external sender. Please do not click links or open attachments unless you recognize the sender and know the content is safe. Forward suspicious emails to isitbad@.

 

HI Sebastien et al,

I don’t have experience with what belongs on Council’s agenda for discussion so I want to ask about these two items first before making any suggestions:

 

  1. Sub Pro Work Track 6 Outreach:

 

https://www.icann.org/en/blogs/details/subpro-work-track-6-capacity-development-communications-and-outreach-02-11-2022-en

 

  1. Auction Proceeds Grant Program Report Delivered to the ICANN Board – is it available to us?

 

https://www.icann.org/ru/blogs/details/icann-org-delivers-icann-grant-program-design-and-implementation-plan-update-20-10-2022-en#:~:text=The%20Grant%20Program%20is%20the%20culmination%20of%20years,last%20resort%20in%20the%202012%20New%20gTLD%20Program.

 

 

Thank you,

Anne

 

Anne E. Aikman-Scalese

Of Counsel

AAikman@lewisroca.com

D. 520.629.4428

 

From: council <council-bounces@gnso.icann.org> On Behalf Of Devan Reed via council
Sent: Tuesday, November 1, 2022 10:07 AM
To: council@gnso.icann.org
Cc: gnso-secs@icann.org
Subject: [council] Document and Motion deadline | Monday 07 November 2022 at 23:59 UTC for GNSO Council Meeting 17 November 2022 at 05:00 UTC

 

[EXTERNAL]


Dear all,

Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday, 07 November 2022 at 23:59 UTC) of the GNSO Council Meeting on Thursday, 17 November 2022 at 05:00 UTC.

Motions should be sent to the Council mailing list by a councilor and will then be posted on the Wiki at: https://community.icann.org/x/oQjVD

 

Thank you.

 

Devan

 



This message and any attachments are intended only for the use of the individual or entity to which they are addressed. If the reader of this message or an attachment is not the intended recipient or the employee or agent responsible for delivering the message or attachment to the intended recipient you are hereby notified that any dissemination, distribution or copying of this message or any attachment is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender. The information transmitted in this message and any attachments may be privileged, is intended only for the personal and confidential use of the intended recipients, and is covered by the Electronic Communications Privacy Act, 18 U.S.C. §2510-2521.