BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

C.3 Notations

NIST PIV and digital identity FIPS 201-3 against FIPS 201-2
All changes in this version
added Appendix C Glossary of Terms, Acronyms, and Notations part of C

Title changed

Before · FIPS 201-2

After · FIPS 201-3

Notations

Control changed

Before · FIPS 201-2

After · FIPS 201-3

This Standard uses the following typographical conventions in text:

• ASN.1 data types are represented in a monospaced font . For example, SignedData and SignerInfo are data types defined for digital signatures.
• Specific terms in CAPITALS represent normative requirements. When these same terms are not in CAPITALS , the term does not represent a normative requirement. – The terms “ SHALL ” and “ SHALL NOT ” indicate requirements to be followed strictly in order to conform to the publication and from which no deviation is permitted. – The terms “ SHOULD ” and “ SHOULD NOT ” indicate that among several possibilities, one is recommended as particularly suitable without mentioning or excluding others, that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. – The terms “ MAY ” and “ NEED NOT ” indicate a course of action permissible within the limits of the publication. – The terms “ CAN ” and “ CANNOT ” indicate a possibility and capability— whether material, physical, or causal—or, in the negative, the absence of that possibility or capability.