[IRT.RegDataPolicy] [Ext] Re: IRT Task 184 Review RedDoc for Thick WHOIS Transition Policy for .COM, .NET and .JOBS 20220131

[Dennis Chang]

Alex,

Excellent question and input.
I agree with you.  I don’t believe that we, the implementation team, has the authority to make any policy obsolete.
There has been a lot of thought on the statement made in the News Box so that we stay within our remit.

For the IRT review, I wanted to make clear what I believe is the result of our implementation even though we do not use the world “obsolete” and the policy continues to stay in effect with contractual compliance on-hold.

In any case, we’ll discuss what we will recommend to GNSO/Board later but the job of the IRT now is to review the language in the News Box and see if it is clear and aligns with the recommendations.   i.e. Is the impact of the Registration Data Policy properly reflected on the Transition Policy with this RedDoc?

Thanks
Dennis Chang

From: Alex Deacon <alex at colevalleyconsulting.com>
Date: Monday, January 17, 2022 at 12:16
To: Dennis Chang <dennis.chang at icann.org>
Cc: "Alex Deacon via IRT.RegDataPolicy" <irt.regdatapolicy at icann.org>
Subject: [Ext] Re: [IRT.RegDataPolicy] IRT Task 184 Review RedDoc for Thick WHOIS Transition Policy for .COM, .NET and .JOBS 20220131

Dennis,

Quick process question - does the IPT (icann org)  or IRT (random members of the community) have the ability to make or declare a consensus policy obsolete?

Sounds to me like a job for the GNSO council and/or ICANN Board.

Alex

___________
Alex Deacon
Cole Valley Consulting
alex at colevalleyconsulting.com<mailto:alex at colevalleyconsulting.com>
+1.415.488.6009



On Sun, Jan 16, 2022 at 8:45 PM Dennis Chang via IRT.RegDataPolicy <irt.regdatapolicy at icann.org<mailto:irt.regdatapolicy at icann.org>> wrote:
Dear IRT,

Please review and comment on the RedDoc for the Transition Policy.
184

Review RedDoc for Thick WHOIS Transition Policy for .COM, .NET and .JOBS [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1BjPomDc-vRmyRorzoRtRs8qQzrn_1ZeU/edit__;!!PtGJab4!t-94uSjsKF8O5RBDgwXrUzHVIu93z5Ggt92DEguS4xwqWVZlSUOH3hpKf2_b_QlK1ijyF9aP$>

20220131

This is an interesting case where we are effectively making this policy obsolete because we believe all requirements for registration data in this policy for the three gTLDs are already covered in our policy.
We’ll add this to one of our February IRT meeting agenda for a detail discussion.

--
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
_______________________________________________
IRT.RegDataPolicy mailing list
IRT.RegDataPolicy at icann.org<mailto:IRT.RegDataPolicy at icann.org>
https://mm.icann.org/mailman/listinfo/irt.regdatapolicy

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20220118/76232aa5/attachment-0001.html>