[IRT.RegDataPolicy] 5 Collection of Registration Data

Tue Nov 19 01:27:02 UTC 2019

Theo and Jody: you may not like offering the RNH the option to change their nameservers, but that is way out of scope for the IRT!

Sarah: I’ve considered your proposal but think that 5.2 and 5.5 are good as they stand.

Specifically, registrars MUST offer RNH the ability to provide technical details that are critical to the correct functioning of a domain name.

It's a different kettle of fish to the collection of optional contact details.

Lastly, I’d suggest that "Name Server IP Address(es)” (i.e. glue) should belong in 5.5 and NOT 5.2.

Cheers,
Benedict.

> On 16 Nov 2019, at 19:53, Theo Geurts CIPP/E <gtheo at xs4all.nl> wrote:
> 
> Agreed.
> 
> Theo
> Op 16-11-2019 om 13:45 schreef Jody Kolker:
>> Hi guys,
>> 
>> Agreed that Registrant Organization should not be classified as MUST until Rec. 12 has been resolved.
>> 
>> However, I believe it should be up to the registrar if the registrar wants to offer the registrant the ability to change nameservers or add DNSSEC elements to a domain.  I believe that it should be a business decision by the registrar to allow it.  If a RNH wants to change customize their nameservers by manually entering them and the registrar does not offer it, the RNH can transfer the domain to a registrar that does offer it.  Same for DNSSEC.
>> 
>> Thanks,
>> Jody Kolker
>> 
>> From: IRT.RegDataPolicy <irt.regdatapolicy-bounces at icann.org> <mailto:irt.regdatapolicy-bounces at icann.org> On Behalf Of Luc SEUFER
>> Sent: Thursday, November 14, 2019 10:26 AM
>> To: Sarah Wyld <swyld at tucows.com> <mailto:swyld at tucows.com>; irt.regdatapolicy at icann.org <mailto:irt.regdatapolicy at icann.org>
>> Subject: Re: [IRT.RegDataPolicy] 5 Collection of Registration Data
>> 
>> Notice: This email is from an external sender.
>> 
>> 
>> Hi Sarah,
>> 
>> I think we need some granularity here.
>> 
>> I agree that the Registrant Organization should not be classified as a MUST display, MUST collect until Rec. 12 has been resolved.
>> 
>> However, I trust that Name Server(s) and DNSSEC elements have to be classified as such to ensure the uniformity and stability of the DNS. RNH can only appoint and update their Name Server(s) via the registrar in charge of their domain registration, they cannot ask the registry operator directly. Having certain registrars displaying it and other not would result in mayhem.
>> 
>> My 2 cants,
>> 
>> Luc
>> 
>> 
>> From: "IRT.RegDataPolicy" <irt.regdatapolicy-bounces at icann.org <mailto:irt.regdatapolicy-bounces at icann.org>> on behalf of Sarah Wyld <swyld at tucows.com <mailto:swyld at tucows.com>>
>> Organisation: Tucows
>> Date: Thursday, 14 November 2019 at 16:59
>> To: "irt.regdatapolicy at icann.org <mailto:irt.regdatapolicy at icann.org>" <irt.regdatapolicy at icann.org <mailto:irt.regdatapolicy at icann.org>>
>> Subject: [IRT.RegDataPolicy] 5 Collection of Registration Data
>> 
>> Hello team,
>> 
>> I'm looking at Section 5 in the OneDoc and have an area of confusion, which I hope we can discuss either here by email or on our next call.
>> 
>> Rec 5 has data collection logic marked either required (green) or optional (yellow). The footnote 7 to Rec 5 says "7 For those data elements marked as “Optional”, these are either optional for the Registrar to offer or optional for the RNH to provide. In both cases, if data is provided, it must be processed."
>> 
>> Our OneDoc has two sections that separately and differently deal with the data elements which are all yellow in the Rec 5 text. My question is why they are different, when in the Recommendation they are the same.
>> 
>> Specifically, we have:
>> 
>> 5.2 The Registrar MAY collect values for the following data elements. If the Registered Name Holder (RNH) elects to provide the value, Registrar MUST collect it:
>> 
>> Registrant Phone ext
>> Registrant Fax
>> Registrant Fax ext
>> Tech Name
>> Tech Phone
>> Tech Email
>> Name Server IP Address(es)
>> 
>> 
>> 
>> 5.5 The Registrar MUST provide the opportunity for the RNH to provide values for the following data elements. If provided by the RNH, the Registrar MUST collect the following data element values:
>> 
>> Registrant Organization
>> Name Server(s)
>> DNSSEC Elements
>> 
>> 
>> 
>> The data elements in both these sections should be required in the same way in the Policy, like they are in the Recommendation. I would propose they should both be:
>> 
>> The Registrar MAY collect values for the following data elements. If the Registrar offers the collection of the value and the Registered Name Holder (RNH) elects to provide the value, Registrar MUST collect it:
>> 
>> 
>> 
>> Thanks,
>> 
>> 
>> 
>> --
>> Sarah Wyld
>> Domains Product Team
>> Tucows
>> +1.416 535 0123 Ext. 1392
>> 
>> 
>> 
>> 
>> _______________________________________________
>> IRT.RegDataPolicy mailing list
>> IRT.RegDataPolicy at icann.org <mailto:IRT.RegDataPolicy at icann.org>
>> https://mm.icann.org/mailman/listinfo/irt.regdatapolicy <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 <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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
> 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/20191119/29226e83/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 528 bytes
Desc: Message signed with OpenPGP
URL: <http://mm.icann.org/pipermail/irt.regdatapolicy/attachments/20191119/29226e83/signature.asc>