hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
314690db30e0da820145d5cd1eef3bc5 | 104 141 | 6.3 Scenario description | Clause 6 pursues the task of planning a bidirectional backhaul connection between two radio sites at a distance of 5,3 km and deployed in a geographical region where rainfall intensities exceed 32 mm/h for 0,01 % of the time in a year (see figure 17 for reference). The expected traffic volume to be transported across t... |
314690db30e0da820145d5cd1eef3bc5 | 104 141 | 6.4 Link planning with known traffic distribution | When an estimate of the cumulative distribution function of the link's target traffic demand is available - such as from the employment of the measurement-based methodology described in clause 5 - the planning procedure should follow the general steps specified in table 6. Table 6: Link planning procedure accordi... |
314690db30e0da820145d5cd1eef3bc5 | 104 141 | 6.5 Link planning with unknown traffic distribution | When the information on the link's target traffic demand distribution is not available, the BTA computation should be based on the conservative but effective approach described in clause 4.3. Table 8 illustrates all the steps needed to plan any backhaul link according to the New KPIs methodology in this case. Table 8: ... |
314690db30e0da820145d5cd1eef3bc5 | 104 141 | 7 Conclusions | Planning backhaul networks through the New KPIs methodology calls for reliable techniques for predicting the traffic demand distributions across the different links, which are essential for accurately evaluating the novel BTA metric. The present document has introduced two complementary solutions to address this challe... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 1 Scope | The present document provides a technical specification for an AI Common Incident Expression Framework for AI Incident Reporting. |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 2 References | |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 3 Definition of terms, symbols and abbreviations | |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 3.1 Terms | For the purposes of the present document, the following terms apply: Additional Data Publication (ADP): set of additional structured information that enriches existing AICIE records AI common incident expression identifier: alphanumeric string that uniquely identifies an AI Incident using the present document AI disast... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 3.2 Symbols | Void. |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AI Artificial Intelligence AICIE AI Common Incident Expression AIID AI Incident Database CSET Center for Security and Emerging Technology CVE Common Vulnerabilities and Exposures DSIT Department for Science, Innovation & Technology (UK) FAS Fe... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 4 Existing Ecosystem | |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 4.1 Cybersecurity information exchange models | The contemporary period of cybersecurity information exchange emerged in the 1990 timeframe and consisted of the exchange of combinations of incident, vulnerability, and threat information via repositories among a complex global community of product and service vendors, end users, and industry and government cyber secu... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 4.2 AI incident information exchange implementations | During the past several years, several well-known, different AI incident repository implementations have emerged that provide different collections with varying record structures to serve a kind of emerging marketplace. See [i.11], [i.25], [i.26], [i.27], [i.28], [i.29] and [i.30]. The implementations lack a common dis... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 4.3 AI Incident information exchange obligations | |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 4.3.1 The exchange obligation ecosystem | AI information exchange obligations arise somewhat autonomously from multiple sources. Organic legislative instruments and implementing regulations by regional and national authorities constitute obligations that incur penalties for non-compliance. See [i.4], [i.5], [i.6] and [i.7]. Government security agency and indus... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 4.3.2 EU Artificial Intelligence Act | One of the most prominent contemporary legislative instruments is the EU Artificial Intelligence Act [i.2]. In five of its Articles, there are provisions that impose the below information sharing obligations. "Art. 17: Quality management system 1. Providers of high-risk AI systems shall put a quality management system ... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 4.3.3 ETSI TS 104 223, UK DSIT Code of Practice | The United Kingdom's National Centre for Cyber Security (NCSC) developed a set of AI best practices [i.3] which were codified into regulator provisions by the regulatory body the Department for Science, Innovation and Technology (DSIT). The provisions were largely transposed into ETSI TS 104 223 [i.1] and contain five ... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 5 AI Common Incident Expression (AICIE) Framework | |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 5.1 The AICIE Framework architecture | The present technical specification facilitates the AI information exchange ecosystem described in Clause 4, above, using a framework that establishes a design architecture for openness, diversity, extensibility, and interoperability among AI reporting communities. This global decentralised, autonomous framework archit... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 5.2 AICIE Framework Resource Record Format and Values | |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 5.2.0 Introduction | The AICIE Framework resource record format is depicted in Figure 5.2-1 and captures the minimum essential information concerning an AI incident reporting resource. Bold field names are mandatory and "…" indicates free-form content. Resources include not only AICIE incident report containers described in other parts of ... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 5.2.1 AICIEverison | This required value describes the AICIE Framework Resource Record specification version being used and expressed as three numbers separated by periods and set initially to 1.0.0. ETSI ETSI TS 104 158-1 V1.1.1 (2026-03) 14 |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 5.2.2 AICIEresourcetype | This required value describes the AI incident reporting resource type in the following non-case-sensitive enumeration: Table 5.2.2-1 list Another AICIE Framework Resource list directory based on the present document spec Any technical specification for AI incident information reporting repository Any repository for AI ... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 5.2.3 AICIEresourcename | This required value describes the name of the resource without any constraints - prefaced by any related identifier associated with the name. EXAMPLE: "ETSI TS 104 158-1 V1.1.1, Securing Artificial Intelligence (SAI); AI Incident Reporting; Part 1: AI Common Incident Expression (AICIE) Global Framework". |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 5.2.4 AICIEresourceaddress | This required value describes the resource address location without any constraints - preferably as a persistent, precise, accessible Uniform Resource Identifier (URI) or a link capable of providing the resource. EXAMPLE: https://www.etsi.org/deliver/etsi_ts/104100_104199/10415801. |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 5.2.5 AICIEresourcecontact | This required value describes the contact information without any constraints for the entity maintaining and accessing the resource preferably including physical and location and useable email address. EXAMPLE: "ETSI Secretariat, ETSI 650, Route des Lucioles 06560 Valbonne - Sophia Antipolis FRANCE, secretariat@etsi.or... |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 5.2.6 AICIEresourceaccess | This optional value without any constraints describes any resource access controls. EXAMPLE: "Members only". The default when leaving blank is publicly available without constraints. |
ab240e5dec472d4fd2871b8208bf1154 | 104 158-1 | 5.2.7 AICIEresourceadd | This optional value without any constraints describes any useful additional attributes of the resource. ETSI ETSI TS 104 158-1 V1.1.1 (2026-03) 15 Annex A (normative): AICIE Framework Resource Record JSON Format V1.0.1 { "$schema": "tbd", "$id": "tbd2", "properties": { "AICIEversion": { "description": "AICIE Framework ... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 1 Scope | 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 d... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 2 References | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.5], IETF RFC 9052 [2] and the following apply: byte string: sequence of octets (8 bits) CB-AdES signature: COSE signature meeting the requirements specified in this or other parts of the present multi-part document CBOR-bstr-wrapped: CBOR o... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 3.2 Symbols | Void. |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASCII American Standard Code For Information Interchange ASN.1 Abstract Syntax Notation 1 bstr byte string CA Certification Authority CBOR Concise Binary Object Representation CDDL Concise Data Definition Language COSE CBOR Object Signing and ... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 3.4 Terminology | The present document adopts, wherever it is possible the same terminology as the terminology used in IETF RFC 9052 [2]. Therefore, within the present document, the term "COSE Signature" shall denote the CBOR structure for digital signatures specified in IETF RFC 9052 [2]. The present document uses the term "CBOR data i... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 4 General Requirements | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 4.1 CDDL definitions | The present document defines the new types and components for CB-AdES signatures using the Concise Data Definition Language (CDDL) [5]. |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 4.2 Requirements on CB-AdES supporting COSE structures | CB-AdES signatures specified in the present document may be built on both types of COSE signature structures specified in IETF RFC 9052 [2], namely: COSE_Sign for multiple signers of the same COSE Payload (specified in clause 4.1 of IETF RFC 9052 [2]), and COSE_Sign1 for one single signer (specified in clause 4.2 of IE... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 4.3 Requirements on CB-AdES encoding | CB-AdES signatures specified in the present document may be encoded as untagged (COSE_Sign and COSE_Sign1) or tagged, namely COSE_Sign_Tagged (specified in clause 4.1 of IETF RFC 9052 [2]), and COSE_Sign1_Tagged (specified in clause 4.2 of IETF RFC 9052 [2]). |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 4.4 Requirements on CB-AdES headers | The unprotected headers map in CB-AdES signatures (regardless they are within the body layer or the signer layer) shall contain only one member, namely the uHeaders header parameter (specified in clause 5.3 of the present document), which is defined as a CBOR array. NOTE 1: The rationale for this is that the unprotecte... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 4.5 Requirements on Payload | In CB-AdES signatures, the COSE Payload may be attached or detached. Detached COSE Payload may either be one detached object, or result from the concatenation of more than one detached data objects. See the specification of sigD signed header parameter in clause 5.2.8 of the present document. |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 4.6 Requirements on map keys and data tags | The present document specifies new CBOR types with the following criteria: • The keys of the CBOR maps pairs shall be integers. • Tags for new CBOR tagged data items shall also be integers. |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 4.7 Requirements on encapsulation in CBOR byte strings | The present document requires to encapsulate CBOR components in CBOR byte strings. This encapsulation shall be performed using the CBOR encoding restrictions defined in clause 9 of IETF RFC 9052 [2]. |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5 Header parameters semantics and syntax | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.1 Header parameters defined by IETF | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.1.1 Introduction | This clause defines additional requirements for the use of some of header parameters specified by IETF. ETSI ETSI TS 119 152-1 V1.1.1 (2026-03) 14 NOTE: Clause 6.3 specifies requirements (mainly of presence and cardinality), for the use of some of the header parameters specified by IETF for CB-AdES baseline signatures. |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.1.2 The alg (algorithm) header parameter | Semantics The alg header parameter shall be a signed header parameter that qualifies the signature. The alg header parameter shall have the semantics specified in IETF RFC 9052 [2], clause 3.1. Syntax The alg header parameter shall have the syntax specified in IETF RFC 9052 [2], clause 3.1. Its value should be one of t... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.1.3 The content type (content type) header parameter | Semantics The content type header parameter shall be a signed header parameter that qualifies the COSE Payload. The content type header parameter shall have the semantics specified in IETF RFC 9052 [2], clause 3.1. The content type header parameter shall not be present if the sigD header parameter, specified in clause ... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.1.4 The kid (key identifier) header parameter | Semantics The kid header parameter shall be a signed header parameter that qualifies the signature. The kid header parameter shall have the semantics specified in IETF RFC 9052 [2], clause 3.1. The content of kid header parameter should be the DER-encoded instance of type IssuerSerial type defined in IETF RFC 5035 [10]... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.1.5 The x5u (X.509 URL) header parameter | Semantics The x5u header parameter shall be a signed header parameter that qualifies the signature. The x5u header parameter shall have the semantics specified in IETF RFC 9360 [3], clause 2. The x5u member shall be used as a hint, as implementations can have alternative ways for retrieving the referenced certificate i... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.1.6 The CBOR component for counter signatures | Semantics The CBOR component for including one or more counter signatures shall be an element of the uHeaders member of the unprotected headers map (see clause 5.3.1 of the present member for the specification of uHeaders member). The element of the uHeaders member of the unprotected headers map used for including one ... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.1.7 The x5t (cert hash) header parameter | Semantics The x5t header parameter shall have the semantics specified in IETF RFC 9360 [3], clause 2. Syntax The x5t header parameter shall have the syntax of COSE_CertHash type, specified in IETF RFC 9360 [3], clause 2. COSE_CertHash = [ hashAlg: (int / tstr), hashValue: bstr ] ETSI ETSI TS 119 152-1 V1.1.1 (2026-03) ... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.1.8 The x5chain (X.509 chain) header parameter | Semantics The x5chain header parameter may be a signed or unsigned header parameter that qualifies the signature. If x5chain has not to be signed, it shall be included within the uHeaders CBOR array specified in clause 5.3.1 of the present document. NOTE: This is for meeting requirements appearing in use cases that req... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.1.9 The iat (issued at) header parameter | Semantics The iat header parameter may be a signed or unsigned header parameter that qualifies the signature. The iat header parameter shall have the semantics specified in clause 3.1.6 of IETF RFC 8392 [18]. The iat header parameter's value shall specify the time at which the signer claims to have performed the signin... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.1.10 The crit (critical) header parameter | Semantics ETSI ETSI TS 119 152-1 V1.1.1 (2026-03) 17 The crit header parameter shall be a signed header parameter that qualifies the signature. The crit header parameter shall have the semantics specified in IETF RFC 9052 [2], clause 3.1. Syntax The crit header parameter shall have the syntax specified in IETF RFC 9052... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2 New signed header parameters | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.1 Labels and tags of the signed header parameters | Clause 5.2 specifies a number of signed header parameters. All of them shall be part of the protected headers map when present. All of them shall be identified by a label in the corresponding CBOR map that shall be an integer. Table 1 below defines the labels associated to each signed header parameter and the tags iden... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.2 The x5ts (X.509 certificates Thumbprints) header parameter | Semantics The x5ts header parameter shall be a signed header parameter that qualifies the signature. Its label shall be 261. ETSI ETSI TS 119 152-1 V1.1.1 (2026-03) 18 The x5ts header parameter shall contain several references of certificates within the certification path of the signing certificate, each one formed by ... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.3 The srCms (signer commitments) header parameter | Semantics The srCms header parameter shall be a signed header parameter that qualifies the COSE Payload. Its label shall be 262. The srCms header parameter shall indicate the commitment made by the signer when signing. The srCms header parameter shall express the commitment type with a URI. The srCms header parameter m... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.4 The sigPl (signature production place) header parameter | Semantics The sigPl header parameter shall be a signed header parameter that qualifies the signer. Its label shall be 263. The sigPl header parameter shall specify an address associated with the signer at a particular geographical (e.g. city) location. Syntax Below follows the CDDL definition of the sigPl header parame... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.5 The srAts (signer attributes) header parameter | Semantics The srAts header parameter shall be a signed header parameter that qualifies the signer. Its label shall be 264. The srAts header parameter shall encapsulate signer attributes (e.g. role). This header parameter may encapsulate the following types of attributes: • attributes claimed by the signer; • attributes... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.6 The adoTst (COSE payload time-stamp) header parameter | Semantics The adoTst header parameter shall be a signed header parameter that qualifies the COSE Payload. Its label shall be 265. The adoTst header parameter shall encapsulate one or more electronic time-stamps, generated before the signature production, whose message imprint computation input shall be the COSE Payload... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.7 The sigPId (signature policy identifier) header parameter | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.7.1 Semantics and syntax | Semantics The sigPId header parameter shall be a signed header parameter qualifying the signature. Its label shall be 266. The sigPId header parameter shall contain an explicit identifier of a signature policy. NOTE: ETSI TS 119 172-1 [i.7] specifies a framework for signature policies. Syntax Below follows the CDDL def... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.7.2 Signature policy qualifiers | Semantics This clause specifies three qualifiers for the signature policy. Each qualifier shall be a CBOR tagged data item. The present document defines the following qualifiers and tags: • A URL where a copy of the signature policy document can be obtained (spURI choice). Its tag shall be 1. • A user notice that shoul... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.8 The sigD header parameter | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.8.1 Semantics and Syntax | Semantics The sigD header parameter shall be a signed header parameter. Its label shall be 267. The sigD header parameter shall not appear in CB-AdES signatures whose COSE Payload is attached. The sigD header parameter may appear in CB-AdES signatures whose COSE Payload is detached. A CB-AdES signature shall have at mo... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.8.2 Mechanisms supported by URI-references | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.8.2.1 General requirements | This clause specifies two mechanisms that use URI-references for referencing the data objects contributing to build the COSE Payload. For these referencing mechanisms, the contents of the pars member shall be an array of strings. Each string shall be an URI-reference, which, once resolved, shall result in an URI appert... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.8.2.2 Mechanism ObjectIdByURI | The URL identifying this referencing mechanism shall be "http://uri.etsi.org/19152/ObjectIdByURI". For this referencing mechanism, neither hashV, nor hashM shall be present. Member ctys may be present. The semantics and syntax of each element of array ctys shall be as specified in clause 5.2.8.1 of the present document... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.2.8.2.3 Mechanism ObjectIdByURIHash | The URL identifying this referencing mechanism shall be "http://uri.etsi.org/19152/ObjectIdByURIHash". For this referencing mechanism, the hashV, and the hashM members shall be present. Member ctys may be present. The semantics and syntax of hashM, hashV, and ctys shall be as specified in clause 5.2.8.1 of the present ... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.3 New unsigned header parameter | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.3.1 The uHeaders header parameter | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.3.1.1 Semantics and syntax | Semantics The uHeaders parameter, member of the unprotected headers map, shall be a CBOR array whose elements contain CBOR values that are not signed by the CB-AdES signature. ETSI ETSI TS 119 152-1 V1.1.1 (2026-03) 28 NOTE 1: The rationale for this is as follows: to allow validating CB-AdES signatures long after they ... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.3.2 The sigPSt CBOR map | Semantics The sigPSt CBOR map shall contain either: • the signature policy document which is referenced in the sigPId CBOR map so that the signature policy document can be used for offline and long-term validation; or • a URI referencing a local store where the signature policy document can be retrieved. Syntax Below f... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.3.3 The sigTst CBOR map | Semantics The sigTst CBOR map shall encapsulate one or more electronic time-stamps time-stamping the COSE signature value. Syntax Below follows the CDDL definition of the sigTst header parameter: sigTst = tstContainer The input of the message imprint computation for the time-stamp tokens encapsulated by sigTst CBOR map... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.3.4 The valData CBOR map | Semantics The valData CBOR map shall contain the certificates identified in 1) below, or the revocation data identified in 2) below, or both of them: 1) Certificate values that are used for validating any digital signature present within any component of the CB-AdES signature regardless the objects that they are signin... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.3.5 The arcTst CBOR map | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.3.5.1 Semantics and syntax | Semantics The arcTst CBOR map shall encapsulate electronic time-stamps computed on the COSE Payload, the protected headers map or maps (depending on the used signature structure), the COSE signature value, the externally supplied data, when present, and the uHeaders CBOR array within the unprotected headers map at the ... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.3.5.2 Generation and incorporation of arcTst | The steps listed below shall be performed for augmenting a CB-AdES signature by incorporation of a new arcTst CBOR map: 1) If the CB-AdES signature misses certificates and/or revocation data required for validating the signed objects present in the CB-AdES signature, then these missing certificates and/or revocation da... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.3.5.3 Computation of message-imprint for arcTst | For computing the input to the message imprint computation, indicated in step 2) in clause 5.3.5.2, the steps listed below shall be performed: 1) Initialize an empty CBOR array. 2) Add a context text string, whose value shall be either: - "Signature", if the CB-AdES signature is built on the COSE_Sign structure defined... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.4 Generally useful syntax | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.4.1 The obId data type | Semantics Instances of obId data type shall contain a unique and permanent identifier of one data object. Instances of obId data type may contain a textual description of the nature of the data object qualified by the instance of the obId data type. Instances of obId data type may contain a number of references to docu... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.4.2 The pkiOb data type | Semantics The pkiOb data type shall be used to incorporate PKI objects, which can be non-CBOR encoded, into the CB-AdES signature. NOTE: Examples of such PKI objects, include X.509 certificates and revocation lists, OCSP responses, attribute certificates, and electronic time-stamps. Syntax Below follows the CDDL defini... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.4.3 Container for electronic time-stamps | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.4.3.1 Introduction | The present document specifies CBOR maps that act as electronic time-stamps containers. Electronic time-stamps within the aforementioned containers may time-stamp isolated components or concatenations of several components of CB-AdES signatures. This clause specifies a CBOR type for containers of electronic time-stamps... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.4.3.2 Containers for electronic time-stamps | Below follows the list of the electronic time-stamps containers that are defined by the present document: • Container for electronic time-stamps proving that the COSE Payload has been created before certain time instant: adoTst (specified in clause 5.2.6 of the present document). • Container for electronic time-stamps ... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 5.4.3.3 The tstContainer type | Semantics The tstContainer type shall: • allow encapsulating IETF RFC 3161 [12] electronic time-stamps as well as electronic time-stamps in other formats; • provide means for managing electronic time-stamps computed on a concatenation of CB-AdES components (including detached COSE Payload); and • allow encapsulating mo... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 6 CB-AdES baseline signatures | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 6.1 Signature levels | Clause 6 defines four levels of CB-AdES baseline signatures, intended to facilitate interoperability and to encompass the life cycle of CB-AdES signature, namely: a) B-B level provides requirements for the incorporation of signed header parameters and some unsigned components within the uHeaders unsigned header paramet... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 6.2 General requirements | |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 6.2.1 Algorithm requirements | The algorithms and key lengths used to generate and augment digital signatures should be as specified in ETSI TS 119 312 [19]. NOTE: Cryptographic suites recommendations defined in ETSI TS 119 312 [19] can be superseded by national recommendations. In addition, MD5 algorithm shall not be used as digest algorithm. |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 6.2.2 Notation for requirements | The present clause describes the notation used for defining the requirements of the different CB-AdES signature levels. ETSI ETSI TS 119 152-1 V1.1.1 (2026-03) 39 The requirements on the header parameters and certain other signature's components for each CB-AdES signature level are expressed in Table 14. A row in the t... |
cfeb51771f38af3290d7c4a899c0aa1d | 119 152-1 | 6.3 Requirements on CB-AdES components and services | The four CB-AdES signature levels specified in the present clause shall be built as specified in clause 4 of the present document. Table 14 shows the presence and cardinality requirements on the signature header parameters, other components, and services indicated in the first column for the four CB-AdES baseline signa... |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 1 Scope | The present document provides a technical specification for an AI Common Incident Expression Common Container for AI Incident Reporting. |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 2 References | |
0a808127317d3d44e01c46e3e2ee7e33 | 104 158-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.