| authenticated-data-cms |
binary |
A CMS structure whose top-most content type MUST be the
authenticated-data content type, as described in Section 9
of RFC 5652. |
| cms |
binary |
A ContentInfo structure, as specified in RFC 5652,
encoded using ASN.1 distinguished encoding rules (DER),
as specified in ITU-T X.690. |
| crl |
binary |
A CertificateList structure, as specified in RFC 5280,
encoded using ASN.1 distinguished encoding rules (DER),
as specified in ITU-T X.690. |
| csr-info |
binary |
A CertificationRequestInfo structure, as defined in
RFC 2986, encoded using ASN.1 distinguished encoding
rules (DER), as specified in ITU-T X.690. |
| data-content-cms |
binary |
A CMS structure whose top-most content type MUST be the
data content type, as described in Section 4 of RFC 5652. |
| digested-data-cms |
binary |
A CMS structure whose top-most content type MUST be the
digested-data content type, as described in Section 7
of RFC 5652. |
| encrypted-data-cms |
binary |
A CMS structure whose top-most content type MUST be the
encrypted-data content type, as described in Section 8
of RFC 5652. |
| end-entity-cert-cms |
binary |
A CMS SignedData structure that MUST contain the end-entity
certificate itself and MAY contain any number
of intermediate certificates leading up to a trust
anchor certificate. The trust anchor certificate
MAY be included as well.
The CMS MUST contain a single end-entity certificate.
The CMS MUST NOT contain any spurious certificates.
This CMS structure MAY (as applicable where this type is
used) also contain suitably fresh (as defined by local
policy) revocation objects with which the device can
verify the revocation status of the certificates.
This CMS encodes the degenerate form of the SignedData
structure (RFC 5652, Section 5.2) that is commonly
used to disseminate X.509 certificates and revocation
objects (RFC 5280). |
| end-entity-cert-x509 |
binary |
A Certificate structure that MUST encode a certificate
that is neither self-signed nor has Basic constraint
CA true. |
| enveloped-data-cms |
binary |
A CMS structure whose top-most content type MUST be the
enveloped-data content type, as described in Section 6
of RFC 5652. |
| oscp-request |
binary |
A OCSPRequest structure, as specified in RFC 6960,
encoded using ASN.1 distinguished encoding rules
(DER), as specified in ITU-T X.690. |
| oscp-response |
binary |
A OCSPResponse structure, as specified in RFC 6960,
encoded using ASN.1 distinguished encoding rules
(DER), as specified in ITU-T X.690. |
| p10-csr |
binary |
A CertificationRequest structure, as specified in
RFC 2986, encoded using ASN.1 distinguished encoding
rules (DER), as specified in ITU-T X.690. |
| signed-data-cms |
binary |
A CMS structure whose top-most content type MUST be the
signed-data content type, as described in Section 5 of
RFC 5652. |
| trust-anchor-cert-cms |
binary |
A CMS SignedData structure that MUST contain the chain of
X.509 certificates needed to authenticate the certificate
presented by a client or end entity.
The CMS MUST contain only a single chain of certificates.
The client or end-entity certificate MUST only authenticate
to the last intermediate CA certificate listed in the chain.
In all cases, the chain MUST include a self-signed root
certificate. In the case where the root certificate is
itself the issuer of the client or end-entity certificate,
only one certificate is present.
This CMS structure MAY (as applicable where this type is
used) also contain suitably fresh (as defined by local
policy) revocation objects with which the device can
verify the revocation status of the certificates.
This CMS encodes the degenerate form of the SignedData
structure (RFC 5652, Section 5.2) that is commonly used
to disseminate X.509 certificates and revocation objects
(RFC 5280). |
| trust-anchor-cert-x509 |
binary |
A Certificate structure that MUST encode a self-signed
root certificate. |
| x509 |
binary |
A Certificate structure, as specified in RFC 5280,
encoded using ASN.1 distinguished encoding rules (DER),
as specified in ITU-T X.690. |