Split (1)

train · 194k rows

hash stringlengths 32 32	doc_id stringlengths 7 13	section stringlengths 3 121	content stringlengths 0 3.82M
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.13 Test assertions for SubmissionTime element	The test assertions defined in clause 5.5 of the present document shall apply for testing the SubmissionTime child element of Evidence element. 6.14 Test assertions for EvidenceRefersToRecipient element ERDS/EVIDENCE/EVID_REF_TO_RECP/TA_01 TA Id ERDS/EVIDENCE/EVID_REF_TO_RECP/TA_01 Normative source ETSI EN 319 522-3 [3], clauses 5.2.2.6 and 5.2.2.21 Target Conformance to ERDS Evidence content Predicate The EvidenceRefersToRecipient element child of Evidence element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EVID_REF_TO_RECP/TA_02 TA Id ERDS/EVIDENCE/EVID_REF_TO_RECP/TA_02 Normative source ETSI EN 319 522-3 [3], clauses 5.2.2.6 and 5.2.2.21 Target Conformance to ERDS Evidence content Predicate The EvidenceRefersToRecipient element child of Evidence element does not have any XML except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 27 ERDS/EVIDENCE/EVID_REF_TO_RECP/TA_03 TA Id ERDS/EVIDENCE/EVID_REF_TO_RECP/TA_03 Normative source ETSI EN 319 522-3 [3], clauses 5.2.2.6 and 5.2.2.21 Target Conformance to ERDS Evidence content Predicate The value of the EvidenceRefersToRecipient element child of Evidence element is an integer Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EVID_REF_TO_RECP/TA_04 TA Id ERDS/EVIDENCE/EVID_REF_TO_RECP/TA_04 Normative source ETSI EN 319 522-3 [3], clauses 5.2.2.6 and 5.2.2.21 Target Conformance to ERDS Evidence content Predicate The integer value of the EvidenceRefersToRecipient element child of Evidence element references one of the recipients Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.15 Test assertions for MessageIdentifier element	The test assertions defined in clause 5.2.6 shall apply for testing the MessageIdentifier child element of Evidence element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.16 Test assertions for UserContentInfo element	ERDS/EVIDENCE/US_CONT_INFO/TA_01 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_01 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The content of UserContentInfo element child of Evidence element, in terms of XML children element is as follows: AppLayerIdentifier? ComposingParts? PartsInfo Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ERDS_POLICY_ID/TA_02 TA Id ERDS/EVIDENCE/ERDS_POLICY_ID/TA_02 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The UserContentInfo element child of Evidence element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_03 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_03 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The AppLayerIdentifier element child of UserContentInfo element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 28 ERDS/EVIDENCE/US_CONT_INFO/TA_04 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_04 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The AppLayerIdentifier element child of UserContentInfo element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_05 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_05 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The ComposingParts element child of UserContentInfo element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_06 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_06 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The ComposingParts element child of UserContentInfo element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_07 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_07 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The value of the ComposingParts element child of UserContentInfo element is an integer Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_08 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_08 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The content of PartsInfo element child of UserContentInfo element, in terms of XML elements is as follows: PartInfo+ Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_09 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_09 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The PartsInfo element child of UserContentInfo element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 29 ERDS/EVIDENCE/US_CONT_INFO/TA_10 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_10 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The content of PartInfo element child of PartsInfo element, in terms of XML elements is as follows: Identifier ContentType DigestMethod? DigestValue? Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_11 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_11 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The PartInfo element child of PartsInfo element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_12 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_12 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The Identifier element child of PartInfo element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_13 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_13 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The Identifier element child of PartInfo element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_14 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_14 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The ContentType element child of PartInfo element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_15 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_15 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Predicate The ContentType element child of PartInfo element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 30 ERDS/EVIDENCE/US_CONT_INFO/TA_16 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_16 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Prerequisite The PartInfo element contains the ds:DigestMethod child element Predicate The PartInfo element contains the ds:DigestValue child element Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/US_CONT_INFO/TA_17 TA Id ERDS/EVIDENCE/US_CONTN_INFO/TA_17 Normative source ETSI EN 319 522-3 [3], clauses 4.3.13 and 5.2.2.23 Target Conformance to ERDS Evidence content Prerequisite The PartInfo element contains the ds:DigestValue child element Predicate The PartInfo element contains the ds:DigestMethod child element Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence The set of test assertions ranging from ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_17 to ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_22, replacing CertDigest by PartInfo, which are defined in clause 6.22.1.3.3.2 shall apply for testing ds:DigestMethod and ds:DigestValue.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.17 Test assertions for ExtenalERDSDetails element	The test assertions defined in clause 6.22.1 shall apply for testing the ExtenalERDSDetails child element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.18 Test assertions for ExtenalSystem element	ERDS/EVIDENCE/EXT_SYSTEM/TA_01 TA Id ERDS/EVIDENCE/EXT_SYSTEM/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.24 Target Conformance to ERDS Evidence content Predicate The ExternalSystem element child of Evidence element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EXT_SYSTEM/TA_02 TA Id ERDS/EVIDENCE/EXT_SYSTEM/TA_02 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.24 Target Conformance to ERDS Evidence content Predicate The ExternalSystem element child of Evidence element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EXT_SYSTEM/TA_03 TA Id ERDS/EVIDENCE/EXT_SYSTEM/TA_03 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.24 Target Conformance to ERDS Evidence content Predicate The ExternalSystem element child of Evidence element is a string Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 31 6.19 Test assertions for TransactionLogInformation element ERDS/EVIDENCE/TRANSACT_LOG_INFO/TA_01 TA Id ERDS/EVIDENCE/TRANSACT_LOG_INFO/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The contents of TransactionLogInformation element child of Evidence element, in terms of XML elements, is as follows: TransactionLog+ Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/TRANSACT_LOG_INFO/TA_02 TA Id ERDS/EVIDENCE/TRANSACT_LOG_INFO/TA_02 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The TransactionLogInformation element child of Evidence element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.20 Test assertions for ds:Signature element	Test assertions defined in ETSI TS 119 134-4 [9] or ETSI TS 119 134-5 [14] shall apply for testing the ds:Signature element child of Evidence if this element is a XAdES signature, depending whether it is a XAdES baseline or a XAdES extended signature, respectively.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.21 Test assertions for Extensions element
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.21.1 Introduction	ERDS/EVIDENCE/EXTENSIONS/TA_01 TA Id ERDS/EVIDENCE/EXTENSIONS/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The Extensions element child of Evidence element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EXTENSIONS/TA_02 TA Id ERDS/EVIDENCE/EXTENSIONS/TA_02 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The content of the Extensions element child of Evidence element, in terms of XML children element is as follows: Extension+ Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 32 6.21.2 Test assertions for GeneralEvidenceInfo child of Extension element ERDS/EVIDENCE/EXTENSION/GENEVIDINFO/TA_01 TA Id ERDS/EVIDENCE/EXTENSIONS/GENEVIDINFO/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The GeneralEvidenceInfo element child of Extension element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EXTENSION/GENEVIDINFO/TA_02 TA Id ERDS/EVIDENCE/EXTENSIONS/GENEVIDINFO/TA_02 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The content of the GeneralEvidenceInfo element child of Extension element, in terms of XML children element is as follows: Subject?, UntrustedPathToRecipient* Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EXTENSION/GENEVIDINFO/TA_03 TA Id ERDS/EVIDENCE/EXTENSIONS/GENEVIDINFO/TA_03 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The Subject element child of GeneralEvidenceInfo element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EXTENSION/GENEVIDINFO/TA_04 TA Id ERDS/EVIDENCE/EXTENSIONS/GENEVIDINFO/TA_04 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The value of the Subject element child of GeneralEvidenceInfo element is a string Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EXTENSION/GENEVIDINFO/TA_05 TA Id ERDS/EVIDENCE/EXTENSIONS/GENEVIDINFO/TA_05 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The UntrustedPathToRecipient element child of GeneralEvidenceInfo element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EXTENSION/GENEVIDINFO/TA_06 TA Id ERDS/EVIDENCE/EXTENSIONS/GENEVIDINFO/TA_06 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The value of the UntrustedPathToRecipient element child of GeneralEvidenceInfo element is an integer Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 33 6.21.3 Test assertions for RelayEvidenceInfo child of Extension element ERDS/EVIDENCE/EXTENSION/RELAYEVIDINFO/TA_01 TA Id ERDS/EVIDENCE/EXTENSIONS/GENEVIDINFO/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The RelayEvidenceInfo element child of Extension element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EXTENSION/RELAYEVIDINFO/TA_02 TA Id ERDS/EVIDENCE/EXTENSIONS/GENEVIDINFO/TA_02 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The content of the RelayEvidenceInfo element child of Extension element, in terms of XML children element is as follows: RelayEvidenceRefersTo* Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EXTENSION/RELAYEVIDINFO/TA_03 TA Id ERDS/EVIDENCE/EXTENSIONS/GENEVIDINFO/TA_03 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The RelayEvidenceRefersTo element child of RelayEvidenceInfo element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/EXTENSION/RELAYEVIDINFO/TA_04 TA Id ERDS/EVIDENCE/EXTENSIONS/GENEVIDINFO/TA_04 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.26 Target Conformance to ERDS Evidence content Predicate The value of the RelayEvidenceRefersTo element child of RelayEvidenceInfo element is an integer Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22 Test assertions for XML types
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.1 Test assertions for instances of EntityDetailsType type
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.1.1 Introduction	Clause 6.22.1 defines test assertions for any instance of EntityDetailsType type, namely: EvidenceIssuerDetails, and ExternalERDSDetails. ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_01 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.10 Target Conformance to ERDS Evidence content Predicate The contents of EntityDetailsType type, in terms of XML elements, is as follows: Id CertificateDetails? Any? Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 34 ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_02 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_02 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.10 Target Conformance to ERDS Evidence content Predicate The instances of EntityDetailsType type do not have any XML attribute except the attributes declaring namespaces. Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence 6.22.1.2 Test assertions for Identity child element of instances of EntityDetailsType type ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_03 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_03 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.11 Target Conformance to ERDS Evidence content Predicate The contents of Identity element child of instances of EntityDetailsType type, in terms of XML elements, is as follows: saml:Attribute+ Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_04 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_04 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.11 Target Conformance to ERDS Evidence content Predicate The Identity element child of instances of EntityDetailsType type do not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_05 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_05 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.11 Target Conformance to ERDS Evidence content Predicate The inner structure of each saml:Attribute element child of Identity type is as specified in the XML Schema of SAML 2 Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence NOTE: The previous test assertion (ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_05) does not provide the level of details regarding the content in terms of XML children elements and attributes for saml:Attribute because ETSI EN 319 522-3 [3], does not define it. ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_06 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_06 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.11 Target Conformance to ERDS Evidence content Predicate The contents of saml:Attribute element child of Identity type is conformant with identity attributes specified in "eIDAS SAML Attribute profile" [8] Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 35 6.22.1.3 Test assertions for CertificateDetails in instances of EntityDetailsType type
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.1.3.1 Test assertions for CertificateDetails child element	ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_07 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_07 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The contents of CertificateDetails element child of instances of EntityDetailsType type, in terms of XML elements is as follows: X509Certificate \|\| CertID \|\| CertIDAndSignature \|\| (X509Certificate CertID) \|\| (CertID X509Certificate) \|\| (X509Certificate CertIDAndSignature) \|\| (CertIDAndSignature X509Certificate) \|\| (CertID CertIDAndSignature) \|\| (CertIDAndSignature CertID) \|\| (X509Certificate CertID CertIDAndSignature) \|\| (X509Certificate CertIDAndSignature CertID) \|\| (CertID X509Certificate CertIDAndSignature) \|\| (CertID CertIDAndSignature X509Certificate) \|\| (CertIDAndSignature CertID X509Certificate) \|\| (CertIDAndSignature X509Certificate CertID) Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_08 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_08 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The CertificateDetails element child of instances of EntityDetailsType type does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.1.3.2 Test assertions for X509Certificate child element of CertificateDetails	ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_09 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_09 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The X509Certificate element child of instances of CertificateDetails does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_10 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_10 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The X509Certificate element child of instances of CertificateDetails does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_11 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_11 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The value X509Certificate element child of instances of CertificateDetails is the base-64 encoding of a DER-encoded X509 certificate Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 36
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.1.3.3 Test assertions for CertID child element of CertificateDetails	6.22.1.3.3.1 Test assertions for the whole CertID child element of CertificateDetails The predicates of the following test assertions are similar to the ones in the test assertions defined in clause A.1.5.2 of ETSI TS 119 134-4 [9]. The rest of the fields in the test assertions have been changed for matching their scope to the scope of the present document. ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_12 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_12 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The content of CertID element child of f CertificateDetails element, in terms of XML elements, is as follows: CertDigest IssuerSerialV2? Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_13 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_13 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The set of attributes (leaving apart the attributes declaring namespaces) of CertID element child of CertificateDetails element is as follows: URI? Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_14 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_14 Normative source ETSI EN 319 132-1 [10], clause 5.2.2 Target Conformance to ERDS Evidence content Predicate The value of attribute URI of CertID element child of CertificateDetailsType element is a valid URI reference Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence 6.22.1.3.3.2 Test assertions for the CertDigest child element of CertID The predicates of the following test assertions are similar to the ones in the test assertions defined in clause A.1.5.2 of ETSI TS 119 134-4 [9]. The rest of the fields in the test assertions have been changed for matching their scope to the scope of the present document. ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_15 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_15 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The contents of CertDigest element child of CertID element, in terms of XML elements, is as follows: ds:DigestMethod ds:DigestValue Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_16 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_16 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The CertDigest element child of CertID element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 37 ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_17 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_17 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.6 Target Conformance to ERDS Evidence content Predicate The ds:DigestValue element child of CertDigest element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_18 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_18 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.6 Target Conformance to ERDS Evidence content Predicate The ds:DigestValue element child of CertDigest does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_19 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_19 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.6 Target Conformance to ERDS Evidence content Predicate The content of ds:DigestValue element child of CertDigest is a valid base-64 value Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_20 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_20 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.5 Target Conformance to ERDS Evidence content Predicate The ds:DigestMethod element child of CertDigest element may have any mixed content of XML children elements and children text nodes Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_21 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_21 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.5 Target Conformance to ERDS Evidence content Predicate The set of attributes (leaving apart the attributes declaring namespaces) of ds:DigestMethod element child of CertDigest is as follows: URI Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_22 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_22 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.5 Target Conformance to ERDS Evidence content Predicate The value of attribute URI of ds:DigestMethod element child of CertDigest is a valid URI Reference Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 38 6.22.1.3.3.3 Test assertions for the IssuerSerialV2 child element of CertID ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_23 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_23 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The IssuerSerialV2 child element of CertID does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_24 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_24 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The IssuerSerialV2 child element of CertID does not have any XML attributes except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_25 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_25 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The content IssuerSerialV2 child element of CertID is the base-64 encoding of one DER- encoded instance of type IssuerSerial type defined in IETF RFC 5035 [12] Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence 6.22.1.3.3.4 Test assertions for CertIDAndSignature child element of CertificateDetails ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_26 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_26 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The contents of CertIDAndSignature element child of instances of CertificateDetailsType type, in terms of XML elements is as follows: CertID, CertSignatureDetails Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence For CertID element, the Test Assertions defined in clause 6.22.1.3.3 of the present document. ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_27 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_27 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.12 Target Conformance to ERDS Evidence content Predicate The contents of CertSignatureDetails element child of instances of CertIDAndSignatureType type, in terms of XML elements is as follows: ds:SignatureMethod, ds:SignatureValue Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 39 ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_28 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_28 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.6 Target Conformance to ERDS Evidence content Predicate The ds:SignatureValue element child of CertSignatureDetails element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_29 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_29 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.6 Target Conformance to ERDS Evidence content Predicate The ds:SignatureValue element child of CertSignatureDetails element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_30 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_30 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.6 Target Conformance to ERDS Evidence content Predicate The ds:SignatureValue element child of CertSignatureDetails element is a valid base- 64 value Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_31 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_31 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.5 Target Conformance to ERDS Evidence content Predicate The ds:SignatureMethod element child of CertSignatureDetails element may have any mixed content of XML children elements and children text nodes Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_32 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_32 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.5 Target Conformance to ERDS Evidence content Predicate The set of attributes (leaving apart the attributes declaring namespaces) of the ds:SignatureMethod element child of CertSignatureDetails element, is as follows: Algorithm Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_33 TA Id ERDS/EVIDENCE/ENTITY_DETS_TYPE/TA_33 Normative source W3C XML Sig 1.1 [11], clause 4.4.3.5 Target Conformance to ERDS Evidence content Predicate The value of attribute Algorithm of the ds:SignatureMethod element child of CertSignatureDetails element is a valid URI Reference Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 40
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.2 Test assertions for instances of UserDetailsType type
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.2.1 Introduction	Clause 6.22.2 defines test assertions for any instance of UserDetailsType type, namely: SenderDetails, and RecipientDetails. ERDS/EVIDENCE/USER_DETS_TYPE/TA_01 TA Id ERDS/EVIDENCE/USER_DETS_TYPE/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.15 Target Conformance to ERDS Evidence content Predicate The contents of the SenderDelegateDetails element, instance of UserDetailsType type, in terms of XML elements, is as follows: Identity Identifier? AssuranceLevelsDetails? Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/USER_DETS_TYPE/TA_02 TA Id ERDS/EVIDENCE/USER_DETS_TYPE/TA_02 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.15 Target Conformance to ERDS Evidence content Predicate An instance of UserDetailsType type, has at least one XML element child Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/USER _DETS_TYPE/TA_03 TA Id ERDS/EVIDENCE/USER _DETS_TYPE/TA_03 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.15 Target Conformance to ERDS Evidence content Predicate The instances of UserDetailsType type do not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.2.2 Test assertions for Identity child element	The test assertions for this element shall be the test assertions defined in clause 6.22.1.2 replacing EntityDetailsType by UserDetailsType.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.2.3 Test assertions for Identifier child element	The test assertions for this element shall be the test assertions defined in clause 5.3.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.2.4 Test assertions for AssuranceLevelsDetails child element	The test assertions defined in clause 6.22.4 of the present document shall apply for testing the AssuranceLevelsDetails child element of instances of UserDetailsType type. 6.22.3 Test assertions for instances of RecipientsDelegateDetailsType type The present clause defines test assertions for instances of RecipientsDelegateDetailsType type. The RecipientsDelegateDetails child element of Evidence is the only instance of this type. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 41 ERDS/EVIDENCE/DELEGATE_TYPE/TA_01 TA Id ERDS/EVIDENCE/DELEGATETYPE/TA_01 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.19 Target Conformance to ERDS Evidence content Predicate The content of instances of RecipientsDelegateDetailsType type, in terms of XML elements, is as follows: Identity Identifier AssuranceLevelsDetails DelegatingRecipients+ Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/DELEGATE_TYPE/TA_02 TA Id ERDS/EVIDENCE/DELEGATETYPE/TA_02 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.19 Target Conformance to ERDS Evidence content Predicate The instances of RecipientsDelegateDetailsType type do not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/DELEGATE_TYPE/TA_03 TA Id ERDS/EVIDENCE/DELEGATETYPE/TA_03 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.19 Target Conformance to ERDS Evidence content Predicate The DelegatingRecipient child element of instances of RecipientsDelegateDetailsType does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/DELEGATE_TYPE/TA_04 TA Id ERDS/EVIDENCE/DELEGATETYPE/TA_04 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.19 Target Conformance to ERDS Evidence content Predicate The DelegatingRecipient child element of instances of RecipientsDelegateDetailsType does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/DELEGATE_TYPE/TA_05 TA Id ERDS/EVIDENCE/DELEGATETYPE/TA_05 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.19 Target Conformance to ERDS Evidence content Predicate The value of the DelegatingRecipient child element of instances of RecipientsDelegateDetailsType is a sequence of integer values Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/DELEGATE_TYPE/TA_06 TA Id ERDS/EVIDENCE/DELEGATETYPE/TA_06 Normative source ETSI EN 319 522-3 [3], clause 5.2.2.19 Target Conformance to ERDS Evidence content Predicate Each integer present in the value of the DelegatingRecipient child element of instances of RecipientsDelegateDetailsType references one of the recipients Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence The test assertions defined in clause 6.22.2.2 of the present document shall apply for testing the Identity child element. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 42 The test assertions defined in clause 6.22.2.3 of the present document shall apply for testing the Identifier child element. The test assertions defined in clause 6.22.2.4 of the present document shall apply for testing the AssuranceLevelsDetailschild element. 6.22.4 Test assertions for instances of AssuranceLevelsDetailsType type
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.4.1 Introduction	This clause defines test assertions for instances of AssuranceLevelsDetailsType type. This type has the following instances: AssuranceLevelsDetails children elements of instances of UserDetailsType, DelegateDetailsType, and RecipientsDelegatesDetailsType. ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_01 TA Id ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence content Predicate The content of AssuranceLevelsDetailsType type, in terms of XML elements, is as follows: (GlobalAssuranceLevel AuthenticationDetails) \|\| (AuthenticationDetsAndAssuranceLevel IdentityProofAssuranceLevel FederationAssuranceLevel?) Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_02 TA Id ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence content Predicate Instances of AssuranceLevelsDetailsType type do not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.4.2 Test assertions for GlobalAssuranceLevel child element	The test assertions defined in clause 5.4 of the present document shall apply for testing the GlobalAssuranceLevel child element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.4.3 Test assertions for AuthenticationDetails child element	ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_03 TA Id ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence content Predicate The content of AuthenticationDetails child element of instances of AssuranceLevelsDetailsType type, in terms of XML elements, is as follows: saml:Assertion \|\| OAuth2 \|\| (AuthenticationTime AuthenticationMethod) \|\| other Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence NOTE: This clause does not provide the level of details regarding the content in terms of XML children elements and attributes neither for saml:Asertion nor for OAuth2 because ETSI EN 319 522-3 [3] does not define them. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 43 ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_04 TA Id ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_04 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence content Predicate The AuthenticationDetails child element of instances of AssuranceLevelsDetailsType type does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence The test assertions defined in clause 5.5 of the present document shall apply for testing each AuthenticationTime child element of AuthenticationDetails element. ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_05 TA Id ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_05 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence content Predicate The AuthenticationMethod child element of AuthenticationDetails element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_06 TA Id ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_06 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence content Predicate The AuthenticationMethod child element of AuthenticationDetails element does not have XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_7 TA Id ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_7 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence content Predicate The value of the AuthenticationMethod child element of AuthenticationDetails element is a valid URI reference Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence 6.22.4.4 Test assertions for AuthenticationDetsAndAssuranceLevel child element ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_8 TA Id ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_8 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence content Predicate The content of the AuthenticationDetsAndAssuranceLevel child element of instances of AssuranceLevelsDetailsType, in terms of XML elements, is as follows: AssuranceLevel AuthenticationDetails Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 44 ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_9 TA Id ERDS/EVIDENCE/ASSURANCE_LEVELS_TYPE/TA_9 Normative source ETSI EN 319 522-3 [3], clause 4.3.14 Target Conformance to ERDS Evidence content Predicate The AuthenticationDetsAndAssuranceLevel child element of instances of AssuranceLevelsDetailsType does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence The test assertions defined in clause 5.4 of the present document shall apply for testing the AssuranceLevel child element. The test assertions defined in clause 6.22.4.3 of the present document shall apply for testing the AuthenticationDetails child element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.4.5 Test assertions for IdentityProofAssuranceLevel child element	The test assertions defined in clause 5.4 of the present document shall apply for testing the IdentityProofAssuranceLevel child element of instances of AssuranceLevelsDetailsType type. The following test assertions, derived from the following additional requirements defined in Table 13 of ETSI EN 319 522-2 [2], clause 8.4 and copied below for the sake of completeness, shall also apply. "(b) either "I10 Sender's identity assurance level detail" component or I11 "Sender's delegate identity assurance level detail" component shall be present in these evidences". ERDS/IDENTITY_ASSURANCE_LEVEL/TA_01 TA Id ERDS/IDENTITTY_ASSURANCE_LEVEL/TA_01 Normative source ETSI EN 319 522-2 [2], clause 8.4 Target Conformance to ERDS Evidence and metadata content Prerequisite The IdentityProofAssuranceLevel element is descendant of the SenderDetails element AND the AssuranceLevel child element of IdentityProofAssuranceLevel of the SenderDelegateDetails element is NOT empty Predicate The value of the AssuranceLevel child element of the IdentityProofAssuranceLevel descendant element of SenderDetails element is an empty string Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/IDENTITY_ASSURANCE_LEVEL/TA_02 TA Id ERDS/IDENTITTY_ASSURANCE_LEVEL/TA_02 Normative source ETSI EN 319 522-2 [2], clause 8.4 Target Conformance to ERDS Evidence and metadata content Prerequisite The IdentityProofAssuranceLevel element is descendant of the SenderDelegateDetails element AND the AssuranceLevel child element of the IdentityProofAssuranceLevel of SenderDetails element is NOT empty Predicate The value of the AssuranceLevel child element of the IdentityProofAssuranceLevel descendant element of SenderDelegateDetails element is an empty string Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence The following test assertions, derived from the following additional requirement defined in Table 13 of ETSI EN 319 522-2 [2], clause 8.4 and copied below for the sake of completeness, shall also apply. "(c) either "I12 Recipient's identity assurance level detail" component or I13 "Recipient's delegate identity assurance level detail" component shall be present in these evidences". ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 45 ERDS/IDENTITY_ASSURANCE_LEVEL/TA_03 TA Id ERDS/IDENTITTY_ASSURANCE_LEVEL/TA_03 Normative source ETSI EN 319 522-2 [2], clause 8.4 Target Conformance to ERDS Evidence and metadata content Prerequisite The IdentityProofAssuranceLevel element is descendant of one of the RecipientDetails elements AND the AssuranceLevel chilld element of IdentityProofAssuranceLevel of the RecipientsDelegateDetails element, containing the details of the delegate of the aforementioned recipient is NOT empty Predicate The value of the AssuranceLevel child element of the IdentityProofAssuranceLevel descendant element of the aforementioned RecipientDetails element is an empty string Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/IDENTITY_ASSURANCE_LEVEL/TA_04 TA Id ERDS/IDENTITTY_ASSURANCE_LEVEL/TA_04 Normative source ETSI EN 319 522-2 [2], clause 8.4 Target Conformance to ERDS Evidence and metadata content Prerequisite The IdentityProofAssuranceLevel element is descendant of one of the RecipientsDelegateDetails elements containing the details of one delegate AND the AssuranceLevel child element of IdentityProofAssuranceLevel of the RecipientDetails providing details of the recipient whose delegate is the one mentioned before is NOT empty Predicate The value of the AssuranceLevel child element of the IdentityProofAssuranceLevel descendant element of the aforementioned RecipientsDelegateDetails element is an empty string Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	6.22.4.6 Test assertions for FederationAssuranceLevel child element	The test assertions defined in clause 5.4 of the present document shall apply for testing the FederationAssuranceLevel child element of instances of AssuranceLevelsDetailsType type. 7 Test assertions for ERDS metadata structure and contents
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.1 Introduction	The next clauses define the set of test assertions for testing conformance of ERDS metadata against ETSI EN 319 522-3 [3]. The same considerations than the ones detailed in clause 5.1 shall apply in the test assertions defined throughout the whole clause 7. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 46
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.2 Test assertions for RelayMetadata element	ERDS/METADATA/ROOT/TA_01 TA Id ERDS/METADATA/ROOT/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.5 Target Conformance to ERDS Evidence structure Predicate The content of the RelayMetadata XML element, in terms of XML children element is as follows: MessageIdentifier ERDMessageType InReplyTo? RelayTime? ExpirationTime? ScheduledDeliveryTime? SenderId ReplyTo? RecipientId UserContentInfo RequiredAssuranceLevel? ApplicablePolicy? RequestedConsignmentMode? Extensions? ds:Signature? Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/METADATA/ROOT/TA_02 TA Id ERDS/METADATA/ROOT/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.3.5 Target Conformance to ERDS Evidence structure Predicate The set of attributes (leaving apart the attributes declaring namespaces) of the RelayMetadata XML element, is as follows: version Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.3 Test assertions for MessageIdentifier element	The test assertions defined in clause 5.2.6 of the present document shall apply for testing the MessageIdentifier child element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.4 Test assertions for ERDMessageType element	ERDS/METADATA/ERDS_MSSG_TYPE/TA_01 TA Id ERDS/METADATA/ERDS_MSSG_TYPE/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.5 Target Conformance to ERDS Evidence and metadata content Predicate The ERDMessageType element child of RelayMetadata element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/METADATA/ERDS_MSSG_TYPE/TA_02 TA Id ERDS/METADATA/ERDS_MSSG_TYPE/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.5 Target Conformance to ERDS Evidence and metadata content Predicate The ERDMessageType element child of RelayMetadata element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 47 ERDS/METADATA/ERDS_MSSG_TYPE/TA_03 TA Id ERDS/METADATA/ERDS_MSSG_TYPE/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.5 Target Conformance to ERDS Evidence and metadata content Predicate The value of ERDMessageType element child of RelayMetadata element is one of the following values: "http://uri.etsi.org/19522/v1#/ERDMessageType/dispatch" "http://uri.etsi.org/19522/v1#/ERDMessageType/receipt" "http://uri.etsi.org/19522/v1#/ERDMessageType/serviceInfo" "http://uri.etsi.org/19522/v1#/ERDMessageType/payload" Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.5 Test assertions for InReplyTo element	The test assertions defined in clause 5.2.6 of the present document shall apply for testing the InReplyTo child element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.6 Test assertions for RelayTime element	The test assertions defined in clause 5.5 of the present document shall apply for testing the RelayTime child element of RelayMetadata element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.7 Test assertions for ExpirationTime element	The test assertions defined in clause 5.5 of the present document shall apply for testing the ExpirationTime child element of RelayMetadata element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.8 Test assertions for ScheduledDeliveryTime element	The test assertions defined in clause 5.5 of the present document shall apply for testing the ScheduledDeliveryTime child element of RelayMetadata element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.9 Test assertions for SenderId element	The test assertions defined in clause 5.3 of the present document shall apply for testing the SenderId child element of RelayMetadata element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.10 Test assertions for ReplyTo element	The test assertions defined in clause 5.3 of the present document shall apply for testing the ReplyTo child element of RelayMetadata element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.11 Test assertions for RecipientId element	The test assertions defined in clause 5.3 of the present document shall apply for testing the RecipientId child element of RelayMetadata element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.12 Test assertions for UserContentInfo element	The test assertions defined in clause 6.16 of the present document shall apply for testing the UserContentInfo child element of RelayMetadata element. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 48
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.13 Test assertions for RequiredAssuranceLevel element	The test assertions defined in clause 5.4 of the present document shall apply for testing the RequiredAssuranceLevel child element of RelayMetadata element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.14 Test assertions for ApplicablePolicy element	The test assertions defined in clause 5.6 of the present document shall apply for testing the ApplicablePolicy child element.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.15 Test assertions for RequestedConsignmentMode element	ERDS/METADATA/CONSIGNMENT_MODE/TA_01 TA Id ERDS/METADATA/CONSIGNMENT_MODE/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.16 Target Conformance to ERDS Evidence and metadata content Predicate The RequestedConsignmentMode element child of RelayMetadata element does not have any XML children elements Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/METADATA/CONSIGNMENT_MODE/TA_02 TA Id ERDS/METADATA/CONSIGNMENT_MODE/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.16 Target Conformance to ERDS Evidence and metadata content Predicate The RequestedConsignmentMode element child of RelayMetadata element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/METADATA/CONSIGNMENT_MODE/TA_03 TA Id ERDS/METADATA/CONSIGNMENT_MODE/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.16 Target Conformance to ERDS Evidence and metadata content Predicate The value of RequestedConsignmentMode element child of RelayMetadata element is one of the following values: "http://uri.etsi.org/19522/v1#/consignment/basic" "http://uri.etsi.org/19522/v1#/consignment/consent" "http://uri.etsi.org/19522/v1#/consignment/signed" "http://uri.etsi.org/19522/v1#/consignment/other" Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.16 Test assertions for Extensions element	ERDS/METADATA/EXTENSIONS/TA_01 TA Id ERDS/METADATA/EXTENSIONS/TA_01 Normative source ETSI EN 319 522-3 [3], clause 4.3.17 Target Conformance to ERDS Evidence and metadata content Predicate The content of the Extensions element child of RelayMetadata element, in terms of XML elements, is as follows: Extension+ Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 49 ERDS/METADATA/EXTENSIONS/TA_02 TA Id ERDS/METADATA/EXTENSIONS/TA_02 Normative source ETSI EN 319 522-3 [3], clause 4.3.17 Target Conformance to ERDS Evidence and metadata content Predicate The Extensions element child of RelayMetadata element does not have any XML attribute except the attributes declaring namespaces Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/METADATA/EXTENSIONS/TA_03 TA Id ERDS/METADATA/EXTENSIONS/TA_03 Normative source ETSI EN 319 522-3 [3], clause 4.3.17 Target Conformance to ERDS Evidence and metadata content Predicate The set of attributes (leaving apart the attributes declaring namespaces) of the Extension child element of Extensions element, is as follows: isCritical Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence ERDS/METADATA/EXTENSIONS/TA_04 TA Id ERDS/METADATA/EXTENSIONS/TA_04 Normative source ETSI EN 319 522-3 [3], clause 4.3.17 Target Conformance to ERDS Evidence and metadata content Predicate The value of the attribute isCritical of the Extension element is either "true" or "false" Prescription level Mandatory Tag Conformance, ERDS, ERDS Evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	7.17 Test assertions for ds:Signature element	Test assertions defined in ETSI TS 119 134-4 [9] or ETSI TS 119 134-5 [14] shall apply for testing the ds:Signature element child of Evidence if this element is a XAdES signature, depending whether it is a XAdES baseline or a XAdES extended signature, respectively.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	8 Test assertions for ERDS AS4-profile messages
71110a50b9eefbc38d87c6747ddad15a	119 524-1	8.1 8Test assertions for generic requirements	ERDS/SERV_PROV/ERDS_EVID_GEN/TA_01 TA Id ERDS/AS4_PROF/TA_01 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 When using AS4 for the implementation of the relay operation ERDS shall conform to the AS4 ebHandler Conformance Clause and all related features as defined in section 6.1 of AS4 Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate Implementation of the relay operation ERDS conforms to the AS4 ebHandler Conformance Clause and all related features as defined in section 6.1 of [15] Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 50 ERDS/AS4_PROF/TA_02 TA Id ERDS/AS4_PROF/TA_02 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 ERDS shall only use the push message exchange pattern Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate ERDS uses only the push message exchange pattern Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_03 TA Id ERDS/AS4_PROF/TA_03 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 ERD messages shall be packaged in User Messages Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate ERD messages are packaged in User Messages Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_04 TA Id ERDS/AS4_PROF/TA_04 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 The user content, ERDS relay meta-data and ERDS evidence shall be included as ebMS payloads that are packaged as SOAP attachments, i.e. the SOAP Body shall not be used Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The user content, ERDS relay meta-data and ERDS evidence are included as ebMS payloads that are packaged as SOAP attachments Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_05 TA Id ERDS/AS4_PROF/TA_05 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 The user content, ERDS relay meta-data and ERDS evidence shall be included as ebMS payloads that are packaged as SOAP attachments, i.e. the SOAP Body shall not be used Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate SOAP Body is not used Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_06 TA Id ERDS/AS4_PROF/TA_06 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 The AS4 Compression Feature as defined in section 3.1 of the AS4 Profile [15] and which offers the option to compress payloads packaged in the SOAP attachments may be used by the ERDS. Alternatively, the ERDS may use the HTTP gzip transfer-encoding Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate ERDS uses compression Prescription level Optional Tag Conformance, ERDS, ERDSP, AS4 message ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 51 ERDS/AS4_PROF/TA_07 TA Id ERDS/AS4_PROF/TA_07 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 The AS4 Compression Feature as defined in section 3.1 of the AS4 Profile [15] and which offers the option to compress payloads packaged in the SOAP attachments may be used by the ERDS. Alternatively, the ERDS may use the HTTP gzip transfer-encoding Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS uses compression. Predicate ERDS uses either the feature as defined in section 3.1 of [15] or HTTP gzip transfer-encoding Prescription level Optional Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_08 TA Id ERDS/AS4_PROF/TA_08 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 Each payload contained in the AS4 message shall have a part property, i.e. a //PartInfo/Property element shall be included in the message header that indicates the object type of the payload. The name of the property shall be http://uri.etsi.org/19522/v1#as4binding/PayloadType Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate Each payload contained in the AS4 message has a PartInfo/Property element whose XML attribute name has the value http://uri.etsi.org/19522/v1#as4binding/PayloadType Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_09 TA Id ERDS/AS4_PROF/TA_09 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 The value (of the element mentioned in test assertion ERDS/AS4_PROF/TA_08) shall be set according to table 1 of ETSI EN 319 522-4-1 [4] Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The content is the User Content Predicate The value of the PartInfo/Property element whose XML attribute name has the value http://uri.etsi.org/19522/v1#as4binding/PayloadType is "UserContent" Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_10 TA Id ERDS/AS4_PROF/TA_10 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 The value (of the element mentioned in test assertion ERDS/AS4_PROF/TA_08) shall be set according to table 1 Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The content is ERDS Relay metadata Predicate The value of the PartInfo/Property element whose XML attribute name has the value http://uri.etsi.org/19522/v1#as4binding/PayloadType is "ERDSRelayMetadata" Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_11 TA Id ERDS/AS4_PROF/TA_11 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 The value (of the element mentioned in test assertion ERDS/AS4_PROF/TA_08) shall be set according to table 1. Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The content is ERDS Evidence Predicate The value of the PartInfo/Property element whose XML attribute name has the value http://uri.etsi.org/19522/v1#as4binding/PayloadType is "ERDSEvidence". Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 52 ERDS/AS4_PROF/TA_12 TA Id ERDS/AS4_PROF/TA_12 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 the AS4 message shall always include at least one payload containing the XML representation of the metadata as specified in clause 4 of ETSI EN 319 522-3 [3] Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The content is ERDS Evidence Predicate The AS4 message includes one or more payload containing the XML representation of the metadata as specified in clause 4 of ETSI EN 319 522-4-1 [4] Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_13 TA Id ERDS/AS4_PROF/TA_13 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 The PMode.Initiator and PMode.Responder parameters shall include the identifiers of the sending and receiving ERDSs respectively Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The PMode.Initiator parameter includes the identifier of the sending ERDS Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_14 TA Id ERDS/AS4_PROF/TA_14 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 The PMode.Initiator and PMode.Responder parameters shall include the identifiers of the sending and receiving ERDSs respectively Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The PMode.Responder parameter includes the identifier of the receiving ERDS Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_15 TA Id ERDS/AS4_PROF/TA_15 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 Both the PMode.Initiator.Role and PMode.Responder.Role shall contain the value http://uri.etsi.org/19522/v1#/as4binding/Roles/ERDS Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The PMode.Initiator.Role and the PMode.Responder.Role have the value http://uri.etsi.org/19522/v1#/as4binding/Roles/ERDS Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_16 TA Id ERDS/AS4_PROF/TA_16 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 PMode [1].BusinessInfo.Service shall be set to http://uri.etsi.org/19522/v1#/as4binding/Relay Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The value of PMode [1].BusinessInfo.Service is http://uri.etsi.org/19522/v1#/as4binding/Relay Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 53 ERDS/AS4_PROF/TA_17 TA Id ERDS/AS4_PROF/TA_17 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 The Service type shall not be used Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The Service type is not used Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_18 TA Id ERDS/AS4_PROF/TA_18 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 both PMode[1].Security.SendReceipt and PMode[1].Security. SendReceipt.NonRepudiation shall have value true Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate PMode[1].Security.SendReceipt and PMode[1].Security. SendReceipt.NonRepudiation have the value true Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_19 TA Id ERDS/AS4_PROF/TA_19 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 PMode[1].Security.SendReceipt.ReplyPattern and PMode[1].ErrorHandling.Report.AsResponse shall have value true Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate PMode[1].Security.SendReceipt.ReplyPattern and PMode[1].ErrorHandling.Report.AsResponse have the value true Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_20 TA Id ERDS/AS4_PROF/TA_20 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 The AS4 Reception Awareness Feature as specified in section 3.2 of the [15] should be used Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The AS4 Reception Awareness Feature as specified in section 3.2 of [15] is used Prescription level Recommended Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/TA_21 TA Id ERDS/AS4_PROF/TA_21 Normative source ETSI EN 319 522-4-1 [4], clause 5.2 ERDS should use the duplicate elimination function to prevent redundant delivery of the same message to the user application Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate ERDS uses the duplicate elimination function Prescription level Recommended Tag Conformance, ERDS, ERDSP, AS4 message ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 54 8.2 Test assertions for signing and encryption of the AS4 message ERDS/AS4_PROF/SIG_ENC/TA_1 TA Id ERDS/AS4_PROF/SIG_ENC/TA_1 Normative source ETSI EN 319 522-4-1 [4], clause 5.3 All AS4 messages exchanged between the ERDS shall be signed and encrypted by the sending ERDS Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The sending ERDS signs and encrypts all the AS4 messages that it exchanges with other ERDSs Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/SIG_ENC/TA_2 TA Id ERDS/AS4_PROF/SIG_ENC/TA_2 Normative source ETSI EN 319 522-4-1 [4], table 2 in clause 5.3 Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The hash algorithm used for signing and for hashing the encryption key is as specified in ETSI TS 119 312 [16] Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/SIG_ENC/TA_3 TA Id ERDS/AS4_PROF/SIG_ENC/TA_3 Normative source ETSI EN 319 522-4-1 [4], table 2 in clause 5.3 Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The Binary Security Token reference as specified in [i.1] is used Prescription level Recommended Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/SIG_ENC/TA_4 TA Id ERDS/AS4_PROF/SIG_ENC/TA_4 Normative source ETSI EN 319 522-4-1 [4], table 2 in clause 5.3 Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The Binary Security Token reference is used Predicate The Binary Security Token reference references one security token of type X509v3, which is the signing certificate Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/SIG_ENC/TA_5 TA Id ERDS/AS4_PROF/SIG_ENC/TA_5 Normative source ETSI EN 319 522-4-1 [4], table 2 in clause 5.3 Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The signature algorithm is as specified in ETSI TS 119 312 [16] Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/SIG_ENC/TA_6 TA Id ERDS/AS4_PROF/SIG_ENC/TA_6 Normative source ETSI EN 319 522-4-1 [4], table 2 in clause 5.3 Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The encryption algorithm is AES-GCM128 Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 55 ERDS/AS4_PROF/SIG_ENC/TA_7 TA Id ERDS/AS4_PROF/SIG_ENC/TA_7 Normative source ETSI EN 319 522-4-1 [4], table 2 in clause 5.3 Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The encryption key transport algorithm is RSA-OAEP Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/SIG_ENC/TA_8 TA Id ERDS/AS4_PROF/SIG_ENC/TA_8 Normative source ETSI EN 319 522-4-1 [4], table 2 in clause 5.3 Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Predicate The encryption key mask algorithm is MGF1 with SHA256 Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message
71110a50b9eefbc38d87c6747ddad15a	119 524-1	8.3 Test assertions for binding of ERD Dispatch	ERDS/AS4_PROF/ERD_DISPATCH/TA_01 TA Id ERDS/AS4_PROF/ERD_DISPATCH/TA_01 Normative source ETSI EN 319 522-4-1 [4], clause 5.4 When relaying an ERD dispatch using AS4 the sending ERDS shall use http://uri.etsi.org/19522/v1#/as4binding/Actions/ERDdispatch as value for PMode[1].Action Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Dispatch Predicate The value of PMode[1].Action is http://uri.etsi.org/19522/v1#/as4binding/Actions/ERDdispatch Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/ERD_DISPATCH/TA_02 TA Id ERDS/AS4_PROF/ERD_DISPATCH/TA_02 Normative source ETSI EN 319 522-4-1 [4], clause 5.4 For each element //UserContentInfo//PartInfo in the ERDS relay metadata XML document there shall be a payload in the AS4 message Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Dispatch Predicate There is one payload in the AS4 message for each element //UserContentInfo//PartInfo element Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/ERD_DISPATCH/TA_03 TA Id ERDS/AS4_PROF/ERD_DISPATCH/TA_03 Normative source ETSI EN 319 522-4-1 [4], clause 5.4 Beside the part property specified in clause 5.2 that indicates the object type there shall be a part property named http://uri.etsi.org/19522/v1#/as4binding/UserContentPartId Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Dispatch Predicate There is one part property named http://uri.etsi.org/19522/v1#/as4binding/UserContentPartId Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 56 ERDS/AS4_PROF/ERD_DISPATCH/TA_04 TA Id ERDS/AS4_PROF/ERD_DISPATCH/TA_04 Normative source ETSI EN 319 522-4-1 [4], clause 5.4 Beside the part property specified in clause 5.2 that indicates the object type there shall be a part property named http://uri.etsi.org/19522/v1#/as4binding/UserContentPartId and with value the identifier contained in the //UserContentInfo//PartInfo/Identifier element in the metadata Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Dispatch Predicate The value of http://uri.etsi.org/19522/v1#/as4binding/UserContentPartId is the identifier contained in the //UserContentInfo//PartInfo/Identifier element in the metadata Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/ERD_DISPATCH/TA_05 TA Id ERDS/AS4_PROF/ERD_DISPATCH/TA_05 Normative source ETSI EN 319 522-4-1 [4], clause 5.4 Furthermore the message may include one or more payloads containing ERDS evidence(s) Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Dispatch Predicate The message contains one or more payloads containing ERDS evidence Prescription level Optional Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/ERD_DISPATCH/TA_06 TA Id ERDS/AS4_PROF/ERD_DISPATCH/TA_06 Normative source ETSI EN 319 522-4-1 [4], clause 5.4 Furthermore the message may include one or more payloads containing ERDS evidence(s). For each of these payloads the AS4 message header should contain a part property named http://uri.etsi.org/19522/v1#/as4binding/PayloadType with value ERDSEvidence Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Dispatch, which contains one or more payloads containing ERDS evidence Predicate For each of these payloads the AS4 message header contains a part property named http://uri.etsi.org/19522/v1#/as4binding/PayloadType with value ERDSEvidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, AS4 message
71110a50b9eefbc38d87c6747ddad15a	119 524-1	8.4 Test assertions for binding of ERDS Receipt	ERDS/AS4_PROF/ERDS_RECEIPT/TA_01 TA Id ERDS/AS4_PROF/ERDS_RECEIPT/TA_01 Normative source ETSI EN 319 522-4-2 [5], clause 5.3 When relaying an ERDS receipt using AS4 [15] the sending ERDS shall use http://uri.etsi.org/19522/v1#/as4binding/Actions/ERDSreceipt as value for PMode[1].Action Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERDS Receipt Predicate The value of PMode[1].Action is http://uri.etsi.org/19522/v1#/as4binding/Actions/ERDSreceipt Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 57 ERDS/AS4_PROF/ERDS_RECEIPT/TA_02 TA Id ERDS/AS4_PROF/ERDS_RECEIPT/TA_02 Normative source ETSI EN 319 522-4-2 [5], clause 5.3 In addition to the payload containing the ERDS Relay metadata the message shall include one or more payloads containing the ERDS evidence(s). Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERDS Receipt Predicate The message includes one or more payloads containing the ERDS evidence(s) Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message
71110a50b9eefbc38d87c6747ddad15a	119 524-1	8.5 Test assertions for binding of ERD ServiceInfo	ERDS/AS4_PROF/ERD_SVCINFO/TA_01 TA Id ERDS/AS4_PROF/ERD_SCVINFO/TA_01 Normative source ETSI EN 319 522-4-1 [4], clause 5.6 When relaying an ERDS serviceInfo using AS4 the sending ERDS shall use http://uri.etsi.org/19522/v1#/as4binding/Actions/ERDserviceInfo as value for PMode[1].Action Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD ServiceInfo Predicate The value of PMode[1].Action is http://uri.etsi.org/19522/v1#/as4binding/Actions/ERDserviceInfo Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/ERD_SVCINFO/TA_02 TA Id ERDS/AS4_PROF/ERD_SCVINFO/TA_02 Normative source ETSI EN 319 522-4-1 [4], clause 5.6 Beside the payload carrying the ERDS relay metadata the message shall not contain any further payloads Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD ServiceInfo Predicate The message does not contain any other payload than the ERDS relay metadata Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message
71110a50b9eefbc38d87c6747ddad15a	119 524-1	8.6 Test assertions for binding of ERD Payload	ERDS/AS4_PROF/ERD_PAYLOAD/TA_01 TA Id ERDS/AS4_PROF/ERD_PAYLOAD/TA_01 Normative source ETSI EN 319 522-4-1 [4], clause 5.7 When relaying an ERD payload using AS4 the sending ERDS shall use http://uri.etsi.org/19522/v1#/as4binding/Actions/ERDpayload as value for PMode[1].Action Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Payload Predicate The value of PMode[1].Action is http://uri.etsi.org/19522/v1#/as4binding/Actions/ERDpayload Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 58 ERDS/AS4_PROF/ERD_PAYLOAD/TA_02 TA Id ERDS/AS4_PROF/ERD_PAYLOAD/TA_02 Normative source ETSI EN 319 522-4-1 [4], clause 5.7 For each element //UserContentInfo//PartInfo in the ERDS relay metadata XML document there shall be a payload in the AS4 messsage Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Payload Predicate There is one payload in the AS4 message for each element //UserContentInfo//PartInfo element Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/ERD_PAYLOAD/TA_03 TA Id ERDS/AS4_PROF/ERD_PAYLOAD/TA_03 Normative source ETSI EN 319 522-4-1 [4], clause 5.7 For each element //UserContentInfo//PartInfo in the metadata XML document there shall be a payload in the AS4 messsage that has the two part properties: one named http://uri.etsi.org/19522/v1#/as4binding/PayloadType with value UserContentPart and one named http://uri.etsi.org/19522/v1#/as4binding/UserContentPartId and with value the identifier contained in the //UserContentInfo//PartInfo/Identifier element in the metadata Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Payload and there are one or more a payloads corresponding to different //UserContentInfo//PartInfo in the metadata XML document Predicate Each payload has two part properties, named http://uri.etsi.org/19522/v1#/as4binding/PayloadType and http://uri.etsi.org/19522/v1#/as4binding/UserContentPartId respectively Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/ERD_PAYLOAD/TA_04 TA Id ERDS/AS4_PROF/ERD_PAYLOAD/TA_04 Normative source ETSI EN 319 522-4-1 [4], clause 5.7 For each element //UserContentInfo//PartInfo in the metadata XML document there shall be a payload in the AS4 message that has the two part properties: one named http://uri.etsi.org/19522/v1#/as4binding/PayloadType with value UserContentPart and one named http://uri.etsi.org/19522/v1#/as4binding/UserContentPartId and with value the identifier contained in the //UserContentInfo//PartInfo/Identifier element in the metadata Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Payload and there are one or more a payloads corresponding to different //UserContentInfo//PartInfo in the metadata XML document Predicate The value of the property named http://uri.etsi.org/19522/v1#/as4binding/PayloadType is UserContentPart Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 59 ERDS/AS4_PROF/ERD_PAYLOAD/TA_05 TA Id ERDS/AS4_PROF/ERD_PAYLOAD/TA_05 Normative source ETSI EN 319 522-4-1 [4], clause 5.7 For each element //UserContentInfo//PartInfo in the metadata XML document there shall be a payload in the AS4 message that has the two part properties: one named http://uri.etsi.org/19522/v1#/as4binding/PayloadType with value UserContentPart and one named http://uri.etsi.org/19522/v1#/as4binding/UserContentPartId and with value the identifier contained in the //UserContentInfo//PartInfo/Identifier element in the metadata Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Payload and there are one or more a payloads corresponding to different //UserContentInfo//PartInfo in the metadata XML document Predicate The value of the property named http://uri.etsi.org/19522/v1#/as4binding/UserContentPartId is the value of the identifier contained in the //UserContentInfo//PartInfo/Identifier element in the metadata Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message ERDS/AS4_PROF/ERD_PAYLOAD/TA_06 TA Id ERDS/AS4_PROF/ERD_PAYLOAD/TA_06 Normative source ETSI EN 319 522-4-1 [4], clause 5.7 Beside the payloads specified above and the one containing the ERDS Relay metadata there shall be no further payloads included in the message Target Conformance to the AS4 profile as further profiled in ETSI EN 319 522-4-1 [4] Prerequisite The ERDS relays an ERD Payload Predicate The ERD Payload does not contain any other payload than the one containing the ERDS Relay metadata and the payloads corresponding to the//UserContentInfo//PartInfo elements in the metadata XML document Prescription level Mandatory Tag Conformance, ERDS, ERDSP, AS4 message
71110a50b9eefbc38d87c6747ddad15a	119 524-1	9 Test assertions for signatures	REMS/SIGNATURE/TA_01 TA Id ERDS/SIGNATURE/TA_01 Normative source ETSI EN 319 522-2 [2], clause 7.1 An ERDS shall digitally sign all ERD messages Target Conformance to ERDS provision Predicate The ERD messages are signed by the ERDS Prescription level Mandatory Tag Conformance, ERDS, ERDSP, ERD message, signature REMS/SIGNATURE/TA_02 TA Id ERDS/SIGNATURE/TA_02 Normative source ETSI EN 319 522-2 [2], clause 7.1 Each evidence shall be digitally signed as an individual document by the ERDS issuing the evidence, even when the evidence is embedded in a signed ERD message Target Conformance to ERDS provision Predicate The ERDS individually signs each ERDS evidence Prescription level Mandatory Tag Conformance, ERDS, ERDSP, ERDS evidence, signature ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 60 REMS/SIGNATURE/TA_03 TA Id ERDS/SIGNATURE/TA_03 Normative source ETSI EN 319 522-2 [2], clause 7.1 Messages exchanged with the Common Service Interface may be digitally signed; this may apply to both requests and responses Target Conformance to ERDS provision Predicate The ERDS signs requests messages exchanged with the Common Service Interface Prescription level Optional Tag Conformance, ERDS, ERDSP, CSI, signature REMS/SIGNATURE/TA_04 TA Id ERDS/SIGNATURE/TA_04 Normative source ETSI EN 319 522-2 [2], clause 7.1 Messages exchanged with the Common Service Interface may be digitally signed; this may apply to both requests and responses. Target Conformance to ERDS provision Predicate The CSI signs responses messages exchanged with the ERDS Prescription level Optional Tag Conformance, ERDS, ERDSP, CSI, signature REMS/SIGNATURE/TA_05 TA Id ERDS/SIGNATURE/TA_05 Normative source ETSI EN 319 522-2 [2], clause 7.1 Requirements may exist for digitally signing metadata stored in a CSI metadata repository and for conveying these metadata in their signed form Target Conformance to ERDS provision Predicate The metadata stored in a CSI is signed Prescription level Optional Tag Conformance, ERDS, ERDSP, CSI, signature REMS/SIGNATURE/TA_06 TA Id ERDS/SIGNATURE/TA_06 Normative source ETSI EN 319 522-2 [2], clause 7.2 The digital signature should be a CAdES, XAdES or PAdES baseline signature as specified in ETSI EN 319 122-1 [i.2], ETSI EN 319 132-1 [10] and ETSI EN 319 142-1 [i.3] Target Conformance to ERDS provision Predicate The digital signature is a CAdES, XAdES or PAdES baseline signature as specified in ETSI EN 319 122-1 [i.2], ETSI EN 319 132-1 [10] and ETSI EN 319 142-1 [i.3] Prescription level Recommended Tag Conformance, ERDS, ERDSP, CSI, signature REMS/SIGNATURE/TA_07 TA Id ERDS/SIGNATURE/TA_07 Normative source ETSI EN 319 522-2 [2], clause 7.2 The digital signature may include a signed property containing the explicit identifier of the signature policy governing the signing and/or validating processes Target Conformance to ERDS provision Predicate The digital signature includes a signed property containing the explicit identifier of the policy governing the signing and/or validating processes Prescription level Optional Tag Conformance, ERDS, ERDSP, CSI, signature ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 61 REMS/SIGNATURE/TA_08 TA Id ERDS/SIGNATURE/TA_08 Normative source ETSI EN 319 522-2 [2], clause 7.2 A signature time-stamp should be added to the digital signature of evidence Target Conformance to ERDS provision Prerequisite The signature signs an ERDS evidence Predicate A signature time-stamp is added to the signature Prescription level Recommended Tag Conformance, ERDS, ERDSP, CSI, signature
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10 Test assertions for Common Services Interface	10.1 Test assertions of BDXL binding for capability metadata location ERDS/CSI/CAPABILITY/BDXL/TA_01 TA Id ERDS/CSI/CAPABILITY/BDXL/TA _01 Normative source ETSI EN 319 522-4-3 [6], clause 5 The actor identified by the participant identifier is either a recipient or an ERDS, meaning the identified SMP publishes either recipient metadata or ERDS capability metadata as defined by ETSI EN 319 522-2 [2]. Target Conformance to BDXL binding Predicate The SMP publishes either recipient metadata or ERDS capability metadata as defined by ETSI EN 319 522-1 [1] Prescription level Mandatory Tag Conformance, ERDS, ERDSP, CSI bindings, capability metadata location, BDXL ERDS/CSI/CAPABILITY/BDXL/TA_02 TA Id ERDS/CSI/CAPABILITY/BDXL/TA _02 Normative source ETSI EN 319 522-4-3 [6], clause 5 ERDS metadata is defined as an extension to SMP metadata, meaning that ERDS metadata is also stored in SMP. Target Conformance to BDXL binding Predicate The SMP stores the ERDS metadata Prescription level Mandatory Tag Conformance, ERDS, ERDSP, CSI bindings, capability metadata location, BDXL ERDS/CSI/CAPABILITY/BDXL/TA_03 TA Id ERDS/CSI/CAPABILITY/BDXL/TA _03 Normative source ETSI EN 319 522-4-3 [6], clause 5 The identity of an ERDS should be registered in BDXL, i.e. in DNS, by a domain name. Target Conformance to BDXL binding Predicate The identity of an ERDS is registered in BDXL by a domain name in DNS Prescription level Recommended Tag Conformance, ERDS, ERDSP, CSI bindings, capability metadata location, BDXL ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 62 ERDS/CSI/CAPABILITY/BDXL/TA_04 TA Id ERDS/CSI/CAPABILITY/BDXL/TA _04 Normative source ETSI EN 319 522-4-3 [6], clause 5 When a recipient subscribes to more than one ERDS using more than one SMP, either: • the BDXL registration for the recipient shall resolve to one and the same SMP, which in turn may include pointers (SMP redirection) to other SMPs holding information about the recipient; or • the recipient identification shall be coupled with a domain, which may be the ERDS name or other information, thereby creating multiple participant identifiers that in BDXL may resolve to URIs for different SMPs Target Conformance to BDXL binding Prerequisite One recipient subscribes to more than one ERDS using more than one SMP Predicate Either the BDXL registration for the recipient resolves to one and the same SMP or the identification of the recipient is coupled with a domain Prescription level Mandatory Tag Conformance, ERDS, ERDSP, CSI bindings, capability metadata location, BDXL ERDS/CSI/CAPABILITY/BDXL/TA_05 TA Id ERDS/CSI/CAPABILITY/BDXL/TA _05 Normative source ETSI EN 319 522-4-3 [6], clause 5 When a recipient subscribes to more than one ERDS using more than one SMP, either: • the BDXL registration for the recipient shall resolve to one and the same SMP, which in turn may include pointers (SMP redirection) to other SMPs holding information about the recipient; or • the recipient identification shall be coupled with a domain, which may be the ERDS name or other information, thereby creating multiple participant identifiers that in BDXL may resolve to URIs for different SMPs Target Conformance to BDXL binding Prerequisite One recipient subscribes to more than one ERDS using more than one SMP and the BDXL registration for the recipient resolves to one and the same SMP Predicate The SMP contains pointer to other SMPs holding information about the recipient Prescription level Optional Tag Conformance, ERDS, ERDSP, CSI bindings, capability metadata location, BDXL ERDS/CSI/CAPABILITY/BDXL/TA_06 TA Id ERDS/CSI/CAPABILITY/BDXL/TA _06 Normative source ETSI EN 319 522-4-3 [6], clause 5 When a recipient subscribes to more than one ERDS using more than one SMP, either: • the BDXL registration for the recipient shall resolve to one and the same SMP, which in turn may include pointers (SMP redirection) to other SMPs holding information about the recipient; or • the recipient identification shall be coupled with a domain, which may be the ERDS name or other information, thereby creating multiple participant identifiers that in BDXL may resolve to URIs for different SMPs Target Conformance to BDXL binding Prerequisite One recipient subscribes to more than one ERDS using more than one SMP and the recipient identification is coupled with a domain Predicate The domain is either the ERDS name or other information Prescription level Optional Tag Conformance, ERDS, ERDSP, CSI bindings, capability metadata location, BDXL ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 63
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2 Test assertions of SMP binding for metadata publishing
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2.1 Test assertions for ERDS capabilities metadata format
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2.1.1 Test assertions for ERDSMetadata element	ERDS/CSI/PUBLISHING/SMP/CAP_FORMAT/TA_01 TA Id ERDS/CSI/PUBLISHING/SMP/CAP_FORMAT/TA_01 Normative source ETSI EN 319 522-3 [3], clause 6.3.2 ERDS capabilities metadata XML schema Target Conformance to SMP binding Predicate The content of ERDSMetadata element, in terms of XML children element is as follows: ERDSId ERDSDomain ERDSGoverningBody ERDSProfileSupported ERDSMetadataRepository? ERDSEUQualifiedIndicator? ERDSTLLocation? ERDSRootCACertLocation? ERDSExpiryDateAndTimeSupport ERDSScheduledDeliverySupport ERDSAssuranceLevelsSupported? ERDSPolicySupport? ERDSSupportedConsignmentModes? Prescription level Mandatory Tag Conformance, ERDS, ERDSP, CSI bindings, metadata publishing, SMP ERDS/CSI/PUBLISHING/SMP/CAP_FORMAT/TA_02 TA Id ERDS/CSI/PUBLISHING/SMP/CAP_FORMAT/TA_02 Normative source ETSI EN 319 522-3 [3], clause 6.3.2 ERDS capabilities metadata XML schema Target Conformance to SMP binding Predicate The set of attributes (leaving apart the attributes declaring namespaces) of the ERDSMetadata XML element, is as follows: version Prescription level Mandatory Tag Conformance, ERDS, ERDSP, CSI bindings, metadata publishing, SMP ERDS/CSI/PUBLISHING/SMP/CAP_FORMAT/TA_03 TA Id ERDS/CSI/PUBLISHING/SMP/CAP_FORMAT/TA_03 Normative source ETSI EN 319 522-3 [3], clause 6.3.2 Meta-data documents shall have "EN319522v1.1.1" as value for version attribute Target Conformance to SMP binding Predicate The value of the version attribute is "EN319522v1.1.1" Prescription level Mandatory Tag Conformance, ERDS, ERDSP, CSI bindings, metadata publishing, SMP
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2.1.2 Test assertions for ERDSId element	Test assertions defined in clause 5.3 of the present document shall apply.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2.1.3 Test assertions for ERDSDomain element	Test assertions defined in clause 5.2.6 of the present document shall apply.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2.1.4 Test assertions for ERDSGoverningBody element	Test assertions defined in clause 5.2.6 of the present document shall apply.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2.1.5 Test assertions for ERDSProfileSupported element	Test assertions defined in clause 5.2.2 of the present document shall apply. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 64
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2.1.6 Test assertions for ERDSMetadataRepository element	Test assertions defined in clause 5.2.2 of the present document shall apply.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2.1.7 Test assertions for ERDSEUQualifiedIndicator element	Test assertions defined in clause 5.2.8 of the present document shall apply.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2.1.8 Test assertions for ERDSTLLocation element	Test assertions defined in clause 5.2.2 of the present document shall apply.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2.1.9 Test assertions for ERDSRootCACertLocation element	Test assertions defined in clause 5.2.2 of the present document shall apply. 10.2.1.10 Test assertions for ERDSExpiryDateAndTimeSupport element Test assertions defined in clause 5.2.8 of the present document shall apply. 10.2.1.11 Test assertions for ERDSScheduledDeliverySupport element Test assertions defined in clause 5.2.8 of the present document shall apply. 10.2.1.12 Test assertions for ERDSAssuranceLevelsSupported element Test assertions defined in clause 5.4 of the present document shall apply. 10.2.1.13 Test assertions for ERDSPolicySupport element Test assertions defined in clause 5.6 of the present document shall apply. 10.2.1.14 Test assertions for ERDSSupportedConsignmentModes element Test assertions defined in clause 7.15 of the present document shall apply. ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 65
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.2.2 Test assertions for metadata publishing	ERDS/CSI/PUBLISHING/SMP/TA_01 TA Id ERDS/CSI/PUBLISHING/SMP/TA_01 Normative source ETSI EN 319 522-3 [3], clause 6.3.2 For ERDSMetadata as an extension to SMP, the following values shall be used for identification of the extension and the responsible agency: ExtensionID: "ERDSMetadata" ExtensionName: "ERDSMetadata" ExtensionAgencyID: "ETSI" ExtensionAgencyName: "European Telecommunications Standards Institute" ExtensionAgencyURI: "http://www.etsi.org" ExtensionVersionID: Same as version attribute of the ERDS metadata ExtensionURI: "http://uri.etsi.org/19522/v1#ERDSMetadata" ExtensionReasonCode: "ERDSMetadata" ExtensionReason: "Publish capability metadata for an Electronic Registered Delivery Service" Target Conformance to SMP binding The ERDSMetadata is used as an extension to SMP Predicate The following values are used: ExtensionID: "ERDSMetadata" ExtensionName: "ERDSMetadata" ExtensionAgencyID: "ETSI" ExtensionAgencyName: "European Telecommunications Standards Institute" ExtensionAgencyURI: "http://www.etsi.org" ExtensionVersionID: Same as version attribute of the ERDS metadata ExtensionURI: "http://uri.etsi.org/19522/v1#ERDSMetadata" ExtensionReasonCode: "ERDSMetadata" ExtensionReason: "Publish capability metadata for an Electronic Registered Delivery Service" Prescription level Optional Tag Conformance, ERDS, ERDSP, CSI bindings, metadata publishing, SMP ERDS/CSI/PUBLISHING/SMP/TA_02 TA Id ERDS/CSI/PUBLISHING/SMP/TA_02 Normative source ETSI EN 319 522-3 [3], clause 6 If more than one ServiceMetadata resource exists (…) selection shall be based on document identifier and/or process identifier Target Conformance to SMP binding Prerequisite There are more than one resource with service metadata Predicate The selection is done based on the document identifier and/or the process identifier Prescription level Optional Tag Conformance, ERDS, ERDSP, CSI bindings, metadata publishing, SMP ERDS/CSI/PUBLISHING/SMP/TA_03 TA Id ERDS/CSI/PUBLISHING/SMP/TA_03 Normative source ETSI EN 319 522-3 [3], clause 6 A service in the SMP data model is a URL, which in the context of the present document is the ERDS RI to which the ERD message shall be routed Target Conformance to SMP binding Predicate The ERDS RI where the ERD message is routed to is identified by an URL Prescription level Mandatory Tag Conformance, ERDS, ERDSP, CSI bindings, metadata publishing, SMP ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 66
71110a50b9eefbc38d87c6747ddad15a	119 524-1	10.3 Test assertions for trust information binding	ERDS/CSI/TRUST/TA_01 TA Id ERDS/CSI/TRUST/TA_01 Normative source ETSI EN 319 522-4-3 [6], clause 7.2 An ERDS that has been granted status as a qualified trust service according to Regulation (EU) No 910/2014, i.e. the service is a QERDS, shall be listed in the EU Trusted List system established in accordance with article 22 of Regulation (EU) No 910/2014 [i.4] Target Conformance to CSI Trust information Prerequisite An ERDS that has been granted status as a qualified trust service according to Regulation (EU) No 910/2014 [i.4] Predicate The ERDS service is listed in the EU Trusted List system established in accordance with article 22 of Regulation (EU) No 910/2014 Prescription level Mandatory Tag Conformance, QERDS, ERDSP, CSI bindings, trust information, Trusted List ERDS/CSI/TRUST/TA_02 TA Id ERDS/CSI/TRUST/TA_02 Normative source ETSI EN 319 522-4-3 [6], clause 7.2 The following service type identifiers URLs are supported for a (Q)ERDS according to ETSI TS 119 612 [i.5] Target Conformance to CSI Trust information Prerequisite An ERDS or a QERDS is listed in the EU Trusted List system Predicate The service type identifier component is present in the Trusted List Prescription level Mandatory Tag Conformance, QERDS, ERDSP, CSI bindings, trust information, Trusted List ERDS/CSI/TRUST/TA_03 TA Id ERDS/CSI/TRUST/TA_03 Normative source ETSI EN 319 522-4-3 [6], clause 7.2 The following service type identifiers URLs are supported for a (Q)ERDS according to ETSI TS 119 612 [i.5]: • http://uri.etsi.org/TrstSvc/Svctype/EDS/Q • http://uri.etsi.org/TrstSvc/Svctype/EDS Target Conformance to CSI Trust information Prerequisite A non-Qualified ERDS is listed in an EU Trusted List Predicate The value of the service type identifier component is http://uri.etsi.org/TrstSvc/Svctype/EDS Prescription level Mandatory Tag Conformance, QERDS, ERDSP, CSI bindings, trust information, Trusted List ERDS/CSI/TRUST/TA_04 TA Id ERDS/CSI/TRUST/TA_04 Normative source ETSI EN 319 522-4-3 [6], clause 7.2 The following service type identifiers URLs are supported for a (Q)ERDS according to ETSI TS 119 612 [i.5]: • http://uri.etsi.org/TrstSvc/Svctype/EDS/Q • http://uri.etsi.org/TrstSvc/Svctype/EDS Target Conformance to CSI Trust information Prerequisite A Qualified ERDS is listed in an EU Trusted List Predicate The value of the service type identifier component is http://uri.etsi.org/TrstSvc/Svctype/EDS/Q Prescription level Mandatory Tag Conformance, QERDS, ERDSP, CSI bindings, trust information, Trusted List ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 67 ERDS/CSI/TRUST/TA_05 TA Id ERDS/CSI/TRUST/TA_05 Normative source ETSI EN 319 522-4-3 [6], clause 7.2 The service digital identity element (tsl:ServiceDigitalIdentity/tsl:DigitalId) of a (Q)ERDS in the EU Trusted List system shall be one of the following: • A single certificate used by the ERDS for digital signing of all ERD messages and ERD evidences • A single CA certificate that shall be used solely for the purpose of issuing certificates to components of the ERDS for digital signing of ERD messages and/or ERD evidences Target Conformance to CSI Trust information Prerequisite A (Q)ERDS is listed in an EU Trusted List Predicate The service digital identity contains a certificate Prescription level Mandatory Tag Conformance, QERDS, ERDSP, CSI bindings, trust information, Trusted List ERDS/CSI/TRUST/TA_06 TA Id ERDS/CSI/TRUST/TA_06 Normative source ETSI EN 319 522-4-3 [6], clause 7.2 Use of a single signing certificate as service digital identity is only applicable where the ERDS is a centralized service, or where it is feasible to replicate the private key corresponding to the certificate to all components of the ERDS where digital signing will take place Target Conformance to CSI Trust information Prerequisite A (Q)ERDS is listed in an EU Trusted List AND • the ERDS is centralized; OR • it is feasible to replicate the private key corresponding to the certificate to all components of the ERDS where digital signing will take place Predicate The service digital identity contains a non-CA certificate Prescription level OPTIONAL Tag Conformance, QERDS, ERDSP, CSI bindings, trust information, Trusted List ERDS/CSI/TRUST/TA_07 TA Id ERDS/CSI/TRUST/TA_07 Normative source ETSI EN 319 522-4-3 [6], clause 7.2 The service digital identity element (tsl:ServiceDigitalIdentity/tsl:DigitalId) of a (Q)ERDS in the EU Trusted List system shall be one of the following: • A single certificate used by the ERDS for digital signing of all ERD messages and ERD evidences • A single CA certificate that shall be used solely for the purpose of issuing certificates to components of the ERDS for digital signing of ERD messages and/or ERD evidences Target Conformance to CSI Trust information Prerequisite A (Q)ERDS is listed in an EU Trusted List AND the service digital identity contains a non-CA certificate Predicate The service digital identity contains the single certificate used by the ERDS for digital signing of all ERD messages and ERD evidences Prescription level OPTIONAL Tag Conformance, QERDS, ERDSP, CSI bindings, trust information, Trusted List ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 68 ERDS/CSI/TRUST/TA_08 TA Id ERDS/CSI/TRUST/TA_08 Normative source ETSI EN 319 522-4-3 [6], clause 7.2 The service digital identity element (tsl:ServiceDigitalIdentity/tsl:DigitalId) of a (Q)ERDS in the EU Trusted List system shall be one of the following: • A single certificate used by the ERDS for digital signing of all ERD messages and ERD evidences • A single CA certificate that shall be used solely for the purpose of issuing certificates to components of the ERDS for digital signing of ERD messages and/or ERD evidences Target Conformance to CSI Trust information Prerequisite A (Q)ERDS is listed in an EU Trusted List and the service digital identity contains a CA certificate Predicate The service digital identity contains the CA certificate that is used solely for issuing certificates to components of the ERDS for digital signing of ERD messages and/or ERD evidences Prescription level Mandatory Tag Conformance, QERDS, ERDSP, CSI bindings, trust information, Trusted List ERDS/CSI/TRUST/TA_09 TA Id ERDS/CSI/TRUST/TA_09 Normative source ETSI EN 319 522-4-3 [6], clause 7.2 All subject certificates issued under this CA (the one whose certificate appears in the service digital identity component of the Trusted List) are authorized to sign ERD messages and ERD evidences on behalf of the ERDS Target Conformance to CSI Trust information Prerequisite A (Q)ERDS is listed in an EU Trusted List and the service digital identity contains a CA certificate Predicate Any signature generated with the private key corresponding to a certificate whose subject has a path to that CA certificate is considered generated on behalf of the ERDS Prescription level Mandatory Tag Conformance, QERDS, ERDSP, CSI bindings, trust information, Trusted List
71110a50b9eefbc38d87c6747ddad15a	119 524-1	11 Test assertions for provision of the service
71110a50b9eefbc38d87c6747ddad15a	119 524-1	11.1 Introduction	The present clause contains test assertions directly related with the provision of the service itself, namely: 1) The generation of ERDS evidence in response to the occurrence of an event. 2) The provision of security features, like confidentiality. 11.2 Test assertions on generation of ERDS evidence in response to events ERDS/SERV_PROV/ERDS_EVID_GEN/TA_01 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_01 Normative source ETSI EN 319 522-1 [1], clause 6.1 (A.1) Generation of SubmissionAcceptance ERDS evidence following the acceptance of the user content sent by sender is mandatory Target Conformance to generation of ERDS evidence following acceptance of user content acceptance Prerequisite Sender has submitted the user content to the S-ERDS and it has accepted submission Predicate The S-ERDS issues a compliant SubmissionAcceptance ERDS evidence Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 69 ERDS/SERV_PROV/ERDS_EVID_GEN/TA_02 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_02 Normative source ETSI EN 319 522-1 [1], clause 6.1 (A.2) Generation of SubmissionRejection ERDS evidence following the rejection of the user content sent by sender is mandatory Target Conformance to generation of ERDS evidence following rejection of user content acceptance Prerequisite Sender has submitted the user content to the S-ERDS and it has rejected submission Predicate The S-ERDS issues a compliant SubmissionRejection ERDS evidence identifying the reason for rejection Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_03 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_03 Normative source ETSI EN 319 522-1 [1], clause 6.1 (B.1) Generation of RelayAcceptance ERDS evidence following the acceptance of the relaying of a ERDS message requested by another ERDS is Mandatory Target Conformance to generation of ERDS evidence following acceptance of relaying Prerequisite Another ERDS has relayed a ERDS message to the ERDS and it has accepted relying it Predicate The ERDS issues a compliant RelayAcceptance ERDS evidence Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_04 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_04 Normative source ETSI EN 319 522-1 [1], clause 6.1 (B.2) Generation of RelayRejection ERDS evidence following the rejection of the relaying of a ERDS message requested by another ERDS is Mandatory Target Conformance to generation of ERDS evidence following rejection of relaying Prerequisite Another ERDS has relayed a ERDS message to the ERDS and it has rejected relying it Predicate The ERDS issues a compliant RelayRejection ERDS evidence identifying the reason for rejection Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_05 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_05 Normative source ETSI EN 319 522-1 [1], clause 6.1 (B.3) Generation of RelayFailure ERDS evidence following failure of the relaying of a ERDS message requested by another ERDS is Mandatory Target Conformance to generation of ERDS evidence following failure of relaying Prerequisite Another ERDS has relayed a ERDS message to the ERDS and it has failed when it tried to relay it Predicate The ERDS issues a compliant RelayFailure ERDS evidence Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_06 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_06 Normative source ETSI EN 319 522-1 [1], clause 6.1 (C.1) Generation of NotificationForAcceptance ERDS evidence following the successful issuance of a notification requesting the acceptance of a message to a recipient at a specific time as indicated by the evidence, is recommended Target Conformance to generation of ERDS evidence following successful issuance of a notification for acceptance Prerequisite The ERDS has successfully sent a notification for acceptance Predicate The ERDS issues a compliant NotificationForAcceptance ERDS evidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 70 ERDS/SERV_PROV/ERDS_EVID_GEN/TA_07 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_07 Normative source ETSI EN 319 522-1 [1], clause 6.1 (C.2) Generation of NotificationForAcceptanceFailure ERDS evidence following the unsuccessful issuance of a notification requesting the acceptance of a message to the specified recipient after a certain number of attempts or a timeout as specified by the applicable policies, is recommended Target Conformance to generation of ERDS evidence following unsuccessful issuance of a notification for acceptance Prerequisite The ERDS has failed in sending a notification for acceptance Predicate The ERDS issues a compliant NotificationForAcceptanceFailure ERDS evidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_08 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_08 Normative source ETSI EN 319 522-1 [1], clause 6.1 (C.3) Generation of ConsignmentAcceptance ERDS evidence following consignment acceptance by the recipient is recommended Target Conformance to generation of ERDS evidence following consignment acceptance by the recipient Prerequisite The recipient has accepted consignment Predicate The ERDS issues a compliant ConsignmentAcceptance ERDS evidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_09 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_09 Normative source ETSI EN 319 522-1 [1], clause 6.1 (C.4) Generation of ConsignmentRejection ERDS evidence following consignment rejection by the recipient is recommended Target Conformance to generation of ERDS evidence following consignment rejection by the recipient Prerequisite The recipient has rejected consignment. Predicate The ERDS issues a compliant ConsignmentRejection ERDS evidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_10 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_10 Normative source ETSI EN 319 522-1 [1], clause 6.1 (C.5) Generation of AcceptancetRejectionExpiry ERDS evidence following the expiration of the time for reacting to a notification for acceptance without any reaction, is recommended Target Conformance to generation of ERDS evidence following expiration of the time for reacting to a notification for acceptance without any reaction by the recipient Prerequisite The recipient has not reacted to a notification for acceptance before the expiration time assigned to that notification Predicate The ERDS issues a compliant AcceptancetRejectionExpiry ERDS evidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_11 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_11 Normative source ETSI EN 319 522-1 [1], clause 6.1 (C.6) Generation of NotificationDelivered ERDS evidence following the expiration of the time for reacting to a notification for acceptance without any reaction, is recommended Target Conformance to generation of ERDS evidence following the successful notification to the recipient about the availability of a message Prerequisite The ERDS has successfully submitted a notification of availability of a message to the recipient Predicate The ERDS issues a compliant NotificationDelivered ERDS evidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 71 ERDS/SERV_PROV/ERDS_EVID_GEN/TA_12 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_12 Normative source ETSI EN 319 522-1 [1], clause 6.1 (D.1) Generation of ContentConsignment ERDS evidence following the successful consignment of the user content Target Conformance to generation of ERDS evidence following successful consignment of the user content Prerequisite The ERDS has successfully consigned the user content Predicate The ERDS issues a compliant ContentConsignment ERDS evidence Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_13 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_13 Normative source ETSI EN 319 522-1 [1], clause 6.1 (D.2) Generation of ContentConsignmentFailure ERDS evidence following the unsuccessful consignment of the user content Target Conformance to generation of ERDS evidence following unsuccessful consignment of the user content Prerequisite The ERDS has failed in consigning the user content Predicate The ERDS issues a compliant ContentConsignmentFailure ERDS evidence Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_14 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_14 Normative source ETSI EN 319 522-1 [1], clause 6.1 (D.3) Generation of ConsignmentNotification ERDS evidence following the successful submission of a notification for consignment, is recommended Target Conformance to generation of ERDS evidence following successful submission of a notification for consignment Prerequisite The ERDS has successfully submitted a notification for consignment Predicate The ERDS issues a compliant ConsignmentNotification ERDS evidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_15 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_15 Normative source ETSI EN 319 522-1 [1], clause 6.1 (D.4) Generation of ConsignmentNotificationFailure ERDS evidence following failure in the submission of a notification for consignment, is recommended Target Conformance to generation of ERDS evidence following unsuccessful submission of a notification for consignment Prerequisite The ERDS has failed in submitting a notification for consignment Predicate The ERDS issues a compliant ConsignmentNotificationFailure ERDS evidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_16 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_16 Normative source ETSI EN 319 522-1 [1], clause 6.1 (D.5) Generation of NotificationAccessTracking ERDS evidence following the access by the recipient to a notification sent to the recipient Target Conformance to generation of ERDS evidence following submission of a notification Prerequisite The ERDS has submitted a notification Predicate The ERDS issues a compliant NotificationAccessTracking ERDS evidence Prescription level Optional Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 72 ERDS/SERV_PROV/ERDS_EVID_GEN/TA_17 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_17 Normative source ETSI EN 319 522-1 [1], clause 6.1 (D.6) Generation of ContentAccessTracking ERDS evidence following the submission of a notification, is optional Target Conformance to generation of ERDS evidence following the access to the user content by the recipient Prerequisite The recipient has accessed to the user content Predicate The ERDS issues a compliant ContentAccessTracking ERDS evidence Prescription level Optional Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_18 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_18 Normative source ETSI EN 319 522-1 [1], clause 6.1 (E.1) Generation of ContentHandover ERDS evidence following the successful handing over of the user content is conditionated Target Conformance to generation of ERDS evidence following successful handing of the user content Prerequisite The ERDS has successfully handed over the user content and did not consigned it Predicate The ERDS issues a compliant ContentHandover ERDS evidence Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_19 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_19 Normative source ETSI EN 319 522-1 [1], clause 6.1 (E.1) Generation of ContentHandover ERDS evidence following the successful handing over of the user content is conditionated Target Conformance to generation of ERDS evidence following successful handing of the user content Prerequisite The ERDS has successfully handed over the user content and also did consign it Predicate The ERDS issues a compliant ContentHandover ERDS evidence Prescription level Optional Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_20 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_20 Normative source ETSI EN 319 522-1 [1], clause 6.1 (E.2) Generation of ContentHandoverFailure ERDS evidence following the unsuccessful handing over of the user content is conditionated Target Conformance to generation of ERDS evidence following unsuccessful handing over of the user content Prerequisite The ERDS has failed in handing over the user content and ERDS did not try to consign it. Predicate The ERDS issues a compliant ContentHandoverFailure ERDS evidence Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_21 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_21 Normative source ETSI EN 319 522-1 [1], clause 6.1 (E.2) Generation of ContentHandoverFailure ERDS evidence following the unsuccessful handing over of the user content is conditionated Target Conformance to generation of ERDS evidence following unsuccessful handing over of the user content Prerequisite The ERDS has failed in handing over the user content and ERDS did try to consign it Predicate The ERDS issues a compliant ContentHandoverFailure ERDS evidence Prescription level Optional Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 73 ERDS/SERV_PROV/ERDS_EVID_GEN/TA_22 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_22 Normative source ETSI EN 319 522-1 [1], clause 6.1 (F.1) Generation of RelayToNonERDS ERDS evidence following successful relaying of the user content to a non ERDS system, is recommended Target Conformance to generation of ERDS evidence following successful relaying of the user content to a non ERDS system Prerequisite The ERDS has relayed the user content to a non ERDS system Predicate The ERDS issues a compliant RelayToNonERDS ERDS evidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_23 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_23 Normative source ETSI EN 319 522-1 [1], clause 6.1 (F.2) Generation of RelayToNonERDSFailure ERDS evidence following unsuccessful relaying of the user content to a non ERDS system, is recommended Target Conformance to generation of ERDS evidence following unsuccessful relaying of the user content to a non ERDS system Prerequisite The ERDS has failed in relaying the user content to a non ERDS system Predicate The ERDS issues a compliant RelayToNonERDSFailure ERDS evidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence ERDS/SERV_PROV/ERDS_EVID_GEN/TA_24 TA Id ERDS/SERV_PROV/ERDS_EVID_GEN/TA_24 Normative source ETSI EN 319 522-1 [1], clause 6.1 (F.3) Generation of ReceivedFromNonERDS ERDS evidence following reception of a message coming from a non ERDS system, is recommended Target Conformance to generation of ERDS evidence following reception of a message coming from a non ERDS system Prerequisite The ERDS has received a message from a non ERDS system Predicate The ERDS issues a compliant ReceivedFromNonERDS ERDS evidence Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS evidence
71110a50b9eefbc38d87c6747ddad15a	119 524-1	11.3 Test assertions on ERDS interfaces
71110a50b9eefbc38d87c6747ddad15a	119 524-1	11.3.1 Introduction	Clause 11.3 defines test assertions on ERDS interfaces. Clause 11.3.2 defines test assertions for testing security measures implemented in ERDS interfaces. Clause 11.3.3 defines test assertions for testing the provision of the ERDS interfaces.
71110a50b9eefbc38d87c6747ddad15a	119 524-1	11.3.2 Security measures on ERDS interfaces	ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_01 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_01 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (MSI: Message Submission Interface) shall require authentication (…) preserving measures. Target Conformance to security requirements in interfaces Predicate The ERDS ensures authentication for interactions through the Message Submission Interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, authentication ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 74 ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_02 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_02 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (MERI: Message and Evidence Retrieval Interface) shall require authentication (…) preserving measures Target Conformance to security requirements in interfaces Predicate The ERDS ensures authentication for interactions through the Message and Evidence Retrieval Interface. Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, authentication ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_03 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_03 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (ERD-UA MEPI: Message and Evidence Push Interface) shall implement authentication (…) preserving measures Target Conformance to security requirements in interfaces Predicate The ERDS ensures authentication for interactions through the Message and Evidence Push Interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, authentication ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_04 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_04 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (ERDS RI: Relay Interface) shall implement authentication (…) preserving measures Target Conformance to security requirements in interfaces Predicate The ERDS ensures authentication for interactions through the Relay Interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, authentication ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_05 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_05 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (MSI: Message Submission Interface) shall implement confidentiality (…) preserving measures Target Conformance to security requirements in interfaces Predicate The ERDS implements measures for preserving confidentiality through the Message Submission Interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, confidentiality ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_06 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_06 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (MERI: Message and Evidence Retrieval Interface) shall implement confidentiality (…) preserving measures Target Conformance to security requirements in interfaces Predicate The ERDS implements measures for preserving confidentiality through the Message and Evidence Retrieval Interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, confidentiality ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 75 ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_07 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_07 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (ERD-UA MEPI: Message and Evidence Push Interface) shall implement confidentiality (…) preserving measures Target Conformance to security requirements in interfaces Predicate The ERDS implements measures for preserving confidentiality through the Message and Evidence Push Interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, confidentiality ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_08 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_08 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (ERDS RI: Relay Interface) shall implement confidentiality (…) preserving measures Target Conformance to security requirements in interfaces Predicate The ERDS implements measures for preserving confidentiality through the Relay Interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, confidentiality ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_09 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_09 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (MSI: Message Submission Interface) shall implement integrity preserving measures Target Conformance to security requirements in interfaces Predicate The ERDS implements measures for preserving integrity through the Message Submission Interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, integrity ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_10 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_10 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (MERI: Message and Evidence Retrieval Interface) shall implement integrity preserving measures Target Conformance to security requirements in interfaces Predicate The ERDS implements measures for preserving integrity through the Message and Evidence Retrieval Interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, integrity ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_11 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_11 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (ERD-UA MEPI: Message and Evidence Push Interface) shall implement integrity preserving measures Target Conformance to security requirements in interfaces Predicate The ERDS implements measures for preserving integrity through the Message and Evidence Push Interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, integrity ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 76 ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_12 TA Id ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_12 Normative source ETSI EN 319 522-1 [1], clause 5 This interface (ERDS RI: Relay Interface) shall implement integrity preserving measures Target Conformance to security requirements in interfaces Predicate The ERDS implements measures for preserving integrity through the Relay Interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, integrity
71110a50b9eefbc38d87c6747ddad15a	119 524-1	11.3.3 Test assertions on provision of ERDS interfaces	ERDS/SERV_PROV/INTFACE/PROV/TA_01 TA Id ERDS/SERV_PROV/INTFACE/PROV/TA_01 Normative source ETSI EN 319 522-1 [1], clause 5 The ERDS MSI shall be provided Target Conformance to security requirements in interfaces Predicate The ERDS provides the ERDS MSI interface Prescription level Mandatory Tag Conformance, ERDS, ERDSP, service provision, ERDS interfaces ERDS/SERV_PROV/INTFACE/PROV/TA_02 TA Id ERDS/SERV_PROV/INTFACE/PROV/TA_02 Normative source ETSI EN 319 522-1 [1], clause 5 An ERDS hall implement (…) either ERDS MERI or ERDS UA-MEPI (or both) Target Conformance to security requirements in interfaces Predicate The ERDS provides either the ERDS MERI interface, or ERDS UA-MEPI or both Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS interfaces ERDS/SERV_PROV/INTFACE/PROV/TA_03 TA Id ERDS/SERV_PROV/INTFACE/PROV/TA_03 Normative source ETSI EN 319 522-1 [1], clause 5 The ERDS RI should be provided Target Conformance to security requirements in interfaces Predicate The ERDS provides the ERDS RI interface Prescription level Recommended Tag Conformance, ERDS, ERDSP, service provision, ERDS interfaces ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 77 Annex A (informative): Change History Date Version Information about changes February 2019 1.1.1 Publication as ETSI TS 119 524-1. April 2023 1.1.2 Early draft - update version 1.1.1 with resolutions to part of the comments received from stakeholders on version 1.1.1 October 2023 1.1.3 Final draft for TS Approval. This version includes the implementation of resolutions to all the comments received to versions v1.1.1 and v1.1.2. Of important relevance are test assertions derived from the definition of three new events and their corresponding ERDS evidence in ETSI EN 319 522-1 clause 6, namely: NotificationDelivered (C.6), NotificationAccessTracking (D.5), and ContentAccessTracking (D.6) October 2023 1.1.4 Final draft for TS Approval. Correct reference to the WorkItem. Fixed some editorial bugs ETSI ETSI TS 119 524-1 V1.2.1 (2023-12) 78 History Document history V1.1.1 February 2019 Publication V1.2.1 December 2023 Publication
850dac4f6e123a5ed970cb08892924a6	119 144-3	1 Scope	The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to additional PAdES signatures profiles [3]. The present document defines test suites for each profile defined in ETSI EN 319 142-2 [3]. Test suites also cover augmentation of additional PAdES signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
850dac4f6e123a5ed970cb08892924a6	119 144-3	2 References
850dac4f6e123a5ed970cb08892924a6	119 144-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 are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] ISO 32000-1: "Document management - Portable document format - Part 1: PDF 1.7". NOTE: Available at http://www.adobe.com/devnet/acrobat/pdfs/PDF32000_2008.pdf. [2] ETSI EN 319 132-1: "Electronic Signatures and Infrastructures (ESI); XAdES digital signatures; Part 1: Building blocks and XAdES baseline signatures". [3] ETSI EN 319 142-2: " Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 2: Additional PAdES signatures profiles". [4] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures". [5] IETF RFC 6960: "X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSP". [6] IETF RFC 5280 (2008): "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 6
850dac4f6e123a5ed970cb08892924a6	119 144-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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 119 144-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 1: Overview". [i.2] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.3] ETSI EN 319 102-1: "Electronic Signatures and Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation".
850dac4f6e123a5ed970cb08892924a6	119 144-3	3 Definitions and abbreviations
850dac4f6e123a5ed970cb08892924a6	119 144-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
850dac4f6e123a5ed970cb08892924a6	119 144-3	3.2 Abbreviations	For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.2] and the following apply: XFA XML Forms Architecture 4 Testing CMS digital signatures in PDF interoperability
850dac4f6e123a5ed970cb08892924a6	119 144-3	4.1 Introduction	This clause refers to clause 4 of ETSI EN 319 142-2 [3]. The test cases in this clause have been defined for different combinations of CMS digital signatures in PDF attributes. They test the use of PDF signatures, as described in ISO 32000-1 [1] and based on CMS. Mandatory attributes for CMS digital signatures in PDF described in ETSI EN 319 142-2 [3], clause 4.2, shall be present.
850dac4f6e123a5ed970cb08892924a6	119 144-3	4.2 Testing CMS digital signatures in PDF	The test cases in this clause have been defined for different combinations of CMS/PDF attributes but the following minimum requirements shall be satisfied. Mandatory attributes for CMS digital signatures in PDF described in ETSI EN 319 142-2 [3], clause 4, shall be present. ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 7 Table 1 shows which attributes are required to generate CMS digital signatures in PDF for each test case. Table 1: Test cases for CMS digital signatures in PDF TC ID Description Pass criteria Signature attributes PAdES/CMS/1 This is the simplest CMS digital signatures in PDF with minimum requirements and signature dictionary entry M (signing time). The signature shall be an approval signature as defined in ISO 32000-1 [1]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded PKCS #7 binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType and SignerInfo attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o adbe.pkcs7.detached o M o ByteRange o Contents (DER PKCS #7) o Certificates o SigningCertificate o ContentType o SignerInfo PAdES/CMS/2 This test case tests a CMS digital signature in PDF with signature time stamp attribute which ensures the time of signing, Location attribute which describes where the data was signed (CPU host name or physical location), Reason attribute that describes the reason for the signing, ContactInfo attribute that provides information to enable a recipient to contact the signer to verify the signature. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, Reason, Location, ContactInfo and ByteRange entries. The DER-encoded PKCS #7 binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, SignerInfo and SignatureTimestamp attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o adbe.pkcs7.detached o Reason o Location o ContactInfo o ByteRange o Contents (DER PKCS #7) o Certificates o SigningCertificate o ContentType o SignerInfo o SignatureTS PAdES/CMS/3 This test case tests a CMS digital signature in PDF with signature time stamp attribute which ensures the time of signing and adbe Revocation Information attribute to ensure revocation checks for the signing certificate and its issuer certificates. Certificate revocation list, described in IETF RFC 5280 [6] shall be used. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, and ByteRange entries. The DER-encoded PKCS #7 binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, SignerInfo, SignatureTimestamp and RevocationInfo attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o adbe.pkcs7.detached o ByteRange o Contents (DER PKCS #7) o Certificates o SigningCertificate o ContentType o SignerInfo o SignatureTS o RevocationInfo Crls ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 8 TC ID Description Pass criteria Signature attributes PAdES/CMS/4 This test case tests a CMS digital signature in PDF with signature time stamp attribute which ensures the time of signing and adbe Revocation Information attribute to ensure revocation checks for the signer's certificate and its issuer certificates. OCSP responses, described in IETF RFC 6960 [5] shall be used. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, and ByteRange entries. The DER-encoded PKCS #7 binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, SignerInfo, SignatureTimestamp and RevocationInfo attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o adbe.pkcs7.detached o ByteRange o Contents (DER PKCS #7) o Certificates o SigningCertificate o ContentType o SignerInfo o SignatureTS o RevocationInfo OCSP resp PAdES/CMS/5 This test case tests a CMS serial digital signature in PDF. The signed document shall include 2 serial signatures. Positive validation. The signed document shall contain 2 serial signatures. The signature dictionary of every signature shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded PKCS #7 binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType and SignerInfo attributes. • SignatureDictionary (2 entries) o Type o Sig o Filter o Adobe.PPKLite o SubFilter o adbe.pkcs7.detached o ByteRange o M o Contents (DER PKCS #7) o Certificates o SigningCertificate o ContentType o SignerInfo PAdES/CMS/6 This test case tests a CMS certification digital signature in PDF with signing time and LegalContentAttestation attributes. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M, Reference and ByteRange entries. The DER-encoded PKCS #7 binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType and SignerInfo attributes. The attestation entry in the LegalAttestationDictionary shall be valued. • LegalAttestationDictionary • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o adbe.pkcs7.detached o ByteRange o M o Reference o DocMDP o Contents (DER PKCS #7) o Certificates o SigningCertificate o ContentType o SignerInfo 5 Testing interoperability of PAdES-E-BES and PAdES-E-EPES signatures
850dac4f6e123a5ed970cb08892924a6	119 144-3	5.1 Introduction	This clause refers to clauses 5.3 of ETSI EN 319 142-2 [3]. The test cases in this clause have been defined for different combinations of PAdES-E-BES and PAdES-E-EPES signatures attributes. Mandatory attributes for PAdES-E-BES and PAdES-E-EPES signatures described in ETSI EN 319 142-2 [3], clauses 5.2, 5.3 and 5.4, shall be present. ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 9
850dac4f6e123a5ed970cb08892924a6	119 144-3	5.2 Testing PAdES-E-BES signatures	Table 2 shows which attributes are required to generate PAdES-E-BES signatures for each test case. Table 2: Test cases for PAdES-E-BES signatures TC ID Description Pass criteria Signature attributes PAdES/BES/1 This test case tests the simplest PAdES-E-BES signature without signature-time-stamp and with M entry in signature dictionary. ContentType, ESSSigningCertificateV2 and MessageDigest attributes shall be added to the PDF signature as specified in CAdES [4]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, ESSSigningCertificateV2 and MessageDigest attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates o SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 PAdES/BES/2 This test case tests a PAdES-E-BES signature without signature-time- stamp and with M, Location, Reason and ContactInfo entries in signature dictionary. ContentType, ESSSigningCertificateV2 and MessageDigest attributes shall be added to the PDF signature as specified in CAdES [4]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M, Location, Reason, ContactInfo and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, ESSSigningCertificateV2 and MessageDigest attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o Location o Reason o ContactInfo o ByteRange o Contents (DER CMS) ) o Certificates o SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 PAdES/BES/3 This test case tests the simplest PAdES-E-BES signature with signature-time-stamp attribute. ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes shall be added to the PDF signature as specified in CAdES [4]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, ESSSigningCertificateV2, MessageDigest signed attributes and SignatureTimeStamp unsigned attribute. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignatureTimeStamp ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 10 TC ID Description Pass criteria Signature attributes PAdES/BES/4 This test case tests a PAdES-E-BES signature with signature-time-stamp and an instance of ClaimedAttributes of SignerAttributesV2 attribute. ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes shall also be added to the PDF signature as specified in CAdES [4]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, SignerAttributesV2, ESSSigningCertificateV2, MessageDigest signed attributes and SignatureTimeStamp unsigned attribute. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignerAttributesV2 ClaimedAttr o SignatureTimeStamp PAdES/BES/5 This test case tests a PAdES-E-BES signature with a ContentTimeStamp attribute which provides time-stamp token of the signed data content before it is signed. ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes shall also be added to the PDF signature as specified in CAdES [4]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, ESSSigningCertificateV2, MessageDigest, ContentTimeStamp signed attributes and SignatureTimeStamp unsigned attribute. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o ContentTimeStamp o SignatureTimeStamp ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 11
850dac4f6e123a5ed970cb08892924a6	119 144-3	5.3 Testing PAdES-E-EPES signatures	Table 3 shows which attributes are required to generate PAdES-E-EPES signatures for each test case. Table 3: Test cases for PAdES-E-EPES signatures TC ID Description Pass criteria Signature attributes PAdES/EPES/1 This test case tests a PAdES-E-EPES signature with Reason, Location, ContactInfo entries in signature dictionary and MessageDigest, ContentType, SignaturePolicyIdentifier, SignatureTimeStamp and ESSSigningCertificateV2 attributes in the CADES [4] signature. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, Reason, Location, ContactInfo and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, ESSSigningCertificateV2, SignaturePolicyIdentifier, MessageDigest signed attributes and SignatureTimeStamp unsigned attribute. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o Reason o Location o ContactInfo o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignaturePolicyIdentif ier o SignatureTimeStamp PAdES/EPES/2 This test case tests a PAdES-E-EPES signature with MessageDigest, ContentType, SignaturePolicyIdentifier, SignatureTimeStamp, CommitmentTypeIndication and ESSSigningCertificateV2 attributes in the CAdES [4] signature. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, ESSSigningCertificateV2, SignaturePolicyIdentifier, MessageDigest, CommitmentTypeIndication signed attributes and SignatureTimeStamp unsigned attribute • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignaturePolicyIdentif ier o CommitmentTypeIndi cation o SignatureTimeStamp
850dac4f6e123a5ed970cb08892924a6	119 144-3	6 Testing interoperability of PAdES-E-LTV signatures
850dac4f6e123a5ed970cb08892924a6	119 144-3	6.1 Testing PAdES-E-LTV signatures	This clause refers to clause 5.5 of ETSI EN 319 142-2 [3]. The test cases in this clause have been defined for different combinations of PAdES-E-LTV signatures attributes. They test the use of PDF signatures, as described in clause 5.5 of ETSI EN 319 142-2 [3]. Mandatory attributes for PAdES-E-LTV signatures described in ETSI EN 319 142-2 [3], clause 5.5, shall be present. ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 12 The PAdES specification [3] supports Long Term Validation (LTV) of PDF Signatures using some extensions from ISO 32000-1 [1]. They are: • Document Security Store (DSS) that is able to carry validation data necessary to validate a signature, optionally with: - Validation Related Information (VRI) which relates the validation data to a specific signature. • Document time-stamp that is able to extend document life-time. PAdES-E-LTV signatures are generated by augmenting CMS digital signatures in PDF and/or PAdES-E-BES, PAdES-E-EPES signatures. Table 4 shows which attributes are required to generate PAdES-E-LTV signatures for each test case. Table 4: Test cases for PAdES-E-LTV signatures TC ID Description Pass criteria Signature attributes PAdES/LTV/1 This test case previews the generation and verification of the CMS digital signature in PDF of the test case PAdES/CMS/1 and subsequent augmentation to a PAdES-LTV format based on DSS with Certs and CRLs. Then one Document Time Stamp shall be applied and verified. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded PKCS #7 binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType and SignerInfo attributes. The DSS dictionary shall contain the Type, Certs and CRLs entries. The DTS dictionary shall contain the Type, SubFilter and Contents entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o adbe.pkcs7.detached o M o ByteRange o Contents (DER PKCS #7) o Certificates o SigningCertificate o ContentType o SignerInfo • DSS o Type o Certs o CRLs • DTS o Type o SubFilter o Contents PAdES/LTV/2 This test case previews the generation and verification of the CMS digital signature in PDF of the test case PAdES/CMS/2 and subsequent augmentation to a PAdES-LTV format based on DSS with Certs and OCSPs. Then one Document Time Stamp shall be applied and verified. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, Reason, Location, ContactInfo and ByteRange entries. The DER-encoded PKCS #7 binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType and SignerInfo attributes. The DSS dictionary shall contain the Type, Certs and OCSPs entries. The DTS dictionary shall contain the Type, SubFilter and Contents entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o adbe.pkcs7.detached o Reason o Location o ContactInfo o ByteRange o Contents (DER PKCS #7) o Certificates o SigningCertificate o ContentType o SignerInfo o SignatureTimeStam p • DSS o Type o Certs o OCSPs • DTS o Type o SubFilter o Contents ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 13 TC ID Description Pass criteria Signature attributes PAdES/LTV/3 This test case previews the generation and verification of the PAdES-E-BES signature of the test case PAdES/BES/1 and subsequent augmentation to a PAdES-LTV format based on DSS with Certs and CRLs. Then one Document Time Stamp shall be applied and verified. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, ESSSigningCertificateV2 and MessageDigest attributes. The DSS dictionary shall contain the Type, Certs and CRLs entries. The DTS dictionary shall contain the Type, SubFilter and Contents entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates o SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 • DSS o Type o Certs o CRLs • DTS o Type o SubFilter o Contents PAdES/LTV/4 This test case previews the generation and verification of the PAdES-E-BES signature of the test case PAdES/BES/1 and subsequent augmentation to a PAdES-LTV format based on DSS with Certs, CRLs and VRI entries and VRI dictionary with Cert and CRL entries. Then a Document time-stamp shall be applied and verified. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, ESSSigningCertificateV2 and MessageDigest attributes. The DSS dictionary shall contain the Type, Certs, CRLs and VRI entries. The VRI dictionary shall contain the Type, Cert and CRL entries. The DTS dictionary shall contain the Type, SubFilter and Contents entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates o SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 • DSS o Type o Certs o CRLs o VRI • VRI o Type o Cert o CRL • DTS o Type o SubFilter o Contents ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 14 TC ID Description Pass criteria Signature attributes PAdES/LTV/5 This test case previews the generation and verification of the CMS digital signature in PDF of the test case PAdES/CMS/6, including 2 serial signatures, and subsequent augmentation to a PAdES-LTV format based on DSS with Certs, OCSPs and VRI entries and VRI dictionary with Cert and OCSP entries. Then a Document time-stamp shall be applied and verified. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded PKCS #7 binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType and SignerInfo attributes. The DSS dictionary shall contain the Type, Certs, OCSPs and VRI entries. The VRI dictionary shall contain the Type, Cert and OCSP entries. The DTS dictionary shall contain the Type, SubFilter and Contents entries. • SignatureDictionary (2 entries) o Type o Sig o Filter o Adobe.PPKLite o SubFilter o adbe.pkcs7.detached o M o ByteRange o Contents (DER PKCS #7) o Certificates o SigningCertificate o ContentType o SignerInfo • DSS o Type o Certs o OCSPs o VRI • VRI o Type o Cert o OCSP • DTS o Type o SubFilter o Contents PAdES/LTV/6 This test case previews the generation and verification of a PAdES-E-BES signature including 2 PAdES/BES/1 signatures, and subsequent augmentation to a PAdES-LTV format based on DSS with Certs, OCSPs and VRI entries and VRI dictionary with Cert and OCSP entries. Then a Document time-stamp shall be applied and verified. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, ESSSigningCertificateV2 and MessageDigest attributes. The DSS dictionary shall contain the Type, Certs, OCSPs and VRI entries. The VRI dictionary shall contain the Type, Cert and OCSP entries. The DTS dictionary shall contain the Type, SubFilter and Contents entries. • SignatureDictionary (2 entries) o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates o SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 • DSS o Type o Certs o OCSPs o VRI • VRI o Type o Cert o OCSP • DTS o Type o SubFilter o Contents ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 15 7 Testing interoperability of XAdES signatures signing XML content in PDF
850dac4f6e123a5ed970cb08892924a6	119 144-3	7.1 Introduction	This clause refers to clause 6 of ETSI EN 319 142-2 [3]. The test cases in this clause have been defined for different combinations of XAdES signatures signing XML content in PDF attributes. They test the use of XML signatures within the PDF container. 7.2 Testing XAdES signatures of XML documents embedded in PDF containers An XML document created and signed with XAdES signatures according to ETSI EN 319 132-1 [2] out of PDF framework can be embedded within a PDF container and transported within it. For the purpose to verify the signatures of an XML document signed with XAdES [2] and embedded within a PDF container long after their creation, a verifier may extract the XML document, verify the XAdES signature, augment the XAdES signature itself (to more evolved forms) and embed again the modified XAdES signature within the PDF container. Minimum requirement: The xades:SigningCertificateV2 or the ds:KeyInfo element shall be used to secure the signing certificate. Table 5 shows which attributes are required to generate XAdES signatures of XML documents embedded in PDF containers for each test case. Table 5: Test cases for XAdES signatures of XML documents embedded in PDF containers TC ID Description Pass criteria Signature attributes PAdES/XML/1 This test case tests a XAdES-B-B signature with the signed properties "SignedSignatureProperties ", conforming to ETSI EN 319 132-1 [2], containing the SigningTime, SigningCertificateV2, SignatureProductionPlaceV 2, SignerRoleV2 properties. Positive validation. The XAdES signature shall contain the SignedInfo, SignatureValue, SigningTime, SigningCertificateV2, SignatureProductionPlaceV2, SignerRoleV2 properties. • SignedInfo • SignatureValue • SignedSignatureProperties o SigningTime o SigningCertificateV2 o SignatureProductionPlace V2 o SignerRoleV2 PAdES/XML/2 This test case tests a XAdES-B-T signature with the signed properties "SignedDataObjectPropertie s" and unsigned properties SignatureTimeStamp conforming to ETSI EN 319 132-1 [2]. The CommitmentTypeIndication, AllDataObjectsTimeStamp, "SignedDataObjectPropertie s" shall be used. Positive validation. The XAdES signature shall contain the SignedInfo, SignatureValue, SigningCertificateV2, CommitmentTypeIndication, AllDataObjectsTimeStamp and SignatureTimeStamp attributes. • SignedInfo • SignatureValue • SignedSignatureProperties o SigningCertificateV2 • SignedDataObjectProperties o CommitmentTypeIndication o AllDataObjectsTimeStamp • UnsignedSignatureProperties o SignatureTimeStamp PAdES/XML/3 This test case tests a XAdES-B-B signature with a countersignature attribute. Positive validation. The XAdES signature shall contain the SignedInfo, SignatureValue, SigningCertificateV2 and CounterSignature attributes. • SignedInfo • SignatureValue • SignedSignatureProperties o SigningCertificateV2 • UnsignedSignatureProperties o CounterSignature ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 16
850dac4f6e123a5ed970cb08892924a6	119 144-3	7.3 Testing XAdES signatures on XFA forms	The XAdES signature will be able to sign XFA data only or any XML content from XFA allowed by XFA specification. Signature is encoded as XAdES-B-B and XAdES-B-T forms. The xades:SigningCertificateV2 or the ds:KeyInfo element shall be used to secure the signing certificate. For long-term validation XAdES signatures on XFA use the XADES-B-LTA forms. Table 6 shows which attributes are required to generate XAdES signatures on XFA forms for each test case. Table 6: Test cases for XAdES signatures on XFA forms TC ID Description Pass criteria Signature attributes PAdES/XFA/1 This test case tests a XAdES signature on XFA forms in which the XFA signed file is a XADES-B-T signature conforming ETSI EN 319 132-1 [2] with the signed properties SigningCertificateV2, SignatureProductionPlaceV 2, SignerRoleV2 and the SignatureTimeStamp unsigned property. Positive validation. The XAdES signature shall contain the SignedInfo, SignatureValue, SigningCertificateV2, SignatureProductionPlaceV2, SignerRoleV2 and SignatureTimeStamp properties. • SignedInfo • SignatureValue • SignedSignatureProperties o SigningCertificateV2 o SignatureProductionPlace V2 o SignerRole • UnsignedSignatureProperties o SignatureTimeStamp PAdES/XFA/2 This test case tests a XAdES-B-B signature with a countersignature attribute. The XFA signed file is XAdES-B-B conforming ETSI EN 319 132-1 [2] with a CounterSignature Positive validation. The XAdES signature shall contain the SignedInfo, SignatureValue, SigningCertificateV2 and CounterSignature attributes. • SignedInfo • SignatureValue • SignedSignatureProperties o SigningCertificateV2 • UnsignedSignatureProperties o CounterSignature
850dac4f6e123a5ed970cb08892924a6	119 144-3	8 Testing negative additional PAdES signatures
850dac4f6e123a5ed970cb08892924a6	119 144-3	8.1 CMS digital signatures in PDF test cases	The test cases in this clause have been defined for CMS digital signatures in PDF. Table 7 summarizes negative test cases for CMS digital signatures in PDF. Table 7: Negative test cases for CMS digital signatures in PDF TC ID Description PAdES/CMSN/1 Verify a signed pdf document having a wrong byte range PAdES/CMSN/2 Verify a signed pdf document having a wrong signature (the hash that was signed is not the hash of the specified byte range) PAdES/CMSN/3 Verify a pdf document signed with an untrusted signing certificate PAdES/CMSN/4 Verify a pdf document signed with an expired signing certificate PAdES/CMSN/5 Verify a pdf document signed with a revoked/suspended signing certificate PAdES/CMSN/6 Verify a signed pdf document containing an untrusted signature timestamp PAdES/CMSN/7 Verify a signed pdf document containing an expired signature timestamp PAdES/CMSN/8 Verify a signed pdf document containing a revoked signature timestamp ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 17
850dac4f6e123a5ed970cb08892924a6	119 144-3	8.2 PAdES-E-BES and PAdES-E-EPES test cases	The test cases in this clause have been defined for PAdES-E-BES and PAdES-E-EPES signatures. Table 8 summarizes negative test cases for PAdES-E-BES and PAdES-E-EPES signatures. Table 8: Negative test cases for PAdES-E-BES and PAdES-E-EPES signatures TC ID Description PAdES/BESN/1 Verify a signed pdf document having a wrong byte range PAdES/BESN/2 Verify a signed pdf document having a wrong signature (the hash that was signed is not the hash of the specified byte range) PAdES/BESN/3 Verify a signed pdf document having a wrong time stamp signature (the signature that was timestamped is not pdf document signature) PAdES/BESN/4 Verify a pdf document signed with an untrusted signing certificate PAdES/BESN/5 Verify a pdf document signed with an expired signing certificate PAdES/BESN/6 Verify a pdf document signed with a revoked/suspended signing certificate PAdES/BESN/7 Verify a signed pdf document containing an untrusted signature timestamp PAdES/BESN/8 Verify a signed pdf document containing an expired signature timestamp PAdES/BESN/9 Verify a signed pdf document containing a revoked signature timestamp PAdES/BESN/10 Verify a signed pdf document in which the hash value of the signing certificate is different from the hash value in signing certificate or ESS signing certificate V2 attribute PAdES/BESN/11 Verify a signed pdf document containing commitment-type-indication attribute and the attribute reason of the dictionary (ETSI EN 319 142-2 [3], clause 5.3)
850dac4f6e123a5ed970cb08892924a6	119 144-3	8.3 PAdES-E-LTV test cases	The test cases in this clause have been defined for PAdES-E-LTV signatures. Table 9 summarizes negative test cases for PAdES-E-LTV signatures. Table 9: Negative test cases for PAdES-E-LTV signatures TC ID Description PAdES/LTVN/1 Verify a PAdES-E-LTV signature in which the Document Time Stamp has a wrong signature (the hash that was signed isn't the hash computed on the specified byte range PAdES/LTVN/2 Verify a PAdES-E-LTV signature which one timestamp is invalid at the time of the successive (in time) timestamp (TSS certificate expired or revoked) PAdES/LTVN/3 Verify a PAdES-E-LTV signature in which the signature is not valid in respect of validation data stored in the DSS ETSI ETSI TS 119 144-3 V1.1.1 (2016-06) 18 History Document history V1.1.1 June 2016 Publication
a8b7583eb7ba0080eb16108956d1a7f9	119 144-2	1 Scope	The present document defines a number of test suites to assess the interoperability between implementations claiming conformance to PAdES baseline signatures [2]. The test suites are defined with four different layers reflecting the four different levels of PAdES baseline signatures: • Tests suite addressing interoperability between applications claiming B-B level conformance. • Tests suite addressing interoperability between applications claiming B-T level conformance. • Tests suite addressing interoperability between applications claiming B-LT level conformance. • Tests suite addressing interoperability between applications claiming B-LTA level conformance. Test suites also cover augmentation of PAdES baseline signatures and negative test cases. These test suites are agnostic of the PKI infrastructure. Any PKI infrastructure can be used including the one based on EU Member States Trusted Lists.
a8b7583eb7ba0080eb16108956d1a7f9	119 144-2	2 References
a8b7583eb7ba0080eb16108956d1a7f9	119 144-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 are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI EN 319 122-1: "Electronic Signatures and Infrastructures (ESI); CAdES digital signatures; Part 1: Building blocks and CAdES baseline signatures". [2] ETSI EN 319 142-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures; Part 1: Building blocks and PAdES baseline signatures".
a8b7583eb7ba0080eb16108956d1a7f9	119 144-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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 119 144-1: "Electronic Signatures and Infrastructures (ESI); PAdES digital signatures - Testing Conformance and Interoperability; Part 1: Overview". [i.2] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 6 [i.3] ETSI EN 319 102-1: "Electronic Signatures and Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation".
a8b7583eb7ba0080eb16108956d1a7f9	119 144-2	3 Definitions and abbreviations
a8b7583eb7ba0080eb16108956d1a7f9	119 144-2	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
a8b7583eb7ba0080eb16108956d1a7f9	119 144-2	3.2 Abbreviations	For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.2] apply.
a8b7583eb7ba0080eb16108956d1a7f9	119 144-2	4 Overview	This clause describes the overall approach used throughout the present document to specify test suites for PAdES baseline signatures interoperability testing. ETSI EN 319 142-1 [2] defines four different levels of PAdES baseline signatures. The test suites are defined with different layers reflecting the levels of PAdES baseline signatures specified in ETSI EN 319 142-1 [2]: • Testing PAdES signatures interoperability between applications claiming B-B level conformance. • Testing PAdES signatures interoperability between applications claiming B-T level conformance. • Testing PAdES signatures interoperability between applications claiming B-LT level conformance. • Testing PAdES signatures interoperability between applications claiming B-LTA level conformance. • Testing augmentation of PAdES signatures from B-T level to B-LTA level. • Negative test cases for PAdES baseline signatures: - PAdES-B-B signatures test cases. - PAdES-B-T signatures test cases. - PAdES-B-LTA signatures test cases.
a8b7583eb7ba0080eb16108956d1a7f9	119 144-2	5 Testing interoperability of PAdES-B-B signatures	The test cases in this clause have been defined for different combinations of PAdES-B-B signatures attributes. Mandatory attributes for PAdES-B-B signatures described in ETSI EN 319 142-1 [2], clauses 6.2 and 6.3, shall be present. Table 1 shows which attributes are required to generate PAdES-B-B signatures for each test case. ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 7 Table 1: Test cases for PAdES-B-B signatures TC ID Description Pass criteria Signature attributes PAdES/BB/1 This is the simplest PAdES- B-B signatures interoperability test case. The signature ONLY CONTAINS the mandatory PAdES attributes. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, ESSSigningCertificateV2 and MessageDigest attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 PAdES/BB/2 In this PAdES-B-B signatures interoperability test case the signature dictionary contains the same entries used in test case PAdES/BB/1 with the addition of Location, ContactInfo and Reason entries. ContentType, ESSSigningCertificateV2 and MessageDigest attributes shall be added to the PDF signature included in the Contents entry as specified in CAdES [1]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M, Location, Reason and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, ESSSigningCertificateV2 and MessageDigest attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o Location o ContactInfo o Reason o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 PAdES/BB/3 In this PAdES-B-B signatures interoperability test case the PDF signature contains ContentTimeStamp attribute in addition to ContentType, ESSSigningCertificateV2 and MessageDigest attributes included to the PDF signature included in the Contents entry as specified in CAdES [1]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, ESSSigningCertificateV2, ContentTimeStamp and MessageDigest attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o ContentTimeStamp ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 8 TC ID Description Pass criteria Signature attributes PAdES/BB/4 This test case tests a PAdES-B-B signature with an instance of ClaimedAttribute of SignerAttributesV2 attribute. ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes shall also be added to the PDF signature included in the Contents entry as specified in CAdES [1]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, M, SubFilter and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, ClaimedAttribute (included in SignerAttributesV2), ESSSigningCertificateV2, MessageDigest attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignerAttributesV2 ClaimedAttribute PAdES/BB/5 This test case tests a PAdES-B-B signature with an instance of CertifiedAttributeV2 of SignerAttributesV2 attribute. ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes shall also be added to the PDF signature included in the Contents entry as specified in CAdES [1]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, M, SubFilter and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, CertifiedAttributesV2 (included in SignerAttributesV2), ESSSigningCertificateV2, MessageDigest attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignerAttributesV2 CertifiedAttributeV2 PAdES/BB/6 This test case tests a PAdES-B-B signature with M, Reason, and Location entries in signature dictionary and MessageDigest, SignaturePolicyIdentifier, ContentType and ESSSigningCertificateV2 attributes in the CAdES [1] signature included in the Contents entry. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M, Reason, Location and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, ESSSigningCertificateV2, SignaturePolicyIdentifier and MessageDigest attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o Reason o Location o M o ByteRange o Contents (DER CMS) o SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignaturePolicyIdentif ier ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 9 TC ID Description Pass criteria Signature attributes PAdES/BB/7 This test case tests a PAdES-B-B signature in which digest algorithm SHA1 is used to digest data to be signed. The signature ONLY CONTAINS the mandatory PAdES properties. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field), ContentType, ESSSigningCertificate and MessageDigest attributes • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat e
a8b7583eb7ba0080eb16108956d1a7f9	119 144-2	6 Testing interoperability of PAdES-B-T signatures	The test cases in this clause have been defined for different combinations of PAdES-B-T signatures attributes. PAdES baseline signatures claiming conformance to B-T level of ETSI EN 319 142-1 [2] shall be built on baseline signatures conformant to B-B level. A PAdES baseline signature conformant to B-T level shall be a baseline signature conformant to B-B level for which a Trust Service Provider has generated a trusted token (time-stamp token) proving that the signature itself actually existed at a certain date and time. Mandatory attributes for PAdES-B-T signatures described in ETSI EN 319 142-1 [2], clauses 6.2 and 6.3, shall be present. Table 2 shows which attributes are required to generate PAdES-B-T signatures for each test case. Table 2: Test cases for PAdES-B-T signatures TC ID Description Pass criteria Signature attributes PAdES/BT/1 This is the simplest PAdES- B-T signatures interoperability test case with M entry in signature dictionary. ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes shall be added to the PDF signature included in the Contents entry as specified in CAdES [1]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, M, SubFilter and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, ESSSigningCertificateV2, MessageDigest signed attributes and SignatureTimeStamp unsigned attribute. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignatureTimeStamp ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 10 TC ID Description Pass criteria Signature attributes PAdES/BT/2 This test case tests a PAdES-B-T signature with an instance of ClaimedAttribute of SignerAttributesV2 attribute. ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes are included in PDF signature included in the Contents entry as specified in CAdES [1]. Positive validation. The signature dictionary shall contain Type, Contents, Filter, M, SubFilter and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, ClaimedAttribute (included in SignerAttributesV2), ESSSigningCertificateV2, MessageDigest signed attributes and SignatureTimeStamp unsigned attribute. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignerAttributesV2 ClaimedAttribute o SignatureTimeStamp PAdES/BT/3 This test case tests a PAdES-B-T signature with MessageDigest, ContentType, SignaturePolicyIdentifier, SignatureTimeStamp, CommitmentTypeIndication and ESSSigningCertificateV2 attributes in the CAdES [1] signature included in the Contents entry. Positive validation. The signature dictionary shall contain Type, Contents, Filter, M, SubFilter and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, ESSSigningCertificateV2, SignatureTimeStamp, SignaturePolicyIdentifier, CommitmentTypeIndication and MessageDigest attributes. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignaturePolicyIdentif ier o CommitmentTypeIndi cation o SignatureTimeStamp PAdES/BT/4 This test case tests a PAdES-B-T signature with a ContentTimeStamp attribute which provides time-stamp token of the signed data content before it is signed. ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes shall also be added to the CAdES signature [1] included in the Contents entry. Positive validation. The signature dictionary shall contain Type, M, Contents, Filter, SubFilter and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, MessageDigest, ESSSigningCertificateV2, ContentTimeStamp signed attributes and SignatureTimeStamp unsigned attribute. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o ContentTimeStamp o SignatureTimeStamp ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 11
a8b7583eb7ba0080eb16108956d1a7f9	119 144-2	7 Testing interoperability of PAdES-B-LT signatures	The test cases in this clause have been defined for different combinations of PAdES-B-LT signatures attributes. PAdES baseline signatures claiming conformance to B-LT level of ETSI EN 319 142-1 [2] shall be built on baseline signatures conformant to B-T level. A PAdES baseline signature conformant to B-LT level shall be a baseline signature conformant to B-T level to which values of certificates and values of certificate status used to validate the signature have been added in the DSS and eventually VRI dictionaries. Mandatory attributes for PAdES-B-LT signatures described in ETSI EN 319 142-1 [2], clauses 6.2 and 6.3, shall be present. Table 3 shows which attributes are required to generate PAdES-B-LT signatures for each test case. Table 3: Test cases for PAdES-B-LT signatures TC ID Description Pass criteria Signature attributes PAdES/BLT/1 This is the simplest PAdES- B-LT signatures interoperability test case with M entry in signature dictionary. CMS signature, included in the Contents entry, contains ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes. The DSS dictionary includes Certs and CRLs entries. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, MessageDigest, ESSSigningCertificateV2 signed attributes and SignatureTimeStamp unsigned attribute. The DSS dictionary shall contain the Type, Certs and CRLs entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignatureTimeStamp • DSS o Type o Certs o CRLs PAdES/BLT/2 This PAdES-B-LT signature contains Type, Contents, Filter, SubFilter, M and ByteRange entries in signature dictionary. CMS signature, included in the Contents entry, contains ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes. The DSS dictionary includes Certs and OCSPs entries. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, MessageDigest, ESSSigningCertificateV2 signed attributes and SignatureTimeStamp unsigned attribute. The DSS dictionary shall contain the Type, Certs and OCSPs entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignatureTimeStamp • DSS o Type o Certs o OCSPs ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 12 TC ID Description Pass criteria Signature attributes PAdES/BLT/3 This PAdES-B-LT signature contains Type, Contents, Filter, SubFilter, M and ByteRange entries in signature dictionary. CMS signature, included in the Contents entry, contains ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes. The DSS dictionary includes Certs, CRLs and VRI entries. The VRI dictionary includes Cert and CRL entries. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, MessageDigest, ESSSigningCertificateV2 signed attributes and SignatureTimeStamp unsigned attribute. The DSS dictionary shall contain the Type, Certs, CRLs and VRI entries. The VRI dictionary shall contain the Type, Cert and CRL entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignatureTimeStamp • DSS o Type o Certs o CRLs o VRI • VRI o Type o Cert o CRL PAdES/BLT/4 This PAdES-B-LT signature contains Type, Contents, Filter, SubFilter, M and ByteRange entries in signature dictionary. CMS signature, included in the Contents entry, contains ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes. The DSS dictionary includes Certs, OCSPs and VRI entries. The VRI dictionary includes Cert and OCSP entries. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, MessageDigest, ESSSigningCertificateV2 signed attributes and SignatureTimeStamp unsigned attribute. The DSS dictionary shall contain the Type, Certs and OCSPs entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignatureTimeStamp • DSS o Type o Certs o OCSPs o VRI • VRI o Type o Cert o OCSP
a8b7583eb7ba0080eb16108956d1a7f9	119 144-2	8 Testing interoperability of PAdES-B-LTA signatures	The test cases in this clause have been defined for different combinations of PAdES-B-LTA signatures attributes. PAdES baseline signatures claiming conformance to B-LTA level of ETSI EN 319 142-1 [2] shall be built on baseline signatures conformant to B-LT level. A PAdES baseline signature conformant to B-LTA level shall be a baseline signature conformant to B-LT level to which one or more DTS dictionaries have been added. ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 13 Mandatory attributes for PAdES-B-LTA signatures described in ETSI EN 319 142-1 [2], clauses 6.2 and 6.3, shall be present. Table 4 shows which attributes are required to generate PAdES-B-LTA signatures for each test case. Table 4: Test cases for PAdES-B-LTA signatures TC ID Description Pass criteria Signature attributes PAdES/BLTA/1 This is the simplest PAdES- B-LTA signatures interoperability test case with Type, Contents, Filter, SubFilter, M and ByteRange entries in signature dictionary. CMS signature, included in the Contents entry, contains ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes. The DSS dictionary includes Certs and CRLs entries. Then one Document Time Stamp shall be applied and verified. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, MessageDigest, ESSSigningCertificateV2 signed attributes and SignatureTimeStamp unsigned attribute. The DSS dictionary shall contain the Type, Certs and CRLs entries. The DTS dictionary shall contain the Type, SubFilter and Contents entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignatureTimeStamp • DSS o Type o Certs o CRLs • DTS o Type o SubFilter o Contents PAdES/BLTA/2 This PAdES-B-LTA signature contains Type, Contents, Filter, SubFilter, M and ByteRange entries in signature dictionary. CMS signature, included in the Contents entry, contains ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes. The DSS dictionary includes Certs and OCSPs. Then one Document Time Stamp shall be applied and verified. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, MessageDigest, ESSSigningCertificateV2 signed attributes and SignatureTimeStamp unsigned attribute. The DSS dictionary shall contain the Type, Certs and OCSPs entries. The DTS dictionary shall contain the Type, SubFilter and Contents entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignatureTimeStamp • DSS o Type o Certs o OCSPs • DTS o Type o SubFilter o Contents ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 14 TC ID Description Pass criteria Signature attributes PAdES/BLTA/3 This PAdES-B-LTA signature contains Type, Contents, Filter, SubFilter, M and ByteRange entries in signature dictionary. CMS signature, included in the Contents entry, contains ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes. The DSS dictionary includes Certs, CRLs and VRI entries. The VRI dictionary includes Cert and CRL entries. Then one Document Time Stamp shall be applied and verified. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, MessageDigest, ESSSigningCertificateV2 signed attributes and SignatureTimeStamp unsigned attribute. The DSS dictionary shall contain the Type, Certs, CRLs and VRI entries. The VRI dictionary shall contain the Type, Cert and CRL entries. The DTS dictionary shall contain the Type, SubFilter and Contents entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignatureTimeStamp • DSS o Type o Certs o CRLs o VRI • VRI o Type o Cert o CRL • DTS o Type o SubFilter o Contents PAdES/BLTA/4 This PAdES-B-LTA signature contains Type, Contents, Filter, SubFilter, M and ByteRange entries in signature dictionary. CMS signature, included in the Contents entry, contains ContentType, ESSSigningCertificateV2, MessageDigest and SignatureTimeStamp attributes. The DSS dictionary includes Certs, OCSPs and VRI entries. The VRI dictionary includes Cert and OCSP entries. Then one Document Time Stamp shall be applied and verified. Positive validation. The signature dictionary shall contain Type, Contents, Filter, SubFilter, M and ByteRange entries. The DER-encoded CMS binary data object included in the Contents entry shall include the SigningCertificate (in SignedData.certificates field) attribute, ContentType, MessageDigest, ESSSigningCertificateV2 signed attributes and SignatureTimeStamp unsigned attribute. The DSS dictionary shall contain the Type, Certs and OCSPs entries. The DTS dictionary shall contain the Type, SubFilter and Contents entries. • SignatureDictionary o Type o Sig o Filter o Adobe.PPKLite o SubFilter o ETSI.CAdES.detache d o M o ByteRange o Contents (DER CMS) o Certificates SigningCertificate o ContentType o MessageDigest o ESSSigningCertificat eV2 o SignatureTimeStamp • DSS o Type o Certs o OCSPs o VRI • VRI o Type o Cert o OCSP • DTS o Type o SubFilter o Contents ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 15 9 Testing PAdES baseline signatures augmentation interoperability The test cases in this clause have been defined for testing augmentation of PAdES-B-T signatures to PAdES-B-LTA signatures and subsequent validation of the augmented signatures. A PAdES baseline signature conformant to B-LTA level shall be a baseline signature conformant to B-T level to which one or more DSS and eventually VRI dictionaries containing values of certificates and values of certificates status used to validate the signature and one or more DTS dictionaries have been added. Table 5 shows which attributes are required to augment a PAdES-B-T signature to a PAdES-B-LTA signature for each test case. Table 5: Test cases for augmentation of PAdES-B-T signatures to B-LTA signatures TC ID Description Pass criteria Signature attributes PAdES/Aug/1 The PAdES-B-T signature, passed as input, shall be validated, the validation material concerning the signing certificate and the certificate that generated the signature timestamp shall be added (the revocation data used are CRLs) and, after that, one Document Time Stamp shall be applied. Positive validation. The signature shall contain a PAdES-B-T signature with a signature dictionary containing Type, Contents, Filter, M, SubFilter and ByteRange entries and a DER-encoded CMS binary data object included in the Contents entry including the SigningCertificate (in SignedData.certificates field) attribute, ContentType, ESSSigningCertificateV2, MessageDigest signed attributes and SignatureTimeStamp unsigned attribute. A DSS dictionary containing the Type, Certs and CRLs entries and a DTS dictionary containing the Type, SubFilter and Contents entries are added to the PAdES- B-T signature. • PAdES-B-T signature • DSS o Type o Certs o CRLs • DTS o Type o SubFilter o Contents PAdES/Aug/2 The PAdES-B-T signature, passed as input, shall be validated, the validation material concerning the signing certificate and the certificate that generated the signature timestamp shall be added (the revocation data used are OCSP responses) and, after that, one Document Time Stamp shall be applied. Positive validation. The signature shall contain a PAdES-B-T signature with a signature dictionary containing Type, Contents, Filter, M, SubFilter and ByteRange entries and a DER-encoded CMS binary data object included in the Contents entry including the SigningCertificate (in SignedData.certificates field) attribute, ContentType, ESSSigningCertificateV2, MessageDigest signed attributes and SignatureTimeStamp unsigned attribute. A DSS dictionary containing the Type, Certs and OCSPs entries and a DTS dictionary containing the Type, SubFilter and Contents entries are added to the PAdES- B-T signature. • PAdES-B-T signature • DSS o Type o Certs o OCSPs • DTS o Type o SubFilter o Contents ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 16 TC ID Description Pass criteria Signature attributes PAdES/Aug/3 The input to this test case is a PAdES-B-LTA signature. The signature, passed as input, shall be validated, the validation material concerning the certificate that generated the timestamp included in the Contents entry of the DTS dictionary shall be added (the revocation data used are CRLs) to the DSS dictionary and, after that, one Document Time Stamp shall be applied too. Positive validation. The signature shall contain a PAdES-B-LTA signature with a signature dictionary containing Type, Contents, Filter, M, SubFilter and ByteRange entries, a DER-encoded CMS binary data object included in the Contents entry including the SigningCertificate (in SignedData.certificates field) attribute, ContentType, ESSSigningCertificateV2, MessageDigest signed attributes and SignatureTimeStamp unsigned attribute, a DSS dictionary containing the Type, Certs and CRLs entries and a DTS dictionary containing the Type, SubFilter and Contents entries. A new DSS dictionary containing the validation material concerning the certificate that generated the timestamp included in the Contents entry of the DTS dictionary and a new DTS dictionary containing the Type, SubFilter and Contents entries shall be added to the PAdES-B-LTA signature. • PAdES-B-T signature • DSS o Type o Certs o CRLs • DTS o Type o SubFilter o Contents • DTS o Type o SubFilter o Contents PAdES/Aug/4 The input to this test case is a PAdES-B-LTA signature. The signature, passed as input, shall be validated, the validation material concerning the certificate that generated the timestamp included in the Contents entry of the DTS dictionary shall be added (the revocation data used are OCSPs) to the DSS dictionary and, after that, one Document Time Stamp shall be applied too. Positive validation. The signature shall contain a PAdES-B-LTA signature with a signature dictionary containing Type, Contents, Filter, M, SubFilter and ByteRange entries, a DER-encoded CMS binary data object included in the Contents entry including the SigningCertificate (in SignedData.certificates field) attribute, ContentType, ESSSigningCertificateV2, MessageDigest signed attributes and SignatureTimeStamp unsigned attribute, a DSS dictionary containing the Type, Certs and OCSPs entries and a DTS dictionary containing the Type, SubFilter and Contents entries. A new DSS dictionary containing the validation material concerning the certificate that generated the timestamp included in the Contents entry of the DTS dictionary and a new DTS dictionary containing the Type, SubFilter and Contents entries shall be added to the PAdES-B-LTA signature. • PAdES-B-T signature • DSS o Type o Certs o OCSPs • DTS o Type o SubFilter o Contents • DTS o Type o SubFilter o Contents ETSI ETSI TS 119 144-2 V2.1.1 (2016-06) 17

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.