Sebastian, et al,

Thanks.  As best I can tell, the proposed revised charter is to proceed with the old SSAD.  To say this another way, the implementation and deployment of RDRS is a two to three year temporizing step, and then the plan is to return to the previously proposed SSAD concept.  I think this is a major mistake.  At the very least, it deserves a careful assessment of the purpose and whether the design will accomplish the purpose.

Here are the key points.  (This is not necessarily complete; there may be other key points.)
  1. Users (requesters) of the system need to know whether their requests will be fulfilled and what data they will receive.  As part of this, they need to know what they have to do to be qualified to make those requests, and they need to know what their obligations are after they receive the requested data.

  2. Holders of the data, usually the registrars, need to know they will not incur significant risk if they provide responses in accordance with the rules.

  3. The vast majority of the requests and responses should be handled automatically.  This is the only way to keep costs under control and to make the system usable for the majority of cases.

  4. There needs to be a way to perform searches and correlations.  These may need to be done via trusted intermediary processes.

  5. The quality/accuracy of the data has to be addressed.  Allowing privacy/proxy services without control vitiates the entire notion of accurate registration data.

  6. Privacy laws and general privacy principles have to be observed.

  7. The system should be designed and operated to apply to and be for the benefit of the entire Internet community, not just the ICANN contracted parties.
I'll try to say more going forward.  For the present, this note signals an objection to the proposed charter as it is currently written.

Thanks,

Steve



On Thu, Aug 24, 2023 at 8:46 AM Sebastien@registry.godaddy <Sebastien@registry.godaddy> wrote:

Dear Small Team,

 

As we will all be back at our desks in the next week or two I wanted to get us back into thinking about what is ahead of us with the RDRS.

 

1/ Thank you to those who contributed to the documents shared by Yuko last month. I am including her 27 July email below if anyone needs a refresher.

We agreed that there was no immediate need to pivot this into presentations, brochures or any other support you might need to promote the service, but as we are now able to look at our calendars for the next few months, it would be good to raise possible requests and deadlines if you are attending relevant events and would want Staff support in producing material.

 

2/ Marika sent 2 days ago a reminder to review and confirm the proposed charter for the Standing Committee to continue our good work after launch  (see https://docs.google.com/document/d/1IFmCY1xEtWy7IoyM-uSYiRkzFkc0jLdM/edit). Thank you to those who confirmed it works. Thumbs up also from the Requestor side would be great.

 

3/ We will need to get into reviewing T&Cs before launch. I understand these have been in the working and we can look forward to drafts soon.

 

4/ We have not scheduled our next meeting yet. A number of us haven’t yet returned from their break.

Next week (28 July) looks early and the following Monday is Labor Day in the US. Unless anyone is itching to get back to it earlier, can I suggest for prepare our next call for Monday 11 September at our regular schedule, for a call every second week thereafter? I will ask Staff to send us invite to block the time slot. We can always agree to augment the cadence in the lead to launch if we find we need more time to get ready for it.

 

 

Kindly,

 

 

Sebastien Ducos

GoDaddy Registry | Senior Client Services Manager

signature_3256585056

+33612284445

France & Australia

sebastien@registry.godaddy

 

 

From: GNSO-EPDPP2-SmallTeam <gnso-epdpp2-smallteam-bounces@icann.org> on behalf of Yuko Yokoyama <yuko.yokoyama@icann.org>
Date: Thursday, 27 July 2023 at 11:43 pm
To: gnso-epdpp2-smallteam@icann.org <gnso-epdpp2-smallteam@icann.org>
Subject: [GNSO-EPDPP2-SmallTeam] RDRS Talking Points - 3 clean documents

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

 

Dear GNSO Small Team,

 

Thank you again for all your valuable input on the RDRS Talking Points document. Due to the nature of the cleaning up process, I have opted to preserve all redline/comments in the original document, but created 3 clean documents based on that. These 3 documents incorporated all of you feedback and comments as appropriate.

 

 

If you see something glaring, please do let me know. Otherwise, please consider these final in principle, and are ready for your use.  

 

Please also be reminded that ICANN now has a one-page flyer, that will complement the talking point documents. They are translated into 6 UN languages + Portuguese:

 

 

Thank you,

 

Yuko Yokoyama

Program Director

Strategic Initiatives, Global Domains & Strategy

Internet Corporation for Assigned Names and Numbers (ICANN)

 

Direct Line:  +1 310 578 8693

Mobile: +1 310 745 1517

E-mail:  yuko.yokoyama@icann.org

www.icann.org

_______________________________________________
GNSO-EPDPP2-SmallTeam mailing list
GNSO-EPDPP2-SmallTeam@icann.org
https://mm.icann.org/mailman/listinfo/gnso-epdpp2-smallteam

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