id stringlengths 7 13 | title stringlengths 26 396 | type stringclasses 2
values | version stringclasses 152
values | url stringlengths 90 98 | scope stringlengths 0 9.03k |
|---|---|---|---|---|---|
119 144-4 | Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 4: Testing Conformance of PAdES baseline signatures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11914404/01.01.01_60/ts_11914404v010101p.pdf | The present document defines the set of checks to be performed for testing conformance of PAdES signatures against PAdES baseline signatures as specified in ETSI EN 319 142-1 [1]. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by PAdES [1]. Regarding PAdES attributes, the present document explicitly differentiates between structural requirements that are defined on building blocks, and the requirements specified for PAdES baseline signatures conformance. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by PAdES [1]. |
119 144-5 | Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 5: Testing Conformance of additional PAdES signatures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11914405/01.01.01_60/ts_11914405v010101p.pdf | The present document defines the set of checks to be performed for testing conformance of PAdES signatures against additional PAdES signatures profiles as specified in ETSI EN 319 142-2 [3]. It defines only the checks that are specific to additional PAdES signatures. The set of checks that are common to both additional and baseline PAdES signatures, are defined in ETSI TS 119 144-4 [6]. The complete set of checks to be performed by any tool on additional PAdES signatures is the union of the sets defined within the present document and the set of common checks for testing conformance against ETSI EN 319 142-1 [1] and ETSI EN 319 142-2 [3] defined in ETSI TS 119 144-4 [6], as indicated in the normative clauses of the present document. The present document does not specify checks leading to conclude whether a signature is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in the signature may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a signature that has been successfully tested by any tool conformant to the present document. Checks specified by the present document are exclusively constrained to elements specified by PAdES [1]. Regarding PAdES attributes, the present document explicitly differentiates between structural requirements that are defined on building blocks, and the requirements specified for additional PAdES signatures conformance. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by PAdES [1]. |
118 516 | oneM2M; Study of Authorization Architecture for Supporting Heterogeneous Access Control Policies (oneM2M TR-0016 version 2.0.0) | TR | 2.0.0 | http://www.etsi.org/deliver/etsi_tr/118500_118599/118516/02.00.00_60/tr_118516v020000p.pdf | The present document provides technical solutions for oneM2M authorization architecture, authorization procedures and access control policies. The present document also gives evaluations of these proposed technical solutions. ETSI TS 118 103 [i.2] only defines a high level authorization architecture that describes its major components and general authorization procedure. The objective of the present document is to provide candidate security solutions related to authorization architecture, authorization procedures and access control policies. The present document provides security solutions in the following three aspects: • Detailed design of authorization architecture: This part investigates the interfaces among authorization components (e.g. procedures and parameters), how these components could be distributed in different oneM2M entities (i.e. different CSEs), and how to implement Role Based Access Control (RBAC) and token based access control. • Supporting user specified access control policies: This part investigates how the oneM2M authorization system could be an extensible system that can support user-defined access control mechanisms and/or access control policy languages. • Investigating existing access control policy languages: This part investigates if some standardized access control policy languages could become oneM2M recommended access control policy description languages. |
119 164-1 | Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Conformance and Interoperability; Part 1: Overview | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119100_119199/11916401/01.01.01_60/tr_11916401v010101p.pdf | The present document provides an overview of the set of test suites for testing interoperability and conformance of ASiC containers. The present document: a) provides a general description of the set of test suites for testing interoperability and conformance of ASiC containers; and b) lists the features of every test suite for testing interoperability and conformance of ASiC containers. The present document is for information only. Normative requirements of each test suite are in other parts of this multi-part deliverable. |
119 164-2 | Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Conformance and Interoperability; Part 2: Test suites for testing interoperability of ASiC baseline containers | TS | 2.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11916402/02.01.01_60/ts_11916402v020101p.pdf | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to ASiC baseline containers as specified in ETSI EN 319 162-1 [1]. The test suites are defined with four different layers reflecting the four different levels of ASiC baseline containers. • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. • Test suites also cover augmentation of ASiC baseline containers and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists. |
119 164-3 | Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Compliance and Interoperability; Part 3: Test suites for testing interoperability of ASiC containers other than baseline | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11916403/01.01.01_60/ts_11916403v010101p.pdf | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to ASiC building blocks defined in ETSI EN 319 162-1 [1] and additional containers defined in ETSI EN 319 162-2 [2]. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists. |
119 164-4 | Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Compliance and Interoperability; Part 4: Testing Conformance of ASiC baseline containers | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11916404/01.01.01_60/ts_11916404v010101p.pdf | The present document defines the set of checks to be performed for testing conformance of ASiC containers against ASiC baseline containers as specified in ETSI EN 319 162-1 [1]. The present document does not specify checks leading to conclude whether a container is technically valid or not (for instance, it does not specify checks for determining whether the cryptographic material present in signatures inside the container may be considered valid or not). In consequence, no conclusion may be inferred regarding the technical validity of a container that has been successfully tested by any tool conformant to the present document. Checks are exclusively constrained to elements specified by ASiC [1]. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set specified in the present document includes tests on the correctness of the structure of all the elements specified by ASiC [1]. |
119 164-5 | Electronic Signatures and Infrastructures (ESI); Associated Signature Containers (ASiC) - Testing Compliance and Interoperability; Part 5: Testing Conformance of additional ASiC containers | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11916405/01.01.01_60/ts_11916405v010101p.pdf | The present document defines the sets of checks required for testing conformance of ASiC containers against: • ASiC containers conforming to building blocks defined in ETSI EN 319 162-1 [1] and containing extended CAdES [i.5] and extended XAdES [i.6] digital dignatures, expanding the scope of ASiC baseline containers also defined in ETSI EN 319 162-1 [1]; and • additional containers defined in ETSI EN 319 162-2 [2]. The set of checks that are common with ASiC baseline containers, are defined in ETSI TS 119 164-4 [5] and referenced when needed. |
119 172-1 | Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 1: Building blocks and table of contents for human readable signature policy documents | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11917201/01.01.01_60/ts_11917201v010101p.pdf | The present document defines the building blocks of signature policy and specifies a table of contents for human readable signature policy documents. |
119 172-2 | Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 2: XML format for signature policies | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11917202/01.01.01_60/ts_11917202v010101p.pdf | The present document defines an XML format of machine readable signature policies based on the building blocks that define technical constraints on digital signatures and are specified in ETSI TS 119 172-1 [i.2]. Pure signature applicability rules, directly related to procedural constraints imposed by business processes, are out of the scope of the present document which does not define XML elements for the building blocks specified in ETSI TS 119 172-1 [i.2] that define only applicability rules. For each element of the machine readable signature policy, the present document specifies the semantics and the how to implement it in XML syntax. The present document defines elements which can be used to describe technical constraints on signature creation, signature validation, and signature augmentation. These elements are designed in a way that it is possible to generate XML documents that include components of a signature generation policy, or/and signature validation policy, and/or signature augmentation policy. An XML document conformant to the present specification, defines constraints (on generation, augmentation, validation, any combination of two of them, or the three of them) that one signature has to meet. NOTE : Complex business processes, where several digital signatures need to be managed, having to meet different set of technical constraints, will require several XML documents conformant to the present document, each one defining one of these sets of technical constraints. It is out of the scope to specify mechanisms for protecting the integrity of the machine-readable signature policy documents specified in the present document. |
119 172-3 | Electronic Signatures and Infrastructures (ESI); Signature Policies; Part 3: ASN.1 format for signature policies | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11917203/01.01.01_60/ts_11917203v010101p.pdf | The present document defines an ASN.1 format of machine readable signature policies based on the building blocks that define technical constraints on digital signatures and are specified in ETSI TS 119 172-1 [i.2]. Pure signature applicability rules, directly related to procedural constraints imposed by business processes, are out of the scope of the present document which does not define ASN.1 elements for the building blocks specified in ETSI TS 119 172-1 [i.2] defining only applicability rules. For each element of the machine readable signature policy, the present document references to the semantics described in ETSI TS 119 172-2 [3] and defines the corresponding ASN.1 syntax. The present document defines elements which can be used to describe technical constraints on signature creation, signature validation, and signature augmentation. These elements are designed in a way that it is possible to generate ASN.1 documents that include components of a signature generation policy, or/and signature validation policy, and/or signature augmentation policy. An ASN.1 document conformant to the present specification, defines constraints (on generation, augmentation, validation, any combination of two of them, or the three of them) that one signature has to meet. NOTE: Complex business processes, where several digital signatures need to be managed, having to meet different set of technical constraints, will require several ASN.1 documents conformant to the present document, each one defining one of these sets of technical constraints. It is out of the scope to specify mechanisms for protecting the integrity of the machine-readable signature policy documents specified in the present document. |
119 172-4 | Electronic Signatures and Trust Infrastructures (ESI); Signature Policies; Part 4: Signature applicability rules (validation policy) for European qualified electronic signatures/seals using trusted lists | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11917204/01.02.01_60/ts_11917204v010201p.pdf | The present document specifies a set of rules that aims at defining the technical requirements for determining, taking into account the EU Member States trusted lists [i.4], whether a digital signature is fit for meeting the requirements of EU qualified electronic signatures/seals in the sense of the applicable European legislation, i.e. either Directive 1999/93/EC [i.2] or Regulation (EU) No 910/2014 [i.1]. |
119 182-1 | Electronic Signatures and Trust Infrastructures (ESI); JAdES digital signatures; Part 1: Building blocks and JAdES baseline signatures | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11918201/01.02.01_60/ts_11918201v010201p.pdf | The present document: 1) Specifies a JSON [1] format for AdES signatures (JAdES signatures hereinafter) built on JSON Web Signatures (JWS hereinafter) as specified in IETF RFC 7515 [2]. For this, the present document: - Extends the JSON Web Signatures specified in IETF RFC 7515 [2] by defining an additional set of JSON header parameters that can be incorporated in the JOSE Header (either in its JWS Protected Header or its JWS Unprotected Header parts). Many of these new header parameters have the same semantics as the attributes/properties defined in CAdES [i.2] and XAdES [4] digital signatures. Other header parameters are defined to meet specific requirements that current JSON Web Signatures cannot meet (e.g. for explicitly referencing detached JWS Payload). These new header parameters and their corresponding types are defined in a JSON schema. - Specifies the mechanisms for incorporating the aforementioned JSON components in JSON Web Signatures [2] to build JAdES signatures, offering the same features as CAdES and XAdES in JSON syntax, and therefore fulfilling the same requirements (such as the long-term validity of digital signatures). 2) Defines four levels of JAdES baseline signatures addressing incremental requirements to maintain the validity of the signatures over the long term. Each level requires the presence of certain JAdES header parameters, suitably profiled for reducing the optionality as much as possible. The aforementioned levels provide the basic features necessary for a wide range of business and governmental use cases for electronic procedures and communications to be applicable to a wide range of communities when there is a clear need for interoperability of digital signatures used in electronic documents. EXAMPLE: An example of requirements raised in specific domains is signing HTTP messages exchanged by parties in certain environments, which require signing both the HTTP body and some specific http headers. The format specified in IETF RFC 7515 [2] does not provide any native mechanism for individually identifying a detached JWS Payload. Clause 5.2.8 of the present document defines sigD, a new JSON header parameter that allows to identify one or more detached data objects which, suitably processed and concatenated, form the detached JWS Payload. Procedures for creation, augmentation, and validation of JAdES digital signatures are out of scope. NOTE 1: ETSI EN 319 102-1 [i.3] specifies procedures for creation, augmentation and validation of other types of AdES digital signatures. The present multi-part deliverable aims at supporting electronic signatures independent of any specific regulatory framework. NOTE 2: Specifically, but not exclusively, it is the aim that JAdES digital signatures specified in the present multi-part deliverable can be used to meet the requirements of electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as defined in Regulation (EU) No 910/2014 [i.1]. |
119 192 | Electronic Signatures and Infrastructures (ESI); AdES related Uniform Resource Identifier | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/119192/01.02.01_60/ts_119192v010201p.pdf | The present document describes the root Uniform Resource Identifier (URI) http://uri.etsi.org/ades and sub branches that allow to define URI applicable for more than one AdES signature format and/or the ASiC signature container. The present document describes how to define URIs to reference a specific version and/specific attribute/property of an AdES format. NOTE: The present document defines URIs which are not used as pointers to a specific location but are used as unique identifiers. |
119 300 | Electronic Signatures and Infrastructures (ESI); Guidance on the use of standards for cryptographic suites | TR | 1.2.1 | http://www.etsi.org/deliver/etsi_tr/119300_119399/119300/01.02.01_60/tr_119300v010201p.pdf | The present document provides business driven guidance on the use of standards for cryptographic suites, and in particular for digital signature creation algorithms. The present document explains the concept of security parameters that helps to choose a proper cryptographic suite for digital signature creation. It also gives an overview how to analyze the business needs and how to select a system that satisfies these needs. The purported audience of the present document is mainly the application designers and implementers. The present document provides recommendations to trust service providers and manufacturers of security devices. |
119 312 | Electronic Signatures and Trust Infrastructures (ESI); Cryptographic Suites | TS | 1.5.1 | http://www.etsi.org/deliver/etsi_ts/119300_119399/119312/01.05.01_60/ts_119312v010501p.pdf | The present document lists cryptographic suites used for the creation and validation of digital signatures and electronic timestamps and related certificates. The present document builds on the agreed cryptographic mechanisms from SOG-IS [14]. It may be used also for electronic registered delivery services in the future. In contrast to previous versions of the present document, specific end dates are provided. The present document works on the assumption that the validity period (i.e. between notBefore and notAfter) of (qualified) end-entity certificates issued by trust services providers is typically three years. The present document focuses on interoperability issues and does not duplicate security considerations given by other standardization bodies, security agencies or supervisory authorities of the Member States. It instead provides guidance on the selection of concrete cryptographic suites that use agreed mechanisms. The use of SOG-IS agreed mechanisms is meant to help ensure a high level of security in the recommended cryptographic suites, while the focus on specific suites of mechanisms is meant to increase interoperability and simplify design choices. There is no normative requirement on selection among the alternatives for cryptographic suites given here but for all of them normative requirements apply to ensure security and interoperability. The present document also provides guidance on hash functions, (digital) signature schemes and (digital) signature suites to be used with the data structures used in the context of digital signatures and seals. For each data structure, the set of algorithms to be used is specified. |
119 322 | Electronic Signatures and Trust Infrastructure (ESI); Schema for machine-readable cryptographic algorithms, and cipher suites catalogues | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119300_119399/119322/01.02.01_60/ts_119322v010201p.pdf | The present document provides a generic schema for machine-readable cryptographic algorithms, and cipher suites catalogues based on IETF RFC 5698 [1] and specifies different formats such as XML [i.4] and JSON [i.5]. The present document is limited to a descriptive schema for algorithms and all parameters involved. No assessment of the suitability of any cryptographic algorithm, or cipher suite is given in the present document. The present document focuses on signature-related algorithms, and cipher suites, and puts an emphasis on enabling a refined suitability description of the algorithms with respect to its status of recommendation as well as the specific context of usage an algorithm is assessed for. |
119 400 | Electronic Signatures and Infrastructures (ESI); Guidance on the use of standards for trust service providers supporting digital signatures and related services | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119400_119499/119400/01.01.01_60/tr_119400v010101p.pdf | The present document provides guidance on the selection of standards and options for the trust service provider supporting digital signatures and related services (area 4) as identified in ETSI TR 119 000 [i.2]. The present document describes the business scoping parameters relevant to this area (see clause 5) and how the relevant standards and options for this area can be identified given the business scoping parameters (see clause 6). The target audience of the present document includes: 1) Business managers who potentially require support from digital signatures and in particular the provision of related supporting trust services in their business will find here an explanation of how digital signatures standards can be used to meet their business needs. 2) Application architects who will find here material that will guide them throughout the process of designing a system that fully and properly satisfies all the business and legal/regulatory requirements specific to digital signatures and in particular the provision of related supporting trust services. They will gain a better understanding on how to select the appropriate standards to be implemented and/or used. 3) Developers of the systems who will find in the present document an understanding of the main reasons that lead the systems to be designed as they were, as well as a proper knowledge of the standards that exist in the field and that they need to know in detail for a proper development. |
119 403-2 | Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment; Part 2: Additional requirements for Conformity Assessment Bodies auditing Trust Service Providers that issue Publicly-Trusted Certificates | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/11940302/01.03.01_60/ts_11940302v010301p.pdf | The present document defines specific supplementary requirements to those defined in ETSI EN 319 403-1 [1] for CABs performing audits based on ETSI EN 319 411-1 [i.9] and those from CA/Browser Forum, [i.7] and [i.8]. In particular, the present document defines the requirements for audit attestations, including their content. |
119 403-3 | Electronic Signatures and Infrastructures (ESI); Trust Service Provider Conformity Assessment; Part 3: Additional requirements for conformity assessment bodies assessing EU qualified trust service providers | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/11940303/01.01.01_60/ts_11940303v010101p.pdf | The present document defines specific supplementary requirements for the application of ETSI EN 319 403 [1] aimed at conformity assessments (audits) of qualified trust service providers (QTSPs) and the qualified trust services (QTSs) they provide, as well as of trust service providers, without qualified status, intending to start providing qualified trust services, against the requirements of Regulation (EU) No 910/2014 [i.1] assuming the use of ETSI policy requirement standards but not precluding use of other specifications. In particular, the present document defines requirements for conformity assessment reports, including their content. |
119 404 | Electronic Signatures and Infrastructures (ESI); NIS2 and its impact on eIDAS standards | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119400_119499/119404/01.01.01_60/tr_119404v010101p.pdf | The present document: • outlines the main requirements of NIS2; • analyses the requirements of NIS2 Directive against the existing cybersecurity provisions of ETSI EN 319 401 [i.7] in order to identify areas where additional provisions are needed; • takes into account the use of ISO 27002 general information security controls for cyber security used in support of ETSI EN 319 401 [i.7] including revisions to align with the major reorganisation to ISO 27002 from the 27002:2013 [i.5] to the 27002:2022 [i.6]; • establishes a methodology for aligning other ETSI standards with the NIS2 Directive. |
119 411-4 | Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 4: Checklist supporting audit of TSP against ETSI EN 319 411-1 or ETSI EN 319 411-2 | TR | 1.3.1 | http://www.etsi.org/deliver/etsi_tr/119400_119499/11941104/01.03.01_60/tr_11941104v010301p.pdf | The present document is a checklist of the policy requirements specific to TSP issuing certificates (as expressed in ETSI EN 319 411-1 [i.2] and ETSI EN 319 411-2 [i.3]) including the generic requirements which are independent of the type of service (as expressed in ETSI EN 319 401 [i.1]). The checklist identifies each requirement associated with each certificate policy, as specified in ETSI EN 319 411-1 [i.2] and ETSI EN 319 411-2 [i.3], and also relates where relevant the requirement to a particular TSP component service. Additional fields are provided to allow TSPs to indicate claimed compliance to a particular requirement and for assessors to indicate the results of an assessment for each requirement. This checklist can be used by the TSP itself to prepare for an assessment of its practices against the referenced documents (i.e. serve as a basis for a self-declaration) and/or by the assessor when conducting the assessment. The present document does not specify how the requirements identified can be assessed by an independent party, including requirements for information to be made available to such independent assessors, or requirements on such assessors. NOTE: See ETSI EN 319 403-1 [i.7] for guidance on assessment of TSP's processes and services. |
119 411-5 | Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 5: Implementation of qualified certificates for website authentication as in amended regulation 910/2014 | TS | 2.1.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/11941105/02.01.01_60/ts_11941105v020101p.pdf | The present document defines two approaches for issuing qualified certificates for website authentication, deploying them to websites, and their consumption by web browsers. Objectives of Approach #1 (i.e. "1-QWAC Approach") 1-QWACs: a) Support coexistence of trust controls based upon meeting requirements from both the Web Browser Vendor within the meaning of Recital 65 of the Regulation (EU) 2024/1183 [i.3] and EU Trusted Lists with ETSI standards aimed at supporting EU trust controls. b) Include requirements for TLS certificates based on CA/Browser Forum Requirements [i.4] and [i.5] as applied in ETSI standards [4]. c) Authenticate the website directly by using the QWAC to establish a TLS connection between the web browser and the server. NOTE: TLS uses encryption to secure data transmitted over a network providing confidentiality, integrity, and authentication. Objectives of Approach #2 (i.e. "2-QWAC with Certificate Binding Validation Approach") 2-QWACs with Certificate Binding Validation: - Support trust controls based upon EU Trusted Lists with ETSI standards aimed at supporting EU trust controls for a QWAC, which is used to bind the identity in the QWAC to the TLS certificate(s) to be used by the web browser to establish a TLS connection between the web browser and the server. - Support trust controls based upon Web Browser Vendor Root Stores for the TLS certificate which is used to establish a TLS connection between the web browser and the server. All approaches: • aim to meet the requirements of Article 45, Article 45a, and Recital 65 of Regulation (EU) 2024/1183 [i.3]; • include requirements of qualified certificates for website authentication as specified in Regulation (EU) 2024/1183 [i.3]; and • enable the display of identity data contained in qualified certificates for website authentication and validated by the EU trust schemes in a user-friendly manner. Clause 4 specifies Trust Service Provider requirements for issuing QWACs. Clause 5 provides website operator guidance for using QWACs. Clause 6 specifies web browser requirements for consuming QWACs. |
119 411-6 | Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 6: Requirements for Trust Service Providers issuing publicly trusted S/MIME certificates | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/11941106/01.01.01_60/ts_11941106v010101p.pdf | The present document specifies policy and security requirements for the issuance, maintenance and life-cycle management of S/MIME certificates as defined in the S/MIME Baseline Requirements (SBR) [1] in the context of the ETSI Electronic Signatures and Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates series. An S/MIME certificate for the purposes of the present document can be identified by the existence of an Extended Key Usage (EKU) for id-kp-emailProtection (OID: 1.3.6.1.5.5.7.3.4) and the inclusion of an email address (in the form of an rfc822Name or an otherName of type id-on-SmtpUTF8Mailbox) in the subjectAltName extension. These policy and security requirements support reference certificate policies for the issuance, maintenance and life- cycle management of S/MIME certificates issued to mailboxes (containing only an email address), natural persons (including natural persons associated with a legal person) and to legal persons, respectively. The present document does not specify how the requirements identified can be assessed by an independent party, including requirements for information to be made available to such independent assessors, or requirements on such assessors. NOTE 1: See ETSI EN 319 403-1 [i.1] for guidance on assessment of TSP's processes and services, expanded as relevant by ETSI TS 119 403-2 [i.2] for additional requirements for publicly-trusted certificates, and by ETSI TS 119 403-3 [i.3] for additional requirements for EU qualified TSPs. NOTE 2: The present document integrates all the policy requirements of the CA/Browser Forum S/MIME Baseline Requirements (SBR) [1] with ETSI EN 319 411-1 [2] for the [LCP], [NCP], and/or [NCP+] certificate policies, and with ETSI EN 319 411-2 [3] for the [QCP-l], [QCP-n], [QCP-l-qscd], and/or [QCP-n-qscd] certificate policies. |
119 411-8 | Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Trust Service Providers issuing certificates; Part 8: Access Certificate Policy for EUDI Wallet Relying Parties | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/11941108/01.01.01_60/ts_11941108v010101p.pdf | The present document specifies requirements for qualified and non-qualified certificates for electronic seals/signatures for wallet-relying party access certificates to be used by wallet-relying parties aiming to meet the needs of eIDAS2 [i.2] and implementing acts, especially CIR (EU) 2025/848 [i.6] on the access certificates for wallet-relying parties. The present document imposes no requirements on the functioning of Competent Authorities registering and overseeing the operation of wallet-relying parties. |
119 412-6 | Electronic Signatures and Trust Infrastructures (ESI); Certificate Profiles; Part 6: Certificate profile requirements for PID, Wallet, EAA, QEAA, and PSBEAA providers | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/11941206/01.01.01_60/ts_11941206v010101p.pdf | The present document specifies requirements on the content end entity certificates used by Person Identification Data (PID) providers, Public Sector Body's Electronic Attestation of Attributes (PSBEAA) providers, Electronic Attestation of Attributes (EAA) providers, Qualified Electronic Attestation of Attributes (QEAA) providers and Wallet providers. This profile is based on ETSI EN 319 412-2 [5] and ETSI EN 319 412-3 [6] which in turn build on IETF RFC 5280 [1] for generic profiling of Recommendation ITU-T X.509 | ISO/IEC 9594-8 [i.3] and also uses IETF RFC 5755 [i.8] for attribute issuer certificate profiles. This profile aims at supporting the requirements of the Regulation (EU) No 910/2014 [i.5] as amended by Regulation (EU) No 2024/1183 [i.7]. The scope of the present document is primary limited to facilitate interoperable processing and display of certificate information. This profile therefore excludes support for some certificate information content options, which can be perfectly valid in a local context but which are not regarded as relevant or suitable for use in widely deployed applications. The present document focuses on requirements on certificate content. Requirements on decoding and processing rules are limited to aspects required to process certificate content defined in the present document. Further processing requirements are only specified for cases where it adds information that is necessary for the sake of interoperability. Certain applications or protocols impose specific requirements on certificate content. The present document is based on the assumption that these requirements are adequately defined by the respective application or protocol. It is therefore outside the scope of the present document to specify such application or protocol specific certificate content. The present document aims to meet the requirements of the Regulation (EU) No 910/2014 [i.5] as amended by Regulation (EU) No 2024/1183 [i.7], and architectural reference framework as available at time of preparation of the present document: • Regulation (EU) No 2024/1183 [i.7] Article 45f 1 b) requirements on qualified certificate of PSBEAA • Regulation (EU) No 2024/1183 [i.7] Annex V g) requirements on use of qualified electronic signature seal of QEAA • Regulation (EU) No 2024/1183 [i.7] Annex VII g) requirements on use of qualified electronic signature seal of PSBEAA |
119 431-1 | Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for trust service providers; Part 1: TSP services operating a remote QSCD / SCDev | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/11943101/01.03.01_60/ts_11943101v010301p.pdf | The present document specifies generally applicable policy and security requirements for Trust Service Providers (TSPs) operating a remote Signature Creation Device (SCDev). Specific requirements apply when the device is a remote QSCD as defined in Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. The service consists of a server signing application and a QSCD / SCDev. The term used in the present document is Server Signing Application Service (SSAS). NOTE 1: Regulation (EU) 2024/1183 [i.11] (eIDASv2) defines the management of remote electronic signature/seal creation devices as a trust service. In addition, it introduces the qualified trust service for the management of remote qualified electronic signature/seal creation devices. The policy and security requirements are defined in terms of requirements for creation, maintenance, life-cycle management and use of signing keys used to create digital signatures. The present document is aimed to be used by independent bodies as the basis for a conformity assessment that a TSP can be trusted for operating a remote QSCD / SCDev. [i.1]. The present document supports European and other regulatory frameworks. NOTE 2: Specifically, but not exclusively, the present document is aimed at qualified and non-qualified trust service managing remote qualified and non-qualified electronic signature/seal creation devices supporting electronic signatures and electronic seals (both advanced and qualified) in accordance with the requirements of Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. Annex A contains requirements specific for an SSAS in the context of Regulation (EU) 2024/1183 [i.11] amending Regulation (EU) No 910/2014 [i.1]. The present document does neither specify how fulfilment of the requirements can be assessed by an independent conformity assessment body, nor requirements for information to be made available to such independent assessors, or requirements on such assessors. NOTE 3: See ETSI EN 319 403 [i.3] for guidance on assessment of a TSP's processes and services. NOTE 4: The present document references ETSI EN 319 401 [1] for general policy requirements common to all TSP services covered by ETSI standards. The present document does not specify protocols used to access the SSAS. NOTE 5: Protocols for remote digital signature creation are defined in ETSI TS 119 432 [i.4]. The present document identifies specific controls needed to address risks associated with services operating remote QSCD / SCDev. |
119 431-2 | Electronic Signatures and Infrastructures (ESI); Policy and security requirements for trust service providers; Part 2: TSP service components supporting AdES digital signature creation | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/11943102/01.02.01_60/ts_11943102v010201p.pdf | The present document provides policy and security requirements for Trust Service Providers (TSPs) implementing a service component supporting AdES digital signature creation. This component contains a signature creation application and is thus called Signature Creation Application Service Component (SCASC). However, it is more than just the SCA. It contains service elements around which parts of the driving application as defined in ETSI TS 119 102-1 [2] and ETSI TS 119 101 [1] can be implemented. The present document does not give restrictions on whether something is covered within a signature creation application or outside, as long as it is done by the SCASC. The present document gives no restrictions on the type of TSP implementing such a service component. The present document aims at supporting the creation of digital signatures in European and other regulatory frameworks. NOTE 1: Specifically, but not exclusively, the present document is aimed at trust services, supporting the creation of digital signatures in accordance with the requirements of the Regulation (EU) No 910/2014 [i.1] for electronic signatures and electronic seals (both advanced and qualified). Annex B contains specific requirements for SCASC in the context of Regulation (EU) No 910/2014 which aim at providing best practice requirements for the creation of advanced electronic signatures and seals based on X.509 certificates. NOTE 2: Specifically, but not exclusively, digital signatures in the present document can be used to create electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.1]. The present document may be used by competent bodies as the basis for confirming that an organization is trustworthy in creating AdES digital signatures. NOTE 3: See ETSI EN 319 403 [i.6] for guidance on assessment of TSP processes and services. The SCASC has connections with external (trust) services that can be contacted for example for provisioning information to be included within the signature. The present document does not put requirements on the trust service policy applied by such external services. The present document does not specify any protocol used to access the SCASC or how the SCACS can contact an SSASC or an SCDev. NOTE 4: Protocols to contact a SCASC or a SSASC are defined in ETSI TS 119 432 [i.9]. The present document identifies specific controls needed to address specific risks associated with services providing AdES signature creation. |
119 432 | Electronic Signatures and Infrastructures (ESI); Protocols for remote digital signature creation | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf | The present document specifies protocols and interfaces applicable when the process of creating AdES digital signatures as defined by ETSI TS 119 102-1 [i.7] and/or digital signature values, as result of Data To Be Signed Representations signatures, is carried out by a distributed solution comprised of two or more systems/services/components. The present document is limited to remote server signing, i.e. the signing key is held in a remote shared service. NOTE: Remote signature creation with local signing, i.e. the signing key is held with the signer's personal device but other steps in the signature creation are carried out by means of networked services, is a possible solution but protocols for such architecture are not covered in the present document. Finally, the present document specifies two bindings, each one in a different syntax (XML and JSON), for each of the protocols mentioned above. As far as it has been possible and suitable, the protocols have re-used constructs of CSC JSON and OASIS DSS-X XML specifications. When this has not been possible the present document specifies new components semantically and also syntactically in the two formats: XML and JSON. The authorized signer's use of its key for signing requires users to provide multiple proofs of their claimed identity before being granted access to the needed set of resources. The way in which the user identity verification process is carried out by the service provider or any suggestion concerning the usage of multi-factor authentication mechanisms is out of the scope of the present document. |
119 441 | Electronic Signatures and Trust Infrastructures (ESI); Policy requirements for TSP providing signature validation services | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/119441/01.03.01_60/ts_119441v010301p.pdf | The present document, based on the general policy requirements specified in ETSI EN 319 401 [2], specifies policy and security requirements for signature validation services operated by a TSP. NOTE 1: Beside signature validation, other signature services, like signature creation, signature augmentation or signature preservation can also be offered by TSPs. Such services can be provided as stand-alone services or combined (e.g. augmentation can be used to support a preservation service). The present document does not provide requirements on signature services beyond validation and does not provide requirements on how to combine signature related services. NOTE 2: A distinct Technical Specification (TS) provides policy and security requirements for TSP offering signature augmentation services as a stand-alone service or in complement to one of the above-mentioned services. The present document is aimed at trust services supporting the validation of digital signatures in accordance with ETSI EN 319 102-1 [3]. It takes into account the relevant requirements for signature validation application specified in ETSI TS 119 101 [1] as they relate to TSPs. It is aimed at supporting the validation of digital signatures in European and other regulatory frameworks. NOTE 3: Specifically, but not exclusively, the present document is aimed at qualified and non-qualified trust services, supporting the validation of digital signatures in accordance with the requirements of the Regulation (EU) No 910/2014 [i.1] for validation of electronic signatures and electronic seals (both advanced and qualified). Annex B complements the requirements for signature validation service providers offering a Qualified Validation Service for qualified electronic signatures or for qualified electronic seals as specified by Regulation (EU) No 910/2014 [i.1]. NOTE 4: Specifically, but not exclusively, digital signatures in the present document cover electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.1]. The present document may be used by competent bodies as the basis for confirming that an organization is trustworthy in validating digital signatures on behalf of other persons or on its own behalf. NOTE 5: See ETSI EN 319 403 [i.13] for guidance on assessment of TSP processes and services. The user's interface is outside the scope of the main TSP service. However, the present document provides in annex D recommendations for the user's interfaces (for inputting the request and to visualize the validation report). The TSP has connections with external (trust) services that can be contacted for provisioning validation information, or to relay the validation request. The present document does not put requirements on the trust service policies applied by such external services. The present document identifies specific controls needed to address specific risks associated with validation services. |
119 442 | Electronic Signatures and Infrastructures (ESI); Protocol profiles for trust service providers providing AdES digital signature validation services | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/119442/01.01.01_60/ts_119442v010101p.pdf | The present document specifies the semantics of a protocol for requesting to a remote server (and for receiving the corresponding response) the validation of AdES digital signatures compliant with the following ETSI deliverables: ETSI EN 319 122 [2], ETSI EN 319 132 [3], ETSI EN 319 142 [4], ETSI TS 101 733 [5], ETSI TS 102 778 [9], ETSI TS 101 903 [7], ETSI TS 103 171 [8], ETSI TS 103 172 [10] and ETSI TS 103 173 [6]. The present document specifies the semantics of a second protocol for requesting the augmentation of AdES digital signatures compliant with the aforementioned ETSI deliverables. The present document also specifies the semantics of a third protocol for requesting the validation and augmentation of AdES digital signatures compliant with the aforementioned ETSI deliverables. Finally, the present document specifies two bindings, each one in a different syntax (XML and JSON), for each of the aforementioned protocols. As far as it has been possible and suitable, the protocols have re-used constructs of DSS-X core v2.0: "Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0" [1] (also identified as DSS-X core v2.0 hereinafter). The protocols define new features which are not supported by DSS-X core v2.0. NOTE 1: The protocols specified in the present document do not include components for submitting to the server ASiC containers compliant with ETSI EN 319 162-1 [i.1], ETSI EN 319 162-2 [i.2], ETSI TS 102 918 [i.3], and ETSI TS 103 174 [i.4]. They do not include either components for reporting on the validation of signatures included within an ASiC container. However, clients can always extract individual signatures and groups of signed documents from ASiC containers and prepare and submit suitable requests to the server for these individual signatures and groups of signed documents. NOTE 2: The protocols specified in the present document do not include components for submitting to the server time-stamp tokens for their verification. They do not include either components for reporting on the verification of time-stamp tokens. Protocols specified by OASIS DSS-X Technical Committees include this type of components. NOTE 3: The present document builds on a draft OASIS Committee Specification as the final OASIS specification was not available at the time of publication of the present document. The present deliverable will then be updated when the OASIS Committee Specification is formally adopted. |
119 460 | Electronic Signatures and Infrastructures (ESI); Survey of technologies and regulatory requirements for identity proofing for trust service subjects | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119400_119499/119460/01.01.01_60/tr_119460v010101p.pdf | The present document provides the results of a survey on the technologies, legislations, specifications, guidelines and standards related to or used for identity proofing. Information has been collected as comprehensively as possible, and is analysed in the present document. The aim is to identify trends and select relevant elements for ETSI DTS/ESI-0019461 [i.50] to address both security policy and security requirements for enrolment of Trust Services subjects. The methodology to achieve this goal is presented in clause 4 and is followed by the analysis. |
119 461 | Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for trust service components providing identity proofing of trust service subjects | TS | 2.1.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/119461/02.01.01_60/ts_119461v020101p.pdf | The present document specifies policy and security requirements for trust service components providing identity proofing of trust service subjects. Such a trust service component can be provided by the Trust Service Provider (TSP) itself as an integral part of the trust service or by a specialized Identity Proofing Service Provider (IPSP) acting as a subcontractor to the TSP. The term "trust service component" is used because identity proofing is not considered as a trust service on its own but as a component of the trust service for which the identity proofing is done. The present document provides requirements for two Levels of Identity Proofing (LoIP), Baseline and Extended. These LoIPs aim to support identity proofing for ETSI trust services standards such as ETSI EN 319 411-1 [i.7], ETSI EN 319 411-2 [i.8] and ETSI EN 319 521 [i.12]. The present document also provides requirements to enhance an identity proofing from Baseline LoIP to Extended LoIP when the Baseline LoIP has been reached by use of electronic Identification means (eID) at Level of Assurance (LoA) 'substantial' according to the amended eIDAS regulation [i.25] or a similar LoA based on a comparable assurance level framework. The present document aims at supporting identity proofing in European and other regulatory frameworks. Specifically, but not exclusively, the Baseline LoIP aims to support identity proofing for qualified certificates as defined in Regulation (EU) No 910/2014 [i.1] (the original eIDAS regulation) Article 24.1, while the Extended LoIP aims to support identity proofing for qualified certificates and qualified attestations of attributes as defined in Articles 24.1, 24.1a, and 24.1b of the amended eIDAS regulation [i.25]. The present document aims to meet the requirements of the original eIDAS regulation [i.1] by the requirements in clause C.2 and the requirements of the amended eIDAS regulation [i.25] by the requirements in clause C.3. The present document is intended to be applicable for reference from an implementing act according to Article 24.1c of the amended eIDAS regulation [i.25], setting out minimum technical specifications, standards and procedures with respect to the verification of identity and attributes in accordance with Articles 24.1, 24.1a, and 24.1b of the amended eIDAS regulation [i.25]. The present document aims to meet the requirements of Article 44 of the aforementioned regulations on identity proofing for qualified electronic registered delivery services by the requirements in clause C.4. eIDAS has no specific requirements for identity proofing for other qualified trust services. The present document can be used by Conformity Assessment Bodies (CAB) as the basis for confirming that an organization is trustworthy and reliable in its identity proofing process. NOTE 1: See ETSI EN 319 403-1 [i.6] for guidance on the assessment of TSP processes and services. NOTE 2: The present document has the potential to have wider applicability than the defined scope, but any application for other purposes than trust services is out of scope. |
119 471 | Electronic Signatures and Trust Infrastructures (ESI); Policy and Security requirements for Providers of Electronic Attestation of Attributes Services | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/119471/01.01.01_60/ts_119471v010101p.pdf | The present document specifies policy and security requirements for electronic attestation of attributes trust service providers and the attestation of attributes services they provide. More specifically the present document specifies policy and security requirements on attributes issuance and validation of EAA by the trust service provider. |
119 472-1 | Electronic Signatures and Trust Infrastructures (ESI); Profiles for Electronic Attestation of Attributes; Part 1: General requirements | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/11947201/01.02.01_60/ts_11947201v010201p.pdf | The present document: 1) Specifies a data model (semantics) for Electronic Attestations of Attributes, a new object defined by the Regulation (EU) 2024/1183 [i.2] clause 4. 2) Defines data model (semantics) requirements for two types of Electronic Attestations of Attributes, namely: the Qualified Attestations of Attributes, and the Electronic Attestations of Attributes issued by or on behalf of a public body responsible for an authentic source, also defined in Regulation (EU) 2024/1183 [i.2] clause 4. 3) Defines 4 realizations for the former data model. These realizations include, wherever needed, specific requirements for the Qualified Attestations of Attributes, and the Electronic Attestations of Attributes issued by or on behalf of a public body responsible for an authentic source, defined in Regulation (EU) 2024/1183 [i.2], particularized for the different realizations. Below follows the list of realizations: a) SD-JWT VC. Realization based on SD-JWT VC (clause 5). SD-JWT VC is specified in IETF SD-JWT [5]. b) ISO/IEC-mdoc. Realization based on the structures defined in ISO/IEC 18013-5 [12], suitably extended by the present document, and data elements defined in ISO/IEC 18013-5 [12], ISO/IEC 23220-2 [13], and the present document. NOTE: ISO/IEC 18013-5 [12] defines a namespace and a set of elements (placed in the mentioned namespace) suitable for EAAs that are mobile driving licenses. ISO/IEC 23220-2 [13] defines another namespace and a set of elements of general use in any type of electronic document, suitable for EAAs that are NOT mobile driving licenses. c) JSON-LD W3C-VC. Realization based on JSON-LD serialization of W3C Verifiable Credentials Data Model (clause 7). W3C Verifiable Credentials Data Model is specified in W3C Recommendation (15 May 2025): "Verifiable Credentials Data Model v2.0" [1]. d) X.509-AC. Realization based on X.509 Attribute Certificates (clause 8). X.509 Attribute Certificates are specified in IETF RFC 5755 [6]. 4) Aims to support the Commission Implementing Regulation (EU) 2024/2977 [i.3]. |
119 472-3 | Electronic Signatures and Trust Infrastructures (ESI); Profiles for Electronic Attestation of Attributes; Part 3: Profiles for issuance of EAA or PID | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/11947203/01.01.01_60/ts_11947203v010101p.pdf | The present document specifies a protocol for allowing an EUDI Wallet to request a Personal Identification Data (PID hereinafter) Provider, the issuance of a PID, and to request an Electronic Attestation of Attributes (EAA hereinafter) Provider, the issuance of EAA. The protocol specified builds on OpenID4VC-HAIP [1], which defines a profile of OpenID4VCI [2]. In addition to that, the protocol extends OpenID4VC-HAIP [1], for meeting requirements imposed by the EUDI Wallet ecosystem as specified in EUDI Wallet ARF [i.1], by EUDI Wallet TS03 [i.2], and by EAA formats, categories, and profiles specified in ETSI TS 119 472-1 [3]. More specifically, the present document defines requirements for: 1) Inclusion of the access certificates issued to PID/EAA Provider in the Issuer Metadata. 2) Inclusion of the registration certificates issued to PID/EAA Provider in the Issuer Metadata. 3) Inclusion of Embedded Disclosure Policy details in the Issuer Metadata. 4) Inclusion of details on the PID/EAA Provider preferences on the method to limit the number of times that a PID/EAA may be presented, in the Issuer Metadata. 5) Sending the Wallet Instance Attestation (WIA hereinafter) to the Pushed Authorisation Endpoint, and the Token Endpoint. 6) Sending the Wallet Unit Attestation (WUA hereinafter) to the Credential Endpoint. 7) Proofing possession of the private key associated to the public key in the WUA. 8) Proofing possession of the private key(s) associated to the public key(s) to be bound to the PID/EAA(s) to be issued. 9) Proofing that the same WSCA/WSCD possesses the private key associated to the public key in the WUA and the private key(s) associated to the public key(s) to be bound to the PID/EAA(s) to be issued. 10) Sending the details of the format(s) of the PID/EAA requested to the Authorisation Endpoint, and the Credential Endpoint. 11) Issuance of EAA in formats that are not covered by OpenID4VCI [2], as EAA built on X.509 Attribute certificates, for instance (X509-AC EAA specified in clause 8 of ETSI TS 119 472-1[3]). 12) Claims path for X509-AC EAA format, not covered by OpenID4VCI [2]. NOTE: Some of the specifications used by the present document are not yet final. Should breaking changes occur in some of the mentioned drafts, they should not be taken into account unless a new version of the present document is generated referencing the updated drafts or final versions. ETSI ETSI TS 119 472-3 V1.1.1 (2026-03) 7 |
119 476 | Electronic Signatures and Trust Infrastructures (ESI); Analysis of selective disclosure and zero-knowledge proofs applied to Electronic Attestation of Attributes | TR | 1.2.1 | http://www.etsi.org/deliver/etsi_tr/119400_119499/119476/01.02.01_60/tr_119476v010201p.pdf | The present document analyses cryptographic schemes for selective disclosure and their potential application for privacy of electronic attestation attributes in line with the expected requirement of the proposed regulation amending Regulation (EU) No 910/2014 (commonly called eIDAS2) [i.86]. NOTE 1: The term selective disclosure is a collective term that may also include various concepts of unlinkability, and predicates such as range proofs, depending on the context of the specific cryptographic scheme. The scope of the present document is primarily to describe selective disclosure and unlinkability properties of each analysed cryptographic scheme. NOTE 2: Range proofs, and more general predicate proofs as well as general-purpose ZKPs are out of scope in the ARF [i.59]. If an analysed cryptographic scheme relies on any of these features, they will be described in the context of that particular cryptographic scheme. The present document aims at providing a comprehensive overview of existing cryptographic schemes for selective disclosure and the formats and protocols associated with these cryptographic schemes. The aim of the present document is first to provide input to ETSI standardization relating to how selective disclosure may be applied to the eIDAS2 (Qualified) Electronic Attribute Attestations ((Q)EAA) and Person Identification Data (PID). More specifically, the present report may serve as input to (Q)EAA issuance policies as being specified in ETSI TS 119 471 [i.80] and (Q)EAA profiles as being specified in ETSI TS 119 472-1 [i.81]. Second, the present document will also analyse the policy requirements for (Q)TSPs and PID providers issuing (Q)EAAs or PIDs with selective disclosure capabilities to EUDI Wallets. Third, the present document analyses how the user of an EUDI Wallet can present selected attributes of a (Q)EAA or PID to relying parties (or (Q)TSPs acting as relying parties). Consequently, the present document can highlight needs that may require future standardization efforts. The present document analyses the concepts of selective disclosure, unlinkability, and predicates (including range proofs) in the following main clauses: • Selective disclosure signature schemes (clause 4): This clause describes the academic research of the cryptographic algorithms and schemes that shape the foundation for selective disclosure signature schemes. • Selective disclosure (Q)EAA formats (clause 5): This clause describes the (Q)EAA formats that have been developed and standardized based on the aforementioned selective disclosure signature schemes. • Selective disclosure protocols and systems (clause 6): This clause describes the complete protocols and /or systems that have been developed and standardized based on the aforementioned selective disclosure signature schemes and (Q)EAA formats. Since the ARF [i.59] specifies the PID to be issued to an EUDI Wallet as ISO mDL [i.140] (with ISO mDL MSO for selective disclosure) or W3C Verifiable Credentials (with SD-JWT for selective disclosure), these formats and protocols are analysed in more detail in clause 7. |
119 476-1 | Electronic Signatures and Trust Infrastructures (ESI); Selective disclosure and zero-knowledge proofs applied to Electronic Attestation of Attributes; Part 1: Feasibility study | TR | 1.3.1 | http://www.etsi.org/deliver/etsi_tr/119400_119499/11947601/01.03.01_60/tr_11947601v010301p.pdf | The present document analyses cryptographic schemes for selective disclosure and their potential application for privacy of electronic attestation attributes in line with the expected requirement of the proposed regulation amending Regulation (EU) No 910/2014 (commonly called eIDAS2) [i.103]. NOTE 1: The term selective disclosure is a collective term that may also include various concepts of unlinkability, and predicates such as range proofs, depending on the context of the specific cryptographic scheme. The scope of the present document is primarily to describe selective disclosure and unlinkability properties of each analysed cryptographic scheme. NOTE 2: Range proofs, and more general predicate proofs as well as general-purpose ZKPs are out of scope in the ARF [i.71]. If an analysed cryptographic scheme relies on any of these features, they will be described in the context of that particular cryptographic scheme. The present document aims at providing a comprehensive overview of existing cryptographic schemes for selective disclosure and the formats and protocols associated with these cryptographic schemes. The aim of the present document is first to provide input to ETSI standardization relating to how selective disclosure may be applied to the eIDAS2 (Qualified) Electronic Attribute Attestations ((Q)EAA) and Person Identification Data (PID). More specifically, the present document may serve as input to (Q)EAA issuance policies as being specified in ETSI TS 119 471 [i.96] and (Q)EAA profiles as being specified in ETSI TS 119 472-1 [i.97]. Second, the present document will also analyse the policy requirements for (Q)TSPs and PID providers issuing (Q)EAAs or PIDs with selective disclosure capabilities to EUDI Wallets. Third, the present document analyses how the user of an EUDI Wallet can present selected attributes of a (Q)EAA or PID to relying parties (or (Q)TSPs acting as relying parties). Consequently, the present document can highlight needs that may require future standardization efforts. The present document analyses the concepts of selective disclosure, unlinkability, and predicates (including range proofs) in the following main clauses: • Selective disclosure signature schemes (clause 4): This clause describes the academic research of the cryptographic algorithms and schemes that shape the foundation for selective disclosure signature schemes. • Selective disclosure (Q)EAA formats (clause 5): This clause describes the (Q)EAA formats that have been developed and standardized based on the aforementioned selective disclosure signature schemes. • Selective disclosure protocols and systems (clause 6): This clause describes the complete protocols and /or systems that have been developed and standardized based on the aforementioned selective disclosure signature schemes and (Q)EAA formats. Since the ARF [i.71] specifies the PID to be issued to an EUDI Wallet as mdoc [i.181] (with MSO for selective disclosure) or W3C Verifiable Credentials (with SD-JWT for selective disclosure), these formats and protocols are analysed in more detail in clause 7. |
119 478 | Electronic Signatures and Trust Infrastructures (ESI); Specification of interfaces related to Authentic Sources | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/119478/01.01.01_60/ts_119478v010101p.pdf | Article 45e of the amended eIDAS-Regulation (EU) No 910/2014 [i.33] obliges the EU Member States to ensure until 24 December 2026, that qualified trust service providers are able to verify at least the attributes listed Annex VI of the Regulation, wherever those attributes rely on authentic sources within the public sector, at the request of the user. Article 9 of CIR (EU) 2025/1569 [i.11] provides more information with respect to the verification mechanism, which can involve single points of verification for the attributes listed in Annex VI. Such a verification access point receives the attributes and the identification data of the subject of the attribute as input (see Article 9 (3) of [i.11]) and returns a verification result, which exclusively states whether the attribute under consideration has been verified or not, and the public sector body responsible for the authentic source or, where applicable, the public sector body designated to act on behalf of the authentic source against which the attribute has been verified (see Article 9 (4) of [i.11]). According to Article 10 (1) of CIR (EU) 2025/1569 [i.11], the "Member States may refer to and re-use the common services of the technical system set out in Article 14 of regulation (EU) 2018/1724 [i.35], as well as the national components connected to them". In a similar manner, according to Article 10 (2) of CIR (EU) 2025/1569 [i.11], "the European Commission shall refer to and re-use, where appropriate, the common services of the technical system pursuant to regulation (EU) 2018/1724 [i.35]". To be able to profit from the functionality of these services, the present document introduces in clause 5 the Discover Interface, which allows to access the semantic repository and the data services directory within the common services of the OOTS. The I1 (Discover) interface described in clause 5 is an HTTP-based interface according to ISO 15000-3 [24], as profiled by the European Commission in [i.16]. Annex A of the present document contains an OpenAPI specification [27] for this interface. The present document specifies in clause 6 the Authentic Source Interface. The I2 (Verify) interface allows to verify attributes against the content stored in an authentic source as requested in Article 45e of the amended eIDAS-Regulation (EU) No 910/2014 [i.33]. In addition, an optional I3 (Retrieve) interface is specified, which allows to retrieve attributes from an authentic source, or an intermediary acting on behalf the authentic source. The Authentic Source Interface specified in the present document contains in clause 6.1 an HTTP-based Application Programming Interface (API), which corresponding OpenAPI specification [27] is provided in Annex B of the present document. Furthermore, the present document also specifies in clause 6.2 a second ISO 15000-based interface, which utilizes the electronic delivery mechanisms according to ISO 15000-2 [23]. Moreover, according to Article 9 (5) of [i.11], the "Member States may impose access controls or other verification mechanisms that provide integrity, authenticity, and confidentiality to determine that the requester is a qualified trust service provider and is acting at the request of a legitimate user". For the HTTP-based API, clause 6.1.3 specifies such an authorization mechanism based on the OAuth 2.0 authorization framework according to IETF RFC 6749 [6] and related standards. For the ISO 15000-based interface, the qualified trust service status is verified and the trust service provider is registered as client in advance, under procedures out of scope of the present specification. In this case the evidence that the client is acting at the request of a legitimate user is also gathered before the request under procedures out of scope of the present specification. The present document specifies the necessary technical framework for the required access of the involved authentic sources, which includes architectures, components, interfaces, protocols and data structures. Note, that policy and security requirements for the involved resource service endpoints are beyond the scope of the present document. ETSI ETSI TS 119 478 V1.1.1 (2026-01) 7 |
119 479-2 | Electronic Signatures and Trust Infrastructures (ESI); Technological Solutions for the EU Digital Identity Framework; Part 2: EAA Extended Validation Services Framework and Application | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119400_119499/11947902/01.01.01_60/tr_11947902v010101p.pdf | The present document proposes an extended validation mechanism leveraging on the existing OID4VP protocol. Its primary aim is to support the secure and interoperable validation of electronic attestations by identifying standardization needs in the context of the attestation rulebook and attribute catalogues. Key focus areas include: • introduction of attestation refreshing and attestation encryption mechanisms; • description of embedded disclosure policies and support for pricing policies; • further considerations on the extension of attestation metadata structures to include policy-related parameters. |
119 495 | Electronic Signatures and Trust Infrastructures (ESI); Sector Specific Requirements; Certificate Profiles and TSP Policy Requirements for Open Banking | TS | 1.7.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/119495/01.07.01_60/ts_119495v010701p.pdf | The present document: 1) Specifies requirements for qualified certificates, or other non-EU schemes which provide equivalent assurance based ETSI best practices, for electronic seals and website authentication, to be used by payment service providers in order to meet needs of Open Banking including the EU PSD2. These profiles are based on ETSI EN 319 412-1 [1], ETSI EN 319 412-3 [3], ETSI EN 319 412-4 [4], IETF RFC 3739 [7] and ETSI EN 319 412-5 [i.6] (by indirect reference). 2) Specifies additional TSP policy requirements for the management (including verification and revocation) of additional certificate attributes as required by the above profiles. These policy requirements extend the requirements in ETSI EN 319 411-2 [5]. 3) Specifies specific requirements for EU use of the qualified certificates for electronic seals and website authentication, to meet the requirements of the EU PSD2 Regulatory Technical Standards (RTS) [i.3]. Certificates for electronic seals can be used for providing evidence with legal assumption of authenticity (including identification and authentication of the source) and integrity of a transaction. Certificates for website authentication can be used for identification and authentication of the communicating parties and securing communications. Communicating parties can be payment initiation service providers, account information service providers, payment service providers issuing card-based payment instruments or account servicing payment service providers. The identifier for the Competent Authority and its country (see clause 5.2.3) can be used to identify the applicable legislation. It can be determined whether a country's' national legislation follows the EU PSD2 Directive (Directive (EU) 2015/2366 [i.2]), and hence whether the RTS [i.3] applies, using the EBA list of NCA identifiers as identified in Annex D. The requirements in clauses 5 and 6 for the certificate profile and policy are common to both EU PSD2 and non- EU Open Banking certificates. The present document identifies information for Open Banking that is provided by a regulatory authority recognized through regulations as competent for providing such information. In the case of EU PSD2 this information is provided through a national register operated by the NCA or a register operated by the European Banking Authority. In addition, the TSP may provide services to the Competent Authority to enable revocation of certificates based on information provided by competent authority. The present document places no requirements on the operation of Competent Authorities providing information for Open Banking. |
119 500 | Business Driven Guidance for Trust Application Service Providers | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119500_119599/119500/01.01.01_60/tr_119500v010101p.pdf | The present document provides guidance on the use of standards for Trust Application Service Providers (area 5) as identified in the framework for standardization of signatures: overview [i.1]. The present document then describes the Business Scoping Parameters relevant to this area (see clause 6) and how the relevant standards and options for this area can be identified given the Business Scoping Parameters (clause 7). The target audience of the present document includes: 1) Business managers who potentially require support from digital signatures in their business will find here an understandable explanation of how services applying digital signatures standards can be used to meet their business needs. 2) Application architects who will find here material that will guide them throughout the difficult process of designing a system that fully and properly satisfies all the business and legal/regulatory requirements specific to services applying digital signatures, and will gain a better understanding on how to select the appropriate standards to be implemented and/or used. 3) Developers of the systems who will find an understanding of a good part of the ultimate reasons that led the systems to be designed as they were, as well as a proper knowledge of the standards that exist in the field and to be known in detail for a proper development. |
119 511 | Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for trust service providers providing long-term preservation of digital signatures or general data using digital signature techniques | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.02.01_60/ts_119511v010201p.pdf | The present document builds on the general policy requirements specified in ETSI EN 319 401 [1], specifies policy and security requirements for trust service providers providing long-term preservation of digital signatures and of general data, i.e. signed data or unsigned data, using digital signature techniques. The present document aims at supporting preservation services in different regulatory frameworks. Specifically, but not exclusively, the preservation service addressed in the present document aims at supporting qualified preservation service for qualified electronic signatures or seals as per Regulation (EU) No 910/2014 [i.2]. Specifically, but not exclusively, digital signatures in the present document cover electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.2]. The present document addresses two main cases: 1) The preservation over long periods of time, using digital signature techniques, of the ability to validate a digital signature, of the ability to maintain its validity status and of the ability to get a proof of existence of the associated signed data as they were at the time of the submission to the preservation service even if later the signing key becomes compromised, the certificate expires, or cryptographic attacks become feasible on the signature algorithm or the hash algorithm used in the submitted signature. NOTE 1: A qualified preservation service for qualified electronic signatures or seals as per Regulation (EU) No 910/2014 [i.2] for which the status of the technical validity needs to be preserved, is covered in this case. NOTE 2: The validity status of a signature means the status of the signature that will not change over time. Such a status may be valid (TOTAL_PASSED according to ETSI EN 319 102-1 [i.6]) or invalid (TOTAL_FAILED and certain cases for INDETERMINATE according to ETSI EN 319 102-1 [i.6]). NOTE 3: "Digital signature techniques" designates techniques based on digital signatures, time-stamps or evidence records. 2) The provision of a proof of existence of digital objects, whether they are signed or not, using digital signature techniques (digital signatures, time-stamp tokens, evidence records, etc.). NOTE 4: In this case, even if the main object to be preserved is a signature, it is treated in the same way as any other file. NOTE 5: A proof of existence of digital object not using digital signature techniques is not in the scope of the present document. The present document covers different strategies for the preservation service. The applicable requirements depend on the strategy chosen by the preservation service. EXAMPLE 1: The preservation service can provide storage, no storage, or temporary storage. EXAMPLE 2: The preservation service can receive the digital signature, the signed data, the revocation information or only hash values and evidences. The present document identifies specific controls needed to address specific risks associated with preservation services. The transformation of the original data into another data object with equivalent object content and semantic to avoid the risk that the original data object/viewer system is becoming obsolete is out of the scope of the present document. ETSI ETSI TS 119 511 V1.2.1 (2025-10) 8 |
119 512 | Electronic Signatures and Infrastructures (ESI); Protocols for trust service providers providing long-term data preservation services | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.02.01_60/ts_119512v010201p.pdf | Based on a scoping study and survey with respect to long-term preservation techniques for digital signatures and general data documented in ETSI SR 019 510 [i.13], the present document and its companion document ETSI TS 119 511 [i.14] have been created. ETSI TS 119 511 [i.14] specifies policy and security requirements for trust service providers providing long-term preservation of digital signatures and of general data, i.e. unsigned data or signed data, using digital signature techniques. The present document complements ETSI TS 119 511 [i.14] and specifies protocols for trust service providers providing long-term data preservation services of digital signatures and of general data (i.e. unsigned data or signed data). Specifically, but not exclusively, digital signatures in the present document cover electronic signatures, advanced electronic signatures, qualified electronic signatures, electronic seals, advanced electronic seals, and qualified electronic seals as per Regulation (EU) No 910/2014 [i.1]. The present document first addresses general aspects (see clause 4) such as a system architecture for preservation, which contains a preservation interface offered by the preservation service and used by the client (see clause 4.1). The preservation service may aim at different preservation goals (see clause 4.2), may or may not provide storage functionality (see clause 4.3), and provide different profiles of preservation schemes, which may implement different preservation evidence policies (see clause 4.4). In a second step, the present document specifies methods and data objects constituting a protocol between a client and a long-term data preservation service for the issuance and maintenance of evidences (see clause 5). For each call at the preservation interface it first specifies the semantics in a generic fashion and then specifies the concrete syntax of the conveyed data elements based on XML and JSON together with its binding to SOAP [i.25] and REST respectively. |
119 520-1 | Electronic Signatures and Trust Infrastructures (ESI); Framework of ERDS/REM standards; Part 1: New (Q)ERDS/(Q)ERDSP standardization rationalized framework as a result of the new components brought by eIDAS2.0 | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119500_119599/11952001/01.01.01_60/tr_11952001v010101p.pdf | The present document defines the new (Q)ERDS/(Q)ERDSP standardization rationalized framework, identifying the most relevant changes to be performed in the framework currently existing, among which: the incorporation of an ERDS HTTP-based baseline, offering similar features than REM baseline but on HTTP-based protocols; those due to the changes brought by eIDAS 2.0 [i.2] (including new components such as the EU eWallet, and the Electronic Attestations of Attributes); and those ones due to emerging technologies that might have an impact in this field. It also contains recommendations for updating ETSI TR 119 000 [i.4] and ETSI TR 119 001 [i.5]. Finally, the present document identifies the issues that may impact in the policy and security requirements standards. |
119 520-2 | Electronic Signatures and Trust Infrastructures (ESI); Framework of ERDS/REM standards; Part 2: Impact of emerging technologies on ERDS/REM Models | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119500_119599/11952002/01.01.01_60/tr_11952002v010101p.pdf | The present document aims to study the impact of emerging technologies and models for ERDS/REM provision and assess their impact on the ERDS framework of standards. The approach followed is to: • Monitor emerging ERDS/REM technologies and models that have been identified. The result of this activity is reported in clause 4. • Assess the result of monitoring and identify concrete proposals on ERDS/REM services provision and models. The result of this activity is reported in clause 5 and the impact on the ERDS framework is reflected in ETSI TR 119 520-1 [i.13]. |
119 524-1 | Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Electronic Registered Delivery Services; Part 1: Testing conformance | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119500_119599/11952401/01.02.01_60/ts_11952401v010201p.pdf | The present document defines the set of checks to be performed for testing conformance in the provision of Electronic Registered Delivery Services against the specific technical requirements defined in ETSI EN 319 522-3 [3], ETSI EN 319 522-4-1 [4] and ETSI EN 319 522-4-2 [5]. More specifically, the present document defines test assertions for testing conformance regarding: 1) The structure and contents of ERDS evidence as defined in ETSI EN 319 522-3 [3] (clause 6). 2) The structure and contents of new metadata defined in ETSI EN 319 522-3 [3] (clause 7). 3) The construction of AS4 ERDS messages (clause 8). 4) The generation of digital signatures in ERDS messages and ERDS evidence (clause 9). 5) Some aspects of the Common Service Interface (clause 10). 6) Relevant aspects of the provision of the service, namely: the generation of ERDS evidence following certain events and the security measures in the relevant interfaces defined in ETSI EN 319 522-1 [1] (clause 11). The present document does not define test assertions for testing conformance in the provision of Electronic Registered Delivery Services against technical requirements defined outside of any of the parts of ETSI EN 319 522 [1] to [6], namely, requirements for: AS4 [15], Business Document Metadata Service Location Version 1.0 (BDXL) [17], Service Metadata Publishing (SMP) Version 1.0 (SMP) [18] and digital signatures that are defined in their respective specifications. |
119 524-2 | Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Electronic Registered Delivery Services; Part 2: Test suites for interoperability testing of Electronic Registered Delivery Service Providers | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119500_119599/11952402/01.02.01_60/ts_11952402v010201p.pdf | The present document defines: 1) A test suite for supporting interoperability tests within the field of Electronic Registered Delivery Services (ERD services or ERDS hereinafter) as specified in ETSI EN 319 522 parts 1 [1], 2 [2], 3 [3], 4 [4], [5] and [6]. The test suite defines test cases for the following environments: - Environments that correspond to the basic model as defined in ETSI EN 319 522-1 [1] where sender and all the entities at receiving side are subscribed to the same ERDS. - Environments that correspond to the 4-corner model as defined in ETSI EN 319 522-1 [1] where sender is subscribed to one ERDS and the entities at receiving side are subscribed to another one, and no intermediate ERDS is required for relaying ERD messages between them. - Environments that correspond to the extended model as defined in ETSI EN 319 522-1 [1] where sender is subscribed to one ERDS and the entities at receiving side are subscribed to another one, and intermediate ERDSs are required for relaying ERD messages between them. 2) A mechanism for documenting new test cases and expanding the aforementioned test suite. |
119 530 | Electronic Signatures and Infrastructures (ESI); Registered Electronic Mail (REM); Feasibility study: Interoperability profile between ETSI EN 319 532-based REM systems and PReM-based systems | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119500_119599/119530/01.01.01_60/tr_119530v010101p.pdf | The present document represents a feasibility study for an interoperability profile between systems based on ETSI EN 319 522 [i.21] / ETSI EN 319 532 [i.22] ERDS/REMS specification and UPU S52-2 PReM specification [i.25]. |
119 534-1 | Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Registered Electronic Mail Services; Part 1: Testing conformance | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119500_119599/11953401/01.02.01_60/ts_11953401v010201p.pdf | The present document defines the set of checks to be performed for testing conformance in the provision of Registered Electronic Mail Services against the specific technical requirements defined in ETSI EN 319 532-3 [1] and against technical requirements for the provision of the service defined in ETSI EN 319 532-1 [2]. More specifically, the present document defines test assertions for testing conformance regarding: 1) The construction of MIME and SMIME headers (clause 5) and bodies (clause 6) in ETSI EN 319 532-3 [1]. 2) The construction of REM messages (clause 7). 3) The generation of digital signatures in REM messages and ERDS evidence (clause 8). 4) Some aspects of the Common Service Interface (clause 9). 5) The structure and contents of ERDS evidence (clause 10). 6) Relevant aspects of the provision of the service, namely: the generation of ERDS evidence following certain events, and the security measures in the relevant interfaces defined in ETSI EN 319 532-3 [1], clause 11. The present document does not define the checks to be performed for testing conformance in the provision of Registered Electronic Mail Services against technical requirements defined in none of the technical specifications on which ETSI EN 319 532-3 [1] is built. |
119 534-2 | Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Registered Electronic Mail Services; Part 2: Test suites for interoperability testing of providers using same format and transport protocols | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119500_119599/11953402/01.02.01_60/ts_11953402v010201p.pdf | The present document defines: 1) A test suite for supporting interoperability tests within the field of Registered Electronic Mail (REM hereinafter) as specified in ETSI EN 319 532 parts 1 [3], 2 [4], 3 [5] and 4 [6]. The test suite defines test cases for the following environments: - Environments that correspond to the basic model as defined in ETSI EN 319 532-1 [3] where sender and all the entities at receiving side are subscribed to the same REMS. Test cases are defined for REMSs operating Store&Forward and for REMSs operating Store&Notify styles. - Environments that correspond to the 4-corner model as defined in ETSI EN 319 532-1 [3] where sender is subscribed to one REMS and the entities at receiving side are subscribed to another one, and no intermediate REMS is required for relaying REM messages between them. Test cases are defined for covering the three possible different combinations of styles, namely Store&Forward to Store&Forward, Store&Forward to Store&Notify, and Store&Notify to Store&Forward. - Environments that correspond to the extended model as defined in ETSI EN 319 532-1 [3] where sender is subscribed to one REMS and the entities at receiving side are subscribed to another one, and intermediate REMSs are required for relaying REM messages between them. Test cases are defined for covering two different combinations of styles, namely Store&Forward to Store&Forward to Store&Forward, Store&Forward to Store&Notify to Store&Forward. 2) A mechanism for documenting new test cases and expanding the aforementioned test suite. |
119 540 | Electronic Signatures and Trust Infrastructures (ESI); Standardization requirements for Smart Contracts based on Electronic Ledgers | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/119500_119599/119540/01.01.01_60/tr_119540v010101p.pdf | The present document defines standardization issues for Smart Contracts, as defined in Data Act [i.1], and based on Electronic Ledgers as defined by eIDAS2 [i.2]. It builds on existing and planned standardization and publicly available specifications. It presents a novel and as yet unpublished Chain of Trust, by addressing the role of all involved entities in building, deploying, and executing a Smart Contract computer program on an Electronic Ledger. All the relevant actors, artifacts, hardware, networks and tools, are identified by emphasizing the critical points where governance, safety, security, and identity issues are required. The Chain of Trust will be extensively translated in suitable recommendations in ETSI TS 119 541 [i.12] and ETSI TS 119 542 [i.16]. The security of Smart Contracts will be significantly compromised by an incomplete validation chain, which exposes users to various risks, including fraud and attacks. NOTE 1: The present document summarizes the results of a scoping study that examines the issues for the application of Smart Contracts, particularly in relation to the European frameworks outlined in the Data Act [i.1] and eIDAS2 [i.2] regulations. The goal is to pinpoint standardization issues for Smart Contracts and Electronic Ledgers in data-sharing computer applications. Additionally, the study considers reports and standards from ETSI ISG PDL (at the time of the publication of the present document conveyed into ETSI TC DATA), ETSI TC ESI, and checks consistency with ISO and CEN documents. NOTE 2: Unless otherwise specified in the present document, the definition of Smart Contracts refers to Regulation (EU) 2023/2854 [i.1] and the definition of Electronic Ledgers, and Qualified Electronic Ledger refer to Regulation (EU) 2022/2065 [i.2]. See Annex C for further details. The present document is structured as follows: • Clause 4 enumerates the regulations, applied standards, EU initiatives and other activities involved for the use of Smart Contracts in Data Sharing Computer Applications. • Clause 5 is the core of the present document. It identifies the entities and their inter-relations for the creation, validation, deployment and use of Smart Contracts in Electronic Ledgers. A Chain of Trust listing the main entities and their relations will be presented and discussed; the Chain of Trust allows to highlight issues that will be focused in the next clause. • Clause 6 lists in a concise way the issues that are translated into formal requirements in ETSI TS 119 541 [i.12] and ETSI TS 119 542 [i.16]. • Clause 7 concludes. • Annex A presents four figures showing a particular, fine-grained, implementation of the Chain of Trust as presented in Table 1: entities, their relations participating in the design of SC Language, the deployment, and execution of Smart Contracts on a Qualified Electronic Ledger. Other implementations are also possible. • Annex B graphically and informally depicts, the Chain of Trust, as formally described in Table 2. • Annex C gives a comparative overview of definitions in normative and standard documents. ETSI ETSI TR 119 540 V1.1.1 (2025-10) 8 |
119 541 | Electronic Signatures and Trust Infrastructures (ESI); Policy and security requirements for Smart Contracts using Electronic Ledgers | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119500_119599/119541/01.01.01_60/ts_119541v010101p.pdf | The present document specifies the policy and security requirements for Smart Contracts using Electronic Ledgers as defined in Regulation (EU) 910/2014 amended by Regulation (EU) 2024/1183 [i.3], and with other trustworthy tools, taking into account the framework of requirements identified in ETSI TR 119 540 [i.1]. NOTE 1: The present document extends provisions from ETSI EN 319 401 [1] and TS 18264 [2], using the structure of ETSI EN 319 401 [1] as the basis, to address the general requirements identified by the Chain of Trust described in clause 5.1 of [i.1]. NOTE 2: When applying ETSI EN 319 401 [1] to the scope and context of the present document any reference in ETSI EN 319 401 [1] to TSP is to be read as "SC Provider". NOTE 3: In ETSI EN 319 401 [1] there are references to "management bodies" which for the purposes of the present document is to be read as an entity within the SC provider's organization with a defined role identifiable using methods defined in ETSI TS 119 542 [5]. |
119 542 | Electronic Signatures and Trust Infrastructures (ESI); Use of EU Digital Identity Wallets and electronic signatures for identification with Smart Contracts | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119500_119599/119542/01.01.01_60/ts_119542v010101p.pdf | The present document specifies the use of EU Digital Identity Wallets, and advanced or qualified electronic signatures and seals conforming to the requirements of Regulation (EU) 2024/1183 [i.3], amending Regulation (EU) No 910/2014, (referred as eIDAS hereinafter in the present document). The advanced or qualified electronic signatures and seals in the present document are implemented using digital signatures. The present document supports identification of natural or legal persons playing relevant roles in different stages of the life cycle of Smart Contracts, taking into account the needs for identification highlighted in ETSI TR 119 540 [i.1]. |
119 600 | Electronic Signatures and Infrastructures (ESI); Guidance on the use of standards for trust service status lists providers | TR | 1.2.1 | http://www.etsi.org/deliver/etsi_tr/119600_119699/119600/01.02.01_60/tr_119600v010201p.pdf | The present document provides guidance on the selection of standards and their options to organizations wishing to establish a trust service status list, for a particular business implementation context and associated business requirements. The present document describes the business scoping parameters relevant to this area and how the relevant standards and options for this area can be identified given these business scoping parameters. The target audience of the present document includes those potentially requiring support from trust services and in particular trust service status lists. The present document provides an explanation of how related standards can be used to meet the business needs. |
119 602 | Electronic Signatures and Trust Infrastructures (ESI); Lists of trusted entities; Data model | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119600_119699/119602/01.01.01_60/ts_119602v010101p.pdf | The present document defines a data model for lists of trusted entities, as well as bindings of such lists in various syntaxes allowing relying parties to establish and process lists of trusted entities. NOTE: The data model for a list of trusted entities aims to be an abstract generalization of the existing specifications of trusted lists provided in ETSI TS 119 612 [1]. The present document applies to any community aiming to establish a way to represent approval statuses of trusted entities as they are defined in the present document. The present document specifically applies to European Union lists of providers of person identity data, wallet providers, providers of wallet relying party access certificates, and public sector bodies issuing electronic attestations of attributes, through the specifications of specific profiles defined in Annexes. |
119 612 | Electronic Signatures and Trust Infrastructures (ESI); Trusted Lists | TS | 2.4.1 | http://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.04.01_60/ts_119612v020401p.pdf | The present document specifies a format and mechanisms for establishing, locating, accessing and authenticating a trusted list which makes available trust service status information so that interested parties may determine the status of a listed trust service at a given time. It defines the format and semantics of a TL as well as the mechanisms for accessing TLs. It also provides guidance for locating and authenticating TLs. The present document applies to European Union Member State (EU MS) trusted lists as a means to express trust service status information with regards to their compliance with the relevant provisions laid down in Regulation (EU) No 910/2014 [i.10] and in its applicable secondary legislation. In the context of non-EU countries or international organizations, scheme operators may issue trusted lists in accordance with the present document to facilitate mutual recognition of digital signatures. In addition, the present document defines requirements for relying parties to use TLs and the status information held within them. |
119 614-1 | Electronic Signatures and Infrastructures (ESI); Testing Conformance and Interoperability of Trusted Lists; Part 1: Specifications for testing conformance of XML representation of Trusted Lists | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf | The present document defines the set of checks to be performed for testing conformance of Trusted Lists as specified in ETSI TS 119 612 [1]. Checks specified by the present document are exclusively constrained to elements specified by ETSI TS 119 612 [1], certain elements defined in ETSI TS 101 903 [2], and certain elements specified in XMLSig [3]. Regarding XML elements, the present document explicitly differentiates between structural requirements that are defined by the different XML Schemas where the tested elements are defined, and the rest of the requirements specified by ETSI TS 119 612 [1]. The present document is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set includes tests on the correctness of the structure of all the elements specified by the XML Schemas associated with ETSI TS 119 612 [1]. |
119 615 | Electronic Signatures and Trust Infrastructures (ESI); Trusted lists; Procedures for using and interpreting European Union Member States national trusted lists | TS | 1.3.1 | http://www.etsi.org/deliver/etsi_ts/119600_119699/119615/01.03.01_60/ts_119615v010301p.pdf | The present document specifies procedures for using and interpreting EUMS national trusted lists when validating EU qualified trust service outputs against them (e.g. validating EU qualified certificates, EU qualified time stamps, evidences created by qualified electronic registered delivery services, EU electronic signatures or seals on EU qualified validation reports on EU qualified electronic signatures or seals). |
121 910 | Universal Mobile Telecommunications System (UMTS); Multi-mode User Equipment (UE) issues; Categories principles and procedures (3G TR 21.910 version 3.0.0 Release 1999) | TR | 3.0.0 | http://www.etsi.org/deliver/etsi_tr/121900_121999/121910/03.00.00_60/tr_121910v030000p.pdf | ........................................................................................................................................................5 |
121 978 | Universal Mobile Telecommunications System (UMTS); Feasibility Technical Report - CAMEL Control of VoIP Services (3G TR 21.978 version 3.0.0 Release 1999) | TR | 3.0.0 | http://www.etsi.org/deliver/etsi_tr/121900_121999/121978/03.00.00_60/tr_121978v030000p.pdf | ........................................................................................................................................................6 |
122 043 | Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Support of Localised Service Area (SoLSA); Service description; Stage 1 (3G TS 22.043 version 3.1.0 Release 1999) | TS | 3.1.0 | http://www.etsi.org/deliver/etsi_ts/122000_122099/122043/03.01.00_60/ts_122043v030100p.pdf | ........................................................................................................................................................5 |
122 907 | Universal Mobile Telecommunications System (UMTS); Terminal and smart card concepts (3G TR 22.907 version 3.1.3 Release 1999) | TR | 3.1.3 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122907/03.01.03_60/tr_122907v030103p.pdf | |
122 924 | Universal Mobile Telecommunications System (UMTS); Service aspects; Charging and Accounting Mechanisms (3G TR 22.924 version 3.1.1 Release 1999) | TR | 3.1.1 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122924/03.01.01_60/tr_122924v030101p.pdf | |
122 925 | Universal Mobile Telecommunications System (UMTS); Service aspects; Quality of Service and Network Performance (3G TR 22.925 version 3.1.1 Release 1999) | TR | 3.1.1 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122925/03.01.01_60/tr_122925v030101p.pdf | |
122 945 | Universal Mobile Telecommunications System (UMTS); Study on provisioning of fax in GSM and UMTS (3G TR 22.945 version 3.0.0 Release 1999) | TR | 3.0.0 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122945/03.00.00_60/tr_122945v030000p.pdf | |
122 960 | Universal Mobile Telecommunications System (UMTS); Mobile multimedia services including mobile Intranet and Internet services (3G TR 22.960 version 3.0.1 Release 1999) | TR | 3.0.1 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122960/03.00.01_60/tr_122960v030001p.pdf | |
122 970 | Universal Mobile Telecommunications System (UMTS); Service aspects; Virtual Home Environment (VHE) (3G TR 22.970 version 3.0.1 Release 1999) | TR | 3.0.1 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122970/03.00.01_60/tr_122970v030001p.pdf | ........................................................................................................................................................5 |
122 971 | Universal Mobile Telecommunications System (UMTS); Automatic Establishment of Roaming Relationships (3G TR 22.971 version 3.1.1 Release 1999) | TR | 3.1.1 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122971/03.01.01_60/tr_122971v030101p.pdf | |
122 975 | Universal Mobile Telecommunications System (UMTS); Service aspects; Advanced Addressing ; (3G TR 22.975 version 3.1.0 Release 1999) | TR | 3.1.0 | http://www.etsi.org/deliver/etsi_tr/122900_122999/122975/03.01.00_60/tr_122975v030100p.pdf | |
123 054 | Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Description for the use of a Shared Inter Working Function (SIWF) in a GSM PLMN - Stage 2 (3G TS 23.054 version 3.0.0 Release 1999) | TS | 3.0.0 | http://www.etsi.org/deliver/etsi_ts/123000_123099/123054/03.00.00_60/ts_123054v030000p.pdf | ........................................................................................................................................................6 |
123 070 | Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Routeing of calls to/from Public Data Networks (PDN) (3G TS 23.070 version 3.0.0 Release 1999) | TS | 3.0.0 | http://www.etsi.org/deliver/etsi_ts/123000_123099/123070/03.00.00_60/ts_123070v030000p.pdf | ........................................................................................................................................................5 |
123 972 | Universal Mobile Telecommunications System (UMTS); Circuit Switched Multimedia Telephony (3G TR 23.972 version 3.0.0 Release 1999) | TR | 3.0.0 | http://www.etsi.org/deliver/etsi_tr/123900_123999/123972/03.00.00_60/tr_123972v030000p.pdf | ........................................................................................................................................................4 |
124 012 | Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface (3G TS 24.012 version 3.0.0 Release 1999) | TS | 3.0.0 | http://www.etsi.org/deliver/etsi_ts/124000_124099/124012/03.00.00_60/ts_124012v030000p.pdf | ........................................................................................................................................................5 |
125 941 | Universal Mobile Telecommunications System (UMTS); TSG RAN WG4 document structure (3G TS 25.941 version 3.1.0 Release 1999) | TR | 3.1.0 | http://www.etsi.org/deliver/etsi_tr/125900_125999/125941/03.01.00_60/tr_125941v030100p.pdf | ........................................................................................................................................................4 |
125 990 | Universal Mobile Telecommunications System (UMTS); Vocabulary (3G TR 25.990 version 3.0.0 Release 1999) | TR | 3.0.0 | http://www.etsi.org/deliver/etsi_tr/125900_125999/125990/03.00.00_60/tr_125990v030000p.pdf | ........................................................................................................................................................5 |
126 915 | Universal Mobile Telecommunications System (UMTS); Echo Control For Speech and Multi-Media Services (3G TR 26.915 version 3.0.0 Release 1999) | TR | 3.0.0 | http://www.etsi.org/deliver/etsi_tr/126900_126999/126915/03.00.00_60/tr_126915v030000p.pdf | ........................................................................................................................................................5 |
129 006 | Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Interworking between the Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of packet switched data transmission services (3G TS 29.006 version 3.0.0 Release 1999) | TS | 3.0.0 | http://www.etsi.org/deliver/etsi_ts/129000_129099/129006/03.00.00_60/ts_129006v030000p.pdf | ........................................................................................................................................................5 |
132 106-8 | Universal Mobile Telecommunications System (UMTS); Telecommunication Management; Configuration Management; Part 8: Name convention for Managed Objects (3G TS 32.106-8 version 3.2.0 Release 1999) | TS | 3.2.0 | http://www.etsi.org/deliver/etsi_ts/132100_132199/13210608/03.02.00_60/ts_13210608v030200p.pdf | ........................................................................................................................................................6 |
133 901 | Universal Mobile Telecommunications System (UMTS); 3G Security - Criteria for cyptographic Algorithm design process (3G TR 33.901 version 4.0.0 Release 4) | TR | 4.0.0 | http://www.etsi.org/deliver/etsi_tr/133900_133999/133901/04.00.00_60/tr_133901v040000p.pdf | ........................................................................................................................................................5 |
134 907 | Universal Mobile Telecommunications System (UMTS); Report on electrical safety requirements and regulations (3G TR 34.907 version 3.0.0 Release 1999) | TR | 3.0.0 | http://www.etsi.org/deliver/etsi_tr/134900_134999/134907/03.00.00_60/tr_134907v030000p.pdf | ........................................................................................................................................................5 |
134 925 | Universal Mobile Telecommunications System (UMTS); Specific Absorbtion Rate (SAR) requirements and regulations in different regions (3G TR 34.925 version 3.0.0 Release 1999) | TR | 3.0.0 | http://www.etsi.org/deliver/etsi_tr/134900_134999/134925/03.00.00_60/tr_134925v030000p.pdf | ........................................................................................................................................................5 |
101 105 | Digital cellular telecommunications system (Phase 2+); Fraud Information Gathering System (FIGS); Service requirements - Stage 0 (GSM 01.31 version 7.0.1 Release 1998) | TR | 7.0.1 | http://www.etsi.org/deliver/etsi_tr/101100_101199/101105/07.00.01_60/tr_101105v070001p.pdf | The present document describes the requirements (at a stage 0 level) of the Fraud Information Gathering System (FIGS). FIGS provides the means for the HPLMN to monitor a defined set of subscriber activities. The aim is to enable service providers/network operators to use FIGS, and service limitation controls such as Operator Determined Barring (ODB) and Immediate Service Termination (IST), to limit their financial exposure to large unpaid bills produced on subscriber accounts whilst the subscriber is roaming outside their HPLMN. HPLMNs may also choose to collect information on subscriber activities whilst their subscribers are within the HPLMN. |
101 266 | Digital cellular telecommunications system (Phase 2+) (GSM); Multiband operation of GSM/DCS 1 800 by a single operator (GSM 03.26 version 7.0.0 Release 1998) | TR | 7.0.0 | http://www.etsi.org/deliver/etsi_tr/101200_101299/101266/07.00.00_60/tr_101266v070000p.pdf | The purpose of the present document is to describe the functionality of a Multiband GSM/DCS Network operated by a single operator and the Multiband GSM/DCS Mobile Station (MS). It also describes the necessary amendments to the GSM/DCS phase 2 specifications for the technical realization of the function. The resulting Amendment Requests (AR) and Change Requests (CR) necessary for Multiband Operation are listed in annex A. |
101 458 | Universal Mobile Telecommunications System (UMTS); Future direction of standards work on UMTS / IMT-2000 (TR 101 458 v1.0.0) | TR | 1.0.0 | http://www.etsi.org/deliver/etsi_tr/101400_101499/101458/01.00.00_60/tr_101458v010000p.pdf | The present document has been written by the ETSI Project for Universal Mobile Telecommunications System (UMTS) with the purpose of documenting ETSI's intentions for standardization work beyond the Initial Phase of UMTS (Note that the initial phase of UMTS is covered by the Third Generation Partnership Project - 3GPP.). This work will initially focus on "Services" and "Systems Architecture". Examples of work to be studied in the present document include the full IP vision for UMTS and the VHE. The present document will be updated as work progresses and decisions are made. Early versions of the present document will contain questions to be addressed by ETSI with the intention that these will evolve into a series of recommendations in later versions. The present document also examines "What should be the role of EP UMTS in defining the key characteristics for the later phases of UMTS?". Should any of the above tasks be done elsewhere in ETSI or should they be performed / managed in EP UMTS? The present document also looks at the place of UMTS within the ITU's IMT-2000 Family. The present document provides a record of the direction of EP UMTS's work. It is intended that later versions will be used as an input to other standardization groups as a statement of ETSI's UMTS requirements. |
101 641 | Digital cellular telecommunications system (Phase 2+) (GSM); Half rate speech; Performance characterization of the GSM half rate speech codec (GSM 06.08 version 6.0.0 Release 1997)) | TR | 6.0.0 | http://www.etsi.org/deliver/etsi_tr/101600_101699/101641/06.00.00_60/tr_101641v060000p.pdf | The present document gives background information on the performance of the GSM half rate speech codec. Experimental results from the characterization and verification tests carried out during the selection process by the Traffic CHannel Half rate Speech (TCH-HS) expert group are reported to give a more detailed picture of the behaviour of the GSM half rate speech codec under different conditions of operation. |
102 133 | Human Factors (HF); Access to ICT by young people: issues and guidelines | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102100_102199/102133/01.01.01_60/tr_102133v010101p.pdf | |
102 457 | Transmission and Multiplexing (TM); Study on the electromagnetic radiated field in fixed radio systems for environmental issues | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102400_102499/102457/01.01.01_60/tr_102457v010101p.pdf | The present document provides guidelines for assessing the compliance of human exposure to established RF exposure limits based on the evaluation of the electromagnetic fields in the main beam emission of fixed service radio (base) stations when operating in line-of-sight (LoS) using directional parabolic (dish) antennas (e.g. in Point to Point applications). The methodology may be applicable also to other fixed radio stations provided that they use similar directional parabolic antenna type (e.g. for some terminals in Point to Multipoint and Multipoint to Multipoint systems). Fixed radio stations using sector and omni-directional antennas are not in the scope of the present document. Fixed service radio stations in the scope of the present document may use integral/integrated antennas or dedicated antennas, supplied by the same manufacturer, or stand-alone antennas from different manufacturer, but compliant to radio equipment manufacturer specifications; detailed definition of those antenna types are found in ETSI EN 302 217-1 [i.10]. Article 3.1a of the 2014/53/EU Directive [i.1], provides essential requirement for health and safety. Council Recommendation 1999/519/EC [i.2] (for general public) and Directive 2013/35/EU (for workers) gives recommended limits for exposure to electromagnetic fields based on the ICNIRP guidelines [i.6]. Assessment of compliance to article 3.1a of the 2014/53/EU Directive [i.1] of equipment in the scope of the present document and to the requirements defined in the Directive 2013/35/EU [i.3] (for workers) and Council Recommendation 1999/519/EC [i.2] (for general public) may be carried on based on harmonised standards CENELEC EN 50385 [i.9] for placing equipment on the market and CENELEC EN 50401 [i.8] for putting them into service. The present document considers these exposure limits for comparison; calculations and measurements are reported. The guidelines presented may be used for calculation of the compliance boundaries as required by CENELEC EN 50385 [i.9] and CENELEC EN 50401 [i.8]. The simplified assessment method described is derived from measurement and calculation techniques defined in clause 8 of CENELEC EN 62232 [i.7] (see note) and may help in the compliance assessment of the above mentioned fixed service radio stations. Definitions from the above mentioned EN standards are used in the present document where appropriate. NOTE: CENELEC EN 62232 [i.7] considers a very broad types of radio antennas used in Base Stations (including Fixed Radio Stations) and is presently limited to 100 GHz; however, in specific case of parabolic (dish) antennas, the electromagnetic field generation is dominated by purely geometrical factors (related to the D/λ ratio); therefore, the methodology in the present document is considered applicable also to fixed service stations operating at higher frequency up to 300 GHz. The maximum electric field or power density evaluation is based on calculations and measurements performed with the most common configurations and the values are tabulated. The measurement and calculation results on real systems that have been used to establish the method are also provided to give an estimation on the accuracy of the method adopted. |
102 546 | Electromagnetic compatibility and Radio spectrum Matters (ERM); Technical characteristics for Professional Wireless Microphone Systems (PWMS); System Reference Document | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/102500_102599/102546/01.01.01_60/tr_102546v010101p.pdf | The present document describes the necessary technical background information on Audio PMSE equipment operating in various frequency ranges and its intended uses. The present document includes in particular: • Market information. • Technical information, including expected sharing and compatibility issues. • Regulatory issues. |
103 088 | Electromagnetic compatibility and Radio spectrum Matters (ERM); Using the ETSI EN 301 489 series of EMC standards | TR | 1.3.1 | http://www.etsi.org/deliver/etsi_tr/103000_103099/103088/01.03.01_60/tr_103088v010301p.pdf | The present document is intended to provide guidance on the use of the ETSI EN 301 489 series [i.2] of harmonised EMC standards produced by ETSI ERM. Specifically this guidance covers selection of which part that is to be selected for use in conjunction with ETSI EN 301 489-1 [i.2] to provide the necessary requirements to enable the user to demonstrate compliance with article 3.1(b) of the Directive 2014/53/EU [i.37] (RE Directive). The aim of this is to increase consistency of application. In addition the present document also details the differences between the individual versions of each part of the ETSI EN 301 489 series [i.2] to assist the reader in reaching a decision on the impact of the different versions on their particular product. In the interest of maintaining the document as up to date as possible the present document starts with those versions of the ETSI EN 301 489 series [i.2] cited in the Official Journal of the European Union (OJEU) on the 08th June 2017. |
103 181-3 | Short Range Devices (SRD) using Ultra Wide Band (UWB); Part 3: Worldwide UWB regulations between 3,1 and 10,6 GHz | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/103100_103199/10318103/01.01.01_60/tr_10318103v010101p.pdf | The present document presents a summary of the worldwide regulatory situation relating to UWB. NOTE: The present document is a snapshot of the known UWB regulation worldwide in June 2018. The reader is invited to report any changes and additional information on UWB regulations and standards to ETSI. |
103 305-1 | CYBER; Critical Security Controls for Effective Cyber Defence; Part 1: The Critical Security Controls | TR | 2.1.1 | http://www.etsi.org/deliver/etsi_tr/103300_103399/10330501/02.01.01_60/tr_10330501v020101p.pdf | The present document describes a specific set of technical measures available to detect, prevent, respond, and mitigate damage from the most common to the most advanced of cyber-attacks. The measures reflect the combined knowledge of actual attacks and effective defences. The present document is technically equivalent and compatible with CIS Controls®, Version 8.1 of the Center for Internet Security [i.46]. |
105 174-5-1 | Access, Terminals, Transmission and Multiplexing (ATTM); Broadband Deployment - Energy Efficiency and Key Performance Indicators; Part 5: Customer network infrastructures; Sub-part 1: Homes (single-tenant) | TR | 1.1.1 | http://www.etsi.org/deliver/etsi_tr/105100_105199/1051740501/01.01.01_60/tr_1051740501v010101p.pdf | The present document details measures which may be taken to improve the energy efficiency within homes (single-tenant) by virtue of broadband deployment. Clauses 2 and 3 contain references, definitions of terms and abbreviations which relate to this part; similar information will be included in the corresponding clauses of the other parts, thus ensuring that each document can be used on a "stand-alone" basis. Within the present document: • clause 4 describes the nature of customer premises networks in homes (single tenant), defines the interfaces to those networks and identifies the standardization bodies working on the design and installation of those networks; • clause 5 describes the strategies that may be employed within homes (single tenant) to both increase the energy efficiency of installed information technology equipment and to use the facilities offered by information technology services to reduce overall energy consumption. This will enable the proper implementation of services, applications and content on an energy efficient infrastructure, though it is not the goal of this multi-part deliverable to provide detailed standardized solutions for home broadband network architecture. |
181 006 | Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Direct Communication Service in NGN; Service Description [Endorsement of OMA-ERELD-PoC-V1] | TS | 2.1.1 | http://www.etsi.org/deliver/etsi_ts/181000_181099/181006/02.01.01_60/ts_181006v020101p.pdf | The present document defines the requirements for a Direct Communication which may be supported by a TISPAN NGN. These requirements form the basis for the definition of network capabilities. These requirements are an endorsement of the OMA requirements specifications. The present document only provides requirements for IP multimedia based networks. Services provided by a TISPAN NGN to support legacy terminals and interfaces (PSTN/ISDN emulation) are defined in existing PSTN/ISDN documents. Requirements for PSTN/ISDN emulation are out of scope of the present document and are described in other documents. The requirements in the present document are described from the user point of view. The requirements do not take into account capabilities of existing protocols defined for the IMS. The evolution or modifications to these protocols are beyond the scope of the present document. NOTE: The present document uses the term "NGN" only in the context of TISPAN. |
182 012 | Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation Sub-system (PES); Functional architecture | TS | 2.1.4 | http://www.etsi.org/deliver/etsi_ts/182000_182099/182012/02.01.04_60/ts_182012v020104p.pdf | The present document describes an IMS-based functional architecture for the PSTN/ISDN Emulation Subsystem (PES) of the ETSI TISPAN NGN overall architecture. The IMS-based PSTN/ISDN Emulation Subsystem described herein supports the emulation of PSTN services for analog terminals and ISDN services for ISDN terminals and PBXs. These may be connected directly to residential gateways or access gateways, or via V5 access networks. The present document provides a framework for an IMS-based functional architecture and is considered to be a preliminary version. In addition, in order to fulfil the requirements of different operators and national regulatory requirements, this architecture will need to be enhanced. See annex A for a list of potential open areas. |
182 032 | CDN Interconnection Architecture | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/182000_182099/182032/01.01.01_60/ts_182032v010101p.pdf | The present document specifies the architecture and functions of a CDN Interconnection system, implementing the requirements defined in TS 102 990 [1]. |
183 011 | Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN simulation services: Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol specification | TS | 1.4.0 | http://www.etsi.org/deliver/etsi_ts/183000_183099/183011/01.04.00_60/ts_183011v010400p.pdf | The present document specifies the, stage three, Protocol Description of the Anonymous Communication Rejection (ACR) and Communication Barring (CB) simulation service, based on stage one and two of the ISDN supplementary service Anonymous Call Rejection (ACR), Incoming Communication Barring (ICB) and Outgoing Communication Barring (OCB). |
183 048 | Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control System (RACS); Protocol Signalling flows specification; RACS Stage 3 | TS | 1.4.0 | http://www.etsi.org/deliver/etsi_ts/183000_183099/183048/01.04.00_60/ts_183048v010400p.pdf | The scope for the present document is to specify normative rules for how to use the Gq', Rq and Ia protocols (TS 183 017 [4], ES 283 026 [3] and ES 283 018 [7]) as of TISPAN release 1. These rules apply to the interface between: • P-CSCF and SPDF using Gq'; • IBCF and SPDF using Gq'; • SPDF and (C- and I-) BGF using Ia; • SPDF and A-RACF using Rq. In addition, to illustrate the usage of these rules, the present document contains informative signalling flows between the above-listed entities. Non IMS AF entities are out of scope of the present document. Thus, the rules for using the Gq', Rq and Ia protocols and the signalling flows provided do NOT cover possible signalling scenarios for non-IMS applications. They describe however basic principles for how parameters travel via these protocols for IMS, which should be considered when using these protocols for non-IMS AF entities. In case of any discrepancy between the end-to-end IMS signalling flows in the present document and the ETSI TISPAN IMS specifications (TS 182 006 [5] and ES 283 003 [6]), the ETSI TISPAN IMS specification shall take precedence. |
183 060 | Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Subsystem (RACS); Re interface based on the DIAMETER protocol | TS | 3.1.1 | http://www.etsi.org/deliver/etsi_ts/183000_183099/183060/03.01.01_60/ts_183060v030101p.pdf | The present document defines a specification based on DIAMETER for use at the Re Reference Point between the TISPAN NGN Access-Resource Admission Control Function (A-RACF) and the Resource Control Enforcement Function (RCEF). Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of DIAMETER. Where this is not possible, extensions to DIAMETER are defined within the present document. |
185 005 | Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services requirements and capabilities for customer networks connected to TISPAN NGN | TS | 2.0.0 | http://www.etsi.org/deliver/etsi_ts/185000_185099/185005/02.00.00_60/ts_185005v020000p.pdf | The present document specifies the services requirements and capabilities for Customer Premises Networks (CPNs) and Customer Network Gateways (CNG) connected to a TISPAN NGN as defined in TS 181 005 [1]. Characteristics of Customer Network Devices (CNDs) that can be connected to Customer Networks specified in the present document are addressed. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.