Seb,

 

If you are going to replace “policies” in the letter, please replace it with a term that equates to the internal standards, rules,  “policies”, etc. (pick whatever synonym makes sense to the registrar community) for the decision-making process to evaluate a disclosure request.  That is what I intended and I think you did as well.

 

John

 

From: farzaneh badii via Gnso-rdrs-sc <gnso-rdrs-sc@icann.org>
Sent: Sunday, June 30, 2024 2:19 PM
To: Steve Crocker <steve@shinkuro.com>
Cc: gnso-rdrs-sc@icann.org
Subject: [Gnso-rdrs-sc] Re: Letter to Greg DiBiase and Council

 

I agree with the intent of the letter. I also agree with Sarah on removing the word policy. I also fear that the “requestors” advocacy comes across as to be treated as a separate stakeholder (something I see keeps being brought up that their

I agree with the intent of the letter. I also agree with Sarah on removing the word policy. I also fear that the “requestors” advocacy  comes across as to be treated as a separate stakeholder (something I see keeps being brought up that their voices not being heard etc) Especially the requesters with commercial interest should use the avenues available at ICANN to facilitate disclosure. Which means through their stakeholder group. In this case the commercial stakeholder group which has been equally treated throughout ICANN’s history. 

Farzaneh 

 

 

On Thu, Jun 27, 2024 at 3:50 PM Steve Crocker via Gnso-rdrs-sc <gnso-rdrs-sc@icann.org> wrote:

Heh, heh.  Some have their places in the ICANN version of a multi-stakeholder community; some do not.  Or, perhaps more precisely, some have first class places in the ICANN version of a multi-stakeholder community; others are left to figure out how to have their voices heard.

 

Steve

 

On Thu, Jun 27, 2024 at 9:46 AM Sarah Wyld <swyld@tucows.com> wrote:

I guess we'll continue to disagree on this. We are all part of the ICANN Community and all have our places in the multi-stakeholder policy development process.

Thank you,

Sarah Wyld, CIPP/E

Policy & Privacy Manager
Pronouns: she/they

swyld@tucows.com

On 2024-06-27 9:44 a.m., Steve Crocker wrote:

Sarah,

 

I disagree.  The Requestors (Respondents) do not have a venue that is as organized and as resourced as the Registrars.  Neither the Requestors nor the Registrars are well served under the existing arrangement.

 

Steve

 

 

On Thu, Jun 27, 2024 at 9:36 AM Sarah Wyld via Gnso-rdrs-sc <gnso-rdrs-sc@icann.org> wrote:

Hi Sebastien, thanks for drafting this! 

I'm good with the overall sentiment, but I'm not sure that we would all agree to this paragraph:

> Through these exchanges during ICANN79 & 80, it has become clearly apparent to us that the Requestor and Respondent Communities need more permanent fora to share and discuss their respective needs and the others’ capacity to respond to them, to potentially find a middle ground in a set of best practices or policy.

I think there are already permanent fora to develop policy, we've been through a whole PDP WG on specifically that topic which led us to this Standing Committee. We should remove "or policy" from that paragraph.

Thank you,

Sarah Wyld, CIPP/E

Policy & Privacy Manager
Pronouns: she/they

swyld@tucows.com

On 2024-06-27 8:32 a.m., Sebastien--- via Gnso-rdrs-sc wrote:

Dear Standing Committee,

 

As discussed on our call last week, please find attached my proposed letter to Greg and Council suggesting/inviting Council or the Requestor+Responder communities directly, to further the more political questions of what constitute requests; allowing to focus on our Pilot Monitoring mandate.

 

Please review and comment. Absent any changes I will send it following our call Monday.

 

Kindly,

 

 

Sebastien Ducos

GoDaddy Registry | Senior Client Services Manager

signature_1642351011

+33612284445

France & Australia

sebastien@registry.godaddy

 

 

_______________________________________________
Gnso-rdrs-sc mailing list -- gnso-rdrs-sc@icann.org
To unsubscribe send an email to gnso-rdrs-sc-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.

_______________________________________________
Gnso-rdrs-sc mailing list -- gnso-rdrs-sc@icann.org
To unsubscribe send an email to gnso-rdrs-sc-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.


 

--

Sent by a Verified

Sent by a Verified sender

sender


 

--

Sent by a Verified

Sent by a Verified sender

sender

_______________________________________________
Gnso-rdrs-sc mailing list -- gnso-rdrs-sc@icann.org
To unsubscribe send an email to gnso-rdrs-sc-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.

Confidentiality Notice
This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged, confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately either by phone (800-237-2000) or reply to this e-mail and delete all copies of this message.