1、 ETSI EN 319 162-2 V1.1.1 (2016-04) Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC); Part 2: Additional ASiC containers EUROPEAN STANDARD ETSI ETSI EN 319 162-2 V1.1.1 (2016-04) 2 Reference DEN/ESI-0019162-2 Keywords ASiC, e-commerce, electronic signature, sec
2、urity ETSI 650 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 fr
3、om: http:/www.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 per
4、ceived difference 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 rev
5、ision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/Comm
6、iteeSupportStaff.aspx Copyright 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
7、authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM an
8、d LTE are Trade Marks of 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 EN 319 162-2 V1.1.1 (2016-04) 3 Contents Intellectual Property Rights 4g3Foreword . 4g3Modal ve
9、rbs terminology 4g3Introduction 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 ASiC additional containers . 6g34.1 Introduction 6g34.2 ASiC-S additional containers . 6g34.2.1 A
10、SiC-S Time assertion additional container . 6g34.3 ASiC-E additional containers . 6g34.3.1 ASiC-E CAdES additional container 6g34.3.2 ASiC-E Time assertion additional container. 7g3Annex A (informative): Using ASiC with existing container specifications 8g3Annex B (informative): ASiC application to
11、archival systems using ER 10g3B.1 Introduction 10g3B.2 Extraction of one single signed data from the archive . 10g3B.3 Extraction of multiple signed data from the archive 10g3Annex C (informative): Example of ASiC-E with CAdES and time-stamp token . 11g3History 13g3ETSI ETSI EN 319 162-2 V1.1.1 (201
12、6-04) 4 Intellectual Property Rights IPRs 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
13、Property Rights (IPRs); Essential, or 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 (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR
14、 searches, has been carried 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 European Standard (EN) has been produce
15、d by ETSI Technical Committee Electronic Signatures and Infrastructures (ESI). The present document is part 2 of a multi-part deliverable specifying Associated Signature Containers (ASiC), as identified below: Part 1: “Building blocks and ASiC baseline containers“; Part 2: “Additional ASiC container
16、s“. National transposition dates Date of adoption of this EN: 25 April 2016 Date of latest announcement of this EN (doa): 31 July 2016 Date of latest publication of new National Standard or endorsement of this EN (dop/e): 31 January 2017 Date of withdrawal of any conflicting National Standard (dow):
17、 31 January 2017 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 ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“
18、 and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. Introduction Part 1 of the present multi-part deliverable, ETSI EN 319 162-1 2 (ASiC part 1 henceforth) specifies the use of container structures for associating either detached CAdES 1 signatures or detached X
19、AdES i.7 signatures or time assertions, with one or more signed objects to which they apply and specifies a number of baseline containers that aim to fulfil the common use cases and allows a number of options. ETSI ETSI EN 319 162-2 V1.1.1 (2016-04) 5 1 Scope Specific communities or use cases may ha
20、ve additional requirements that are not addressed by the baseline containers defined in ASiC part 1 2 that can be built using the building blocks defined there or additional ones. The present document references such specific additional use of ASiC and aims to be used for containers that collect tog
21、ether electronic documents including those supported by OCF, ODF and UCF describing how these container formats can be used to associate digital signatures with any data objects in the container. 2 References 2.1 Normative references References are either specific (identified by date of publication
22、and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the e
23、xpected location 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. The following referenced documents are necessary for the application of the present document.
24、1 ETSI EN 319 122-1: “Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures“. 2 ETSI EN 319 162-1: “Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC); Part 1: Building blocks and ASiC Bas
25、eline containers“. 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, only the cited version applies. For non-specific references, the latest version of the reference document
26、 (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 referenced documents are not necessary for the application of the present document but they assist the user wit
27、h regard to a particular subject area. i.1 Application Note: “APPNOTE.TXT - .ZIP File Format Specification“, PKWARE Inc., September 2012. NOTE: Available at http:/ i.2 Universal Container Format (UCF). NOTE: Available at https:/ i.3 ISO/IEC TS 30135 (all parts): “Information technology - Digital pub
28、lishing - EPUB3“. i.4 OASIS: “Open Document Format for Office Applications (OpenDocument) Version 1.2; Part 3: Packages“, 29 September 2011. i.5 IETF RFC 4998: “Evidence Record Syntax (ERS)“. i.6 IETF RFC 6283: “Extensible Markup Language Evidence Record Syntax (XMLERS)“. i.7 ETSI EN 319 132-1: “Ele
29、ctronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures“. ETSI ETSI EN 319 162-2 V1.1.1 (2016-04) 6 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in CAdES
30、 1, XAdES i.7 and ASiC part 1 2 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in CAdES 1, XAdES i.7 and ASiC part 1 2 apply. 4 ASiC additional containers 4.1 Introduction This clause defines ASiC additional containers designed to maximize interoperability
31、 for ASiC for use cases considered of general use not covered by baseline containers specified in ASiC part 1 2 clause 5: ASiC-S with time assertion specified in clause 4.2.1; ASiC-E with CAdES specified in clause 4.3.1; and ASiC-E with time assertion specified in clause 4.3.2. 4.2 ASiC-S additional
32、 containers 4.2.1 ASiC-S Time assertion additional container The present clause defines the ASiC-S Time assertion additional container. The requirement specified in ASiC part 1 2 for ASiC-S shall apply with the following additional restrictions: a) it shall comply with the specific provision given i
33、n ASiC part 1 2, clause 4.3.3.1 item 2) a) and clause 4.3.3.2, item 4) a), 4) d) or 4) e); b) it may contain additional elements in the META-INF folder as specified in ASiC part 1 2, clause 4.3.3.2 item 5) a) and 5) b); c) it shall support ASiC part 1 2, clause 4.3.3.2 item 2); and d) if one or more
34、 ASiCArchiveManifest files are present they shall comply with ASiC part 1 2, clause A.7 with the additional restriction that only SignedData shall be used to include certificate and revocation information. 4.3 ASiC-E additional containers 4.3.1 ASiC-E CAdES additional container The present clause de
35、fines the ASiC-E CAdES additional container. The requirements specified in ASiC part 1 2 clause 4.4 for ASiC-E shall apply with the following additional restrictions: a) it shall comply with the specific provision given in ASiC part 1 2, clause 4.4.4.1, item 1) a), and clause 4.4.4.2, item 3) a); an
36、d b) it shall support ASiC part 1 2, clause 4.4.5, item 2). NOTE: Implementations compliant with ASiC-E CAdES additional container requirements can support the same levels defined for baseline containers specified in ASiC part 1 2, clause 5. ETSI ETSI EN 319 162-2 V1.1.1 (2016-04) 7 4.3.2 ASiC-E Tim
37、e assertion additional container The present clause defines the ASiC-E time assertion additional container. The requirement specified in ASiC part 1 2 for ASiC-E shall apply with the following additional restrictions: a) it shall comply with the specific provision given in ASiC part 1 2, clause 4.4.
38、4.1, item 1) a), and clause 4.4.4.2, item 3) b) or 4) a) or 4) b); and b) it shall support ASiC part 1 2, clause 4.4.5 item 2). ETSI ETSI EN 319 162-2 V1.1.1 (2016-04) 8 Annex A (informative): Using ASiC with existing container specifications The present annex specifies recommendations for the use o
39、f ASiC containers in a way which is compatible with existing container specifications that define a file structure with associated metadata and signatures. The container may be realized either as a physical container based on ZIP i.1 as required by ASiC part 1 2, clause 4.4.2 item 1) or, when suppor
40、ted by the external specification, as an abstract container with a file system model supporting storage of files in a folder hierarchy. NOTE: UCF i.2 is an example of container formats supporting abstract containers. ASiC part 1 2, clause 4.4.2 item 3), clause 4.4.3.1 should apply, and clause 4.4.3.
41、2 should apply with the following additional requirements: “mimetype“ may be present and should comply with ASiC part 1 2 and contain the media type identifying the container type, if applicable. “META-INF/container.xml“ may be present and should comply with OCF i.3. “META-INF/manifest.xml“ may be p
42、resent and should comply with ODF i.4. “META-INF/metadata.xml“ may be present and should comply with ODF i.4. “META-INF/signatures.xml“ may be present and should comply with OCF i.3 if “mimetype“ is present and its value is “application/epub+zip“. “META-INF/*signatures*.xml“ may be present and shoul
43、d comply with ODF i.4 if “mimetype“ is present and its value is an ODF supported media type. Other files defined in the OCF i.3, UCF i.2 and ODF i.4 formats may be present and combined within ASiC as appropriate and should not violate the format implied by the “mimetype“ file. The following table sp
44、ecifies the general requirements that should apply for all ASiC-E containers. Table A.1 Container files or properties OCF ODF UCF Additional requirements and notes Mimetype may be present may be present may be present a META-INF/manifest.xml may be present should be present may be present b META-INF
45、/container.xml should be present may be present may be present c META-INF/metadata.xml may be present may be present may be present c META-INF/ *signatures*.xml should be present should be present should be present d Container filename extension should be present should be present should be present
46、f, e Archive level ZIP comment may be present may be present may be present g, e Additional requirements: a) If present the value should be conformant to the relevant container specification. b) If present the content should be conformant to ODF i.4. c) If present the content should be conformant to
47、 OCF i.3. d) The filename should be conformant to the relevant container specification. The content root element should be compliant with ASiC part 1 2, clause 4.4.3.2, item 3) b) for ODF i.4, item 3) c) for OCF i.3 and UCF i.2. e) If applicable (i.e. the container is a physical container). ETSI ETS
48、I EN 319 162-2 V1.1.1 (2016-04) 9 f) The file extension should comply with the container media type associated to the container content or with ASiC part 1 2, clause 4.4.3.1, item 2) b). g) Presence and value should be as specified in ASiC part 1 2, clause 4.4.3.1, item 3). ETSI ETSI EN 319 162-2 V1
49、.1.1 (2016-04) 10 Annex B (informative): ASiC application to archival systems using ER B.1 Introduction The present annex specifies a possible way to support the extraction from an archival system of one or more signed data object protected with one or more ERs. B.2 Extraction of one single signed data from the archive When one single
