While working on implementing the methods defined by ballot 169, we noticed a lot of inconsistencies in the language and process. This made some of the methods confusing, especially on how they applied to reuse of information and verification of subdomains/wildcards. Attached is a proposal that we think clarifies the process and tightens up the language.
A couple of notes: 1. The proposal doesn't intend to substantially change any of the methods. However, this is DigiCert's interpretation of the requirements. Given the previous language, disagreement on the interpretation is likely and will highlight the need for a clarifying ballot. 2. This method doesn't necessarily replace 190. If longer discussion is needed (because there are lots of changes), then this could be a subsequent revision to the validation methods and include more stringent controls (like reverifying WHOIS information within 30 days and restricting sub-domain methods). For now, I tried to keep the process and reuse the same. 3. The proposal separates out sub domain reuse, reuse of documentation, and splits the longer methods into discrete steps. There are lots of redundant sections. This is intentional. The goal is to (eventually) talk about each method discretely and decide what requirements are tied to document reuse and sub-domain validation. Look forward to your comments. Jeremy
Domain Validation - revised.docx
Description: MS-Word 2007 document
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Public mailing list [email protected] https://cabforum.org/mailman/listinfo/public
