March 2024 - IRT.RegDataPolicy

IRT Task 251: Review draft advisory to Registry Operator for Escrowing Registrar Abuse Contacts. Due 20240410
by Dennis Chang 15 Apr '24

15 Apr '24

Dear IRT, Thank you for supporting the IRT call yesterday;. I had considered working this topic via emails without a meeting but saw that it was helpful to avoid confusion with other Abuse Contact discussions happening elsewhere. Thank you, Marc, for your careful evaluation and double checking with your technical team to providing the explanation as a Registry Operator for whom this advisory is intended. Steve, I know you had to drop before the end, but Marc was very kind to provide an explanation for you so that you can pick it up from the recor4ding. Following the next steps per our plan, we have drafted an Advisory for your review. 251 Review Draft Advisory to Registry Operators for Escrowing Registrar Abuse Contacts<https://docs.google.com/document/d/1J_QbE-Gkuywn6OSOJkbjkBR-o86bRfV7kX7iuVJ…> 20240410 Please review and comment directly on the document. As we discussed, this Advisory is an instruction to the Registry Operators to use the two data elements already available to meet the Registration Data Policy requirement in a consistent way. This is an implementation effort collaborating on how we meet the requirement; not making or changing requirements. An example of an implementation that the IRT asked me to bring to you for awareness instead of working directly with Registry Operators only. I am providing the slides we used at the meeting that contains that explanation for your convenience there. 249 Registry Escrow for Registrar Abuse Contacts <https://community.icann.org/display/RDPIRT/RegDataPolicy+Implementation+Res…> 20240326 Please share this with your technical implementation team and I think you’ll find them most receptive as a straight forward and clear implementation approach. When the Advisory is ready, it will be added to the list of Advisories here following our process. https://www.icann.org/resources/pages/advisories-2012-02-25-en Please feel free to reach out to me off-line too if you’d like further explanation or discussion. I’d be happy to support your call with your technical teams too if you’d like. One month in and five months to go till our Transition start date: 21 August 2024. Thanks you for your support to make this implementation a success for all. … 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 4

Post Call | Registration Data Policy IRT | Wednesday, 27 March 2024
by Andrea Glandon 27 Mar '24

27 Mar '24

Dear all, All recordings for the Registration Data Policy IRT call held on Wednesday, 27 March 2024 at 16:30 UTC can be found on the agenda wiki page <https://community.icann.org/x/NQAIEw> (attendance included). These include: * Attendance (please let me know if your name has been left off the attendance list) * Audio recording * Zoom recording (including audio, visual, rough transcript) * Transcript For additional information, you may consult the mailing list archives <https://mm.icann.org/pipermail/irt.regdatapolicy/> and the main wiki page<https://community.icann.org/x/hpaGBg>. **Reminder: Only IRT members are allowed to join the live IRT meetings. If you would like to join the meetings in the future, please sign up to be a member of the IRT Thank you. Kind regards, Andrea

1 0

IRT Task 250: Public Comment for RST 2.0
by Dennis Chang 27 Mar '24

27 Mar '24

Dear IRT, Please note that the Public Comment proceeding for the Registry System Testing 2.0 Test Specifications and API. 250 https://www.icann.org/en/public-comment/proceeding/review-of-the-registry-s… 20240506 * ICANN org is seeking feedback from the technical community on the proposed test specifications and API for Version 2.0 of the Registry System Testing (RST 2.0) service. * RST v2.0 is a major improvement over the original Registry System Testing framework. It is more comprehensive and thoroughly documented and provides a fully automated workflow with no human involvement in the testing process. * Test cases of RST 2.0 support the latest consensus policies (e.g., the Registration Data Policy) and technical standards. Please inform your technical teams to review and provide comments for the RST 2.0 following the instructions provided on the Public Comment preceding page. As you know, our IRT meeting today will be on the Registry Operator Escrow for Registrar Abuse Contacts but if we have time left, we could discuss this also if you wish. -- 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 1

IRT Task 249: Registry Escrow for Registrar Abuse Contact Email and Phone
by Dennis Chang 25 Mar '24

25 Mar '24

Dear IRT, Here it is. #249 IRT Task. This should provide more info on what I was referring to in my earlier email below. Please review to prepare to discuss at the next IRT meeting. 249 Registry Escrow for Registrar Abuse Contacts <https://community.icann.org/display/RDPIRT/RegDataPolicy+Implementation+Res…> 20240326 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, March 18, 2024 at 2:45 PM To: "Dennis Chang via IRT.RegDataPolicy" <irt.regdatapolicy(a)icann.org> Subject: [IRT.RegDataPolicy] IRT Meeting on 27 March Agenda: Registry Escrow for Registrar Abuse Contact Email and Phone Dear IRT, How’s everyone post-ICANN79? It was nice seeing you in person in Puerto Rico, As you’ve advised, we will keep the IRT meetings going for policy related items and implementation details that warrants broader awareness. For the next meeting, we have one topic regarding Registry Escrow for Registrar Abuse Contacts. * Registry Data Policy Section 8.4 covers what Registry Operator MUST submit to escrow agent. . . . 8.4.8 Registrar Abuse Contact Email 8.4.9 Registrar Abuse Contact Phone We’ like to discuss with the IRT on how we propose to handle these two data items in a consistent clear way for implementation. We are putting together a few slides to provide the information in advance of the meeting and will discuss the details and answer questions at the meeting. I’ll be following up with the slide deck this week but wanted to first let you know what the meeting will be about. Stay tuned, -- 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

3 2

IRT Meeting on 27 March Agenda: Registry Escrow for Registrar Abuse Contact Email and Phone
by Dennis Chang 18 Mar '24

18 Mar '24

Dear IRT, How’s everyone post-ICANN79? It was nice seeing you in person in Puerto Rico, As you’ve advised, we will keep the IRT meetings going for policy related items and implementation details that warrants broader awareness. For the next meeting, we have one topic regarding Registry Escrow for Registrar Abuse Contacts. * Registry Data Policy Section 8.4 covers what Registry Operator MUST submit to escrow agent. . . . 8.4.8 Registrar Abuse Contact Email 8.4.9 Registrar Abuse Contact Phone We’ like to discuss with the IRT on how we propose to handle these two data items in a consistent clear way for implementation. We are putting together a few slides to provide the information in advance of the meeting and will discuss the details and answer questions at the meeting. I’ll be following up with the slide deck this week but wanted to first let you know what the meeting will be about. Stay tuned, -- 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

Registration Data Policy IRT Meeting
by ICANN Policy Calendar 18 Mar '24

18 Mar '24

Meeting: Registration Data Policy Implementation IRT Date/time: Wednesday, 27 March 2024 at 16:30 UTC for 30 minutes. Join the Zoom room directly (recommended): https://icann.zoom.us/j/92324437108?pwd=WkVtbm55QlZpMzdDbXdrNHYwZW9xQT09 (no password required) Before joining the call: Please be sure you have read the Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> Visit the Wiki agenda page: https://community.icann.org/x/NQAIEw If joining Zoom via the Zoom App, the following will be required: Meeting ID: 923 2443 7108 Password: 0Q$4h1*g+r If you are joining via audio only: One tap mobile +16699006833,,92324437108#,,,,0#,,420123# US (San Jose) +12532158782,,92324437108#,,,,0#,,420123# US (Tacoma) Dial in directly with your chosen number<https://zoom.us/u/acwzlz1QoY> and provide: Meeting ID: 923 2443 7108 Password: 420123 If this is your first time with Zoom, please take a look here: Welcome to Zoom<https://gnso.icann.org/sites/default/files/policy/2020/presentation/welcome…>

1 0

Registration Data Policy IRT Meeting
by ICANN Policy Calendar 18 Mar '24

18 Mar '24

Meeting: Registration Data Policy Implementation IRT Date/time: Wednesday, 27 March 2024 at 16:30 UTC for 30 minutes. Join the Zoom room directly (recommended): https://icann.zoom.us/j/92324437108?pwd=WkVtbm55QlZpMzdDbXdrNHYwZW9xQT09 (no password required) Before joining the call: Please be sure you have read the Expected Standards of Behavior<https://www.icann.org/resources/pages/expected-standards-2016-06-28-en> Visit the Wiki agenda page: https://community.icann.org/x/NQAIEw If joining Zoom via the Zoom App, the following will be required: Meeting ID: 923 2443 7108 Password: 0Q$4h1*g+r If you are joining via audio only: One tap mobile +16699006833,,92324437108#,,,,0#,,420123# US (San Jose) +12532158782,,92324437108#,,,,0#,,420123# US (Tacoma) Dial in directly with your chosen number<https://zoom.us/u/acwzlz1QoY> and provide: Meeting ID: 923 2443 7108 Password: 420123 If this is your first time with Zoom, please take a look here: Welcome to Zoom<https://gnso.icann.org/sites/default/files/policy/2020/presentation/welcome…>

1 0