1、 ETSI TS 102 734 V1.1.1 (2007-02)Technical Specification Electronic Signatures and Infrastructures;Profiles of CMS Advanced Electronic Signaturesbased on TS 101 733 (CAdES)ETSI ETSI TS 102 734 V1.1.1 (2007-02) 2 Reference DTS/ESI-000042 Keywords electronic signature, security ETSI 650 Route des Luci
2、oles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http
3、:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the pr
4、inting on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http
5、:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and
6、 the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being reg
7、istered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 734 V1.1.1 (2007-02) 3 Contents Intellectual Property Rights5 Foreword.5 Introduction 5 1 Scope 6 2 References 6 3 Defini
8、tions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 General requirements .8 4.1 Algorithm requirements .8 4.2 Compliance requirements.8 5 CAdES profile for e-Invoicing.10 5.1 Elements defined in CMS.10 5.1.1 Placement of the signature10 5.1.2 Signer identifier 10 5.1.3 Content type10 5
9、.1.4 Message digest10 5.1.5 Signing time10 5.1.6 Countersignature.11 5.1.7 Parallel signatures.11 5.2 Elements defined in ESS 11 5.2.1 Signing certificate.11 5.3 Additional attributes defined in CAdES.12 5.3.1 Signature time-stamp / time-mark 12 5.4 Additional attributes defined in CAdES for long te
10、rm signatures12 5.4.1 Certificate references 12 5.4.2 Revocation status references.12 5.4.3 Certificate values 13 5.4.4 Revocation status values.13 5.4.5 Archive time-stamp.14 5.5 Other standards.14 5.5.1 X.509 Certificates .14 5.5.2 Certificate key usage for e-Invoicing14 5.5.3 Naming .14 6 CAdES p
11、rofile for e-Government 15 6.1 Elements defined in CMS.15 6.1.1 Placement of the signature15 6.1.2 Signer identifier 16 6.1.3 Content type16 6.1.4 Message digest16 6.1.5 Signing time16 6.1.6 Countersignature.16 6.1.7 Parallel signatures.17 6.2 Elements defined in ESS 17 6.2.1 Signing certificate.17
12、6.3 Additional attributes defined in CAdES.17 6.3.1 Signature time-stamp / time-mark 17 6.4 Additional attributes defined in CAdES for long term signatures18 6.4.1 Certificate references 18 6.4.2 Revocation status references.18 6.4.3 Certificate values 19 6.4.4 Revocation status values.19 ETSI ETSI
13、TS 102 734 V1.1.1 (2007-02) 4 6.4.5 Archive time-stamp.19 6.5 Other standards.20 6.5.1 X.509 Certificates .20 7 CAdES baseline profile20 7.1 Elements defined in CMS.20 7.1.1 Placement of the signature20 7.1.2 Signer identifier 20 7.1.3 Content type20 7.1.4 Message digest21 7.1.5 Signing time21 7.1.6
14、 Countersignature.21 7.1.7 Parallel signatures.21 7.2 Elements defined in ESS 22 7.2.1 Signing certificate.22 7.3 Additional attributes defined in CAdES.22 7.3.1 Signature time-stamp / time-mark 22 7.4 Additional attributes defined in CAdES for long term signatures22 7.4.1 Certificate references 22
15、7.4.2 Revocation status references.23 7.4.3 Certificate values 23 7.4.4 Revocation status values.24 7.4.5 Archive time-stamp.24 7.5 Other standards.24 7.5.1 X.509 Certificates .24 Annex A (informative): Bibliography.26 History 27 ETSI ETSI TS 102 734 V1.1.1 (2007-02) 5 Intellectual Property Rights I
16、PRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or
17、potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carr
18、ied out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technica
19、l Committee Electronic Signatures and Infrastructures (ESI). Introduction TS 101 733 1 (CAdES henceforth) specifies formats for Advanced Electronic Signatures built on CMS 2. That document defines a number of signed and unsigned optional signature attributes, resulting in support for a number of var
20、iations in the signature contents and powerful processing requirements. In order to maximize interoperability in communities applying CAdES to particular environments it is necessary to identify a common set of options that are appropriate to that environment. Such a selection is commonly called a p
21、rofile. The present document defines three profiles that minimize the differences between implementations and so maximize interoperability. The two first profiles are suitable for specific business areas, namely e-Invoicing and e-Government, respectively. The third profile provides a baseline for ot
22、her application areas. Profiles specified in clauses 5, 6 and 7 are based on the actual usage of the CMS 2 and CAdES 1 options, as emerged from a survey conducted by ETSI over a substantial number of prominent European actors in the electronic signature domain. Therefore the following provisions rep
23、resent a general consensus of the use of these standards and hence provide a reliable basis for maximizing interoperability. Nevertheless, in particular business areas and niches there may be specific needs and/or regulations that may require variations to these profiles. ETSI ETSI TS 102 734 V1.1.1
24、 (2007-02) 6 1 Scope The present document profiles the use of TS 101 733 (CAdES) 1 signatures, based on CMS 2 for its use within the following specific environments as follows: e-Invoicing area. e-government area. a baseline for other application areas. These profiles do not repeat the base requirem
25、ents of the referenced standards, but their aim is to maximize interoperability of CMS-based advanced electronic signatures in the e-Invoicing and e-Government business areas. In addition to that, the baseline profile is given as basis for interoperability profiles in other application areas. Option
26、al elements defined in CAdES 1 but not specified in the current document are treated as optional for both generator and verifiers. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either speci
27、fic (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected lo
28、cation might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 1 ETSI TS 101 733 (V1.7.3): “Electronic Signatures and Infrastructures (ESI); CMS Advanced Electronic Sig
29、natures (CAdES)“. 2 IETF RFC 3852: “Cryptographic Message Syntax (CMS)“. 3 IETF RFC 2634: “Enhanced Security Services for S/MIME“. 4 draft-ietf-smime-escertid-01.txt (October 2006): “ESS Update: Adding CertID Algorithm Agility“. 5 ITU-T Recommendation X.509 / ISO/IEC 9594-8: “Information technology
30、- Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks“. 6 IETF RFC 3280: “Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile“. 7 CEN Workshop Agreement 15579 to be published: “E-invoices and digital signatures“
31、. NOTE: As a fault has been identified in the 2006 version CWA 15579, it will be updated soon after publication of this TS. Implementations should refer to this revised version 8 IETF RFC 2560: “X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP“. 9 ETSI TS 102 176-1(
32、V1.2.1): “Electronic Signatures and Infrastructures (ESI); Algorithms and Parameters for Secure Electronic Signatures; Part 1: Hash functions and asymmetric algorithms“. ETSI ETSI TS 102 734 V1.1.1 (2007-02) 7 10 CEN Workshop Agreement 14171 (2004): “General guidelines for electronic signature verif
33、ication“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: generator: any party which creates, or adds attributes to, a signature NOTE: This may be the signatory or any party which initially verifies or further maint
34、ains the signature. long term signatures: signatures that are expected to be verified beyond the signers certificate expiration date and, possibly, even after the expiration date of the certificate of the signers certificate-issuing CA NOTE: Refer to CWA 14171, clause 5.1 10. protocol element: eleme
35、nt of the protocol which may be including data elements and / or elements of procedure service element: element of service that may be provided using one or more protocol elements NOTE: All alternative protocol elements provide an equivalent service to the users of the protocol. short term signature
36、s: signatures that are to be verified for a period of time that does not go beyond the signers certificate expiration date NOTE: Refer to CWA 14171, clause 5.1 10. verifier: entity that validates or verifies an electronic signature The present document makes use of certain key words to signify requi
37、rements. Below follows their definitions: may: Means that a course of action is permissible within the limits of the present document. shall: Means that the definition is an absolute requirement of the present document. It has to strictly be followed in order to conform to the present document. shou
38、ld: Means that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others, or that a certain course of action is preferred but not necessarily required. Implementers may know valid reasons in particular circumstances to ignore this recommendation,
39、 but the full implications must be understood and carefully weighed before choosing a different course. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CA Certification Authority CAdES CMS Advanced Electronic Signatures NOTE: As per TS 101 733 1. CEN Eu
40、ropean Committee for Standardization CMS Cryptographic Message Syntax CRL Certificate Revocation List CWA CEN Workshop Agreement ESS Enhanced Security Services OCSP Online Certificate Status Protocol TSP Trusted Service Providers TST Time-Stamp Token ETSI ETSI TS 102 734 V1.1.1 (2007-02) 8 4 General
41、 requirements 4.1 Algorithm requirements Implementers are strongly recommended to take into account TS 102 176-1 9 when selecting algorithms and key lengths. 4.2 Compliance requirements Profiles in the present document define separated requirements for both generator and verifier of CAdES signatures
42、. Requirements are grouped in three different categories, each one having its corresponding identifier. Table 1 defines these categories and their identifiers. Table 1: Requirement categories Identifier Requirement on generator Requirement on verifier M Generator shall include the element in the sig
43、nature. Verifier shall process the element. R Generator should include the element in the signature. Verifier shall process the element if present. O Generator may include the element in the signature. Verifier may either process or ignore this element and process the rest of the signature. Clauses
44、5 to 7 specify additional requirements on signature formats that must be taken into account along with those ones already present in TS 101 733 (CAdES) 1 and CMS 2. Systems claiming to support the CAdES profile for e-Invoicing shall be compliant with requirements in clauses 5.1, 5.2, 5.3 and 5.5. Sy
45、stems claiming to support the CAdES profile for e-Invoicing with support for long term signatures shall also be compliant with requirements in clause 5.4. Systems claiming to support the CAdES profile for e-Government shall be compliant with requirements in clauses 6.1, 6.2, 6.3 and 6.5. Systems cla
46、iming to support the CAdES profile for e-Government with support for long term signatures shall also be compliant with requirements in clause 6.4. Systems claiming to support the CAdES baseline profile shall be compliant with requirements in clauses 7.1, 7.2, 7.3 and 7.5. Systems claiming to support
47、 the CAdES baseline profile with support of long term signatures shall also be compliant with requirements in clause 7.4. Optional elements defined in CAdES 1 but not specified in the current document are treated as “O“ as above for both generator and verifiers. In certain cases, elements are marked
48、 with an “O“ for both generator and verifier to bring the readers“ attention to the fact that their processing is optional. Certain service elements may be provided by different protocol elements at users choice. In these cases the semantics of M, R and O defined in the table above depend on the req
49、uirement for the service element itself. Tables 2 to 4 (each one applies to a different requirement on the service element) define these semantics. Table 2: Requirements for mandatory service with choices Requirement Identifier for the Service / Protocol element Requirement on generator Requirement on verifier Service = M Generator shall provide the service by including one protocol element chosen from the list of choices. Verifiers shall be able to process at least one of the protocol elements in the list of choic
