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 |
|---|---|---|---|---|---|
103 097 | Intelligent Transport Systems (ITS); Security; Security header and certificate formats; Release 2 | TS | 2.2.1 | http://www.etsi.org/deliver/etsi_ts/103000_103099/103097/02.02.01_60/ts_103097v020201p.pdf | The present document specifies the secure data structure including header and certificate formats for Intelligent Transport Systems. In addition to supporting the use of explicit certificates, the present document includes the amendment for the use of implicit certificates. As such, the present document is backwards compatible for the sender of secure data structures, but implies the additional implementation of implicit certificates on receiver side in order to support interoperability. NOTE 1: The use of explicit certificates is allowed in previous versions (V1.3.1 and V1.4.1) of the present document. NOTE 2: The use of implicit certificates is not allowed in previous versions of the present document. |
104 158-1 | Securing Artificial Intelligence (SAI); AI Incident Reporting; Part 1: AI Common Incident Expression (AICIE) Global Framework | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/104100_104199/10415801/01.01.01_60/ts_10415801v010101p.pdf | The present document provides a technical specification for an AI Common Incident Expression Framework for AI Incident Reporting. |
119 472-2 | Electronic Signatures and Trust Infrastructures (ESI); Profiles for Electronic Attestation of Attributes; Part 2: Profiles for EAA/PID Presentations to Relying Party | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/11947202/01.02.01_60/ts_11947202v010201p.pdf | The present document: 1) Specifies three (3) realizations for Presentations of Electronic Attestation of Attributes (EAAP hereinafter) built on the realizations of Electronic Attestation of Attributes (EAA hereinafter), specified in ETSI TS 119 472-1 [5] namely: - SD-JWT VC EAAP (clause 4.1); - ISO/IEC-mdoc EAAP (clause 4.2); and - JSON-LD W3C VC EAAP (Annex A). NOTE 1: The realization of X509-AC EAAP will be added in the next version of the present document. 2) Specifies two (2) profiles of protocols for allowing Relying Parties (RP hereinafter) to request EAAPs or Personal Identification Data (PID hereinafter) to the EUDI Wallet, and the EUDI Wallet to send the requested EAAPs/PIDs to the RP. One of the profiles supports two transmission mechanisms, namely: API-mediated and non-API mediated. The other profile only supports the non-API mediated transmission mechanisms, as shown below: a) A profile is built on ISO/IEC 18013-5 [10] for non-API mediated transmission mechanism only. This profile is named ISO/IEC-mdoc profile and it is defined in clause 5 of the present document. b) A profile is built on OpenID4VC-HAIP [11] for both API-mediated and non-API mediated transmission mechanisms, as follows: Sections 5, 5.1, 5.3, 7, and 8 of [11] for transmission via Redirects or non-API mediated transmission mechanism; and Sections 5, 5.2, 5.3, 7, and 8 of [11] for API mediated transmission mechanism. This profile is named OpenID4VC-HAIP profile and it is defined in clause 6 of the present document. NOTE 2: The protocols for requesting and retrieving EAAPs/PIDs defined in OpenID4VC-HAIP [11] are profiles based on OpenID4 VP [7]. |
103 874-2 | DECT-2020 New Radio (NR); Access Profile; Part 2: Smart Metering, City and Buildings Release 2 | TS | 2.1.1 | http://www.etsi.org/deliver/etsi_ts/103800_103899/10387402/02.01.01_60/ts_10387402v020101p.pdf | The present document specifies the access profile requirements and recommendations of smart metering, city and buildings as well as any other similarly applicable use case for the DECT-2020 New Radio (NR). |
119 475 | Electronic Signatures and Trust Infrastructures (ESI); Relying party attributes supporting EUDI Wallet user's authorization decisions | TS | 1.2.1 | http://www.etsi.org/deliver/etsi_ts/119400_119499/119475/01.02.01_60/ts_119475v010201p.pdf | The present document specifies requirements for the use of certificate-based attestations that support the identification and authorization of wallet-relying parties when interacting with the European Digital Identity Wallet (EUDIW), in accordance with eIDAS Regulation (EU) No 910/2014 [i.1], and Commission Implementing Regulation (EU) 2025/848 [i.2]. Specifically, the present document defines: 1) policy and profile requirements for wallet-relying party registration certificates used to convey the authorizations, entitlements, and intended purposes of wallet-relying parties, as well as the types of attributes they are authorized to request from wallet users; 2) guidance for the inclusion and mapping of wallet-relying party information, such as entitlements, identifiers in both certificates; 3) recommendations for coordination between providers of WRPRC and WRPAC. The specification builds upon existing ETSI standards including ETSI EN 319 411-1 [4], ETSI EN 319 412-1 [1], ETSI EN 319 412-2 [2], ETSI EN 319 412-3 [3], and complements the legal framework established under eIDAS for trust service provision, digital identity, and wallet interoperability. The present document does not define requirements for the design, implementation, or internal operation of the European Digital Identity Wallet itself, in particular it is assumed that attributes in registration certificates are confirmed by the register. |
119 152-1 | Electronic Signatures and Trust Infrastructures (ESI); CB AdES (CBOR-AdES) digital signatures; Part 1: Building blocks and CB-AdES baseline signatures | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/119100_119199/11915201/01.01.01_60/ts_11915201v010101p.pdf | The present document: 1) Specifies a CBOR [1] format for AdES signatures (CB-AdES signatures hereinafter) built on CBOR Object Signing and Encryption (COSE hereinafter) as specified in IETF RFC 9052 [2]. For this, the present document: - Extends the CBOR Object Signing and Encryption specified in IETF RFC 9052 [2] by defining an additional set of CBOR header parameters that can be incorporated in the COSE Headers (either in its protected headers map or its unprotected headers map). Many of these new header parameters have the same semantics as the attributes/properties defined in CAdES [i.2], XAdES [8], and JAdES [9] digital signatures. Other header parameters are defined to meet specific requirements that current COSE cannot meet (e.g. for explicitly referencing detached payload). These new header parameters and their corresponding types are defined in CDDL, which is specified in IETF RFC 8610 [5]. - Specifies the mechanisms for incorporating the aforementioned CBOR components in COSE [2] to build CB-AdES signatures, offering the same features as CAdES, XAdES, and JAdES in CBOR syntax, and therefore fulfilling the same requirements (such as the long-term validity of digital signatures). 2) Defines four levels of CB-AdES baseline signatures addressing incremental requirements to maintain the validity of the signatures over the long term. Each level requires the presence of certain CB-AdES 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. NOTE 1: ETSI EN 319 102-1 [i.3] specifies procedures for creation, augmentation and validation of other types of AdES digital signatures. Procedures for creation, augmentation, and validation of CB-AdES digital signatures are out of scope. 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 CB-AdES 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]. |
103 982 | Publicly Available Specification (PAS); O-RAN Architecture Description (O-RAN.WG1.TS.OAD-R004 - v14.00) | TS | 14.0.0 | http://www.etsi.org/deliver/etsi_ts/103900_103999/103982/14.00.00_60/ts_103982v140000p.pdf | The present document: • specifies the overall architecture of O-RAN; • describes the O-RAN architecture elements and relevant interfaces that connect them. |
104 158-2 | Securing Artificial Intelligence (SAI); AI Incident Reporting; Part 2: AI Common Incident Expression (AICIE) Common Container | TS | 1.1.1 | http://www.etsi.org/deliver/etsi_ts/104100_104199/10415802/01.01.01_60/ts_10415802v010101p.pdf | The present document provides a technical specification for an AI Common Incident Expression Common Container for AI Incident Reporting. |
103 481 | Smart Cards; Test specification for the Remote APDU structure for UICC based applications; UICC features (Release 16) | TS | 16.5.0 | http://www.etsi.org/deliver/etsi_ts/103400_103499/103481/16.05.00_60/ts_103481v160500p.pdf | The present document covers the minimum characteristics considered necessary for the UICC in order to provide compliance to ETSI TS 102 226 [1]. It specifies conformance test cases for the UICC relating to Remote APDU structure for UICC based applications as specified in ETSI TS 102 226 [1]. |
103 903 | Intelligent Transport Systems (ITS); Framework; Basic principles; Release 2 | TR | 2.1.1 | http://www.etsi.org/deliver/etsi_tr/103900_103999/103903/02.01.01_60/tr_103903v020101p.pdf | The present document identifies the ITS domain and its elements. It provides the ITS architectural and ecosystem context. The present document complements and extends the ETSI drafting rules [i.3] and identifies consistency aspects related to the protocol stack layering and referencing between the ITS specifications and other documents. Further, it provides the ETSI ITS deliverable structure. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.