- IRT.RegDataPolicy - lists.icann.org

Registration Data Policy published!
by Dennis Chang 21 Feb '24

21 Feb '24

Dear IRT, We did it! The Registration Data Policy has been published as planned. Please read the Announcement here. https://www.icann.org/en/announcements/details/icann-publishes-registration… I am ever so grateful to the IRT for years of support in getting this done. We’ll take a minute to celebrate and then get to work on the Implementation that will go till 21 August 2025. Thanks, Dennis Chang From: "IRT.RegDataPolicy" <irt.regdatapolicy-bounces(a)icann.org> on behalf of "Dennis Chang via IRT.RegDataPolicy" <irt.regdatapolicy(a)icann.org> Reply-To: Dennis Chang <dennis.chang(a)icann.org> Date: Monday, February 12, 2024 at 1:43 PM To: "Rubens Kuhl via IRT.RegDataPolicy" <irt.regdatapolicy(a)icann.org> Cc: "aheineman(a)godaddy.com" <aheineman(a)godaddy.com>, "Karen.Day(a)sas.com" <Karen.Day(a)sas.com>, Andee Hill <andee.hill(a)icann.org> Subject: [IRT.RegDataPolicy] Courtesy Notice to IRT: Registration Data Policy scheduled to be published on 21 Feb 2024. Dear IRT, This is a quick note to inform you that we now have a publication date for our Registration Data Policy: 21 Feb 2024. Next week Wednesday. ICANN org team will begin the process of preparing for the publication and legal notices to deliver on that day. Also, the ICANN79 Meeting schedule is now available: https://www.icann.org/en/announcements/details/icann79-schedule-now-availab… Here is the link for our IRT session. Andrea should be sending out a meeting invite to get it on your calendar as she always do. https://icann79.sched.com/event/1a17X/gds-registration-data-policy-irt-coll… I’ll send you another note after we publish our policy next week. Please consider this email a courtesy notice for the collective implementation team. -- 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

ICANN79 GNSO Sessions - How to Get Organized / Remote Participation Details
by Andrea Glandon 13 Feb '24

13 Feb '24

Dear all, With ICANN79<https://meetings.icann.org/en/icann79> just around the corner, please take a moment to read the information below for a seamless and successful meeting. REGISTER NOW! DEADLINE TO REGISTER IS 29 February 2024! * Sign into Your ICANN Account or create an account here [account.icann.org]<https://urldefense.com/v3/__https:/account.icann.org/login__;!!PtGJab4!7Ose…>. * Register by selecting the Meeting Registration tile. * Click on the Registration link. NOTE: There will be no onsite registration facilities this year so you must register in advance. In-person, advance registration will close on 29 February 2024. After that point in time, only virtual participation will be open for continued registration. Walk-up and late registrations will not be accepted after the in-person advance registration closes. All walk-up and late registered attendees will only have access to virtual participation. Before creating your schedule, please read this page carefully: https://meetings.icann.org/en/remote-participation. If participating on-site, please read the Health and Safety page<https://meetings.icann.org/en/79healthandsafety>. CREATE YOUR MEETING SCHEDULE * Access the schedule here [icann79.sched.com]<https://urldefense.com/v3/__https:/icann79.sched.com/__;!!PtGJab4!7OsehoONe…>. The schedule shows up with blank circular radial buttons to the left of each session. Hover over the radial button and click “ADD TO MY SCHEDULE” or just click to add the checkmark. * Once you’ve selected all sessions, click the My Schedule link in the lower left corner or hover over your profile and select My Schedule. * Click the Phone icon, “Mobile app + iCal” (located on the right side of the page) * In the bottom section, “Export Calendar”, click the link next to “My Schedule”. When the .ics is exported, add it to the appropriate calendar. OR, after exporting, drag and drop the .ics file into your calendar. * Please remember, for security purposes, participation links will be posted 24-hours prior to the session start times. There will be no calendar invitations sent, as the meeting schedule allows you to download all sessions of interest to your individual calendars Review the Participation Tools and update Zoom * All sessions will use Zoom rooms. Access details are available 24hrs prior. * Visit the Participation Tools page<https://meetings.icann.org/en/remote-participation> for links to download the latest version of Zoom for access to the ICANN Meeting sessions. * Please see the ICANN Meeting Virtual Participation How-To Guide for more information on how to get the most out of the virtual meeting tools. Links to Bookmark ICANN79 Meeting Schedule [icann79.sched.com]<https://urldefense.com/v3/__https:/icann79.sched.com/__;!!PtGJab4!7OsehoONe…> ICANN79 GNSO Remote Participation Wiki Page<https://community.icann.org/x/XIMYEQ> GNSO Session agendas<https://community.icann.org/x/WYMYEQ> For all GNSO meeting-related queries (RP or others), please email us at: gnso-secs(a)icann.org<mailto:gnso-secs@icann.org> and we will be more than happy to assist! Kind regards, GNSO SO/AC Support team

1 0

ICANN79 Registration Data Policy IRT-Collaborative Planning for Transition Work Session
by Andrea Glandon 13 Feb '24

13 Feb '24

ICANN79 Registration Data Policy IRT-Collaborative Planning for Transition Work Session Saturday, 02 March 2024 at 16:15-17:30 local time Please see the ICANN79 schedule for location and Zoom information: https://icann79.sched.com/event/1a17X/gds-registration-data-policy-irt-coll…

1 0

Courtesy Notice to IRT: Registration Data Policy scheduled to be published on 21 Feb 2024.
by Dennis Chang 12 Feb '24

12 Feb '24

Dear IRT, This is a quick note to inform you that we now have a publication date for our Registration Data Policy: 21 Feb 2024. Next week Wednesday. ICANN org team will begin the process of preparing for the publication and legal notices to deliver on that day. Also, the ICANN79 Meeting schedule is now available: https://www.icann.org/en/announcements/details/icann79-schedule-now-availab… Here is the link for our IRT session. Andrea should be sending out a meeting invite to get it on your calendar as she always do. https://icann79.sched.com/event/1a17X/gds-registration-data-policy-irt-coll… I’ll send you another note after we publish our policy next week. Please consider this email a courtesy notice for the collective implementation team. -- 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

The SSAC has published SAC122
by Steve Crocker 17 Jan '24

17 Jan '24

Dennis, Per the note below, SSAC has published its report on Urgent Requests. This completes the action we initiated within SSAC in response to the incompleteness of the policy adopted by the IRT. Section 3 of the report contains its recommendations: *3 Recommendations * Since the SSAC began the work that became this report the ICANN Board and ICANN Community have continued to discuss the outcomes of the IRT and Urgent Requests. [17,18] This topic is currently in active discussion. Thus, rather than provide recommendations directed to the ICANN Board, or the specific group implementing Registration Data Request Service (RDRS), this report provides recommendations on the eventual outcome of these deliberations. The SSAC hopes that the recommendations below will be taken into consideration by all groups working on policies for handling Urgent Requests. *Recommendation 1*: The policy must provide additional structure so that Urgent Requests will be handled in an appropriately expedited fashion. Specifically, the SSAC recommends that the required structure must include at least the following elements: a. Registrar's and Registry Operator's published mechanism and process must state that Reasonable Requests for Lawful Disclosure and Urgent Requests for Lawful Disclosure are different, and must allow Urgent Requests to be identified as such by a requestor. b. When a requestor submits an Urgent Request, Registrar and Registry Operator must provide an acknowledgment of receipt within 30 minutes. This acknowledgment is separate from the "response" to the disclosure request described in paragraph 10.7. c. Paragraph 10.7.2 must specify that Response to all Disclosure Requests must be in writing by email to the requestor. A written response is necessary for the information of the Requestor, and for compliance purposes. The requirement for written responses is not intended to prohibit other communication from occurring (e.g., if ongoing telephonic communication is conducted in parallel to the writing of the email response), so long as the written response is also provided. *Recommendation 2*: The policy must ensure that response time for handling Urgent Requests be fit for purpose. Specifically, the SSAC recommends that the required response time must have at least the following characteristics: a. Urgent Requests are a matter of imminent danger. The language of the policy should reflect that responses are to be fulfilled as soon as possible, with urgency befitting the situation. b. Paragraphs 10.6.1 and 10.6.2 provide time extensions that are not fit for purpose, and these paragraphs should be deleted. No legitimate Urgent Request should be responded to in more than 24 hours. c. In paragraph 10.6, the word "generally" is imprecise and confusing and should be deleted. *Recommendation 3*: ICANN org should acquire and document datar egarding Urgent Requests and make high-level information available to the community for future consideration. Specifically, the SSAC recommends the data made available to the community must include at least the following metrics a. Number of Urgent Requests received at registrars and registry operators; b. Expediency with which Urgent Requests were reviewed, evaluated, and handled; c. Percentage of Urgent Requests classified as spam, not urgent, or otherwise invalid; and d. Counts of requests handled and not handled within the contractual requirements (i.e., compliance statistics). The data collected must be comprehensive enough for ICANN org to examine a registrar or registry operator’ Shandling of Urgent Requests for compliance purposes. [17] See Letter from Tripti Sinha to Gregory DiBiase, November 13 2023, https://gnso.icann.org/sites/default/files/policy/2023/correspondence/sinha… [18] See GAC ICANN78 Hamburg Communique, https://gac.icann.org/contentMigrated/icann78-hamburg-communique As you can see, these recommendations speak to the substance of the matter. This report does not address the process that led to the incomplete specification of a policy. I expect there will be some separate conversations on that score. I also look forward to working with you to bring the same message to the appropriate Org managers. Cheers and best wishes for the new year. Steve P.S. Note that as of the beginning of this month Ram Mohan is now chair of SSAC and Tara Whalen is vice chair. Jim Galvin continues as SSAC's liaison to the board. ---------- Forwarded message --------- From: Danielle Rutherford <danielle.rutherford(a)icann.org> Date: Wed, Dec 20, 2023 at 2:35 PM Subject: [SSAC] The SSAC has published SAC122 and SAC123 To: SSAC - Full List <ssac(a)icann.org> Dear SSAC Members, The SSAC has published SAC122: SSAC Report on Urgent Requests in the gTLD Registration Data Policy < https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committe… > Thanks, Danielle

4 3

Re: [IRT.RegDataPolicy] Documenting Urgent Requests
by Steve Crocker 13 Dec '23

13 Dec '23

Dennis and Marika, Any progress on this? I want to document the sequence of actions and decisions regarding Urgent Requests from the introduction of the requirement in the Phase I EPDP to the recent removal of the requirement. Thanks, Steve On Sun, Nov 5, 2023 at 3:50 PM Steve Crocker <steve(a)shinkuro.com> wrote: > Dennis and Marika, > > Can you put together a succinct summary and timeline on the introduction, > discussions, decisions and resolution of Urgent Requests? > > Thanks, > > Steve > >

2 4

Registration Data Policy Publication plan
by Dennis Chang 29 Nov '23

29 Nov '23

Dear IRT, Thank you for the excellent support at the ICANN78 for Registration Data Policy. I was glad to see both RrSG and RySG sessions included Registration Data Policy implementation on the agenda and the proactive education and call to action happening prior to the publication of the policy. The ICANN78 IRT session<https://icann78.sched.com/event/1T4Mj/gnso-registration-data-policy-irt> was very productive and served as a critical meeting getting us aligned in providing all of our support to the new approach to the policy publication. I am speaking, of course, of the publication excluding Urgent Requests. This, as I am reminded, was an approach we had discussed a long ago but became an approach of choice with the GAC’s letter to the Board. We all know just how difficult it was for us to come up with the policy language requirement balancing the need for timely disclosure with the practical business realities at hand. With the IRT support, you’ve seen that Seb wrote his letter to the GNSO Council documenting the IRT’s agreement and asking the GNSO Council to take up the Urgent Request issue. We were well supported at the IRT session by Becky’s attendance to clarify the Board’s understanding of the difficult issue and the thinking that publication should proceed without the sections pertaining to Urgent Requests. At the moment, ICANN org is coordinating with the Board to receive formal direction to proceed with publication of the policy. Once that direction is received, we’d be able to fill in the effective dates in Section 4 of the policy. As promised, we will maintain the full 18-month implementation period with the 6+12 concept we had agreed to. I am providing a copy of the policy with tbd dates<https://community.icann.org/display/RDPIRT/RegDataPolicy+Implementation+Res…> for now so that you can clearly see the changes reflecting the removal of the Urgent Request definition and response time requirement. One more thing - you’ll note an addition in Section 9.2.4 where we are adding a reference to 9.2.2.4. This is meant to correct a reference that had been left off inadvertently. Our next step will be to inform the IRT when we have direction from the Board and dates and come back to you with the final clean policy document ready for publication. I’d like to take this time to announce that Thomas Rickert has replaced Sebestian Ducos as our GNSO Liaison going forward. Please join me in thanking Seb for his fantastic support throughout and until the last minute writing that important email to the GNSO Council <https://mm.icann.org/pipermail/irt.regdatapolicy/2023-October/001058.html> for us. You might be interested to know that Seb thought it was finally the right time and the two of us conducted a jumping high-five after our meeting. I do think it’s about time we enjoy a milestone victory after all these years. As always, thank you so much for hanging in there and supporting this policy implementation until the end. -- Gratefully yours, Dennis S. Chang GDD Programs Director Phone: +1 213 293 7889 Sykpe: dennisSchang www.icann.org<http://www.icann.org> One World – One Internet

3 3

Registration Data Policy Implementation Review Team
by Sebastien＠registry.godaddy 26 Oct '23

26 Oct '23

Dear GNSO Council, The Registration Data Policy IRT has met today to review its position following the GAC letter<https://www.icann.org/en/system/files/correspondence/caballero-to-sinha-23a…> of 23 August 2023 and the RrSG letter<https://www.icann.org/en/system/files/correspondence/heineman-to-sinha-08se…> of 8 September 2023 offering to remove the contentious Urgent Request wording to allow for a speeding publication of the Policy. The IRT going back to the original Recommendation 18 requesting the IRT to “consider” Urgent Requests believes that in essence it has considered the topic and therefore is able to remove the wording from the final policy without requiring further input from either the GNSO Council or the ICANN Board. The IRT also notes that in the spirit of the above mentioned letters, the issue of Urgent Requests is a topic that must be resolved and asks the GNSO Council to consider it and relevantly prioritize it in its work. Kindly, Sebastien Ducos GoDaddy Registry | Senior Client Services Manager [signature_905115032] +33612284445 France & Australia sebastien(a)registry.godaddy<mailto:sebastien@registry.godaddy>

1 0

Re: [IRT.RegDataPolicy] ICANN78 IRT Session Agenda
by Thomas Rickert | rickert.law 22 Oct '23

22 Oct '23

Hi Dennis, all, this overlaps with the Council Wrap Up, so I have to send my apology. Best, Thomas Von: "IRT.RegDataPolicy" <irt.regdatapolicy-bounces(a)icann.org> im Auftrag von "Dennis Chang via IRT.RegDataPolicy" <irt.regdatapolicy(a)icann.org> Antworten an: Dennis Chang <dennis.chang(a)icann.org> Datum: Samstag, 21. Oktober 2023 um 15:09 An: "Steve Crocker via IRT.RegDataPolicy" <irt.regdatapolicy(a)icann.org> Betreff: [IRT.RegDataPolicy] ICANN78 IRT Session Agenda Dear IRT, I hope you can all join us at our meeting on Thursday. You should have received a reminder invite from Andrea by now. Our Agenda for the meeting is on the two topics. 1. Urgent Request 2. Implementation Timeline Earlier today the Board discussed our policy publication and the urgent request requirement. While this topic is still under consideration, they supported the idea of having the IRT discuss an option for proceeding with the publication to begin the implementation without the Urgent Request requirement in it for now. The Urgent Request is an important topic in RDRS and Privacy Proxy as well and the thought now is that this needs to be a topic that needs to be treated in a more wholistic way which will take time. Let’s discuss this approach and share our thoughts so that we can share with the board. For the implementation timeline, I expect that we’d need to update our effectivity dates in Section 4 of the policy. Let’s discuss this also. Looking forward to seeing you on Thursday. Please note that this is an ICANN meeting IRT session and therefore open to the public. -- 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

2 1

ICANN78 IRT Session Agenda
by Dennis Chang 21 Oct '23

21 Oct '23

Dear IRT, I hope you can all join us at our meeting on Thursday. You should have received a reminder invite from Andrea by now. Our Agenda for the meeting is on the two topics. 1. Urgent Request 2. Implementation Timeline Earlier today the Board discussed our policy publication and the urgent request requirement. While this topic is still under consideration, they supported the idea of having the IRT discuss an option for proceeding with the publication to begin the implementation without the Urgent Request requirement in it for now. The Urgent Request is an important topic in RDRS and Privacy Proxy as well and the thought now is that this needs to be a topic that needs to be treated in a more wholistic way which will take time. Let’s discuss this approach and share our thoughts so that we can share with the board. For the implementation timeline, I expect that we’d need to update our effectivity dates in Section 4 of the policy. Let’s discuss this also. Looking forward to seeing you on Thursday. Please note that this is an ICANN meeting IRT session and therefore open to the public. -- 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

2 1