136
edits
Changes
→CP/CPS Structured According to RFC 3647: Reference updated policy
CP/CPS documents must be structured according to RFC 3647. This requirement is stated in section 2.2 of the CA/Browser Forum Baseline Requirements, with the effective of 31 May 2018. Further, CP/CPS documents should include every component and subcomponent, and the placement of information should be aligned with the BRs; e.g. domain validation practices should be documented in section 3.2.2.4 of the CA’s CP/CPS.
* The words "''No Stipulation''" mean that the particular document imposes no requirements related to that section.
** Note that Mozilla's root store policy may be has been updated soon to forbid the use define acceptable usage of "No Stipulation" in CP/CPS documents.
* The words "''Not applicable''" are acceptable to indicate that the CA’s policies forbid the practice that is the title of the section. Language similar to “We do not perform <subject of the section>” is preferred.
* Sections should not be left blank. The purpose of "No Stipulation" is to make it clear that the omission of content was intentional.
