September 2020 - IRT.RegDataPolicy

Task 111: Review Redline - URS High Level Technical Requirements
by Dennis Chang 22 Sep '20

22 Sep '20

Dear IRT, Redline document for URS High Level Technical Requirements is ready for your review and added to IRT Task. 111 Review Redline - URS High Level Technical Requirements<https://docs.google.com/document/d/11Ng3Lix78lD1UruF6as1a9Ya-AXsQ4lA/edit> 20201006 -- With Gratitude, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Change in SOI
by Amr Elsadr 21 Sep '20

21 Sep '20

Hi IRT and IPT, I’m sending this email to notify members of the IRT and IPT that I have recently joined UNR (fka UniRegistry), and will therefore be representing UNR moving forward. I have updated my GNSO SOI to indicate this. I can now be reached via amr(a)unr.com. Thanks. Amr

1 0

Task #110: RedDoc - URS Procedure Review
by Dennis Chang 18 Sep '20

18 Sep '20

Dear IRT, RedDoc for Uniform Rapid Suspension System Procedure is provided to you for review and added to IRT task: 110 Review Redline - Uniform Rapid Suspension System Procedure<https://docs.google.com/document/d/1epxSpRxEP2yisd5Kik619ULvYfj-cEux/edit#h…> 20201002 As a reminder, the sheet called ImpactedList in the IRT Workbook contains the growing list we are working on. You’ll note the listed documents are now linked per your request. (Thanks Isabelle!) When we believe the list is completed (IPT has identified all documents to be redlined), I’ll make an announcement. Till then please feel free to let us know of documents you believe should be added to the list. As always, thank you so much for your support! Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Task#109: RedDoc - URS Rules Review
by Dennis Chang 18 Sep '20

18 Sep '20

Dear IRT, As we discussed at the IRT meeting, the redlined documents will be provided for your review; one document at a time and assigned as IRT tasks. Here is the 1st RedDoc. It is for the Uniform Rapid Suspension System Rules – URS Rules. Added to the IRT task as Task #109. 109 Review Redline - Uniform Rapid Suspension System Rules<https://docs.google.com/document/d/1WxIB-HwfEPYj6g_9_Y4piK591czX7wxB/edit#h…> 20201002 Please note the deadline being 2 weeks out; don’t mean to ask you to work the weekend of course, Thank you for your support! -- Kind Regards, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Review the plan for redlining documents impacted by the RegDataPolicy
by Dennis Chang 16 Sep '20

16 Sep '20

Dear IRT, As discussed at today’s call, this task is added to the IRT Task list 108 Review the plan for Impacted policies and procedure update (RedDocPlan)<https://docs.google.com/document/d/1S6NI7oOQxtt0JM3f-2RLu8y3wJ_y_2YoMswKci5…> 20200930 The task here it to review the “PLAN” and not the redlined documents. The Redlined Documents will be assigned one by one as individual review tasks to the IRT as we have them available to you. With Grattitude, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

1 0

Liaison Report submitted to Council
by Sebastien＠registry.godaddy 14 Sep '20

14 Sep '20

Dear IRT, Please find attached my report to the Council. As mentioned in my earlier email in answer to Roger’s comments, I am happy to take points of precision on this between now and Sep 24th. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1094528548] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos> From: Sebastien Ducos <Sebastien(a)registry.godaddy> Date: Monday, 14 September 2020 at 1:53 pm To: Nathalie Peregrine <nathalie.peregrine(a)icann.org>, "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: Re: [council] ** REMINDER of due date | Document and Motion deadline Monday 14th September 2020 at 23:59 UTC for GNSO Council Meeting 24 September 2020 at 12:00 UTC Dear Natalie, Please find attached my Liaison Report on the IRT for Registration Data Policy Implementation’s work on Recommendation 7. If appropriate, I would like to have time on the agenda to present it. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1709713060] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos> From: council <council-bounces(a)gnso.icann.org> on behalf of Nathalie Peregrine <nathalie.peregrine(a)icann.org> Date: Friday, 11 September 2020 at 9:47 am To: "council(a)gnso.icann.org" <council(a)gnso.icann.org> Cc: "gnso-secs(a)icann.org" <gnso-secs(a)icann.org> Subject: [council] ** REMINDER of due date | Document and Motion deadline Monday 14th September 2020 at 23:59 UTC for GNSO Council Meeting 24 September 2020 at 12:00 UTC Notice: This email is from an external sender. Dear all, Reports, motions and documents for consideration are due no later than (NLT) 10 days in advance (i.e. Monday 14 September 2020 at 23:59 UTC) of the GNSO Council Meeting on Thursday 24 September 2020 at 12: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/wAS-C Thank you. Nathalie Nathalie Peregrine Manager, Operations Support (GNSO) Internet Corporation for Assigned Names and Numbers (ICANN) Skype: nathalie.peregrine.icann Find out more about the GNSO by visiting: https://learn.icann.org/ <https://urldefense.proofpoint.com/v2/url?u=https-3A__learn.icann.org_&d=DwM…> Follow @GNSO on Twitter: https://twitter.com/ICANN_GNSO <https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_ICANN-5FGN…> Transcripts and recordings of GNSO Working Group and Council events are located on the GNSO Master Calendar <https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_grou…>

1 0

IRT Liaison to the GNSO Council
by Sebastien＠registry.godaddy 14 Sep '20

14 Sep '20

Dear IRT Members, Please find attached my report to the GNSO Council. This will be filed tomorrow to meet my deadline on document submission for the next GNSO Meeting on 24 September. Please note that as per my suggestion on Friday, I based the report on the earlier “Path Forward” document, removing any mention of my earlier suggested path. I have left you a redline from that earlier document. As per my 26 August email, having received no group-approved instructions in writing, I am reporting in my own name on the situation as I see it. In a continuous attempt to remain neutral, I try representing the different views as I understand them, up until the last exchanges on Friday. I will seek direction/suggestions from the Council on their views on “if the Council believes there is no conflict between Rec 7 and the Thick WHOIS Policy” and their understanding of the implications. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_445988404] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> www.linkedin.com/in/sebastienducos<https://www.linkedin.com/in/sebastienducos>

3 3

IRT Liaison report on Rec7 during the 20Aug2020 GNSO Council Meeting
by Ducos, Sebastien 13 Sep '20

13 Sep '20

Dear IRT, As per our discussion during our IRT call on 19Aug2020, I reported yesterday (20Aug2020) to the GNSO Council the IRT’s request for clarification on the prior existence of a Legal Basis to support the transfer of data under Rec 7. For clarity, I now have to present the said request in writing. I propose the following wording, but invite your input. As has been the case all along in this exercise, this is not a reflexion of my personal point of view, but should represent the different points of view of the IRT. Please ensure yours is reflected. For the sake of council members who may not all be as familiar with the topic as we are, I would like to submit a limited relevant number of reference documents for their review. Please confirm that the ones I have included are indeed relevant and the links I have provided are the most direct to the latest/final versions of the said documents. [Date] RE: EPDP Phase 1 Recommendation 7 – Legal Basis Dear GNSO Council, In an attempt to resolve a different in interpretation of the EPDP Phase I Recommendation 7, the IRT is seeking clarification with regards to the existence of legal basis which covers the transfer of data (including personal data) from Registrars to Registries, in all cases. Recommendation 7 states: “The EPDP Team recommends that the specifically-identified data elements under “[t]ransmission of registration data from Registrar to Registry”, as illustrated in the aggregate data elements workbooks, must be transferred from registrar to registry provided an appropriate legal basis exists and data processing agreement is in place. In the aggregate, these data elements are:” [followed by the list of data points that may be transferred, some marked as Mandatory (The domain name, fields pertaining to the Registrar and Domain Statuses), others as Optional (contact fields, name servers, Registrar expiry date and Reseller)] Ref: https://urldefense.com/v3/__https://gnso.icann.org/sites/default/files/file… The IRT remains divided in the interpretation of the mention “provided an appropriate legal basis exists and data processing agreement is in place” with: * Parties who consider the mention key as in their view a legal basis may not exist in all cases and must be established for each TLD, * Parties who consider the mention relevant, view the legal basis as pre-established under Consensus Policy and expect that the currently negotiated data processing agreement (between ICANN and the CPH) will reflect the said legal basis, * Parties who consider legal basis established in all cases in this context, and seek to remove the sentence for the avoidance of confusion. Further, each party cites in its argument: * The EPDP Phase I Final Report and the underlying work - https://urldefense.com/v3/__https://gnso.icann.org/sites/default/files/file… * Existing Consensus Policy including but not limited to the Thick RDDS (WHOIS) Transition Policy - https://urldefense.com/v3/__https://www.icann.org/resources/pages/thick-who… * The “Bird & Bird memo” of 8 March 2019 “Advice on the legal basis for transferring Thick WHOIS” - https://urldefense.com/v3/__https://community.icann.org/download/attachment… and related public comments submitted in the context of the above. Question to the GNSO Council: * Does the GNSO Council advise that there exists under Consensus Policy and in accordance with GDPR a legal basis which covers the transfer of data, including personal data, between Registrar and Registries in all cases? [IRT Liaison signature] Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_1081474336] +61449623491 Level 8, 10 Queens Road Melbourne, VIC, Australia 3004 sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy> https://urldefense.com/v3/__http://www.linkedin.com/in/sebastienducos__;!!N… <https://urldefense.com/v3/__https://www.linkedin.com/in/sebastienducos__;!!… >

12 42

Followup to Rec 27/yesterday's call
by Sarah Wyld 10 Sep '20

10 Sep '20

Hello team, Could the IPT please provide a summary of the updated plan discussed yesterday to approach Recommendation 27/modifying affected Consensus Policies, hopefully specifically referring back to the "Possible next steps <https://gnso.icann.org/sites/default/files/file/field-file-attach/next-step…>" document? This would help those who weren't able to attend the call, but also I find it easier to think through when it's all written down in front of me. Thank you, -- Sarah Wyld Domains Product Team Tucows +1.416 535 0123 Ext. 1392

2 1