[IRT.RegDataPolicy] Rec 10 consideration: error in recommendation to be corrected? or proceed with implementing the recommendation as is.

Tue Sep 3 14:43:27 UTC 2019

Dennis, IRT and IPT teams,

I also agree with Sarah.  For the Registrar is should be required to publish the “Registrar registration expiration date” and optional to publish the “registry expiry date” as is existing behavior.  At no point during the phase one deliberations was changing this contemplated.  This seems to be a simple drafting error that was missed.

Best,

Marc

From: IRT.RegDataPolicy <irt.regdatapolicy-bounces at icann.org> On Behalf Of Dennis Chang
Sent: Monday, September 2, 2019 6:16 PM
To: Eric Rokobauer <eric.rokobauer at endurance.com>; theo geurts <gtheo at xs4all.nl>
Cc: irt.regdatapolicy at icann.org
Subject: [EXTERNAL] Re: [IRT.RegDataPolicy] Rec 10 consideration: error in recommendation to be corrected? or proceed with implementing the recommendation as is.

Dear IRT,

So far, I counted 3 IRT members agreeing that we should treat the “expiration date” requirement as an error in the final report that we MUST correct in the implementation.  Please do reply with your agreement or disagreement.  It’s important that all IRT members are aware that our implementation is inconsistent with the recommendation language.

We will be sure to highlight this in the public comment with the support of the IRT.

Also, please note that an Approach #3 Alternative language for the Publication needs your review.

https://docs.google.com/document/d/1OuZT7xL5wuV1ynVmpVNxFycU93gvPlvbzx_g9lXCYCw/edit

We’ve made the language more concise while still providing for option for Registrars and Registries regarding the expiration dates and reseller.

We’ll go over the Field-Key-Value concept at the IRT meeting as I’ve gathered that the confusion may have stemmed from our lack of consistent understanding,

Thanks for your continued support of the RegDataPolicy implementation.

Dennis Chang

From: "IRT.RegDataPolicy" <irt.regdatapolicy-bounces at icann.org<mailto:irt.regdatapolicy-bounces at icann.org>> on behalf of Eric Rokobauer <eric.rokobauer at endurance.com<mailto:eric.rokobauer at endurance.com>>
Date: Monday, August 26, 2019 at 12:40 PM
To: theo geurts <gtheo at xs4all.nl<mailto:gtheo at xs4all.nl>>
Cc: "irt.regdatapolicy at icann.org<mailto:irt.regdatapolicy at icann.org>" <irt.regdatapolicy at icann.org<mailto:irt.regdatapolicy at icann.org>>
Subject: Re: [IRT.RegDataPolicy] Rec 10 consideration: error in recommendation to be corrected? or proceed with implementing the recommendation as is.

+1 Sarah's comments

On Mon, Aug 26, 2019 at 3:14 PM theo geurts <gtheo at xs4all.nl<mailto:gtheo at xs4all.nl>> wrote:

   +1 Sarah.

   Theo

   On 26-8-2019 20:48, Sarah Wyld wrote:

      Hi Dennis,

      Yes, this appears to be a drafting error.

      We should maintain the status quo in this area; the registry must publish the registry expiry date, and the registrar must publish the registrar registration expiration date.

      Thanks,

      --
      Sarah Wyld
      Domains Product Team
      Tucows
      +1.416 535 0123 Ext. 1392

      On 8/21/2019 8:23 PM, Dennis Chang wrote:

         Dear IRT,

         Thanks for supporting the IRT call today.

         Regarding the Recommendation 10, there was a suggestion that we have a table.

         I wanted to show you this IRT.Data Elements Matrix today but unfortunately my computer quit on me.

         https://docs.google.com/spreadsheets/d/1c235iuKWX5-lKufkR67pPF0OEf-Fw3W94WPepCx4ep8/edit#gid=1382512791

         As you may recall, this matrix is referenced in the IRT.Rec 10 Analysis document but may not have not been used the IRT in the analysis.

         https://docs.google.com/document/d/1OuZT7xL5wuV1ynVmpVNxFycU93gvPlvbzx_g9lXCYCw/edit#<https://docs.google.com/document/d/1OuZT7xL5wuV1ynVmpVNxFycU93gvPlvbzx_g9lXCYCw/edit>

         I believe the IRT.Data Elements Matrix already offers the table you are wanting.

         I draw your attention to the Registrar sheet cell 8X and 9X where we’ve flag these for IRT attention.

         We are making it clear here that what’s reflected is aligned with the recommendation and we are now considering changing this to be “inconsistent with the recommendation” due to an error in the recommendation language.

         We, as the implementation team, can deviate from the recommendation if we all agree that we are correcting an obvious error and not changing the policy.

         Lack of an IRT agreement is likely to default in the implementation language true to the recommendation language at least for the public comment.

         The way the recommendation reads now is Registry Expiry Date MUST be published by both Registrar and Registry Operators according to the recommendation, while Registrar Registration Expiration Date MAY be published

         I submit this for IRT consideration and proceeding with caution as not to rush an important implementaiton decision.

         —

         Kind Regards,

         Dennis S. Chang

         GDD Services & Engagement Program Director

         Telephone: +1 213 293 7889

         Skype: dennisSchang

         www.icann.org<http://www.icann.org>

         _______________________________________________
         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.

      _______________________________________________
      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.

   _______________________________________________
   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: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20190903/cc808f73/attachment.html>