CA/Revocation Reasons: Difference between revisions

Jump to navigation Jump to search
m
fixing problems with normative text (all-caps MUST) introducing requirements more stringent than MRSP
(fixing problems with normative text (all-caps MUST) introducing requirements more stringent than MRSP)
m (fixing problems with normative text (all-caps MUST) introducing requirements more stringent than MRSP)
Line 130: Line 130:
For example, if both privilegeWithdrawn and cessationOfOperation apply, then privilegeWithdrawn should be used.
For example, if both privilegeWithdrawn and cessationOfOperation apply, then privilegeWithdrawn should be used.


Each sub-section within section 6.1.1 of Mozilla's Root Store policy ends with the sentence: "Otherwise, the <reason code> CRLReason MUST NOT be used." That sentence applies to the entire sub-section for each revocation reason code.  
Each sub-section within section 6.1.1 of Mozilla's Root Store policy ends with the sentence: "''Otherwise, the <reason code> CRLReason MUST NOT be used.''" That sentence applies to the entire sub-section for each revocation reason code.  


Treat the "intended" list within each sub-section as "SHOULD" (e.g. "The CRLReason <reason code> is intended to be used to indicate when:").  
Treat the "intended" list within each sub-section as "SHOULD" (e.g. "The CRLReason <reason code> is intended to be used to indicate when:").  
Confirmed users, Administrators
5,526

edits

Navigation menu