2002
DOI: 10.17487/rfc3369
|View full text |Cite
|
Sign up to set email alerts
|

Cryptographic Message Syntax (CMS)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
65
0
1

Year Published

2002
2002
2019
2019

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 42 publications
(66 citation statements)
references
References 1 publication
0
65
0
1
Order By: Relevance
“…It is necessary to standardize the data formats and processing procedures for such timestamps in order to be able to verify and communicate preservation evidence. A first approach was made by IETF within [RFC3126], where an optional Archive Timestamp Attribute was specified for integration in signatures according to the Cryptographic Messages Syntax (CMS) [RFC3852].…”
Section: Motivationmentioning
confidence: 99%
“…It is necessary to standardize the data formats and processing procedures for such timestamps in order to be able to verify and communicate preservation evidence. A first approach was made by IETF within [RFC3126], where an optional Archive Timestamp Attribute was specified for integration in signatures according to the Cryptographic Messages Syntax (CMS) [RFC3852].…”
Section: Motivationmentioning
confidence: 99%
“…according to CMS requirements [CMS02]. To obtain a higher assurance level a user should digitally sign all information (requests), e.g.…”
Section: Securitymentioning
confidence: 99%
“…The contentType field, which has type OBJECT IDENTIFIER, specifies the content type, and the content field, whose type is defined by the contentType field, contains the content value. This type is defined in [14] and [3].…”
Section: Contentinfomentioning
confidence: 99%
“…This document defines two new auxiliary object classes, pkcsEntity and naturalPerson, and selected attribute types for use with these classes. It also defines some attribute types for use in conjunction with PKCS #7 [14] (and S/MIME CMS [3]) digitally signed messages, PKCS #10 [16] certificate-signing requests, PKCS #12 [17] personal information exchanges and PKCS #15 [18] cryptographic tokens. Matching rules for use with these attributes are also defined, whenever necessary.…”
Section: Introductionmentioning
confidence: 99%