August 2022 - IRT.RegDataPolicy

RDAP Profile for public comment
by Anderson, Marc 12 Aug '22

12 Aug '22

Dennis and the Registration Data Policy IRT, On behalf of myself and Roger Carney as the registry and registrar liaisons between the RDAP working group and the Registration Data Policy IRT, I am forwarding you an email from Rick Wilhelm, chair of the RDAP working group containing links to the public comment ready google document versions of the RDAP Response Profile and RDAP Technical Implementation Guide which together make up the RDAP profile. Also attached to this email are the PDF versions. We would like to recognize the work of all RDAP members who participated in the drafting of this updated RDAP profile, particularly Rick Wilhelm who as chair had the task of shepherding the entire process. Thank you, Marc Anderson From: Rick Wilhelm <Rwilhelm(a)PIR.org<mailto:Rwilhelm@PIR.org>> Sent: Friday, August 12, 2022 5:01 PM To: Roger Carney <rcarney(a)godaddy.com<mailto:rcarney@godaddy.com>>; Anderson, Marc <mcanderson(a)verisign.com<mailto:mcanderson@verisign.com>> Cc: rdap-pilot-wg(a)googlegroups.com<mailto:rdap-pilot-wg@googlegroups.com> Subject: [EXTERNAL] Profile docs for public comment Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Roger/Marc, Consistent with prior discussions on the RDAP WG mailing list and in-meeting discussion, on behalf of the RDAP Working Group, please find the updated gTLD RDAP Profile documents: the Technical Implementation Guide (TIG) and the Response Profile (RP). They are being provided for public comment. These documents include updates that reflect changes required due to the implementation of the ePDP Phase 2a Policy Recommendations, represent the consensus of the RDAP Working Group, and have been accomplished via a collaborative process. I'm providing two googledoc links, but also, for reference, I am attaching two PDF files that I rendered just now to provide a snapshot in case there are questions about versioning that emerge in the future. In the googledocs, I kept certain comments that identify spots where the doc requires an editorial update (by ICANN) to fix certain links. * RP: https://docs.google.com/document/d/19Hlt-_oID4pb7Pm-Epn4Kfm4PWTxVcpLlb61c34… * TIG: https://docs.google.com/document/d/1T9octf2lghuebyPrQ5VJkNgEyWlKmzWQP37-j0Q… Please note that I have made these googledoc links "comment-only" in order to maintain document integrity. If the IRT identifies issues with the docs that require updates before going to Public Comment, the RDAP WG would do its best to promptly accommodate. The RDAP Working Group looks forward to addressing public comments related to the RDAP Profile Documents and expects, after the Public Comment period, to issue an updated set of documents that reflect both public comments and editorial/implementation issues raised by participants during the processing of Public Comments. Additionally, the RDAP Working Group looks forward to supporting the IRT on technical matters related to RDAP. Many thanks to the members of the RDAP Working Group for their consistent, sustained effort to reach this milestone. Questions welcome... Rick

1 0

IRT Task 228 Review OneDoc Section 9.1.7 - 9.1.9: Registry Operator MUST publish Name Server IP Address ... 20220815
by Dennis Chang 09 Aug '22

09 Aug '22

Dear IRT, Please review. 228 Review OneDoc Section 9.1.7 - 9.1.9: Registry Operator MUST publish Name Server IP Address ... <https://docs.google.com/document/d/1SVFkoI6RmrVVz--RrVLSOj1bmz1qLb7_JTuvt7A…> 20220815 Your see from the rationales provided in Gustavo’s comment that 1. There is no change for Registrars 2. There is no change for Registrars or Registry Operators for the Reseller Data Element 3. There is a change to this policy language requirement for the Registry Operator for the Name Server IP Address data element, however … * It’s not a change to the current mode of operation * It’s not a change for requirements specified by RA * It’s not a change to the currently effective RDAP profile requirement (this is requirement not expected to change with the new update) * It’s a change to the policy language to avoid an unintended change This error in our policy language was uncovered by the careful and through review while working the RDAP profile document updates. Again, a good example of an excellent team work and synergy among the teams involved. -- 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

IRT Task 227 Review OneDoc Section 10.2 suggested language revision for clarity: Disclosure Request format 20220815
by Dennis Chang 09 Aug '22

09 Aug '22

Dear IRT, While we wait for the draft RDAP Profile, I’d like to ask for a quick review of the rewording for Section 10.2. 227 Review OneDoc Section 10.2 suggested language revision for clarity: Disclosure Request format<https://docs.google.com/document/d/1SVFkoI6RmrVVz--RrVLSOj1bmz1qLb7_JTuvt7A…> 20220815 No requirements change here but better wording thanks to Sarah. -- 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

Re: [IRT.RegDataPolicy] [Ntfy-IRT.RegDataPolicy] Meeting Invitation: Registration DataPolicy Implementation - IRT Meeting | Wednesday, 17 August 2022 at 17:00 UTC
by Sarah Wyld 08 Aug '22

08 Aug '22

Hello IRT Leadership Team, It’s very disruptive when a biweekly meeting is moved by one week. I schedule other work in the same timeslot on the opposite weeks of our meeting, and so when this IRT moves by one week I always need to reschedule at least one other meeting if not more. I understand that we are very close to wrapping up and there are not that many more meetings ahead of us in this team, but hopefully you will take this feedback into consideration for the future and for other recurring meetings. Thank you, -- Sarah Wyld, CIPP/E Policy & Privacy Manager Pronouns: she/they swyld(a)tucows.com From: Andrea Glandon via Ntfy-IRT.RegDataPolicy Sent: August 8, 2022 1:04 PM To: ntfy-irt.regdatapolicy(a)icann.org Subject: [Ntfy-IRT.RegDataPolicy] Meeting Invitation: Registration DataPolicy Implementation - IRT Meeting | Wednesday, 17 August 2022 at 17:00 UTC Dear all, The next Registration Data Policy Implementation IRT meeting has been scheduled for Wednesday, 17 August 2022 at 17:00 UTC. 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 Visit the Wiki agenda page: https://community.icann.org/x/ogVpD 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 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 Kind Regards, Andrea

2 1

IRT Task 226 Review OneDoc Public Comment prep changes including tagging for Implementation Notes and Drafting Errors due 20220805
by Dennis Chang 02 Aug '22

02 Aug '22

Dear IRT, Thank you for completing your tasks; 225 tasks to date! This is a tremendous amount of work both in scope and complexity. Since we’ve completed the requirements definition work, the rest of the work is likely to be simpler. We’ll find out if we face unexpected requirements interpretation challenges with public comment, so better sooner than later with our public comment. It’s been six (6) months since the last project scope changes (Rec 12) so we should be ready by now. I hear that RDAP WG is meeting again this Thursday and we hope to have the draft profiles soon after that just in time for an IRT review and open the public comment as promised. I hope this will be the last task on OneDoc for public comment. 226 Review OneDoc Public Comment prep changes including tagging for Implementation Notes and Drafting Errors<https://docs.google.com/document/d/1SVFkoI6RmrVVz--RrVLSOj1bmz1qLb7_JTuvt7A…> 20220805 We’ve made minor changes for clarity and readability for the reviewers as well as adding what I call “tags.” Much like the tags we had for each section to note the Recommendation Numbers to reference, we’ve added tags to those requirements and data elements to note the Drafting Errors and Implementation Interpretation. We’ve also added tags to the Implementation Notes below within the document where examples and further clarity are provided. At the moment, we plan to remove these tags for the final policy publication and keep them as part of the Educational Material we’ll prepare for the implementers. Let’s discuss this further after public comment. Our next meeting is 3 August 2022; we’ll focus on OneDoc. The meeting after that is on 10 August 2022 to review draft RDAP Profiles. We try to space out the meetings by at least a couple of weeks but this scheduling is needed for us to be on the public comment schedule. Thank you again for your great support to the significant policy implementation project. -- 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