35.040.01 - Information coding in general

The present document specifies requirements on the content of certificates issued to natural persons. This profile builds
on IETF RFC 5280 [1] for generic profiling of Recommendation ITU-T X.509 | ISO/IEC 9594-8 [i.3].
This profile supports the requirements of EU Qualified Certificates as specified in the Regulation (EU)
No 910/2014 [i.5] as well as other forms of certificate. The scope of the present document is primary limited to
facilitate interoperable processing and display of certifica...view more

The present document provides an overview of the Recommendation ITU-T X.509 | ISO/IEC 9594-8 [i.3] based certificate profiles and the statements for EU Qualified Certificates specified in other parts of ETSI EN 319 412 ([i.4] to [i.7]). It specifies common data structures that are referenced from other parts of ETSI EN 319 412 ([i.4] to [i.7]).
The profiles specified in this multi-part deliverable aim to support both the Regulation (EU) No 910/2014 [i.9] and use of certificates in a wider inter...view more

The present document specifies a certificate profile for certificates issued to legal persons. The profile defined in the
present document builds on requirements defined in ETSI EN 319 412-2 [2].
The present document supports the requirements of EU qualified certificates as specified in the Regulation (EU)
No 910/2014 [i.3] as well as other forms of certificate.

The present document contains requirements for the competence, consistent operation and impartiality of conformity
assessment bodies assessing and certifying the conformity of Trust Service Providers (TSPs) and the trust services they
provide towards defined criteria against which they claim conformance.
NOTE 1: Those requirements are independent of the type and class of trust service provided.
The present document also contains requirements for the conformity assessment of trust services co...view more

The present document defines specific QCStatement for the qcStatements extension as defined in IETF
RFC 3739 [2], clause 3.2.6, including requirements for their use in EU qualified certificates. Some of these
QCStatements can be used for other forms of certificate.
The QCStatements defined in the present document can be used in combination with any certificate profile, either
defined in ETSI EN 319 412-2 [i.2], ETSI EN 319 412-3 [i.5] and ETSI EN 319 412-4 [i.6], or defined elsewhere.
The Q...view more

This European Standard specifies a protection profile for trustworthy systems supporting time stamping.

This document specifies a protection profile for trustworthy systems supporting time stamping.

This document specifies conditions for use of an EN 419221-5 certified device in the case the signatory or seal creator has direct local control of the cryptographic module with the aim of being recognised as a qualified seal and/or signature creation device as defined in Regulation EU 910/2014 [1].
This document is aimed at use by entities other than trust service providers. Trust service providers can use EN 419221-5 directly without the need to take into account specific conditions as specif...view more

The present document specifies the formats for messages that are produced and handled by a Registered Electronic Mail
(REM) service according to the concepts 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, the present document:
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 are mapped ...view more

The scope of proposed 419 241 part 2 (PP TSCM) covers security requirements to reach compliance with Annex II of Regulation No 910/2014 of the remote (qualified TSP operated) parts of the system, other than those relating to Signature Activation Data (SAD) management and the operation of the Signature Activation Protocol (SAP), assuming use of a cryptographic module conforming to EN 419 221-5. EN 419 241 part 2 will be balloted simultaneously with EN 419241 Part 3 Protection profile for Signatur...view more

This document specifies conditions for use of an EN 419221-5 certified device in the case the signatory or seal creator has direct local control of the cryptographic module with the aim of being recognised as a qualified seal and/or signature creation device as defined in Regulation EU 910/2014 [1].
This document is aimed at use by entities other than trust service providers. Trust service providers can use EN 419221-5 directly without the need to take into account specific conditions as specif...view more

The present document specifies generally applicable policy and security requirements for Electronic Registered
Delivery Services Providers (ERDSP), including the services they provide.
The present document is applicable to:
• the policy and security requirements of the ERDSP and EU qualified ERDSP;
• the general and security requirements of Electronic Registered Delivery Services (ERDS) and EU qualified
ERDS in terms of message integrity; protection against loss, theft, damage or any unauth...view more

The present document defines the binding of the ERD messages, whose semantics is defined in ETSI EN 319 522-2 [1]
and whose format is defined in ETSI EN 319 522-3 [2], to the specific transmission protocol AS4 [4].

The present document specifies generally applicable policy and security requirements for Registered Electronic Mail
Service Provider (REMSP), including the services they provide.
The present document is applicable to:
• The policy and security requirements of REMS and EU qualified REMS providers.
• The general and security requirements of REMS and EU qualified REMS.
The present document does not specify interconnection requirements.
The present document aims to cover the common and worldwi...view more

The present document specifies the format for the semantic content (metadata, evidence, identification, and Common
Service Infrastructure) that flows across the different interfaces of an Electronic Registered Delivery Service (ERDS) as
defined in ETSI EN 319 522-2 [1].

The present document specifies the formats for messages that are produced and handled by a Registered Electronic Mail
(REM) service according to the concepts 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 are mapped in the REM service mes...view more

The present document defines the semantic content of messages and evidence used in registered electronic mail (REM)
service.
The present document relies on ETSI EN 319 522-2 [1] for all semantic contents and requirements which are generally
applicable to all electronic registered delivery services, and defines the interpretation and specific requirements which
apply only to registered electronic mail.

The present document defines the binding of the ERD messages, whose semantics is defined in ETSI EN 319 522-2 [1]
and whose format is defined in ETSI EN 319 522-3 [2], to the specific transmission protocol AS4 [4].

The present document specifies the logical model and basic concepts of registered electronic mail (REM) service.
The present document relies on ETSI EN 319 522-1 [1] for all concepts and requirements which are generally
applicable to all electronic registered delivery services, and defines the interpretation and specific requirements which
apply only to registered electronic mail.

The present document provides the binding of the Common Service Interface information, whose semantics is defined
in ETSI EN 319 522-2 [1] and whose format is defined in ETSI EN 319 522-3 [2] to the specific services provided by
OASIS Business Metadata Service Location [3] and the OASIS Service Metadata Publishing [4]. Furthermore, the
present document specifies how to establish trust between ERDSs by use of a Trusted List [5], including the EU Trusted
List system used for qualified trust se...view more