hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.3.14 List issue date and time | Presence: This field shall be present. Description: It specifies the date and time on which the trusted list was issued. Format: Date-time value (see clause 5.1.3). Value: Coordinated Universal Time (UTC) at which the TL was issued. NOTE: See also the applicable requirement on TLSO to ensure the consistency of the (re)... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.3.15 Next update | Presence: This field shall be present. Description: It specifies the date and time by which, at the latest, an update of the TL will be made available by the scheme operator or be null to indicate a closed TL. Format: Date-time value (see clause 5.1.3). Value: Coordinated Universal Time (UTC) by which, at the latest, a... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.3.16 Distribution points | Presence: This field is optional. Description: When used, it specifies locations where the current TL is published and where updates to the current TL can be found. Format: Non-empty sequence of URIs. Value: Dereferencing the given URI will always deliver the latest update of this TL. If multiple distribution points ar... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.3.17 Scheme extensions | Presence: This field shall not be present for EU Member States' trusted lists. It is optional for non-EU countries and international organizations. Description: It provides specific scheme-related information and enhancements that do not require a change in the version identifier, which can be interpreted by all access... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.3.18 Trust Service Provider List | Presence: If no TSP is or was approved in the context of the trusted list scheme, this field shall not be present. If one or more TSP services are or were approved under the TL scheme, this field shall be present. Description: List of TSPs and their trust services approved in accordance with the trusted list scheme. Fo... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.4 TSP information | |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.4.1 TSP name | Presence: This field shall be present. Description: It specifies the name of the legal entity, or when applicable the natural person, responsible for the TSP's services that are or were recognized by the scheme, in particular for the TSP's services that are or were approved under the applicable scheme. Format: A sequen... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.4.2 TSP trade name | Presence: This field shall be present. Description: It specifies an official registration identifier as registered in official records, where such a registered identifier exists, that unambiguously identifies the TSP. It may additionally be used to specify an alternative name under which the TSP identifies itself in th... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.4.3 TSP address | |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.4.3.0 General | Presence: This field shall be present. Description: It specifies the address of the legal entity or mandated organization, or when applicable the natural person, identified in the 'TSP name' field (clause 5.4.1) for both postal and electronic communications. Format: This is a multi-part field consisting of the TSP phys... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.4.3.1 TSP postal address | Presence: This field shall be present. Description: It specifies the postal address of the TSP identified in clause 5.4.1, with the provision for the inclusion of the address in multiple languages. Format: As specified in clause 5.3.5.1. Value: This shall be a postal address at which the TSP provides a customer care or... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.4.3.2 TSP electronic address | Presence: This field shall be present. Description: It specifies an email address, a web-site URI, and an optional telephone number of the TSP identified in clause 5.4.1, to be used for electronic communications. Format: As specified in clause 5.3.5.2. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 29 Value: The e-mail address,... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.4.4 TSP information URI | Presence: This field shall be present. Description: It specifies the URI(s) where users (e.g. relying parties) can obtain TSP-specific information. Format: Sequence of multilingual pointers (see clause 5.1.4). Value: The referenced URI(s) shall provide a path to information describing or leading to the description of t... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.4.5 TSP information extensions | Presence: This field is optional. Description: It may be used by scheme operators to provide specific TSP-related information, to be interpreted according to the specific scheme's rules. Format: Sequence of TSP extensions whose format is left open. Value: Each TSP information extension may be selected by the scheme ope... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.4.6 TSP Services (list of services) | Presence: This field shall be present. Description: It contains a sequence identifying each of the TSP's recognized services and the approval status (and history of that status) of that service. Format: A sequence of TSP Service elements, where each of such TSP Service element is a tuple made of a Service Information e... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5 Service information | |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.1 Service type identifier | |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.1.0 General requirements | Presence: This field shall be present. Description: It specifies the identifier of the service type. Format: An indicator expressed as a URI. Value: The quoted URI shall be: a) one of the URIs specified in clause 5.5.1.1 corresponding to the type of listed trust service for qualified trust services specified in Regulat... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.1.1 Regulation (EU) No 910/2014 qualified trust service types | (a) URI: http://uri.etsi.org/TrstSvc/Svctype/CA/QC Description: A qualified certificate issuing trust service creating and signing qualified certificates based on the identity and other attributes verified by the relevant registration services, and under which are provided the relevant and related revocation and certif... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.1.2 Regulation (EU) No 910/2014 non qualified trust service types | Unless explicitly stated, those services shall not fall under the category of services not using PKI public-key technology (see clause 5.5.3). (a) URI: http://uri.etsi.org/TrstSvc/Svctype/CA/PKC Description: A certificate generation service, not qualified, creating and signing non-qualified public key certificates base... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.2 Service name | Presence: This field shall be present. Description: It specifies the name under which the TSP identified in 'TSP name' (clause 5.4.1) provides the service whose type is identified in 'Service type identifier' (clause 5.5.1). Format: A sequence of multilingual character strings (see clause 5.1.4). Value: The name under ... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.3 Service digital identity | Presence: This field shall be present. Description: It specifies one and only one service digital identifier uniquely and unambiguously identifying the service with the type it is associated to (as identified in 'Service type identifier', clause 5.5.1). Format: When not using PKI public-key technology (e.g. for a servi... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.4 Service current status | Presence: This field shall be present. Description: It specifies the identifier of the current status of the service. Format: An identifier expressed as an URI. Value: In the context of EU Member States, from the date Regulation (EU) No 910/2014 [i.10] applies: i) The identifier of the status of the services of a type ... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.5 Current status starting date and time | Presence: This field shall be present. Description: It specifies the date and time on which the current approval status became effective. Format: Date-time value (see clause 5.1.3). Value: Coordinated Universal Time (UTC) at which the current approval status became effective. TLSO shall ensure the consistency of the (r... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.6 Scheme service definition URI | Presence: This field is optional. Description: It specifies the URI(s) where relying parties can obtain service-specific information provided by the TL scheme operator. Format: A sequence of multilingual pointers (see clause 5.1.4). Value: The referenced URI(s) shall provide a path to information describing the service... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.7 Service supply points | Presence: This field is optional. Description: It specifies one or more URIs where relying parties can access the service, or component services or other types of services related with the service. Optionally, for each URI it specifies the type of service that can be accessed at this URI. Format: Non-empty sequence of ... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.8 TSP service definition URI | Presence: When the service type is "http://uri.etsi.org/TrstSvc/Svctype/NationalRootCA-QC" (clause 5.5.1.3), this field shall be present. In other cases, this field is optional. Description: It specifies the URI(s) where relying parties can obtain service-specific information provided by the TSP. Format: A sequence of ... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.9 Service information extensions | |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.9.0 General | Presence: This field is optional. Description: It specifies specific service-related information. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 44 Format: Sequence of service information extensions, each of which is formatted as specified in next clauses and each of which may be selected by the TLSO according to the meaning an... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.9.1 expiredCertsRevocationInfo Extension | Presence: This field is optional but may only be present when used with the following 'Service types' (clause 5.5.1): - "http://uri.etsi.org/TrstSvc/Svctype/CA/PKC"; - "http://uri.etsi.org/TrstSvc/Svctype/CA/QC"; - "http://uri.etsi.org/TrstSvc/Svctype/NationalRootCA-QC"; - "http://uri.etsi.org/TrstSvc/Svctype/Certstatu... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.9.2 Qualifications Extension | |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.9.2.0 General | Presence: This field shall be present when the information present in the qualified certificates created and signed by or under a listed trust service of the type "CA/QC" does not allow machine-processable identification: - of the fact that it is a claimed qualified certificate or not; and/or - whether or not the priva... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.9.2.1 QualificationElement | Presence: This field shall be present. Description: This field bundles a list of assertions (criteria) that specifies the attributes identifying the certificates (e.g. certain key-usage-bits set) to which a list of qualifiers apply that specify some certificate properties (e.g. it is a qualified certificate or not, the... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.9.2.2 CriteriaList | 5.5.9.2.2.0 General Presence: This field shall be present. Description: It provides a list of assertions related to certificate contents (e.g. key usage) and/or status (e.g. additional assessment) used to filter certificates. An assertion can be itself a CriteriaList allowing a recursive definition. An optional Descrip... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.9.2.3 Qualifier | Presence: This field shall be present. Description: It specifies the properties a certificate with the specified criteria possesses. Format: Sequence of indicators expressed as URIs. Value: The following qualifiers shall only be used when the type of the service to which it applies is "CA/QC". They are defined in claus... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.9.3 TakenOverBy Extension | Presence: This field shall be present when a service that was formerly under the legal responsibility of a TSP is taken over by another TSP. Description: It specifies the identity of the TSP having taken over the responsibility of the service to which this extension applies and is meant to state formally the nature of ... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.9.4 additionalServiceInformation Extension | Presence: This field is optional. Description: It specifies additional information on a service. Format: A sequence of one or more tuples, each tuple providing the information detailed below. A TL may have more than one additionalServiceInformation extension in the same service entry, each extension giving: a) an URI i... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.5.10 Service history | Presence: This field shall be present only when historical information is applicable to the related service. In the case the service has no history prior to the current status (i.e. a first recorded status or history information not retained by the scheme operator) this field shall not be present. Description: It speci... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.6 Service history instance | |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.6.1 Service type identifier | Presence: This field shall be present. Description: It specifies the identifier of the service type, with the Format and Value used in clause 5.5.1. |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.6.2 Service name | Presence: This field shall be present. Description: It specifies the name under which the TSP provided the service identified in clause 5.5.1, with the Format and Value used in clause 5.5.2. NOTE: This clause does not require the name to be the same as that specified in clause 5.5.2. A change of name may be one of the ... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.6.3 Service digital identity | Presence: This field shall be present. Description: It specifies at least one representation of a digital identifier of the service used in clause 5.5.1, with the Format and Value used in clause 5.5.3 for any representation, with at least the X509SKI element and to the exception of any certificate. |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.6.4 Service previous status | Presence: This field shall be present. Description: It specifies the identifier of the previous status of the service, with the Format and Value used in clause 5.5.4. |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.6.5 Previous status starting date and time | Presence: This field shall be present. Description: It specifies the date and time on which the previous status in question became effective, with the Format and Value used in clause 5.5.5. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 51 |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.6.6 Service information extensions | Presence: This field is optional. Description: It may be used by TLSOs to provide specific service-related information, to be interpreted according to the specific scheme's rules, with the Format and Value used in clause 5.5.9. |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.7 Digital signature | |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.7.1 Digitally signed Trusted List | The trusted list shall be digitally signed by the 'Scheme operator name' (clause 5.3.4) to ensure its authenticity and integrity. The format of the digital signature shall be XAdES-B-B as defined by ETSI EN 319 132-1 [3]. Such digital signature implementation shall meet requirements as stated in annex B. The digital si... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.7.2 Digital signature algorithm identifier | Presence: This field shall be present. Description: It specifies the cryptographic algorithm that has been used to create the digital signature. Depending on the algorithm used, this field may require additional parameters. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 52 Format: Character string or Bit string is suggested, de... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 5.7.3 Digital signature value | Presence: This field shall be present. Description: It contains the actual value of the digital signature. Value: All fields of the TL except the signature value itself shall be included in the calculation of the digital signature. |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 6 Operations | |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 6.1 TL publication | TL Scheme Operators shall make TLs available through the Hypertext Transfer Protocol (HTTP) defined in IETF RFC 2616 [7]. TLSOs may in addition support publication through LDAP, or FTP. The HTTP URI pointing to the TL shall be without any special character, shall contain a fully qualified domain name in the host sectio... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 6.2 Transport Protocols | |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 6.2.1 HTTP-Transport | |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 6.2.1.1 HTTP-Media Type | This clause specifies a means for transport of TLs via the Internet using HTTP. ETSI ETSI TS 119 612 V2.4.1 (2025-08) 53 TL payloads shall be sent using the following media type: • application/vnd.etsi.tsl+xml The client may, when sending requests, provide an HTTP Accept header field. This header field should indicate ... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 6.2.2 MIME registrations | A MIME-Type and a file-extensions support the transfer of TLs: MIME media type name: Application MIME subtype name: vnd.etsi.tsl+xml Required parameters: none encoding considerations: binary File extension: xml or xtsl Security considerations: TLs do not contain any active code or invoke any automated processing by its... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 6.3 TL Distribution Points in trust service tokens | Trust Service Providers may wish to give information on how to locate a TL of the scheme they operate under. To do so, they may include an appropriate extension in their trust service tokens (e.g. certificates, CRLs, time-stamp tokens, OCSP responses and other). If such extension mechanism allows for the expression of ... |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 6.4 TL availability | TLSOs shall make their TLs available 24 hours a day and 7 days a week, with an availability percentage of minimum 99,9 % over one year. |
2c97fbdab5c9922ce792e755087f81ec | 119 612 | 6.5 TLSO practices | The TLSO shall define, maintain and implement appropriate measures, practices and policies, including change management and security procedures, for establishing, publishing and maintaining the trusted list to ensure that the information provided in the trusted list is timely, accurate, complete and authentic. ETSI ETS... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 1 Scope | The present document defines: 1) A test suite for supporting interoperability tests within the field of Registered Electronic Mail (REM hereinafter) as specified in ETSI EN 319 532 parts 1 [3], 2 [4], 3 [5] and 4 [6]. The test suite defines test cases for the following environments: - Environments that correspond to th... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 2 References | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-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... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-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... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 3 Definition of terms, symbols and abbreviations | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI EN 319 532-1 [3] apply. |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 3.2 Symbols | Void. |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACC_REJ_EXP ACCeptanceREJectionEXPiry CONS_ACC CONSignmentACCeptance CONS_NOT CONSignmentNOTification CONS_NOT_FAIL CONSignmentNOTificationFAILure CONS_REJ CONSignmentREJection CONT_CONS CONTentCONSignment CONT_CONS_FAIL CONTentCONSignmentFAIL... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 4 Technical approach | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-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 Registered Electronic Mail (REM hereinafter) as specified in ETSI EN 319 532 parts 1 [3], 2 [4], 3 [5] and 4 [6]. 2) A mechanism for documenting new test cases and expanding the aforem... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-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... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5 Scenarios | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-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 REMS. Clause 5.4 defines scenarios where the sender and the recipient(s) are subscribed to different REMSs and there are not intermediate REMSs b... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.2 Abbreviations used in tables defining scenarios | The present clause shows some abbreviations (which have already been anticipated in clause 3.3 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 534-2 V1.2.1 (2023-12) 12 Table 2: ERDS e... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.3 Black-box model scenarios | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.3.1 Introduction | This clause defines scenarios where the sender and the entities at the receiving side are subscribed to the same REMS and consequently REM messages are not relayed between different REMSs. Clause 5.3.2 defines scenarios where the REMS operates in Store and Forward style. Clause 5.3.3 defines scenarios where the REMS op... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.3.2 Scenarios for Store and Forward style | Table 3 defines a number of scenarios for the case where sender and the entities at receiving side are subscribed to the same REMS operating in Store and Forward style. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 13 Table 3: Scenarios for intra-REMS operating in Store and Forward style (1/13) Scenario id: REMS_SF#1 Purpose... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.3.3 Scenarios for Store and Notify style | Table 4 defines a number of scenarios for the case where sender and the entities at receiving side are subscribed to the same REMS operating in Store and Notify style. Table 4: Scenarios for intra-REMS operating in Store&Notify model of operation (1/4) Scenario id: REMS_SN#1 Purpose Parameter: <REM_dispatch>_with_XML_S... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.4 Scenarios for 4-corner model | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-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 REMSs but there are not intermediate REMSs between the SREMS and the RREMSs. Clause 5.4.2 defines test cases when both REMSs operate in Store and Forward style. Clause 5... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.4.2 Scenarios for Store&Forward to Store&Forward | Table 5 defines a number of scenarios for the case where SREMS and RREMS operate both Store and Forward style and are NOT the same REMS. The scenarios are based on scenarios in Table 3 adding the relay acceptance and relay rejection events at the some of the RREMSs and their corresponding ERDS evidences. For the sake o... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.4.3 Scenarios for Store&Forward to Store&Notify | Table 6 defines a number of scenarios for the case where SREMS operates Store and Forward and RREMS operates Store and Notify. The scenarios are based on scenarios in Table 4 adding the relay acceptance and relay rejection events at the some of the RREMSs and their corresponding ERDS evidences. For the sake of simplici... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.4.4 Scenarios for Store&Notify to Store&Forward | Table 7 defines a number of scenarios for the case where SREMS operates Store and Notify and RREMS operates Store and Forward. For the sake of simplicity, it will suppose that all the entities at receiving side are served by the same RREMS. It could be possible to use the templates defined in the present document for d... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.5 Scenarios for extended model | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-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 REMSs and there is one intermediate IREMS between the SREMS and the RREMSs. Clause 5.5.2 defines test cases when the all the REMSs operate in Store and Forward style. Cl... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.5.2 Scenarios for S&F->S&F->S&F | Table 8 shows scenarios where SREMS, IREMS and RREMS all operate in Store and Forward style. The sets of scenarios shown in Table 8 extend the set shown in clause 4.4.2.1 of ETSI EN 319 532-1 [3]. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 61 Table 8: Scenarios where SREMS, IREMS, RREMSs all operate in Store&Forward style... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 5.5.3 Scenarios for S&F -> S&N -> S&F | Table 9 shows scenarios where SREMS, and RREMS operate Store and Forward style and IREMS operates Store and Notify. The sets of scenarios shown in Table 9 extend the set shown in clause 4.4.2.2 of ETSI EN 319 532-1 [3]. ETSI ETSI TS 119 534-2 V1.2.1 (2023-12) 70 Table 9: Scenarios where SREMS and RREMSs operate Store&F... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6 REM Messages instances | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.1 Introduction and technical approach | The present clause defines a number of instances of the different types of REM Messages, namely: • REMS notification; • REM payload; • REMS receipt; and • REM dispatch; • as defined in ETSI EN 319 532-1 [3]. These instances are used in clause 8 for defining different test cases. The set of REM message instances is buil... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2 Combinations of fields for headers in REM envelopes | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2.1 Introduction | The following clauses define combinations of headers fields for all the headers that may be present in REM envelopes, namely: the REMS relay metadata MIME Header, the signed data MIME header, the headers in REMS introduction MIME section, the original message MIME section header, the REMS extensions MIME section header... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2.2 Combinations of fields for the REMS relay metadata MIME Header | The present clause defines different combinations of fields for the REMS relay metadata MIME Header of the REM envelope. The definition of a certain combination is split in two tables, namely Table 10 and Table 11. Table 10 shows combinations of fields that are defined in MIME and SMIME RFCs. Only the fields listed in ... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2.3 Combinations of fields for the signed data MIME header | In all the test cases defined in the present document this header shall be as specified in ETSI EN 319 532-3 [5], clause 6.2.2. The resulting combination of header fields will be identified as SIGDATA_COMB. |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2.4 Combinations of fields for the REMS introduction section | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2.4.1 Introduction | The present clause defines combinations of fields for three different headers in the REMS introduction section, namely: the REMS introduction MIME header, the multipart/alternative free text subsection header, and the multipart/alternative html subsection header. |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2.4.2 Combinations of fields for the REMS introduction MIME header | All the test cases defined in the present shall include the "REM-Section-Type" field in this header. Its value shall be the recommended value in ETSI EN 319 532-3 [5], namely "rem_message/introduction". This combination is identified as REMS_IntrComb. The mandatory field "REM-Content-Type" shall also be present with it... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2.4.4 Combinations of fields for the multipart/alternative html subsection header | All the test cases defined in the present document shall include the two mandatory header fields ("Content-Type" and "Content-Transfer-Encoding") in the multipart/alternative html subsection header, with the values specified in ETSI EN 319 532-3 [5]. This combination is identified as HTMLComb. 6.2.5 Combinations of fie... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2.7 Combinations of fields for one ERDS evidence MIME section header | |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2.7.1 Combinations of fields for one XML ERDS evidence MIME section header | Table 16 shows three combinations of fields for one ERDS evidence MIME section header derived from ETSI EN 319 532-3 [5] specifications when the ERDS evidence is in XML format. Columns in Table 16 are identical to columns in Table 11. Values in "Header field value" have the same semantics as the values in column "Value... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2.7.2 Combinations of fields for one PDF ERDS evidence MIME section header | Table 17 shows three combinations of fields for one ERDS evidence MIME section header derived from ETSI EN 319 532-3 [5] specifications when the ERDS evidence is a PDF document. Columns in Table 17 are identical to columns in Table 11. Values in "Header field value" have the same semantics as the values in column "Valu... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.2.8 Combinations of fields for the REMS signature MIME section header | Table 18 shows combinations of fields for the REMS signature section header derived from ETSI EN 319 532-3 [5] specifications, namely one with the "Content-Description" field present and one without the "Content- Description" field. Columns in Table 18 are identical to columns in Table 11. Values in "Header field value... |
438d2bf0f70eaf9db324bb04b8b1263b | 119 534-2 | 6.3 Instances of REM payload | The present clause defines instances of REM payloads for being used in test cases. Cells in column "Instance" shows the specific instance of REM payload and all its parametrized components. Each instance is the aggregation of one of the instances of the outmost header defined in clause 6.2.2 and a list of MIME sections... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.