hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.4 Instances of REMS notification | Table 20 defines instances of REM notifications for being used in test cases. Columns are as in clause 6.3. The notation for the content of cells in column "Instances" is as indicated in clause 6.3, with the addition that the instances of REMS notifications include Extension MIME sections, and the identification of the... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.5 Instances of REMS receipts | Table 21 defines instances of REMS receipts for being used in test cases. Columns are as in clause 6.3. A REMS receipt can have more than one ERDS evidence MIME section. The number and contents of these MIME sections will depend on the specific test case. Table 21: Instances of REMS receipt Instance Purpose REMS_Receip... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.6 Instances of REM dispatch | Table 22 defines instances of REM dispatches for being used in test cases. Columns are as in clause 6.3. Details of the ERDS evidence MIME sections are indicated as in clause 6.5. Table 22: Instances of REM dispatch Instance Purpose REM_dispatchInst (REMSRelayMetadata (RFCFields#I,NewFields#J,nil,nil),REMSIntrCom,FreeT... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 7 Other named sets | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 7.1 Named sets of participating REMSs | The present clause defines named sets of participating REMSs that are used for naming test cases in clause 5. The details on the participating REMSs are given using the following pattern: REMSs(I,J), where: • I stands for the number of Intermediate REMSs (IREMSs); and • J stands for the number of the Recipient's REMSs ... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-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 23 shows the named sets of additional requirements. Table 23: Named sets of additional requirements Name of the set Additional requirements in the set Addit... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-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 ... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8 Test cases definition | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.1 Introduction | The notations shown in clauses 4.1, 6 and 7, allow building a compact notation for defining tests cases. 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 several values, other -mainly reasons for ... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2 Test cases for black-box model | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1 Test cases for Store&Forward style of operation | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.1 Introduction | The present clause defines a set of test cases for each scenario defined in clause XXX (Store&Forward style of operation in the black-box model). Below follow some remarks that apply to all the sets defined in the present clause: • All the scenarios do not deal with relaying of REM messages. REM-RelayDate header field ... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.2 Test cases for scenario REM_SF#1 | REM_SF#1( RecSide(F,G,H), REMS_receipt_with_XML_SUB_REJ (REMSRelayMetadata(RFCFields#I,NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P, FailureReason ) Where: • For RecSide: (F,G,H) is one of {(1,0,0), (3,0,0), (3,1,2),(3,1,3)}: define test cases f... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.3 Test cases for scenario REM_SF#2 | REMSF#2( RecSide(F,G,H), REMS_receipt_with_{2 XML_SUB_REJ} (REMSRelayMetadata(RFCFields#I,NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID#M>+,Sig#N), AdditionalReqs#P FailureReason ) Where: • For RecSide: (F,G,H) is one of {(1,0,0), (3,0,0), (3,1,2),(3,1,3)}: define test cases... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.4 Test cases for scenario REM_SF#3 | REM_SF#3( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_XML_SUB_REJ (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrC... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.5 Test cases for scenario REM_SF#4 | REM_SF#4( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC , XML_CONT_CONS, XML_CONT_CONS_FAIL} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssL... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.6 Test cases for scenario REM_SF#5 | REM_SF#5( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC , XML_CONT_CONS, 2 XML_CONT_CONS_FAIL} (REMSRelayMetadata(RFCFields#I, NewFields#J, As... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.7 Test cases for scenario REM_SF#6 | REM_SF#6( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONT_HAND} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelCo... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.8 Test cases for scenario REM_SF#7 | REM_SF#7( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONT_HAND, XML_CONT_HAND_FAIL} (REMSRelayMetadata(RFCFields#I, New... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.9 Test cases for scenario REM_SF#8 | REM_SF#8( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONT_HAND, 2 XML_CONT_HAND_FAIL} (REMSRelayMetadata(RFCFields#I, N... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.10 Test cases for scenario REM_SF#9 | REM_SF#9( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC,XML_CONS_NOT, XML_CONT_CONS} (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.11 Test cases for scenario REM_SF#10 | REM_SF#10( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONS_NOT, XML_CONS_NOT_FAIL } (REMSRelayMetadata(RFCFields#I, New... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.12 Test cases for scenario REM_SF#11 | REM_SF#11( RecSide(F,G,H), REM_dispatchInst_with_XML_SUB_ACC (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,FreeText#K,HTMLComb,OrMess#L, Ext#M,<EVID#N>,Sig#O), REMS_receipt_with_{XML_SUB_ACC, XML_CONT_CONS, XML_CONS_NOT, 2 XML_CONS_NOT_FAIL } (REMSRelayMetadata(RFCFields#I, N... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.13 Test cases for scenario REM_SF#12 | REM_SF#12( RecSide(F,G,H), REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#J,AssLevelComb,ConsignmentModeId),REMSIntrCom,FreeText#K,HT MLComb,OrMess#L,Sig#M) REMS_receipt_with_XML_SUB_ACC, (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.1.14 Test cases for scenario REM_SF#13 | REM_SF#13( RecSide(F,G,H), REM_payloadInst (REMSRelayMetadata(RFCFields#I,NewFields#J,AssLevelComb,ConsignmentModeId),REMSIntrCom,FreeText#K,HT MLComb,OrMess#L,Sig#M) REMS_receipt_with_XML_SUB_ACC, (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrComb,FreeText#K,HTMLComb,Ext#L,<EVID... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.2 Test cases for Store&Notify style of operation | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.2.1 Rules for REM messages | The following rules will apply for parametrizing the REM messages, which are components of the sets of test cases for scenarios REM_SN#1 to REM_SN#4: REM dispatches with ERDS Evidences will be built on the following components: (REMSRelayMetadata(RFCFields#I, NewFields#J, AssLevelComb, ConsignmentModeId),REMSIntrCom,Fr... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.2.2.2 Rules for failure reasons | The following FailureReason codes will be used for the (black-box model/Store&Notify style): 1) In scenario REMS_SN#2, one of the receiving entities rejects consignment. One XML_CONS_REJ ERDS evidence is generated and encapsulated in a REMS receipt. For this scenario the reason for failure code is RC08 as specified in ... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.3 Test cases for 4-corner model | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.3.1 Introduction and general rules | In this model, SREMS relays REM messages to the RREMS. Below follow a set of rules that govern the values of NewFields#J, Assurance levels indication, and Consignment mode indication: 1) For NewFields#1 and NewFields#4 neither Assurance levels indication nor Consignment mode indication are present. ETSI ETSI TS 119 534... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.3.2 Test cases for Store&Forward to Store&Forward scenarios | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.3.2.1 Rules for REM messages | The following rules will apply for parametrizing the REM messages, which are components of the sets of test cases for scenarios SREMS_SF_RREMS_SF#1 to SREMS_SF_RREMS_SF#5: REM dispatches that are relayed from SREMS to RREMS and REM dispatches that are generated by RREMS from REM dispatches that have been relayed by the... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.3.2.2 Rules for failure reasons | The following FailureReason codes will be used for the (4-corner model/Store&Forward to Store&Forward): 1) In scenario SREMS_SF_RREMS_SF#1, RREMS rejects relaying of the REM dispatch generated by SREMS. One XML_REL_REJ ERDS evidence is generated and encapsulated in a REMS receipt. For this scenario the reason for failu... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.3.3 Test cases for Store&Forward to Store&Notify scenarios | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.3.3.1 Rules for REM messages | The rules that will apply for parametrizing the REM messages, which are components of the sets of test cases for scenarios SREMS_SF_RREMS_SN#1 to SREMS_SF_RREMS_SN#5 shall be the same as the rules defined in clause 8.3.2.1 for Store&Forward to Store&Forward scenarios. |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.3.3.2 Rules for failure reasons | The following FailureReason codes will be used for the (4-corner model/Store&Forward to Store&Notify): 1) In scenario SREMS_SF_RREMS_SN#2, one receiving entity rejects consignment. One XML_CONS_REJ ERDS evidence is generated and encapsulated in a REMS receipt. For this scenario the reason for failure code is RC08 as sp... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.3.4 Test cases for Store&Notify to Store&Forward scenarios | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.3.4.1 Rules for REM messages | The rules that will apply for parametrizing the REM messages, which are components of the sets of test cases for scenarios SREMS_SN_RREMS_SF#1 to SREMS_SN_RREMS_SF#5 shall be the same as the rules defined in clause 8.3.2.1 for Store&Forward to Store&Forward scenarios. |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.3.4.2 Rules for failure reasons | The following FailureReason codes will be used for the (4-corner model/Store&Notify to Store&Forward): 1) In scenario SREMS_SN_RREMS_SF#2, one receiving entity rejects consignment. One XML_CONS_REJ ERDS evidence is generated and encapsulated in a REMS receipt. For this scenario the reason for failure code is RC08 as sp... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.4 Test cases for extended model | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.4.1 Test cases for scenarios S&F->S&F->S&F | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.4.1.1 Rules for REM messages | The rules that will apply for parametrizing the REM messages, which are components of the sets of test cases for scenarios SREMS_SF_IREMS_SF_RREMS_SF#1 to SREMS_SF_IREMS_SF_RREMS_SF#5 shall be the same as the rules defined in clause 8.3.2.1 for Store&Forward to Store&Forward scenarios. |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.4.1.2 Rules for failure reasons | The following FailureReason codes will be used for the (extended model/S&F->S&F-S&F): 1) In scenario SREMS_SF_IREMS_SF_RREMS_SF#2, one of the consignments to a receiving entity fails. One XML_CONT_CONS_FAIL ERDS Evidence is generated. For this scenario the reason for failure code is one of {RD04, RD05, RD06} as specifi... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.4.2 Test cases for scenarios S&F->S&N->S&F | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.4.2.1 Rules for REM messages | The rules that will apply for parametrizing the REM messages, which are components of the sets of test cases for scenarios SREMS_SF_IREMS_SN_RREMS_SF#1 to SREMS_SF_IREMS_SN_RREMS_SF#3 shall be the same as the rules defined in clause 8.3.2.1 for Store&Forward to Store&Forward scenarios. |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 8.4.2.2 Rules for failure reasons | The following FailureReason codes will be used for the (extended model/S&F->S&N-S&F): 1) In scenario SREMS_SF_IREMS_SN_RREMS_SF#2, one of the receiving entities rejects consignment. One XML_CONS_REJ ERDS Evidence is generated. For this scenario the reason for failure code is RC08 as specified in clause 8.3.3.3 of ETSI ... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 9 Test suite for REM Baseline | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 9.1 Introduction | Clause 9 defines test cases for REM Baseline. All the test cases are defined for 4-corner models based on Store&Forward to Store&Forward scenarios. All the test cases are defined assuming only the mandatory contents for all the REM Messages. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 119 |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 9.2 Test cases for REM Baseline | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 9.2.1 Combinations of fields for the REM relay metadata header | Below follow the combinations of headers for these test cases. Table 24: Combinations of header fields defined in MIME and S/MIME RFCs Combination identifier Field name Value RFCFields_BS_REMS _RELAY_H#3 Reply-To As specified in ETSI EN 319 532-3 [5] From As specified in ETSI EN 319 532-3 [5] To As recommended in ETSI ... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 9.2.2 Combinations of fields for the signed data MIME section header | Below follow the combinations of headers for these test cases. Table 26: Combinations of header fields defined in MIME and S/MIME RFCs Combination identifier Field name Value RFCFields_BS _SIGDAT_H#5 Content-Type As specified in ETSI EN 319 532-4 [6], clause 5.4.2 |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 9.2.3 Combinations of fields for the introduction MIME section header | Below follow the combinations of headers for these test cases. Table 27: Combinations of new header fields defined in ETSI EN 319 532-3 [5] Combination identifier Field name Value NewFields_BS _INTR_H#1 REM-Section-Type As specified in ETSI EN 319 532-4 [6], clause 5.4.3.1 |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 9.2.4 Combinations of fields for the free text MIME subsection header | Below follow the combinations of headers for these test cases. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 120 Table 28: Combinations of header fields defined in MIME and S/MIME RFCs Combination identifier Field name Value RFCFields_BS _FREETXT_H#1 Content-Type As specified in ETSI EN 319 532-4 [6], clause 5.4.3.2 |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 9.2.5 Combinations of fields for the HTML MIME subsection header | Below follow the combinations of headers for these test cases. Table 29: Combinations of header fields defined in MIME and S/MIME RFCs Combination identifier Field name Value RFCFields_BS _HTML_H#1 Content-Type As specified in ETSI EN 319 532-4 [6], clause 5.4.3.3 9.2.6 Combinations of fields for the original message M... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 9.2.7 Combinations of fields for the ERDS evidence MIME section header | Below follow the combinations of headers for these test cases. Table 31: Combinations of new header fields defined in ETSI EN 319 532-3 [5] Combination identifier Field name Value NewFields_BS _EVID_H#1 REM-Section-Type As specified in ETSI EN 319 532-4 [6], clause 5.4.6 Table 32: Combinations of header fields defined ... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 9.2.8 Combinations of fields for the REMS signature MIME section header | Below follow the combinations of headers for these test cases. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 121 Table 33: Combinations of header fields defined in MIME and S/MIME RFCs Combination identifier Field name Value RFCFields_BS _SIG_H#1 Content-Type As specified in ETSI EN 319 532-4 [6], clause 5.4.7 Content-Dispos... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 1 Scope | The present document defines the set of checks to be performed for testing conformance in the provision of Registered Electronic Mail Services against the specific technical requirements defined in ETSI EN 319 532-3 [1] and against technical requirements for the provision of the service defined in ETSI EN 319 532-1 [2]... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 2 References | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 3 Definition of terms, symbols and abbreviations | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 319 532-1 [2] apply. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 3.2 Symbols | Void. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ARI Acceptance/Rejection Interface CA Certification Authority CSI Common Service Infrastructure DER Distinguished Encoding Rules DNS Domain Name System eIDAS electronic Identification, Authentication and Trust Services ERD Electronic Registere... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 4 Overview | The present clause describes the main aspects of the technical approach used for specifying the whole set of tests to be performed for testing conformance against ETSI EN 319 532-3 [1] with the scope defined in clause 1 of the present document. No tests are included testing conformance on requirements not specified in ... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 5.1 Introduction | This clause defines the whole set of assertions required for testing compliance of the requirements defined by ETSI EN 319 532-3 [1] for the header fields present in the following REM messages' MIME section headers: 1) The REMS Relay metadata MIME section header. This defines test assertions for [1], clause 6.2.1. 2) T... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 5.4.1 Test assertions for Introduction MIME section header | This clause defines test assertions for the headers in the Introduction MIME section. Clauses 5.4.2 and 5.4.3 define test assertions for headers in the two alternative MIME sub-sections, namely the free-text, and the HTML sub-sections. ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 28 REMS/HEADER/INTRO/FIELD/TA_01 TA Id REMS/... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 5.4.2 Test assertions for free text MIME subsection header | REMS/HEADER/INTRO/FREETEXT/FIELD/TA_01 TA Id REMS/HEADER/INTRO/FREETEXT/FIELD/TA_01 Normative source ETSI EN 319 532-3 [1], clause 6.2.3.2 Content-Type The value for this field shall be: "text/plain" 'charset' parameter value should be "UTF-8" Target Conformance to Introduction MIME section header, Free Text sub-sectio... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 5.4.3 Test assertions for HTML MIME subsection header | REMS/HEADER/INTRO/HTML/FIELD/TA_01 TA Id REMS/HEADER/INTRO/HTML/FIELD/TA_01 Normative source ETSI EN 319 532-3 [1], clause 6.2.3.3 Content-Type The value for this field shall be: "text/html;". 'charset' parameter value should be "UTF-8" Target Conformance to Introduction MIME section header, HTML sub-section MIME heade... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 6 Test assertions for MIME sections bodies | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 6.1 Introduction | This clause defines the whole set of assertions required for testing compliance of the requirements defined by ETSI EN 319 532-3 [1] for REMS Plain text introduction MIME section body and the REMS HTML introduction MIME section body specified by ETSI EN 319 532-3 [1], clause 6.2.3.4. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 6.2 Test assertions for Introduction MIME section body | This clause defines test assertions for the body of the Introduction MIME section as specified in clause 6.2.3.4 of ETSI EN 319 532-3 [1]. REMS/BODY/INTRO/CONTENT/TA_01 TA Id REMS/BODY/INTRO/CONTEN/TA_01 Normative source ETSI EN 319 532-3 [1], clause 6.2.3.4 Introduction MIME section body If both sections are present t... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 7 Test assertions for REM messages structures | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 7.1 Introduction | This clause defines test assertions for testing presence and cardinality of the different MIME headers and bodies for each type of REM message. ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 47 |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 7.2 Test assertions for REM payload structure | REMS/MSSG/STRUCT/REMPAYLOAD/TA_01 TA Id REMS/MSSG/STRUCT/REMPAYLOAD/TA_01 Normative source ETSI EN 319 532-3 [1], clause 4.3 and Figure 4 Target Conformance to REM payload structure Predicate One conformant outermost MIME section is present Prescription level Mandatory Tag Conformance, REMS, REMSP, REM payload REMS/MSS... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 7.3 Test assertions for REMS notification structure | REMS/MSSG/STRUCT/REMNOT/TA_01 TA Id REMS/MSSG/STRUCT/REMNOT/TA_01 Normative source ETSI EN 319 532-3 [1], clause 4.3 and Figure 3 Target Conformance to REM notification structure Predicate One conformant outermost MIME section is present Prescription level Mandatory Tag Conformance, REMS, REMSP, REM notification REMS/M... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 7.4 Test assertions for REMS notification structure | REMS/MSSG/STRUCT/REMRECEIPT/TA_01 TA Id REMS/MSSG/STRUCT/REMRECEIPT/TA_01 Normative source ETSI EN 319 532-3 [1], clause 4.3 and Figure 2 Target Conformance to REM receipt structure Predicate One conformant outermost MIME section is present Prescription level Mandatory Tag Conformance, REMS, REMSP, REM receipt REMS/MSS... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 7.5 Test assertions for REM dispatch structure | REMS/MSSG/STRUCT/REMDISPATCH/TA_01 TA Id REMS/MSSG/STRUCT/REMDISPATCH/TA_01 Normative source ETSI EN 319 532-3 [1], clause 4.3 and Figure 1 Target Conformance to REM dispatch structure Predicate One conformant outermost MIME section is present Prescription level Mandatory Tag Conformance, REMS, REMSP, REM dispatch REMS... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 8 Test assertions for REM messages structures | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 8.1 Introduction | This clause defines test assertions for testing: 1) signatures that individually sign ERDS evidence (clause 8.2); and 2) signatures that sign REM messages (clause 8.3). 8.2 Test assertions for signatures individually signing ERDS evidence REMS/ERDSEVIDSIG/TA_01 TA Id REMS/ERDSEVIDSIG/TA_01 Normative source ETSI EN 319 ... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 8.3 Test assertions for signatures signing REM messages | REMS/REMMESSSIG/TA_01 TA Id REMS/REMMESSSIG/TA_01 Normative source ETSI EN 319 532-3 [1], clause 8.1 The algorithms and key lengths used to generate digital signatures should be as specified in ETSI TS 119 312 [i.1] Target Conformance to REM Message signature Predicate The algorithms and key lengths used to generate th... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 9 Test assertions for Common Service Interface | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 9.1 Introduction | This clause defines test assertions for testing conformance against the specifications in ETSI EN 319 532-3 [1] on the Common Service Interface. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 9.2 Test assertions for routing information | REMS/CSI/ROUTING/TA_01 TA Id REMS/CSI/ROUTING/TA_01 Normative source ETSI EN 319 532-3 [1], clause 9.2 The REM RI (Relay Interface) should be identified by a transport protocol, a hostname and a port number Target Conformance to CSI Routing information Predicate The REM RI (Relay Interface) is identified by a transport... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 9.3 Test assertions for trust information binding | If the information on REMS and REMSPs are published using Trusted Lists, the test assertions defined below shall apply to the contents of the Trusted Lists listing REM services. ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 56 REMS/CSI/TRUST/TA_01 TA Id REMS/CSI/TRUST/TA_01 Normative source ETSI EN 319 532-3 [1], clause 9.3 ... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 9.4 Test assertions for capability discovery and management | REMS/CSI/CAPMNG/TA_01 TA Id REMS/CSI/CAPMNG/TA_01 Normative source ETSI EN 319 532-3 [1], clause 9.4 If the REMS uses TL to publish trust information about itself, the REMS capability metadata may also be published using the TL, as indicated for ERDS capability metadata in clause 7.2 of ETSI EN 319 522-4-3 [i.6] Target... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 11 Test assertions for provision of the service | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 11.1 Introduction | This 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 REM... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 11.3 Test assertions on REM interfaces | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 11.3.1 Introduction | This clause defines test assertions on REM interfaces. Clause 11.3.2 defines test assertions for testing security measures implemented in REM interfaces. Clause 11.3.3 defines test assertions for testing the provision of the REM interfaces. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 11.3.2 Security measures on REM interfaces | The test assertions defined in ETSI TS 119 524-1 [7] clause 11.3.2, replacing ERDS by REMS, shall apply except the following ones: • ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_03, ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_07, and ERDS/SERV_PROV/INTFACE/SEC_MEAS/TA_11, because they deal with ERD-UA MEPI, which, as stated in clause 5 o... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 11.3.3 Test assertions on provision of REM interfaces | The test assertions defined in ETSI TS 119 524-1 [7] clause 11.3.3, replacing ERDS by REMS, shall apply, except the following one: • ERDS/SERV_PROV/INTFACE/PROV/TA_02, because this test assertion deals with ERD-UA MEPI, which, as stated in clause 5 of ETSI EN 319 532-1 [2], is an interface not defined for REMS, and the... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12 Test assertions for REM Baseline | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.1 Introduction | This clause contains test assertions which are specific for testing conformance of REM Baseline. Testing conformance of REM Baseline shall require testing the test assertions specified in the present clause and test assertions specified in clauses 5 to 11 of the present document, except those ones that are superseded o... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2 Test assertions for SMIME sections headers | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2.1 Introduction | Clause 12.2 specifies the test assertions required for testing compliance of the requirements defined in REM Baseline for the header fields present in the following REM messages' MIME section headers for REM Baseline SMIME sections in REM messages. 1) The REMS Relay metadata MIME section header. This clause defines new... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2.2 Test assertions for the REMS Relay metadata header | All the tests assertions defined in clause 5.2 with a prescription level of Mandatory shall apply, unless stated otherwise. In addition, the following test assertions shall also apply. REMS/BS/HEADER/REMSRELAY/FIELD/TA_01 TA Id REMS/BS/HEADER/REMSRELAY/FIELD/TA_01 Normative source ETSI EN 319 532-4 [11] clause C.4.5.4,... |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2.3 Test assertions for fields in the signed data MIME section header | All the tests assertions defined in clause 5.3 with a prescription level of Mandatory shall apply, unless stated otherwise. |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2.4 Test assertions for fields in REMS introduction MIME section header | |
4f9d8cab416c99e490f57fde6231c491 | 119 534-1 | 12.2.4.1 Test assertions for Introduction MIME section header | All the tests assertions defined in clause 5.4.1 with a prescription level of Mandatory shall apply, unless stated otherwise. The tests assertions referenced in the table below shall not apply. ETSI ETSI TS 119 534-1 V1.2.1 (2023-12) 71 Test assertions that shall not apply Test assertion identifier ETSI document clause... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.