Any objections if the Spring Cleanup branch includes cleanup changes involving dates that will be true in Spring of 2019?
For example, removing the definition of Domain Authorization Document, and changing 3.2.2.4.5 to read: "3.2.2.4.5 Domain Authorization Document This method has been retired and MUST NOT be used. Completed validations using this method SHALL NOT be used for the issuance of certificates." There are similar changes that could be made in 2.2: "The Certificate Policy and/or Certification Practice Statement MUST: 1. be structured in accordance with RFC 3647, 2. include all material required by RFC 3647, 3. state the CA's policy or practice on processing CAA Records for Fully Qualified Domain Names. The CA's CAA policy or practice MUST: 1. be consistent with these Requirements, 2. clearly specify the set of Issuer Domain Names that the CA recognizes in CAA "issue" or "issuewild" records as permitting it to issue The CA SHALL log all actions taken, if any, consistent with its processing practice." Where we don't have to worry about RFC 2527 any longer. -Tim
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Public mailing list [email protected] https://cabforum.org/mailman/listinfo/public
