[IRT.RegDataPolicy] [Ext] RE: FW: IRT Task 127 Review Deletion of RDDSdefinition from OneDoc 3.6

Tue Dec 22 23:48:19 UTC 2020

Thanks Sarah and Alex for your inputs here. Thanks to the IRT members attending the meeting this week contributing this topic.
Per Alex’s request, I am noting some of the points made at the meeting on rationale for removing the definition in following Sarah’s points below.

  1.  Glossary in Final Report is not a recommendation
  2.  RDDS definition already exists in RA and RAA
  3.  RDDS definition in OneDoc refers to RA and RAA
  4.  OneDoc 3.10 says  - Terms capitalized but not defined in this Policy SHALL have the meaning given to them in the RA and RAA.
  5.  The policy language that obligates Registries and Registars belong in the main requirements section
  6.  Definition should be used to help in understanding the requirement, not become a source for debate on requirement
  7.  Removing RDDS definition in OneDoc does not limit requirement
  8.  The efforts to define RDDS is out-of-scope for this implementation
  9.  While it may have been nice to do so, it has proven to be overly time consuming and continues to be a subject of debate as cautioned by IRT members with long ICANN history. Therefore, we will proceed without a definition in OneDoc.

I added these points in the comment for deletion in OneDoc for your reference also.

Next year, we’ll review the RedDocs with this approach and determine if we need to change the way we update the document.
I wish everyone happy holidays and well deserved break.

I look forward to seeing everyone again in 2021.

Thanks
Dennis Chang

From: Sarah Wyld <swyld at tucows.com>
Date: Wednesday, December 16, 2020 at 08:44
To: Alex Deacon <alex at colevalleyconsulting.com>, Dennis Chang <dennis.chang at icann.org>, "irt.regdatapolicy at icann.org" <irt.regdatapolicy at icann.org>
Subject: [Ext] RE: [IRT.RegDataPolicy] FW: IRT Task 127 Review Deletion of RDDSdefinition from OneDoc 3.6

Hello All,

I take a different view here; I thought it made sense to remove the definition from the OneDoc and refer to existing definitions from our RA/RAA instead.

The glossary section of the Final Report was not part of the Recommendations; was the glossary voted on by the Council and Board? I thought they approved numbered recommendations only, and the glossary was provided as helpful context but is not itself policy.

Looking forward to our meeting, thanks!

--

Sarah Wyld, CIPP/E

Policy & Privacy Manager

Tucows

swyld at tucows.com<mailto:swyld at tucows.com>

+1.416 535 0123 Ext. 1392

[cid:image001.png at 01D698B1.25CB4480]

From: Alex Deacon<mailto:alex at colevalleyconsulting.com>
Sent: December 16, 2020 10:50 AM
To: Dennis Chang<mailto:dennis.chang at icann.org>; irt.regdatapolicy at icann.org<mailto:irt.regdatapolicy at icann.org>
Subject: Re: [IRT.RegDataPolicy] FW: IRT Task 127 Review Deletion of RDDSdefinition from OneDoc 3.6

Dennis,

I have to admit I am struggling to understand the logic for this decision.

Can you please explain why an IRT would not apply definitions as they are defined in the Phase 1 Final report and recommended by the PDP team, approved by the GNSO and agreed to by the ICANN board?

What grounds does the IRT have to unilaterally override such a definition (one of many I point out)?

Finally, the Community has spent years of time and effort defining and agreeing to language in a Final Report via the ICANN multistakeholder model of policy development.  Therefore, how can ICANN org now simply override those decisions?

Alex

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

On Sat, Dec 12, 2020 at 9:17 AM Dennis Chang <dennis.chang at icann.org<mailto:dennis.chang at icann.org>> wrote:
Dear IRT,

After careful study of diverse inputs over many weeks, we decided to remove the RDDS definition in OneDoc.
We will discuss this at our next iRT meeting but I wanted to alert you for your advance for your consideration.
127

Review Deletion of RDDS definition from OneDoc 3.6 [docs.google.com]<https://urldefense.com/v3/__https:/docs.google.com/document/d/1SVFkoI6RmrVVz--RrVLSOj1bmz1qLb7_JTuvt7At4Uo/edit__;!!PtGJab4!vuXY7q9fUbpbcTVtHXubZpJvL1QpHDdNnNHzxu-YuO29jjnix2mDuGf_B9TnFWIiJDvbd5Uh$>

20201215

In your review, please note definition 3.10 as it will be meaningful when 3.6 is deleted.

--
Kind Regards,
Dennis S. Chang
GDD Programs Director
Phone: +1 213 293 7889
Sykpe: dennisSchang
www.icann.org [icann.org]<https://urldefense.com/v3/__http:/www.icann.org__;!!PtGJab4!vuXY7q9fUbpbcTVtHXubZpJvL1QpHDdNnNHzxu-YuO29jjnix2mDuGf_B9TnFWIiJNgTm6V1$> 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 [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/privacy/policy__;!!PtGJab4!vuXY7q9fUbpbcTVtHXubZpJvL1QpHDdNnNHzxu-YuO29jjnix2mDuGf_B9TnFWIiJL1VDCCs$>) and the website Terms of Service (https://www.icann.org/privacy/tos [icann.org]<https://urldefense.com/v3/__https:/www.icann.org/privacy/tos__;!!PtGJab4!vuXY7q9fUbpbcTVtHXubZpJvL1QpHDdNnNHzxu-YuO29jjnix2mDuGf_B9TnFWIiJCQka1zL$>). 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: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20201222/0155da6e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3033 bytes
Desc: image001.png
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20201222/0155da6e/image001-0001.png>