1、 ETSI EN 319 532-3 V1.1.1 (2018-09) Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 3: Formats EUROPEAN STANDARD ETSI ETSI EN 319 532-3 V1.1.1 (2018-09) 2 Reference DEN/ESI-0019532-3 Keywords e-delivery services, registered e-delivery services, regist
2、ered electronic mail 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 b
3、e downloaded from: 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
4、existing or perceived 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
5、 subject to revision 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.
6、org/People/CommiteeSupportStaff.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 witho
7、ut the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI
8、 registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI EN 319 532-3 V1.1.1 (2018-09) 3 Contents Intellectual Property Rights
9、 4g3Foreword . 4g3Modal verbs terminology 4g3Introduction 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 7g33 Definitions, abbreviations and terminology . 7g33.1 Definitions 7g33.2 Abbreviations . 7g33.3 Terminology . 8g34 Message formats . 8g34.1 Introduction
10、 8g34.2 Internet Message Format in the REM services . 8g34.3 REM message - Structure Definition 10g35 REMS - identification formats . 15g36 REMS - relay metadata formats . 15g36.1 General requirements . 15g36.2 REM message structure 16g36.2.1 REMS relay metadata MIME Header Fields 16g36.2.2 signed d
11、ata MIME Header Fields . 19g36.2.3 REMS introduction MIME Header Fields-Body 19g36.2.3.1 General requirements 19g36.2.3.2 multipart/alternative: free text subsection Header Fields 19g36.2.3.3 multipart/alternative: HTML subsection Header Fields 20g36.2.3.4 Introduction body formats . 20g36.2.4 origi
12、nal message MIME Header Fields 20g36.2.4.1 original message general requirements . 20g36.2.4.2 original message - MIME section Header Fields 20g36.2.4.3 original message - MIME section Body formats . 21g36.2.5 REMS extensions MIME Header Fields . 21g36.2.6 ERDS evidence MIME Header Fields 22g36.2.6.
13、1 General requirements 22g36.2.6.2 Header Fields for XML ERDS evidence usage . 22g36.2.6.3 Header Fields for PDF ERDS evidence usage 23g36.2.7 REMS signature MIME Header Fields-Body . 23g37 REMS - evidence set formats . 24g38 REMS - signatures formats 24g38.1 General . 24g38.2 Signatures individuall
14、y signing ERDS Evidence . 25g38.3 Signatures on REM messages 25g39 Common Service Interface formats 25g39.1 General requirements . 25g39.2 Routing information . 25g39.3 Trust information 26g39.4 Capability management 26g3Annex A (informative): REM message examples 28g3History 35g3ETSI ETSI EN 319 53
15、2-3 V1.1.1 (2018-09) 4 Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables 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
16、 in ETSI SR 000 314: “Intellectual 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 Poli
17、cy, no investigation, including IPR 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. Trademarks The pre
18、sent document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those t
19、rademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This European Standard (EN) has been produced by ETSI Technical Committee Electronic Signatures and Infrastructures (ESI). The present docume
20、nt is part 3 of a multi-part deliverable. Full details of the entire series can be found in part 1 10. National transposition dates Date of adoption of this EN: 23 August 2018 Date of latest announcement of this EN (doa): 30 November 2018 Date of latest publication of new National Standard or endors
21、ement of this EN (dop/e): 31 May 2019 Date of withdrawal of any conflicting National Standard (dow): 31 May 2019 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
22、in clause 3.2 of the 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. ETSI ETSI EN 319 532-3 V1.1.1 (2018-09) 5 Introduction Registered Electronic Mail (REM) is a particular instance o
23、f An “Electronic Registered Delivery Service“ (ERDS). Standard email, used as backbone, makes interoperability smooth and increases usability. At the same time, the application of additional security mechanisms ensures integrity, confidentiality and non-repudiation (of submission, consignment, hando
24、ver, etc.), and protects against risk of loss, theft, damage and any illegitimate modification. The present document aims to cover the common and worldwide-recognized requirements to address electronic registered delivery in a secure and reliable way. Particular attention is paid to the Regulation (
25、EU) No 910/2014 i.5. However, the legal effects are outside the scope of the present document. ETSI ETSI EN 319 532-3 V1.1.1 (2018-09) 6 1 Scope The present document specifies the formats for messages that are produced and handled by a Registered Electronic Mail (REM) service according to the concep
26、ts and semantic defined in ETSI EN 319 522 parts 1 7 and 2 8 and ETSI EN 319 532 parts 1 10 and 2 11. More specifically: a) Specifies how the general ERDS concepts like user content and metadata are identified and mapped in the standard email structure. b) Specifies how the aforementioned concepts a
27、re mapped in the REM service messaging structures. c) Specifies how the ERDS evidence set is plugged inside the REM service messaging structures. d) Specifies additional mechanisms like digital signature and other security controls. 2 References 2.1 Normative references References are either specifi
28、c (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 referenced document (including any amendments) applies. Referenced documents which are not fo
29、und to be publicly available in the expected location might be found at https:/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 th
30、e application of the present document. 1 IETF RFC 8118: “The application/pdf Media Type“. 2 IETF RFC 2183: “Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field“. 3 IETF RFC 5751: “Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message
31、Specification“. 4 IETF RFC 5322: “Internet Message Format“. 5 IETF RFC 2854: “The text/html Media Type“. 6 IETF RFC 7303: “XML Media Types“. 7 ETSI EN 319 522-1: “Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 1: Framework and Architecture“. 8 ETSI EN
32、319 522-2: “Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 2: Semantic Contents“. 9 ETSI EN 319 522-3: “Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery Services; Part 3: Formats“. 10 ETSI EN 319 532-1: “Electronic Signat
33、ures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 1: Framework and Architecture“. 11 ETSI EN 319 532-2: “Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 2: Semantic contents“. 12 IETF RFC 2045: “Multipurpose Internet Mail
34、 Extensions (MIME) Part One: Format of Internet Message Bodies“. ETSI ETSI EN 319 532-3 V1.1.1 (2018-09) 7 13 IETF RFC 2046: “Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types“. 14 IETF RFC 5321: “Simple Mail Transfer Protocol“. 15 ETSI TS 119 612: “Electronic Signatures and Infrast
35、ructures (ESI); Trusted Lists“. 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 refer
36、enced 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 referenced documents are not necessary for the application of the present document but they assis
37、t the user with regard to a particular subject area. i.1 ETSI EN 319 532-4: “Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM) Services; Part 4: Interoperability profiles“. i.2 ETSI TS 119 312: “Electronic Signatures and Infrastructures (ESI); Cryptographic Suites“. i
38、.3 IETF RFC 6648: “Deprecating the “X-“ Prefix and Similar Constructs in Application Protocols“. i.4 ETSI EN 319 521: “Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Electronic Registered Delivery Service Providers“. i.5 Regulation (EU) No 910/2014 of the Europ
39、ean Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. i.6 ETSI EN 319 122-1: “Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building
40、 blocks and CAdES baseline signatures“. i.7 ETSI EN 319 142-1: “Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures“. i.8 ETSI EN 319 522-4-3: “Electronic Signatures and Infrastructures (ESI); Electronic Registered Delivery
41、 Services; Part 4: Bindings; Sub-part 3: Capability/requirements bindings“. i.9 IETF RFC 6931: “Additional XML Security Uniform Resource Identifiers (URIs)“. 3 Definitions, abbreviations and terminology 3.1 Definitions For the purposes of the present document, the terms and definitions given in ETSI
42、 EN 319 532-1 10 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ETSI EN 319 532-1 10 apply. ETSI ETSI EN 319 532-3 V1.1.1 (2018-09) 8 3.3 Terminology Since Registered Electronic Mail Services are specific types of Electronic Registered Delivery Services
43、, the present document uses the terms and definitions from ETSI EN 319 521 i.4 and ETSI EN 319 522 7, 8 and 9. ETSI EN 319 532-2 11, clause 4.1 specifies the usage of prefixes ERD versus REM or ERDS versus REMS for naming concepts and/or structures. The naming convention used in the present document
44、 is that constructs whose content is completely generated by the REMS are prefixed with “ERDS“ or “REMS“, while constructs whose content includes user generated data is prefixed with “ERD“ or “REM“. 4 Message formats 4.1 Introduction The present clause defines and explains how metadata and contents
45、are formatted in REM messages. Schemas and format definitions of ETSI EN 319 522-3 9 are reviewed in the REM perspective. Further implicit references are to ETSI EN 319 532-2 11, clause 4 describing the contents. To define the formats involved in communication exchanges in the REM (and so email) sco
46、pe, it is necessary to individuate and distinguish fundamental parts like user content and metadata components. As outlined in ETSI EN 319 522-2 8, clause 4, the user content is the content generated or provided by the sender, that is intended to be delivered to a recipient. Metadata related to the
47、user content, e.g. in the case of submission, relay or handover events, are provided for purposes of handling and processing a message, e.g. message identification, identification of sender/recipient(s), or also for service capabilities discovery. The next clauses describe how these meaningful conce
48、pts have been mapped first in email and later in REMSs provision context starting with a description example for a graphical individuation of the components, and following with the format specifications. 4.2 Internet Message Format in the REM services In the context of email and REM services provisi
49、on the concepts like user content and metadata have a correspondence with the elements of Mail Object as defined in IETF RFC 5321 14, clause 2.3.1 and with the definitions contained in ETSI EN 319 522-1 7, clause 3.1, ETSI EN 319 522-2 8, clause 4, and ETSI EN 319 532-2 11, clause 4. Table 1 illustrates the root of terms (if any), used in the next clauses, and the intended meaning in the REM context. Table 1: ERD to REM terms mapping Root definition (from ETSI EN 319 522-2 8) REM equiva
