hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2.4.2 Test assertions for free text MIME subsection header | All the tests assertions defined in clause 5.4.2 with a prescription level of Mandatory shall apply, unless stated otherwise. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2.4.3 Test assertions for HTML MIME subsection header | All the tests assertions defined in clause 5.4.3 with a prescription level of Mandatory shall apply, unless stated otherwise. ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 72 |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2.5 Test assertions for fields in original message MIME section header | All the tests assertions defined in clause 5.5 with a prescription level of Mandatory shall apply, unless stated otherwise. In addition, the test assertions defined below shall apply. REMS/BS/HEADER/ORMESS/FIELD/TA_01 TA Id REMS/BS/HEADER/ORMESS/FIELD/TA_01 Normative source ETSI EN 319 532-4 [11], clause 5.4.4 Nº Servi... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2.6 Test assertions for fields in REMS extension MIME section header | All the tests assertions defined in clause 5.6 with a prescription level of Mandatory shall apply, unless stated otherwise. In addition, the test assertions defined in the tables below shall apply. REMS/BS/HEADER/EXT/FIELD/TA_01 TA Id REMS/BS/HEADER/EXT/FIELD/TA_01 Normative source ETSI EN 319 532-4 [11], clause 5.4.5 ... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2.7 Test assertions for fields in ERDS evidence MIME section header | All the tests assertions defined in clause 5.7.1 with a prescription level of Mandatory shall apply, unless stated otherwise. Furthermore, the test assertions defined in the tables below shall apply. REMS/BS/HEADER/EVID/FIELD/TA_01 TA Id REMS/BS/HEADER/EVID/FIELD/TA_01 Normative source ETSI EN 319 532-4 [11], clause 5.... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2.8 Test assertions for fields in REMS signature MIME section header | All the tests assertions defined in clause 5.8 with a prescription level of Mandatory shall apply, unless stated otherwise. In addition, the test assertions defined in the tables below shall apply. ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 74 REMS/BS/HEADER/REMSSIG/FIELD/TA_01 TA Id REMS/BS/HEADER/REMSSIG/FIELD/TA_01 Nor... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.3 Test assertions for MIME sections body | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.3.1 Introduction | This clause defines test assertions on the bodies of some of the MIME sections within REM Baseline messages. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.3.2 Test assertions for Introduction MIME section body | Test assertions defined in clause 6.2 shall apply. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.4 Test assertions for REM messages structures | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.4.1 Introduction | The tests assertions referenced in the table below shall apply. Test assertions that shall apply Test assertion identifier ETSI document clause REMS/MSSG/STRUCT/REMPAYLOAD/TA_01 The present document 7.2 REMS/MSSG/STRUCT/REMPAYLOAD/TA_02 The present document 7.2 REMS/MSSG/STRUCT/REMPAYLOAD/TA_03 The present document 7.2... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.4.2 Test assertions for REM payload structure | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.4.2.1 Test assertions for ERDS serviceinfo structure | The tests assertions referenced in the table below shall apply when the REMS notification is an ERDS serviceinfo. Test assertions that shall apply Test assertion identifier ETSI document clause REMS/MSSG/STRUCT/REMNOT/TA_01 The present document 7.3 REMS/MSSG/STRUCT/REMNOT/TA_02 The present document 7.3 REMS/MSSG/STRUCT... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.4.2.2 Test assertions for ERDS receipt structure | The tests assertions referenced in the table below shall apply when the REMS notification is an ERDS receipt. Test assertions that shall apply Test assertion identifier ETSI document clause REMS/MSSG/STRUCT/REMRECEIPT/TA_01 The present document 7.4 REMS/MSSG/STRUCT/REMRECEIPT/TA_02 The present document 7.4 REMS/MSSG/ST... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.4.3 Test assertions for REMS dispatch structure | The tests assertions referenced in the table below shall apply. Test assertions that shall apply Test assertion identifier ETSI document clause REMS/MSSG/STRUCT/REMDISPATCH/TA_01 The present document 7.5 REMS/MSSG/STRUCT/REMDISPATCH/TA_02 The present document 7.5 REMS/MSSG/STRUCT/REMDISPATCH/TA_03 The present document ... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.4.4 Test assertions for signatures for signatures signing REM messages | The tests assertions referenced in the table below shall apply. Test assertions that shall apply Test assertion identifier ETSI document clause REMS/REMMESSSIG/TA_02 The present document 8.3 REMS/REMMESSSIG/TA_03 The present document 8.3 REMS/REMMESSSIG/TA_08 The present document 8.3 REMS/REMMESSSIG/TA_02 The present d... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.5.1 Introduction | The present clause defines Test Assertions for the different interfaces present in REMS. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.5.2 Test assertions for REM Message Submission Interface (MSI) | REMS/BS/INTERFACES/MSI/TA_01 TA Id REMS/BS/INTERFACES/MSI/TA_01 Normative source ETSI EN 319 532-4 [11], clause 5.3.2 The Message Submission Interface shall be implemented with a protocol that shall secure the communication from the originating mail User Agent to the SMTP server. More specifically, this protocol shall ... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.5.4 Test assertions for REM Rely Interface (RI) | REMS/BS/INTERFACES/RI/TA_01 TA Id REMS/BS/INTERFACES/RI/TA_01 Normative source ETSI EN 319 532-4 [11], clause 5.3.4 The Relay Interface shall be implemented using SMTP protocol securing the communication from the sender REMSP server to the recipient REMSP server using TLS according to IETF RFC 3207 [15] Target Conforma... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.5.5 Test assertions for Common Service Interface (CSI) | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.5.5.1 Introduction | The present clause defines Test Assertions for the Common Service Interface. ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 78 |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.5.5.2 Test assertions for routing information | REMS/BS/INTERFACES/ROUTINGINFO/TA_01 TA Id REMS/BS/INTERFACES/ROUTINGINFO/TA_01 Normative source ETSI EN 319 532-4 [11], clause C.2.3.2 The Routing Interface, part of CSI, shall be implemented using DNS protocol properly secured. Target Conformance to REMS INTERFACES Predicate The routing interface of the Common Servic... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.5.5.3 Test assertions for trust information binding | The following test assertion shall apply. REMS/BS/INTERFACES/TRUSTINFO/TA_01 TA Id REMS/BS/INTERFACES/TRUSTINFO/TA_01 Normative source ETSI EN 319 532-4 [11], clause C.2.3.3.1 implementation guidance b.2.1.3) The Trusting Interface, part of CSI trust infrastructure, allowing the cooperation among participants to the tr... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.5.5.4 Test assertions for capability discovery and management | 12.5.5.4.1 Test assertions for referencing in Trusted Lists REMS/BS/CAPMNG/TA_01 TA Id REMS/CSI/CAPMNG/TA_01 Normative source ETSI EN 319 532-4 [11], clause C.2.3.4.1 implementation guidance c.3.1.4) The common capabilities constituted according to ETSI EN 319 532-4 [11], clause C.2.3.4.1, point c.3.1.3) shall be refer... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.5.5.4.2.10 Test assertions for ds:Signature element | REMS/BS/CAPMNG/XSD/TA_42 TA Id REMS/BS/CAPMNG/XSD/TA_42 Normative source XML schema defined in https://forge.etsi.org/rep/esi/x19_53204_rem_services/- /blob/main/1953204CSIxmlSchema.xsd Target Conformance to XML Schema Predicate The ds:Signature child element of CapabilityAndSecurityInformation element meets the test a... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6 Test assertions for ERDS evidence structure and content | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.1 Introduction | Clause 12.6 defines test assertions that shall apply to ERDS Evidence in REM Baseline, specified in ETSI EN 319 532-4 [11], Annex C. Test assertions defined in ETSI TS 119 524-1 [7], clause 6 which have a prescription level equal to Mandatory shall apply, unless otherwise stated in clause 12.6 of the present document. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.2 ERDS evidence set in REM Baseline | The tests assertions referenced in the table below shall apply. Test assertions that shall apply Test assertion identifier ETSI document clause REMS/SERV_PROV/ERDSEVGEN/TA_01 The present document 11.2 REMS/SERV_PROV/ERDSEVGEN/TA_02 The present document 11.2 REMS/SERV_PROV/ERDSEVGEN/TA_03 The present document 11.2 REMS/... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.4 Test assertions for new ERDS Evidence Extensions | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.4.1 Test assertions for GeneralEvidenceInfo extension | REMS/BS/EVIDENCE/TA_20 TA Id REMS/BS/EVIDENCE/TA_20 Normative source ETSI EN 319 532-4 [11], clause C.3.2.1 The Extension (child of Extensions) root element for general additional ERDS information shall be GeneralEvidenceInfo, and it shall have "false" Target Conformance to XML Schema of GeneralEvidenceInfo extension P... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.4.2 Test assertions for RelayEvidenceInfo extension | REMS/BS/EVIDENCE/TA_27 TA Id REMS/BS/EVIDENCE/TA_27 Normative source ETSI EN 319 532-4 [11], clause C.3.2.2 The Extension (child of Extensions) root element for general additional ERDS information shall be RelayEvidenceInfo, and it shall have "false" Target Conformance REM Baseline Predicate The Extension XML element p... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5 Test assertions for contents of ERDS Evidence components | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5.1 Introduction | This clause defines new test assertions derived from the constraints imposed by REM Baseline in ETSI EN 319 532-4 [11], clause C.3.4. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5.2 Test assertions for EvidenceIdentifier element | REMS/BS/EVIDENCE/TA_32 TA Id REMS/BS/EVIDENCE/TA_32 Normative source ETSI EN 319 532-4 [11],clause C.3.4, implementation guideline a) The EvidenceIdentifier element shall be a UID generated according to IETF RFC 5322 [4], clause 3.6.4 Target Conformance to ERDS Evidence in REM Baseline Predicate The EvidenceIdentifier ... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5.3 Test assertions for EventReason element | The test assertion ERDS/EVIDENCE/EVENT_REASONS/TA_01 defined in ETSI TS 119 524-1 [7] shall not apply. ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 102 REMS/BS/EVIDENCE/TA_33 TA Id REMS/BS/EVIDENCE/TA_33 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline d.I) The EventReason element shall be set... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5.4 Test assertions for EvidenceIssuerPolicyID element | REMS/BS/EVIDENCE/TA_37 TA Id REMS/BS/EVIDENCE/TA_37 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline f.I and d.II) Target Conformance to ERDS Evidence in REM Baseline Predicate The EvidenceIssuerPolicyID element has two or more PolicyID XML children Prescription level Mandatory Tag Confor... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5.5 Test assertions for EvidenceIssuerDetails element | REMS/BS/EVIDENCE/TA_40 TA Id REMS/BS/EVIDENCE/TA_40 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline f.I) The EvidenceIssuerPolicyID element shall be set at least with the following URIs: • I. http://uri.etsi.org/19532/v1#/REMbaseline Target Conformance to ERDS Evidence in REM Baseline Pr... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5.6 Test assertions for Identity child element of RecipientDetails element | REMS/BS/EVIDENCE/TA_41 TA Id REMS/BS/EVIDENCE/TA_41 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline h) The SenderDetails/Sender's Identity attributes element shall be set as follows, according to eIDAS TS SAML Attribute Profile [17], clauses 2.2.2 and 2.2.3 Target Conformance to ERDS Evi... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5.7 Test assertions for Identity child element of SenderDetails element | REMS/BS/EVIDENCE/TA_42 TA Id REMS/BS/EVIDENCE/TA_42 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline i) The RecipientDetails/Recipient's Identity attributes element shall be set as follows, according to IDAS Technical Specifications SAML Attribute Profile [17], clauses 2.2.2 and 2.2.3 Tar... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5.8 Test assertions for UserContentInfo element | REMS/BS/EVIDENCE/TA_43 TA Id REMS/BS/EVIDENCE/TA_43 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline l) The value of the element "AppLayerIdentifier" shall be set to the original message's Message-ID header taking care of the necessary transcoding of the not admitted characters in the val... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5.9 Test assertions for MessageIdentifier element | REMS/BS/EVIDENCE/TA_44 TA Id REMS/BS/EVIDENCE/TA_44 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline k) The MessageIdentifier element shall be a UID generated according to IETF RFC 5322 [4], section 3.6.4 Target Conformance to ERDS Evidence in REM Baseline Predicate The value of MessageId... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5.11 Test assertions for ExternalERDSDetails element | REMS/BS/EVIDENCE/TA_47 TA Id REMS/BS/EVIDENCE/TA_47 Normative source ETSI EN 319 532-4 [11], clause C.3.4, implementation guideline q) The ExternalERDSDetails element (..) shall be set as follows, according to eIDAS TS SAML Attribute Profile [17], clauses 2.3.2 and 2.3.4 (…) where The value "LEGAL NAME OF THE SERVICE P... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.6.5.12 Test assertions for ds:Signature element | The test assertions defined in ETSI TS 119 134-4 [13] shall apply. In addition, the tests assertions referenced in the table below shall apply. Test assertions that shall apply Test assertion identifier ETSI document clause REMS/ERDSEVIDSIG/TA_04 The present document 8.2 Finally, the following test assertion shall also... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 1 Scope | The present document defines: 1) A test suite for supporting interoperability tests within the field of Electronic Registered Delivery Services (ERD services or ERDS hereinafter) as specified in ETSI EN 319 522 parts 1 [1], 2 [2], 3 [3], 4 [4], [5] and [6]. The test suite defines test cases for the following environmen... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 2 References | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 3 Definition of terms, symbols and abbreviations | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 319 522-1 [1] apply. |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 3.2 Symbols | Void. |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACC_REJ_EXP ACCeptance REJection EXPiry AS4 Applicability Statement 4 CONS_ACC CONSignment ACCeptance CONS_NOT CONSignment NOTification CONS_NOT_FAIL CONSignment NOTification FAILure CONS_REJ CONSignment REJection CONT_AC_TRACK CONTent ACcess ... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 4 Technical approach | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 4.1 Components of test cases and their identifiers | As it has been mentioned before the present document defines: 1) A test suite for supporting interoperability tests within the field of Electronic Registered Delivery (ERD hereinafter) as specified in ETSI EN 319 522 parts 1 [1], 2 [2], 3 [3], 4 [4], [5] and [6]. 2) A mechanism for documenting new test cases and expand... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 4.2 Adding new test cases to the test suite | The strategy followed for building the definitions of the test cases makes it easy to expand the test suite by incorporation of new test cases. For defining a new test case the following steps are required: 1) Identify the set of receiving entities. If none of the predefined set of entities at the receiving side is the... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5 Scenarios | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.1 Introduction | The present clause defines a number of selected scenarios that will be used in clause 8. Clause 5.3 defines scenarios where sender and recipient(s) are subscribed to the same ERDS (black-box model described in ETSI EN 319 522-1 [1]). Clause 5.4 defines scenarios where the sender and the recipient(s) are subscribed to d... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.2 Abbreviations used in tables defining scenarios | This clause shows some abbreviations (which have already been anticipated in clause 3.3) used in the tables that define the scenarios. Table 2 shows the abbreviations used for the different ERDS evidence. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 12 Table 2: ERDS evidence abbreviations ERDS Evidence name ERDS Evidence ab... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.3 Black-box model scenarios | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.3.1 Introduction | The present clause defines scenarios where the sender and the entities at the receiving side are subscribed to the same ERDS and consequently the user content is not relayed between different ERDSs. Clause 5.3.2 defines scenarios where the ERDS operates in Store and Forward style. Clause 5.3.3 defines scenarios where t... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.3.2 Scenarios without notification for acceptance | Table 3 defines a number of scenarios for the case where sender and the entities at the receiving side are subscribed to the same ERDS and the ERDS does not send notification for acceptance to the entities at the receiving side. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 14 Table 3: Scenarios for intra-ERDS without notifi... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.3.3 Scenarios with notification for acceptance | Table 4 defines a number of scenarios for the case where sender and the entities at receiving side are subscribed to the same ERDS and the ERDS sends notification for acceptance to the entities at the receiving side. Table 4: Scenarios for intra-ERDS with notifications for acceptance (1/7) Scenario id: ERDS_BB_NOT_F_AC... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.4 Scenarios for 4-corner model | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.4.1 Introduction | The present clause defines test cases for scenarios that take place when the sender and the entities at the receiving side are subscribed to different ERDSs but there are not intermediate ERDSs between the SERDS and the RERDS. Clause 5.4.2 defines test cases when RERDS does not notify for acceptance. Clause 5.4.3 defin... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.4.2 Scenarios where RERDS does not use notification for acceptance | Table 5 defines a number of scenarios for the case where RERDS does not notify for acceptance. The scenarios are based on scenarios at Table 3 adding the relay acceptance and relay rejection events at the some of the RERDSs and their corresponding ERDS evidences. For the sake of simplicity, it will be supposes that all... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.4.3 Scenarios where RERDS uses notification for acceptance | Table 6 defines a number of scenarios for the case where RERDS uses notification for acceptance. The scenarios are based on scenarios at Table 4 adding the relay acceptance and relay rejection events at the some of the RERDSs and their corresponding ERDS evidences. For the sake of simplicity, it is supposed that all th... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.5 Scenarios for extended model | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.5.1 Introduction | The present clause defines test cases for scenarios that take place when the sender and the entities at the receiving side are subscribed to different ERDSs and there is one intermediate IERDS between the SERDS and the RERDSs. Clause 5.5.2 defines test cases where the RERDS does not use notification for acceptance. Cla... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.5.2 Scenarios where RERDS does not use notification for acceptance | Table 7 shows scenarios where RERDS does not use notification for acceptance. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 58 Table 7: Scenarios where SERDS operates Store&Notify and RERDS operate Store&Forward (1/6) Scenario id: EXT_RERDS_NO_NOT_F_ACC#1 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC The simplest posi... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 5.5.3 Scenarios where RERDS uses notification for acceptance | Table 8 shows scenarios where RERDS submits notification for acceptance. Table 8: Scenarios where SERDS operates Store&Notify and RERDSs operate Store&Forward (1/3) Scenario id: SERDS_SN_IERDS_SF_RERDS_BB_NO_NOT_F_ACC#1 Purpose Parameter: <ERD_dispatch_1>_WITH_XML_SUB_ACC Var EV_SET#1 = {XML_NOT_F_ACC, XML_NOT_DEL} The... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 6 ERD Messages instances | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 6.1 Introduction and technical approach | The present clause defines a number of instances of the different types of ERD Messages, namely: ERDS notification, ERD payload, ERDS receipt, and ERD dispatch, as defined in ETSI EN 319 522-1 [1]. These instances are used in clause 8 for defining different test cases. The set of ERD messages instances is built followi... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 6.2 Combinations of fields for headers in ERD envelopes | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 6.2.1 Introduction | Clause 6.2.2 defines combinations of values for the metadata components defined in OASIS Standards [i.2] and [8] and further profiled in ETSI EN 319 522-4-1 [4]. Clause 6.2.3 defines combinations of values for the relay metadata components defined in ETSI EN 319 522-3 [3]. Clause 6.2.4 defines aggregations of combinati... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 6.2.2 Combinations of AS4 metadata profiled in ETSI EN 319 522-4 | The present clause defines different combinations of values for the metadata components defined in OASIS Standards [i.2] and [8] and further profiled in ETSI EN 319 522-4-1 [4]. These combinations are shown in Table 9. Cells in column "Component name" contain the name of the metadata components. ETSI ETSI TS 119 524-2 ... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 6.2.3 Combinations of components of relay metadata | Table 10 shows combinations of values of the relay metadata defined in ETSI EN 319 522-3 [3]. For the purpose of defining the test cases, the field "ApplicablePolicy" shall always consist in a single URI. New combinations may be added where this field consists in a sequence of URIs. Cells in "Component name" column con... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 6.2.4 Combinations of AS4 metadata profiled and relay metadata | The present clause defines aggregations of AS4 metadata components defined in OASIS Standards [i.2] and [8] and further profiled in ETSI EN 319 522-4-1 [4], and relay metadata. These combinations are shown in Table 11. Each metadata combination instance is defined as the aggregation of the combination defined in Table ... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 6.3 Instances of ERD payload | As an ERD payload is the aggregation of metadata and user content, the present document defines as many ERD payload instances as metadata instances have been defined in clause 6.2.4. |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 6.4 Instances of ERDS receipts | An ERD receipt is the aggregation of one metadata payload and one or more ERDS evidence payloads. The number and contents of these payloads will depend on the specific test case. The present document uses the following convention for identifying sets of ERDS receipts: ERD_ReceiptInst (Metadata(AS4Met#1,RelayMet#J,nil,n... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 6.5 Instances of ERD dispatch | The present document uses the following convention for identifying sets of ERD dispatches: ERDS_DispatchInst(Metadata(AS4Met#1,RelayMet#J, AssLevelComb, ConsignmentModeId), <EVID#M>+) Where: • J is a positive integer between 1 and 9 (inclusive), AssLevelComb is one of {low/low, substantial/substantial, high/high}, Cons... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 7 Other named sets | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 7.1 Named sets of participating ERDSs | The present clause defines named sets of participating REMSs that are used for naming test cases in clause 5. The details on the participating ERDSs are given using the following pattern: ERDS(I,J), where: • I stands for the number of Intermediate ERDSs (IERDSs); and • J stands for the number of the Recipient's ERDSs (... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 7.2 Named sets of additional requirements | The present clause defines named sets of additional requirements that are used for building different test cases based on the same scenarios of REM messages. Table 12 shows the named sets of additional requirements. Table 12: Named sets of additional requirements Name of the set Additional requirements in the set Addit... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 7.3 Named sets of entities in receiving side | The present clause defines named sets of entities that are present at receiving side. This allows using one scenario in defining different test cases by changing the entities in the receiving side. EXAMPLE: Scenarios defined for one recipient could be used in test cases where the scenarios involve only one delegate of ... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8 Test cases definition | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.1 Introduction | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.1.1 General | The notations shown in clauses 4.1, 6 and 7, allow building a compact notation for defining tests cases. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 91 The present document defines sets of test cases. Each set of test cases is expressed as a function of a number of parameters (some of them are integers, other are tuples of... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.1.2 Notation for black box model scenarios | No ERD messages are generated in the scenarios defined for the black box model. Consequently, the only parameters the test cases depend on are the additional requirements specified in clause 7.2 and the entities present at receiving side, identified in clause 7.3. Below follows the notation used for identifying the set... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.1.3 Notation for 4 corner and extended models scenarios | For helping in understanding the notation, below follows the definition of the set of test cases for the scenario 4C_RERDS_NO_NOT_F_ACC #2. The definition of a set of test cases has two parts. Below follows the first one: 4C_RERDS_NO_NOT_F_ACC #2 ( RecSide(F,G,H), ERD_dispatchInst_WITH_XML_SUB_ACC (Metadata(AS4Met#1, R... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.1.4 Reasons for Failures | The present clause shows the different values that may have the reason for failure parameters in those scenarios where failures occur: • For XML_SUB_REJ, the FailureReasonId is one of {RA02, RA03, RA04, RA05, RA06} as specified in clause 8.3.3.1 of ETSI EN 319 522-2 [2]. • For XML_REL_REJ, the FailureReasonId is one of... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.2 Test cases for black box model | For each scenario the present document defines the set of test cases defined by the following expression: SCENARIOID ( RecSide(F,G,H), AssLevelComb,ConsignmentModelId, AdditionalReqs#P, FailureReasonId ) Where: • For RecSide: (F,G,H) is one of {(1,0,0), (3,0,0), (3,1,2),(3,1,3)}: define test cases for one recipient, se... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.3 Test cases for 4-cornel and extended models | |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.3.1 General | The present clause, instead of showing one test case set expression for each scenario, which would make the present document very long, defines rules for building these expressions for each scenario in function of: the ERD dispatches, ERDS receipts, ERD payloads present in them, the entities at the receiving side, the ... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.3.2 Rules for parametrizing ERD dispatches | The ERD dispatches for these scenarios will be built on the following components: (Metadata(AS4Met#1, RelayMet#I, AssLevelComb, ConsignmentModeId), UserContent,<EVID>+) ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 94 Where: • i is one of {1,2,3,4,5,6,7,8}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.3.3 Rules for parametrizing ERD payloads | The ERD payloads for these scenarios will be built on the following components: (Metadata(AS4Met#1, RelayMet#I, AssLevelComb, ConsignmentModeId), UserContent Where: • i is one of {1,2,3,4,5,6,7,8}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, and ConsignmentModeId is one of {nil, basic, co... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.3.4 Rules for parametrizing ERDS receipts | The ERDS receipts for these scenarios will be built on the following components: (Metadata(AS4Met#1, RelayMet#I, AssLevelComb, nil), <EVID>+) Where: • i is one of {1,2,3,4,5,6,7,8}, AssLevelComb is one of {nil, low/low, substantial/substantial, high/high}, and <EVID>+ stands for the ERDS evidences present in the ERDS r... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.3.5 Rules for parametrizing entities at receiving side | The number and type of entities present at the receiving side will be parametrized as indicated below: RecSide(F,G,H), Where, as specified in clause 7.3: • F stands for the number of recipients. • G stands for the number of recipient's delegates. • H stands for the number of recipients each delegate is delegate of. H s... |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.3.6 Rules for parametrizing failure reasons | The FailureReasonId shall follow the requirements specified in clause 8.1.4. |
8983622e5d417335095cba14cb702b60 | 119 524-2 | 8.3.7 Rules for parametrizing additional requirements | The additional requirements will be parametrized as indicated below: AdditionalReqs#P Where P is one of {1,2} with the meaning specified in clause 7.2. ETSI ETSI TS 119 524-2 V1.2.1 (2023-12) 95 Annex A (informative): Bibliography • ETSI EN 319 532-1: "Electronic Signatures and Infrastructures (ESI); Registered Electro... |
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 1 Scope | The present document defines specific supplementary requirements to those defined in ETSI EN 319 403-1 [1] for CABs performing audits based on ETSI EN 319 411-1 [i.9] and those from CA/Browser Forum, [i.7] and [i.8]. In particular, the present document defines the requirements for audit attestations, including their co... |
abf56025611bf39064e4e57cf7cf5fae | 119 403-2 | 2 References |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.