[cabf_validation] Domain Contact definition

[Jeremy Rowley]

This wording could let you retrieve it from the customer’s webpage if the Registrar is also a hosting service, couldn’t it?

 

From: Peter Bowen [mailto:pzb at amzn.com] 
Sent: Friday, March 11, 2016 7:44 AM
To: Jeremy Rowley
Cc: validation at cabforum.org
Subject: Domain Contact definition

 

Jeremy,

 

Thank you for creating the Domain Contact definition and refactoring the methods to use it where appropriate. I would suggest a change, given ICANN’s presentation at the F2F on their plan to replace WHOIS with RDAP.


Domain Contact: The Domain Name Registrant, technical contact, or administrative contract (or the equivalent under a ccTLD) of the Base Domain Name as reported by a Domain Name Registrar. Such information MAY be retrieved from WHOIS servers run by Domain Name Registrars.

 

This also makes it clear the required source of the information and uses the already defined term Domain Name Registrar (which is defined in the BRs to mean both Registry and/or Registrar).

 

Thanks,

Peter

 

On Mar 10, 2016, at 9:34 PM, Jeremy Rowley <jeremy.rowley at digicert.com <mailto:jeremy.rowley at digicert.com> > wrote:

 

Here’s the updated domain validation draft based on today’s discussion (and a couple of attempts to clarify items of confusion).  I look forward to the comments.

<Domain Validation Draft (3-11-2016).docx>_______________________________________________
Validation mailing list
 <mailto:Validation at cabforum.org> Validation at cabforum.org
 <https://cabforum.org/mailman/listinfo/validation> https://cabforum.org/mailman/listinfo/validation

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://cabforum.org/pipermail/validation/attachments/20160311/0b7f5f99/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4964 bytes
Desc: not available
Url : https://cabforum.org/pipermail/validation/attachments/20160311/0b7f5f99/attachment-0001.bin