draft-ietf-smime-cades-07.txt   rfc5126.txt 
S/MIME Working Group D.Pinkas (Bull SAS)
INTERNET-DRAFT N.Pope (Thales eSecurity)
Expires May 2008 J.Ross (Security and Standards)
Obsoletes: RFC 3126 November 2007
Intended status: Informational
CMS Advanced Electronic Signatures (CAdES)
<draft-ietf-smime-cades-07.txt>
Status of this memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Network Working Group D. Pinkas
Task Force (IETF), its areas, and its working groups. Note that Request for Comments: 5126 Bull SAS
other groups may also distribute working documents as Internet- Obsoletes: 3126 N. Pope
Drafts. Category: Informational Thales eSecurity
J. Ross
Internet-Drafts are draft documents valid for a maximum of six Security and Standards
months and may be updated, replaced, or obsoleted by other February 2008
documents at any time. It is inappropriate to use Internet-Drafts
as reference material or to cite them other than as "work in
progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html.
The list of Internet-Draft Shadow Directories can be accessed at CMS Advanced Electronic Signatures (CAdES)
http://www.ietf.org/shadow.html.
Copyright Notice Status of This Memo
Copyright (C) The IETF Trust (2007). This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Abstract Abstract
This document defines the format of an electronic signature that can This document defines the format of an electronic signature that can
remain valid over long periods. This includes evidence as to its remain valid over long periods. This includes evidence as to its
validity even if the signer or verifying party later attempts to deny validity even if the signer or verifying party later attempts to deny
(i.e., repudiates) the validity of the signature. (i.e., repudiates) the validity of the signature.
The format can be considered as an extension to RFC 3852 [4] and The format can be considered as an extension to RFC 3852 and RFC
RFC 2634 [5], where, when appropriate, additional signed and 2634, where, when appropriate, additional signed and unsigned
unsigned attributes have been defined. attributes have been defined.
The contents of this Informational RFC amounts to a The contents of this Informational RFC amount to a transposition of
transposition of the ETSI TS 101 733 V.1.7.4 (CMS Advanced the ETSI Technical Specification (TS) 101 733 V.1.7.4 (CMS Advanced
Electronic Signatures - CAdES) [TS101733] and is technically Electronic Signatures -- CAdES) and is technically equivalent to it.
equivalent to it.
The technical contents of this specification are maintained by ETSI. The technical contents of this specification are maintained by ETSI.
The ETSI TS and further updates are available free of charge at : The ETSI TS and further updates are available free of charge at :
http://www.etsi.org/WebSite/Standards/StandardsDownload.aspx http://www.etsi.org/WebSite/Standards/StandardsDownload.aspx
Table of Contents Table of Contents
1. Introduction 6 1. Introduction ....................................................6
2. Scope ...........................................................6
2. Scope 6 3. Definitions and Abbreviations ...................................8
3.1. Definitions ................................................8
3. Definitions and abbreviations 8 3.2. Abbreviations .............................................11
3.1 Definitions 8 4. Overview .......................................................12
3.2 Abbreviations 11 4.1. Major Parties .............................................13
4.2. Signature Policies ........................................14
4. Overview 12 4.3. Electronic Signature Formats ..............................15
4.1 Major parties 12 4.3.1. CAdES Basic Electronic Signature (CAdES-BES) .......15
4.2 Signatures policies 14 4.3.2. CAdES Explicit Policy-based Electronic
4.3 Electronic signature formats 14 Signatures (CAdES-EPES) ............................18
4.3.1 CAdES Basic Electronic Signature (CAdES-BES) 14 4.4. Electronic Signature Formats with Validation Data .........19
4.3.2 CAdES Explicit Policy Electronic Signatures (CAdES-EPES) 17 4.4.1. Electronic Signature with Time (CAdES-T) ...........20
4.4 Electronic signature formats with validation data 18 4.4.2. ES with Complete Validation Data References
4.4.1 Electronic Signature with Time (CAdES-T) 19 (CAdES-C) ..........................................21
4.4.2 ES with Complete validation data references (CAdES-C) 20 4.4.3. Extended Electronic Signature Formats ..............23
4.4.3 Extended electronic signature formats 22 4.4.3.1. EXtended Long Electronic Signature
4.4.4 Archival Electronic Signature (CAdES-A) 26 (CAdES-X Long) ............................24
4.5 Arbitration 27 4.4.3.2. EXtended Electronic Signature with
4.6 Validation process 28 Time Type 1 ...............................25
4.4.3.3. EXtended Electronic Signature with
5. Electronic signature attributes 29 Time Type 2 ...............................26
5.1 General syntax 29 4.4.3.4. EXtended Long Electronic Signature
5.2 Data content type 29 with Time (CAdES-X Long ...................27
5.3 Signed-data content type 29 4.4.4. Archival Electronic Signature (CAdES-A) ............27
5.4 SignedData type 29 4.5. Arbitration ...............................................28
5.5 EncapsulatedContentInfo type 30 4.6. Validation Process ........................................29
5.6 SignerInfo type 30 5. Electronic Signature Attributes ................................30
5.6.1 Message digest calculation process 31 5.1. General Syntax ............................................30
5.6.2 Message signature generation process 31 5.2. Data Content Type .........................................30
5.6.3 Message signature verification process 31 5.3. Signed-data Content Type ..................................30
5.7 Basic ES mandatory present attributes 31 5.4. SignedData Type ...........................................31
5.7.1 Content type 31 5.5. EncapsulatedContentInfo Type ..............................31
5.7.2 Message digest 32 5.6. SignerInfo Type ...........................................31
5.7.3 Signing certificate reference attribute 32 5.6.1. Message Digest Calculation Process .................32
5.8 Additional mandatory attributes for Explicit Policy-based 5.6.2. Message Signature Generation Process ...............32
Electronic Signatures 34 5.6.3. Message Signature Verification Process .............32
5.8.1 Signature policy identifier 34 5.7. Basic ES Mandatory Present Attributes .....................32
5.9 CMS imported optional attributes 36 5.7.1. content-type .......................................32
5.9.1 Signing time 36 5.7.2. Message Digest .....................................33
5.9.2 Countersignature 36 5.7.3. Signing Certificate Reference Attributes ...........33
5.10 ESS imported optional attributes 37 5.7.3.1. ESS signing-certificate Attribute
5.10.1 Content reference attribute 37 Definition ................................34
5.10.2 Content identifier attribute 37 5.7.3.2. ESS signing-certificate-v2
5.10.3 Content hints attribute 37 Attribute Definition ......................34
5.7.3.3. Other signing-certificate
5.11 Additional optional attributes defined in the present document 38 Attribute Definition ......................35
5.11.1 Commitment type indication attribute 38 5.8. Additional Mandatory Attributes for Explicit
5.11.2 Signer location attribute 40 Policy-based Electronic Signatures ........................36
5.11.3 Signer attributes attribute 40 5.8.1. signature-policy-identifier ........................36
5.11.4 Content time-stamp 41 5.9. CMS Imported Optional Attributes ..........................38
5.12 Support for multiple signatures 41 5.9.1. signing-time .......................................38
5.12.1 Independent signatures 41 5.9.2. countersignature ...................................39
5.12.2 Embedded signatures 42 5.10. ESS-Imported Optional Attributes .........................39
5.10.1. content-reference Attribute .......................39
6. Additional Electronic Signature validation attributes 42 5.10.2. content-identifier Attribute ......................39
6.1 Electronic Signature Time-stamped (CAdES-T) 43 5.10.3. content-hints Attribute ...........................40
6.1.1 Signature time- stamp attribute definition 44 5.11. Additional Optional Attributes Defined in the
6.2 Complete validation reference data (CAdES-C) 44 Present Document .........................................40
6.2.1 Complete certificate references attribute definition 45 5.11.1. commitment-type-indication Attribute ..............41
6.2.2 Complete Revocation References attribute definition 45 5.11.2. signer-location Attribute .........................43
6.2.3 Attribute certificate references attribute definition 47 5.11.3. signer-attributes Attribute .......................43
6.2.4 Attribute revocation references attribute definition 48 5.11.4. content-time-stamp Attribute ......................44
6.3 Extended validation data (CAdES-X) 48 5.12. Support for Multiple Signatures ..........................44
6.3.1 Time-stamped validation data (CAdES-X Type 1 or Type 2) 48 5.12.1. Independent Signatures ............................44
6.3.2 Long validation data (CAdES-X Long, CAdES-X Long Type 1 or 2) 48 5.12.2. Embedded Signatures ...............................45
6.3.3 Certificate values attribute definition 49 6. Additional Electronic Signature Validation Attributes ..........45
6.3.4 Revocation values attribute definition 50 6.1. signature time-stamp Attribute (CAdES-T) ..................47
6.3.5 CAdES-C time-stamp attribute definition 51 6.1.1. signature-time-stamp Attribute Definition ..........47
6.3.6 Time-stamped certificates and crls references attribute 6.2. Complete Validation Data References (CAdES-C) .............48
definition 52 6.2.1. complete-certificate-references Attribute
6.4 Archive validation data 53 Definition .........................................48
6.4.1 Archive time-stamp attribute definition 53 6.2.2. complete-revocation-references Attribute
Definition .........................................49
7. Other standard data structures 55 6.2.3. attribute-certificate-references Attribute
7.1 Public-key certificate format 55 Definition .........................................51
7.2 Certificate revocation list format 55 6.2.4. attribute-revocation-references Attribute
7.3 OCSP response format 55 Definition .........................................52
7.4 Time-stamp token format 55 6.3. Extended Validation Data (CAdES-X) ........................52
7.5 Name and attribute formats 55 6.3.1. Time-Stamped Validation Data (CAdES-X Type
7.6 Attribute certificate 56 1 or Type 2) .......................................53
6.3.2. Long Validation Data (CAdES-X Long, CAdES-X
8. Conformance requirements 56 Long Type 1 or 2) ..................................53
8.1 CAdES-Basic Electronic Signature (CAdES-BES) 56 6.3.3. certificate-values Attribute Definition ............54
8.2 CAdES-Explicit Policy-based Electronic Signature 57 6.3.4. revocation-values Attribute Definition .............54
8.3 Verification using time-stamping 57 6.3.5. CAdES-C-time-stamp Attribute Definition ............56
8.4 Verification using secure records 58 6.3.6. time-stamped-certs-crls-references
Attribute Definition ...............................57
9. IANA Considerations 58 6.4. Archive Validation Data ...................................58
6.4.1. archive-time-stamp Attribute Definition ............58
10. References 58 7. Other Standard Data Structures .................................60
10.1 Normative references 58 7.1. Public Key Certificate Format .............................60
10.2 Informative references 59 7.2. Certificate Revocation List Format ........................60
7.3. OCSP Response Format ......................................60
11. Authors' addresses 62 7.4. Time-Stamp Token Format ...................................60
7.5. Name and Attribute Formats ................................60
12. Acknowledgments 62 7.6. AttributeCertificate ......................................61
8. Conformance Requirements .......................................61
Annex A (normative): ASN.1 definitions 63 8.1. CAdES-Basic Electronic Signature (CAdES-BES) ..............62
A.1 Signature format definitions using X.208 ASN.1 syntax 63 8.2. CAdES-Explicit Policy-based Electronic Signature ..........63
A.2 Signature format definitions using X.680 ASN.1 syntax 71 8.3. Verification Using Time-Stamping ..........................63
8.4. Verification Using Secure Records .........................63
Annex B (informative): Extended forms of Electronic Signatures 80 9. References .....................................................64
B.1 Extended forms of validation data 80 9.1. Normative References ......................................64
B.1.1 CAdES-X Long 81 9.2. Informative References ....................................65
B.1.2 CAdES-X Type 1 82 Annex A (normative): ASN.1 Definitions ............................69
B.1.3 CAdES-X Type 2 83 A.1. Signature Format Definitions Using
B.1.4 CAdES-X Long Type 1 and CAdES-X Long Type 2 85 X.208 ASN.1 Syntax ...................................69
B.2 Timestamp extensions 86 A.2. Signature Format Definitions Using
B.3 Archive validation data (CAdES-A) 87 X.680 ASN.1 Syntax ...................................77
B.4 Example validation sequence 89 Annex B (informative): Extended Forms of Electronic Signatures ....86
B.5 Additional optional features 94 B.1. Extended Forms of Validation Data ....................86
B.1.1. CAdES-X Long ..................................87
Annex C (informative):General description 95 B.1.2. CAdES-X Type 1 ................................88
C.1 The signature policy 95 B.1.3. CAdES-X Type 2 ................................90
C.2 Signed information 96 B.1.4. CAdES-X Long Type 1 and CAdES-X Long Type 2 ...91
C.3 Components of an electronic signature 96 B.2. Time-Stamp Extensions ................................93
C.3.1 Reference to the signature policy 96 B.3. Archive Validation Data (CAdES-A) ....................94
C.3.2 Commitment type indication 97 B.4. Example Validation Sequence ..........................97
C.3.3 Certificate identifier from the signer 97 B.5. Additional Optional Features ........................102
C.3.4 Role attributes 98 Annex C (informative): General Description .......................103
C.3.4.1 Claimed role 98 C.1. The Signature Policy ................................103
C.3.4.2 Certified role 99 C.2. Signed Information ..................................104
C.3.5 Signer location 99 C.3. Components of an Electronic Signature ...............104
C.3.6 Signing time 99 C.3.1. Reference to the Signature Policy ............104
C.3.7 Content format 100 C.3.2. Commitment Type Indication ...................105
C.3.8 Content hints 100 C.3.3. Certificate Identifier from the Signer .......106
C.3.9 Content cross referencing 100 C.3.4. Role Attributes ..............................106
C.4 Components of validation data 100 C.3.4.1. Claimed Role .......................107
C.4.1 Revocation status information 100 C.3.4.2. Certified Role .....................107
C.4.1.1 CRL information 101 C.3.5. Signer Location ..............................108
C.4.1.2 OCSP information 101 C.3.6. Signing Time .................................108
C.4.2 Certification path 102 C.3.7. Content Format ...............................108
C.4.3 Time-stamping for long life of signatures 102 C.3.8. content-hints ................................109
C.4.4 Time-stamping for long life of signature before CA key C.3.9. Content Cross-Referencing ....................109
compromises 103 C.4. Components of Validation Data .......................109
C.4.4.1 Time-stamping the ES with complete validation data 104 C.4.1. Revocation Status Information ................109
C.4.4.2 Time-stamping certificates and revocation information C.4.1.1. CRL Information .....................110
references 105 C.4.1.2. OCSP Information ....................110
C.4.5 Time-stamping for archive of signature 106 C.4.2. Certification Path ...........................111
C.4.6 Reference to additional data 107 C.4.3. Time-stamping for Long Life of Signatures ....111
C.4.7 Time-stamping for mutual recognition 107 C.4.4. Time-stamping for Long Life of Signature
C.4.8 TSA key compromise 108 before CA key Compromises ....................113
C.5 Multiple signatures 108 C.4.4.1. Time-stamping the ES with
Complete Validation Data ...........113
Annex D (informative):Data protocols to interoperate with TSPs 109 C.4.4.2. Time-Stamping Certificates and
D.1 Operational protocols 109 Revocation Information References ..114
D.1.1 Certificate retrieval 109 C.4.5. Time-stamping for Archive of Signature .......115
D.1.2 CRL retrieval 109 C.4.6. Reference to Additional Data .................116
D.1.3 OnLine certificate status 109 C.4.7. Time-Stamping for Mutual Recognition .........116
D.1.4 Time-stamping 109 C.4.8. TSA Key Compromise ...........................117
C.5. Multiple Signatures .................................118
D.2 Management protocols 109 Annex D (informative): Data Protocols to Interoperate with TSPs ..118
D.2.1 Request for certificate revocation 109 D.1. Operational Protocols ...............................118
D.1.1. Certificate Retrieval ........................118
Annex E (informative): Security Considerations 110 D.1.2. CRL Retrieval ................................118
E.1 Protection of private key 110 D.1.3. Online Certificate Status ....................119
E.2 Choice of algorithms 110 D.1.4. Time-Stamping ................................119
D.2. Management Protocols ................................119
Annex F (informative): Example structured contents and MIME 111 D.2.1. Request for Certificate Revocation ...........119
F.1 General description 111 Annex E (informative): Security Considerations ...................119
F.2 Header information 111 E.1. Protection of Private Key ...........................119
F.3 Content encoding 113 E.2. Choice of Algorithms ................................119
F.4 Multi-part content 113 Annex F (informative): Example Structured Contents and MIME ......120
F.5 S/MIME 113 F.1. General Description .................................120
F.1.1. Header Information ...........................120
F.1.2. Content Encoding .............................121
F.1.3. Multi-Part Content ...........................121
F.2. S/MIME ..............................................122
F.2.1. Using application/pkcs7-mime .................123
F.2.2. Using application/pkcs7-signature ............124
Annex G (informative): Relationship to the European Directive Annex G (informative): Relationship to the European Directive
and EESSI 115 and EESSI .................................125
G.1 Introduction 116 G.1. Introduction ........................................125
G.2 Electronic signatures and the directive 116 G.2. Electronic Signatures and the Directive .............126
G.3 ETSI electronic signature formats and the directive 117 G.3. ETSI Electronic Signature Formats and the Directive .127
G.4 EESSI standards and classes of electronic signature 117 G.4. EESSI Standards and Classes of Electronic Signature .127
G.4.1 Structure of EESSI standardization 117 G.4.1. Structure of EESSI Standardization ...........127
G.4.2 Classes of electronic signatures 118 G.4.2. Classes of Electronic Signatures .............128
G.4.3 EESSI classes and the ETSI electronic signature format 118 G.4.3. Electronic Signature Classes and the ETSI
Electronic Signature Format ..................128
Annex H (informative): APIs for the generation and verification Annex H (informative): APIs for the Generation and Verification
of electronic signatures tokens 118 of Electronic Signatures Tokens ...........129
H.1 Data framing 119 H.1. Data Framing ........................................129
H.2 IDUP-GSS-APIs defined by the IETF 120 H.2. IDUP-GSS-APIs Defined by the IETF ...................131
H.3 CORBA security interfaces defined by the OMG 121 H.3. CORBA Security Interfaces Defined by the OMG ........132
Annex I (informative): Cryptographic Algorithms ..................133
Annex I (informative):Cryptographic algorithms 123 I.1. Digest Algorithms ...................................133
I.1 Digest algorithms 123 I.1.1. SHA-1 ........................................133
I.1.1 SHA-1 123 I.1.2. General ......................................133
I.1.2 General 123 I.2. Digital Signature Algorithms ........................134
I.2 Digital signature algorithms 124 I.2.1. DSA ..........................................134
I.2.1 DSA 124 I.2.2. RSA ..........................................135
I.2.2 RSA 124 I.2.3. General ......................................135
I.2.3 General 125 Annex J (informative): Guidance on Naming ........................137
J.1. Allocation of Names .................................137
Annex J (informative): Guidance on naming 127 J.2. Providing Access to Registration Information ........138
J.1 Allocation of names 127 J.3. Naming Schemes ......................................138
J.2 Providing access to registration information 127 J.3.1. Naming Schemes for Individual Citizens .......138
J.3 Naming schemes 128 J.3.2. Naming Schemes for Employees of an
J.3.1 Naming schemes for individual citizens 128 Organization .................................139
J.3.2 Naming schemes for employees of an organization 128
Annex K (informative): Changes from the previous version 130
Full Copyright Statement 131
Intellectual Property 131
Acknowledgements 132
1. Introduction 1. Introduction
This document is intended to cover electronic signatures for various This document is intended to cover electronic signatures for various
types of transactions, including business transactions (e.g. purchase types of transactions, including business transactions (e.g.,
requisition, contract, and invoice applications) where long term purchase requisition, contract, and invoice applications) where
validity of such signatures is important. This includes evidence as long-term validity of such signatures is important. This includes
to its validity even if the signer or verifying party later attempts evidence as to its validity even if the signer or verifying party
to deny (i.e., repudiates, see ISO/IEC 10181-5 [ISO10181-5]) the later attempts to deny (i.e., repudiates; see ISO/IEC 10181-5
validity of the signature). [ISO10181-5]) the validity of the signature.
Thus the present document can be used for any transaction between an Thus, the present document can be used for any transaction between an
individual and a company, between two companies, between an individual individual and a company, between two companies, between an
and a governmental body, etc. The present document is independent of individual and a governmental body, etc. The present document is
any environment. It can be applied to any environment e.g. smart cards, independent of any environment; it can be applied to any environment,
GSM SIM cards, special programs for electronic signatures, etc. e.g., smart cards, Global System for Mobile Communication Subscriber
Identity Module (GSM SIM) cards, special programs for electronic
signatures, etc.
The European Directive on a community framework for Electronic The European Directive on a community framework for Electronic
Signatures defines an electronic signature as: "Data in electronic form Signatures defines an electronic signature as: "Data in electronic
which is attached to or logically associated with other electronic data form which is attached to or logically associated with other
and which serves as a method of authentication". electronic data and which serves as a method of authentication".
An electronic signature as used in the present document is a form An electronic signature, as used in the present document, is a form
of advanced electronic signature as defined in the Directive. of advanced electronic signature, as defined in the Directive.
2. Scope 2. Scope
The scope of the present document covers Electronic Signature Formats The scope of the present document covers electronic signature formats
only. The aspects of Electronic Signature Policies are defined in only. The aspects of Electronic Signature Policies are defined in
RFC 3125 [RFC3125] and in ETSI TR 102 272 [TR102272]. RFC 3125 [RFC3125] and ETSI TR 102 272 [TR102272].
The present document defines a number of Electronic Signature Formats, The present document defines a number of electronic signature
including electronic signature that can remain valid over long periods. formats, including electronic signatures that can remain valid over
This includes evidence as to its validity even if the signer or long periods. This includes evidence as to its validity even if the
verifying party later attempts to deny (repudiates) the validity of the signer or verifying party later attempts to deny (repudiates) the
electronic signature. validity of the electronic signature.
The present document specifies use of trusted service providers (e.g. The present document specifies use of Trusted Service Providers
Time-Stamping Authorities), and the data that needs to be archived (e.g., Time-Stamping Authorities) and the data that needs to be
(e.g. cross certificates and revocation lists) to meet the requirements archived (e.g., cross-certificates and revocation lists) to meet the
of long term electronic signatures. requirements of long-term electronic signatures.
An electronic signature defined by the present document can be used for An electronic signature, as defined by the present document, can be
arbitration in case of a dispute between the signer and verifier, which used for arbitration in case of a dispute between the signer and
may occur at some later time, even years later. verifier, which may occur at some later time, even years later.
The present document includes the concept of signature policies that The present document includes the concept of signature policies that
can be used to establish technical consistency when validating can be used to establish technical consistency when validating
electronic signatures but does not mandate their use. electronic signatures, but it does not mandate their use.
The present document is based on the use of public key cryptography to The present document is based on the use of public key cryptography
produce digital signatures, supported by public key certificates. to produce digital signatures, supported by public key certificates.
The present document also specifies the use of time-stamping and time- The present document also specifies the use of time-stamping and
marking services to prove the validity of a signature long after the time-marking services to prove the validity of a signature long after
normal lifetime of critical elements of an electronic signature. It the normal lifetime of critical elements of an electronic signature.
also, as an option, defines ways to provide very long-term protection This document also, as an option, defines ways to provide very
against key compromise or weakened algorithms. long-term protection against key compromise or weakened algorithms.
The present document builds on existing standards that are widely The present document builds on existing standards that are widely
adopted. This includes: adopted. These include:
- RFC 3852 [4] "Cryptographic Message Syntax (CMS)"; - RFC 3852 [4]: "Cryptographic Message Syntax (CMS)";
- ISO/IEC 9594-8/ITU-T Recommendation X.509 [1]: "Information - ISO/IEC 9594-8/ITU-T Recommendation X.509 [1]: "Information
technology - Open Systems Interconnection - The Directory: technology - Open Systems Interconnection - The Directory:
Authentication framework"; Authentication framework";
- RFC 3280 [2] "Internet X.509 Public Key Infrastructure (PKIX) - RFC 3280 [2]: "Internet X.509 Public Key Infrastructure (PKIX)
Certificate and CRL Profile"; Certificate and Certificate Revocation List (CRL) Profile";
- RFC 3161 [7] "Internet X.509 Public Key Infrastructure Time-Stamp - RFC 3161 [7]: "Internet X.509 Public Key Infrastructure
Protocol". Time-Stamp Protocol (TSP)".
NOTE: See section 11 for a full set of references. NOTE: See Section 11 for a full set of references.
The present document describes formats for advanced electronic The present document describes formats for advanced electronic
signatures using ASN.1 (Abstract Syntax Notation 1) [14]. ASN.1 signatures using ASN.1 (Abstract Syntax Notation 1) [14]. ASN.1 is
is encoded using X.690 [16]. encoded using X.690 [16].
These formats are based on CMS (Cryptographic Message Syntax) defined These formats are based on CMS (Cryptographic Message Syntax) defined
in RFC 3852 [4]. These electronic signatures are thus called CAdES, in RFC 3852 [4]. These electronic signatures are thus called CAdES,
for "CMS Advanced Electronic Signatures". for "CMS Advanced Electronic Signatures".
Another document, TS 101 903 [TS101903], describes formats for XML Another document, TS 101 903 [TS101903], describes formats for XML
advanced electronic signatures (XAdES) built on XMLDSIG [XMLDSIG]. advanced electronic signatures (XAdES) built on XMLDSIG as specified
in [XMLDSIG].
In addition, the present document identifies other documents that In addition, the present document identifies other documents that
define formats for Public Key Certificates, Attribute Certificates, define formats for Public Key Certificates, Attribute Certificates,
Certificate Revocation Lists and supporting protocols, including, and Certificate Revocation Lists and supporting protocols, including
protocols for use of trusted third parties to support the operation of protocols for use by trusted third parties to support the operation
electronic signature creation and validation. of electronic signature creation and validation.
Informative annexes include: Informative annexes include:
- illustrations of extended forms of extended Electronic Signatures - illustrations of extended forms of Electronic Signature formats
formats that protect against various vulnerabilities and examples that protect against various vulnerabilities and examples of
of validation processes (Annex B); validation processes (Annex B);
- descriptions and explanations of some of the concepts used in the - descriptions and explanations of some of the concepts used in
present document, giving a rationale for normative parts of the the present document, giving a rationale for normative parts of
present document (Annex C); the present document (Annex C);
- information on protocols to interoperate with Trusted Service - information on protocols to interoperate with Trusted Service
Providers (Annex D); Providers (Annex D);
- guidance on naming (Annex E); - guidance on naming (Annex E);
- an example structured content and MIME (Annex F); - an example structured content and MIME (Annex F);
- the relationship between the present document and the directive - the relationship between the present document and the directive
on electronic signature and associated standardization on electronic signature and associated standardization
initiatives (Annex G); initiatives (Annex G);
- APIs to support the generation and the verification of electronic
- APIs to support the generation and verification of electronic
signatures (Annex H); signatures (Annex H);
- cryptographic algorithms that may be used (Annex I); and - cryptographic algorithms that may be used (Annex I); and
- changes from the previous version (see Annex J). - naming schemes (see Annex J).
3 Definitions and abbreviations 3. Definitions and Abbreviations
3.1 Definitions 3.1. Definitions
For the purposes of the present document, the following terms and For the purposes of the present document, the following terms and
definitions apply: definitions apply:
Arbitrator: arbitrator entity may be used to arbitrate a dispute Arbitrator: an arbitrator entity may be used to arbitrate a dispute
between a signer and verifier when there is a disagreement on the between a signer and verifier when there is a disagreement on the
validity of a digital signature. validity of a digital signature.
Attribute Authority (AA): authority which assigns privileges by issuing Attribute Authority (AA): an authority that assigns privileges by
attribute certificates. issuing attribute certificates.
Authority certificate: certificate issued to an authority (e.g. either Authority Certificate: a certificate issued to an authority (e.g.,
to a certification authority or to an attribute authority). either to a certification authority or an attribute authority).
Attribute Authority Revocation List (AARL): revocation list containing Attribute Authority Revocation List (AARL): a revocation list
a list of references to certificates issued to AAs, that are no longer containing a list of references to certificates issued to AAs that
considered valid by the issuing authority. are no longer considered valid by the issuing authority.
Attribute Certificate Revocation List (ACRL): revocation list Attribute Certificate Revocation List (ACRL): a revocation list
containing a list of references to attribute certificates that are no containing a list of references to attribute certificates that are no
longer considered valid by the issuing authority. longer considered valid by the issuing authority.
Certification Authority Revocation List (CARL): revocation list Certification Authority Revocation List (CARL): a revocation list
containing a list of public-key certificates issued to certification containing a list of public key certificates issued to certification
authorities, that are no longer considered valid by the certificate authorities that are no longer considered valid by the certificate
issuer. issuer.
Certification Authority (CA): authority trusted by one or more users to Certification Authority (CA): an authority trusted by one or more
create and assign public key certificates, optionally the certification users to create and assign public key certificates; optionally, the
authority may create the users' keys. certification authority may create the users' keys.
NOTE: See ITU-T Recommendation X.509 [1]. NOTE: See ITU-T Recommendation X.509 [1].
Certificate Revocation List (CRL): signed list indicating a set of Certificate Revocation List (CRL): a signed list indicating a set of
public key certificates that are no longer considered valid by the public key certificates that are no longer considered valid by the
certificate issuer. certificate issuer.
Digital signature: data appended to, or a cryptographic transformation Digital Signature: data appended to, or a cryptographic
of, a data unit that allows a recipient of the data unit to prove the transformation of, a data unit that allows a recipient of the data
source and integrity of the data unit and protect against forgery, e.g. unit to prove the source and integrity of the data unit and protect
by the recipient. against forgery, e.g., by the recipient.
NOTE: See ISO 7498-2 [ISO7498-2]. NOTE: See ISO 7498-2 [ISO7498-2].
Electronic signature: data in electronic form which are attached to or Electronic Signature: data in electronic form that is attached to or
logically associated with other electronic data and which serve as a logically associated with other electronic data and that serves as a
method of authentication. method of authentication.
NOTE: See Directive 1999/93/EC of the European Parliament and of the NOTE: See Directive 1999/93/EC of the European Parliament and of
Council of 13 December 1999 on a Community framework for the Council of 13 December 1999 on a Community framework for
electronic signatures [EU Directive]. electronic signatures [EU Directive].
Enhanced electronic signatures: electronic signatures enhanced by Extended Electronic Signatures: electronic signatures enhanced by
complementing the baseline requirements with additional data, such as complementing the baseline requirements with additional data, such as
time tamp tokens and certificate revocation data, to address commonly time-stamp tokens and certificate revocation data, to address
recognized threats. commonly recognized threats.
Explicit Policy-based Electronic Signature (EPES): an electronic Explicit Policy-based Electronic Signature (EPES): an electronic
signature where the signature policy is explicitly specified that shall signature where the signature policy that shall be used to validate
be used to validate it. it is explicitly specified.
Grace period: time period which permits the certificate revocation Grace Period: a time period that permits the certificate revocation
information to propagate through the revocation process to relying information to propagate through the revocation process to relying
parties. parties.
Initial verification: a process performed by a verifier done after an Initial Verification: a process performed by a verifier done after an
electronic signature is generated in order to capture additional electronic signature is generated in order to capture additional
information that could make it valid for long term verification. information that could make it valid for long-term verification.
Public Key Certificate (PKC): public keys of a user, together with some Public Key Certificate (PKC): public keys of a user, together with
other information, rendered unforgeable by encipherment with the some other information, rendered unforgeable by encipherment with the
private key of the certification authority which issued it. private key of the certification authority that issued it.
NOTE: See ITU-T Recommendation X.509 [1]. NOTE: See ITU-T Recommendation X.509 [1].
Rivest-Shamir-Adleman (RSA): asymmetric cryptography algorithm based on Rivest-Shamir-Adleman (RSA): an asymmetric cryptography algorithm
the difficulty to factor very large numbers, using a key pair: a based on the difficulty to factor very large numbers using a key
private key and a public key. pair: a private key and a public key.
Signature policy: set of rules for the creation and validation of an Signature Policy: a set of rules for the creation and validation of
electronic signature, that defines the technical and procedural an electronic signature that defines the technical and procedural
requirements for electronic signature creation and validation, in order requirements for electronic signature creation and validation, in
to meet a particular business need, and under which the signature can order to meet a particular business need, and under which the
be determined to be valid. signature can be determined to be valid.
Signature policy issuer: entity that defines and issues a signature Signature Policy Issuer: an entity that defines and issues a
policy. signature policy.
Signature validation policy: part of the signature policy which Signature Validation Policy: part of the signature policy that
specifies the technical requirements on the signer in creating a specifies the technical requirements on the signer in creating a
signature and verifier when validating a signature. signature and verifier when validating a signature.
Signer: entity that creates an electronic signature. Signer: an entity that creates an electronic signature.
Subsequent Verification: a process performed by a verifier to assess Subsequent Verification: a process performed by a verifier to assess
the signature validity. the signature validity.
NOTE: It may be done even years after the electronic signature was NOTE: Subsequent verification may be done even years after the
produced by the signer and completed by the Initial electronic signature was produced by the signer and completed by
Verification and it might not need to capture more data than the initial verification, and it might not need to capture more
those captured at the time of initial verification. data than those captured at the time of initial verification.
Time-Stamp token: data object that binds a representation of a datum to Time-Stamp Token: a data object that binds a representation of a
a particular time, thus establishing evidence that the datum existed datum to a particular time, thus establishing evidence that the datum
before that time. existed before that time.
Time-Mark: information in an audit trail from a Trusted Service Time-Mark: information in an audit trail from a Trusted Service
Provider that binds a representation of a datum to a particular time, Provider that binds a representation of a datum to a particular time,
thus establishing evidence that the datum existed before that time. thus establishing evidence that the datum existed before that time.
Time-Marking Authority: trusted third party that creates records in an Time-Marking Authority: a trusted third party that creates records in
audit trail in order to indicate that a datum existed before a an audit trail in order to indicate that a datum existed before a
particular point in time. particular point in time.
Time-Stamping Authority (TSA): trusted third party that creates time- Time-Stamping Authority (TSA): a trusted third party that creates
stamp tokens in order to indicate that a datum existed at a particular time-stamp tokens in order to indicate that a datum existed at a
point in time. particular point in time.
Time-Stamping Unit (TSU): set of hardware and software which is managed Time-Stamping Unit (TSU): a set of hardware and software that is
as a unit and has a single time-stamp token signing key active at a managed as a unit and has a single time-stamp token signing key
time. active at a time.
Trusted Service Provider (TSP): entity that helps to build trust Trusted Service Provider (TSP): an entity that helps to build trust
relationships by making available or providing some information upon relationships by making available or providing some information upon
request. request.
Validation data: additional data that may be used by a verifier of Validation Data: additional data that may be used by a verifier of
electronic signatures to determine the signature is valid. electronic signatures to determine that the signature is valid.
Valid electronic signature: electronic signature which passes Valid Electronic Signature: an electronic signature that passes
validation. validation.
Verifier: entity that verifies evidence. Verifier: an entity that verifies evidence.
NOTE 1: See ISO/IEC 13888-1 [ISO13888-1]. NOTE 1: See ISO/IEC 13888-1 [ISO13888-1].
NOTE 2: Within the context of the present document this is an entity NOTE 2: Within the context of the present document, this is an
that validates an electronic signature. entity that validates an electronic signature.
3.2 Abbreviations 3.2. Abbreviations
For the purposes of the present document, the following abbreviations For the purposes of the present document, the following abbreviations
apply: apply:
AA Attribute Authority AA Attribute Authority
AARL Attribute Authority Revocation List AARL Attribute Authority Revocation List
ACRL Attribute Certificate Revocation List ACRL Attribute Certificate Revocation List
API Application Program Interface API Application Program Interface
ASCII American Standard Code for Information Interchange ASCII American Standard Code for Information Interchange
ASN.1 Abstract Syntax Notation 1 ASN.1 Abstract Syntax Notation 1
CA Certification Authority CA Certification Authority
CAD Card Accepting Device CAD Card Accepting Device
CAdES CMS Advanced Electronic Signature CAdES CMS Advanced Electronic Signature
CAdES-A CAdES with Archive validation data CAdES-A CAdES with Archive validation data
CAdES-BES CAdES Basic Electronic Signature CAdES-BES CAdES Basic Electronic Signature
CAdES-C CAdES with Complete validation data CAdES-C CAdES with Complete validation data
CAdES-EPES CAdES Explicit Policy Electronic Signature CAdES-EPES CAdES Explicit Policy Electronic Signature
CAdES-T CAdES with Time-stamp CAdES-T CAdES with Time
CAdES-X CAdES with eXtended validation data CAdES-X CAdES with eXtended validation data
CAdES-X Long CAdES with EXtended Long validation data
CARL Certification Authority Revocation List CARL Certification Authority Revocation List
CMS Cryptographic Message Syntax CMS Cryptographic Message Syntax
CRL Certificate Revocation List CRL Certificate Revocation List
CWA CEN Workshop Agreement CWA CEN (European Committee for Standardization) Workshop
Agreement
DER Distinguished Encoding Rules (for ASN.1) DER Distinguished Encoding Rules (for ASN.1)
DSA Digital Signature Algorithm DSA Digital Signature Algorithm
EDIFACT Electronic Data Interchange For Administration, Commerce EDIFACT Electronic Data Interchange For Administration,
and Transport Commerce and Transport
EESSI European Electronic Signature Standardization
EESSI European Electronic Signature Standardization Initiative Initiative
EPES Explicit Policy-based Electronic Signature EPES Explicit Policy-based Electronic Signature
ES Electronic Signature ES Electronic Signature
ESS Enhanced Security Services (enhances CMS) ESS Enhanced Security Services (enhances CMS)
IDL Interface Definition Language IDL Interface Definition Language
MIME Multipurpose Internet Mail Extensions MIME Multipurpose Internet Mail Extensions
OCSP Online Certificate Status Provider OCSP Online Certificate Status Provider
OID Object IDentifier OID Object IDentifier
PKC Public Key Certificate PKC Public Key Certificate
PKIX Public Key Infrastructure using X.509 (IETF Working Group) PKIX Public Key Infrastructure using X.509
(IETF Working Group)
RSA Rivest-Shamir-Adleman RSA Rivest-Shamir-Adleman
SHA-1 Secure Hash Algorithm 1 SHA-1 Secure Hash Algorithm 1
TSA Time-Stamping Authority TSA Time-Stamping Authority
TSP Trusted Service Provider TSP Trusted Service Provider
TST Time-Stamp Token TST Time-Stamp Token
TSU Time-Stamping Unit TSU Time-Stamping Unit
URI Uniform Resource Identifier URI Uniform Resource Identifier
URL Uniform Resource Locator URL Uniform Resource Locator
XML eXtended Mark up Language XML Extensible Markup Language
XMLDSIG XML-Signature Syntax and Processing XMLDSIG XML Digital Signature
4 Overview 4. Overview
The present document defines a number of Electronic Signature (ES) The present document defines a number of Electronic Signature (ES)
formats that build on CMS (RFC 3852 [4]) by adding signed and unsigned formats that build on CMS (RFC 3852 [4]) by adding signed and
attributes. unsigned attributes.
This section provides an introduction to the major parties involved This section:
(section 4.1), the concept of Signature Policies (section 4.2), provides
an overview of the various ES formats (section 4.3), introduces the
concept of validation data and provides an overview of formats that
incorporate validation data (section 4.4), presents relevant
considerations on arbitration (section 4.5) and for the validation
process (section 4.6).
The formal specifications of the attributes are specified in sections 5 - provides an introduction to the major parties involved
and 6, annexes C and D provide rationale for the definitions of the (Section 4.1),
- introduces the concept of signature policies (Section 4.2),
- provides an overview of the various ES formats (Section 4.3),
- introduces the concept of validation data, and provides an
overview of formats that incorporate validation data
(Section 4.4), and
- presents relevant considerations on arbitration
(Section 4.5) and for the validation process (Section 4.6).
The formal specifications of the attributes are specified in Sections
5 and 6; Annexes C and D provide rationale for the definitions of the
different ES forms. different ES forms.
4.1 Major parties 4.1. Major Parties
The major parties involved in a business transaction supported by The major parties involved in a business transaction supported by
electronic signatures as defined in the present document are: electronic signatures, as defined in the present document, are:
- the Signer; - the signer;
- the Verifier; - the verifier;
- Trusted Service Providers (TSP); and - Trusted Service Providers (TSP); and
- the Arbitrator. - the arbitrator.
The signer is the entity that creates the electronic signature. When The signer is the entity that creates the electronic signature. When
the signer digitally signs over data using the prescribed format, this the signer digitally signs over data using the prescribed format,
represents a commitment on behalf of the signing entity to the data this represents a commitment on behalf of the signing entity to the
being signed. data being signed.
The verifier is the entity that validates the electronic signature, it The verifier is the entity that validates the electronic signature;
may be a single entity or multiple entities. it may be a single entity or multiple entities.
The Trusted Service Providers (TSPs) are one or more entities that help The Trusted Service Providers (TSPs) are one or more entities that
to build trust relationships between the signer and verifier. They help to build trust relationships between the signer and verifier.
support the signer and verifier by means of supporting services They support the signer and verifier by means of supporting services
including: user certificates, cross-certificates, time-stamp tokens, including: user certificates, cross-certificates, time-stamp tokens,
CRLs, ARLs, OCSP responses. The following TSPs are used to support the CRLs, ARLs, and OCSP responses. The following TSPs are used to
functions defined in the present document: support the functions defined in the present document:
- Certification Authorities; - Certification Authorities;
- Registration Authorities; - Registration Authorities;
- CRL Issuers; - CRL Issuers;
- OCSP Responders; - OCSP Responders;
- Repository Authorities (e.g. a Directory); - Repository Authorities (e.g., a Directory);
- Time-Stamping Authorities; - Time-Stamping Authorities;
- Time-Marking Authorities; and - Time-Marking Authorities; and
- Signature Policy Issuers. - Signature Policy Issuers.
Certification Authorities provide users with public key certificates Certification Authorities provide users with public key certificates
and with a revocation service. and a revocation service.
Registration Authorities allow the identification and registration of Registration Authorities allow the identification and registration of
entities before a CA generates certificates. entities before a CA generates certificates.
Repository Authorities publish CRLs issued by CAs, signature policies Repository Authorities publish CRLs issued by CAs, signature policies
issued by Signature Policy Issuers and optionally public key issued by Signature Policy Issuers, and optionally public key
certificates. certificates.
Time-Stamping Authorities attest that some data was formed before a Time-Stamping Authorities attest that some data was formed before a
given trusted time. given trusted time.
Time-Marking Authorities record that some data was formed before a Time-Marking Authorities record that some data was formed before a
given trusted time. given trusted time.
Signature Policy Issuers define the signature policies to be used by Signature Policy Issuers define the signature policies to be used by
signers and verifiers. signers and verifiers.
In some cases the following additional TSPs are needed: In some cases, the following additional TSPs are needed:
- Attribute Authorities. - Attribute Authorities.
Attributes Authorities provide users with attributes linked to public Attributes Authorities provide users with attributes linked to public
key certificates. key certificates.
An Arbitrator is an entity that arbitrates in disputes between a signer An Arbitrator is an entity that arbitrates in disputes between a
and a verifier. signer and a verifier.
4.2 Signatures policies 4.2. Signature Policies
The present document includes the concept of signature policies that The present document includes the concept of signature policies that
can be used to establish technical consistency when validating can be used to establish technical consistency when validating
electronic signatures. electronic signatures.
When a comprehensive signature policy used by the verifier is either When a comprehensive signature policy used by the verifier is either
explicitly indicated by the signer or implied by the data being signed, explicitly indicated by the signer or implied by the data being
then a consistent result can be obtained when validating an electronic signed, then a consistent result can be obtained when validating an
signature. electronic signature.
When the signature policy being used by the verifier is neither When the signature policy being used by the verifier is neither
indicated by the signer nor can be derived from other data, or the indicated by the signer nor can be derived from other data, or the
signature policy is incomplete then verifiers, including arbitrators, signature policy is incomplete, then verifiers, including
may obtain different results when validating an electronic signature. arbitrators, may obtain different results when validating an
Therefore, comprehensive signature policies that ensure consistency of electronic signature. Therefore, comprehensive signature policies
signature validation are recommended from both the signers and that ensure consistency of signature validation are recommended from
verifiers point of view. both the signer's and verifier's point of view.
Further information on signature policies is provided in: Further information on signature policies is provided in:
- TR 102 038 [TR102038]; - TR 102 038 [TR102038];
- sections 5.8.1, C.1 and C.3.1 of the present document; - Sections 5.8.1, C.1, and C.3.1 of the present document;
- RFC 3125 [RFC3125]; and - RFC 3125 [RFC3125]; and
- TR 102 272 [TR102272]. - TR 102 272 [TR102272].
4.3 Electronic signature formats 4.3. Electronic Signature Formats
The current document sectionprovides an overview for two forms of CMS The current section provides an overview for two forms of CMS
advanced electronic signature specified in the present document, advanced electronic signature specified in the present document,
namely, the CAdES Basic Electronic Signature (CAdES-BES) and the namely, the CAdES Basic Electronic Signature (CAdES-BES) and the
CAdES Explicit Policy-based Electronic Signature (CAdES-EPES). CAdES Explicit Policy-based Electronic Signature (CAdES-EPES).
Conformance to the present document mandates the signer creates one of Conformance to the present document mandates that the signer create
these formats. one of these formats.
4.3.1 CAdES Basic Electronic Signature (CAdES-BES) 4.3.1. CAdES Basic Electronic Signature (CAdES-BES)
A CAdES Basic Electronic Signature (CAdES-BES) in accordance with the A CAdES Basic Electronic Signature (CAdES-BES), in accordance with
present contains: the present document, contains:
- The signed user data (e.g. the signer's document) as defined in - The signed user data (e.g., the signer's document), as defined
CMS (RFC 3852 [4]); in CMS (RFC 3852 [4]);
- A collection of mandatory signed attributes as defined in CMS - A collection of mandatory signed attributes, as defined in CMS
(RFC 3852 [4]) and in ESS (RFC 2634 [5]); (RFC 3852 [4]) and in ESS (RFC 2634 [5]);
- Additional mandatory signed attributes defined in the present - Additional mandatory signed attributes, defined in the present
document; and document; and
- The digital signature value computed on the user data and, when - The digital signature value computed on the user data and, when
present, on the signed attributes, as defined in CMS (RFC 3852 present, on the signed attributes, as defined in CMS (RFC 3852
[4]). [4]).
A CAdES Basic Electronic Signature (CAdES-BES) in accordance with the A CAdES Basic Electronic Signature (CAdES-BES), in accordance with
present document may contain: the present document, may contain:
- a collection of additional signed attributes; and - a collection of additional signed attributes; and
- a collection of optional unsigned attributes. - a collection of optional unsigned attributes.
The mandatory signed attributes are: The mandatory signed attributes are:
- Content-type. It is defined in RFC 3852 [4] and specifies the - Content-type. It is defined in RFC 3852 [4] and specifies the
type of the EncapsulatedContentInfo value being signed. Details type of the EncapsulatedContentInfo value being signed. Details
are provided in 5.7.1. Rationale for its inclusion is provided are provided in Section 5.7.1 of the present document.
in section C.3.7; Rationale for its inclusion is provided in Annex C.3.7;
- Message-digest. It is defined in RFC 3852 [4] and specifies the - Message-digest. It is defined in RFC 3852 [4] and specifies the
message digest of the eContent OCTET STRING within message digest of the eContent OCTET STRING within
encapContentInfo being signed. Details are provided in section encapContentInfo being signed. Details are provided in Section
5.7.2; 5.7.2;
- ESS signing-certificate OR ESS signing-certificate v2. The ESS - ESS signing-certificate OR ESS signing-certificate-v2. The ESS
signing-certificate attribute is defined in Enhanced Security signing-certificate attribute is defined in Enhanced Security
Services (ESS), RFC 2634 [5] and only allows for the use of SHA-1 Services (ESS), RFC 2634 [5], and only allows for the use of
as digest algorithm. The ESS signing-certificate attribute V2 SHA-1 as a digest algorithm. The ESS signing-certificate-v2
is defined in "ESS Update: Adding CertID Algorithm Agility" attribute is defined in "ESS Update: Adding CertID Algorithm
RFC 5035 [15], and allows for the use of any digest algorithm. Agility", RFC 5035 [15], and allows for the use of any digest
A CAdES-BES claiming compliance with the present document must algorithm. A CAdES-BES claiming compliance with the present
include one of them. Section 5.7.3 provides the details of document must include one of them. Section 5.7.3 provides the
these attributes. Rationale for its inclusion is provided in details of these attributes. Rationale for its inclusion is
section C.3.3. provided in Annex C.3.3.
Optional signed attributes may be added to the CAdES-BES, including Optional signed attributes may be added to the CAdES-BES, including
optional signed attributes defined in CMS (RFC 3852 [4]), ESS (RFC 2634 optional signed attributes defined in CMS (RFC 3852 [4]), ESS (RFC
[5]) and the present document. Listed below are optional attributes 2634 [5]), and the present document. Listed below are optional
that are defined in section 5 and have a rational provided in annex C: attributes that are defined in Section 5 and have a rationale
provided in Annex C:
- Signing-time: as defined in CMS (RFC 3852 [4]) indicates the time - Signing-time: as defined in CMS (RFC 3852 [4]), indicates the
of the signature as claimed by the signer. Details and short time of the signature, as claimed by the signer. Details and
rationale are provided in section 5.9.1. Section C.3.6 provides short rationale are provided in Section 5.9.1. Annex C.3.6
the rationale. provides the rationale.
- Content-hints as defined in ESS (RFC 2634 [5]) provides - content-hints: as defined in ESS (RFC 2634 [5]), provides
information that describes the innermost signed content of a information that describes the innermost signed content of a
multi-layer message where one content is encapsulated in another. multi-layer message where one content is encapsulated in
Section 5.10.1 provides the specification details. Section C.3.8 another. Section 5.10.1 provides the specification details.
provides the rationale. Annex C.3.8 provides the rationale.
- Content-reference. as defined in ESS (RFC 2634 [5]) can be - content-reference: as defined in ESS (RFC 2634 [5]), can be
incorporated as a way to link request and reply messages in an incorporated as a way to link request and reply messages in an
exchange between two parties. Section 5.10.1 provides the exchange between two parties. Section 5.10.1 provides the
specification details. Section C.3.9 provides the rationale. specification details. Annex C.3.9 provides the rationale.
- Content-identifier. as defined in ESS (RFC 2634 [5]) contains an - content-identifier: as defined in ESS (RFC 2634 [5]), contains
identifier that may be used later on in the previous content- an identifier that may be used later on in the previous
reference attribute. Section 5.10.2 provides the specification content-reference attribute. Section 5.10.2 provides the
details. Section C.3.8 provides the rationale. specification details.
- Commitment-type-indication. This attribute is defined by the - commitment-type-indication: this attribute is defined by the
present document as a way to indicate the commitment endorsed by present document as a way to indicate the commitment endorsed by
the signer when producing the signature. Section 5.11.1 provides the signer when producing the signature. Section 5.11.1
the specification details. Section C.3.2 provides the provides the specification details. Annex C.3.2 provides the
rationale. rationale.
- Signer-location. This attribute is defined by the present - signer-location: this attribute is defined by the present
document. It allows the signer to indicate the place where the document. It allows the signer to indicate the place where the
signer purportedly produced the signature. Section 5.11.2 signer purportedly produced the signature. Section 5.11.2
provides the specification details. Section C.3.5 provides the provides the specification details. Annex C.3.5 provides the
rationale. rationale.
- Signer-attributes. This attribute is defined by the present - signer-attributes: this attribute is defined by the present
document. It allows a claimed or certified role to be document. It allows a claimed or certified role to be
incorporated into the signed information. Section 5.11.3 provides incorporated into the signed information. Section 5.11.3
the specification details. Section C.3.4 provides the rationale. provides the specification details. Annex C.3.4 provides the
rationale.
- Content-time-stamp. This attribute is defined by the present - content-time-stamp: this attribute is defined by the present
document. It allows a time-stamp token of the data to be signed document. It allows a time-stamp token of the data to be signed
to be incorporated into the signed information. It provides to be incorporated into the signed information. It provides
proof of the existence of the data before the signature was proof of the existence of the data before the signature was
created. Section 5.11.4 provides the specification details. created. Section 5.11.4 provides the specification details.
Section C.3.6 provides the rationale. Annex C.3.6 provides the rationale.
A CAdES-BES form can also incorporate instances of unsigned attributes A CAdES-BES form can also incorporate instances of unsigned
as defined in CMS (RFC 3852 [4]) and ESS (RFC 2634 [5]). attributes, as defined in CMS (RFC 3852 [4]) and ESS (RFC 2634 [5]).
- CounterSignature, as defined in CMS (RFC 3852 [4]). It can be - CounterSignature, as defined in CMS (RFC 3852 [4]); it can be
incorporated wherever embedded signatures (i.e. a signature on incorporated wherever embedded signatures (i.e., a signature on
a previous signature) are needed. Section 5.9.2 provides the a previous signature) are needed. Section 5.9.2 provides the
specification details. Section C.5 in annex C provides the specification details. Annex C.5 in Annex C provides the
rationale. rationale.
The structure of the CAdES-BES is illustrated in figure 1. The structure of the CAdES-BES is illustrated in Figure 1.
+------Elect.Signature (CAdES-BES)------+ +------Elect.Signature (CAdES-BES)------+
|+----------------------------------- + | |+----------------------------------- + |
||+---------+ +----------+ | | ||+---------+ +----------+ | |
|||Signer's | | Signed | Digital | | |||Signer's | | Signed | Digital | |
|||Document | |Attributes| Signature | | |||Document | |Attributes| Signature | |
||| | | | | | ||| | | | | |
||+---------+ +----------+ | | ||+---------+ +----------+ | |
|+------------------------------------+ | |+------------------------------------+ |
+---------------------------------------+ +---------------------------------------+
Figure 1: Illustration of a CAdES-BES Figure 1: Illustration of a CAdES-BES
The signer's conformance requirements of a CAdES-BES are defined in The signer's conformance requirements of a CAdES-BES are defined in
section 8.1. Section 8.1.
NOTE: The CAdES-BES is the minimum format for an electronic signature NOTE: The CAdES-BES is the minimum format for an electronic
to be generated by the signer. On its own, it does not signature to be generated by the signer. On its own, it does not
provide enough information for it to be verified in the longer provide enough information for it to be verified in the longer
term. For example, revocation information issued by the term. For example, revocation information issued by the relevant
relevant certificate status information issuer needs to be certificate status information issuer needs to be available for
available for long term validation (see section 4.4.2). long-term validation (see Section 4.4.2).
The CAdES-BES satisfies the legal requirements for electronic The CAdES-BES satisfies the legal requirements for electronic
signatures as defined in the European Directive on electronic signatures, as defined in the European Directive on Electronic
signatures, (see annex C for further discussion on relationship of the Signatures, (see Annex C for further discussion on the relationship
present document to the Directive). It provides basic authentication of the present document to the Directive). It provides basic
and integrity protection. authentication and integrity protection.
The semantics of the signed data of a CAdES-BES or its context may The semantics of the signed data of a CAdES-BES or its context may
implicitly indicate a signature policy to the verifier. Specification implicitly indicate a signature policy to the verifier.
of the contents of signature policies is outside the scope of the
present document. However, further information on signature policies
is provided in TR 102 038 [TR102038], RFC 3125 [RFC3125] and sections
5.8.1, C.1 and C.3.1 of the present document.
4.3.2 CAdES Explicit Policy Electronic Signatures (CAdES-EPES) Specification of the contents of signature policies is outside the
scope of the present document. However, further information on
signature policies is provided in TR 102 038 [TR102038], RFC 3125
[RFC3125], and Sections 5.8.1, C.1, and C.3.1 of the present
document.
A CAdES Explicit Policy-based Electronic Signature (CAdES-EPES) in 4.3.2. CAdES Explicit Policy-based Electronic Signatures (CAdES-EPES)
A CAdES Explicit Policy-based Electronic Signature (CAdES-EPES), in
accordance with the present document, extends the definition of an accordance with the present document, extends the definition of an
electronic signature to conform to the identified signature policy. electronic signature to conform to the identified signature policy.
A CAdES Explicit Policy-based Electronic Signature (CAdES-EPES) A CAdES Explicit Policy-based Electronic Signature (CAdES-EPES)
incorporates a signed attribute (signature-policy-identifier) incorporates a signed attribute (sigPolicyID attribute) indicating
indicating that a signature policy that is mandatory to use to validate the signature policy that shall be used to validate the electronic
the signature and specifies explicitly the signature policy that shall signature. This signed attribute is protected by the signature. The
be used. This signed attribute is protected by the signature. The signature may also have other signed attributes required to conform
signature may also have other signed attributes required to conform to to the mandated signature policy.
the mandated signature policy.
Section 5.7.3 provides the details on the specification of signature- Section 5.7.3 provides the details on the specification of
policy-identifier attribute. Section C.1 provides a short rationale. signature-policy-identifier attribute. Annex C.1 provides a short
Specification of the contents of signature policies is outside the rationale. Specification of the contents of signature policies is
scope of the present document. outside the scope of the present document.
Further information on signature policies is provided in TR 102 038 Further information on signature policies is provided in TR 102 038
[TR102038] and sections 5.8.1, C.1 and C.3.1 of the present document. [TR102038] and Sections 5.8.1, C.1, and C.3.1 of the present
document.
The structure of the CAdES-EPES is illustrated in figure 2. The structure of the CAdES-EPES is illustrated in Figure 2.
+------------- Elect.Signature (CAdES-EPES) ---------------+ +------------- Elect.Signature (CAdES-EPES) ---------------+
| | | |
|+-------------------------------------------------------+ | |+-------------------------------------------------------+ |
|| +-----------+ | | || +-----------+ | |
|| | | +---------------------------+ | | || | | +---------------------------+ | |
|| | | | +----------+ | | | || | | | +----------+ | | |
|| | Signer's | | |Signature | Signed | Digital | | || | Signer's | | |Signature | Signed | Digital | |
|| | Document | | |Policy ID | Attributes |Signature| | || | Document | | |Policy ID | Attributes |Signature| |
|| | | | +----------+ | | | || | | | +----------+ | | |
|| | | +---------------------------+ | | || | | +---------------------------+ | |
|| +-----------+ | | || +-----------+ | |
|+-------------------------------------------------------+ | |+-------------------------------------------------------+ |
| | | |
+----------------------------------------------------------+ +----------------------------------------------------------+
Figure 2: Illustration of a CAdES-EPES Figure 2: Illustration of a CAdES-EPES
The signer's conformance requirements of CAdES-EPES are defined in The signer's conformance requirements of CAdES-EPES are defined in
section 8.2. Section 8.2.
4.4 Electronic signature formats with validation data 4.4. Electronic Signature Formats with Validation Data
Validation of an electronic signature in accordance with the present Validation of an electronic signature, in accordance with the present
document requires additional data needed to validate the electronic document, requires additional data needed to validate the electronic
signature. This additional data is called validation data; and signature. This additional data is called validation data, and
includes: includes:
- Public Key Certificates (PKCs); - Public Key Certificates (PKCs);
- revocation status information for each PKC; - revocation status information for each PKC;
- trusted time-stamps applied to the digital signature or a time- - trusted time-stamps applied to the digital signature, otherwise
mark shall be available in an audit log; and a time-mark shall be available in an audit log.
- when appropriate, the details of a signature policy to be used to - when appropriate, the details of a signature policy to be used
verify the electronic signature. to verify the electronic signature.
The validation data may be collected by the signer and/or the verifier. The validation data may be collected by the signer and/or the
When the signature-policy-identifier signed attribute is present, it verifier. When the signature-policy-identifier signed attribute is
shall meet the requirements of the signature policy. present, it shall meet the requirements of the signature policy.
Validation data includes CA certificates as well as revocation status Validation data includes CA certificates as well as revocation status
information in the form of Certificate Revocation Lists (CRLs) or information in the form of Certificate Revocation Lists (CRLs) or
certificate status information (OCSP) provided by an on-line service. certificate status information (OCSP) provided by an online service.
Validation data also includes evidence that the signature was created Validation data also includes evidence that the signature was created
before a particular point in time this may be either a time-stamp before a particular point in time; this may be either a time-stamp
token or time-mark. token or time-mark.
The present document defines unsigned attributes able to contain The present document defines unsigned attributes able to contain
validation data that can be added to CAdES-BES and CAdES-EPES leading validation data that can be added to CAdES-BES and CAdES-EPES,
to electronic signature formats that include validation data. Sections leading to electronic signature formats that include validation data.
below summarize these formats and their most relevant characteristics. The sections below summarize these formats and their most relevant
characteristics.
4.4.1 Electronic Signature with Time (CAdES-T) 4.4.1. Electronic Signature with Time (CAdES-T)
Electronic Signature with Time (CAdES-T) in accordance with the present An electronic signature with time (CAdES-T), in accordance with the
document is when there exits trusted time associated with the ES. present document, is when there exits trusted time associated with
the ES.
The trusted time may be provided by: The trusted time may be provided by:
- the signature-time-stamp as an unsigned attribute added to the - a time-stamp attribute as an unsigned attribute added to the ES;
ES; and and
- A time mark of the ES provided by a trusted service provider. - a time-mark of the ES provided by a Trusted Service Provider.
The signature-time-stamp attribute contains a time-stamp token of the The time-stamp attribute contains a time-stamp token of the
electronic signature value. Section 6.1.1 provides the specification electronic signature value. Section 6.1.1 provides the specification
details. Section C.4.3 in provides the rationale. details. Annex C.4.3 provides the rationale.
A time-mark provided by a Trusted Service would have similar effect to A time-mark provided by a Trusted Service would have a similar effect
the signature-time-stamp attribute but in this case no attribute is to the signature-time-stamp attribute, but in this case, no attribute
added to the ES as it is the responsibility of the TSP to provide is added to the ES, as it is the responsibility of the TSP to provide
evidence of a time mark when required to do so. The management of time evidence of a time-mark when required to do so. The management of
marks is outside the scope of the present document. time marks is outside the scope of the present document.
Trusted time provides the initial steps towards providing long term Trusted time provides the initial steps towards providing long-term
validity. Electronic signatures with the time stamp attribute forming validity. Electronic signatures with the time-stamp attribute or a
the CAdES-T is illustrated in figure 3. time-marked BES/EPES, forming the CAdES-T are illustrated in Figure
3.
+-------------------------------------------------CAdES-T ---------+ +-------------------------------------------------CAdES-T ---------+
|+------ CAdES-BES or CAdES-EPES -------+ | |+------ CAdES-BES or CAdES-EPES -------+ |
||+-----------------------------------+ | +----------------------+ | ||+-----------------------------------+ | +----------------------+ |
|||+---------+ +----------+ | | | | | |||+---------+ +----------+ | | | | |
||||Signer's | | Signed | Digital | | | Signature-time-stamp | | ||||Signer's | | Signed | Digital | | | Signature-time-stamp | |
||||Document | |Attributes| Signature | | | attribute required | | ||||Document | |Attributes| Signature | | | attribute required | |
|||| | | | | | | when using time | | |||| | | | | | | when using time | |
|||+---------+ +----------+ | | | stamps. | | |||+---------+ +----------+ | | | stamps. | |
||+-----------------------------------+ | | | | ||+-----------------------------------+ | | | |
|+--------------------------------------+ | or the BES/EPES | | |+--------------------------------------+ | or the BES/EPES | |
| | shall be time marked | | | | shall be time-marked | |
| | | | | | | |
| | Management and | | | | Management and | |
| | provision of time | | | | provision of time | |
| | mark is the | | | | mark is the | |
| | responsibility of | | | | responsibility of | |
| | the TSP. | | | | the TSP. | |
| +----------------------+ | | +----------------------+ |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
Figure 3: Illustration of CAdES-T formats Figure 3: Illustration of CAdES-T formats
NOTE 1 : A time stamp token is added to the CAdES-BES or CAdES-EPES
NOTE 1: A time-stamp token is added to the CAdES-BES or CAdES-EPES
as an unsigned attribute. as an unsigned attribute.
NOTE 2 : Timestamp tokens that may themselves include unsigned NOTE 2: Time-stamp tokens that may themselves include unsigned
attributes required to validate the timestamp token, such attributes required to validate the time-stamp token, such as the
as the complete-certificate-references and complete- complete-certificate-references and complete-revocation-references
revocation-references attributes as defined by the present attributes, as defined by the present document.
document.
4.4.2 ES with Complete validation data references (CAdES-C) 4.4.2. ES with Complete Validation Data References (CAdES-C)
Electronic Signature with Complete validation data references (CAdES-C) Electronic Signature with Complete validation data references
in accordance with the present document adds to the CAdES-T the (CAdES-C), in accordance with the present document, adds to the
complete-certificate-references and complete-revocation-references CAdES-T the complete-certificate-references and
attributes as defined by the present document. The complete- complete-revocation-references attributes, as defined by the present
certificate-references attribute contain references to all the document. The complete-certificate-references attribute contains
certificates present in the certification path used for verifying the references to all the certificates present in the certification path
signature. The complete-revocation-references attribute contains used for verifying the signature. The complete-revocation-references
references to the CRLs and/or OCSP responses used for verifying the attribute contains references to the CRLs and/or OCSPs responses used
signature. Section 6.2 provides the specification details. Storing for verifying the signature. Section 6.2 provides the specification
the references allows the values of the certification path and the CRLs details. Storing the references allows the values of the
or OCSPs responses to be stored elsewhere, reducing the size of a certification path and the CRLs or OCSPs responses to be stored
stored electronic signature format. elsewhere, reducing the size of a stored electronic signature format.
Sections C.4.1 to C.4.2 provide rationale on the usage of validation Sections C.4.1 to C.4.2 provide rationale on the usage of validation
data and when it is suitable to generate the CAdES-C form. data and when it is suitable to generate the CAdES-C form.
Electronic signatures with the additional validation data forming the Electronic signatures, with the additional validation data forming
CAdES-C are illustrated in figure 4. the CAdES-C, are illustrated in Figure 4.
+------------------------- CAdES-C --------------------------------+ +------------------------- CAdES-C --------------------------------+
|+----------------------------- CAdES-T ---------+ | |+----------------------------- CAdES-T ---------+ |
|| +----------+ | +-------------+ | || +----------+ | +-------------+ |
|| |Timestamp | | | | | || |Timestamp | | | | |
|| |attribute | | | | | || |attribute | | | | |
||+- CAdES-BES or CAdES-EPES ------+|over | | | | | ||+- CAdES-BES or CAdES-EPES ------+|over | | | | |
||| ||digital | | | Complete | | ||| ||digital | | | Complete | |
|||+---------++----------+ ||signature | | | certificate | | |||+---------++----------+ ||signature | | | certificate | |
||||Signer's || Signed | Digital ||is | | | and | | ||||Signer's || Signed | Digital ||is | | | and | |
||||Document ||Attributes|Signature||mandatory | | | revocation | | ||||Document ||Attributes|Signature||mandatory | | | revocation | |
|||| || | ||if is not | | | references | | |||| || | ||if is not | | | references | |
|||+---------++----------+ ||timemarked| | | | | |||+---------++----------+ ||timemarked| | | | |
||+--------------------------------++----------+ | | | | ||+--------------------------------++----------+ | | | |
|+-----------------------------------------------+ +-------------+ | |+-----------------------------------------------+ +-------------+ |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
Figure 4: Illustration of CAdES-C format Figure 4: Illustration of CAdES-C format
NOTE 1: The complete certificate and revocation references are added NOTE 1: The complete certificate and revocation references are
to the CAdES-T as an unsigned attribute. added to the CAdES-T as an unsigned attribute.
NOTE 2: As a minimum, the signer will provide the CAdES-BES or when NOTE 2: As a minimum, the signer will provide the CAdES-BES or,
indicating that the signature conforms to an explicit signing when indicating that the signature conforms to an explicit signing
policy the CAdES-EPES. policy, the CAdES-EPES.
NOTE 3: To reduce the risk of repudiating signature creation, the NOTE 3: To reduce the risk of repudiating signature creation, the
trusted time indication needs to be as close as possible to trusted time indication needs to be as close as possible to the
the time the signature was created. The signer or a TSP could time the signature was created. The signer or a TSP could provide
provide the CAdES-T, if not the verifier should create the the CAdES-T; if not, the verifier should create the CAdES-T on
CAdES-T on first receipt of an electronic signature because first receipt of an electronic signature because the CAdES-T
the CAdES-T provides independent evidence of the existence of provides independent evidence of the existence of the signature
the signature prior to the trusted time indication. prior to the trusted time indication.
NOTE 4: An CAdES-T trusted time indications must be created before a NOTE 4: A CAdES-T trusted time indication must be created before a
certificate has been revoked or expired. certificate has been revoked or expired.
NOTE 5: The signer and TSP could provide the CAdES-C, to minimize NOTE 5: The signer and TSP could provide the CAdES-C to minimize
this risk and when the signer does not provide the CAdES-C, this risk, and when the signer does not provide the CAdES-C, the
verifier should create the CAdES-C when the required component of
the verifier should create the CAdES-C when the required revocation and validation data become available; this may require
component of revocation and validation data become available, a grace period.
this may require a grace period.
NOTE 6: A grace period permits certificate revocation information to NOTE 6: A grace period permits certificate revocation information
propagate through the revocation processes. This period could to propagate through the revocation processes. This period could
extend from the time an authorized entity requests certificate extend from the time an authorized entity requests certificate
revocation, to when the information is available for the revocation to when the information is available for the relying
relying party to use. In order to make sure that the party to use. In order to make sure that the certificate was not
certificate was not revoked at the time the signature was revoked at the time the signature was time-marked or time-stamped,
time-marked or time-stamped, verifiers should wait until the verifiers should wait until the end of the grace period. A
end of the grace period. A signature policy may define signature policy may define specific values for grace periods.
specific values for grace periods.
An illustration of a grace period is provided in figure 5. An illustration of a grace period is provided in Figure 5.
+<--------------Grace Period --------->+ +<--------------Grace Period --------->+
----+-------+-------+--------+---------------------+----------+ ----+-------+-------+--------+---------------------+----------+
^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^
| | | | | | | | | | | |
| | | | | | | | | | | |
Signature | First | Second | Signature | First | Second |
creation | revocation | revocation | creation | revocation | revocation |
time | status | status | time | status | status |
| checking | checking | | checking | checking |
skipping to change at page 22, line 4 skipping to change at page 23, line 33
time | status | status | time | status | status |
| checking | checking | | checking | checking |
| | | | | |
Time-stamp Certification Build Time-stamp Certification Build
or path CAdES-C or path CAdES-C
time-mark construction time-mark construction
over & verification over & verification
signature signature
Figure 5: Illustration of a grace period Figure 5: Illustration of a grace period
NOTE 7: CWA 14171 [CWA14171] specifies a signature validation NOTE 7: CWA 14171 [CWA14171] specifies a signature validation
process using CAdES-T, CAdES-C and a grace period. process using CAdES-T, CAdES-C, and a grace period. Annex B
Annex B provides example validation processes. Section C.4 provides example validation processes. Annex C.4 provides
provides additional information about applying grace periods additional information about applying grace periods during the
during the validation process. validation process.
The verifier's conformance requirements are defined in section 8.3 for The verifier's conformance requirements are defined in Section 8.3
time stamped CAdES-C and section 8.4 for time marked CAdES-C. The for time-stamped CAdES-C, and Section 8.4 for time-marked CAdES-C.
present document only defines conformance requirements for the verifier The present document only defines conformance requirements for the
up to an ES with complete validation data (CAdES-C). This means that verifier up to an ES with Complete validation data (CAdES-C). This
none of the extended and archive forms of Electronic Signature as means that none of the extended and archive forms of electronic
defined in sections 4.4.3 to 4.4.4) need to be implemented to achieve signatures, as defined in Sections 4.4.3 to 4.4.4, need to be
conformance to the present document. implemented to achieve conformance to the present document.
4.4.3 Extended electronic signature formats 4.4.3. Extended Electronic Signature Formats
CAdES-C can be extended by adding unsigned attributes to the electronic CAdES-C can be extended by adding unsigned attributes to the
signature. The present document defines various unsigned attributes electronic signature. The present document defines various unsigned
that are applicable for very long term verification, and for preventing attributes that are applicable for very long-term verification, and
some disaster situations which are discussed in annex C. Annex B for preventing some disaster situations that are discussed in Annex
provides the details of the various extended formats, all the required C. Annex B provides the details of the various extended formats, all
unsigned attributes for each type and how they can be used within the the required unsigned attributes for each type, and how they can be
electronic signature validation process. The sections below give an used within the electronic signature validation process. The
overview of the various forms of extended signature formats in the sections below give an overview of the various forms of extended
present document. signature formats in the present document.
4.4.3.1 EXtended Long Electronic Signature (CAdES-X Long) 4.4.3.1. EXtended Long Electronic Signature (CAdES-X Long)
Extended Long format (CAdES-X Long) in accordance with the present Extended Long format (CAdES-X Long), in accordance with the present
document adds to the CAdES-C format the certificate-values and document, adds the certificate-values and revocation-values
revocation-values attributes. The first one contains the whole attributes to the CAdES-C format. The first one contains the whole
certificate path required for verifying the signature; the second one certificate path required for verifying the signature; the second one
the CRLs and/OCSP responses required for the validation of the contains the CRLs and/OCSP responses required for the validation of
signature. This provides a known repository of certificate and the signature. This provides a known repository of certificate and
revocation information required to validate an CAdES-C and prevents revocation information required to validate a CAdES-C and prevents
such information getting lost. Sections 6.3.3 and 6.3.4 give such information from getting lost. Sections 6.3.3 and 6.3.4 give
specification details. Section B.1.1 gives details on the production specification details. Annex B.1.1 gives details on the production
of the format. Sections C4.1 to C.4.2 provide the rationale. of the format. Annexes C4.1 to C.4.2 provide the rationale.
The structure of the CAdES-X Long format is illustrated in figure 6. The structure of the CAdES-X Long format is illustrated in Figure 6.
+----------------------- CAdES-X-Long -----------------------------+ +----------------------- CAdES-X-Long -----------------------------+
|+------------------------------------ CadES-C --+ | |+------------------------------------ CadES-C --+ |
|| +----------+ | +-------------+ | || +----------+ | +-------------+ |
||+------ CAdES -------------------+|Timestamp | | | | | ||+------ CAdES -------------------+|Timestamp | | | | |
||| || over | | | Complete | | ||| || over | | | Complete | |
|||+---------++----------+ ||digital | | | certificate | | |||+---------++----------+ ||digital | | | certificate | |
||||Signer's || Signed | Digital ||signature | | | and | | ||||Signer's || Signed | Digital ||signature | | | and | |
||||Document ||Attributes|Signature|| | | | revocation | | ||||Document ||Attributes|Signature|| | | | revocation | |
|||| || | ||Optional | | | data | | |||| || | ||Optional | | | data | |
skipping to change at page 23, line 32 skipping to change at page 25, line 5
|| | and | | | || | and | | |
|| | revocation | | | || | revocation | | |
|| | references | | | || | references | | |
|| +-------------+ | | || +-------------+ | |
|+-----------------------------------------------+ | |+-----------------------------------------------+ |
| | | |
+------------------------------------------------------------------+ +------------------------------------------------------------------+
Figure 6: Illustration of CAdES-X-Long Figure 6: Illustration of CAdES-X-Long
4.4.3.2 EXtended Electronic Signature with Time Type 1 4.4.3.2. EXtended Electronic Signature with Time Type 1
(CAdES-X Type 1) (CAdES-X Type 1)
Extended format with time type 1 (CAdES-X Type 1) in accordance with Extended format with time type 1 (CAdES-X Type 1), in accordance with
the present document adds to the CAdES-C format the CAdES-C-time-stamp the present document, adds the CAdES-C-time-stamp attribute, whose
attribute, whose content is a time-stamp token on the CAdES-C itself. content is a time-stamp token on the CAdES-C itself, to the CAdES-C
format.
This provides an integrity and trusted time protection over all the This provides an integrity and trusted time protection over all the
elements and references. It may protect the certificates, CRLs and elements and references. It may protect the certificates, CRLs, and
OCSP responses in case of a later compromise of a CA key, CRL key or OCSP responses in case of a later compromise of a CA key, CRL key, or
OCSP issuer key. Section 6.3.5 provides the specification details. OCSP issuer key. Section 6.3.5 provides the specification details.
Section B.1.2 gives details on the production of the time-stamping Annex B.1.2 gives details on the production of the time-stamping
process. Sections C.4.4.1 provides the rationale. process. Annex C.4.4.1 provides the rationale.
The structure of the CAdES-X Type 1 format is illustrated in figure 7. The structure of the CAdES-X Type 1 format is illustrated in Figure
7.
+----------------------- CAdES-X-Type 1 ------------------------------+ +----------------------- CAdES-X-Type 1 ------------------------------+
|+-------------------------------------- CAdES-C -----+ | |+-------------------------------------- CAdES-C -----+ |
|| +-------------+ | +-----------+ | || +-------------+ | +-----------+ |
||+--------- CAdES ------------------+| Timestamp | | | | | ||+--------- CAdES ------------------+| Timestamp | | | | |
||| || over | | | | | ||| || over | | | | |
|||+---------++----------+ || digital | | | | | |||+---------++----------+ || digital | | | | |
||||Signer's || Signed | Digital || signature | | | Timestamp | | ||||Signer's || Signed | Digital || signature | | | Timestamp | |
||||Document ||Attributes| Signature || | | | over | | ||||Document ||Attributes| Signature || | | | over | |
|||| || | || Optional | | | CAdES-C | | |||| || | || Optional | | | CAdES-C | |
skipping to change at page 24, line 31 skipping to change at page 26, line 5
|| | certificate | | | || | certificate | | |
|| | and | | | || | and | | |
|| | revocation | | | || | revocation | | |
|| | references | | | || | references | | |
|| +-------------+ | | || +-------------+ | |
|+----------------------------------------------------+ | |+----------------------------------------------------+ |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
Figure 7: Illustration of CAdES-X Type 1 Figure 7: Illustration of CAdES-X Type 1
4.4.3.3 EXtended Electronic Signature with Time Type 2 4.4.3.3. EXtended Electronic Signature with Time Type 2
(CAdES-X Type 2) (CAdES-X Type 2)
Extended format with time type 2 (CAdES-X Type 2) in accordance with Extended format with time type 2 (CAdES-X Type 2), in accordance with
the present document adds to the CAdES-C format the CAdES-C-time- the present document, adds to the CAdES-C format the
stamped-certs-crls-references attribute, whose content is a time-stamp CAdES-C-time-stamped-certs-crls-references attribute, whose content
token on the certification path and revocation information references. is a time-stamp token on the certification path and revocation
This provides an integrity and trusted time protection over all the information references. This provides an integrity and trusted time
references. protection over all the references.
It may protect the certificates, CRLs and OCSP responses in case of a It may protect the certificates, CRLs and OCSP responses in case of a
later compromise of a CA key, CRL key or OCSP issuer key. later compromise of a CA key, CRL key or OCSP issuer key.
Both CAdES-X Type 1 and CAdES-X Type 2 counter the same threats and the Both CAdES-X Type 1 and CAdES-X Type 2 counter the same threats, and
usage of one or the other depends on the environment. Section 6.3.5 the usage of one or the other depends on the environment. Section
provides the specification details. Section B.1.3 gives details on the 6.3.5 provides the specification details. Annex B.1.3 gives details
production of the time-stamping process. Section C.4.4.2 provides the on the production of the time-stamping process. Annex C.4.4.2
rationale. provides the rationale.
The structure of the CAdES-X Type 2 format is illustrated in figure 8. The structure of the CAdES-X Type 2 format is illustrated in Figure
8.
+------------------------- CAdES-X-Type 2 ----------------------------+ +------------------------- CAdES-X-Type 2 ----------------------------+
|+----------------------------------------CAdES-C ---+ | |+----------------------------------------CAdES-C ---+ |
|| +------------+| | || +------------+| |
||+----- CAdES -----------------------+| Timmestamp || | ||+----- CAdES -----------------------+| Timestamp || |
||| || over || | ||| || over || |
|||+---------+ +----------+ || digital || +-------------+| |||+---------+ +----------+ || digital || +-------------+|
||||Signer's | | Signed | Digital || signature || | Time-stamp || ||||Signer's | | Signed | Digital || signature || | Time-stamp ||
||||Document | |Attributes| signature || || | only over || ||||Document | |Attributes| signature || || | only over ||
|||| | | | || optional || | complete || |||| | | | || optional || | complete ||
|||+---------+ +----------+ || when || | certificate || |||+---------+ +----------+ || when || | certificate ||
||+-----------------------------------+| timemarked || | and || ||+-----------------------------------+| timemarked || | and ||
|| +------------+| | revocation || || +------------+| | revocation ||
|| +-------------+ | | references || || +-------------+ | | references ||
|| | Complete | | +-------------+| || | Complete | | +-------------+|
|| | certificate | | | || | certificate | | |
|| | and | | | || | and | | |
|| | revocation | | | || | revocation | | |
|| | references | | | || | references | | |
|| +-------------+ | | || +-------------+ | |
|+---------------------------------------------------+ | |+---------------------------------------------------+ |
+---------------------------------------------------------------------+ +---------------------------------------------------------------------+
Figure 8: Illustration of CAdES-X Type 2 Figure 8: Illustration of CAdES-X Type 2
4.4.3.4 EXtended Long Electronic Signature with Time (CAdES-X Long Type 4.4.3.4. EXtended Long Electronic Signature with Time (CAdES-X Long
1 or 2) Type 1 or 2)
Extended Long with Time (CAdES-X Long Type 1 or 2) in accordance with Extended Long with Time (CAdES-X Long Type 1 or 2), in accordance
the present document is a combination of CAdES-X Long and one of the with the present document, is a combination of CAdES-X Long and one
two former types (CAdES-X Type 1 and CAdES-X Type 2). Section B.1.4 of the two former types (CAdES-X Type 1 and CAdES-X Type 2). Annex
gives details on the production of the time-stamping process. Section B.1.4 gives details on the production of the time-stamping process.
C4.8 in annex C provides the rationale. Annex C.4.8 in Annex C provides the rationale.
The structure of the CAdES-X Long Type 1 and CAdES-X Long Type 2. The structure of the CAdES-X Long Type 1 and CAdES-X Long Type 2
format is illustrated in figure 9. format is illustrated in Figure 9.
+------------------ CAdES-X Long Type 1 or 2 -----------------------+ +------------------ CAdES-X Long Type 1 or 2 -----------------------+
| +--------------+| | +--------------+|
|+-------------------------------------- CAdES-C --+|+------------+|| |+-------------------------------------- CAdES-C --+|+------------+||
|| ||| Timestamp ||| || ||| Timestamp |||
||+------- CAdES --------------------++----------+ ||| over ||| ||+------- CAdES --------------------++----------+ ||| over |||
||| ||Timestamp | ||| CAdES-C ||| ||| ||Timestamp | ||| CAdES-C |||
||| ||over | ||+------------+|| ||| ||over | ||+------------+||
|||+---------++----------+ ||digital | || OR || |||+---------++----------+ ||digital | || OR ||
||||Signer's || Signed | Digital ||signature | ||+------------+|| ||||Signer's || Signed | Digital ||signature | ||+------------+||
skipping to change at page 26, line 37 skipping to change at page 27, line 46
|| | revocation | | | Complete | | || | revocation | | | Complete | |
|| | references | | |certificate | | || | references | | |certificate | |
|| +-------------+ | | and | | || +-------------+ | | and | |
|+-------------------------------------------------+ |revocation | | |+-------------------------------------------------+ |revocation | |
| | value | | | | value | |
| +------------+ | | +------------+ |
+-------------------------------------------------------------------+ +-------------------------------------------------------------------+
Figure 9: Illustration of CAdES-X Long Type 1 and CAdES Long Type 2 Figure 9: Illustration of CAdES-X Long Type 1 and CAdES Long Type 2
4.4.4 Archival Electronic Signature (CAdES-A) 4.4.4. Archival Electronic Signature (CAdES-A)
Archival Form (CAdES-A) in accordance with the present document builds Archival Form (CAdES-A), in accordance with the present document,
on a CAdES-X Long or a CAdES-X Long Type 1 or 2 by adding one or more builds on a CAdES-X Long or a CAdES-X Long Type 1 or 2 by adding one
archive-time-stamp attributes. This form is used for archival of long- or more archive-time-stamp attributes. This form is used for
term signatures. Successive time-stamps protect the whole material archival of long-term signatures. Successive time-stamps protect the
against vulnerable hashing algorithms or the breaking of the whole material against vulnerable hashing algorithms or the breaking
cryptographic material or algorithms. Section 6.4 contains the of the cryptographic material or algorithms. Section 6.4 contains
specification details. Sections C.4.5 and C.4.8 provide the rationale. the specification details. Sections C.4.5 and C.4.8 provide the
rationale.
The structure of the CAdES-A form is illustrated in figure 10. The structure of the CAdES-A form is illustrated in Figure 10.
+---------------------------CAdES-A ---------------------------------+ +---------------------------CAdES-A ---------------------------------+
|+----------------------------------------------------+ | |+----------------------------------------------------+ |
|| +--------------+| +----------+ | || +--------------+| +----------+ |
||+----------------------CAdES-C ----+|+------------+|| | | | ||+----------------------CAdES-C ----+|+------------+|| | | |
||| +----------+ ||| Timestamp ||| | | | ||| +----------+ ||| Timestamp ||| | | |
|||+---- CAdES-BES ----+|Timestamp | ||| over ||| | | | |||+---- CAdES-BES ----+|Timestamp | ||| over ||| | | |
|||| or CAdeS-EPES || over | ||| CAdES-C ||| | Archive | | |||| or CAdeS-EPES || over | ||| CAdES-C ||| | Archive | |
|||| ||digital | ||+------------+|| | | | |||| ||digital | ||+------------+|| | | |
|||| ||signature | || or || |Timestamp | | |||| ||signature | || or || |Timestamp | |
skipping to change at page 27, line 36 skipping to change at page 28, line 41
||| +-------------+ | |certificate | | | ||| +-------------+ | |certificate | | |
||| | | and | | | ||| | | and | | |
||+----------------------------------+ |revocation | | | ||+----------------------------------+ |revocation | | |
|| | values | | | || | values | | |
|| +------------+ | | || +------------+ | |
|+----------------------------------------------------+ | |+----------------------------------------------------+ |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
Figure 10: Illustration of CAdES-A Figure 10: Illustration of CAdES-A
4.5 Arbitration 4.5. Arbitration
The CAdES-C may be used for arbitration should there be a dispute The CAdES-C may be used for arbitration should there be a dispute
between the signer and verifier, provided that: between the signer and verifier, provided that:
- the arbitrator knows where to retrieve the signer's certificate - the arbitrator knows where to retrieve the signer's certificate
(if not already present), all the cross-certificates and the (if not already present), all the cross-certificates and the
required CRLs, ACRLs or OCSP responses referenced in the CAdES-C; required CRLs, ACRLs, or OCSP responses referenced in the
CAdES-C;
- when time-stamping in the CAdES-T is being used, the certificate - when time-stamping in the CAdES-T is being used, the certificate
from the TSU that has issued the time-stamp token in the CAdES-T from the TSU that has issued the time-stamp token in the CAdES-T
format is still within its validity period; format is still within its validity period;
- when time-stamping in the CAdES-T is being used, the certificate - when time-stamping in the CAdES-T is being used, the certificate
from the TSU that has issued the time-stamp token in the CAdES-T from the TSU that has issued the time-stamp token in the CAdES-T
format is not revoked at the time of arbitration; format is not revoked at the time of arbitration;
- when time-marking in the CAdES-T is being used, a reliable audit - when time-marking in the CAdES-T is being used, a reliable audit
trail from the Time-Marking Authority is available for trail from the Time-Marking Authority is available for
examination regarding the time; examination regarding the time;
- none of the private keys corresponding to the certificates used - none of the private keys corresponding to the certificates used
to verify the signature chain have ever been compromised; to verify the signature chain have ever been compromised;
skipping to change at page 28, line 18 skipping to change at page 29, line 22
- when time-marking in the CAdES-T is being used, a reliable audit - when time-marking in the CAdES-T is being used, a reliable audit
trail from the Time-Marking Authority is available for trail from the Time-Marking Authority is available for
examination regarding the time; examination regarding the time;
- none of the private keys corresponding to the certificates used - none of the private keys corresponding to the certificates used
to verify the signature chain have ever been compromised; to verify the signature chain have ever been compromised;
- the cryptography used at the time the CAdES-C was built has not - the cryptography used at the time the CAdES-C was built has not
been broken at the time the arbitration is performed; and been broken at the time the arbitration is performed; and
- If the signature policy can be explicit or implicitly identified - if the signature policy can be explicitly or implicitly
then an arbitrator is able to determine the rules required to identified, then an arbitrator is able to determine the rules
validate the electronic signature. required to validate the electronic signature.
4.6 Validation process 4.6. Validation Process
The Validation Process validates an electronic signature, the output The validation process validates an electronic signature; the output
status of the validation process can be: status of the validation process can be:
- invalid; - invalid;
- incomplete validation; or - incomplete validation; or
- valid. - valid.
An Invalid response indicates that either the signature format is An invalid response indicates that either the signature format is
incorrect or that the digital signature value fails verification (e.g. incorrect or that the digital signature value fails verification
the integrity check on the digital signature value fails or any of the (e.g., the integrity check on the digital signature value fails, or
certificates on which the digital signature verification depends is any of the certificates on which the digital signature verification
known to be invalid or revoked). depends is known to be invalid or revoked).
An Incomplete Validation response indicates that the signature An incomplete validation response indicates that the signature
validation status is currently unknown. In the case of incomplete validation status is currently unknown. In the case of incomplete
validation, additional information may be made available to the validation, additional information may be made available to the
application or user, thus allowing them to decide what to do with the application or user, thus allowing them to decide what to do with the
electronic signature. In the case of incomplete validation, the electronic signature. In the case of incomplete validation, the
electronic signature may be checked again at some later time when electronic signature may be checked again at some later time when
additional information becomes available. additional information becomes available.
NOTE: For example; an incomplete validation may be because all the NOTE: For example, an incomplete validation may be because all the
required certificates are not available or the grace period is required certificates are not available or the grace period is not
not completed. completed.
A Valid response indicates that the signature has passed verification A valid response indicates that the signature has passed
and it complies with the signature validation policy. verification, and it complies with the signature validation policy.
Example validation sequences are illustrated in annex B. Example validation sequences are illustrated in Annex B.
5 Electronic signature attributes 5. Electronic Signature Attributes
This section builds upon the existing Cryptographic Message Syntax This section builds upon the existing Cryptographic Message Syntax
(CMS), as defined in RFC 3852 [4], and Enhanced Security Services (CMS), as defined in RFC 3852 [4], and Enhanced Security Services
(ESS), as defined in RFC 2634 [5]. The overall structure of Electronic (ESS), as defined in RFC 2634 [5]. The overall structure of an
Signature is as defined in CMS. The Electronic Signature (ES) uses Electronic Signature is as defined in CMS. The Electronic Signature
attributes defined in CMS, ESS and the present document. The present (ES) uses attributes defined in CMS, ESS, and the present document.
document defines ES attributes which it uses and are not defined The present document defines ES attributes that it uses and that are
elsewhere. not defined elsewhere.
The mandated set of attributes and the digital signature value is The mandated set of attributes and the digital signature value is
defined as the minimum Electronic Signature (ES) required by the defined as the minimum Electronic Signature (ES) required by the
present document. A signature policy may mandate that other signed present document. A signature policy may mandate that other signed
attributes are present. attributes be present.
5.1 General syntax 5.1. General Syntax
The general syntax of the ES is as defined in CMS (RFC 3852 [4]). The general syntax of the ES is as defined in CMS (RFC 3852 [4]).
NOTE: CMS defines content types for id-data, id-signedData, id- NOTE: CMS defines content types for id-data, id-signedData,
envelopedData, id-digestedData, id-encryptedData, and id- id-envelopedData, id-digestedData, id-encryptedData, and
authenticatedData. Although CMS permits other documents to id-authenticatedData. Although CMS permits other documents to
define other content types, the ASN.1 type defined should not define other content types, the ASN.1 type defined should not be a
be a CHOICE type. The present document does not define other CHOICE type. The present document does not define other content
content types. types.
5.2 Data content type 5.2. Data Content Type
The data content type of the ES is as defined in CMS (RFC 3852 [4]). The data content type of the ES is as defined in CMS (RFC 3852 [4]).
NOTE: If the content type is id-data, it is recommended that the NOTE: If the content type is id-data, it is recommended that the
content is encoded using MIME and that the MIME type is used content be encoded using MIME, and that the MIME type is used to
to identify the presentation format of the data. See annex F.1 identify the presentation format of the data. See Annex F.1 for
for an example of using MIME to identify encoding type. an example of using MIME to identify the encoding type.
5.3 Signed-data content type 5.3. Signed-data Content Type
The signed-data content type of the ES is as defined in CMS (RFC 3852 The Signed-data content type of the ES is as defined in CMS (RFC 3852
[4]). [4]).
5.4 SignedData type 5.4. SignedData Type
The syntax of the SignedData of the ES is as defined in CMS (RFC 3852 The syntax of the SignedData of the ES is as defined in CMS (RFC 3852
[4]). [4]).
The fields of type SignedData have the meanings as defined in CMS The fields of type SignedData are as defined in CMS (RFC 3852 [4]).
(RFC 3852 [4]).
The identification of signer's certificate used to create the signature The identification of a signer's certificate used to create the
is always signed (see section 5.7.3). The validation policy may specify signature is always signed (see Section 5.7.3). The validation
requirements for the presence of certain certificates. The degenerate policy may specify requirements for the presence of certain
case where there are no signers is not valid in the present document. certificates. The degenerate case, where there are no signers, is
not valid in the present document.
5.5 EncapsulatedContentInfo type 5.5. EncapsulatedContentInfo Type
The syntax of the EncapsulatedContentInfo type ES is as defined in CMS The syntax of the EncapsulatedContentInfo type ES is as defined in
(RFC 3852 [4]). CMS (RFC 3852 [4]).
For the purpose of long term validation as defined by the present For the purpose of long-term validation, as defined by the present
document, it is advisable that either the eContent is present, or the document, it is advisable that either the eContent is present, or the
data which is signed is archived in such as way as to preserve any data data that is signed is archived in such as way as to preserve any
encoding. It is important that the OCTET STRING used to generate the data encoding. It is important that the OCTET STRING used to
signature remains the same every time either the verifier or an generate the signature remains the same every time either the
arbitrator validates the signature. verifier or an arbitrator validates the signature.
NOTE: The eContent is optional in CMS : NOTE: The eContent is optional in CMS :
- When it is present, this allows the signed data to be - When it is present, this allows the signed data to be
encapsulated in the SignedData structure, which then encapsulated in the SignedData structure, which then
contains both the signed data and the signature. However, contains both the signed data and the signature. However,
the signed data may only be accessed by a verifier able to the signed data may only be accessed by a verifier able to
decode the ASN.1 encoded SignedData structure. decode the ASN.1 encoded SignedData structure.
- When it is missing, this allows the signed data to be sent - When it is missing, this allows the signed data to be sent
or stored separately from the signature and the SignedData or stored separately from the signature, and the SignedData
structure only contains the signature. It is in the case structure only contains the signature. It is, in the case
of signature only that the data which is signed needs to be of the signature, only the data that is signed that needs to
stored and distributed in such as way as to preserve any be stored and distributed in such as way as to preserve any
data encoding. data encoding.
The degenerate case where there are no signers is not valid in the The degenerate case where there are no signers is not valid in the
present document. present document.
5.6 SignerInfo type 5.6. SignerInfo Type
The syntax of the SignerInfo type ES is as defined in CMS (RFC 3852 The syntax of the SignerInfo type ES is as defined in CMS (RFC 3852
[4]). [4]).
Per-signer information is represented in the type SignerInfo. In the Per-signer information is represented in the type SignerInfo. In the
case of multiple independent signatures (see section B.5), there is an case of multiple independent signatures (see Annex B.5), there is an
instance of this field for each signer. instance of this field for each signer.
The fields of type SignerInfo have the meanings defined in CMS (RFC The fields of type SignerInfo have the meanings defined in CMS (RFC
3852 [4]) but the signedAttrs field shall contain the following 3852 [4]), but the signedAttrs field shall contain the following
attributes: attributes:
- content-type as defined in section 5.7.1; and - content-type, as defined in Section 5.7.1; and
- message-digest as defined in section 5.7.2;
- signing-certificate as defined in section 5.7.3. - message-digest, as defined in Section 5.7.2;
5.6.1 Message digest calculation process - signing-certificate, as defined in Section 5.7.3.
5.6.1. Message Digest Calculation Process
The message digest calculation process is as defined in CMS (RFC 3852 The message digest calculation process is as defined in CMS (RFC 3852
[4]). [4]).
5.6.2 Message signature generation process 5.6.2. Message Signature Generation Process
The input to the message signature generation process is as defined in The input to the message signature generation process is as defined
CMS (RFC 3852 [4]). in CMS (RFC 3852 [4]).
5.6.3 Message signature verification process 5.6.3. Message Signature Verification Process
The procedures for message signature verification are defined in CMS The procedures for message signature verification are defined in CMS
(RFC 3852 [4]) and enhanced in the present document: the input to the (RFC 3852 [4]) and enhanced in the present document: the input to the
signature verification process must be the signer's public key which signature verification process must be the signer's public key, which
shall be verified as correct using the signing certificate reference shall be verified as correct using the signing certificate reference
attribute containing a reference to the signing certificate, i.e. attribute containing a reference to the signing certificate, i.e.,
when SigningCertificateV2 from RFC 5035 [16] or SigningCertificate when SigningCertificateV2 from RFC 5035 [16] or SigningCertificate
from ESS [5] is used, the public key from the first certificate from ESS [5] is used, the public key from the first certificate
identified in the sequence of certificate identifiers from identified in the sequence of certificate identifiers from
SigningCertificate must be the key used to verify the digital SigningCertificate must be the key used to verify the digital
signature. signature.
5.7 Basic ES mandatory present attributes 5.7. Basic ES Mandatory Present Attributes
The following attributes shall be present with the signed-data defined The following attributes shall be present with the signed-data
by the present document. The attributes are defined in CMS (RFC 3852 defined by the present document. The attributes are defined in CMS
[4]). (RFC 3852 [4]).
5.7.1 Content type 5.7.1. content-type
The content-type attribute indicates the type of the signed content. The content-type attribute indicates the type of the signed content.
The syntax of the content-type attribute type is as defined in CMS The syntax of the content-type attribute type is as defined in CMS
(RFC 3852 [4]) section 11.1. (RFC 3852 [4]) Section 11.1.
Note 1 : As stated in RFC 3852 [4] , the content-type attribute NOTE 1: As stated in RFC 3852 [4] , the content-type attribute
must have its value (i.e. ContentType) equal to the must have its value (i.e., ContentType) equal to the eContentType
eContentType of the EncapsulatedContentInfo value being of the EncapsulatedContentInfo value being signed.
signed.
Note 2 : For implementations supporting signature generation, if NOTE 2: For implementations supporting signature generation, if
the content-type attribute is id-data, then it is the content-type attribute is id-data, then it is recommended that
recommended that the eContent be encoded using MIME. the eContent be encoded using MIME. For implementations
For implementations supporting signature verification, if supporting signature verification, if the signed data (i.e.,
the signed data (i.e. eContent) is MIME-encoded, then the eContent) is MIME-encoded, then the OID of the content-type
OID of the content-type attribute must be id-data. attribute must be id-data. In both cases, the MIME
In both cases, the MIME content-type(s) must be used to content-type(s) must be used to identify the presentation format
identify the presentation format of the data. See Annex F of the data. See Annex F for further details about the use of
for further details about the use of MIME. MIME.
5.7.2 Message digest 5.7.2. Message Digest
The syntax of the message-digest attribute type of the ES is as defined The syntax of the message-digest attribute type of the ES is as
in CMS (RFC 3852 [4]). defined in CMS (RFC 3852 [4]).
5.7.3 Signing certificate reference attributes 5.7.3. Signing Certificate Reference Attributes
The Signing certificate reference attributes are supported by using The Signing certificate reference attributes are supported by using
either the ESS signing-certificate attribute or the ESS-signing- either the ESS signing-certificate attribute or the
certificate-v2 attribute. ESS-signing-certificate-v2 attribute.
These attributes shall contain a reference to the signer's certificate, These attributes shall contain a reference to the signer's
they are designed to prevent the simple substitution and re-issue certificate; they are designed to prevent simple substitution and
attacks and to allow for a restricted set of certificates to be used in reissue attacks and to allow for a restricted set of certificates to
verifying a signature. They have a compact form (much shorter than the be used in verifying a signature. They have a compact form (much
full certificate) that allows to a certificate to be unambiguously shorter than the full certificate) that allows for a certificate to
identified. be unambiguously identified.
One, and only one, of the following alternative attributes shall be One, and only one, of the following alternative attributes shall be
present with the signedData defined by the present document. present with the signedData, defined by the present document:
- The ESS signing-certificate attribute, defined in ESS [5], must - The ESS signing-certificate attribute, defined in ESS [5], must
be used if the SHA-1 hashing algorithm is used. be used if the SHA-1 hashing algorithm is used.
- The ESS signing-certificate attribute v2, defined in "ESS Update: - The ESS signing-certificate-v2 attribute, defined in "ESS
Adding CertID Algorithm Agility", RFC 5035 [15] which shall be Update: Adding CertID Algorithm Agility", RFC 5035 [15], which
used when other hashing algorithms are to be used. shall be used when other hashing algorithms are to be used.
The certificate to be used to verify the signature shall be identified The certificate to be used to verify the signature shall be
in the sequence (i.e. the certificate from the signer) and the sequence identified in the sequence (i.e., the certificate from the signer),
shall not be empty. The signature validation policy may mandate other and the sequence shall not be empty. The signature validation policy
certificates be present that may include all the certificates up to the may mandate other certificates be present that may include all the
trust anchor. certificates up to the trust anchor.
5.7.3.1 ESS signing certificate attribute definition 5.7.3.1. ESS signing-certificate Attribute Definition
The syntax of the signing-certificate attribute type of the ES is as The syntax of the signing-certificate attribute type of the ES is as
defined in Enhanced Security Services (ESS), RFC 2634 [5] and further defined in Enhanced Security Services (ESS), RFC 2634 [5], and
qualified in the present document. further qualified in the present document.
The sequence of policy information field is not used in the present The sequence of the policy information field is not used in the
document. present document.
The ESS signing-certificate attribute shall be a signed attribute. The ESS signing-certificate attribute shall be a signed attribute.
The encoding of the ESSCertID for this certificate shall include the The encoding of the ESSCertID for this certificate shall include the
issuerSerial field. issuerSerial field.
If present, the issuerAndSerialNumber in SignerIdentifier field of the If present, the issuerAndSerialNumber in SignerIdentifier field of
SignerInfo shall match the issuerSerial field present in ESSCertID. the SignerInfo shall match the issuerSerial field present in
In addition the certHash from ESSCertID shall match the SHA-1 hash of ESSCertID. In addition, the certHash from ESSCertID shall match the
the certificate. The certificate identified shall be used during the SHA-1 hash of the certificate. The certificate identified shall be
signature verification process. If the hash of the certificate does used during the signature verification process. If the hash of the
not match the certificate used to verify the signature, the signature certificate does not match the certificate used to verify the
shall be considered invalid. signature, the signature shall be considered invalid.
NOTE: Where an attribute certificate is used by the signer to NOTE: Where an attribute certificate is used by the signer to
associate a role, or other attributes of the signer, with the associate a role, or other attributes of the signer, with the
electronic signature, this is placed in the signer-attributes electronic signature; this is placed in the signer-attributes
attribute as defined in section 5.8.3. attribute as defined in Section 5.8.3.
5.7.3.2 ESS signing certificate v2 attribute definition 5.7.3.2. ESS signing-certificate-v2 Attribute Definition
The ESS signing-certificate v2 attribute is similar to the ESS The ESS signing-certificate-v2 attribute is similar to the ESS
signing-certificate defined above, except that this attribute can be signing-certificate defined above, except that this attribute can be
used with hashing algorithms other than SHA-1. used with hashing algorithms other than SHA-1.
The syntax of the signing-certificate v2 attribute type of the ES is as The syntax of the signing-certificate-v2 attribute type of the ES is
defined in "ESS Update: Adding CertID Algorithm Agility", RFC 5035 [15] as defined in "ESS Update: Adding CertID Algorithm Agility", RFC 5035
and further qualified in the present document. [15], and further qualified in the present document.
The sequence of policy information field is not used in the present The sequence of the policy information field is not used in the
document. present document.
This attribute shall be used in the same manner as defined above for This attribute shall be used in the same manner as defined above for
the ESS signing-certificate attribute. the ESS signing-certificate attribute.
The object identifier for this attribute is: The object identifier for this attribute is:
id-aa-signingCertificateV2 OBJECT IDENTIFIER ::= id-aa-signingCertificateV2 OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
smime(16) id-aa(2) 47 } smime(16) id-aa(2) 47 }
If present, the issuerAndSerialNumber in SignerIdentifier field of
the SignerInfo shall match the issuerSerial field present in
ESSCertIDv2. In addition, the certHash from ESSCertIDv2 shall match
the hash of the certificate computed using the hash function
specified in the hashAlgorithm field. The certificate identified
shall be used during the signature verification process. If the hash
of the certificate does not match the certificate used to verify the
signature, the signature shall be considered invalid.
If present, the issuerAndSerialNumber in SignerIdentifier field of the NOTE 1: Where an attribute certificate is used by the signer to
SignerInfo shall match the issuerSerial field present in ESSCertID.
In addition the certHash from ESSCertID shall match the SHA-1 hash of
the certificate. The certificate identified shall be used during the
signature verification process. If the hash of the certificate does
not match the certificate used to verify the signature, the signature
shall be considered invalid.
Note 1 : Where an attribute certificate is used by the signer to
associate a role, or other attributes of the signer, with the associate a role, or other attributes of the signer, with the
electronic signature, this is placed in the signer-attributes electronic signature; this is placed in the signer-attributes
attribute as defined in section 5.8.3. attribute as defined in Section 5.8.3.
Note 2 : RFC 3126 was using the other signing certificate attribute NOTE 2: RFC 3126 was using the other signing-certificate attribute
(see section 5.7.3.3) for the same purpose. Its use is now (see Section 5.7.3.3) for the same purpose. Its use is now
deprecated, since this structure is simpler. deprecated, since this structure is simpler.
5.7.3.3 Other signing certificate attribute definition 5.7.3.3. Other signing-certificate Attribute Definition
RFC 3126 was using the other signing certificate attribute as RFC 3126 was using the other signing-certificate attribute as an
an alternative to the ESS signing-certificate when hashing algorithms alternative to the ESS signing-certificate when hashing algorithms
other than SHA-1 were being used. Its use is now deprecated, since other than SHA-1 were being used. Its use is now deprecated, since
the structure of the general-signing-certificate-v2 attribute is the structure of the signing-certificate-v2 attribute is simpler.
simpler. Its description is however still present in this version for Its description is however still present in this version for
backwards compatibility. backwards compatibility.
id-aa-ets-otherSigCert OBJECT IDENTIFIER ::= { iso(1) id-aa-ets-otherSigCert OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
smime(16) id-aa(2) 19 } smime(16) id-aa(2) 19 }
The other-signing-certificate attribute value has the ASN.1 syntax The other-signing-certificate attribute value has the ASN.1 syntax
OtherSigningCertificate: OtherSigningCertificate:
OtherSigningCertificate ::= SEQUENCE { OtherSigningCertificate ::= SEQUENCE {
skipping to change at page 34, line 26 skipping to change at page 36, line 4
OtherCertID ::= SEQUENCE { OtherCertID ::= SEQUENCE {
otherCertHash OtherHash, otherCertHash OtherHash,
issuerSerial IssuerSerial OPTIONAL } issuerSerial IssuerSerial OPTIONAL }
OtherHash ::= CHOICE { OtherHash ::= CHOICE {
sha1Hash OtherHashValue, -- This contains a SHA-1 hash sha1Hash OtherHashValue, -- This contains a SHA-1 hash
otherHash OtherHashAlgAndValue} otherHash OtherHashAlgAndValue}
OtherHashValue ::= OCTET STRING OtherHashValue ::= OCTET STRING
OtherHashAlgAndValue ::= SEQUENCE { OtherHashAlgAndValue ::= SEQUENCE {
hashAlgorithm AlgorithmIdentifier, hashAlgorithm AlgorithmIdentifier,
hashValue OtherHashValue } hashValue OtherHashValue }
5.8 Additional mandatory attributes for Explicit Policy-based 5.8. Additional Mandatory Attributes for Explicit Policy-based
Electronic Signatures Electronic Signatures
5.8.1 Signature policy identifier 5.8.1. signature-policy-identifier
The present document mandates that for CAdES-EPES a reference to the The present document mandates that for CAdES-EPES, a reference to the
signature policy is included in the signedData. This reference is signature policy is included in the signedData. This reference is
explicitly identified. A signature policy defines the rules for explicitly identified. A signature policy defines the rules for
creation and validation of an electronic signature, is included as a creation and validation of an electronic signature, and is included
signed attribute with every Explicit Policy-based Electronic Signature. as a signed attribute with every Explicit Policy-based Electronic
The signature-policy-identifier shall be a signed attribute. Signature. The signature-policy-identifier shall be a signed
attribute.
The following object identifier identifies signature-policy-identifier The following object identifier identifies the
attribute: signature-policy-identifier attribute:
id-aa-ets-sigPolicyId OBJECT IDENTIFIER ::= { iso(1) id-aa-ets-sigPolicyId OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
smime(16) id-aa(2) 15 } smime(16) id-aa(2) 15 }
signature-policy-identifier attribute values have ASN.1 type signature-policy-identifier attribute values have ASN.1 type
SignaturePolicyIdentifier: SignaturePolicyIdentifier:
SignaturePolicyIdentifier ::= CHOICE { SignaturePolicyIdentifier ::= CHOICE {
signaturePolicyId SignaturePolicyId, signaturePolicyId SignaturePolicyId,
skipping to change at page 35, line 4 skipping to change at page 36, line 36
smime(16) id-aa(2) 15 } smime(16) id-aa(2) 15 }
signature-policy-identifier attribute values have ASN.1 type signature-policy-identifier attribute values have ASN.1 type
SignaturePolicyIdentifier: SignaturePolicyIdentifier:
SignaturePolicyIdentifier ::= CHOICE { SignaturePolicyIdentifier ::= CHOICE {
signaturePolicyId SignaturePolicyId, signaturePolicyId SignaturePolicyId,
signaturePolicyImplied SignaturePolicyImplied signaturePolicyImplied SignaturePolicyImplied
-- not used in this version -- not used in this version
} }
SignaturePolicyId ::= SEQUENCE { SignaturePolicyId ::= SEQUENCE {
sigPolicyId SigPolicyId, sigPolicyId SigPolicyId,
sigPolicyHash SigPolicyHash, sigPolicyHash SigPolicyHash,
sigPolicyQualifiers SEQUENCE SIZE (1..MAX) OF sigPolicyQualifiers SEQUENCE SIZE (1..MAX) OF
SigPolicyQualifierInfo OPTIONAL} SigPolicyQualifierInfo OPTIONAL}
SignaturePolicyImplied ::= NULL SignaturePolicyImplied ::= NULL
The sigPolicyId field contains an object-identifier that uniquely
The sigPolicyId field contains an object-identifier which uniquely
identifies a specific version of the signature policy. The syntax of identifies a specific version of the signature policy. The syntax of
this field is as follows: this field is as follows:
SigPolicyId ::= OBJECT IDENTIFIER SigPolicyId ::= OBJECT IDENTIFIER
The sigPolicyHash field optionally contains the identifier of the hash The sigPolicyHash field optionally contains the identifier of the
algorithm and the hash of the value of the signature policy. The hash algorithm and the hash of the value of the signature policy.
hashValue within the sigPolicyHash may be set to zero to indicate The hashValue within the sigPolicyHash may be set to zero to indicate
that the policy hash value is not known. that the policy hash value is not known.
NOTE: The use of zero policy hash value is to ensure backward NOTE: The use of a zero sigPolicyHash value is to ensure backwards
compatibility with earlier versions of the current document. compatibility with earlier versions of the current document. If
If hashValue is zero then the hash value should not be sigPolicyHash is zero, then the hash value should not be checked
checked against the calculated hash value of signature against the calculated hash value of the signature policy.
policy.
If the signature policy is defined using ASN.1, then the hash is If the signature policy is defined using ASN.1, then the hash is
calculated on the value without the outer type and length fields and calculated on the value without the outer type and length fields, and
the hashing algorithm shall be as specified in the field sigPolicyHash. the hashing algorithm shall be as specified in the field
sigPolicyHash.
If the signature policy is defined using another structure, the type of If the signature policy is defined using another structure, the type
structure and the hashing algorithm shall be either specified as part of structure and the hashing algorithm shall be either specified as
of the signature policy, or indicated using a signature policy part of the signature policy, or indicated using a signature policy
qualifier. qualifier.
SigPolicyHash ::= OtherHashAlgAndValue SigPolicyHash ::= OtherHashAlgAndValue
OtherHashAlgAndValue ::= SEQUENCE { OtherHashAlgAndValue ::= SEQUENCE {
hashAlgorithm AlgorithmIdentifier, hashAlgorithm AlgorithmIdentifier,
hashValue OtherHashValue } hashValue OtherHashValue }
OtherHashValue ::= OCTET STRING OtherHashValue ::= OCTET STRING
A signature policy identifier may be qualified with other information A Signature Policy Identifier may be qualified with other information
about the qualifier. The semantics and syntax of the qualifier is as about the qualifier. The semantics and syntax of the qualifier is as
associated with the object-identifier in the sigPolicyQualifierId associated with the object-identifier in the sigPolicyQualifierId
field. The general syntax of this qualifier is as follows: field. The general syntax of this qualifier is as follows:
SigPolicyQualifierInfo ::= SEQUENCE { SigPolicyQualifierInfo ::= SEQUENCE {
sigPolicyQualifierId SigPolicyQualifierId, sigPolicyQualifierId SigPolicyQualifierId,
sigQualifier ANY DEFINED BY sigPolicyQualifierId } sigQualifier ANY DEFINED BY sigPolicyQualifierId }
The present document specifies the following qualifiers: The present document specifies the following qualifiers:
- spuri: this contains the web URI or URL reference to the - spuri: this contains the web URI or URL reference to the
signature policy, and signature policy, and
- sp-user-notice: this contains a user notice which should be - sp-user-notice: this contains a user notice that should be
displayed whenever the signature is validated. displayed whenever the signature is validated.
sigpolicyQualifierIds defined in the present document: sigpolicyQualifierIds defined in the present document:
SigPolicyQualifierId ::= OBJECT IDENTIFIER SigPolicyQualifierId ::= OBJECT IDENTIFIER
id-spq-ets-uri OBJECT IDENTIFIER ::= { iso(1) id-spq-ets-uri OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
smime(16) id-spq(5) 1 } smime(16) id-spq(5) 1 }
SPuri ::= IA5String SPuri ::= IA5String
skipping to change at page 36, line 36 skipping to change at page 38, line 39
NoticeReference ::= SEQUENCE { NoticeReference ::= SEQUENCE {
organization DisplayText, organization DisplayText,
noticeNumbers SEQUENCE OF INTEGER } noticeNumbers SEQUENCE OF INTEGER }
DisplayText ::= CHOICE { DisplayText ::= CHOICE {
visibleString VisibleString (SIZE (1..200)), visibleString VisibleString (SIZE (1..200)),
bmpString BMPString (SIZE (1..200)), bmpString BMPString (SIZE (1..200)),
utf8String UTF8String (SIZE (1..200)) } utf8String UTF8String (SIZE (1..200)) }
5.9 CMS imported optional attributes 5.9. CMS Imported Optional Attributes
The following attributes may be present with the signed-data, the The following attributes may be present with the signed-data; the
attributes are defined in CMS (RFC 3852 [4]) and are imported into the attributes are defined in CMS (RFC 3852 [4]) and are imported into
present document. Were appropriated the attributes are qualified and the present document. Where appropriate, the attributes are
profiled by the present document. qualified and profiled by the present document.
5.9.1 Signing time 5.9.1. signing-time
The signing-time attribute specifies the time at which the signer The signing-time attribute specifies the time at which the signer
claims to have performed the signing process. claims to have performed the signing process.
Signing-time attribute values for ES have the ASN.1 type SigningTime Signing-time attribute values for ES have the ASN.1 type SigningTime
as defined in CMS (RFC 3852 [4]). as defined in CMS (RFC 3852 [4]).
NOTE: RFC 3852 [4] states that dates between 1 January 1950 and 31 NOTE: RFC 3852 [4] states that dates between January 1, 1950 and
December 2049 (inclusive) must be encoded as UTCTime. Any December 31, 2049 (inclusive) must be encoded as UTCTime. Any
dates with year values before 1950 or after 2049 must be dates with year values before 1950 or after 2049 must be encoded
encoded as GeneralizedTime. as GeneralizedTime.
5.9.2 Countersignature 5.9.2. countersignature
The counterSignature attribute values for ES have ASN.1 type The countersignature attribute values for ES have ASN.1 type
CounterSignature as defined in CMS (RFC 3852 [4]). A counterSignature CounterSignature, as defined in CMS (RFC 3852 [4]). A
attribute shall be an unsigned attribute. countersignature attribute shall be an unsigned attribute.
5.10 ESS imported optional attributes 5.10. ESS-Imported Optional Attributes
The following attributes may be present with the signed-data defined by The following attributes may be present with the signed-data defined
the present document. The attributes are defined in ESS and are by the present document. The attributes are defined in ESS and are
imported into the present document and were appropriate qualified and imported into the present document and are appropriately qualified
profiled by the present document. and profiled by the present document.
5.10.1 Content reference attribute 5.10.1. content-reference Attribute
The content-reference attribute is a link from one SignedData to The content-reference attribute is a link from one SignedData to
another. It may be used to link a reply to the original message to another. It may be used to link a reply to the original message to
which it refers, or to incorporate by reference one SignedData into which it refers, or to incorporate by reference one SignedData into
another. The content-reference attribute shall be a signed attribute. another. The content-reference attribute shall be a signed
attribute.
Content-reference attribute values for ES have ASN.1 type content-reference attribute values for ES have ASN.1 type
ContentReference as defined in ESS (RFC 2634 [5]). ContentReference, as defined in ESS (RFC 2634 [5]).
The content-reference attribute shall be used as defined in ESS (RFC The content-reference attribute shall be used as defined in ESS (RFC
2634 [5]). 2634 [5]).
5.10.2 Content identifier attribute 5.10.2. content-identifier Attribute
The content-identifier attribute provides an identifier for the signed The content-identifier attribute provides an identifier for the
content for use when reference may be later required to that content, signed content, for use when a reference may be later required to
for example in the content reference attribute in other signed data that content; for example, in the content-reference attribute in
sent later. The content-identifier shall be a signed attribute. other signed data sent later. The content-identifier shall be a
signed attribute.
content-identifier attribute type values for of the ES have ASN.1 type content-identifier attribute type values for the ES have an ASN.1
ContentIdentifier as defined in ESS (RFC 2634 [5]). type ContentIdentifier, as defined in ESS (RFC 2634 [5]).
The minimal content-identifier attribute should contain a concatenation The minimal content-identifier attribute should contain a
of user-specific identification information (such as a user name or concatenation of user-specific identification information (such as a
public keying material identification information), a GeneralizedTime user name or public keying material identification information), a
string, and a random number. GeneralizedTime string, and a random number.
5.10.3 Content hints attribute 5.10.3. content-hints Attribute
The content-hints attribute provides information on the innermost The content-hints attribute provides information on the innermost
signed content of a multi-layer message where one content is signed content of a multi-layer message where one content is
encapsulated in another. encapsulated in another.
The syntax of the content-hints attribute type of the ES as defined in The syntax of the content-hints attribute type of the ES is as
ESS (RFC 2634 [5]). defined in ESS (RFC 2634 [5]).
When used to indicate the precise format of the data to be presented to When used to indicate the precise format of the data to be presented
the user the following rules apply: to the user, the following rules apply:
- the contentType indicates the type of the associated content. - the contentType indicates the type of the associated content.
It is an object identifier (i.e., a unique string of integers)
It is an object identifier (i.e. a unique string of integers)
assigned by an authority that defines the content type; and assigned by an authority that defines the content type; and
- when the contentType is id-data, the contentDescription shall - when the contentType is id-data, the contentDescription shall
define the presentation format, the format may be defined by MIME define the presentation format; the format may be defined by
types. MIME types.
When the format of the content is defined by MIME types the following When the format of the content is defined by MIME types, the
rules apply: following rules apply:
- the contentType shall be id-data as defined in CMS (RFC 3852 - the contentType shall be id-data, as defined in CMS (RFC 3852
[4]); [4]);
- the contentDescription shall be used to indicate the encoding of - the contentDescription shall be used to indicate the encoding of
the data in accordance with the rules defined RFC 2045 [6], see the data, in accordance with the rules defined RFC 2045 [6]; see
annex F for an example structured contents and MIME. Annex F for an example of structured contents and MIME.
NOTE 1: id-data OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840) NOTE 1: id-data OBJECT IDENTIFIER ::= { iso(1) member-body(2) us(840)
rsadsi(113549) pkcs(1) pkcs7(7) 1 } rsadsi(113549) pkcs(1) pkcs7(7) 1 }
NOTE 2: contentDescription is optional in ESS (RFC 2634 [5]). It may NOTE 2: contentDescription is optional in ESS (RFC 2634 [5]). It may
be used to complement contentTypes defined elsewhere , such be used to complement contentTypes defined elsewhere; such
definitions are outside the scope of the present document. definitions are outside the scope of the present document.
5.11 Additional optional attributes defined in the present document 5.11. Additional Optional Attributes Defined in the Present Document
This section defines a number of attributes that may be used to This section defines a number of attributes that may be used to
indicate additional information to a verifier : indicate additional information to a verifier :
a) the type of commitment from the signer, and/or a) the type of commitment from the signer, and/or
b) the claimed location where the signature is performed, and/or b) the claimed location where the signature is performed, and/or
c) claimed attributes or certified attributes of the signer, and/or c) claimed attributes or certified attributes of the signer,
and/or
d) a content time-stamp applied before the content was signed. d) a content time-stamp applied before the content was signed.
5.11.1 Commitment type indication attribute 5.11.1. commitment-type-indication Attribute
There may be situations where a signer wants to explicitly indicate to There may be situations where a signer wants to explicitly indicate
a verifier that by signing the data, it illustrates a type of to a verifier that by signing the data, it illustrates a type of
commitment on behalf of the signer. The commitment-type-indication commitment on behalf of the signer. The commitment-type-indication
attribute conveys such information. attribute conveys such information.
The commitment-type-indication attribute shall be a signed attribute. The commitment-type-indication attribute shall be a signed attribute.
The commitment type may be: The commitment type may be:
- defined as part of the signature policy, in which case the - defined as part of the signature policy, in which case, the
commitment type has precise semantics that is defined as part of commitment type has precise semantics that are defined as part
the signature policy; and of the signature policy; and
- be a registered type, in which case the commitment type has - be a registered type, in which case, the commitment type has
precise semantics defined by registration, under the rules of the precise semantics defined by registration, under the rules of
registration authority. Such a registration authority may be a the registration authority. Such a registration authority may
trading association or a legislative authority. be a trading association or a legislative authority.
The signature policy specifies a set of attributes that it The signature policy specifies a set of attributes that it
"recognizes". This "recognized" set includes all those commitment "recognizes". This "recognized" set includes all those commitment
types defined as part of the signature policy as well as any externally types defined as part of the signature policy, as well as any
defined commitment types that the policy may choose to recognize. Only externally defined commitment types that the policy may choose to
recognized commitment types are allowed in this field. recognize. Only recognized commitment types are allowed in this
field.
The following object identifier identifies the commitment-type- The following object identifier identifies the
indication attribute: commitment-type-indication attribute:
id-aa-ets-commitmentType OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-commitmentType OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 16} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 16}
commitment-type-indication attribute values have ASN.1 type commitment-type-indication attribute values have ASN.1 type
CommitmentTypeIndication. CommitmentTypeIndication.
CommitmentTypeIndication ::= SEQUENCE { CommitmentTypeIndication ::= SEQUENCE {
commitmentTypeId CommitmentTypeIdentifier, commitmentTypeId CommitmentTypeIdentifier,
commitmentTypeQualifier SEQUENCE SIZE (1..MAX) OF commitmentTypeQualifier SEQUENCE SIZE (1..MAX) OF
skipping to change at page 40, line 5 skipping to change at page 42, line 36
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) cti(6) 4} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) cti(6) 4}
id-cti-ets-proofOfApproval OBJECT IDENTIFIER ::= { iso(1) id-cti-ets-proofOfApproval OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16)
cti(6) 5} cti(6) 5}
id-cti-ets-proofOfCreation OBJECT IDENTIFIER ::= { iso(1) id-cti-ets-proofOfCreation OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16)
cti(6) 6} cti(6) 6}
These generic commitment types have the following meaning: These generic commitment types have the following meanings:
Proof of origin indicates that the signer recognizes to have created, Proof of origin indicates that the signer recognizes to have created,
approved and sent the message. approved, and sent the message.
Proof of receipt indicates that signer recognizes to have received the Proof of receipt indicates that signer recognizes to have received
content of the message. the content of the message.
Proof of delivery indicates that the TSP providing that indication has Proof of delivery indicates that the TSP providing that indication
delivered a message in a local store accessible to the recipient of the has delivered a message in a local store accessible to the recipient
message. of the message.
Proof of sender indicates that the entity providing that indication has Proof of sender indicates that the entity providing that indication
sent the message (but not necessarily created it). has sent the message (but not necessarily created it).
Proof of approval indicates that the signer has approved the content of Proof of approval indicates that the signer has approved the content
the message. of the message.
Proof of creation indicates that the signer has created the message Proof of creation indicates that the signer has created the message
(but not necessarily approved, nor sent it). (but not necessarily approved, nor sent it).
5.11.2 Signer location attribute 5.11.2. signer-location Attribute
The signer-location attribute specifies a mnemonic for an address The signer-location attribute specifies a mnemonic for an address
associated with the signer at a particular geographical (e.g. city) associated with the signer at a particular geographical (e.g., city)
location. The mnemonic is registered in the country in which the location. The mnemonic is registered in the country in which the
signer is located and is used in the provision of the Public Telegram signer is located and is used in the provision of the Public Telegram
Service (according to ITU-T Recommendation F.1 [11]). Service (according to ITU-T Recommendation F.1 [11]).
The signer-location attribute shall be a signed attribute. The The signer-location attribute shall be a signed attribute. The
following object identifier identifies the signer-location attribute: following object identifier identifies the signer-location attribute:
id-aa-ets-signerLocation OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-signerLocation OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 17} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 17}
Signer-location attribute values have ASN.1 type SignerLocation: Signer-location attribute values have ASN.1 type SignerLocation:
SignerLocation ::= SEQUENCE { -- at least one of the following shall be
present
SignerLocation ::= SEQUENCE {
-- at least one of the following shall be present:
countryName [0] DirectoryString OPTIONAL, countryName [0] DirectoryString OPTIONAL,
-- As used to name a Country in X.500 -- As used to name a Country in X.500
localityName [1] DirectoryString OPTIONAL, localityName [1] DirectoryString OPTIONAL,
-- As used to name a locality in X.500 -- As used to name a locality in X.500
postalAdddress [2] PostalAddress OPTIONAL } postalAdddress [2] PostalAddress OPTIONAL }
PostalAddress ::= SEQUENCE SIZE(1..6) OF DirectoryString PostalAddress ::= SEQUENCE SIZE(1..6) OF DirectoryString
5.11.3 Signer attributes attribute 5.11.3. signer-attributes Attribute
The signer-attributes attribute specifies additional attributes of the The signer-attributes attribute specifies additional attributes of
signer (e.g. role). It may be either: the signer (e.g., role). It may be either:
- claimed attributes of the signer; or - claimed attributes of the signer; or
- certified attributes of the signer. - certified attributes of the signer.
The signer-attributes attribute shall be a signed attribute. The The signer-attributes attribute shall be a signed attribute. The
following object identifier identifies the signer-attribute attribute: following object identifier identifies the signer-attribute
attribute:
id-aa-ets-signerAttr OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-signerAttr OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 18} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 18}
signer-attributes values have ASN.1 type SignerAttribute: signer-attributes values have ASN.1 type SignerAttribute:
SignerAttribute ::= SEQUENCE OF CHOICE { SignerAttribute ::= SEQUENCE OF CHOICE {
claimedAttributes [0] ClaimedAttributes, claimedAttributes [0] ClaimedAttributes,
certifiedAttributes [1] CertifiedAttributes } certifiedAttributes [1] CertifiedAttributes }
ClaimedAttributes ::= SEQUENCE OF Attribute ClaimedAttributes ::= SEQUENCE OF Attribute
CertifiedAttributes ::= AttributeCertificate CertifiedAttributes ::= AttributeCertificate
-- as defined in RFC 3281: see Section 4.1.
NOTE 1: Only a single signer-attributes can be used NOTE 1: Only a single signer-attributes can be used.
NOTE 2: The claimedAttributes and certifiedAttributes fields are as NOTE 2: Attribute and AttributeCertificate are as defined
defined in ITU-T Recommendations X.501 [9] and X.509 [1]. respectively in ITU-T Recommendations X.501 [9] and X.509 [1].
5.11.4 Content time-stamp 5.11.4. content-time-stamp Attribute
The content-time-stamp attribute is an attribute which is the time- The content-time-stamp attribute is an attribute that is the
stamp token of the signed data content before it is signed. time-stamp token of the signed data content before it is signed. The
The content-time-stamp attribute shall be a signed attribute. content-time-stamp attribute shall be a signed attribute.
The following object identifier identifies the content-time-stamp The following object identifier identifies the content-time-stamp
attribute: attribute:
id-aa-ets-contentTimestamp OBJECT IDENTIFIER ::= id-aa-ets-contentTimestamp OBJECT IDENTIFIER ::=
{ iso(1) member- body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member- body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 20} smime(16) id-aa(2) 20}
Content-time-stamp attribute values have ASN.1 type ContentTimestamp: content-time-stamp attribute values have ASN.1 type ContentTimestamp:
ContentTimestamp ::= TimeStampToken ContentTimestamp ::= TimeStampToken
The value of messageImprint of TimeStampToken (as described in RFC 3161 The value of messageImprint of TimeStampToken (as described in RFC
[7]) shall be a hash of the value of eContent field within 3161 [7]) shall be a hash of the value of the eContent field within
encapContentInfo in the signedData. encapContentInfo in the signedData.
For further information and definition of TimeStampToken see For further information and definition of TimeStampToken, see Section
section 7.4. 7.4.
NOTE: Content-time-stamp indicates that the signed information was NOTE: content-time-stamp indicates that the signed information was
formed before the date included in the Content-time-stamp. formed before the date included in the content-time-stamp.
5.12 Support for multiple signatures 5.12. Support for Multiple Signatures
5.12.1 Independent signatures 5.12.1. Independent Signatures
Multiple independent signatures (see section B.5) are supported by Multiple independent signatures (see Annex B.5) are supported by
independent SignerInfo from each signer. independent SignerInfo from each signer.
Each SignerInfo shall include all the attributes required under the Each SignerInfo shall include all the attributes required under the
present document and shall be processed independently by the verifier. present document and shall be processed independently by the
verifier.
Note: Independent signatures may be used to provide independent NOTE: Independent signatures may be used to provide independent
signatures from different parties with different signed attributes, or signatures from different parties with different signed
to provide multiple signatures from the same party using alternative attributes, or to provide multiple signatures from the same party
signature algorithms in which case the other attributes, excluding using alternative signature algorithms, in which case the other
time values and signature policy information, will generally be the attributes, excluding time values and signature policy
same. information, will generally be the same.
5.12.2 Embedded signatures 5.12.2. Embedded Signatures
Multiple embedded signatures (see section C.5) are supported using the Multiple embedded signatures (see Annex C.5) are supported using the
countersignature unsigned attribute (see section 5.9.2). Each counter countersignature unsigned attribute (see Section 5.9.2). Each
signature is carried in Countersignature held as an unsigned attribute counter signature is carried in countersignature held as an unsigned
to the SignerInfo to which the counter-signature is applied. attribute to the SignerInfo to which the counter-signature is
applied.
Note: Counter signatures may be used to provide signatures from NOTE: Counter signatures may be used to provide signatures from
different parties with different signed attributes, or to provide different parties with different signed attributes, or to provide
multiple signatures from the same party using alternative signature multiple signatures from the same party using alternative
algorithms in which case the other attributes, excluding time values signature algorithms, in which case the other attributes,
and signature policy information, will generally be the same. excluding time values and signature policy information, will
generally be the same.
6 Additional Electronic Signature validation attributes 6. Additional Electronic Signature Validation Attributes
This section specifies attributes that contain different types of This section specifies attributes that contain different types of
validation data. These attributes build on the electronic signature validation data. These attributes build on the electronic signature
specified in section 5. This includes: specified in Section 5. This includes:
- Signature-time-stamp applied to the electronic signature value or - Signature-time-stamp applied to the electronic signature value
a Time-Mark in an audit trail. This is defined as the Electronic or a Time-Mark in an audit trail. This is defined as the
Signature with Time (CAdES-T); and Electronic Signature with Time (CAdES-T); and
- complete validation data references which comprises the time- - Complete validation data references that comprise the time-stamp
stamp of the signature value (CAdES-T), plus references to all of the signature value, plus references to all the certificates
the certificates (complete-certificate-references) and revocation (complete-certificate-references) and revocation (complete-
(complete-revocation-references) information used for full revocation-references) information used for full validation of
validation of the electronic signature. This is defined as the the electronic signature. This is defined as the Electronic
Electronic Signature with Complete data references (CAdES-C). Signature with Complete data references (CAdES-C).
NOTE 1: Formats for CAdES-T are illustrated in section 4.4 and the NOTE 1: Formats for CAdES-T are illustrated in Section 4.4, and
attribute are defined in section 6.1.1. the attributes are defined in Section 6.1.1.
NOTE 2: Formats for CAdES-C are illustrated in section 4.4. The NOTE 2: Formats for CAdES-C are illustrated in Section 4.4. The
required attributes for the CAdES-C signature format are required attributes for the CAdES-C signature format are defined
defined in section 6.2.1 to 6.2.2, optional attributes are in Sections 6.2.1 to 6.2.2; optional attributes are defined in
defined in sections 6.2.3 and 6.2.4. Sections 6.2.3 and 6.2.4.
In addition the following optional eXtended forms of validation data In addition, the following optional extended forms of validation data
are also defined, see annex B for an overview the eXtended forms of are also defined; see Annex B for an overview of the extended forms
validation data: of validation data:
- CAdES-X with time stamp: there are two types of time-stamp used - CAdES-X with time-stamp: there are two types of time-stamps used
in extended validation data defined by the present document: in extended validation data defined by the present document;
- Type 1(CAdES-X Type 1): comprises a time-stamp over the ES - Type 1(CAdES-X Type 1): comprises a time-stamp over the ES
with complete validation data (CAdES-C); and with Complete validation data (CAdES-C); and
- Type 2 (CAdES-X Type2): comprises a time-stamp over the - Type 2 (CAdES-X Type2): comprises a time-stamp over the
certification path references and the revocation information certification path references and the revocation information
references used to support the CAdES-C. references used to support the CAdES-C.
NOTE 3: Formats for CAdES-X Type 1 and CAdES-X Type 2 are illustrated NOTE 3: Formats for CAdES-X Type 1 and CAdES-X Type 2 are
in sections B.1.2 and B.1.3, respectively. illustrated in Sections B.1.2 and B.1.3, respectively.
- CAdES-X Long :comprises the complete validation data references - CAdES-X Long: comprises the Complete validation data
(CAdES-C) plus the actual values of all the certificates and references (CAdES-C), plus the actual values of all the
revocation information used in the CAdES-C. certificates and revocation information used in the CAdES-C.
NOTE 4: Formats for CAdES-X Long are illustrated in section B.1.1. NOTE 4: Formats for CAdES-X Long are illustrated in Annex B.1.1.
- CAdES-X Long Type 1 or CAdES-X Long Type 2: comprises an X-Time- - CAdES-X Long Type 1 or CAdES-X Long Type 2: comprises an
Stamp (Type 1 or Type 2) plus the actual values of all the X-Time-Stamp (Type 1 or Type 2), plus the actual values of
certificates and revocation information used in the CAdES-C as all the certificates and revocation information used in the
per CAdES-X Long. CAdES-C as per CAdES-X Long.
This section also specifies the data structures used in Archive This section also specifies the data structures used in Archive
validation data format (CAdES-A)of eXtended forms: validation data format (CAdES-A)of extended forms:
- Archive form of electronic signature (CAdES-A) comprises the - Archive form of electronic signature (CAdES-A) comprises:
complete validation data references (CAdES-C), the certificate
and revocation values (as in a CAdES-X Long ), if present any - the Complete validation data references (CAdES-C),
existing extended electronic signature timestamps (CAdES-X Type 1
or CAdES-X Type 2), plus the signed user data and an additional - the certificate and revocation values (as in a CAdES-X Long ),
archive time-stamp applied over all that data. An archive time-
stamp may be repeatedly applied after long periods to maintain - any existing extended electronic signature time-stamps
validity when electronic signature and time-stamping algorithms (CAdES-X Type 1 or CAdES-X Type 2), if present, and
weaken.
- the signed user data and an additional archive time-stamp
applied over all that data.
An archive time-stamp may be repeatedly applied after long
periods to maintain validity when electronic signature and
time-stamping algorithms weaken.
The additional data required to create the forms of electronic The additional data required to create the forms of electronic
signature identified above is carried as unsigned attributes associated signature identified above is carried as unsigned attributes
with an individual signature by being placed in the unsignedAttrs field associated with an individual signature by being placed in the
of SignerInfo. Thus all the attributes defined in section 6 are unsignedAttrs field of SignerInfo. Thus, all the attributes defined
unsigned attributes. in Section 6 are unsigned attributes.
NOTE 5: Where multiple signatures are to be supported, as described NOTE 5: Where multiple signatures are to be supported, as
in section 5.12, each signature has a separate SignerInfo. described in Section 5.12, each signature has a separate
Thus, each signature requires its own unsigned attribute SignerInfo. Thus, each signature requires its own unsigned
values to create CAdES-T, CAdES-C, etc. attribute values to create CAdES-T, CAdES-C, etc.
NOTE 6: the optional attributes of the extended validation data are NOTE 6: The optional attributes of the extended validation data
defined in sections 6.3 and 6.4. are defined in Sections 6.3 and 6.4.
6.1 Electronic Signature Time-stamped (CAdES-T) 6.1. signature time-stamp Attribute (CAdES-T)
An Electronic Signature with time-stamp is an electronic signature for An electronic signature with time-stamp is an electronic signature
which part, but not all, of the additional data required for validation for which part, but not all, of the additional data required for
is available (i.e. some certificates and revocation information are validation is available (i.e., some certificates and revocation
available but not all). information are available, but not all).
The minimum structure time-stamp validation data is: The minimum structure time-stamp validation data is:
- the Signature Time-stamp Attribute as defined in section 6.1.1 - the signature time-stamp attribute, as defined in Section 6.1.1,
over the ES signature value. over the ES signature value.
6.1.1 Signature time- stamp attribute definition 6.1.1. signature-time-stamp Attribute Definition
The signature-time-stamp attribute is a TimeStampToken computed on the The signature-time-stamp attribute is a TimeStampToken computed on
signature value for a specific signer. It is an unsigned attribute. the signature value for a specific signer; it is an unsigned
Several instances of this attribute may occur with an electronic attribute. Several instances of this attribute may occur with an
signature, from different TSAs. electronic signature, from different TSAs.
The following object identifier identifies the signature-time-stamp The following object identifier identifies the signature-time-stamp
attribute: attribute:
id-aa-signatureTimeStampToken OBJECT IDENTIFIER ::= id-aa-signatureTimeStampToken OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 14} smime(16) id-aa(2) 14}
The signature-time-stamp attribute value has ASN.1 type The signature-time-stamp attribute value has ASN.1 type
SignatureTimeStampToken: SignatureTimeStampToken:
SignatureTimeStampToken ::= TimeStampToken SignatureTimeStampToken ::= TimeStampToken
The value of the messageImprint field within TimeStampToken shall be
The value of messageImprint field within TimeStampToken shall be a a hash of the value of the signature field within SignerInfo for the
hash of the value of the signature field within SignerInfo for the
signedData being time-stamped. signedData being time-stamped.
For further information and definition of TimeStampToken see For further information and definition of TimeStampToken, see Section
section 7.4. 7.4.
NOTE 1: In the case of multiple signatures it is possible to have a NOTE 1: In the case of multiple signatures, it is possible to have
a:
TimeStampToken computed for each and all signers, or - TimeStampToken computed for each and all signers; or
TimeStampToken computed on one signer's signature and no
TimeStampToken on another signer's signature.
NOTE 2: In the case of multiple signatures, several TSTs, issued by - TimeStampToken computed on one signer's signature; and no
different TSAs, may be present within the same signerInfo
(see RFC 3852 [4]).
6.2 Complete validation reference data (CAdES-C) - TimeStampToken on another signer's signature.
An electronic signature with complete validation data references NOTE 2: In the case of multiple signatures, several TSTs, issued
(CAdES-C) is an Electronic Signature for which all the additional data by different TSAs, may be present within the same signerInfo (see
required for validation (i.e. all certificates and revocation RFC 3852 [4]).
6.2. Complete Validation Data References (CAdES-C)
An electronic signature with Complete validation data references
(CAdES-C) is an electronic signature for which all the additional
data required for validation (i.e., all certificates and revocation
information) is available. This form is built on the CAdES-T form information) is available. This form is built on the CAdES-T form
defined above. defined above.
As a minimum, the complete validation data shall include the following: As a minimum, the Complete validation data shall include the
- a time, which shall either be a signature-timestamp attribute, as following:
defined in section 6.1.1, or a time mark operated by a Time-
Marking Authority;
- complete-certificate-references, as defined in section 6.2.1;
- complete-revocation-references , as defined in section 6.2.2. - a time, which shall either be a signature-timestamp attribute,
as defined in Section 6.1.1, or a time-mark operated by a
Time-Marking Authority;
6.2.1 Complete certificate references attribute definition - complete-certificate-references, as defined in Section 6.2.1;
The complete-certificate-references attribute is an unsigned attribute. - complete-revocation-references, as defined in Section 6.2.2.
It references the full set of CA certificates that have been used to
validate an ES with Complete validation data up to (but not including) 6.2.1. complete-certificate-references Attribute Definition
the signer's certificate. Only a single instance of this attribute
shall occur with an electronic signature. The complete-certificate-references attribute is an unsigned
attribute. It references the full set of CA certificates that have
been used to validate an ES with Complete validation data up to (but
not including) the signer's certificate. Only a single instance of
this attribute shall occur with an electronic signature.
NOTE 1: The signer's certificate is referenced in the signing NOTE 1: The signer's certificate is referenced in the signing
certificate attribute (see section 5.7.3). certificate attribute (see Section 5.7.3).
id-aa-ets-certificateRefs OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-certificateRefs OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 21} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 21}
The complete-certificate-references attribute value has the ASN.1 The complete-certificate-references attribute value has the ASN.1
syntax CompleteCertificateRefs. syntax CompleteCertificateRefs.
CompleteCertificateRefs ::= SEQUENCE OF OtherCertID CompleteCertificateRefs ::= SEQUENCE OF OtherCertID
OtherCertID is defined in section 5.7.3.2. OtherCertID is defined in Section 5.7.3.3.
The IssuerSerial that shall be present in OtherCertID. The certHash The IssuerSerial that shall be present in OtherCertID. The certHash
shall match the hash of the certificate referenced. shall match the hash of the certificate referenced.
NOTE 2: Copies of the certificate values may be held using the NOTE 2: Copies of the certificate values may be held using the
certificate-values attribute defined in section 6.3.3. certificate-values attribute, defined in Section 6.3.3.
This attribute may include references to the certification This attribute may include references to the certification chain
chain for any TSUs that provides time-stamp tokens. In this for any TSUs that provides time-stamp tokens. In this case, the
case the unsigned attribute shall be added to the signedData unsigned attribute shall be added to the signedData of the
of the relevant times tamp token as an unsignedAttrs in the relevant time-stamp token as an unsignedAttrs in the signerInfos
signerInfos field. field.
6.2.2 Complete Revocation References attribute definition 6.2.2. complete-revocation-references Attribute Definition
The complete-revocation-references attribute is an unsigned attribute. The complete-revocation-references attribute is an unsigned
Only a single instance of this attribute shall occur with an electronic attribute. Only a single instance of this attribute shall occur with
signature. It references the full set of the CRL, ACRL or OCSP an electronic signature. It references the full set of the CRL,
responses that have been used in the validation of the signer and CA ACRL, or OCSP responses that have been used in the validation of the
certificates used in ES with Complete validation data. signer, and CA certificates used in ES with Complete validation data.
This attribute can be used to illustrate that the verifier has taken This attribute indicates that the verifier has taken due diligence to
due diligence of the available revocation information and then to be gather the available revocation information. The references stored
able to retrieve that information when stored elsewhere. in this attribute can be used to retrieve the referenced information,
if not stored in the CMS structure, but somewhere else.
The following object identifier identifies the complete-revocation- The following object identifier identifies the
references attribute: complete-revocation-references attribute:
id-aa-ets-revocationRefs OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-revocationRefs OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 22} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 22}
The complete-revocation-references attribute value has the ASN.1
The complete-revocation-references attribute value has the ASN.1 syntax syntax CompleteRevocationRefs:
CompleteRevocationRefs:
CompleteRevocationRefs ::= SEQUENCE OF CrlOcspRef CompleteRevocationRefs ::= SEQUENCE OF CrlOcspRef
CrlOcspRef ::= SEQUENCE { CrlOcspRef ::= SEQUENCE {
crlids [0] CRLListID OPTIONAL, crlids [0] CRLListID OPTIONAL,
ocspids [1] OcspListID OPTIONAL, ocspids [1] OcspListID OPTIONAL,
otherRev [2] OtherRevRefs OPTIONAL otherRev [2] OtherRevRefs OPTIONAL
} }
CompleteRevocationRefs shall contain one CrlOcspRef for the signing- CompleteRevocationRefs shall contain one CrlOcspRef for the
certificate, followed by one for each OtherCertID in the signing-certificate, followed by one for each OtherCertID in the
CompleteCertificateRefs attribute. The second and subsequent CompleteCertificateRefs attribute. The second and subsequent
CrlOcspRef fields shall be in the same order as the OtherCertID to CrlOcspRef fields shall be in the same order as the OtherCertID to
which they relate. At least one of CRLListID or OcspListID or which they relate. At least one of CRLListID or OcspListID or
OtherRevRefs should be present for all but the "trusted" CA of the OtherRevRefs should be present for all but the "trusted" CA of the
certificate path. certificate path.
CRLListID ::= SEQUENCE { CRLListID ::= SEQUENCE {
crls SEQUENCE OF CrlValidatedID } crls SEQUENCE OF CrlValidatedID }
CrlValidatedID ::= SEQUENCE { CrlValidatedID ::= SEQUENCE {
skipping to change at page 46, line 50 skipping to change at page 51, line 4
ocspIdentifier OcspIdentifier, ocspIdentifier OcspIdentifier,
ocspRepHash OtherHash OPTIONAL ocspRepHash OtherHash OPTIONAL
} }
OcspIdentifier ::= SEQUENCE { OcspIdentifier ::= SEQUENCE {
ocspResponderID ResponderID, ocspResponderID ResponderID,
-- As in OCSP response data -- As in OCSP response data
producedAt GeneralizedTime producedAt GeneralizedTime
-- As in OCSP response data -- As in OCSP response data
} }
When creating a crlValidatedID, the crlHash is computed over the
When creating a crlValidatedID, the crlHash is computed over the entire entire DER encoded CRL including the signature. The crlIdentifier
DER encoded CRL including the signature. The crlIdentifier would would normally be present unless the CRL can be inferred from other
normally be present unless the CRL can be inferred from other
information. information.
The crlIdentifier is to identify the CRL using the issuer name and the The crlIdentifier is to identify the CRL using the issuer name and
CRL issued time, which shall correspond to the time thisUpdate the CRL issued time, which shall correspond to the time thisUpdate
contained in the issued CRL, and if present, the crlNumber. The contained in the issued CRL, and if present, the crlNumber. The
crlListID attribute is an unsigned attribute. In the case that the crlListID attribute is an unsigned attribute. In the case that the
identified CRL is a Delta CRL then references to the set of CRLs to identified CRL is a Delta CRL, then references to the set of CRLs to
provide a complete revocation list shall be included. provide a complete revocation list shall be included.
The OcspIdentifier is to identify the OCSP response using the issuer The OcspIdentifier is to identify the OCSP response using the issuer
name and the time of issue of the OCSP response which shall correspond name and the time of issue of the OCSP response, which shall
to the time producedAt contained in the issued OCSP response. Since it correspond to the time produced as contained in the issued OCSP
may be needed to make the difference between two OCSP responses response. Since it may be needed to make the difference between two
received within the same second, then the hash of the response OCSP responses received within the same second, the hash of the
contained in the OcspResponsesID may be needed to solve the ambiguity. response contained in the OcspResponsesID may be needed to solve the
ambiguity.
NOTE 1: Copies of the CRL and OCSP responses values may be held using
the revocation-values attribute defined in section 6.3.4.
NOTE 2: It is recommended that this attribute is used in preference to NOTE 1: Copies of the CRL and OCSP responses values may be held
using the revocation-values attribute defined in Section 6.3.4.
The OtherRevocationInfoFormat specified in RFC 3852 to NOTE 2: It is recommended that this attribute be used in
Maintain backward compatibility with earlier version of this preference to the OtherRevocationInfoFormat specified in RFC 3852
specification. to maintain backwards compatibility with the earlier version of
this specification.
The syntax and semantics of other revocation references is outside the The syntax and semantics of other revocation references are outside
scope of the present document. The definition of the syntax of the the scope of the present document. The definition of the syntax of
other form of revocation information is as identified by the other form of revocation information is as identified by
OtherRevRefType. OtherRevRefType.
This attribute may include the references to the full set of the CRL, This attribute may include the references to the full set of the CRL,
ACRL or OCSP responses that have been used to verify the certification ACRL, or OCSP responses that have been used to verify the
chain for any TSUs that provides time-stamp tokens. In this case the certification chain for any TSUs that provide time-stamp tokens. In
unsigned attribute shall be added to the signedData of the relevant this case, the unsigned attribute shall be added to the signedData of
timestamp token as an unsignedAttrs in the signerInfos field. the relevant time-stamp token as an unsignedAttrs in the signerInfos
field.
6.2.3 Attribute certificate references attribute definition 6.2.3. attribute-certificate-references Attribute Definition
This attribute is only used when a user attribute certificate is This attribute is only used when a user attribute certificate is
present in the electronic signature. present in the electronic signature.
The attribute-certificate-references attribute is an unsigned The attribute-certificate-references attribute is an unsigned
attribute. It references the full set of AA certificates that have attribute. It references the full set of AA certificates that have
been used to validate the attribute certificate. Only a single been used to validate the attribute certificate. Only a single
instance of this attribute shall occur with an electronic signature. instance of this attribute shall occur with an electronic signature.
id-aa-ets-attrCertificateRefs OBJECT IDENTIFIER ::= id-aa-ets-attrCertificateRefs OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 44} smime(16) id-aa(2) 44}
The attribute-certificate-references attribute value has the ASN.1 The attribute-certificate-references attribute value has the ASN.1
syntax AttributeCertificateRefs: syntax AttributeCertificateRefs:
AttributeCertificateRefs ::= SEQUENCE OF OtherCertID AttributeCertificateRefs ::= SEQUENCE OF OtherCertID
OtherCertID is defined in section 5.8.2. OtherCertID is defined in Section 5.7.3.3.
NOTE: Copies of the certificate values may be held using the NOTE: Copies of the certificate values may be held using the
certificate-values attribute defined in section 6.3.3. certificate-values attribute defined in Section 6.3.3.
6.2.4 Attribute revocation references attribute definition 6.2.4. attribute-revocation-references Attribute Definition
This attribute is only used when a user attribute certificate is This attribute is only used when a user attribute certificate is
present in the electronic signature and when that attribute certificate present in the electronic signature and when that attribute
can be revoked. certificate can be revoked.
The attribute-revocation-references attribute is an unsigned attribute. The attribute-revocation-references attribute is an unsigned
Only a single instance of this attribute shall occur with an attribute. Only a single instance of this attribute shall occur with
electronic signature. It references the full set of the ACRL or OCSP an electronic signature. It references the full set of the ACRL or
responses that have been used in the validation of the attribute OCSP responses that have been used in the validation of the attribute
certificate. This attribute can be used to illustrate that the certificate. This attribute can be used to illustrate that the
verifier has taken due diligence of the available revocation verifier has taken due diligence of the available revocation
information. information.
The following object identifier identifies the attribute-revocation- The following object identifier identifies the
references attribute: attribute-revocation-references attribute:
id-aa-ets-attrRevocationRefs OBJECT IDENTIFIER ::= { iso(1) id-aa-ets-attrRevocationRefs OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16)
id-aa(2) 45} id-aa(2) 45}
The attribute-revocation-references attribute value has the ASN.1 The attribute-revocation-references attribute value has the ASN.1
syntax AttributeRevocationRefs: syntax AttributeRevocationRefs:
AttributeRevocationRefs ::= SEQUENCE OF CrlOcspRef AttributeRevocationRefs ::= SEQUENCE OF CrlOcspRef
6.3 Extended validation data (CAdES-X) 6.3. Extended Validation Data (CAdES-X)
This section specifies a number of optional attributes that are used This section specifies a number of optional attributes that are used
by extended forms of electronic signatures (see annex B for an by extended forms of electronic signatures (see Annex B for an
overview these forms of validation data). overview of these forms of validation data).
6.3.1 Time-stamped validation data (CAdES-X Type 1 or Type 2) 6.3.1. Time-Stamped Validation Data (CAdES-X Type 1 or Type 2)
The extended validation data may include one of the following The extended validation data may include one of the following
additional attributes, forming a CAdES-X Time-Stamp validation data additional attributes, forming a CAdES-X Time-Stamp validation data
(CAdES-X Type 1 or CAdES-X Type 2), to provide additional protection (CAdES-X Type 1 or CAdES-X Type 2), to provide additional protection
against later CA compromise and provide integrity of the validation against later CA compromise and provide integrity of the validation
data used: data used:
- CAdES-C Time-stamp, as defined in section 6.3.5 (CAdES-X Type 1); - CAdES-C Time-stamp, as defined in Section 6.3.5 (CAdES-X Type
or 1); or
- Time-Stamped Certificates and CRLs references, as defined in - Time-Stamped Certificates and CRLs references, as defined in
section 6.3.6 (CAdES-X Type 2). Section 6.3.6 (CAdES-X Type 2).
6.3.2 Long validation data (CAdES-X Long, CAdES-X Long Type 1 or 2) 6.3.2. Long Validation Data (CAdES-X Long, CAdES-X Long Type 1 or 2)
The extended validation data may also include the following additional The extended validation data may also include the following
information, forming a CAdES-X Long, for use if later validation additional information, forming a CAdES-X Long, for use if later
processes may not have access to this information: validation processes may not have access to this information:
- certificate-values as defined in section 6.3.3; and - certificate-values, as defined in Section 6.3.3; and
- revocation-values as defined in section 6.3.4.
The extended validation data may in addition to certificate-values and - revocation-values, as defined in Section 6.3.4.
revocation-values as defined in sections 6.3.3 and 6.3.4 include one of
the following additional attributes, forming an CAdES-X Long Type 1 or
CAdES-X Long Type 2.
- CAdES-C Time-stamp, as defined in section 6.3.3 (CAdES-X long The extended validation data may, in addition to certificate-values
and revocation-values as defined in Sections 6.3.3 and 6.3.4, include
one of the following additional attributes, forming a CAdES-X Long
Type 1 or CAdES-X Long Type 2.
- CAdES-C Time-stamp, as defined in Section 6.3.3 (CAdES-X long
Type 1); or Type 1); or
- Time-Stamped Certificates and CRLs references, as defined in - Time-Stamped Certificates and CRLs references, as defined in
section 6.3.4 (CAdES-X Long Type 2). Section 6.3.4 (CAdES-X Long Type 2).
The CAdES-X Long Type 1 or CAdES-X Long Type 2 provide additional The CAdES-X Long Type 1 or CAdES-X Long Type 2 provides additional
protection against later CA compromise and provide integrity of the protection against later CA compromise and provides integrity of the
validation data used. validation data used.
NOTE 1: The CAdES-X-Long signature provides long term proof of the NOTE 1: The CAdES-X-Long signature provides long-term proof of the
validity of the signature for as long as the CA keys, CRL validity of the signature for as long as the CA keys, CRL Issuers
Issuers keys and OCSP responder keys are not compromised and keys, and OCSP responder keys are not compromised and are
are resistant to cryptographic attacks. resistant to cryptographic attacks.
NOTE 2: As long as the time stamp data remains valid, the CAdES-X NOTE 2: As long as the time-stamp data remains valid, the CAdES-X
Long Type 1 and the CAdES-X Long Type 2 provides the following Long Type 1 and the CAdES-X Long Type 2 provide the following
important property for long standing signatures; that having important property for long-standing signatures; that having been
been found once to be valid, it shall continue to be so months found once to be valid, it shall continue to be so months or years
or years later, long after the validity period of the later, long after the validity period of the certificates has
certificates have expired, or after the user key has been expired, or after the user key has been compromised.
compromised.
6.3.3 Certificate values attribute definition 6.3.3. certificate-values Attribute Definition
This attribute may be used to contain the certificate information This attribute may be used to contain the certificate information
required for the following forms of eXtended Electronic Signature: required for the following forms of extended electronic signature:
CAdES-X Long , ES X-Long Type 1 and CAdES-X Long Type 2, see section CAdES-X Long, ES X-Long Type 1, and CAdES-X Long Type 2; see Annex
B.1.1 for an illustration of this form of electronic signature. B.1.1 for an illustration of this form of electronic signature.
The certificate-values attribute is an unsigned attribute. Only a The certificate-values attribute is an unsigned attribute. Only a
single instance of this attribute shall occur with an electronic single instance of this attribute shall occur with an electronic
signature. It holds the values of certificates referenced in the signature. It holds the values of certificates referenced in the
complete-certificate-references attribute. complete-certificate-references attribute.
NOTE: If an attribute certificate is used, it is not provided in this NOTE: If an attribute certificate is used, it is not provided in
structure but shall be provided by the signer as a signer- this structure but shall be provided by the signer as a
attributes attribute (see section 5.11.3). signer-attributes attribute (see Section 5.11.3).
The following object identifier identifies the certificate-values The following object identifier identifies the certificate-values
attribute: attribute:
id-aa-ets-certValues OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-certValues OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 23} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 23}
The certificate-values attribute value has the ASN.1 syntax The certificate-values attribute value has the ASN.1 syntax
CertificateValues. CertificateValues.
CertificateValues ::= SEQUENCE OF Certificate CertificateValues ::= SEQUENCE OF Certificate
Certificate is defined in section 7.1. (which is as defined in ITU-T Certificate is defined in Section 7.1. (which is as defined in ITU-T
Recommendation X.509 [1]. Recommendation X.509 [1]).
This attribute may include the certification information for any TSUs This attribute may include the certification information for any TSUs
that have provided the time-stamp tokens if these certificates are not that have provided the time-stamp tokens, if these certificates are
already included in the TSTs as part of the TSUs signatures. In this not already included in the TSTs as part of the TSUs signatures. In
case the unsigned attribute shall be added to the signedData of the this case, the unsigned attribute shall be added to the signedData of
relevant timestamp token. the relevant time-stamp token.
6.3.4 Revocation values attribute definition 6.3.4. revocation-values Attribute Definition
This attribute is used to contain the revocation information required This attribute is used to contain the revocation information required
for the following forms of eXtended Electronic Signature: CAdES-X Long, for the following forms of extended electronic signature: CAdES-X
ES X-Long Type 1 and CAdES-X Long Type 2, see section B.1.1 for an Long, ES X-Long Type 1, and CAdES-X Long Type 2; see Annex B.1.1 for
illustration of this form of electronic signature. an illustration of this form of electronic signature.
The revocation-values attribute is an unsigned attribute. Only a The revocation-values attribute is an unsigned attribute. Only a
single instance of this attribute shall occur with an electronic single instance of this attribute shall occur with an electronic
signature. It holds the values of CRLs and OCSP referenced in the signature. It holds the values of CRLs and OCSP referenced in the
complete-revocation-references attribute. complete-revocation-references attribute.
NOTE : It is recommended that this attribute is used in preference to NOTE: It is recommended that this attribute be used in preference
the OtherRevocationInfoFormat specified in RFC 3852 to maintain to the OtherRevocationInfoFormat specified in RFC 3852 to maintain
backward compatibility with earlier version of this backwards compatibility with the earlier version of this
specification. specification.
The following object identifier identifies the revocation-values The following object identifier identifies the revocation-values
attribute: attribute:
id-aa-ets-revocationValues OBJECT IDENTIFIER ::= { iso(1) id-aa-ets-revocationValues OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 24} smime(16) id-aa(2) 24}
The revocation-values attribute value has the ASN.1 syntax The revocation-values attribute value has the ASN.1 syntax
skipping to change at page 50, line 57 skipping to change at page 55, line 33
crlVals [0] SEQUENCE OF CertificateList OPTIONAL, crlVals [0] SEQUENCE OF CertificateList OPTIONAL,
ocspVals [1] SEQUENCE OF BasicOCSPResponse OPTIONAL, ocspVals [1] SEQUENCE OF BasicOCSPResponse OPTIONAL,
otherRevVals [2] OtherRevVals OPTIONAL } otherRevVals [2] OtherRevVals OPTIONAL }
OtherRevVals ::= SEQUENCE { OtherRevVals ::= SEQUENCE {
OtherRevValType OtherRevValType, OtherRevValType OtherRevValType,
OtherRevVals ANY DEFINED BY OtherRevValType } OtherRevVals ANY DEFINED BY OtherRevValType }
OtherRevValType ::= OBJECT IDENTIFIER OtherRevValType ::= OBJECT IDENTIFIER
The syntax and semantics of the other revocation values (OtherRevVals) The syntax and semantics of the other revocation values
is outside the scope of the present document. (OtherRevVals) are outside the scope of the present document.
The definition of the syntax of the other form of revocation The definition of the syntax of the other form of revocation
information is as identified by OtherRevRefType. information is as identified by OtherRevRefType.
CertificateList is defined in section 7.2. (which as defined in ITU-T CertificateList is defined in Section 7.2. (which is as defined in
Recommendation X.509 [1]). ITU-T Recommendation X.509 [1]).
BasicOCSPResponse is defined in section 7.3. (which as defined in BasicOCSPResponse is defined in Section 7.3. (which is as defined in
RFC 2560 [3]). RFC 2560 [3]).
This attribute may include the values of revocation data including CRLs This attribute may include the values of revocation data including
and OCSP for any TSUs that have provided the time-stamp tokens if these CRLs and OCSPs for any TSUs that have provided the time-stamp tokens,
certificates are not already included in the TSTs as part of the TSUs if these certificates are not already included in the TSTs as part of
signatures. In this case the unsigned attribute shall be added to the the TSUs signatures. In this case, the unsigned attribute shall be
signedData of the relevant timestamp token. added to the signedData of the relevant time-stamp token.
6.3.5 CAdES-C time-stamp attribute definition 6.3.5. CAdES-C-time-stamp Attribute Definition
This attribute is used to protect against CA key compromise. This attribute is used to protect against CA key compromise.
This attribute is used for the time stamping the complete electronic This attribute is used for the time-stamping of the complete
signature (CAdES-C). It is used in the following forms of eXtended electronic signature (CAdES-C). It is used in the following forms of
Electronic Signature; CAdES-X Type 1 and CAdES-X Long Type 1, see extended electronic signature; CAdES-X Type 1 and CAdES-X Long Type
section B.1.2 for an illustration of this form of electronic signature. 1; see Annex B.1.2 for an illustration of this form of electronic
signature.
The CAdES-C-timestamp attribute is an unsigned attribute. It is a The CAdES-C-time-stamp attribute is an unsigned attribute. It is a
time-stamp token of the hash of the electronic signature and the time-stamp token of the hash of the electronic signature and the
complete validation data (CAdES-C). It is a special purpose complete validation data (CAdES-C). It is a special-purpose
TimeStampToken Attribute which time-stamps the CAdES-C. Several TimeStampToken Attribute that time-stamps the CAdES-C. Several
instances of this attribute may occur with an electronic signature from instances of this attribute may occur with an electronic signature
different TSAs. from different TSAs.
NOTE 1: It is recommended that the attributes being time-stamped are NOTE 1: It is recommended that the attributes being time-stamped
encoded in DER. If DER is not employed then the binary encoding be encoded in DER. If DER is not employed, then the binary
of the ASN.1structures being time-stamped should be preserved to encoding of the ASN.1 structures being time-stamped should be
ensure that the recalculation of the data hash is consistent. preserved to ensure that the recalculation of the data hash is
consistent.
NOTE 2: Each attribute is included in the hash with the attrType and NOTE 2: Each attribute is included in the hash with the attrType
attrValues (including type and length) but without the type and and attrValues (including type and length) but without the type
length of the outer SEQUENCE. and length of the outer SEQUENCE.
The following object identifier identifies the CAdES-C-Timestamp The following object identifier identifies the CAdES-C-Timestamp
attribute: attribute:
id-aa-ets-escTimeStamp OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-escTimeStamp OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 25} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 25}
The CAdES-C-timestamp attribute value has the ASN.1 syntax The CAdES-C-timestamp attribute value has the ASN.1 syntax
ESCTimeStampToken : ESCTimeStampToken :
ESCTimeStampToken ::= TimeStampToken ESCTimeStampToken ::= TimeStampToken
The value of messageImprint field within TimeStampToken shall be a hash The value of the messageImprint field within TimeStampToken shall be
of the concatenated values (without the type or length encoding for a hash of the concatenated values (without the type or length
that value) of the following data objects: encoding for that value) of the following data objects:
- OCTETSTRING of the SignatureValue field within SignerInfo; - OCTETSTRING of the SignatureValue field within SignerInfo;
- signature-time-stamp, or a time mark operated by a Time-Marking - signature-time-stamp, or a time-mark operated by a Time-Marking
Authority; Authority;
- complete-certificate-references s attribute; and - complete-certificate-references attribute; and
- complete-revocation-references attribute. - complete-revocation-references attribute.
For further information and definition of the TimeStampToken, see For further information and definition of the TimeStampToken, see
clause 7.4. Section 7.4.
6.3.6 Time-stamped certificates and crls references attribute 6.3.6. time-stamped-certs-crls-references Attribute Definition
definition
This attribute is used to protect against CA key compromise. This This attribute is used to protect against CA key compromise. This
attribute is used for the time stamping certificate and revocation attribute is used for the time-stamping certificate and revocation
references. It is used in the following forms of eXtended Electronic references. It is used in the following forms of extended electronic
Signature; CAdES-X Type 2 and CAdES-X Long Type 2, see section B.1.3 signature: CAdES-X Type 2 and CAdES-X Long Type 2; see Annex B.1.3
for an illustration of this form of electronic signature. for an illustration of this form of electronic signature.
A time-stamped-certs-crls-references attribute is an unsigned A time-stamped-certs-crls-references attribute is an unsigned
attribute. It is a time-stamp token issued for a list of referenced attribute. It is a time-stamp token issued for a list of referenced
certificates and OCSP responses or/and CRLs to protect against certain certificates and OCSP responses and/or CRLs to protect against
CA compromises. Its syntax is as follows: certain CA compromises. Its syntax is as follows:
NOTE 1: It is recommended that the attributes being time-stamped are NOTE 1: It is recommended that the attributes being time-stamped
encoded in DER. If DER is not employed then the binary encoding be encoded in DER. If DER is not employed, then the binary
of the ASN.1structures being time-stamped should be preserved to encoding of the ASN.1 structures being time-stamped should be
ensure that the recalculation of the data hash is consistent. preserved to ensure that the recalculation of the data hash is
consistent.
NOTE 2: Each attribute is included in the hash with the attrType and NOTE 2: Each attribute is included in the hash with the attrType
attrValues (including type and length) but without the type and and attrValues (including type and length) but without the type
length of the outer SEQUENCE and length of the outer SEQUENCE.
The following object identifier identifies the time-stamped-certs-crls- The following object identifier identifies the
references attribute: time-stamped-certs-crls-references attribute:
id-aa-ets-certCRLTimestamp OBJECT IDENTIFIER ::= id-aa-ets-certCRLTimestamp OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 26} smime(16) id-aa(2) 26}
The attribute value has the ASN.1 syntax TimestampedCertsCRLs : The attribute value has the ASN.1 syntax TimestampedCertsCRLs :
TimestampedCertsCRLs ::= TimeStampToken TimestampedCertsCRLs ::= TimeStampToken
The value of messageImprint field within TimeStampToken shall be a hash The value of the messageImprint field within the TimeStampToken shall
of the concatenated values (without the type or length encoding for be a hash of the concatenated values (without the type or length
that value) of the following data objects as present in the ES with encoding for that value) of the following data objects, as present in
Complete validation data (CAdES-C): the ES with Complete validation data (CAdES-C):
- complete-certificate-references attribute; and - complete-certificate-references attribute; and
- complete-revocation-references attribute. - complete-revocation-references attribute.
6.4 Archive validation data 6.4. Archive Validation Data
Where an electronic signature is required to last for a very long time, Where an electronic signature is required to last for a very long
and a the time-stamp token on an electronic signature is in danger of time, and the time-stamp token on an electronic signature is in
being invalidated due to algorithm weakness or limits in the validity danger of being invalidated due to algorithm weakness or limits in
period of the TSA certificate, then it may be required to time-stamp the validity period of the TSA certificate, it may be required to
the electronic signature several times. When this is required an time-stamp the electronic signature several times. When this is
archive time-stamp attribute may be required for the archive form of required, an archive time-stamp attribute may be required for the
electronic signature (CAdES-A). This archive time-stamp attribute may archive form of the electronic signature (CAdES-A). This archive
be repeatedly applied over a period of time. time-stamp attribute may be repeatedly applied over a period of time.
6.4.1 Archive time-stamp attribute definition 6.4.1. archive-time-stamp Attribute Definition
The archive-time-stamp attribute is a time-stamp token of many of the The archive-time-stamp attribute is a time-stamp token of many of the
elements of the signedData in the electronic signature. If the elements of the signedData in the electronic signature. If the
certificate-values and revocation-values attributes are not present in certificate-values and revocation-values attributes are not present
the CAdES-BES or CAdES-EPES, then they shall be added to the electronic in the CAdES-BES or CAdES-EPES, then they shall be added to the
signature prior to computing the archive time-stamp token. electronic signature prior to computing the archive time-stamp token.
The archive-time-stamp attribute is an unsigned attribute. Several The archive-time-stamp attribute is an unsigned attribute. Several
instances of this attribute may occur with an electronic signature instances of this attribute may occur with an electronic signature
both over time and from different TSUs. both over time and from different TSUs.
The following object identifier identifies the nested The following object identifier identifies the nested
archive-time-stamp attribute: archive-time-stamp attribute:
id-aa-ets-archiveTimestampV2 OBJECT IDENTIFIER ::= id-aa-ets-archiveTimestampV2 OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 48} smime(16) id-aa(2) 48}
Archive-time-stamp attribute values have the ASN.1 syntax Archive-time-stamp attribute values have the ASN.1 syntax
ArchiveTimeStampToken ArchiveTimeStampToken
ArchiveTimeStampToken ::= TimeStampToken ArchiveTimeStampToken ::= TimeStampToken
The value of messageImprint field within TimeStampToken shall be a hash The value of the messageImprint field within TimeStampToken shall be
of the concatenation of: a hash of the concatenation of:
- The encapContentInfo element of the SignedData sequence; - the encapContentInfo element of the SignedData sequence;
- If the eContent element of the encapContentInfo is omitted, - any external content being protected by the signature, if the
any external content being protected by the signature; eContent element of the encapContentInfo is omitted;
- When present, the Certificates and crls elements of the - the Certificates and crls elements of the SignedData sequence,
SignedData sequence; and when present, and;
- Together with all data elements in the SignerInfo sequence - all data elements in the SignerInfo sequence including all
including all signed and unsigned attributes. signed and unsigned attributes.
NOTE 1: An alternative archiveTimestamp attribute, identified by NOTE 1: An alternative archiveTimestamp attribute, identified by
object identifier { iso(1) member-body(2) us(840) an object identifier { iso(1) member-body(2) us(840)
rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 27, is rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 27, is defined
defined in prior versions of TS 101 733 and in RFC 3126. in prior versions of TS 101 733 [TS101733] and in RFC 3126.
The archiveTimestamp attribute defined in versions of The archiveTimestamp attribute, defined in versions of TS 101 733
TS 101 733 prior to 1.5.1 and in RFC 3126 is not compatible prior to 1.5.1 and in RFC 3126, is not compatible with the
with the attribute defined in the current document. The attribute defined in the current document. The archiveTimestamp
archiveTimestamp attribute defined in versions 1.5.1 to 1.7.3 attribute, defined in versions 1.5.1 to 1.6.3 of TS 101 733, is
of TS 101 733 is compatible with the current document if the compatible with the current document if the content is internal to
content is internal to encapContentInfo. Unless the version encapContentInfo. Unless the version of TS 101 733 employed by
of TS 101 733 employed by the signing party is known by all the signing party is known by all recipients, use of the
recipients, use of the archiveTimestamp attribute defined in archiveTimestamp attribute defined in prior versions of TS 101 733
prior versions of TS 101 733 is deprecated. is deprecated.
NOTE 2: Counter signatures held as countersignature attributes do not NOTE 2: Counter signatures held as countersignature attributes do
require independent archive time-stamps as they are protected not require independent archive time-stamps, as they are protected
by the archive time-stamp against the containing signedData by the archive time-stamp against the containing SignedData
structure. structure.
NOTE 3: Unless DER is used throughout, it is recommended that the NOTE 3: Unless DER is used throughout, it is recommended that the
binary encoding of the ASN.1 structures being time-stamped are binary encoding of the ASN.1 structures being time-stamped be
preserved when being archived to ensure that the recalculation preserved when being archived to ensure that the recalculation of
of the data hash is consistent. the data hash is consistent.
NOTE 4: The hash is calculated over the concatenated data elements as NOTE 4: The hash is calculated over the concatenated data elements
received / stored including the Type and Length encoding. as received/stored, including the Type and Length encoding.
NOTE 5: Whilst it is recommended that unsigned attributes are DER NOTE 5: Whilst it is recommended that unsigned attributes be DER
encoded it cannot generally be so guaranteed except by prior encoded, it cannot generally be so guaranteed except by prior
arrangement. Further information and definition of arrangement. For further information and definition of
TimeStampToken see section 7.4. The timestamp should be TimeStampToken, see Section 7.4. The timestamp should be created
created using stronger algorithms (or longer key lengths) than using stronger algorithms (or longer key lengths) than in the
in the original electronic signatures and weak algorithm (key original electronic signatures and weak algorithm (key length)
length) timestamps. timestamps.
NOTE 6: This form of ES also provides protection against a TSP key NOTE 6: This form of ES also provides protection against a TSP key
compromise. compromise.
The ArchiveTimeStamp will be added as an unsigned attribute in the The ArchiveTimeStamp will be added as an unsigned attribute in the
SignerInfo sequence. For the validation of one ArchiveTimeStamp the SignerInfo sequence. For the validation of one ArchiveTimeStamp, the
data elements of the SignerInfo must be concatenated excluding all data elements of the SignerInfo must be concatenated, excluding all
later ArchivTimeStampToken attributes. later ArchivTimeStampToken attributes.
Certificates and revocation information required to validate the Certificates and revocation information required to validate the
ArchiveTimeStamp shall be provided by one of the following methods: ArchiveTimeStamp shall be provided by one of the following methods:
- The TSU provides the information in the SignedData of the - The TSU provides the information in the SignedData of the
timestamp token; timestamp token;
- Adding the complete-certificate-references attribute and the - Adding the complete-certificate-references attribute and the
complete-revocation-references attribute of the TSP as an complete-revocation-references attribute of the TSP as an
unsigned attribute within TimeStampToken, when the required unsigned attribute within TimeStampToken, when the required
information is store elsewhere; or information is stored elsewhere; or
- Adding the certificate-values attribute and the revocation-values - Adding the certificate-values attribute and the
attribute of the TSP as an unsigned attribute within revocation-values attribute of the TSP as an unsigned attribute
TimeStampToken, when the required information is store elsewhere. within TimeStampToken, when the required information is stored
elsewhere.
7 Other standard data structures 7. Other Standard Data Structures
7.1 Public-key certificate format 7.1. Public Key Certificate Format
The X.509 v3 certificate basis syntax is defined in ITU-T The X.509 v3 certificate basis syntax is defined in ITU-T
Recommendation X.509 [1]. A profile of the X.509 v3 certificate is Recommendation X.509 [1]. A profile of the X.509 v3 certificate is
defined in RFC 3280 [2]. defined in RFC 3280 [2].
7.2 Certificate revocation list format 7.2. Certificate Revocation List Format
The X.509 v2 CRL syntax is defined in ITU-T Recommendation X.509 [1]. The X.509 v2 CRL syntax is defined in ITU-T Recommendation X.509 [1].
A profile of the X.509 v2 CRL is defined in RFC 3280 [2]. A profile of the X.509 v2 CRL is defined in RFC 3280 [2].
7.3 OCSP response format 7.3. OCSP Response Format
The format of an OCSP token is defined in RFC 2560 [3]. The format of an OCSP token is defined in RFC 2560 [3].
7.4 Time-stamp token format 7.4. Time-Stamp Token Format
The format of a TimeStampToken type is defined in RFC 3161 [7] and The format of a TimeStampToken type is defined in RFC 3161 [7] and
profiled in ETSI TS 101 861 [TS101861]. profiled in ETSI TS 101 861 [TS101861].
7.5 Name and attribute formats 7.5. Name and Attribute Formats
The syntax of the naming and other attributes is defined in ITU-T The syntax of the naming and other attributes is defined in ITU-T
Recommendation X.509 [1]. Recommendation X.509 [1].
Note: The name used by the signer, held as the subject in the signer's NOTE: The name used by the signer, held as the subject in the
certificate, is allocated and verified on registration with the signer's certificate, is allocated and verified on registration
Certification Authority, either directly or indirectly through a with the Certification Authority, either directly or indirectly
Registration Authority, before being issued with a Certificate. through a Registration Authority, before being issued with a
Certificate.
The present document places no restrictions on the form of the name. The present document places no restrictions on the form of the name.
The subject's name may be a distinguished name, as defined in ITU-T The subject's name may be a distinguished name, as defined in ITU-T
Recommendation X.500 [12], held in the subject field of the Recommendation X.500 [12], held in the subject field of the
certificate, or any other name form held in the subjectAltName certificate, or any other name form held in the subjectAltName
certificate extension field as defined in ITU-T Recommendation X.509 certificate extension field, as defined in ITU-T Recommendation X.509
[1]. In the case that the subject has no distinguished name, the [1]. In the case that the subject has no distinguished name, the
subject name can be an empty sequence and the subjectAltName extension subject name can be an empty sequence and the subjectAltName
shall be critical. extension shall be critical.
All Certification Authorities, Attribute Authorities and Time Stamping All Certification Authorities, Attribute Authorities, and
Authorities shall use distinguished names in the subject field of Time-Stamping Authorities shall use distinguished names in the
their certificate. subject field of their certificate.
The distinguished name shall include identifiers for the organization The distinguished name shall include identifiers for the organization
providing the service and the legal jurisdiction (e.g. country) under providing the service and the legal jurisdiction (e.g., country)
which it operates. under which it operates.
Where a signer signs as an individual but wishes to also identify
him/herself as acting on behalf of an organization, it may be necessary
to provide two independent forms of identification. The first
identity, with is directly associated with the signing key identifies
him/her as an individual. The second, which is managed independently, Where a signer signs as an individual, but wishes to also identify
identifies that person acting as part of the organization, possibly him/herself as acting on behalf of an organization, it may be
with a given role. In this case one of the two identities is carried necessary to provide two independent forms of identification. The
in the subject/subjectAltName field of the signer's certificate as first identity, which is directly associated with the signing key,
described above. identifies him/her as an individual. The second, which is managed
independently, identifies that person acting as part of the
organization, possibly with a given role. In this case, one of the
two identities is carried in the subject/subjectAltName field of the
signer's certificate as described above.
The present document does not specify the format of signer's attribute The present document does not specify the format of the signer's
that may be included in public key certificates. attribute that may be included in public key certificates.
NOTE : Signer's attribute may be supported by using a claimed role in NOTE: The signer's attribute may be supported by using a claimed
the CMS signed attributes field or by placing an attribute role in the CMS signed attributes field or by placing an attribute
certificate containing a certified role in the CMS signed certificate containing a certified role in the CMS signed
attributes field, see section 7.6. attributes field; see Section 7.6.
7.6 Attribute certificate 7.6. AttributeCertificate
The syntax of the AttributeCertificate type is defined in RFC 3281 [13]. The syntax of the AttributeCertificate type is defined in RFC 3281
[13].
8. Conformance requirements 8. Conformance Requirements
For implementations supporting signature generation, the present For implementations supporting signature generation, the present
document defines conformance requirements for the generation of two document defines conformance requirements for the generation of two
forms of basic electronic signature, one of the two forms must be forms of basic electronic signature, one of the two forms must be
implemented. implemented.
For implementations supporting signature verification, the present For implementations supporting signature verification, the present
document defines conformance requirements for the verification of two document defines conformance requirements for the verification of two
forms of basic electronic signature, one of the two forms must be forms of basic electronic signature, one of the two forms must be
implemented. implemented.
The present document only defines conformance requirements up to an ES The present document only defines conformance requirements up to an
with Complete validation data (CAdES-C). This means that none of the ES with Complete validation data (CAdES-C). This means that none of
extended and archive forms of Electronic Signature (CAdES-X, CAdES-A) the extended and archive forms of the electronic signature (CAdES-X,
need to be implemented to get conformance to the present document. CAdES-A) need to be implemented to get conformance to the present
document.
On verification the inclusion of optional signed and unsigned On verification the inclusion of optional signed and unsigned
attributes must be supported only to the extended that the signature is attributes must be supported only to the extent that the signature is
verifiable. The semantics of optional attributes may be unsupported, verifiable. The semantics of optional attributes may be unsupported,
unless specified otherwise by a signature policy. unless specified otherwise by a signature policy.
8.1 CAdES-Basic Electronic Signature (CAdES-BES) 8.1. CAdES-Basic Electronic Signature (CAdES-BES)
A system supporting CAdES-BES signers according to the present A system supporting CAdES-BES signers, according to the present
document shall, at a minimum, support generation of an electronic document, shall, at a minimum, support generation of an electronic
signature consisting of the following components: signature consisting of the following components:
- The general CMS syntax and content type as defined in RFC 3852 - The general CMS syntax and content type, as defined in RFC 3852
[4] (see sections 5.1 and 5.2); [4] (see Sections 5.1 and 5.2);
- CMS SignedData as defined in RFC 3852 [4] with version set to 3 - CMS SignedData, as defined in RFC 3852 [4], with the version set
and at least one SignerInfo shall be present (see sections 5.3 to to 3 and at least one SignerInfo present (see Sections 5.3 to
5.6); 5.6);
- The following CMS attributes as defined in RFC 3852 [4]:
- content-type; this shall always be present - The following CMS attributes, as defined in RFC 3852 [4]:
(see section 5.7.1); and
- message-digest; this shall always be present (see section - content-type; this shall always be present (see Section
5.7.1); and
- message-digest; this shall always be present (see Section
5.7.2). 5.7.2).
- One of following attributes as defined in the present document: - One of the following attributes, as defined in the present
document:
- signing-certificate: as defined in section 5.7.3.1; or - signing-certificate: as defined in Section 5.7.3.1; or
- signing-certificate v2 : as defined in section 5.7.3.2. - signing-certificate v2 : as defined in Section 5.7.3.2.
Note : RFC 3126 was using the other signing certificate attribute NOTE: RFC 3126 was using the other signing-certificate attribute
(see section 5.7.3.3). Its use is now deprecated, since the (see Section 5.7.3.3). Its use is now deprecated, since the
structure of the signing-certificate v2 attribute is simpler structure of the signing-certificate v2 attribute is simpler than
than the other signing certificate attribute. the other signing-certificate attribute.
8.2 CAdES-Explicit Policy-based Electronic Signature 8.2. CAdES-Explicit Policy-based Electronic Signature
A system supporting Policy-based signers according to the present A system supporting Policy-based signers, according to the present
document shall, at a minimum, support generation of an electronic document, shall, at a minimum, support the generation of an
signature consisting of the previous components defined for the basic electronic signature consisting of the previous components defined
signer, plus: for the basic signer, plus:
- The following attributes as defined in section 5.9: - The following attributes, as defined in Section 5.9:
- signature-policy-identifier; this shall always be present (see - signature-policy-identifier; this shall always be present
section 5.8.1). (see Section 5.8.1).
8.3 Verification using time-stamping 8.3. Verification Using Time-Stamping
A system supporting verifiers according to the present document with A system supporting verifiers, according to the present document,
time-stamping facilities shall, at a minimum, support: with time-stamping facilities shall, at a minimum, support:
- verification of the mandated components of an electronic - verification of the mandated components of an electronic
signature, as defined in section 8.1; signature, as defined in Section 8.1;
- signature-time-stamp attribute, as defined in section 6.1.1; - signature-time-stamp attribute, as defined in Section 6.1.1;
- complete-certificate-references, attribute as defined in - complete-certificate-references attribute, as defined in Section
section 6.2.1; 6.2.1;
- complete-revocation-references attribute, as defined in - complete-revocation-references attribute, as defined in Section
section 6.2.2; 6.2.2;
- Public Key Certificates, as defined in ITU-T Recommendation X.509 - Public Key Certificates, as defined in ITU-T Recommendation
[1] (see section 8.1); and X.509 [1] (see Section 8.1); and
- either of: - either of:
- Certificate Revocation Lists. as defined in ITU-T - Certificate Revocation Lists, as defined in ITU-T
Recommendation X.509 [1] (see section 8.2); or Recommendation X.509 [1] (see Section 8.2); or
- on-line Certificate Status Protocol, as defined in RFC 2560
[3] (see section 8.3).
8.4 Verification using secure records - Online Certificate Status Protocol, as defined in RFC 2560
[3] (see Section 8.3).
A system supporting verifiers according to the present document shall, 8.4. Verification Using Secure Records
at a minimum, support:
- verification of the mandated components of an electronic A system supporting verifiers, according to the present document,
signature, as defined in section 8.1; shall, at a minimum, support:
- complete-certificate-references attribute, as defined in - verification of the mandated components of an electronic
section 6.2.1; signature, as defined in Section 8.1;
- complete-certificate-references attribute, as defined in Section
6.2.1;
- complete-revocation-references attribute, as defined in - complete-revocation-references attribute, as defined in Section
section 6.2.2; 6.2.2;
- a record of the electronic signature and the time when the - a record of the electronic signature and the time when the
signature was first validated using the referenced certificates signature was first validated, using the referenced certificates
and revocation information must be maintained such that records and revocation information, must be maintained, such that
cannot be undetectable modified; records cannot be undetectably modified;
- Public Key Certificates, as defined in ITU-T Recommendation X.509 - Public Key Certificates, as defined in ITU-T Recommendation
[1] (see section 8.1); and X.509 [1] (see Section 8.1); and
- either of: - either of:
- Certificate Revocation Lists. as defined in ITU-T - Certificate Revocation Lists, as defined in ITU-T
Recommendation X.509 [1] (see section 8.2); or Recommendation X.509 [1] (see Section 8.2); or
- on-line Certificate Status Protocol, as defined in RFC 2560
[3] (see section 8.3).
9. IANA Considerations
No IANA actions required. - online Certificate Status Protocol, as defined in RFC 2560
[3] (see Section 8.3).
10. References 9. References
10.1 Normative references 9.1. Normative References
[1] ITU-T Recommendation X.509 (2000)/ISO/IEC 9594-8 (2001): [1] ITU-T Recommendation X.509 (2000)/ISO/IEC 9594-8 (2001):
"Information technology - Open Systems Interconnection - "Information technology - Open Systems Interconnection - The
The Directory: Authentication framework". Directory: Public key and Attribute Certificate framework".
[2] IETF RFC 3280 (2002): "Internet X.509 Public Key [2] Housley, R., Polk, W., Ford, W., and D. Solo, "Internet X.509
Infrastructure Certificate and Certificate Revocation List Public Key Infrastructure Certificate and Certificate
(CRL) Profile". Revocation List (CRL) Profile", RFC 3280, April 2002.
[3] IETF RFC 2560 (1999): "X.509 Internet Public Key [3] Myers, M., Ankney, R., Malpani, A., Galperin, S., and C.
Infrastructure Online Certificate Status Protocol - OCSP". Adams, "X.509 Internet Public Key Infrastructure Online
Certificate Status Protocol - OCSP", RFC 2560, June 1999.
[4] IETF RFC 3852 (2004): "Cryptographic Message Syntax (CMS)". [4] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 3852,
July 2004.
[5] IETF RFC 2634 (1999): "Enhanced Security Services for [5] Hoffman, P., Ed., "Enhanced Security Services for S/MIME", RFC
S/MIME". 2634, June 1999.
[6] IETF RFC 2045 (1996): "Multipurpose Internet Mail Extensions [6] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
(MIME) Part One: Format of Internet Message Bodies". Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996.
[7] IETF RFC 3161 (2001): "Internet X.509 Public Key [7] Adams, C., Cain, P., Pinkas, D., and R. Zuccherato, "Internet
Infrastructure Time-Stamp Protocol ". X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)",
RFC 3161, August 2001.
[8] ITU-T Recommendation X.680 (1997): "Information technology - [8] ITU-T Recommendation X.680 (1997): "Information technology -
Abstract Syntax Notation One (ASN.1): Specification of basic Abstract Syntax Notation One (ASN.1): Specification of basic
notation". notation".
[9] ITU-T Recommendation X.501 (2000)/ISO/IEC 9594-1 (2001): [9] ITU-T Recommendation X.501 (2000)/ISO/IEC 9594-1 (2001):
"Information technology - Open Systems Interconnection - "Information technology - Open Systems Interconnection -
Directory models ". Directory models ".
[10] IETF RFC 3370 (2002): "Cryptographic Message Syntax (CMS) [10] Housley, R., "Cryptographic Message Syntax (CMS) Algorithms",
Algorithms". RFC 3370, August 2002.
[11] ITU-T Recommendation F.1: "Operational provisions for the [11] ITU-T Recommendation F.1: "Operational provisions for the
international public telegram service". international public telegram service".
[12] ITU-T Recommendation X.500: "Information technology - Open [12] ITU-T Recommendation X.500: "Information technology - Open
Systems Interconnection - The Directory: Overview of Systems Interconnection - The Directory: Overview of concepts,
concepts, models and services". models and services".
[13] IETF RFC 3281 (2002): "An Internet Attribute Certificate [13] Farrell, S. and R. Housley, "An Internet Attribute Certificate
Profile for Authorization". Profile for Authorization", RFC 3281, April 2002.
[14] ITU-T Recommendation X.208 (1988): "Specification of Abstract [14] ITU-T Recommendation X.208 (1988): "Specification of Abstract
Syntax Notation One (ASN.1)". Syntax Notation One (ASN.1)".
[15] IETF RFC 5035 (2007). ESS Update: Adding CertID Algorithm [15] Schaad, J., "Enhanced Security Services (ESS) Update: Adding
Agility. CertID Algorithm Agility", RFC 5035, August 2007.
[16] ITU-T Recommendation X.690 (2002): "Information technology [16] ITU-T Recommendation X.690 (2002): "Information technology
ASN.1 encoding rules: Specification of Basic Encoding Rules ASN.1 encoding rules: Specification of Basic Encoding Rules
(BER), Canonical Encoding Rules (CER) and Distinguished (BER), Canonical Encoding Rules (CER) and Distinguished
Encoding Rules (DER) Encoding Rules (DER)".
10.2 Informative references
ETSI technical specifications can be downloaded free of charge 9.2. Informative References
via the Services and Products Download Area at:
http://www.etsi.org/WebSite/Standards/StandardsDownload.aspx
[EU Directive] Directive 1999/93/EC of the European Parliament and [EUDirective] Directive 1999/93/EC of the European Parliament and of
of the Council of 13 December 1999 on a Community framework for the Council of 13 December 1999 on a community
electronic signatures. framework for Electronic Signatures.
[TS101733] ETSI Standard TS 101 733 V.1.7.3 (2005-06) Electronic [TS101733] ETSI Standard TS 101 733 V.1.7.3 (2005-06) Electronic
Signature Formats. Signature Formats.
[TS101861] ETSI TS 101 861: "Time stamping profile". [TS101861] ETSI TS 101 861: "Time stamping profile".
[TS101903] ETSI TS 101 903: "XML Advanced Electronic Signatures [TS101903] ETSI TS 101 903: "XML Advanced Electronic Signatures
(XAdES)". (XAdES)".
[TR102038] ETSI TR 102 038: "Electronic Signatures and [TR102038] ETSI TR 102 038: "Electronic Signatures and
Infrastructures (ESI); XML format for signature policies". Infrastructures (ESI); XML format for signature
policies".
[TR102272] ETSI TR 102 272 V1.1.1 (2003-12). "Electronic Signatures [TR102272] ETSI TR 102 272 V1.1.1 (2003-12). "Electronic
and Infrastructures (ESI); ASN.1 format for signature policies". Signatures and Infrastructures (ESI); ASN.1 format for
signature policies".
[RFC2479] IETF RFC 2479 (1998): "Independent Data Unit Protection [RFC2479] Adams, C., "Independent Data Unit Protection Generic
Generic Security Service Application Program Interface Security Service Application Program Interface (IDUP-
(IDUP-GSS-API)". GSS-API)", RFC 2479, December 1998.
[RFC2743] IETF RFC 2743 (2000): "Generic Security Service [RFC2743] Linn, J., "Generic Security Service Application
Application Program Interface Version 2, Update 1 Program Interface Version 2, Update 1", RFC 2743,
January 2000.
[RFC3125] IETF RFC 3125 (2000): "Electronic Signature Policies". [RFC3125] Ross, J., Pinkas, D., and N. Pope, "Electronic
Signature Policies", RFC 3125, September 2001.
[RFC3447] IETF RFC 3447 (2003): "PKCS #1: RSA Cryptography [RFC3447] Jonsson, J. and B. Kaliski, "Public-Key Cryptography
Specifications Version 2.1". Standards (PKCS) #1: RSA Cryptography Specifications
Version 2.1", RFC 3447, February 2003.
[RFC3494] IETF RFC 3494 (2003): "Internet X.509 Public Key [RFC3494] Zeilenga, K., "Lightweight Directory Access Protocol
Infrastructure Operational Protocols - LDAPv2". version 2 (LDAPv2) to Historic Status", RFC 3494,
March 2003.
[RFC3851] IETF RFC 3851 (2004): "SMIME Version 3.1 Message [RFC3851] Ramsdell, B., Ed., "Secure/Multipurpose Internet Mail
Specification". Extensions (S/MIME) Version 3.1 Message
Specification", RFC 3851, July 2004.
[RFC4210] IETF RFC 4210 (2005): "Internet X.509 Public Key [RFC4210] Adams, C., Farrell, S., Kause, T., and T. Mononen,
Infrastructure Certificate Management Protocols". "Internet X.509 Public Key Infrastructure Certificate
Management Protocol (CMP)", RFC 4210, September 2005.
[RFC4346] IETF RFC 4346 (2006): "The TLS Protocol Version 1.1". [RFC4346] Dierks, T. and E. Rescorla, "The Transport Layer
Security (TLS) Protocol Version 1.1", RFC 4346, April
2006.
[RFC4523] IETF RFC 4523 (2006): " Lightweight Directory Access [RFC4523] Zeilenga, K., "Lightweight Directory Access Protocol
Protocol (LDAP). Schema Definitions for X.509 Certificates". (LDAP) Schema Definitions for X.509 Certificates", RFC
4523, June 2006.
[ISO7498-2] ISO 7498-2 (1989): "Information processing systems - [ISO7498-2] ISO 7498-2 (1989): "Information processing systems -
Open Systems Interconnection - Basic Reference Model - Part 2: Open Systems Interconnection - Basic Reference Model -
Security Architecture". Part 2: Security Architecture".
[ISO9796-2] ISO/IEC 9796-2 (2002): "Information technology - [ISO9796-2] ISO/IEC 9796-2 (2002): "Information technology -
Security techniques - Digital signature schemes giving message Security techniques - Digital signature schemes giving
recovery - Part 2: Integer factorization based mechanisms". message recovery - Part 2: Integer factorization based
mechanisms".
[ISO9796-4] ISO/IEC 9796-4 (1998): "Digital signature schemes [ISO9796-4] ISO/IEC 9796-4 (1998): "Digital signature schemes
giving message recovery - Part 4: Discrete logarithm based giving message recovery - Part 4: Discrete logarithm
mechanisms". based mechanisms".
[ISO10118-1] ISO/IEC 10118-1 (2000): "Information technology - [ISO10118-1] ISO/IEC 10118-1 (2000): "Information technology -
Security techniques - Hash-functions - Part 1: General". Security techniques - Hash-functions - Part 1:
General".
[ISO10118-2] ISO/IEC 10118-2 (2000): "Information technology - [ISO10118-2] ISO/IEC 10118-2 (2000): "Information technology -
Security techniques - Hash-functions - Part 2: Hash-functions using Security techniques - Hash-functions - Part 2:
an n-bit block cipher algorithm". Hash-functions using an n-bit block cipher algorithm".
[ISO10118-3] ISO/IEC 10118-3 (2004): "Information technology - [ISO10118-3] ISO/IEC 10118-3 (2004): "Information technology -
Security techniques - Hash-functions - Part 3: Dedicated Security techniques - Hash-functions - Part 3:
hash-functions". Dedicated hash-functions".
[ISO10118-4] ISO/IEC 10118-4 (1998): "Information technology - [ISO10118-4] ISO/IEC 10118-4 (1998): "Information technology -
Security techniques - Hash-functions - Part 4: Hash-functions using Security techniques - Hash-functions - Part 4: Hash-
modular arithmetic". functions using modular arithmetic".
[ISO10181-5] ISO/IEC 10181-5: Security Frameworks in Open Systems. [ISO10181-5] ISO/IEC 10181-5: Security Frameworks in Open Systems.
Non-Repudiation Framework. April 1997. Non-Repudiation Framework. April 1997.
[ISO13888-1] ISO/IEC 13888-1 (2004): "IT security techniques - [ISO13888-1] ISO/IEC 13888-1 (2004): "IT security techniques -
Non-repudiation - Part 1: General". Non-repudiation - Part 1: General".
[ISO14888-1] ISO/IEC 14888-1 (1998): "Information technology - [ISO14888-1] ISO/IEC 14888-1 (1998): "Information technology -
Security techniques - Digital signatures with appendix - Part 1: Security techniques - Digital signatures with appendix
General". - Part 1: General".
[ISO14888-2] ISO/IEC 14888-2 (1999): "Information technology - [ISO14888-2] ISO/IEC 14888-2 (1999): "Information technology -
Security techniques - Digital signatures with appendix - Part 2: Security techniques - Digital signatures with appendix
Identity-based mechanisms". - Part 2: Identity-based mechanisms".
[ISO14888-3] ISO/IEC 14888-3 (1998): "Information technology - [ISO14888-3] ISO/IEC 14888-3 (1998): "Information technology -
Security techniques - Digital signatures with appendix - Part 3: Security techniques - Digital signatures with appendix
Certificate-based mechanisms". - Part 3: Certificate-based mechanisms".
[ISO15946-2] ISO/IEC 15946-2 (2002): "Information technology - [ISO15946-2] ISO/IEC 15946-2 (2002): "Information technology -
Security techniques - Cryptographic techniques based on elliptic Security techniques - Cryptographic techniques based
curves - Part 2: Digital signatures". on elliptic curves - Part 2: Digital signatures".
[CWA14171] CWA 14171 CEN Workshop Agreement: "General Guidelines [CWA14171] CWA 14171 CEN Workshop Agreement: "General Guidelines
for Electronic Signature Verification". for Electronic Signature Verification".
[XMLDSIG] XMLDSIG: W3C/IETF Recommendation (February 2002): [XMLDSIG] XMLDSIG: W3C/IETF Recommendation (February 2002):
"XML-Signature Syntax and Processing". "XML-Signature Syntax and Processing".
[X9.30-1] ANSI X9.30-1 (1997): "Public Key Cryptography for the [X9.30-1] ANSI X9.30-1 (1997): "Public Key Cryptography for the
Financial Services Industry - Part 1: The Digital
Financial Services Industry - Part 1: The Digital Signature Signature Algorithm (DSA)".
Algorithm (DSA)".
[X9.30-2] ANSI X9.30-2 (1997): "Public Key Cryptography for the [X9.30-2] ANSI X9.30-2 (1997): "Public Key Cryptography for the
Financial Services Industry - Part 2: The Secure Hash Algorithm Financial Services Industry - Part 2: The Secure Hash
(SHA-1)". Algorithm (SHA-1)".
[X9.31-1] ANSI X9.31-1 (1997): "Public Key Cryptography Using [X9.31-1] ANSI X9.31-1 (1997): "Public Key Cryptography Using
Reversible Algorithms for the Financial Services Industry - Reversible Algorithms for the Financial Services
Part 1: The RSA Signature Algorithm". Industry - Part 1: The RSA Signature Algorithm".
[X9.31-2] ANSI X9.31-2 (1996): "Public Key Cryptography Using [X9.31-2] ANSI X9.31-2 (1996): "Public Key Cryptography Using
Reversible Algorithms for the Financial Services Industry - Reversible Algorithms for the Financial Services
Part 2: Hash Algorithms". Industry - Part 2: Hash Algorithms".
[X9.62] ANSI X9.62 (1998): "Public Key Cryptography for the [X9.62] ANSI X9.62 (1998): "Public Key Cryptography for the
Financial Services Industry - The Elliptic Curve Digital Signature Financial Services Industry - The Elliptic Curve
Algorithm (ECDSA)". Digital Signature Algorithm (ECDSA)".
[P1363] IEEE P1363 (2000): "Standard Specifications for Public-Key
Cryptography".
12. Authors' addresses
Denis Pinkas
Bull S.A.S.
Rue Jean-Jaures
78340 Les Clayes sous Bois CEDEX
FRANCE
EMail: Denis.Pinkas@bull.net
Nick Pope
Thales eSecurity
Meadow View House
Long Crendon
Aylesbury
Buck
HP18 9EQ
United Kingdom
EMail: nick.pope@thales-esecurity.com
John Ross
Security & Standards Consultancy Ltd
The Waterhouse Business Centre
2 Cromer Way
Chelmsford
Essex
CM1 2QE
United Kingdom
EMail: ross@secstan.com
13. Acknowledgments [P1363] IEEE P1363 (2000): "Standard Specifications for
Public-Key Cryptography".
Special thanks to Russ Housley for reviewing the document. ETSI technical specifications can be downloaded free of charge via
the Services and Products Download Area at:
http://www.etsi.org/WebSite/Standards/StandardsDownload.aspx
Annex A (normative): ASN.1 definitions Annex A (Normative): ASN.1 Definitions
This annex provides a summary of all the ASN.1 syntax definitions for This annex provides a summary of all the ASN.1 syntax definitions for
new syntax defined in the present document. new syntax defined in the present document.
A.1 Signature format definitions using X.208 ASN.1 syntax A.1. Signature Format Definitions Using X.208 ASN.1 Syntax
NOTE: The ASN.1 module defined in section A.1 using syntax defined in NOTE: The ASN.1 module defined in Annex A.1 using syntax defined
ITU-T Recommendation X.208 [14] has precedence over that in ITU-T Recommendation X.208 [14] has precedence over that
defined in section A.2 in the case of any conflict. defined in Annex A.2 in the case of any conflict.
ETS-ElectronicSignatureFormats-ExplicitSyntax88 { iso(1) member-body(2) ETS-ElectronicSignatureFormats-ExplicitSyntax88 { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-mod(0) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-mod(0)
eSignature-explicit88(28)} eSignature-explicit88(28)}
DEFINITIONS EXPLICIT TAGS ::= DEFINITIONS EXPLICIT TAGS ::=
BEGIN BEGIN
-- EXPORTS All -- EXPORTS All
skipping to change at page 64, line 35 skipping to change at page 70, line 39
FROM PKIXTSP FROM PKIXTSP
{iso(1) identified-organization(3) dod(6) internet(1) security(5) {iso(1) identified-organization(3) dod(6) internet(1) security(5)
mechanisms(5) pkix(7) id-mod(0) id-mod-tsp(13)} mechanisms(5) pkix(7) id-mod(0) id-mod-tsp(13)}
; ;
-- Definitions of Object Identifier arcs used in the present document -- Definitions of Object Identifier arcs used in the present document
-- ================================================================== -- ==================================================================
-- OID used referencing electronic signature mechanisms based on -- OID used referencing electronic signature mechanisms based on
-- the present document for use with the Independent Data Unit
-- Protection (IDUP) API (see Annex D)
id-etsi-es-IDUP-Mechanism-v1 OBJECT IDENTIFIER ::= id-etsi-es-IDUP-Mechanism-v1 OBJECT IDENTIFIER ::=
{ itu-t(0) identified-organization(4) etsi(0) { itu-t(0) identified-organization(4) etsi(0)
electronic-signature-standard (1733) part1 (1) idupMechanism (4) electronic-signature-standard (1733) part1 (1) idupMechanism (4)
etsiESv1(1) } etsiESv1(1) }
-- Basic ES CMS Attributes Defined in the present document -- Basic ES CMS Attributes Defined in the present document
-- ======================================================= -- =======================================================
-- OtherSigningCertificate - deprecated -- OtherSigningCertificate - deprecated
skipping to change at page 65, line 15 skipping to change at page 71, line 22
certs SEQUENCE OF OtherCertID, certs SEQUENCE OF OtherCertID,
policies SEQUENCE OF PolicyInformation OPTIONAL policies SEQUENCE OF PolicyInformation OPTIONAL
-- NOT USED IN THE PRESENT DOCUMENT -- NOT USED IN THE PRESENT DOCUMENT
} }
OtherCertID ::= SEQUENCE { OtherCertID ::= SEQUENCE {
otherCertHash OtherHash, otherCertHash OtherHash,
issuerSerial IssuerSerial OPTIONAL } issuerSerial IssuerSerial OPTIONAL }
OtherHash ::= CHOICE { OtherHash ::= CHOICE {
sha1Hash OtherHashValue, -- This contains a SHA-1 hash sha1Hash OtherHashValue,
-- This contains a SHA-1 hash
otherHash OtherHashAlgAndValue} otherHash OtherHashAlgAndValue}
-- Policy ES Attributes Defined in the present document -- Policy ES Attributes Defined in the present document
-- ==================================================== -- ====================================================
-- Mandatory Basic Electronic Signature Attributes as above, -- Mandatory Basic Electronic Signature Attributes as above,
-- plus in addition. -- plus in addition.
-- Signature-policy-identifier attribute
id-aa-ets-sigPolicyId OBJECT IDENTIFIER ::= id-aa-ets-sigPolicyId OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
smime(16) id-aa(2) 15 } smime(16) id-aa(2) 15 }
SignaturePolicy ::= CHOICE { SignaturePolicy ::= CHOICE {
signaturePolicyId SignaturePolicyId, signaturePolicyId SignaturePolicyId,
signaturePolicyImplied SignaturePolicyImplied signaturePolicyImplied SignaturePolicyImplied
-- not used in this version -- not used in this version
} }
skipping to change at page 66, line 38 skipping to change at page 72, line 46
noticeNumbers SEQUENCE OF INTEGER } noticeNumbers SEQUENCE OF INTEGER }
DisplayText ::= CHOICE { DisplayText ::= CHOICE {
visibleString VisibleString (SIZE (1..200)), visibleString VisibleString (SIZE (1..200)),
bmpString BMPString (SIZE (1..200)), bmpString BMPString (SIZE (1..200)),
utf8String UTF8String (SIZE (1..200)) } utf8String UTF8String (SIZE (1..200)) }
-- Optional Electronic Signature Attributes -- Optional Electronic Signature Attributes
-- Commitment-type attribute
id-aa-ets-commitmentType OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-commitmentType OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 16} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 16}
CommitmentTypeIndication ::= SEQUENCE { CommitmentTypeIndication ::= SEQUENCE {
commitmentTypeId CommitmentTypeIdentifier, commitmentTypeId CommitmentTypeIdentifier,
commitmentTypeQualifier SEQUENCE SIZE (1..MAX) OF commitmentTypeQualifier SEQUENCE SIZE (1..MAX) OF
CommitmentTypeQualifier OPTIONAL} CommitmentTypeQualifier OPTIONAL}
CommitmentTypeIdentifier ::= OBJECT IDENTIFIER CommitmentTypeIdentifier ::= OBJECT IDENTIFIER
skipping to change at page 67, line 23 skipping to change at page 73, line 35
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) cti(6) 4} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) cti(6) 4}
id-cti-ets-proofOfApproval OBJECT IDENTIFIER ::= id-cti-ets-proofOfApproval OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) cti(6) 5} smime(16) cti(6) 5}
id-cti-ets-proofOfCreation OBJECT IDENTIFIER ::= id-cti-ets-proofOfCreation OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) cti(6) 6} smime(16) cti(6) 6}
-- Signer-location attribute
id-aa-ets-signerLocation OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-signerLocation OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 17} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 17}
SignerLocation ::= SEQUENCE { SignerLocation ::= SEQUENCE {
-- at least one of the following shall be present -- at least one of the following shall be present
countryName [0] DirectoryString OPTIONAL, countryName [0] DirectoryString OPTIONAL,
-- As used to name a Country in X.500 -- As used to name a Country in X.500
localityName [1] DirectoryString OPTIONAL, localityName [1] DirectoryString OPTIONAL,
-- As used to name a locality in X.500 -- As used to name a locality in X.500
postalAdddress [2] PostalAddress OPTIONAL } postalAdddress [2] PostalAddress OPTIONAL }
PostalAddress ::= SEQUENCE SIZE(1..6) OF DirectoryString PostalAddress ::= SEQUENCE SIZE(1..6) OF DirectoryString
-- Signer-attributes attribute
id-aa-ets-signerAttr OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-signerAttr OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 18} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 18}
SignerAttribute ::= SEQUENCE OF CHOICE { SignerAttribute ::= SEQUENCE OF CHOICE {
claimedAttributes [0] ClaimedAttributes, claimedAttributes [0] ClaimedAttributes,
certifiedAttributes [1] CertifiedAttributes } certifiedAttributes [1] CertifiedAttributes }
ClaimedAttributes ::= SEQUENCE OF Attribute ClaimedAttributes ::= SEQUENCE OF Attribute
CertifiedAttributes ::= AttributeCertificate CertifiedAttributes ::= AttributeCertificate
-- as defined in RFC 3281 : see section 4.1 -- as defined in RFC 3281: see Section 4.1
-- Content-time-stamp attribute
id-aa-ets-contentTimestamp OBJECT IDENTIFIER ::= id-aa-ets-contentTimestamp OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 20} smime(16) id-aa(2) 20}
ContentTimestamp ::= TimeStampToken ContentTimestamp ::= TimeStampToken
-- Signature-time-stamp attribute
id-aa-signatureTimeStampToken OBJECT IDENTIFIER ::= id-aa-signatureTimeStampToken OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 14} smime(16) id-aa(2) 14}
SignatureTimeStampToken ::= TimeStampToken SignatureTimeStampToken ::= TimeStampToken
-- Complete-certificate-references attribute
id-aa-ets-certificateRefs OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-certificateRefs OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 21} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 21}
CompleteCertificateRefs ::= SEQUENCE OF OtherCertID CompleteCertificateRefs ::= SEQUENCE OF OtherCertID
-- Complete-revocation-references attribute
id-aa-ets-revocationRefs OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-revocationRefs OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 22} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 22}
CompleteRevocationRefs ::= SEQUENCE OF CrlOcspRef CompleteRevocationRefs ::= SEQUENCE OF CrlOcspRef
CrlOcspRef ::= SEQUENCE { CrlOcspRef ::= SEQUENCE {
crlids [0] CRLListID OPTIONAL, crlids [0] CRLListID OPTIONAL,
ocspids [1] OcspListID OPTIONAL, ocspids [1] OcspListID OPTIONAL,
otherRev [2] OtherRevRefs OPTIONAL otherRev [2] OtherRevRefs OPTIONAL
skipping to change at page 69, line 4 skipping to change at page 75, line 30
ocspIdentifier OcspIdentifier, ocspIdentifier OcspIdentifier,
ocspRepHash OtherHash OPTIONAL ocspRepHash OtherHash OPTIONAL
} }
OcspIdentifier ::= SEQUENCE { OcspIdentifier ::= SEQUENCE {
ocspResponderID ResponderID, ocspResponderID ResponderID,
-- As in OCSP response data -- As in OCSP response data
producedAt GeneralizedTime producedAt GeneralizedTime
-- As in OCSP response data -- As in OCSP response data
} }
OtherRevRefs ::= SEQUENCE { OtherRevRefs ::= SEQUENCE {
otherRevRefType OtherRevRefType, otherRevRefType OtherRevRefType,
otherRevRefs ANY DEFINED BY otherRevRefType otherRevRefs ANY DEFINED BY otherRevRefType
} }
OtherRevRefType ::= OBJECT IDENTIFIER OtherRevRefType ::= OBJECT IDENTIFIER
-- Certificate-values attribute
id-aa-ets-certValues OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-certValues OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 23} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 23}
CertificateValues ::= SEQUENCE OF Certificate CertificateValues ::= SEQUENCE OF Certificate
-- Certificate-revocation-values attribute
id-aa-ets-revocationValues OBJECT IDENTIFIER ::= { iso(1) id-aa-ets-revocationValues OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 24} smime(16) id-aa(2) 24}
RevocationValues ::= SEQUENCE { RevocationValues ::= SEQUENCE {
crlVals [0] SEQUENCE OF CertificateList OPTIONAL, crlVals [0] SEQUENCE OF CertificateList OPTIONAL,
ocspVals [1] SEQUENCE OF BasicOCSPResponse OPTIONAL, ocspVals [1] SEQUENCE OF BasicOCSPResponse OPTIONAL,
otherRevVals [2] OtherRevVals OPTIONAL} otherRevVals [2] OtherRevVals OPTIONAL}
OtherRevVals ::= SEQUENCE { OtherRevVals ::= SEQUENCE {
otherRevValType OtherRevValType, otherRevValType OtherRevValType,
otherRevVals ANY DEFINED BY otherRevValType otherRevVals ANY DEFINED BY otherRevValType
} }
OtherRevValType ::= OBJECT IDENTIFIER OtherRevValType ::= OBJECT IDENTIFIER
-- CAdES-C time-stamp attribute
id-aa-ets-escTimeStamp OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-escTimeStamp OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 25} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 25}
ESCTimeStampToken ::= TimeStampToken ESCTimeStampToken ::= TimeStampToken
-- Time-Stamped Certificates and CRLs -- Time-Stamped Certificates and CRLs
id-aa-ets-certCRLTimestamp OBJECT IDENTIFIER ::= { iso(1) id-aa-ets-certCRLTimestamp OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 26} smime(16) id-aa(2) 26}
TimestampedCertsCRLs ::= TimeStampToken TimestampedCertsCRLs ::= TimeStampToken
-- Archive time-stamp attribute
id-aa-ets-archiveTimestampV2 OBJECT IDENTIFIER ::= { iso(1) id-aa-ets-archiveTimestampV2 OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 48} smime(16) id-aa(2) 48}
ArchiveTimeStampToken ::= TimeStampToken ArchiveTimeStampToken ::= TimeStampToken
-- Attribute-certificate-references attribute
id-aa-ets-attrCertificateRefs OBJECT IDENTIFIER ::= { iso(1) id-aa-ets-attrCertificateRefs OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 44} smime(16) id-aa(2) 44}
AttributeCertificateRefs ::= SEQUENCE OF OtherCertID AttributeCertificateRefs ::= SEQUENCE OF OtherCertID
-- Attribute-revocation-references attribute
id-aa-ets-attrRevocationRefs OBJECT IDENTIFIER ::= { iso(1) id-aa-ets-attrRevocationRefs OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 45} smime(16) id-aa(2) 45}
AttributeRevocationRefs ::= SEQUENCE OF CrlOcspRef AttributeRevocationRefs ::= SEQUENCE OF CrlOcspRef
END END
A.2 Signature format definitions using X.680 ASN.1 syntax A.2. Signature Format Definitions Using X.680 ASN.1 Syntax
NOTE: The ASN.1 module defined in section A.1 has precedence over that NOTE: The ASN.1 module defined in Annex A.1 has precedence over
defined in section A.2 using syntax defined in ITU-T that defined in Annex A.2 using syntax defined in ITU-T
Recommendation X.680 (1997) [8] in the case of any conflict. Recommendation X.680 (1997) [8] in the case of any conflict.
ETS-ElectronicSignatureFormats-ExplicitSyntax97 { iso(1) member-body(2) ETS-ElectronicSignatureFormats-ExplicitSyntax97 { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-mod(0) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-mod(0)
eSignature-explicit97(29)} eSignature-explicit97(29)}
DEFINITIONS EXPLICIT TAGS ::= DEFINITIONS EXPLICIT TAGS ::=
BEGIN BEGIN
skipping to change at page 72, line 41 skipping to change at page 78, line 44
DirectoryString {} DirectoryString {}
FROM SelectedAttributeTypes FROM SelectedAttributeTypes
{joint-iso-itu-t ds(5) module(1) selectedAttributeTypes(5) 4} {joint-iso-itu-t ds(5) module(1) selectedAttributeTypes(5) 4}
; ;
-- Definitions of Object Identifier arcs used in the present document -- Definitions of Object Identifier arcs used in the present document
-- ================================================================== -- ==================================================================
-- OID used referencing electronic signature mechanisms based -- OID used referencing electronic signature mechanisms based
-- on the present document for use with the IDUP API (see Annex D)
id-etsi-es-IDUP-Mechanism-v1 OBJECT IDENTIFIER ::= id-etsi-es-IDUP-Mechanism-v1 OBJECT IDENTIFIER ::=
{ itu-t(0) identified-organization(4) etsi(0) { itu-t(0) identified-organization(4) etsi(0)
electronic-signature-standard (1733) part1 (1) idupMechanism (4) electronic-signature-standard (1733) part1 (1) idupMechanism (4)
etsiESv1(1) } etsiESv1(1) }
-- Basic ES Attributes Defined in the present document -- Basic ES Attributes Defined in the present document
-- =================================================== -- ===================================================
-- CMS Attributes defined in the present document -- CMS Attributes defined in the present document
skipping to change at page 73, line 22 skipping to change at page 79, line 27
certs SEQUENCE OF OtherCertID, certs SEQUENCE OF OtherCertID,
policies SEQUENCE OF PolicyInformation OPTIONAL policies SEQUENCE OF PolicyInformation OPTIONAL
-- NOT USED IN THE PRESENT DOCUMENT -- NOT USED IN THE PRESENT DOCUMENT
} }
OtherCertID ::= SEQUENCE { OtherCertID ::= SEQUENCE {
otherCertHash OtherHash, otherCertHash OtherHash,
issuerSerial IssuerSerial OPTIONAL } issuerSerial IssuerSerial OPTIONAL }
OtherHash ::= CHOICE { OtherHash ::= CHOICE {
sha1Hash OtherHashValue, -- This contains a SHA-1 hash sha1Hash OtherHashValue,
-- This contains a SHA-1 hash
otherHash OtherHashAlgAndValue} otherHash OtherHashAlgAndValue}
-- Policy ES Attributes Defined in the present document -- Policy ES Attributes Defined in the present document
-- ==================================================== -- ====================================================
-- Mandatory Basic Electronic Signature Attributes, plus in addition. -- Mandatory Basic Electronic Signature Attributes, plus in addition.
-- Signature Policy Identifier -- Signature Policy Identifier
id-aa-ets-sigPolicyId OBJECT IDENTIFIER ::= { iso(1) id-aa-ets-sigPolicyId OBJECT IDENTIFIER ::= { iso(1)
member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
skipping to change at page 76, line 27 skipping to change at page 82, line 44
id-aa-ets-signerAttr OBJECT IDENTIFIER ::= { iso(1) member-body(2) id-aa-ets-signerAttr OBJECT IDENTIFIER ::= { iso(1) member-body(2)
us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 18} us(840) rsadsi(113549) pkcs(1) pkcs-9(9) smime(16) id-aa(2) 18}
SignerAttribute ::= SEQUENCE OF CHOICE { SignerAttribute ::= SEQUENCE OF CHOICE {
claimedAttributes [0] ClaimedAttributes, claimedAttributes [0] ClaimedAttributes,
certifiedAttributes [1] CertifiedAttributes } certifiedAttributes [1] CertifiedAttributes }
ClaimedAttributes ::= SEQUENCE OF Attribute ClaimedAttributes ::= SEQUENCE OF Attribute
CertifiedAttributes ::= AttributeCertificate CertifiedAttributes ::= AttributeCertificate
-- as defined in RFC 3281 : see section 4.1 -- as defined in RFC 3281: see Section 4.1
-- Content Timestamp -- Content Timestamp
id-aa-ets-contentTimestamp OBJECT IDENTIFIER ::= id-aa-ets-contentTimestamp OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 20} smime(16) id-aa(2) 20}
ContentTimestamp ::= TimeStampToken ContentTimestamp ::= TimeStampToken
-- Signature Timestamp -- Signature Timestamp
skipping to change at page 80, line 5 skipping to change at page 86, line 5
-- Attribute revocation references -- Attribute revocation references
id-aa-ets-attrRevocationRefs OBJECT IDENTIFIER ::= id-aa-ets-attrRevocationRefs OBJECT IDENTIFIER ::=
{ iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9) { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
smime(16) id-aa(2) 45} smime(16) id-aa(2) 45}
AttributeRevocationRefs ::= SEQUENCE OF CrlOcspRef AttributeRevocationRefs ::= SEQUENCE OF CrlOcspRef
END END
Annex B (informative): Extended forms of Electronic Signatures Annex B (Informative): Extended Forms of Electronic Signatures
Section 4 provides on overview of the various formats of electronic Section 4 provides an overview of the various formats of electronic
signatures included in the present document. This annex lists the signatures included in the present document. This annex lists the
attributes that need to be present in the various extended electronic attributes that need to be present in the various extended electronic
signature formats and provide example validation sequences using the signature formats and provides example validation sequences using the
extended formats. extended formats.
B.1 Extended forms of validation data B.1. Extended Forms of Validation Data
The complete validation data (CAdES-C) described in section 4.3 and The Complete validation data (CAdES-C) described in Section 4.3 and
illustrated in figure 3 may be extended to create Electronic Signatures illustrated in Figure 3 may be extended to create electronic
with extended validation data. Some Electronic Signatures forms that signatures with extended validation data. Some electronic signature
include extended validation are explained below. forms that include extended validation are explained below.
An X-Long electronic signature (CAdES-X Long) is when the values of the An X-Long electronic signature (CAdES-X Long) is the CAdES-C with the
certificates and revocation information are added to the CAdES-C. values of the certificates and revocation information.
This form of Electronic Signature can be useful when the verifier does This form of electronic signature can be useful when the verifier
not have direct access to the following information: does not have direct access to the following information:
- the signer's certificate; - the signer's certificate;
- all the CA certificates that make up the full certification path; - all the CA certificates that make up the full certification
path;
- all the associated revocation status information, as referenced - all the associated revocation status information, as referenced
in the CAdES-C. in the CAdES-C.
In some situations additional time-stamps may be created and added to In some situations, additional time-stamps may be created and added
the Electronic Signatures as additional attributes. For example: to the Electronic Signatures as additional attributes. For example:
- time-stamping all the validation data as held with the ES (CAdES- - time-stamping all the validation data as held with the ES
C), this eXtended validation data is called a CAdES-X Type 1; or (CAdES-C), this eXtended validation data is called a CAdES-X
Type 1; or
- time-stamping individual reference data as used for complete - time-stamping individual reference data as used for complete
validation. This form of eXtended validation data is called an validation. This form of eXtended validation data is called an
CAdES-X Type 2. CAdES-X Type 2.
NOTE 1: The advantages/drawbacks for CAdES-X Type 1 and CAdES-X Type 2 NOTE 1: The advantages/drawbacks for CAdES-X Type 1 and CAdES-X
are discussed in section C.4.4. Type 2 are discussed in Annex C.4.4.
The above time-stamp forms can be useful when it is required to counter The above time-stamp forms can be useful when it is required to
the risk that any CA keys used in the certificate chain may be counter the risk that any CA keys used in the certificate chain may
compromised. be compromised.
A combination of the two formats above may be used. This form of A combination of the two formats above may be used. This form of
eXtended validation data is called an ES X-Long Type 1 or CAdES-X Long eXtended validation data is called an ES X-Long Type 1 or CAdES-X
Type 2. This form of Electronic Signature can be useful when the Long Type 2. This form of electronic signature can be useful when
verifier needs both the values and proof of when the validation data the verifier needs both the values and proof of when the validation
existed. data existed.
NOTE 2: The advantages/drawbacks for CAdES-X long Type 1 and CAdES-X NOTE 2: The advantages/drawbacks for CAdES-X long Type 1 and
long Type 2 are discussed in section C.4.6. CAdES-X long Type 2 are discussed in Annex C.4.6.
B.1.1 CAdES-X Long B.1.1. CAdES-X Long
An Electronic Signature with the additional validation data forming the An electronic signature with the additional validation data forming
CAdES-X Long form (CAdES-X-Long)) is illustrated in figure B.1 and the CAdES-X Long form (CAdES-X-Long) is illustrated in Figure B.1 and
comprises the following: comprises the following:
- CAdES-BES or CAdES-EPES as defined in sections 4.3 , 5.7 or 5.8; - CAdES-BES or CAdES-EPES, as defined in Sections 4.3 , 5.7, or
5.8;
- complete-certificate-references attribute as defined in section - complete-certificate-references attribute, as defined in Section
6.2.1; 6.2.1;
- complete-revocation-references attribute as defined in section - complete-revocation-references attribute, as defined in Section
6.2.2. 6.2.2.
The following attributes are required if a TSP is not providing a time- The following attributes are required if a TSP is not providing a
mark of the ES: time-mark of the ES:
- signature-time-stamp attribute as defined in section 6.1.1. - signature-time-stamp attribute, as defined in Section 6.1.1.
The following attributes are required if the full certificate values The following attributes are required if the full certificate values
and revocation values are not already included in the CAdES-BES or and revocation values are not already included in the CAdES-BES or
CAdES-EPES: CAdES-EPES:
- certificate-values attribute as defined in section 6.3.3; - certificate-values attribute, as defined in Section 6.3.3;
- revocation-values attribute, as defined in section 6.3.4.
If attributes certificates are used then the following attributes may - revocation-values attribute, as defined in Section 6.3.4.
be present:
- attribute-certificate-references attribute defined in section If attributes certificates are used, then the following attributes
may be present:
- attribute-certificate-references attribute, defined in Section
6.2.3; 6.2.3;
- attribute-revocation-references attribute as defined in section - attribute-revocation-references attribute, as defined in Section
6.2.4. 6.2.4.
Other unsigned attributes may be present, but are not required. Other unsigned attributes may be present, but are not required.
NOTE: Attribute certificate and revocation references are only NOTE: Attribute certificate and revocation references are only
present if a user attribute certificate is present in the present if a user attribute certificate is present in the
electronic signature, see sections 6.2.2 and 6.2.3. electronic signature; see Sections 6.2.2 and 6.2.3.
+---------------------- CAdES-X-Long --------------------------------+ +---------------------- CAdES-X-Long --------------------------------+
|+-------------------------------------- CAdES-C ---+ | |+-------------------------------------- CAdES-C ---+ |
|| +----------+ | +-------------+| || +----------+ | +-------------+|
||+----- CAdES-BES or CAdES-EPES ----+ |Timestamp | | | || ||+----- CAdES-BES or CAdES-EPES ----+ |Timestamp | | | ||
||| | |over | | | Complete || ||| | |over | | | Complete ||
|||+---------++----------++---------+| |digital | | | certificate || |||+---------++----------++---------+| |digital | | | certificate ||
|||| || || || |signature | | | and || |||| || || || |signature | | | and ||
||||Signer's || Signed ||Digital || | | | | revocation || ||||Signer's || Signed ||Digital || | | | | revocation ||
||||Document ||Attributes||signature|| |Optional | | | data || ||||Document ||Attributes||signature|| |Optional | | | data ||
skipping to change at page 82, line 30 skipping to change at page 88, line 34
|| |and || | || |and || |
|| |revocation || | || |revocation || |
|| |references || | || |references || |
|| +-----------+| | || +-----------+| |
|+--------------------------------------------------+ | |+--------------------------------------------------+ |
| | | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
Figure B.1 : Illustration of CAdES-X-Long Figure B.1 : Illustration of CAdES-X-Long
B.1.2 CAdES-X Type 1 B.1.2. CAdES-X Type 1
An Electronic Signature with the additional validation data forming the An electronic signature with the additional validation data forming
eXtended Validation Data - Type 1 X is illustrated in figure B.2 and the eXtended validation data - Type 1 X is illustrated in Figure B.2
comprises the following: and comprises the following:
- the CAdES-BES or CAdES-EPES as defined in sections 4.2, 5.7 or - the CAdES-BES or CAdES-EPES, as defined in Sections 4.2, 5.7, or
5.8; 5.8;
- complete-certificate-references attribute as defined in section - complete-certificate-references attribute, as defined in Section
6.2.1; 6.2.1;
- complete-revocation-references attribute as defined in section - complete-revocation-references attribute, as defined in Section
6.2.2; 6.2.2;
- CAdES-C-Timestamp attribute, as defined in section 6.3.5. - CAdES-C-Timestamp attribute, as defined in Section 6.3.5.
The following attributes are required if a TSP is not providing a time- The following attributes are required if a TSP is not providing a
mark of the ES: time-mark of the ES:
- signature-time-stamp attribute as defined in section 6.1.1. - signature-time-stamp attribute, as defined in Section 6.1.1.
If attributes certificates are used then the following attributes may If attributes certificates are used, then the following attributes
be present: may be present:
- attribute-certificate-references attribute defined in section - attribute-certificate-references attribute, defined in Section
6.2.3; 6.2.3;
- attribute-revocation-references attribute as defined in section - attribute-revocation-references attribute, as defined in Section
6.2.4. 6.2.4.
Other unsigned attributes may be present, but are not required. Other unsigned attributes may be present, but are not required.
+------------------------ CAdES-X-Type 1 ----------------------------+ +------------------------ CAdES-X-Type 1 ----------------------------+
|+---------------------------------- CAdES-C ------+ | |+---------------------------------- CAdES-C ------+ |
|| +----------+ | +-------------+ | || +----------+ | +-------------+ |
||+--- CAdES-BES or CAdES-EPES ------+|Timestamp | | | | | ||+--- CAdES-BES or CAdES-EPES ------+|Timestamp | | | | |
||| ||over | | | | | ||| ||over | | | | |
|||+---------++----------++---------+||digital | | | | | |||+---------++----------++---------+||digital | | | | |
skipping to change at page 83, line 41 skipping to change at page 90, line 5
|| | and || | || | and || |
|| |revocation || | || |revocation || |
|| |references || | || |references || |
|| +-----------+| | || +-----------+| |
|+-------------------------------------------------+ | |+-------------------------------------------------+ |
| | | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
Figure B.2 : Illustration of CAdES-X Type 1 Figure B.2 : Illustration of CAdES-X Type 1
B.1.3 CAdES-X Type 2 B.1.3. CAdES-X Type 2
An Electronic Signature with the additional validation data forming An electronic signature with the additional validation data forming
the eXtended Validation Data - Type 2 X is illustrated in figure B.3. the eXtended Validation Data - Type 2 X is illustrated in Figure B.3
and comprises the following: and comprises the following:
- CAdES-BES or CAdES-EPES as defined in sections 4.2, 5.7 or 5.8; - CAdES-BES or CAdES-EPES, as defined in Sections 4.2, 5.7, or
5.8;
- complete-certificate-references attribute as defined in section - complete-certificate-references attribute, as defined in Section
6.2.1; 6.2.1;
- complete-revocation-references attribute as defined in section - complete-revocation-references attribute, as defined in Section
6.2.2; 6.2.2;
- time-stamped-certs-crls-references attribute as defined in section
6.3.6.
The following attributes are required if a TSP is not providing a time- - time-stamped-certs-crls-references attribute, as defined in
mark of the ES: Section 6.3.6.
- signature-time-stamp attribute as defined in section 6.1.1. The following attributes are required if a TSP is not providing a
time-mark of the ES:
If attributes certificates are used then the following attributes may - signature-time-stamp attribute, as defined in Section 6.1.1.
be present:
- attribute-certificate-references attribute defined in section If attributes certificates are used, then the following attributes
may be present:
- attribute-certificate-references attribute, defined in Section
6.2.3; 6.2.3;
- attribute-revocation-references attribute as defined in section
- attribute-revocation-references attribute, as defined in Section
6.2.4. 6.2.4.
Other unsigned attributes may be present, but are not required. Other unsigned attributes may be present, but are not required.
+----------------------- CAdES-X-Type 2 -----------------------------+ +----------------------- CAdES-X-Type 2 -----------------------------+
|+-------------------------------------- CAdES-C --+ | |+-------------------------------------- CAdES-C --+ |
|| +----------+ | | || +----------+ | |
||+-- CAdES-BES or CAdES-EPES -------+|Timestamp | | | ||+-- CAdES-BES or CAdES-EPES -------+|Timestamp | | |
||| ||over | | | ||| ||over | | |
|||+---------++----------++---------+||digital | | +-------------+ | |||+---------++----------++---------+||digital | | +-------------+ |
skipping to change at page 84, line 47 skipping to change at page 91, line 30
|| |and || | || |and || |
|| |revocation || | || |revocation || |
|| |references || | || |references || |
|| +-----------+| | || +-----------+| |
|+-------------------------------------------------+ | |+-------------------------------------------------+ |
| | | |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
Figure B.3 : Illustration of CAdES-X Type 2 Figure B.3 : Illustration of CAdES-X Type 2
B.1.4 CAdES-X Long Type 1 and CAdES-X Long Type 2 B.1.4. CAdES-X Long Type 1 and CAdES-X Long Type 2
An Electronic Signature with the additional validation data forming the An electronic signature with the additional validation data forming
CAdES-X Long Type 1 and CAdES-X Long Type 2 is illustrated in the CAdES-X Long Type 1 and CAdES-X Long Type 2 is illustrated in
figure B.4 and comprises the following: Figure B.4 and comprises the following:
- CAdES-BES or CAdES-EPES as defined in sections 4.3, 5.7 or 5.8; - CAdES-BES or CAdES-EPES, as defined in Sections 4.3, 5.7, or
5.8;
- complete-certificate-references attribute as defined in section - complete-certificate-references attribute, as defined in Section
6.2.1; 6.2.1;
- complete-revocation-references attribute as defined in section - complete-revocation-references attribute, as defined in Section
6.2.2; 6.2.2;
The following attributes are required if a TSP is not providing a time- The following attributes are required if a TSP is not providing a
mark of the ES: time-mark of the ES:
- signature-time-stamp attribute as defined in section 6.1.1. - signature-time-stamp attribute, as defined in Section 6.1.1.
The following attributes are required if the full certificate values The following attributes are required if the full certificate values
and revocation values are not already included in the CAdES-BES or and revocation values are not already included in the CAdES-BES or
CAdES-EPES: CAdES-EPES:
- certificate-values attribute as defined in section 6.3.3; - certificate-values attribute, as defined in Section 6.3.3;
- revocation-values attribute, as defined in section 6.3.4.
If attributes certificates are used then the following attributes may - revocation-values attribute, as defined in Section 6.3.4.
be present:
- attribute-certificate-references attribute defined in section If attributes certificates are used, then the following attributes
may be present:
- attribute-certificate-references attribute, defined in Section
6.2.3; 6.2.3;
- attribute-revocation-references attribute as defined in section - attribute-revocation-references attribute, as defined in Section
6.2.4. 6.2.4.
Plus one of the following attributes is required: Plus one of the following attributes is required:
- CAdES-C-Timestamp attribute, as defined in section 6.3.5; - CAdES-C-Timestamp attribute, as defined in Section 6.3.5;
- time-stamped-certs-crls-references attribute as defined in section
6.3.6. - time-stamped-certs-crls-references attribute, as defined in
Section 6.3.6.
Other unsigned attributes may be present, but are not required. Other unsigned attributes may be present, but are not required.
+---------------------- CAdES-X-Type 1 or 2 ------------------------+ +---------------------- CAdES-X-Type 1 or 2 ------------------------+
| +--------------+| | +--------------+|
|+-------------------------------------- CAdES-C --+|+------------+|| |+-------------------------------------- CAdES-C --+|+------------+||
|| +----------+ ||| Timestamp ||| || +----------+ ||| Timestamp |||
||+-- CAdES-BES or CAdES-EPES -------+|Timestamp | ||| over ||| ||+-- CAdES-BES or CAdES-EPES -------+|Timestamp | ||| over |||
||| ||over | ||| CAdES-C ||| ||| ||over | ||| CAdES-C |||
|||+---------++----------++---------+||digital | | +------------+ | |||+---------++----------++---------+||digital | | +------------+ |
skipping to change at page 86, line 35 skipping to change at page 93, line 35
|| +-----------+| |certificate | | || +-----------+| |certificate | |
|+-------------------------------------------------+ | and | | |+-------------------------------------------------+ | and | |
| |revocation | | | |revocation | |
| | values | | | | values | |
| +------------+ | | +------------+ |
+-------------------------------------------------------------------+ +-------------------------------------------------------------------+
Figure B.4 : Illustration of CAdES-X Long Type 1 Figure B.4 : Illustration of CAdES-X Long Type 1
and CAdES-X Long Type 2 and CAdES-X Long Type 2
B.2 Timestamp extensions B.2. Time-Stamp Extensions
Each instance of time-stamp attribute may include as unsigned Each instance of the time-stamp attribute may include, as unsigned
attributes in the signedData of the timestamp the following attribute attributes in the signedData of the time-stamp, the following
related to the TSU: attributes related to the TSU:
- complete-certificate-references attribute of the TSU as defined - complete-certificate-references attribute of the TSU, as defined
in section 6.2.1; in Section 6.2.1;
- complete-revocation-references attribute of the TSU as defined in - complete-revocation-references attribute of the TSU, as defined
section 6.2.2; in Section 6.2.2;
- certificate-values attribute; of the TSU as defined in section - certificate-values attribute of the TSU, as defined in Section
6.3.3; 6.3.3;
- revocation-values attribute, of the TSU as defined in section - revocation-values attribute of the TSU, as defined in Section
6.3.4. 6.3.4.
Other unsigned attributes may be present, but are not required. Other unsigned attributes may be present, but are not required.
B.3 Archive validation data (CAdES-A) B.3. Archive Validation Data (CAdES-A)
Before the algorithms, keys and other cryptographic data used at the Before the algorithms, keys, and other cryptographic data used at the
time the CAdES-C was built become weak and the cryptographic functions time the CAdES-C was built become weak and the cryptographic
become vulnerable, or the certificates supporting previous time-stamps functions become vulnerable, or the certificates supporting previous
expires, the signed data, the CAdES-C and any additional information time-stamps expire, the signed data, the CAdES-C, and any additional
(i.e. any CAdES-X) should be time-stamped. If possible this should use information (i.e., any CAdES-X) should be time-stamped. If possible,
stronger algorithms (or longer key lengths) than in the original time- this should use stronger algorithms (or longer key lengths) than in
stamp. This additional data and time-stamp is called Archive the original time-stamp. This additional data and time-stamp is
Validation Data required for the ES Archive format (CAdES-A). The called Archive validation data required for the ES Archive format
Time-stamping process may be repeated every time the protection used to (CAdES-A). The Time-stamping process may be repeated every time the
time-stamp a previous CAdES-A becomes weak. An CAdES-A may thus bear protection used to time-stamp a previous CAdES-A becomes weak. A
multiple embedded time stamps. CAdES-A may thus bear multiple embedded time-stamps.
An example of an Electronic Signature (ES), with the additional An example of an electronic signature (ES), with the additional
validation data for the CAdES-C and CAdES-X forming the CAdES-A is validation data for the CAdES-C and CAdES-X forming the CAdES-A is
illustrated in figure B.5. illustrated in Figure B.5.
+--------------------------- CAdES-A---------------------------------+ +--------------------------- CAdES-A---------------------------------+
|+----------------------------------------------------+ | |+----------------------------------------------------+ |
|| +--------------+| +----------+ | || +--------------+| +----------+ |
||+--------------------- CAdES-C ----+|+------------+|| | | | ||+--------------------- CAdES-C ----+|+------------+|| | | |
||| +----------+ ||| Timestamp ||| | | | ||| +----------+ ||| Timestamp ||| | | |
|||+-- CAdES-BES ------+|Timestamp | ||| over ||| | | | |||+-- CAdES-BES ------+|Timestamp | ||| over ||| | | |
|||| or CAdES-EPES ||over | ||| CAdES-C ||| | Archive | | |||| or CAdES-EPES ||over | ||| CAdES-C ||| | Archive | |
|||| ||digital | ||+------------+|| | | | |||| ||digital | ||+------------+|| | | |
|||| ||signature | || or || |Timestamp | | |||| ||signature | || or || |Timestamp | |
skipping to change at page 88, line 7 skipping to change at page 95, line 38
|| |revocation | | | || |revocation | | |
|| | values | | | || | values | | |
|| +------------+ | | || +------------+ | |
|+----------------------------------------------------+ | |+----------------------------------------------------+ |
+--------------------------------------------------------------------+ +--------------------------------------------------------------------+
Figure B.5 : Illustration of CAdES-A Figure B.5 : Illustration of CAdES-A
The CAdES-A comprises the following elements: The CAdES-A comprises the following elements:
- the CAdES-BES or CAdES-EPES including their signed and unsigned - the CAdES-BES or CAdES-EPES, including their signed and unsigned
attributes; attributes;
- complete-certificate-references attribute as defined in section - complete-certificate-references attribute, as defined in Section
6.2.1; 6.2.1;
- complete-revocation-references attribute as defined in section - complete-revocation-references attribute, as defined in Section
6.2.2. 6.2.2.
The following attributes are required if a TSP is not providing a time- The following attributes are required if a TSP is not providing a
mark of the ES: time-mark of the ES:
- signature-time-stamp attribute as defined in section 6.1.1. - signature-time-stamp attribute, as defined in Section 6.1.1.
If attributes certificates are used then the following attributes may If attributes certificates are used, then the following attributes
be present: may be present:
- attribute-certificate-references attribute defined in section - attribute-certificate-references attribute, defined in Section
6.2.3; 6.2.3;
- attribute-revocation-references attribute as defined in section
- attribute-revocation-references attribute, as defined in Section
6.2.4. 6.2.4.
The following attributes are required if the full certificate values The following attributes are required if the full certificate values
and revocation values are not already included in the CAdES-BES or and revocation values are not already included in the CAdES-BES or
CAdES-EPES: CAdES-EPES:
- certificate-values attribute as defined in section 6.3.3; - certificate-values attribute, as defined in Section 6.3.3;
- revocation-values attribute as defined in section 6.3.4.
- revocation-values attribute, as defined in Section 6.3.4.
At least one of the following two attributes is required: At least one of the following two attributes is required:
- CAdES-C-Timestamp attribute as defined in section 6.3.5; - CAdES-C-Timestamp attribute, as defined in Section 6.3.5;
- time-stamped-certs-crls-references attribute as defined in section - time-stamped-certs-crls-references attribute, as defined in
6.3.6. Section 6.3.6.
The following attribute is required: The following attribute is required:
- archive-time-stamp attributes defined in section 6.4.1. - archive-time-stamp attributes, defined in Section 6.4.1.
Several instances of archive-time-stamp attribute may occur with an Several instances of the archive-time-stamp attribute may occur with
electronic signature both over time and from different TSUs. The time- an electronic signature, both over time and from different TSUs. The
stamp should be created using stronger algorithms (or longer key time-stamp should be created using stronger algorithms (or longer key
lengths) than in the original electronic signatures or time-stamps. lengths) than in the original electronic signatures or time-stamps.
Other unsigned attributes of the ES may be present, but are not Other unsigned attributes of the ES may be present, but are not
required. required.
The archive timestamp will itself contain the certificate and The archive-time-stamp will itself contain the certificate and
revocation information required to validate the archive timestamp, this revocation information required to validate the archive-time-stamp;
may include the following unsigned attributes: this may include the following unsigned attributes:
- complete-certificate-references attribute of the TSU as defined - complete-certificate-references attribute of the TSU, as defined
in section 6.2.1; in Section 6.2.1;
- complete-revocation-references attribute of the TSU as defined in - complete-revocation-references attribute of the TSU, as defined
section 6.2.2; in Section 6.2.2;
- certificate-values attribute of the TSU as defined in section - certificate-values attribute of the TSU, as defined in Section
6.3.3; 6.3.3;
- revocation-values attribute of the TSU, as defined in Section
- revocation-values attribute of the TSU as defined in section
6.3.4. 6.3.4.
Other unsigned attributes may be present, but are not required. Other unsigned attributes may be present, but are not required.
B.4 Example validation sequence B.4. Example Validation Sequence
As described earlier the signer or initial verifier may collect all the As described earlier, the signer or initial verifier may collect all
additional data that forms the electronic signature. Figure B.6, and the additional data that forms the electronic signature. Figure B.6
subsequent description, describes how the validation process may build and the subsequent description describe how the validation process
up a complete electronic signature over time. may build up a complete electronic signature over time.
+------------------------------------------ CAdES-C -------------+ +------------------------------------------ CAdES-C -------------+
|+------------------------------- CAdES-T ------+ | |+------------------------------- CAdES-T ------+ |
||+-------------- CAdES ------------+ | | ||+-------------- CAdES ------------+ | |
|||+--------------------++---------+|+---------+| +-----------+ | |||+--------------------++---------+|+---------+| +-----------+ |
|||| ________ || |||Timestamp|| |Complete | | |||| ________ || |||Timestamp|| |Complete | |
|||||Sign.Pol| ||Digital |||over || |certificate| | |||||Sign.Pol| ||Digital |||over || |certificate| |
||||| Id. | Signed ||signature|||digital || | and | | ||||| Id. | Signed ||signature|||digital || | and | |
||||| option.|attributes|| |||signature|| |revocation | | ||||| option.|attributes|| |||signature|| |revocation | |
|||||________| |+---------+|+---------+| |references | | |||||________| |+---------+|+---------+| |references | |
skipping to change at page 90, line 35 skipping to change at page 97, line 46
+----------+ | ^ | ^ |- Validation | +----------+ | ^ | ^ |- Validation |
v | v | | Incomplete | v | v | | Incomplete |
+---------+ +--------+ +-------------+ +---------+ +--------+ +-------------+
|Signature| |Trusted | |Signature| |Trusted |
| Policy | |Service | | Policy | |Service |
| Issuer | |Provider| | Issuer | |Provider|
+---------+ +--------+ +---------+ +--------+
Figure B.6 : Illustration of a CAdES validation sequence Figure B.6 : Illustration of a CAdES validation sequence
Soon after receiving the Electronic Signature (CAdES) from the signer Soon after receiving the electronic signature (CAdES) from the signer
(1), the digital signature value may be checked; the validation process (1), the digital signature value may be checked; the validation
shall at least add a time-stamp (2), unless the signer has provided one process shall at least add a time-stamp (2), unless the signer has
which is trusted by the verifier. The validation process may also provided one which is trusted by the verifier. The validation
validate the electronic signature, using additional data (e.g. process may also validate the electronic signature using additional
certificates, CRL, etc.) provided by trusted service providers. When data (e.g., certificates, CRL, etc.) provided by Trusted Service
applicable, the validation process will also need to conform to the Providers. When applicable, the validation process will also need to
requirements specified in a signature policy. If the validation conform to the requirements specified in a signature policy. If the
process is validation incomplete, then the output from this stage is validation process is validation incomplete, then the output from
the CAdES-T. this stage is the CAdES-T.
To ascertain the validity status as Valid or Invalid and communicate To ascertain the validity status as Valid or Invalid and communicate
that to the user (4) all the additional data required to validate the that to the user (4), all the additional data required to validate
CAdES-C, must be available (e.g. the complete certificate and the CAdES-C must be available (e.g., the complete certificate and
revocation information). revocation information).
Once the data needed to complete validation data references (CAdES-C) Once the data needed to complete validation data references (CAdES-C)
is available then the validation process should: is available, then the validation process should:
- obtain all the necessary additional certificate and revocation - obtain all the necessary additional certificates and revocation
status information; status information;
- complete all the validation checks on the ES, using the complete
- complete all the validation checks on the ES using the complete
certificate and revocation information (if a time-stamp is not certificate and revocation information (if a time-stamp is not
already present, this may be added at the same stage combining already present, this may be added at the same stage, combining
CAdES-T and CAdES-C process); the CAdES-T and CAdES-C processes);
- record the complete certificate and revocation references (3); - record the complete certificate and revocation references (3);
- indicate the validity status to the user (4). - indicate the validity status to the user (4).
At the same time as the validation process creates the CAdES-C, the At the same time as the validation process creates the CAdES-C, the
validation process may provide and/or record the values of certificates validation process may provide and/or record the values of
and revocation status information used in CAdES-C, called the CAdES-X certificates and revocation status information used in CAdES-C (5).
Long (5). The end result is called CAdES-X Long.
This is illustrated in figure B.7. This is illustrated in Figure B.7.
+--