[IRT.RegDataPolicy] FYI: Phase 2 Policy to OneDoc mapping exercise.
Anderson, Marc
mcanderson at verisign.com
Wed Aug 12 14:33:19 UTC 2020
Alex, thank you for providing this. Obviously a lot of time and effort went into this document. You do a really good job of accounting for all aspects of the phase 1 policy recommendations and linking them to sections in the One Doc. I hope we (IPT/IRT) can leverage this as a tool to make sure everything in the phase 1 policy recommendations are accounted for and that the draft policy language that goes out for public comment is consistent with those policy recommendations. As you point out, this highlights a number of areas that need work before the One Doc can be ready for public comment.
You make a great point about the DPA/DPTs. I know that work is going on via a separate process but it directly impacts the policy. As you say that work really is foundational for the policy itself and in some cases required to fulfill recommendations.
Best,
Marc
From: IRT.RegDataPolicy <irt.regdatapolicy-bounces at icann.org> On Behalf Of Alex Deacon
Sent: Tuesday, August 11, 2020 6:41 PM
To: irt.regdatapolicy at icann.org
Subject: [EXTERNAL] [IRT.RegDataPolicy] FYI: Phase 2 Policy to OneDoc mapping exercise.
IRT colleagues,
As I mentioned in my previous email I have spent some time analyzing the Phase 1 Policy and the current One Doc (actually a version from August 3rd). My goal was to ensure we didn't miss anything and also to assess where we were in the process.
See the Google Drive link below with the results of this analysis.
•• Green means things look good.
•• Red means OneDoc language is either missing or wrong or not consistent with the final report language.
•• Yellow means that recommendation language will (should) end up in a DPA/DPT.
While you review this keep the following in mind.
* I've tried to keep this analysis neutral, but you will see a few (not many!) actually indicate a divergence in opinion between IRT members. I've put that info in square brackets.
* I skipped Rec 7 analysis as I didn't have the write up from Sebastien. This can be updated once everyone has a chance to review. (which I plan to do this afternoon).
My major takeaways from this work is
* There is way too much red and yellow for my liking, especially given we have been working on this for eons. (it seems like eons at least). For some perspective, remember that the IRT has been working on IRT language longer than the EPDP Phase 1 team took to draft and deliver the final report.
* The DPA/DPT work is foundational to policy as a whole and without them it is impossible to assess if the work of the IRT is in fact complete.
Anyway - my goal in doing this was to prepare for an eventual "last call" review of the OneDoc. However I thought I would share it with the team in the hopes it is helpful to everyone and enables us to complete our task with some common understanding and efficiency.
I've uploaded the file into Google Drive and everyone with the link can view and add comments. If others feel this is useful I can update the permissions to allow anyone to edit the doc also.
https://drive.google.com/file/d/1f4zOnP1LXOJXgg1RxUSXYCFUHcqfhyWq/view?usp=sharing
Thanks!!
Alex
___________
Alex Deacon
Cole Valley Consulting
alex at colevalleyconsulting.com<mailto:alex at colevalleyconsulting.com>
+1.415.488.6009
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20200812/3163590e/attachment.html>
More information about the IRT.RegDataPolicy
mailing list