[IRT.RegDataPolicy] Rec 28 - Implementation date - call for IRT comment completion

[Roger D Carney]

+1, communicate to the council

From: IRT.RegDataPolicy <irt.regdatapolicy-bounces at icann.org> On Behalf Of Sarah Wyld
Sent: Friday, September 27, 2019 9:56 AM
To: irt.regdatapolicy at icann.org
Subject: Re: [IRT.RegDataPolicy] Rec 28 - Implementation date - call for IRT comment completion

Notice: This email is from an external sender.



Hello team,

It does seem to me that the IRT feels we can already rule out the original deadline, and that this should be communicated to the Council.



Thanks,

--

Sarah Wyld

Domains Product Team

Tucows

+1.416 535 0123 Ext. 1392




On 9/26/2019 8:59 PM, Dennis Chang wrote:
Thanks IRT for many good comments on the date.

Has the IRT answered Ruben in his earlier email?
“if the group feels we can already rule out the original deadline, I can relay that to the Council. Just let me know.

Ruben,
Let us know if we could assist you in your message to the Council.

Thanks
Dennis Chang

From: "IRT.RegDataPolicy" <irt.regdatapolicy-bounces at icann.org><mailto:irt.regdatapolicy-bounces at icann.org> on behalf of Jody Kolker <jkolker at godaddy.com><mailto:jkolker at godaddy.com>
Date: Wednesday, September 25, 2019 at 1:10 PM
To: "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 28 - Implementation date - call for IRT comment completion



From: IRT.RegDataPolicy <irt.regdatapolicy-bounces at icann.org><mailto:irt.regdatapolicy-bounces at icann.org> On Behalf Of Rubens Kuhl
Sent: Wednesday, September 25, 2019 2:38 PM
To: irt.regdatapolicy at icann.org<mailto:irt.regdatapolicy at icann.org>
Subject: Re: [IRT.RegDataPolicy] Rec 28 - Implementation date - call for IRT comment completion

Notice: This email is from an external sender.






Em 25 de set de 2019, à(s) 09:42:000, Luc SEUFER <lseufer at dclgroup.eu<mailto:lseufer at dclgroup.eu>> escreveu:

Hello Marc et alia,

I also believe that we should inform the Counsel that the original date cannot be met.

Regarding the incentive, as much I like ICANN waiving its fees (or offering us free t-shirts),

I haven't suggested fee incentives because they are prone to be anti-competitive (per DUM favours registrars with many DUMs, per accreditation favours drop catch registrars) and trigger endless conversations about budgeting.




I trust there will be too many unknowns here. Even after its finalization, the policy will be so far reaching that there will be some side effects we won’t have expected. Plus, speaking as a registrar, we will be dependent on the registries’ implementation.

Different from thick WHOIS where registrars simply proxied requests, the world of EPDP and RDAP brought data primacy to registrars. So most registrars won't depend on registries.

Please don’t forget that if the number of contacts or the type of contacts that are required to register a domain or the amount of information that is required to create a contact at a registry is changed, it will result in significant changes for both registrars and registrys.

Rubens

Jody



_______________________________________________

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/20190927/e2ec0e77/attachment.html>