hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 1 Scope | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to XAdES baseline signatures as specified in ETSI EN 319 132-1 [1]. The test suites are defined with four different layers reflecting the four different levels of XAdES baseline signatures: •... |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 2 References | |
07088244ff76d77b9a4d5b111e77d508 | 119 134-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... |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 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... |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 3 Definitions and abbreviations | |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TR 119 001 [i.1] and the following apply: negative test case: test case either for a signature that is not a XAdES baseline signature, or for a signature whose validation according to ETSI EN 319 102-1 [i.4] would not result in TOTAL_PASS... |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.1] and the following apply: CA Certification Authority CRL Certificate Revocation List OCSP Online Certificate Status Provider TSA Time-Stamping Authority TSA1 Time-Stamping Authority 1 TSA2 Time-Stamping Authority 2 |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 4 Overview | This clause describes the overall approach used throughout the present document to specify test suites for testing interoperability of XAdES baseline signature a specified in ETSI EN 319 132-1 [1]. ETSI EN 319 132-1 [1] defines four different levels of XAdES baseline signatures. The test suites are defined with differe... |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 10 Test suites with negative test cases | |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 10.1 Introduction | The present clause distinguishes two different types of negative test cases: 1) Test cases leading to valid XAdES signatures that nevertheless, are not XAdES baseline signatures. 2) Test cases leading to XAdES baseline signatures whose validation according to ETSI EN 319 102-1 [i.4] would not result in TOTAL_PASSED. |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 10.2 Test cases generating non XAdES baseline signatures | The present clause defines test cases that do not generate XAdES baseline signatures. ETSI ETSI TS 119 134-2 V1.1.1 (2016-06) 30 Table 8: Test cases generating non XAdES baseline signatures TC ID Description Pass criteria Signature qualifying properties XAdES/NB/1 A XAdES signature signing one data object (a text file)... |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 10.3 Test cases on XAdES-B-B signatures | The present clause defines test cases that generate XAdES baseline signatures whose validation according to ETSI EN 319 102-1 [i.4] do not result in TOTAL_PASSED. The values within the Pass Criteria column in Table 9 are not the actual final results generated by a validation tool. ETSI ETSI TS 119 134-2 V1.1.1 (2016-06... |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 10.4 Test cases on XAdES-B-T signatures | Table 10 defines test cases that generate XAdES-B-T signatures whose validation process as specified in ETSI EN 319 102-1 [i.4] shall not be TOTAL_PASSED. ETSI ETSI TS 119 134-2 V1.1.1 (2016-06) 34 Table 10: Test cases on XAdES-B-T signatures TC ID Description Pass criteria Signature qualifying properties XAdES/BTN/1 A... |
07088244ff76d77b9a4d5b111e77d508 | 119 134-2 | 10.5 Test cases on XAdES-B-LTA signatures | Table 11 defines test cases that generate XAdES-B-LTA signatures whose validation process as specified in ETSI EN 319 102-1 [i.4] shall not be TOTAL_PASSED. ETSI ETSI TS 119 134-2 V1.1.1 (2016-06) 36 Table 11: Test cases on XAdES-B-LTA signatures TC ID Description Pass criteria Signature qualifying properties XAdES/BLT... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 1 Scope | The present document specifies the semantics and the syntax for a new unsigned XAdES qualifying property able to contain evidence records. The present document specifies the rules that govern the incorporation of evidence records within a XAdES signature or a legacy XAdES signature. NOTE: The present specification allo... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 2 References | |
aed047926db27688653caaa48504eb1e | 119 132-3 | 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... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 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... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 3 Definition of terms, symbols and abbreviations | |
aed047926db27688653caaa48504eb1e | 119 132-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.1], ETSI EN 319 132-1 [1] and the following apply: ArchiveTimeStamp: either a XMLERS ArchiveTimeStamp or an ERS ArchiveTimeStamp ArchiveTimeStampChain: either ers:ArchiveTimeStampChain, as specified in IETF RFC 6283 [5] or an instance of Ar... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.1] and the following apply: ER Evidence Record ERS Evidence Record Syntax TSA Time Stamp Authority XML eXtensible Markup Language XMLERS XML Evidence Record Syntax |
aed047926db27688653caaa48504eb1e | 119 132-3 | 4 General requirements | |
aed047926db27688653caaa48504eb1e | 119 132-3 | 4.1 XML Namespaces | The present document uses the URI namespaces listed below: • http://www.w3.org/2001/XMLSchema • urn:ietf:params:xml:ns:ers In addition to that, it defines a new namespace for including the new unsigned qualifying property specified in the present document, namely: • http://uri.etsi.org/19132/v1.1.1# Table 1 shows the m... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 4.2 Electronic time-stamps in evidence-records | All the electronic time-stamps present within the evidence-records incorporated to the XAdES signatures specified in the present document shall be instances of TimeStampToken type as specified in IETF RFC 3161 [4] and updated by IETF RFC 5816 [6]. ETSI ETSI TS 119 132-3 V1.1.1 (2021-01) 8 |
aed047926db27688653caaa48504eb1e | 119 132-3 | 4.3 Placement of validation data of time-stamp tokens | When including validation data required for verifying a time-stamp token that is encapsulated within an ArchiveTimeStamp, one of the following methods shall be used: 1) adding the information in the SignedData of the instance of the TimeStampToken type specified in IETF RFC 3161 [4] and updated by IETF RFC 5816 [6] its... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 5.1 Semantics | |
aed047926db27688653caaa48504eb1e | 119 132-3 | 5.1.1 Data time-stamped by time-stamp tokens | The present document specifies one qualifying property that allows to incorporate into the XAdES signature one or more evidence records: xadesen:SealingEvidenceRecords. The xadesen:SealingEvidenceRecords qualifying property shall be an unsigned qualifying property. The xadesen:SealingEvidenceRecords unsigned qualifying... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 5.2 Syntax | |
aed047926db27688653caaa48504eb1e | 119 132-3 | 5.2.1 Introduction | The xadesen:SealingEvidenceRecords unsigned qualifying property shall be defined as in XML Schema file "XAdES1913203v111-202101.xsd", whose location is detailed in clause A.1, and is copied below for information. <!-- targetNamespace="http://uri.etsi.org/19132/v1.1.1#"--> <xsd:element name="SealingEvidenceRecords" type... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 5.2.2.1 General requirements | The initial time-stamp token encapsulated within the first ArchiveTimeStamp of any of the evidence-records enclosed within the xadesen:SealingEvidenceRecords unsigned qualifying property, shall incorporate a HashTree, whose first child shall contain the digest value of the group of data objects listed below, concatenat... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 5.2.2.2 Contribution of unsigned qualifying properties directly incorporated | In non-distributed XAdES signatures, where the direct incorporation of the unsigned qualifying properties is used, the set of unsigned qualifying properties contributing to the message imprint computation input shall be the set formed by all the unsigned qualifying properties present within the sequence in the xadesen:... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 5.2.2.3 Contribution of unsigned qualifying properties indirectly incorporated | In distributed XAdES signatures, where the indirect incorporation of the unsigned qualifying properties is used, the set of the unsigned qualifying properties contributing to the message imprint computation input shall be as formed as follows: 1) First add to the set the unsigned qualifying properties that are children... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 6 XAdES signature level including ERS | |
aed047926db27688653caaa48504eb1e | 119 132-3 | 6.1 Overview | The present document specifies a new level for XAdES signatures including evidence records. Each level is created by a combination of attributes defined in ETSI EN 319 132-1 [1] and the present document. |
aed047926db27688653caaa48504eb1e | 119 132-3 | 6.2 General requirements | The XAdES signature shall be a signature incorporating signed and unsigned qualifying properties as specified in clauses 4 and 5 of ETSI EN 319 132-1 [1]. The algorithms and key lengths used to generate and augment digital signatures should be as specified in ETSI TS 119 312 [i.2]. NOTE: Cryptographic suites recommenda... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 6.3 XAdES-E-ERS | XAdES-E-ERS may be built on all the levels described in ETSI EN 319 132-1 [1] or ETSI EN 319 132-2 [2]. Table 2: Requirements for XAdES-E-ERS Elements/Qualifying properties/Services Presence in E-ERS level Cardinality Additional notes and requirements Reference xades:SigningTime may be present 1 a ETSI EN 319 132-1 [1]... |
aed047926db27688653caaa48504eb1e | 119 132-3 | 7 Legacy XAdES baseline signatures | When an ers:SealingEvidenceRecords unsigned qualifying property is incorporated into legacy XAdES extended signatures, this unsigned qualifying property shall comply with the present document. ETSI ETSI TS 119 132-3 V1.1.1 (2021-01) 17 Annex A (normative): XML Schema file A.1 XML Schema file location for namespace http... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 1 Scope | The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to extended CAdES signatures [2]. The present document defines test suites for each level defined in ETSI EN 319 122-2 [2]. Test suites also cover augmentation of extended CAdES signatures an... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 2 References | |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 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... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 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... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 3 Definitions and abbreviations | |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TR 119 001 [i.2] and the following apply: negative test case: test case for a signature whose validation according to ETSI EN 319 102-1 [i.3] would not result in TOTAL-PASSED |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.2] apply. |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 4 Overview | This clause describes the overall approach used to specify test suites for extended CAdES signatures interoperability testing. ETSI EN 319 122-2 [2] defines different signature levels. The test suites are defined with different layers reflecting the levels of extended CAdES signatures specified in [2]. Testing CAdES si... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 5 Testing extended CAdES signatures interoperability | |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 5.1 CAdES-E-BES test cases | The test cases in this clause have been defined for different combinations of CAdES-E-BES signatures attributes. Mandatory attributes for CAdES-E-BES described in [2] specification, clauses 4.2 and 4.3, shall be present. Table 1 shows which attributes are required to generate CAdES-E-BES signatures for each test case. ... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 5.2 CAdES-E-EPES test cases | The test cases in this clause have been defined for different combinations of CAdES-E-EPES signatures attributes. Mandatory attributes for CAdES-E-EPES described in [2] specification, clauses 4.2 and 4.3, shall be present. Table 2 shows which attributes are required to generate CAdES-E-EPES signatures for each test cas... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 5.3 CAdES-E-T test cases | The test cases in this clause have been defined for different combinations of CAdES-E-T signatures attributes. Mandatory attributes for CAdES-E-T described in [2] specification, clause 4.3, shall be present. Table 3 shows which attributes are required to generate CAdES-E-T signatures for each test case. Table 3: Test c... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 5.4 CAdES-E-C test cases | The test cases in this clause have been defined for different combinations of CAdES-E-C signatures attributes. Mandatory attributes for CAdES-E-C described in [2] specification, clause A.1, shall be present. Table 4 shows which attributes are required to generate CAdES-E-C signatures for each test case. Table 4: Test c... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 5.5 CAdES-E-X test cases | The test cases in this clause have been defined for different combinations of CAdES-E-X signatures attributes. Mandatory attributes for CAdES-E-X described in [2] specification, clause A.1, shall be present. Table 5 shows which attributes are required to generate test CAdES-E-X signatures for each test case. Table 5: T... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 5.6 CAdES-E-XL test cases | The test cases in this clause have been defined for different combinations of CAdES-E-XL signatures attributes. Mandatory attributes for CAdES-E-XL described in [2] specification, clause A.1, shall be present. Table 6 shows which attributes are required to generate test CAdES-E-XL signatures for each test case. Table 6... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 5.7 CAdES-E-A test cases | The test cases in this clause have been defined for different combinations of CAdES-E-A signatures attributes. Mandatory attributes for CAdES-E-A described in [2] specification, clauses 6.3 and A.2, shall be present. Table 7 shows which attributes are required to generate test CAdES-E-A signatures for each test case. T... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 6.1 Introduction | This clause describes augmentation tests where a signer generates a basic signature and a verifier, after verifying, augments it to a more evolved form. The following clauses contain augmentation test cases grouped by CAdES level. |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 6.2 Augmentation to CAdES-E-C signatures test cases | The test cases in this clause deal with the augmentation to CAdES-E-C signatures. Table 8 shows 2 augmentation to CAdES-E-C signatures test cases. Table 8: Test cases for augmentation to CAdES-E-C signatures TC ID Description Pass criteria Signature attributes CAdES/Aug/1 This test case tests the augmentation of a CAdE... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 6.3 Augmentation to CAdES-E-X signatures test cases | The test cases in this clause deal with the augmentation to CAdES-E-X signatures. Table 9 shows 3 augmentation to CAdES-E-X signatures test cases. Table 9: Test cases for augmentation to CAdES-E-X signatures TC ID Description Pass criteria Signature attributes CAdES/Aug/3 This test case tests the augmentation of a CAdE... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 6.4 Augmentation to CAdES-E-XL signatures test cases | The test cases in this clause deal with the augmentation to CAdES-E-XL signatures. Table 10 shows 3 augmentation to CAdES-E-XL signatures test cases. Table 10: Test cases for augmentation to CAdES-E-XL signatures TC ID Description Pass criteria Signature attributes CAdES/Aug/6 This test case tests the augmentation of a... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 6.5 Augmentation to CAdES-E-A signatures test cases | The test cases in this clause deal with the augmentation to CAdES-E-A signatures. Table 11 shows 3 augmentations to CAdES-E-A signatures test cases. Table 11: Test cases for upgrading to CAdES-A forms TC ID Description Pass criteria Signature attributes CAdES/Aug/9 This test case tests the augmentation of a CAdES- E-BE... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 7 Testing negative extended CAdES signatures | |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 7.1 CAdES-E-BES test cases | The test cases in this clause have been defined for CAdES-E-BES signatures. Table 12 shows which attributes are defined in the negative CAdES-E-BES signatures for each test case. Table 12: Negative test cases for CAdES-E-BES signatures TC ID Description Pass criteria Signature attributes CAdES/BESN/1 Verify a signed do... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 7.2 CAdES-E-EPES test cases | The test cases in this clause have been defined for CAdES-E-EPES signatures. Table 13 shows which attributes are defined in the negative CAdES-E-EPES signatures for each test case. Table 13: Negative test cases for CAdES-E-EPES signatures TC ID Description Pass criteria Signature attributes CAdES/EPESN/1 Verify a signe... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 7.3 CAdES-E-T test cases | The test cases in this clause have been defined for CAdES-E-T signatures. Table 14 shows which attributes are defined in the negative CAdES-E-T signatures for each test case. Table 14: Negative test cases for CAdES-E-T signatures TC ID Description Pass criteria Signature attributes CAdES/TN/1 Verify a signed document i... |
61cae43c0e2451863c31e9442f9d8612 | 119 124-3 | 7.4 CAdES-E-A test cases | The test cases in this clause have been defined for CAdES-E-A signatures. Table 15 shows which attributes are defined in the negative CAdES-E-A signatures for each test case. Table 15: Negative test cases for CAdES-A signatures TC ID Description Pass criteria Signature attributes CAdES/AN/1 Verify a signed document in ... |
06559e33e90280230a357784864e9b49 | 119 122-3 | 1 Scope | The present document provides mechanism to incorporate evidence records in ASN.1 format within a CAdES signature as outlined in ETSI EN 319 122-1 [4], annex B. It specifies the attributes to be used and profiles the ERS standard (IETF RFC 4998 [2]) to provide clear rules how to incorporate ERS within a CAdES signature ... |
06559e33e90280230a357784864e9b49 | 119 122-3 | 2 References | |
06559e33e90280230a357784864e9b49 | 119 122-3 | 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... |
06559e33e90280230a357784864e9b49 | 119 122-3 | 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... |
06559e33e90280230a357784864e9b49 | 119 122-3 | 3 Definitions and abbreviations | |
06559e33e90280230a357784864e9b49 | 119 122-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TR 119 001 [i.1], ETSI EN 319 122-1 [4] and the following apply: archive-timestamp: timestamp which is used for long-term preservation purposes EXAMPLE: An archive-timestamp can for example be a TimeStampToken according to IETF RFC 3161 [... |
06559e33e90280230a357784864e9b49 | 119 122-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.1] and the following apply: ER Evidence Record ERS Evidence Record Syntax TSU Time Stamping Unit |
06559e33e90280230a357784864e9b49 | 119 122-3 | 4 General requirements | |
06559e33e90280230a357784864e9b49 | 119 122-3 | 4.1 Introduction | This clause specifies mechanisms how to include validation data into the signature. 4.2 Inclusion of validation data within a TimeStampToken instance When including validation data within a TimeStampToken instance according to IETF RFC 3161 [1] and updated by IETF RFC 5816 [3] one of the following methods shall be used... |
06559e33e90280230a357784864e9b49 | 119 122-3 | 4.3 Inclusion of validation data within CAdES signatures | The present document specifies two strategies for the inclusion of validation data within a CAdES signature, depending on whether attributes for long term availability, as defined in different versions of ETSI TS 101 733 [i.2], have already been added to the SignedData: • If none of ATSv2 attributes (see clause A.2.4 o... |
06559e33e90280230a357784864e9b49 | 119 122-3 | 5 Attribute semantics and syntax | |
06559e33e90280230a357784864e9b49 | 119 122-3 | 5.1 The evidence-records attributes | In the present document two attributes are described that allow to include an evidence record (ER) over the whole SignedData instance: • The internal-evidence-records attribute (clause 5.2) protects the whole SignedData instance and is used in cases of attached signatures. • The external-evidence-records attribute (cla... |
06559e33e90280230a357784864e9b49 | 119 122-3 | 5.2 The internal-evidence-records attribute | Semantics The internal-evidence-records attribute incorporates an ER covering the ContentInfo instance of type signed-data, as specified in ETSI EN 319 122-1 [4], containing an eContent element within encapContentInfo. Syntax The internal-evidence-records attribute shall be identified by the id-aa-er-internal OID as de... |
06559e33e90280230a357784864e9b49 | 119 122-3 | 5.3 The external-evidence-records attribute | Semantics The external-evidence-records attribute incorporates an ER covering the ContentInfo instance of type signed-data, as specified in ETSI EN 319 122-1 [4], not containing an eContent element within encapContentInfo, i.e. in case of an external signature, and the external signed data. Syntax The external-evidence... |
06559e33e90280230a357784864e9b49 | 119 122-3 | 6 CAdES signature level including ERS | |
06559e33e90280230a357784864e9b49 | 119 122-3 | 6.1 Overview | The present document specifies a new level for CAdES signatures including ERS. Each level is created by a combination of attributes defined in ETSI EN 319 122-1 [4] and the present document. |
06559e33e90280230a357784864e9b49 | 119 122-3 | 6.2 General requirements | The general CMS syntax shall be as specified in ETSI EN 319 122-1 [4], clause 4. The signature shall contain a CMS SignedData, as defined in ETSI EN 319 122-1 [4], clause 4.4 and at least one SignerInfo (ETSI EN 319 122-1 [4], clause 4.6). The algorithms and key lengths used to generate and augment digital signatures s... |
06559e33e90280230a357784864e9b49 | 119 122-3 | 6.3 CAdES-E-ERS | CAdES-E-ERS may be built on all the levels described in ETSI EN 319 122-1 [4] or ETSI EN 319 122-2 [i.3]. Table 1: Requirements for CAdES-E-ERS Signature fields/Attributes/Services Presence in E-ERS level Cardinality References Additional requirements and notes content-type shall be present 1 ETSI EN 319 122-1 [4], cla... |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 1 Scope | The present document specifies Interoperability Test Descriptions (TDs) for the oneM2M Primitives as specified in ETSI TS 118 101 [1], oneM2M TS-0004 [2], the bindings ETSI TS 118 108 [3], ETSI TS 118 109 [4] and ETSI TS 118 110 [5]. |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 2 References | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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... |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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... |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 3 Definitions of terms, symbols and abbreviations | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [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 [7]. hosting CSE: CSE where the addressed resource is hosted M2M service provider domai... |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 3.2 Symbols | Void. |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACP Access Control Policy ACP-SD Access Control Policy-Semantic Descriptor ADN-AE AE which resides in the Application Dedicated Node AE Application Entity AE-ID Application Entity Identifier APP-ID Application Identifier BBF BroadBand Forum CF... |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 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]. |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 5 Testing conventions | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 5.1 The Test Description proforma | The testing methodology used in the present document is specified in the ETSI TS 118 115 [6]. A Test Description (TD) is a well detailed description of a process that aims to test one or more functionalities of an implementation. Applying to interoperability testing, these testing objectives address the interoperable f... |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 5.2 Test Description naming convention | TD/<root>/<gr>/<nn> <root> = root M2M oneM2M <gr> = group NH No Hop: Testing on Mca reference point NB Non-Blocking scenario SH Single Hop: management of remote resources on Mca + Mcc MH Multi Hop SE Security <nn> = sequential number 01 to 99 |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 5.3 Test Settings | This clause contains some test requirements applied to the testing, some constraints, restrictions for executions or some recommendations. In order to ease test setup and execution, the CSE and AE are requested to support the following settings: • Security shall be disable as it is out of scope of this interoperability... |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 5.4 Pre-conditions | |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 5.4.1 Registration | The AE or CSE that originates the request has been successfully registered to its corresponding CSE. The registration of the AE includes the creation of <AE> resource under the <CSEBase> of its registrar CSE. The registration of the CSE includes the creation of <remoteCSE> resource representing itself under the <CSEBas... |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 5.4.2 Security | The Originator and the receiver have successfully established security association between each other. This may involve the exchange of key and the establishment of a security connection. The security pre-condition also assumes that the originator has the appropriate access control privilege towards the requested resou... |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 5.4.3 Service Subscription | Service subscription means that the originator is allowed to be connected with the oneM2M system by contract between the owner of the application and the service provider of the oneM2M system. This may require a corresponding information record in the <m2mServiceSubscriptionProfile> resource. |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 5.4.4 ID allocation | ID allocation means that the Originator has already acquired usable identity, either from its registrar CSE or the IN-CSE of the oneM2M system. The ID may be CSE relative or SP relative. The ID is then further used as the identity of the Originator to perform access control, charging, etc. |
e80b5da6c14ed17fdbf5d0fb9b8ebe31 | 118 113 | 5.4.5 Existence of resource | Existence of resource means the resource been addressed and has already been created. 5.4.6 Management Session between Management Server and Management Client Before the device management using external technologies is executed, it is required that a management session has already been established between the Managemen... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.