You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During review of the BRs by the Validation Subcommittee at F2F 57, focused on identifying areas where the CA issuing certificates to itself may require clarification, Section 4.1.2 caused some fair amount of discussion on an unrelated topic.
4.1.2 sets forth requirements for receiving and processing certificate requests. There is ambiguity in what this encompasses (e.g. is a CSR in itself a compliant certificate request?) and questions as to the relevance of this section today, compared to when it was first written.
Rough consensus was achieved during this discussion that the Validation Subcommittee should:
Update from using "certificate request" to a defined term, such as "Certificate Application"; and
Revise usage of "certificate request" -> "Certificate Application" to ensure clarity and relevance of associated requirements.
The text was updated successfully, but these errors were encountered:
During review of the BRs by the Validation Subcommittee at F2F 57, focused on identifying areas where the CA issuing certificates to itself may require clarification, Section 4.1.2 caused some fair amount of discussion on an unrelated topic.
4.1.2 sets forth requirements for receiving and processing certificate requests. There is ambiguity in what this encompasses (e.g. is a CSR in itself a compliant certificate request?) and questions as to the relevance of this section today, compared to when it was first written.
Rough consensus was achieved during this discussion that the Validation Subcommittee should:
The text was updated successfully, but these errors were encountered: