1、 ETSI TS 119 422 V1.0.1 (2015-07) Electronic Signatures and Infrastructures (ESI); Time-stamping protocol and time-stamp profiles TECHNICAL SPECIFICATION ETSI ETSI TS 119 422 V1.0.1 (2015-07)2Reference RTS/ESI-0019422-TS Keywords electronic signature, security, time-stamping, trust services ETSI 650
2、 Route des Lucioles 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 The present document can be downloaded from: http:/www.
3、etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived differe
4、nce in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (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 chang
5、e of status. Information on the current status of this and other ETSI documents is available at http:/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: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Co
6、pyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. T
7、he copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2015. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of
8、 ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 119 422 V1.0.1 (2015-07)3Contents Intellectual Property Rights 4g3Foreword . 4g3Modal verbs terminology 4g3Introduct
9、ion 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Requirements for a time-stamping client . 6g34.1 Profile for the format of the request . 6g34.1.1 Core requirement 6g34.1.2 P
10、arameters to be supported . 6g34.1.3 Hash algorithms to be used . 6g34.2 Profile for the format of the response . 7g34.2.1 Core requirement 7g34.2.2 Parameters to be supported . 7g34.2.3 Algorithms to be supported . 7g34.2.4 Key lengths to be supported 7g35 Requirements for a time-stamping server. 7
11、g35.1 Profile for the format of the request . 7g35.1.1 Core requirement 7g35.1.2 Parameters to be supported . 7g35.1.3 Algorithms to be supported . 7g35.2 Profile for the format of the response . 7g35.2.1 Core requirement 7g35.2.2 Parameters to be supported . 8g35.2.3 Algorithms to be used . 8g36 TS
12、U certificate profile 8g36.1 General requirements . 8g36.2 Subject name requirements. 8g36.3 Key lengths requirements . 8g36.4 Key usage requirements . 8g36.5 Algorithm requirements . 9g37 Profiles for the transport protocols to be supported . 9g38 Object identifiers of the cryptographic algorithms
13、. 9g39 Additional requirements for Regulation (EU) No 910/2014 9g39.1 Regulation statement 9g3Annex A (normative): Structure for the policy field . 10g3Annex B (normative): ASN.1 declarations. 11g3History 12g3ETSI ETSI TS 119 422 V1.0.1 (2015-07)4Intellectual Property Rights IPRs essential or potent
14、ially 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 potentially Essential,
15、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:/ipr.etsi.org). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be gi
16、ven 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 Technical Committee Electronic Signatures and I
17、nfrastructures (ESI). The present document was previously published as ETSI TS 101 861 i.2. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the
18、ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. Introduction The present document is aiming to meet the general requirements of the international community to provide trust and confid
19、ence in electronic transactions including, amongst others, applicable requirements from Regulation (EU) No 910/2014 i.3. Time-stamping is critical for digital signatures in order to know whether the digital signature was affixed during the validity period of the certificate. One method of assuring t
20、he signing time is to affix a time-stamp bound to the signature as defined in IETF RFC 3161 1. IETF RFC 3161 1 defines a time-stamp protocol and a time-stamp token format. The present document limits the number of options by placing some additional constraints. ETSI ETSI TS 119 422 V1.0.1 (2015-07)5
21、1 Scope The present document defines a profile for the time-stamping protocol and the time-stamp token defined in IETF RFC 3161 1 including optional ESSCertIDv2 update in IETF RFC 5816 2. It defines what a time-stamping client supports and what a time-stamping server supports. Time-stamp validation
22、is out of scope and is defined in ETSI TS 119 102-1 i.6. 2 References 2.1 Normative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific referen
23、ces, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the ti
24、me of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. 1 IETF RFC 3161: “Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)“. 2 IETF RFC 5816: “ESSCertIDV2 update to RFC 3161“. 3
25、 ETSI TS 119 312: “Electronic Signatures and Infrastructures (ESI); Cryptographic Suites“. 4 ETSI TS 119 412-2: “Electronic Signatures and Infrastructures (ESI); Certificate Profiles; Part 2: Certificate profile for certificates issued to natural persons“. 5 ETSI TS 119 412-3: “Electronic Signatures
26、 and Infrastructures (ESI); Certificate Profiles; Part 3: Certificate profile for certificates issued to legal persons“. 2.2 Informative references References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, onl
27、y the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenc
28、ed documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. i.1 ETSI TS 119 421: “Electronic Signatures and Infrastructures (ESI); Policy and Security Requirements for Trust Service Providers issuing Time-Stamps“. i.2
29、ETSI TS 101 861: “Electronic Signatures and Infrastructures (ESI); Time stamping profile“. i.3 Regulation (EU) No 910/2014 of the European Parliament and of the Council on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/
30、EC. i.4 Recommendation ITU-T X.520 (10/2012): “Information technology - Open Systems Interconnection - The Directory: Selected attribute types“. i.5 IETF RFC 3739: “Internet X.509 Public Key Infrastructure: Qualified Certificates Profile“. ETSI ETSI TS 119 422 V1.0.1 (2015-07)6i.6 ETSI TS 119 102-1:
31、 “Electronic Signatures and Infrastructures (ESI); Procedures for Signature Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: time-
32、stamp: data in electronic form which binds other electronic data to a particular time establishing evidence that these data existed at that time time-stamp token: data object defined in IETF RFC 3161 1, representing a time-stamp time-stamping authority: Trust Service Provider which issues time-stamp
33、 using one or more time-stamping units time-stamping unit: set of hardware and software which is managed as a unit and has a single time-stamp signing key active at a time. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ASN Abstract Syntax Notation EU
34、Europe HTTP HyperText Transfer Protocol HTTPS Hypertext Transfer Protocol over TLS OID Object Identifier RFC Request for Comments TLS Transport Layer Security TSA Time-Stamping AuthorityTSU Time-Stamping Unit 4 Requirements for a time-stamping client 4.1 Profile for the format of the request 4.1.1 C
35、ore requirement A time-stamping client shall support the time-stamping request as defined in IETF RFC 3161 1, clause 2.4.1 with the amendments defined in the following clauses. 4.1.2 Parameters to be supported The following parameters in the time-stamping request should be supported: the reqPolicy;
36、the nonce; and the certReq. 4.1.3 Hash algorithms to be used Hash algorithms used to hash the information to be time-stamped should be as specified in clause A.8 of ETSI TS 119 312 3. This should take into account the expected duration of the time-stamp and recommended hash functions versus time giv
37、en in clause 9.2 of ETSI TS 119 312 3. ETSI ETSI TS 119 422 V1.0.1 (2015-07)74.2 Profile for the format of the response 4.2.1 Core requirement A time-stamping client shall support the time-stamping response as defined in IETF RFC 3161 1, clause 2.4.2 with the amendments defined in the following clau
38、ses. 4.2.2 Parameters to be supported The following requirements apply: the accuracy field shall be supported and understood; and the nonce parameter should be supported; A TSU needs not support ordering hence clients should not depend on the ordering of time-stamps. 4.2.3 Algorithms to be supported
39、 Time-stamp token signature algorithms to be supported shall be as specified in clause A.8 of ETSI TS 119 312 3. 4.2.4 Key lengths to be supported Signature algorithm key lengths for the selected signature algorithm should be supported as recommended in clause 9.3 of ETSI TS 119 312 3. 5 Requirement
40、s for a time-stamping server 5.1 Profile for the format of the request 5.1.1 Core requirement A time-stamping server shall support the time-stamping request as defined in IETF RFC 3161 1, clause 2.4.1 with the amendments defined in the following clauses. 5.1.2 Parameters to be supported The followin
41、g requirements apply: reqPolicy shall be supported; the nonce shall be supported; and certReq shall be supported. 5.1.3 Algorithms to be supported Hash algorithms for the time-stamp data to be supported shall be as specified in clause A.8 of ETSI TS 119 312 3. This should take into account the expec
42、ted duration of the time-stamp and recommended hash functions versus time given in clause 9.2 of ETSI TS 119 312 3. 5.2 Profile for the format of the response 5.2.1 Core requirement A time-stamping server shall support the time-stamping response as defined in IETF RFC 3161 1 clause 2.4.2 with the am
43、endments defined in the following clauses. ETSI ETSI TS 119 422 V1.0.1 (2015-07)85.2.2 Parameters to be supported The requirements from IETF RFC 3161 1, clause 2.4.2 shall apply and the following requirements apply: the policy parameter shall be present as an identifier for the time-stamp policy and
44、 shall conform to annex A; a genTime parameter representing time with a precision necessary to support the declared accuracy shall be supported; the accuracy parameter shall be present and a minimum accuracy of one second shall be supported; the ordering parameter shall not be present or shall be se
45、t to false; and no extension shall be critical. The following requirement applies to the content of the SignedData structure in which the TSTInfo structure is encapsulated: the certificate identifier of the TSU certificate (ESSCertID as in IETF RFC 3161 1 or ESSCerIDv2 as in IETF RFC 5816 2) shall b
46、e included as a signerInfo attribute inside a SigningCertificate attribute. 5.2.3 Algorithms to be used Hash algorithms used to hash the information to be time-stamped and time-stamp token signature algorithms shall be as specified in clause A.8 of ETSI TS 119 312 3. 6 TSU certificate profile 6.1 Ge
47、neral requirements The TSU certificate shall be as defined in ETSI TS 119 412-2 4 for natural person or as defined in ETSI TS 119 412-3 5 for legal person with the amendments defined in the present document. 6.2 Subject name requirements The countryName attribute shall specify the country in which t
48、he TSA is established (which is not necessarily the name of the country where the time-stamping unit is located). The organizationName, when applicable, shall contain the full registered name of the TSA responsible for managing the time-stamping unit. That name should be an officially registered nam
49、e of the TSA. For legal person, an organizationIdentifier attribute should be used as defined in Recommendation ITU-T X.520 i.4. The commonName shall be present. It specifies an identifier for the time-stamping unit. Within the TSA, the attribute commonName uniquely identifies the time-stamping unit used. For natural person, a serialNumber attribute should be used. Additional attributes may be present. 6.3 Key lengths requirements The key length for the selected signature algor
