hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
08752d782f34fc3424740df1e49ff117 | 119 312 | 9.3 Time period resistance for signer's key | NOTE 1: The focus is very often placed on the resistance of signer's keys. Signer's keys shall remain suitable during the certificate maintenance period (commonly called validity period from notBefore to notAfter) of the associated certificate. NOTE 2: If they become weak due to progress in cryptographic research, revo... |
08752d782f34fc3424740df1e49ff117 | 119 312 | 9.4 Time period resistance for trust anchors | A trust anchor shall remain secure during the whole time period during which advanced electronic signature ETSI TS 101 733 [i.6], ETSI TS 101 903 [i.7], ETSI TS 102 778 [i.8], ETSI EN 319 122 [i.17], ETSI EN 319 132 [i.18] and ETSI EN 319 142 [i.19] needs to be verified. ETSI ETSI TS 119 312 V1.4.3 (2023-08) 18 NOTE 1:... |
08752d782f34fc3424740df1e49ff117 | 119 312 | 9.5 Time period resistance for other keys | All other keys (TSU keys, CA keys, CRL issuer keys, OCSP responder keys) should resist during the validity period of the associated certificate and the certificates that rely on its validity. Their security parameters shall then be chosen at least as strong as the corresponding parameters of the certified keys. If they... |
08752d782f34fc3424740df1e49ff117 | 119 312 | 10.1 General | Hash functions and signatures algorithms shall be referenced using an OID and/or a URN. NOTE 1: Only the owner of the OID or the URN is allowed to define its meaning and thus the meaning of the algorithm, usually referencing another document. NOTE 2: If such an OID/URN is not available the algorithm is unusable. 10.2 H... |
08752d782f34fc3424740df1e49ff117 | 119 312 | 10.2.1 Introduction | NOTE: All listed here OID can be found in the OID repository http://oid-info.com [i.13]. For example one gets the OID assigned for EC-SDSA in the optimized version by http://oid-info.com/get/1.0.14888.3.0.13. ETSI ETSI TS 119 312 V1.4.3 (2023-08) 19 |
08752d782f34fc3424740df1e49ff117 | 119 312 | 10.2.2 Hash functions | The hash functions shall be identified using the OIDs in table 11. Table 11 Short object name OID References id-sha224 { joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101) csor(3) nistalgorithm(4) hashalgs(2) 4 } IETF RFC 4055 [8] id-sha256 { joint-iso-itu-t(2) country(16) us(840) organization(1) gov(101) ... |
08752d782f34fc3424740df1e49ff117 | 119 312 | 10.2.3 Elliptic curves | The signature algorithms shall be identified using the OIDs in table 12. Table 12 Short object name OID References FRP256v1 {iso(1) member-body(2) fr(250) type-org(1) 223 101 256 1} ANSSI [i.16] brainpoolP256r1 {iso(1) identified-organization(3) teletrust(36) algorithm(3) signatureAlgorithm(3) ecSign(2) ecStdCurvesAndG... |
08752d782f34fc3424740df1e49ff117 | 119 312 | 10.2.4 Signature algorithms | The signature algorithms shall be identified using the OIDs in table 13. Table 13 Short object name OID References rsaEncryption { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 1 } IETF RFC 3279 [7] id-dsa { iso(1) member-body(2) us(840) x9-57(10040) x9cm(4) 1 } IETF RFC 3279 [7] id-ecPublicKey { iso(1... |
08752d782f34fc3424740df1e49ff117 | 119 312 | 10.2.5 Signature suites | The signature suites shall be identified using the OIDs in table 14. ETSI ETSI TS 119 312 V1.4.3 (2023-08) 20 Table 14 Short object name OID References sha256WithRSAEncryption { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-1(1) 11 } IETF RFC 4055 [8] sha512WithRSAEncryption { iso(1) member-body(2) us(840) ... |
08752d782f34fc3424740df1e49ff117 | 119 312 | 10.3.1 Hash functions | The hash functions shall be identified using the URIs in table 15. Table 15 Short object name URI References sha224 http://www.w3.org/2001/04/xmldsig-more#sha224 IETF RFC 6931 [10] sha256 http://www.w3.org/2001/04/xmlenc#sha256 W3C® Recommendation XML Encryption Syntax and Processing, April 2013 [11] sha384 http://www.... |
08752d782f34fc3424740df1e49ff117 | 119 312 | 10.3.2 Signature algorithms | NOTE: There is no need to define such URIs since XadES uses the signature algorithms contained in X.509 certificates which are referenced using OIDs. ETSI ETSI TS 119 312 V1.4.3 (2023-08) 21 |
08752d782f34fc3424740df1e49ff117 | 119 312 | 10.3.3 Signature suites | The signature suites shall be identified using the URIs in table 16. Table 16 Short object name URI References rsa-sha256 http://www.w3.org/2001/04/xmldsig-more#rsa-sha256 IETF RFC 6931 [10] rsa-sha384 http://www.w3.org/2001/04/xmldsig-more#rsa-sha384 IETF RFC 6931 [10] rsa-sha512 http://www.w3.org/2001/04/xmldsig-more... |
879a725570519f02de8c9581298981b7 | 118 140 | 1 Scope | The present document specifies the oneM2M and Modbus interworking technologies that enable Modbus devices and oneM2M entities produce/consume services. Clause 5 defines the interworking architecture model that describes where the Modbus IPE is hosted and how the IPE is composed with. Clause 6 defines the architecture a... |
879a725570519f02de8c9581298981b7 | 118 140 | 2 References | |
879a725570519f02de8c9581298981b7 | 118 140 | 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 reference document (including any amendments) applies. Referenced documents which ar... |
879a725570519f02de8c9581298981b7 | 118 140 | 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 reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
879a725570519f02de8c9581298981b7 | 118 140 | 3 Definition of terms, symbols and abbreviations | |
879a725570519f02de8c9581298981b7 | 118 140 | 3.1 Terms | For the purposes of the present document, the following terms apply: Modbus Master: software running on a computer or a server as a host to access Modbus Slaves by issuing unicast requests Modbus Slave/Device: peripheral device that provides a Modbus interface and responds by supplying the requested data to the master,... |
879a725570519f02de8c9581298981b7 | 118 140 | 3.2 Symbols | Void. |
879a725570519f02de8c9581298981b7 | 118 140 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADU Application Data Unit AE Application Entity ASCII American Standard Code for Information Interchange ASN/MN Application Service Node/Middle Node CSE Common Services Entity CSV Comma-Separated Values HDLC High-level Data Link Control I/O In... |
879a725570519f02de8c9581298981b7 | 118 140 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in the present document are to be interpreted as described in the oneM2M Drafting Rules [i.1]. ETSI ETSI TS 118 140 V4.0.0 (2022-09) 7 oneM2M TS-0040 version 4.0.0 Release 4 |
879a725570519f02de8c9581298981b7 | 118 140 | 5 Architecture Model | |
879a725570519f02de8c9581298981b7 | 118 140 | 5.1 Reference model | The architecture model followed in the present document is based on the architecture model in ETSI TS 118 101 [1] that describes how interworking between oneM2M CSEs and non-oneM2M systems using specialized Interworking Proxy application Entities (IPEs). The present document describes the Modbus IPE that supports the f... |
879a725570519f02de8c9581298981b7 | 118 140 | 5.2 Composition of the IPE | As shown in Figure 5.2-1, the Modbus IPE consists of AE and Modbus Master [i.2]. To provide the interworking functions to other oneM2M entities, the IPE shall register to a CSE and communicate with Modbus devices using Modbus protocol. The IPE registration is mandatory in oneM2M systems. Modbus discovery and session es... |
879a725570519f02de8c9581298981b7 | 118 140 | 6 Architecture Aspects | |
879a725570519f02de8c9581298981b7 | 118 140 | 6.1 Introduction | The present document specifies the functions for Modbus interworking in the following aspects: • oneM2M resource mapping structure; • Modbus IPE registration; • Modbus service mapping; • Modbus interworking procedures. |
879a725570519f02de8c9581298981b7 | 118 140 | 6.2 oneM2M resource mapping structure | |
879a725570519f02de8c9581298981b7 | 118 140 | 6.2.1 Introduction | In this clause, the overall resource mapping structure for exposing services between Modbus devices and oneM2M entities is introduced. Firstly, Modbus devices are modelled according to the oneM2M SDT described in ETSI TS 118 123 [3]. The oneM2M SDT offers a generic and flexible modeling structure for describing functio... |
879a725570519f02de8c9581298981b7 | 118 140 | 6.2.2 Mapping Modbus devices into SDT schemas | Each Modbus device shall be modelled as a Device component. The Modules of the Device shall be created according to the functionality of the Modbus device as defined in ETSI TS 118 123 [3]. For representing data objects of a Modbus device, the mapping between a Modbus device's registers [i.2], [i.3] and SDT DataPoints ... |
879a725570519f02de8c9581298981b7 | 118 140 | 6.2.3 Mapping SDT schemas into oneM2M resources | The mapping of all SDT components follows the mapping procedure defined in clause 6.2 of ETSI TS 118 123 [3]. For example, the ModuleClass models shall be mapped to the specializations of <flexContainer> resource and their DataPoints to customAttributes of the corresponding <flexContainer> specializations. However, the... |
879a725570519f02de8c9581298981b7 | 118 140 | 6.3 Modbus IPE registration | Figure 6.3-1 shows the device registration call flow: 1) The IPE shall request to create an <AE> resource on the Hosting CSE to register the Modbus master collocated on the IPE. 2) The Hosting CSE shall evaluate the request, performs the appropriate checks, and creates the <AE> resource. The Hosting CSE shall respond w... |
879a725570519f02de8c9581298981b7 | 118 140 | 6.4 Modbus service mapping | The Modbus devices can accept either read or write requests from the Master. The operation to be executed is identified from the function code of a Modbus message. Therefore, the IPE needs to be able to map the oneM2M messages to Modbus messages with the appropriate function code. The function code is identified from r... |
879a725570519f02de8c9581298981b7 | 118 140 | 6.5 Modbus interworking procedures | |
879a725570519f02de8c9581298981b7 | 118 140 | 6.5.1 Retrieve data from a Modbus device | Suppose a scenario when current readings of a Modbus device need to be displayed at an AE application and Modbus- IPE continuously monitors a Modbus device and uploads that data to a CSE hosted on a server in the network. Initially, the AE shall be subscribed to the <flexContainer> resource, which is a specialization o... |
879a725570519f02de8c9581298981b7 | 118 140 | 6.5.2 Write data to a Modbus device | Suppose a scenario when it is required to update some value in a Modbus device through an AE application registered to a CSE. Initially, the Modbus IPE shall be subscribed to the <flexContainer> resource, which is a specialization of some SDT module for a Modbus device, using a blocking type of <subscription> resource ... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 1 Scope | The present document defines general guidelines when interworking between external Proximal IoT technologies which are not aware of oneM2M-defined functionality, and the oneM2M system (i.e. the interaction between non-oneM2M- aware devices, gateways or applications (non-oneM2M entities) and oneM2M-defined entities). In... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 2 References | |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 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. The following referenced doc... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 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. The following referenced doc... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 3 Definition of terms, symbols and abbreviations | |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [1], ETSI TS 118 102 [7] and the following apply: NOTE: A term defined in the present document takes precedence over the definition of the same term, if any, in ETSI TS 118 111 [1] and ETSI TS 118 101 [2]. proximal IoT: IoT components communic... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 3.2 Symbols | Void. |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 118 111 [1] and the following apply: IoT Internet of Things |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 4 Conventions | The key words "Shall", "Shall not", "May", "Need not", "Should", "Should not" in this document are to be interpreted as described in the oneM2M Drafting Rules [i.1] |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 5 Introduction | The scope of Proximal IoT Interworking is to enable the exchange of information between different things, devices and applications and the use of services they provide, irrespective of whether they are designed as oneM2M-defined entities according to the Functional architecture specified in ETSI TS 118 101 [2] or accor... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 6 General interworking architecture | |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 6.1 Concept of Representation | In the oneM2M system, any kind of device, application or service or more generally speaking any kind of function that needs to be exposed to oneM2M-specified entities such as CSEs or AEs is represented by instances of specified resource types. Interaction with these termed functions is enabled by executing operations (... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 6.2 Role of IPE(s) | |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 6.2.1 Fit with the Functional Architecture | oneM2M uses an Interworking Proxy Entity (IPE) to handle the interworking between the oneM2M system and external non-oneM2M Proximal IoT functions residing on Non-oneM2M Device Nodes (NoDNs). The functional relationship between a NoDN and the CSE that is supposed to host the interworking functionality is defined in the... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 6.2.2 Exposure of Proximal IoT functions to the oneM2M System | The role of an IPE, when it comes to exposure of external non-oneM2M Proximal IoT functions to the oneM2M System, includes the creation, monitoring, modification (update/delete) of resource instances that represent those external functions on its own Registrar CSE. This role also includes the following: • The IPE needs... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 6.2.3 Exposure of native oneM2M functions to the Proximal IoT System | The role of an IPE, when it comes to exposure of native oneM2M functions (aspects of devices, applications, services) to an external non-oneM2M Proximal IoT network, includes the monitoring, modification (update/delete) of resource instances that are representing oneM2M-internal functions to be exposed to an external n... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 7.1 Representation of non-oneM2M Proximal IoT Devices | From a device management perspective in oneM2M, a device is represented using a <node> resource. All management related capabilities of a device are then represented using <mgmtObj> child resources of a <node> resource. This principle shall also be applied for non-oneM2M Proximal IoT devices (which are NoDNs), i.e. all... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 7.2 Representation of non-oneM2M Proximal IoT Applications | A general pattern in oneM2M is the use of instances of an <AE> resource to represent applications running on devices/gateways if needed. In addition, all services provided by these applications should be represented as child resources of the respective <AE> resource instance. By browsing the child resources of an <AE> ... |
4593f72f2aa9cdb5ee3e877381639c68 | 118 133 | 7.3 Representation of non-oneM2M Proximal IoT Services | oneM2M defines different types of resources that may be used to represent services provided by a device. When representing non-oneM2M Proximal IoT services from interworked NoDN(s), proper resource types shall be chosen since the misuse of resource types for representing services may cause interoperability problems. Ge... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 1 Scope | The present document defines the sets of checks required for testing conformance of XAdES signatures against extended XAdES signatures as specified ETSI EN 319 132-2 [2]. It defines only the checks that are specific to extended XAdES signatures. The set of checks that are common to both extended and baseline XAdES sign... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 2 References | |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 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... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 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... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BER Basic Encoding Rules CER Canonical Encoding Rules DER Distinguished Encoding Rules HTTP Hyper Text Transfer Protocol OCSP Online Certificate Status Protocol OID Object IDentifier PER Packed Encoding Rules TSP Trusted Service Providers URI ... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 4 Overview | The present clause describes the main aspects of the technical approach used for specifying the whole set of tests to be performed for testing conformance to ETSI EN 319 132-2 [2]. In order to test conformance against the aforementioned specification, several types of tests are identified, namely: 1) Tests on the signa... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.1 Introduction | The present clause specifies the set of assertions, not directly derived from XAdES XML schema and specific to only XAdES–E-BES signatures, to be tested on applications claiming conformance to the XAdES- E-BES signatures as specified in ETSI EN 319 132-2 [2]. Clause 5.2 specifies the assertions for testing conformance ... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.1 Testing XML Signature elements | |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.1.1 Testing ds:Signature element | TA id: XADES_ES/XMLSIG/DSIG/1 Normative source: [1] Clause 4.3, [2] – Clause 4.2 Target: XAdES signature generator claiming conformance to XAdES extended signatures as specified in [2] Predicate: The signature has 0 or more ds:Object children. Prescription level: mandatory Tag: extended XAdES signatures. ETSI ETSI TS 1... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.1.2 Testing ds:KeyInfo element | TA id: XADES_ES/XMLSIG/KEYINFO/1 Normative source: [1] Clause 4.3, [2] – Clause 4.2 Target: XAdES signature generator claiming conformance to XAdES extended signatures as specified in [2] Prerequisite: The signature does not incorporate the SigningCertificateV2 signed property. Predicate: One of its ds:X509Certificate ... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.2.1 Testing incorporation of XAdES qualifying properties to the signature | For testing that the incorporation of XAdES qualifying properties is conformant, the following test assertions shall apply: TA id: XAdES_ES/PROPERTIES/INCORPORATION/1 Normative source: [1]- Clause 4.4.1 Target: XAdES signature generator claiming conformance to XAdES extended signatures as specified in [2] Predicate: Th... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.2.2 Testing xades:QualifyingPropertiesReference | For testing conformance of xades: QualifyingPropertiesReference element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions specified in clause A.2 of the present document, and the following test assertions shall apply: TA id: XAdES_ES/QPREFS/1 Normative source: [1]- Clause 4.4.... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.2.3 Testing xades:QualifyingProperties | For testing conformance of xades:QualifyingProperties element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4], clauses 5.2.2.2.1 and A.2.1.1 test assertions shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.2.4 Testing xades:SignedProperties | For testing conformance of xades:SignedProperties element against extended XAdES signatures, the test assertions defined in ETSI TS 119 134-4 [4], clause A.2.1.2, and the following test assertions shall apply: TA id: XADES_ES/SIGPROP/1 Normative source: [1] Clause 4.3, [2] – Clause 4.2 Target: XAdES signature generator... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.2.5 Testing xades:SignedSignatureProperties | For testing conformance of xades:SignedSignatureProperties element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4], clause A.2.1.2.2, and the following test assertions shall apply: TA id: XADES_ES/SIGSIGPROP/1 Normative source: [1] – Clause 4... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.2.6 Testing xades:SignedDataObjectProperties | For testing conformance of xades:SignedDataObjectProperties element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.2.2.5.1 and A.2.1.2.3 shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.2.7 Testing xades:UnSignedProperties | For testing conformance of xades:UnsignedProperties element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.2.2.6.1 and A.2.1.3.1 shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.2.8 Testing xades:UnSignedSignatureProperties | For testing conformance of xades:UnsignedSignatureProperties element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.2.2.7.1 and A.2.1.3.2 test assertions shall apply. ETSI ETSI TS 119 134-5 V2.1.1 (2016-06) 13 |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.2.2.9 Testing xades:UnSignedDataObjectProperties | For testing conformance of xades:UnsignedSignatureProperties element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.2.2.8.1 and A.2.1.3.3 shall apply. NOTE : So far no property of this type has been specified within XAdES framework... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.3 Testing XAdES qualifying properties | |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.3.1 Testing xades:SigningTime element | For testing conformance of xades:SigningTime element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clause A.3.2 test assertions shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.3.2 Testing xades:SigningCertificateV2 element | For testing conformance of xades:SigningCertificateV2 element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.2.1 and A.3.3, and the following test assertions shall apply: TA id: XADES_ES/SIGCERTV2/1 Normative source: [2] – Clause... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.3.3 Testing xades:CommitmentTypeIndication element | For testing conformance of xades:CommitmentTypeIndication element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.3.1 and A.3.4 shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.3.4 Testing xades:DataObjectFormat element | For testing conformance of xades:DataObjectFormat element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.4.1 and A.3.5 shall apply. ETSI ETSI TS 119 134-5 V2.1.1 (2016-06) 14 |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.3.5 Testing xades:SignatureProductionPlaceV2 element | For testing conformance of xades:SignatureProductionPlaceV2 element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.5.1 and A.3.6 shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.3.6 Testing xades:SignerRoleV2 element | For testing conformance of xades:SignerRoleV2 element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.6.1 and A.3.7 shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.3.7 Testing xades:CounterSignature element | For testing conformance of xades:CounterSignature element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.7.1 and A.3.8, and the following requirements shall apply. For testing conformance of the countersignature itself against ex... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.3.8 Testing xades:AllDataObjectsTimeStamp element | For testing conformance of xades:AllDataObjectsTimeStamp element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.8.1 and A.3.9 shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.3.9 Testing xades:IndividualDataObjectsTimeStamp element | For testing conformance of xades:IndividualDataObjectsTimeStamp element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.9.1 and A.3.10 shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 5.3.10 Testing properties from upper levels | According to ETSI EN 319 132-2 [2], XAdES-E-BES extended signatures should not incorporate the following qualifying properties: xades:SignaturePolicyIdentifier, xadesv141:SignaturePolicyStore, xades:SignatureTimeStamp, xadesv141:CompleteCertificateRefsV2, xadesv141:AttributeCertificateRefsV2, xades:CompleteRevocationRe... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 6.1 Introduction | The clause 6 specifies the set of assertions not directly derived from XAdES XML schema to be tested on XAdES qualifying properties corresponding to XAdES-E-EPES level as specified in ETSI EN 319 132-2 [2], which should not be present in lower levels of extended XAdES signatures, namely: xades:SignaturePolicyIdentifier... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 6.2 Testing xades:SignaturePolicyIdentifier element | |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 6.2.1 General requirements | For testing conformance of xades:SignaturePolicyIdentifier element against XAdES-E-EPES extended signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.10.1 and A.3.11, and clauses 6.2.2, 6.2.3, 6.2.4, and 6.2.5 of the present document shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 6.2.2 Test assertions specific to E-EPES level | TA id: XADES_ES/E_EPES/SIGPOLID/1 Normative source: [2] – clause 4.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Predicate: The xades:SignaturePolicyIdentifier property is present in the signature. Prescription level: mandatory Tag: extended XAdES signatures |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 6.2.3 Testing xades:SPURI signature policy qualifier | For testing conformance of xades:SPURI signature policy qualifier against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.10.2.1 and A.3.11.2 shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 6.2.4 Testing xades:SPUserNotice signature policy qualifier | For testing conformance of xades:SPUserNotice signature policy qualifier against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clause A.3.11.3 shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 6.2.5 Testing xadesv141:SPDocSpecification signature policy qualifier | For testing conformance of xadesv141:SPDocSpecification signature policy qualifier against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.10.3.1 and A.3.11.4 shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 6.3 Testing xadesv141:SignaturePolicyStore element | For testing conformance of xadesv141:SignaturePolicyStore element against extended XAdES signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 5.3.11.1 and A.3.12 shall apply. ETSI ETSI TS 119 134-5 V2.1.1 (2016-06) 17 |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 6.4 Testing properties of upper levels | According ETSI EN 319 132-2 [2], XAdES-E-EPES extended signatures should not incorporate the following qualifying properties: xades:SignatureTimeStamp, xadesv141:CompleteCertificateRefsV2, xadesv141:AttributeCertificateRefsV2, xades:CompleteRevocationRefs, xades:AttributeRevocationRefs, xadesv141:RefsOnlyTimeStampV2, x... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 7.1 Introduction | The present clause specifies the set of assertions not directly derived from XAdES XML schema to be tested on the XAdES qualifying property corresponding to XAdES-E-T level as specified in ETSI EN 319 132-2 [2], which should not be present in lower levels of extended XAdES signatures, namely: xades:SignatureTimeStamp. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 7.2 Testing xades:SignatureTimeStamp element | |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 7.2.1 General requirements | For testing conformance of xades:SignatureTimeStamp element against XAdES-E-T extended signatures as specified in ETSI EN 319 132-2 [2], the test assertions defined in ETSI TS 119 134-4 [4] clauses 6.2.1 and A.3.13, and the test assertions defined in clause 7.2.2 of the present document shall apply. |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 7.2.2 Test assertions specific to E-T level | TA id: XADES_ES/E_T/SIGTST/1 Normative source: [2] – clause 4.3 Target: XAdES signature generator claiming conformance to XAdES baseline signatures as specified in [1] Predicate: The xades:SignatureTimeStamp property is present in the signature. Prescription level: mandatory Tag: extended XAdES signatures |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 7.3 Testing properties from upper levels | According ETSI EN 319 132-2 [2], XAdES-E-T extended signatures should not incorporate the following qualifying properties: xadesv141:CompleteCertificateRefsV2, xadesv141:AttributeCertificateRefsV2, xades:CompleteRevocationRefs, xades:AttributeRevocationRefs, xadesv141:RefsOnlyTimeStampV2, xadesv141:SigAndRefsTimeStampV... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 8.1 Introduction | The present clause specifies the set of assertions not directly derived from XAdES XML schema to be tested on the XAdES qualifying properties corresponding to XAdES-E-C level as specified in ETSI EN 319 132-2 [2], which should not be present in lower levels of extended XAdES signatures, namely: xadesv141:CompleteCertif... |
382aab34632242dff6c525d9edbda0f8 | 119 134-5 | 8.2 Testing xadesv141:CompleteCertificateRefsV2 element |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.