Confirmed users
593
edits
m (→Governance Review: fixed numbering) |
m (→Relevant MRSP Text: Added hyperlink) |
||
| Line 242: | Line 242: | ||
<blockquote> | <blockquote> | ||
5. CP/CPS Documentation MUST be structured according to the common outline set forth in [section 6 of RFC 3647 | 5. CP/CPS Documentation MUST be structured according to the common outline set forth in [https://datatracker.ietf.org/doc/html/rfc3647#section-6 section 6 of RFC 3647], as may be amended by the CA/Browser Forum's TLS BRs or its S/MIME BRs, and MUST: | ||
* include at least every section and subsection defined in [section 6 of RFC 3647 | * include at least every section and subsection defined in [https://datatracker.ietf.org/doc/html/rfc3647#section-6 section 6 of RFC 3647]; | ||
* only use the words "No Stipulation" to mean that the particular document imposes no requirements related to that section; and | * only use the words "No Stipulation" to mean that the particular document imposes no requirements related to that section; and | ||
* contain no sections that are entirely blank, having no text or subsections; | * contain no sections that are entirely blank, having no text or subsections; | ||