hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.1.3.1.2 XML component
|
The container for the optional components shall be an instance of the OptionalInputsVerifyType type specified in clause 5.1.4.1.2. All the requirements of clause 5.1.4.1.2 shall apply in the validation and augmentation request message with the following differences: 1) The ReturnAugmentedSignature element shall be present. 2) The TSTokensQualityLevel element may be present.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.1.3.1.3 JSON component
|
The container for the optional components shall be an instance of the OptionalInputsVerifyType type specified in clause 5.1.4.1.3. All the requirements of clause 5.1.4.1.3 shall apply in the validation and augmentation request message with the following differences: 1) The returnAugmentedSig element shall be present. 2) The tstkQualityLevel element may be present.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2 Response message
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.1 Component for responding to validation and augmentation request
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.1.1 Component semantics
|
The requirements for this component shall be the requirements specified in clause 5.2.1.1, except by the following differences: 1) This component shall have a profile identifier that shall identify the message as compliant with the "validation and augmentation" protocol specified in the present document. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 61
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.1.2 XML component
|
The element that shall be the component for responding to a request of validation and augmentation of AdES signature(s) shall be the root element of the message dss2:VerifyResponse as specified in clause 5.2.1.2 with the following difference: 1) the dss2:VerifyResponse element shall have one or more dsb:Profile children elements. The first one shall have the value http://uri.etsi.org/19442/v1.1.1/validationAndAugmentationprotocol#, identifying the response as a validation and augmentation response compliant with the augmentation and validation protocol specified in the present document.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.1.3 JSON component
|
The element that shall be the component for responding to a request of validation and augmentation of AdES signature(s) shall be an instance of VerifyResp as specified in clause 5.2.1.3 of the present document with the following difference: 1) the profile array shall have one or more items. The first one shall have the value http://uri.etsi.org/19442/v1.1.1/validationAndAugmentationprotocol#, identifying the response as a validation and augmentation response compliant with the validation and augmentation protocol specified in the present document.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.2 Component for the global validation and augmentation result
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.2.1 Component semantics
|
This component shall contain a major result, which shall report whether the server has been able to perform its task, regardless the results obtained. This component may also contain a minor result providing additional information on the task performed by the server. For details of the values of its result major and result minor, see clause 8.4.3.1 of the present document.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.2.2 XML component
|
The element that shall notify the global validation and augmentation result shall be the dsb:Result element specified in clause 4.1.7.2 of DSS-X core v2.0 [1].
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.2.3 JSON component
|
The element that shall notify the global validation and augmentation result shall be result of type dsb-ResultType type specified in clause 4.1.7.1 of DSS-X core v2.0 [1].
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.3 Optional components
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.3.1 Container for optional components
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.3.1.1 Component semantics
|
The requirements in clause 5.2.3.1.1 apply to the component consisting in a sequence of signature results container.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.3.1.2 XML component
|
The element for incorporating the sequence of signature result containers shall be an instance of OptionalOutputsVerifyType type specified in clause 5.2.3.1.2. The requirements specified in clause 5.2.3.1.2 shall apply for this element. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 62
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.3.1.3 JSON component
|
The element for incorporating the sequence of signature result containers shall be the oplOutp property, instance of OptionalOutputsVerifyType type as specified in clause 5.2.3.1.3. The requirements specified in clause 5.2.3.1.3 shall apply for this element.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.3.2 Signature processing results container
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.3.2.1 Component semantics
|
The requirements in clause 5.2.3.2.1 shall apply to this component with the following difference: 1) It shall include the augment signature result container.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.3.2.2 XML component
|
The element for implementing the signature results container shall be the ResultsForOneSignature element as specified in clause 5.2.3.2.1.2. The requirements specified in clause 5.2.3.2.1.2 shall apply for this element with the following differences: 1) This element shall include the AugmentSignatureResult element. 2) The AugmentSignatureResult element shall not include the SignatureRefInRequest element, as the SignatureReference child element of ResultsForOneSignature element already contains the reference to the validated and augmented signature.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.3.2.3 JSON component
|
The element for implementing the signature results container shall be the resForOneSig property as specified in clause 5.2.3.2.1.3. The requirements specified in the aforementioned clause shall apply for this element with the following differences: 1) This element shall include the augmentSigResult child. 2) The augmentSigResult element shall not include the SigRefInReq child, as the SignatureReference child element of resForOneSig element already contains the reference to the validated and augmented signature.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.4 Reporting results
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.4.1 Introduction
|
Being the validation and the attempt to augment one signature two different processes, their results shall be reported in two different result components in the response message, as indicated below.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.4.2 Reporting results in XML protocol
|
The result of the validation of a certain signature shall be reported in the dsb:Result child element of the ResultsForOneSignature element reporting the processing results for that signature. The contents of this element shall be as specified in clause 8.4.3.1 of the present document. The result of the attempt to augment a certain signature shall be reported in the dsb:Result child element of the AugmentSignatureResult element reporting the results of that augmentation attempt. The contents of this element shall be as specified in clause 8.4.3.6 of the present document.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
7.2.4.3 Reporting results in JSON protocol
|
The result of the validation of a certain signature shall be reported in the result child element of the resForOneSig element reporting the processing results for that signature. The contents of this element shall be as specified in clause 8.4.3.1 of the present document. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 63 The result of the attempt to augment a certain signature shall be reported in the result child element of the augmentSigResult element reporting the results of that augmentation attempt. The contents of this element shall be as specified in clause 8.4.3.6 of the present document.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8 Processing models
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.1 Introduction
|
The present clause specifies the processing models for the three protocols defined in the present document. When the server receives a request from the client, it shall conduct the following tasks: 1) Retrieve the signature(s) that the client has requested to process. Clause 8.2 of the present document specifies models for this task. 2) Process all the signatures that the client requested to process. Clause 8.3 of the present document specifies models for this task. 3) Build the response for the client. Clause 8.4 of the present document specifies models for this task. The models for retrieving the signatures to be processed shall depend on the type of signature to be retrieved. Models for retrieving XAdES and CAdES are based on the processing models for XML and CMS signatures specified in clauses 6.1 and 6.2 of DSS-X core v2.0 [1]. The model for retrieving PAdES signatures is fully specified in the present document as DSS-X core v2.0 [1] does not cover their submission and processing. The models for retrieving the signatures to be processed shall be common to the three protocols, as the supporting structures for submitting signatures and signed documents are the same in all of them. The models for processing the signatures shall depend on both, the types of signatures to be processed, and the protocol. In essence, the present document specifies two different types of signature processing, namely: validation and augmentation. For servers implementing the 'validation' protocol the process applied to the signatures shall be their validation. For servers implementing the 'augmentation' protocol the process applied to the signatures shall be their augmentation. For servers implementing the 'validation and augmentation' protocol the process applied to the signatures shall be their validation and augmentation. The model for building the responses shall be shared by all the protocols and all the types of signatures. The processing models for validating XAdES and CAdES signatures are based on the processing models for XML and CMS signatures specified in clauses 6.1 and 6.2 of DSS-X core v2.0 [1]. Clauses below specify the changes in those processing models introduced by the particularities of the validation protocol specified in the present document. The protocol specified in DSS-X core v2.0 [1] does not allow submission of PAdES signatures for their validation.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.2 Retrieving signature(s)
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.2.1 Retrieving XAdES signature(s)
|
The process for retrieving the XAdES signatures in the request messages shall be as follows: • If the request message does not include the optional input (specified in clause 5.1.4.2.1) for identifying the signatures to be processed, the server shall retrieve the XAdES signatures (built on XML signatures) as specified in clause 6.1.1 of DSS-X core v2.0 [1]. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 64 • If the request message includes the optional input for identifying the signatures to be validated, the server shall proceed as follows: - If this optional input contains the component enclosing digest values of the signatures to be processed, the server shall retrieve those signatures enclosed in (or referenced by) the signature object container, and it shall inspect all the input documents enclosed in (or referenced by) the different input documents containers searching for signatures embedded within them matching the aforementioned digest values. - If this optional input contains components enclosing a pointer to one XAdES signature, the server shall retrieve each XAdES signature pointed by each component, as specified in DSS-X core v2.0 [1]. • If the protocol implemented is the 'validation' or the 'validation and augmentation', then the server shall retrieve the documents that match the RefURI and RefType values, as specified in clause 6.1.2 of DSS-X core v2.0 [1].
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.2.2 Retrieving CAdES signature(s)
|
If the request message does not include the optional input (specified in clause 5.1.4.2.1) for identifying the signatures to be processed, the server shall retrieve the CMS structure as specified in step 1 of clause 6.2.1 of DSS-X core v2.0 [1]. The signerInfos set of this CMS structure may contain several items. Each item is considered to be part of one CAdES signature. Consequently, once retrieved the CMS structure, the server shall consider that it has as many CAdES signatures as items within the signerInfos set. If the request message does include the optional input for identifying the signatures to be processed, the server shall retrieve those CAdES signatures enclosed in (or referenced by) the signature object container, that match the digest values present in the aforementioned optional input identifying the signatures to be processed.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.2.3 Retrieving PAdES signature(s)
|
The process for retrieving the PAdES signatures in the request messages shall be as follows. If the request message does not include the optional input (specified in clause 5.1.4.2.1) for identifying the signatures to be processed then: • If the signature object container does enclose a pointer, the server shall retrieve the PDF document present or referenced within the document container referenced by that pointer and it shall then retrieve all the PAdES signatures embedded in that document. • If the signature object container encloses the PAdES signature itself, the server shall retrieve the digest of the signed document from the digest document container. If the request message includes the optional input (specified in clause 5.1.4.2.1) for identifying the signatures to be processed then: 1) The server hall retrieve the PDF document present or referenced within the document container referenced by the pointer within the signature object container and it shall then retrieve all the PAdES signatures embedded in that document. 2) The server shall then retain those PAdES signatures referenced in the optional input (specified in clause 5.1.4.2.1) for identifying the signatures to be processed then the server as follows: - If this optional input contains the component enclosing digest values of the signatures to be processed, the server shall retain those signatures that match the aforementioned digest values. - If this optional input contains the component identifying PDF field names, the server shall retain the signatures placed within the PDF fields whose names match any of the values present in the aforementioned optional input. NOTE: At the end of this task, the server has retrieved either a non empty set of PAdES signatures and one PDF document, or one PAdES signature and one document digest. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 65
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.2.4 Non retrieved signatures
|
In any of the three cases described in preceding clauses, for each signature reference that the server does not match with any signature in the request, the server shall generate one signature results container with only the result component, with its major result set to urn:oasis:names:tc:dss:1.0:resultmajor:RequesterError, and its minor result set to http://uri.etsi.org/19442/v1.1.1#SignatureNotLocated.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.3 Processing signature(s)
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.3.1 Validating signature(s)
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.3.1.1 Validating XAdES signature(s)
|
For each XAdES signature retrieved after conducting the task specified in clause 8.2.1 the server: 1) Shall conduct the sub-process 'recalculate references' as specified in clause 6.1.2 of DSS-X core v2.0 [1]. 2) Shall conduct its validation as specified in ETSI TS 119 102-1 [13].
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.3.1.2 Validating CAdES signature(s)
|
The server shall first retrieve either the signed document as specified in step 2 of clause 6.2.1 of DSS-X core v2.0 [1], or retrieves the document digest from the digest document container. For each CAdES signature retrieved after conducting the task specified in clause 8.2.2, the server shall conduct its validation as specified in ETSI TS 119 102-1 [13].
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.3.1.3 Validating PAdES signature(s)
|
For each PAdES signature retrieved after conducting the task specified in clause 8.2.3, the server shall conduct its validation as specified in ETSI TS 119 102-1 [13].
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.3.2 Augmenting signature(s)
|
For each AdES signature retrieved after conducting the task specified in the sub-clause of clause 8.2 corresponding to the AdES signature type, the server shall proceed to augment it to the level indicated in the component (specified in clause 6.1.2.2 of the present document) identifying the level that the signatures have to be augmented to. For XAdES signatures the augmentation shall be conducted incorporating unsigned attributes/properties as specified in ETSI EN 319 132 [3], ETSI TS 101 903 [7] or ETSI TS 103 171 [8]. For CAdES signatures the augmentation shall be conducted incorporating unsigned attributes/properties as specified in ETSI EN 319 122 [2], ETSI TS 101 733 [5] or ETSI TS 103 173 [6]. For PAdES signatures the augmentation shall be conducted incorporating unsigned attributes/properties as specified in ETSI EN 319 142 [4], ETSI TS 102 778 [9] or ETSI TS 103 172 [10].
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.4 Building response message
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.4.1 Introduction
|
This task shall be affected by the optional inputs present in the request message. Clause 8.4.3 specifies how to build the new optional outputs originated by the new optional inputs specified in clauses 5.1.4.2 and 6.1.2 of the present document. Clause 8.4.5 specifies where the server shall place the different optional outputs, and what values shall the server assign to the different result components present within the response message. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 66
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.4.2 Building the global result component
|
For the responses of any of the three protocols specified in the present document, if the server has not been able to process the request, it shall generate a result component with its result major set to a value indicating the cause of the failure, as specified in clause 4.1.7 of DSS-X core v2.0 [1]. Under these circumstances this component shall not have a result minor component. NOTE 1: According to DSS-X core v2.0 [1], when the server is able to complete the processing of the signatures requested, i.e., when it has been able to retrieve and validate all of them, and regardless whether all of them are valid or not, the result major of the result component is urn:oasis:names:tc:dss:1.0:resultmajor:Success, and whose minor result may have different values depending on the results of the processing. Otherwise, the server does not process any signature and returns a result major different than the former one indicating the reasons preventing the processing, without any result minor. If the server has been able to successfully process the request the following requirements apply. NOTE 2: In the former sentence "the server has been able to successfully process the request" means that the request was fully correct, that the server correctly understood it, and that the server tried to process (validate, augment, or validate-and-augment depending on the protocol) all the signatures identified in the request. See the rest of this clause (for cases where the response does not contain any signature processing results container), and clauses 8.4.2 and 8.4.3.6 (for cases where the response contains one or more signature processing results containers) for more details on how to report on each process applied to each signature. For the responses of the "validation" protocol that do not include any signature results container, the server shall generate the following contents: NOTE 3: This only happens under certain circumstances, see clause 8.4.3.1 for details. • If the server has been able to successfully process the request, then: - the result major shall have the value urn:oasis:names:tc:dss:1.0:resultmajor:Success AND - The result minor shall indicate the result of validating the signature, as follows: If the validation has succeeded (total-passed as specified in ETSI TS 119 102-1 [13]), it shall have the following value: http://uri.etsi.org/19442/validation/signature/totalpassed. If the validation returns the value indeterminate as specified in ETSI TS 119 102-1 [13], it shall have the following value: http://uri.etsi.org/19442/validation/signature/indeterminated. If the validation returns the value total-failed as specified in ETSI TS 119 102-1 [13], it shall have the following value: http://uri.etsi.org/19442/validation/signature/totalfailed. - The result component may also provide textual information on the causes for this result. For the responses of the "validation" protocol that include one or more signature results container, and for all the responses the "augmentation" and the "validation and augmentation" protocols the server shall generate a global result component as follows: • It shall set its major result value to urn:oasis:names:tc:dss:1.0:resultmajor:Success indicating that it was able to complete the requested. • It shall set the value of the result minor to http://uri.etsi.org/19442/v1.1.1/result/CheckIndividualResults. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 67
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.4.3 Building new optional outputs
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.4.3.1 Building the signature processing results container
|
The server shall include one or more processing signature containers within the response message: • if the message is the response for a request of the 'augmentation' OR 'validation and augmentation' protocols; OR • if the messages is the response for a request of the 'validation protocol' AND: - The request message included the signatures-to-process-refs container (specified in clause 5.1.4.2.1 of the present document) identifying the signatures that the client requested to process; OR - The request message did NOT include signatures-to-process-refs container AND the request message: contained several signatures; OR contained one signature AND included the optional input (specified in clause 5.1.4.2.3 of the present document) requesting the generation of a (signed or unsigned) validation report. Otherwise the server does not need to generate and include this component within the response message (although it still may do it). NOTE: This allows that when operating in the validation protocol, if the request contains one signature and it does not contain any of the new optional inputs specified in the present document, the response may actually be the response message specified in DSS-X core v2.0 [1] with the only difference of the result minor value indicating the result of the validation. The server shall generate one component of this type for each processed signature. The server shall place all the components of this type as children of the optional outputs container (specified in clause 5.1.4.1 of the present document). Each component shall have one child summarizing the result of the validation of one signature. The contents of its result major and result minor shall be as specified in DSS-X core v2.0 [1], with the following difference: 1) If the validation of the reported signature in this component has succeeded (total-passed as specified in ETSI TS 119 102-1 [13]), the result major shall have the following value: http://uri.etsi.org/19442/validation/signature/totalpassed and there shall not be any result minor. 2) If the validation of the reported signature in this component returns the value indeterminate as specified in ETSI TS 119 102-1 [13], the result major shall have the following value: http://uri.etsi.org/19442/validation/signature/indeterminated and there shall be a result minor component identifying one cause for this result. The result component may also provide textual information on the causes for this result. 3) If the validation of the reported signature in this component returns the value total-failed as specified in ETSI TS 119 102-1 [13], the result major shall have the following value: http://uri.etsi.org/19442/validation/signature/totalfailed and there shall be a result minor component indicating identifying the reason for this failure. The result component may also provide textual information on the causes for this result. In a response message for the "validation and augmentation" protocol, this component may also have a augment results container child, whose building is specified in clause 8.4.3.6 of the present document.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.4.3.2 Building component for referencing the processed signature
|
The server shall generate this component (specified in clause 5.2.3.2.2 of the present document) if it also generates one or more instances of the component for including details corresponding to the processing of one signature. The server shall generate one component of this type for each processed signature, and shall place it as child component of the component that encloses the processing details for the referenced signature. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 68
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.4.3.3 Building component for returning the (signed or unsigned) validation report
|
The server shall generate this component (specified in clause 5.2.3.2.5 of the present document) if the request included the optional input (specified in clause 5.1.4.2.3 of the present document) requesting the generation of a (signed or unsigned) validation report. If the server has been requested to validate a set of N signatures, it may choose either: 1) generating one unique validation report reporting on the validation of the N validated signatures; in this case it shall incorporate this validation report component into the validation response message as a child of the optional outputs component; OR 2) generating as many validation reports (N) as validated signatures, each one reporting on the validation of one signature; in this case it shall incorporate each validation report as a child of the signature processing results container with the details of the validated signature; OR 3) implementing a mixed solution: - generating one validation report with details of the validation of a subset of M (being M<N) validated signatures; as in bullet 1) it shall incorporate it into the response message as child of the optional outputs component; AND - generating N-M validation reports each one reporting on the validation of one of the N-M signatures not present in the aforementioned subset; as in bullet 2), it shall incorporate each one of these N-M validation reports as child of the signature processing results container with the details of the validated signature. 8.4.3.4 Building component for notifying the signature validation policy applied during the validation The server shall include this component (specified in clause 5.2.3.2.3 of the present document) if the request included the optional input (specified in clause 5.1.4.2.2 of the present document) requesting that the server uses a certain signature validation policy for validating any signature. The server shall place this component as direct child of the optional outputs container component. NOTE: Because the server uses the same signature validation policy for validating all the signatures, there is no need to repeat this information within each component notifying the validation details of one signature: instead, the component notifying the applied signature validation policy is placed as a sibling component.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.4.3.5 Building component for returning the signature policies available
|
The server may include this component (specified in clause 5.2.3.2.4 of the present document) if the request included the optional input (specified in clause 5.1.4.2.2 of the present document) requesting that the server uses a certain signature validation policy for validating any signature AND the server could not validate signatures applying the requested signature validation policy. The server shall place this component as direct child of the optional outputs container component. NOTE: This component is placed there for the same reasons as the component for notifying the applied signature validation policy.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.4.3.6 Building the augment signature result container
|
The server shall build this component (specified in clause 6.2.3 of the present document) only for the response messages of the 'augmentation' and the 'validation and augmentation' protocols. The server shall build one component of this type for each signature whose augmentation has been requested by the client. The server shall place this component as a child of the signature processing results container (specified in clause 5.2.3.2.1) in response messages of "validation and augmentation" protocol. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 69 The server shall place this component as a child of the root element in response messages of "augmentation" protocol. For each augmented signature the server shall generate this component as follows: • If the signature was not embedded within any document then the server shall place the augmented signature within this component. • If the signature was embedded within an embedding document, then the server: - Shall place the augmented signature within the embedding document, shall create a new document-with- signature container, and shall place the embedding document there. - Shall generate a pointer to the aforementioned document-with-signature container and shall put it within this component. If the server has succeeded in the augmentation of the signature referenced in this component, this component: 1) Shall have the three elements enumerated in clause 6.2.3.1. 2) Shall have a result component with its major result child set to a value indicating that the process has succeeded and with its minor result child set to http://uri.etsi.org/19442/v1.1.1/augmentation/Success. If the server has not succeeded in the augmentation of the signature this component: 1) Shall have a reference to the signature that the client requested to validate and augment in the augmentation request. 2) Shall not contain the element allowing to return the augmented signature. 3) Shall have a result component with its major result child set to http://uri.etsi.org/19442/v1.1.1/augmentation/Failure. The result component may have a minor result child. Below follows a list of possible causes for augmentation failure: - If the client requested augmenting the signature to a level that the signature cannot be augmented to, then the minor result child shall be set to http://uri.etsi.org/19442/v1.1.1/augmentation/Forbidden. EXAMPLE: Requesting augmentation to AdES-B-B level is never possible. Also, if a signature is a XAdES-B- L-T, a client can only request augmentation to AdES-L-TA level. Any other augmentation request will fail with the result minor set to http://uri.etsi.org/19442/v1.1.1/augmentation/Forbidden. - If the server does not know the signature level indicated in the request then the minor result shall be set to http://uri.etsi.org/19442/v1.1.1/augmentation/unknownLevel. - If the server is not prepared for augmenting the signature to the level indicated in the request then the minor result shall be set to http://uri.etsi.org/19442/v1.1.1/augmentation/notPreparedForThisLevel. - If the server could not get all the material required for augmenting the signature then the minor result child shall be set to http://uri.etsi.org/19442/v1.1.1/augmentation/validationMaterialNotAvailable. - Any other cause shall be reported setting the minor result child to http://uri.etsi.org/19442/v1.1.1/augmentation/otherCause.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.4.4 Building DSS-X re-used optional outputs
|
The building of the DSSX re-used optional outputs present in the response message shall be performed as specified in clause 6.3.3 of DSS-X core v2.0 [1]. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 70
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
8.4.5 Building the response message
|
If the server has found itself in the situation of not being able to complete the request, it shall generate a response message with only one global result component. Its result major shall identify the reason that prevented the server to successfully process the request, as specified in clause 4.1.7 of DSS-X core v2.0 [1]. This result component shall not contain any result minor. NOTE 1: According to DSS-X core v2.0 [1], when the server is able to complete the processing of the signatures requested, i.e., when it has been able to retrieve and validate all of them, and regardless whether all of them are valid or not, the result major of the result component is urn:oasis:names:tc:dss:1.0:resultmajor:Success, and whose minor result may have different values depending on the results of the processing. Otherwise, the server does not process any signature and returns a result major different than the former one indicating the reasons preventing the processing, without any result minor. If the server has been able to process all the signatures whose processing the client requested: 1) The server shall generate a global result component as follows: a) It shall set its major result value to urn:oasis:names:tc:dss:1.0:resultmajor:Success indicating that it was able to complete the requested. b) It shall set the value of the result minor as follows: If the response does not include any signature processing results container (specified in clause 5.2.3.2.1 of the present document), meaning that only one signature has been validated, then value for the result minor shall be one of the three values specified in clause 8.4.3.1 of the present document, depending on the result obtained by the validation process. NOTE 2: This can only happen in the response of the 'validation' protocol. If the response does include one or more signature processing results containers, then the value for the result minor shall be http://uri.etsi.org/19442/v1.1.1/result/CheckIndividualResults. 2) If the response does NOT include any signature processing results container, then the server proceeds to generate the optional outputs as per the optional inputs present in the request, following the specifications in clause 6.3.3 of DSS-X core v2.0 [1], and clauses 8.4.3.4, and 8.4.3.5 of the present document. After that, it places the generated optional outputs as children of the optional outputs container component. NOTE 3: This can only happen in the response of the 'validation' protocol. 3) For responses of the 'validation' and 'validation and augmentation' protocols, if the response does include one or more signature processing results containers, the server: - Shall build all the optional outputs common to all the processed signatures as per the optional inputs present in the request, namely the components containing: the applied service policy, the schemas used, the documents embedding signatures, the verification time information, and the notification of the applied signature validation policy (or the available signature validation policies). The server shall place all these components as children of the optional outputs container. The server shall build all these components as specified in DSS-X core v2.0 [1] and the present document. - Shall build one signature processing results container per each processed signature. For each processed signature, the server proceeds to generate the components reporting one aspect of its processing as per the optional inputs in the request, and places them as children of the signature processing results container. These children components are: a signature reference component, a result component reporting the result of processing that signature, the (signed or unsigned) validation report, the augment signature result container (which shall be built as indicated in the next bullet), transformed documents, results of verifying manifests, the signing time information, and the signer identity. 4) For responses of the 'augmentation' and the 'validation and augmentation' protocols: - The server shall build one augment signature result container specified in clause 7.2.3.2 of the present document for each processed signature. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 71 - The server shall set the value of the result component in each augment signature result container as specified in clause 6.2.3.1 of the present document. 5) For the 'augmentation' protocol the server shall place the augment signature results containers as children of the root element of the response. 6) For the 'augmentation' protocol, the server shall place the document-with-signature containers generated during the processing of the signatures as children of the root element of the response. For the 'augmentation and validation' protocol, the server shall place the document-with-signature containers generated during the processing of the signatures as children of the optional outputs component. 7) Shall set the values of the profiles used. The server shall set the value of the first one as specified in the present document, depending on the protocol. 8) May set values for the components containing the request identifier, and the response identifier.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9 Asynchronous processing
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.1 Asynchronous operation for the three protocols
|
For all the protocols specified in the present document, the server shall not send back to the client a response message that contains the results of processing only a subset of the set of signatures that the client requested to process. The asynchronous processing allows to the server sending back to the client "not yet finished" messages, which do not contain any result of processing any signature, but serve to notify the client that it has to wait for getting the results it asked for. In asynchronous processing one client usually sends an initial request to the server. The initial request shall contain a component with the request identifier generated by the client. As a response to that initial request, if after a certain time the server has not been able to finalize the processing of all the signatures (either their validation, their augmentation, or their validation-and-augmentation) that the client requested to process, it shall return a protocol response with a component set to a value that indicates that it has not been able to finalize the processing of all the signatures ("not yet finished"). This response-pending message shall contain an identifier. This response-pending message shall not contain any result of processing any signature. Under this processing mode the client, after a certain time, can send a pending-request to the server. This pending- request shall include the response identifier of the response-pending message returned by the server. This response identifier allows the server to correlate this pending-request to the initial request. If the server has finalized the processing of all the signatures that the client requested to process, it shall return the response message with the corresponding results; otherwise, it shall return a new response-pending. The client can send subsequent requests until the server returns a response with the result of processing all the signatures that the client requested to process. Each subsequent request shall include the response identifier returned by the server in the response to the initial request. For managing asynchronous processing, the following components are required in the three protocols: a) An identifier for the initial request. b) An identifier for the first response-pending message, which shall be used in subsequent pending-request messages. c) A pending-request message that includes the identifier for the first response-pending message. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 72
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.2 Components for sending a pending-request
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.2.1 Components semantics
|
This component shall request to the server to return the response corresponding to an initial request previously sent. Requests of this type are named pending-request hereinafter. This component shall include an identifier, generated by the server and returned by the server in the response to the initial request (the first response-pending message), which allows correlating the subsequent pending requests to the initial request and to the subsequent responses.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.2.2 XML component
|
The element that shall indicate to the server that the client is requesting the response corresponding to a previously sent initial request (as part of an asynchronous protocol) shall be the dss2:PendingRequest element specified in clause 4.2.12.2 of DSS-X core v2.0 [1].
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.2.3 JSON component
|
The element that shall indicate to the server that the client is requesting the response corresponding to a previously sent initial request (as part of an asynchronous protocol) shall be the pendingReq element. It shall be an instance of the dss2-PendingRequestType type specified in clause 4.2.12.1 of DSS-X core v2.0 [1].
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.3 Component for identifying the initial request
| |
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.3.1 Component semantics
|
This component shall contain a unique identifier for the initial request submitted by the client to the server.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.3.2 XML component
|
The component implementing the identifier of the initial request shall be the RequestID attribute specified in clause 4.1.10.2 of DSS-X core v2.0 [1] for the "validation" protocol and the "validation and augmentation" protocol. The component implementing the identifier of the initial request shall be the RequestID attribute specified in clause 6.1.1.2 of the present document for the "augmentation" protocol.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.3.3 JSON component
|
The component implementing the identifier of the initial request shall be the reqID component specified in clause 4.1.10.1 of DSS-X core v2.0 [1] for the "validation" protocol and the "validation and augmentation" protocol. The component implementing the identifier of the initial request shall be the reqID component specified in clause 6.1.1.3 of the present document for the "augmentation" protocol. 9.4 Component for identifying the initial response-pending message
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.4.1 Component semantics
|
This component shall contain a unique identifier for the initial response-pending message sent by the sender to the client. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 73
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.4.2 XML components
|
The component implementing the identifier of the initial request shall be the ResponseID attribute specified in clause 4.1.11.2 of DSS-X core v2.0 [1] for the "validation" protocol and the "validation and augmentation" protocol. The component implementing the identifier of the initial request shall be the ResponseID attribute specified in clause 6.2.3.2 of the present document for the "augmentation" protocol.
|
01baa530c4a62e404e91e3569227c3a1
|
119 442
|
9.4.3 JSON component
|
The component implementing the identifier of the initial request shall be the respID component specified in clause 4.1.11.2 of DSS-X core v2.0 [1] for the "validation" protocol and the "validation and augmentation" protocol. The component implementing the identifier of the initial request shall be the respID component specified in clause 6.2.3.3 of the present document for the "augmentation" protocol. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 74 Annex A (normative): XML and JSON Schema files A.1 XML Schema file location for namespace http://uri.etsi.org/19442/v1.1.1# The file at https://forge.etsi.org/rep/esi/x19_442_sign_validation_protocol/raw/v1.1.1/19442xmlSchema.xsd ("19442xmlSchema.xsd") contains the definitions of elements and types defined within the namespace whose URI value is http://uri.etsi.org/19442/v1.1.1#. A.2 JSON Schema file location for "$schema" "http://etsi.org/19442/v1.1.1/json#" The file at https://forge.etsi.org/rep/esi/x19_442_sign_validation_protocol/raw/v1.1.1/19442jsonSchema.json ("19442jsonSchema.json") contains the definitions of elements and types defined within the JSON schema associated to the present document. ETSI ETSI TS 119 442 V1.1.1 (2019-02) 75 Annex B (informative): Bibliography • IETF RFC 7515: "JSON Web Signature (JWS)". • IETF RFC 5652 (September 2009): "Cryptographic Message Syntax (CMS)". • ETSI TS 119 172-4: "Electronic Signatures and Infrastructures (ESI); Signature policies; Part 4: Signature validation policy for European qualified electronic signatures/seals using trusted lists". ETSI ETSI TS 119 442 V1.1.1 (2019-02) 76 History Document history V1.1.1 February 2019 Publication
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
1 Scope
|
The present document specifies procedures for using and interpreting EUMS national trusted lists when validating EU qualified trust service outputs against them (e.g. validating EU qualified certificates, EU qualified time stamps, evidences created by qualified electronic registered delivery services, EU electronic signatures or seals on EU qualified validation reports on EU qualified electronic signatures or seals).
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
2 References
| |
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 119 612 (V2.1.1): "Electronic Signatures and Infrastructures (ESI); Trusted Lists". [2] ISO 3166-1:2013: "Codes for the representation of names of countries and their subdivisions - Part 1: Country codes". [3] ETSI EN 319 412-5: "Electronic Signatures and Infrastructures (ESI); Certificate Profiles; Part 5: QCStatements". [4] IETF RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile". [5] T7 & Teletrust: "Common PKI Specifications for Interoperable Applications", Specification Part 5: Certificate Path Validation, Version 2.0, 20 January 2009.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] Regulation (EU) No 910/2014 of the European Parliament and of the Council on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC. [i.2] Commission Implementing Decision (EU) 2015/1505 of 8 September 2015 laying down technical specifications and formats relating to trusted lists pursuant to Article 22(5) of Regulation (EU) No 910/2014 of the European Parliament and of the Council on electronic identification and trust services for electronic transactions in the internal market. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 8 [i.3] Official Journal of the European Union OJ C 276, 16.08.2019, p. 1-7. Information related to data on Member States' trusted lists as notified under Commission Implementing Decision (EU) 2015/1505. [i.4] ETSI TR 119 001: "Electronic Signatures and Infrastructures (ESI); The framework for standardization of signatures; Definitions and abbreviations". [i.5] Void. [i.6] IETF RFC 3161: "Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)". [i.7] Directive 1999/93/EC of the European Parliament and of the Council of 13 December 1999 on a Community framework for electronic signatures. [i.8] ETSI EN 319 102-1: "Electronic Signatures and Infrastructures (ESI); Procedures for Creation and Validation of AdES Digital Signatures; Part 1: Creation and Validation". 3 Definition of terms, symbols, abbreviations and notations
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI TR 119 001 [i.4] and the following apply: pivot LOTL: specific instance of a LOTL that announces changes in the LOTL signing certificates and/or LOTL location NOTE: For further explanations on the concept of pivot LOTL refer to annex A. tuple: group of multiple elements or groups of multiple elements
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
3.2 Symbols
|
Void.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.4] and the following apply: EUMS European Union Member State LOTL List Of Trusted Lists LOTLSO LOTL Scheme Operator OJEU Official Journal of the European Union QTS Qualified Trust Service TL Trusted List
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
3.4 Notations
|
The requirements in the present document are identified as follows: <3 letters identifying the section title or type of requirement>-<the clause number>-<2-digit number (incremental)> The management of the requirement identifiers for subsequent editions of the present document is as follows: • When a requirement is inserted at the end of a clause, the 2-digits number above is incremented to the next available digit. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 9 • When a requirement is inserted between two existing requirements, capital letters appended to the previous requirement identifier are used to distinguish new requirements. • The requirement identifier for deleted requirements is kept and completed with "Void". • The requirement identifier for modified requirement is kept void and the modified requirement is identified by capital letter(s) appended to the initial requirement number. 4 Procedures for using and interpreting European Union Member States national trusted lists
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.0 General provisions
|
The present document presents procedures for using and interpreting European Union Member States national trusted lists in the form of algorithms, which provide a conformant behaviour when implemented by a conformant application. GPR-4.0-01: Alternative implementations may be used provided that they shall produce the same output and main status indication when given the same set of input information. GPR-4.0-02: The following parameters shall be preconfigured as follows for use in all the procedures specified in the remaining clauses of the present document: Name Description - Value OJEU-Loc URI value referencing the latest publication of the Official Journal of the European Union (OJEU) related to data on EUMS TL as they are notified under Commission Implementing Decision (EU) 2015/1505 [i.2]. OJEU-LOTL-Loc URI value representing the location where the current instance of the XML file of the LOTL is available, as specified in the OJEU publication available from OJEU-Loc. OJEU-LOTL- Certs-Set The full set of certificates used for ensuring authenticity and integrity of the LOTL as provided in the OJEU publication available from OJEU-Loc. NOTE 1: At the time of publication of the present document: • the URI value described in the OJEU-Loc row of the above table was: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.C_.2019.276.01.0001.01.ENG [i.3]. • This URI value is expected to be the first URI value not ending by ".xml" in the sequence of URI values present in the 'Scheme information URI' field of the LOTL (see clause 5.3.7 of ETSI TS 119 612 [1]). • the URI value described in the OJEU-LOTL-Loc row of the above table was: https://ec.europa.eu/tools/lotl/eu-lotl.xml. NOTE 2: Such initial configurations are likely to be performed outside the software application implementing the procedures specified in the present document and come from configuration files or other appropriate source. Once configured, and as per the content of OJ C 233 276 [i.3] and the explanation material available from that publication, those three variables can be updated in a machine processable way as further explained and specified in clause 4.1. GPR-4.0-03: In the procedures specified in the present document, whenever the validation of an https connection fails, implementations should refrain from stopping the processing for that reason but should add an appropriate warning to the corresponding procedure sub-status information. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 10
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.1 Authenticating the EC compiled list of trusted lists
| |
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.1.1 Description
|
EUMS Trusted Lists (TLs) have a legal constitutive value. It is the single formal source to verify that a claimed EU qualified trust service provider and the claimed EU qualified trust service it provides are indeed granted an EU qualified status by the competent EUMS body. Regulation (EU) No 910/2014 [i.1] mandates EUMS to set up their national TL, at least under an XML machine processable format, compliant to the specifications established by CID (EU) 2015/1505 [i.2] building upon ETSI TS 119 612 [1]. EUMS have the obligation to electronically sign or seal the XML version of their national TL by means of a digital signature compliant with the specifications of CID (EU) 2015/1505 [i.2] relying on clause 5.7.1 of ETSI TS 119 612 [1]. To verify such a digital signature, relying parties need to be able to access the applicable public key. In order to allow access to the TLs of all Member States in an easy manner, the European Commission (EC) publishes a central list, called the List Of Trusted Lists (LOTL), with links to the locations where the TLs are published as notified by Member States. The public key certificate(s) corresponding to the private key(s) entitled to be used to sign EUMS TLs and hence to be used by relying parties to validate those TL signatures are notified by the EUMSs to the EC and published in the LOTL as well. The LOTL is available in a format suitable for automated processing (XML). The authenticity and integrity of the machine processable version of the LOTL is ensured through a digital signature supported by a certificate which can be authenticated through a publication in the Official Journal of the European Union. At the time of publication of the present document, pursuant to a publication in the OJEU C276 [i.3], the LOTL can be accessed from the following location: https://ec.europa.eu/tools/lotl/eu-lotl.xml. OJEU C276 [i.3] additionally identifies and authenticates the LOTL Scheme Operator (LOTLSO) public key certificate(s) corresponding to the private key(s) entitled to be used to sign the LOTL and hence the public keys to be used by relying parties to validate the LOTL signature. Both the location of the LOTL and the LOTLSO certificates can be updated through a new publication in the OJEU or through the mechanism of pivot LOTL in accordance with OJEU C276 [i.3]. The LOTLSO certificates and the location of the LOTL XML file are contained in the LOTL itself, as part of the first tuple of the 'Pointers to other TSLs' field of the LOTL as specified in clause 5.3.13 of ETSI TS 119 612 [1] and whose 'Scheme territory' corresponds to the "EU" country code. This enables relying parties to detect in a machine processable way a change in the LOTLSO certificates and/or in its location. Any such future change will be reflected in the publication of a new instance of a pivot LOTL which will include a new location URL and/or a modified set of digital certificates for relying parties to use when authenticating the LOTL. The change of the location of the LOTL will always lead to a new publication of the OJEU to authenticate such a new location. A change of the LOTL location is made effective in a pivot LOTL while the previous location is maintained and the current instance of the LOTL is kept available at that location until the next publication in the OJEU and for a further transition period. Starting at the date of issuance of the pivot LOTL in which new LOTLSO certificates and/or new location is first published, the new URL and/or a modified set of digital certificates can be used by relying parties to locate and authenticate the LOTL in replacement of the formerly issued information. It is however always possible for the European Commission to publish a new publication in the OJEU, for instance as a temporary response to an emergency situation requiring the immediate replacement of all the digital certificates of the LOTL. Each instance of the LOTL will include, as the first part of the information regarding the underlying scheme ('Scheme information URI" element as specified in clause 5.3.7 of ETSI TS 119 612 [1]), in their chronological order showing the most recent element first, the list of: • when applicable, one or more URLs where the last archived previous instance(s) of the pivot LOTL containing a new location and/or a modified set of digital certificates of the LOTL is(are) published, back until and followed by; • the URL of the latest relevant publication in the OJEU resetting the initial location and the initial set of digital certificates for relying parties to use when authenticating the LOTL. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 11 In case of a transition between two publications in the OJEU, the above list can be piled on top of the list of pivot LOTLs, when applicable and the URL of the previous relevant publication in the OJEU resetting the initial location and the initial set of digital certificates for relying parties to use when authenticating the LOTL. Each pivot LOTL is digitally signed by means of a private key for which the corresponding digital certificate is part of the set of LOTLSO certificates included in the previous pivot LOTL or included in the latest OJEU publication when the pivot LOTL is the first from that OJEU publication. The current instance of the LOTL includes the exact same set of LOTLSO certificates included in the previous pivot LOTL and is digitally signed by means of a private key corresponding to one of these LOTLSO certificates. The procedure specified in clause 4.1 allows to obtain the authenticated XML version of the current instance of the LOTL. NOTE: Further information about the concept of pivot LOTL and on the procedure related to the change of location of the LOTL can be found in OJEU C276 [i.3] and in particular in the referenced webpage https://ec.europa.eu/tools/lotl/pivot-lotl-explanation.html.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.1.2 Inputs
|
The parameters OJEU-Loc, OJEU-LOTL-Loc and OJEU-LOTL-Certs-Set shall either initially be configured as specified in GPR-4.0-02 or updated through the regular processing specified in clause 4.1.4.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.1.3 Outputs
|
Name Description Authenticated-LOTL The authenticated XML version of the current instance of the LOTL. LOTL-Status The status indication of the process of authenticating the current instance of the LOTL. LOTL-Sub-Status A list of indications supplementing LOTL-Status indication of the process of authenticating the current instance of the LOTL. OUT-4.1.3-01: All above listed output variables shall be initialized to void.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.1.4 Processing
|
NOTE 1: The processing basically checks the chain of trust between the LOTL XML file obtained from OJEU-LOTL-Loc input and the OJEU-LOTL- Certs-Set input. It checks in particular that: - the public key certificate corresponding to the private key having signed the LOTL XML file is part of the set of certificates included in the LOTL itself as part of the pointer to itself; - when no pivot LOTL is present, the public key certificate corresponding to the private key having signed the LOTL XML file is part of the set of certificates included in the OJEU-LOTL- Certs- Set. - when pivot LOTL is/are present: each pivot LOTL is signed by means of a private key for which the corresponding digital certificate: - is part of the set of certificates included in the previous pivot LOTL or included in the latest OJEU publication when the pivot LOTL is the first from that OJEU publication; and - is part of the set of certificates included in the pivot LOTL itself as part of the pointer to itself; - the current instance of the LOTL includes the exact same set of LOTLSO certificates included in he previous pivot LOTL and is signed by means of a private key corresponding to one of these LOTLSO certificates. The signatures of the LOTL and of each pivot LOTL are valid. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 12 Additional consistency checks are performed: NOTE 2: As per OJEU C276 [i.3] and in particular the referenced webpage https://ec.europa.eu/tools/lotl/pivot-lotl- explanation.html, in case of changing the LOTL location. a) The first element value that will change is the 'TSLLocation' value string containing the URI of the machine processable format of the LOTL in the pointer to the LOTL in the LOTL itself. When this is the case, the OJEU-LOTL-Loc parameter (see clause 4.0) can be updated with that new location. b) Subsequently, when the first encountered element of the LOTL 'Scheme information URI' whose value is not ending by ".xml" is not the value of the configured OJEU-Loc parameter (see clause 4.0), then this parameter can be updated with that new value. This reflects the latest publication of the OJEU related to data on EUMS TL as they are notified under Commission Implementing Decision (EU) 2015/1505 [i.2]. c) The parameter OJEU-LOTL-Certs-Set (see clause 4.0) can be updated either in an automated way from the set of certificates available in the pointer to the LOTL from the LOTL instance that first includes the new value of the latest publication of the OJEU referred in point b) above, or "manually" directly from that publication. PRO-4.1.4-01: The processing shall set LOTL to the current instance of the LOTL XML file obtained from OJEU-LOTL-Loc. PRO-4.1.4-02: The processing shall set LOTL-Signer-Cert to the ds:X509Certificate value of the ds:KeyInfo of the ds:Signature of LOTL. PRO-4.1.4-03: If the processing parses the 'Scheme information URI' element of LOTL as specified in clause 5.3.7 of ETSI TS 119 612 [1] without finding a URI value matching the OJEU-Loc value, then: a) the processing shall set Authenticated-LOTL to void; b) the processing shall set LOTL-Status to the value "LOTL_VERIFICATION_FAILED"; c) the processing shall set LOTL-Sub-Status to the value "OJEU_LOCATION_INPUT_NOT_MATCHING_OJEU_LOCATION_IN_LOTL"; and d) the processing shall stop the process. NOTE 3: It is likely that the configuration specified in GPR-4.0-02 is not taking into consideration the latest publication of the OJEU related to data on EUMS TL as they are notified under Commission Implementing Decision (EU) 2015/1505 [i.2]. PRO-4.1.4-04: The processing shall set 'n' to the number of successive URIs having an https scheme, an authority, and a non-empty path ending with the character string ".xml" until the URI value matching the OJEU-Loc value, as those URIs are listed in the 'Scheme information URI' element of LOTL as specified in clause 5.3.7 of ETSI TS 119 612 [1]. PRO-4.1.4-05: If OJEU-LOTL-Loc is not matching the TSLLocation string available in the tuple from the 'Pointers to other TSLs' field of LOTL (see clause 5.3.13 of ETSI TS 119 612 [1]) whose 'Scheme territory' qualifier has the value "EU" and if LOTL does not match the XML file obtained from that TSLLocation string, then: a) the processing shall set Authenticated-LOTL to void; b) the processing shall set LOTL-Status to the value "LOTL_VERIFICATION_FAILED"; c) the processing shall set LOTL-Sub-Status to the value "LOTL_FILE_CONFLICT"; and d) the processing shall stop the process. PRO-4.1.4-06: If OJEU-LOTL-Loc is matching the TSLLocation string available in the tuple from the 'Pointers to other TSLs' field of LOTL (see clause 5.3.13 of ETSI TS 119 612 [1]) whose 'Scheme territory' qualifier has the value "EU" and if LOTL does not match the XML file obtained from that TSLLocation string, then: a) the processing shall set LOTL to the XML file obtained from that TSLLocation string; and b) the processing shall go to PRO-4.1.4-02. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 13 NOTE 4: This case corresponds to the publication of a new LOTL instance from the time of the initialization of LOTL. PRO-4.1.4-07: The processing shall validate ds:Signature of LOTL considering LOTL-Signer-Cert as a directly trusted certificate, i.e. as a trust anchor. NOTE 5: This corresponds to the basic signature validation process of ETSI EN 319 102-1 [i.8]. PRO-4.1.4-08: If the signature validation performed in PRO-4.1.4-07 failed or was indeterminate, then: a) the processing shall set Authenticated-LOTL to void; b) the processing shall set LOTL-Status to the value "LOTL_VERIFICATION_FAILED"; c) the processing shall set LOTL-Sub-Status to the values provided by the validation procedure together with the additional value "LOTL_SIGNATURE_VERIFICATION_FAILED"; and d) the processing shall stop the process. PRO-4.1.4-09: The processing shall set the following variables to the following values: a) LOTLSO-Cert to LOTL-Signer-Cert; and b) LOTLSO-Certs-Set to the full set of certificates available in the tuple from the 'Pointers to other TSLs' field (see clause 5.3.13 of ETSI TS 119 612 [1]) of LOTL, whose 'Scheme territory' qualifier has the value "EU". PRO-4.1.4-10: If n is equal to 0, then: a) If LOTLSO-Cert is not part of LOTLSO-Certs-Set then: 1) the processing shall set Authenticated-LOTL to void; 2) the processing shall set LOTL-Status to the value "LOTL_VERIFICATION_FAILED"; 3) the processing shall set LOTL-Sub-Status to the value "LOTL_SIGNER_CERT_NOT_AUTHENTICATED_BY_LOTL"; and 4) the processing shall stop the process. b) The processing shall go to PRO-4.1.4-12. PRO-4.1.4-11: For all i in [1..n] a) The processing shall set Pivot to the instance of the XML file obtained from the ith successive URI having an https scheme, an authority, and a non-empty path ending with the character string ".xml" until the URI value matching the OJEU-Loc value in the 'Scheme information URI" (see clause 5.3.7 of ETSI TS 119 612 [1]) field of LOTL, considering the first such URI as number 1. b) The processing shall set LOTLSO-Certs-Set to the full set of certificates as they are available in the tuple from the 'Pointers to other TSLs' field (see clause 5.3.13 of ETSI TS 119 612 [1]) of Pivot, whose 'Scheme territory' qualifier has the value "EU". c) If LOTLSO-Cert is not part of LOTLSO-Certs-Set then: 1) the processing shall set Authenticated-LOTL to void; 2) the processing shall set LOTL-Status to the value "LOTL_VERIFICATION_FAILED"; 3) the processing shall set LOTL-Sub-Status to the value "PIVOT_i- 1_SIGNER_CERT_NOT_AUTHENTICATED_BY_PIVOT_i"; and 4) the processing shall stop the process. d) The processing shall set LOTLSO-Cert to the ds:X509Certificate value of the ds:KeyInfo of the ds:Signature of Pivot. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 14 e) The processing shall validate ds:Signature of Pivot considering LOTLSO-Cert as a directly trusted certificate, i.e. as a trust anchor. NOTE 6: This corresponds to the basic signature validation process of ETSI EN 319 102-1 [i.8]. f) If the signature validation performed in the previous point failed or was indeterminate then: 1) the processing shall set Authenticated-LOTL to void; 2) the processing shall set LOTL-Status to the value "LOTL_VERIFICATION_FAILED"; 3) the processing shall set LOTL-Sub-Status to the values provided by the validation procedure together with the additional value "PIVOT_i_SIGNATURE_VERIFICATION_FAILED"; and 4) the processing shall stop the process. g) If LOTLSO-Cert is not part of LOTLSO-Certs-Set then: 1) the processing shall set Authenticated-LOTL to void; 2) the processing shall set LOTL-Status to the value "LOTL_VERIFICATION_FAILED"; 3) the processing shall set LOTL-Sub-Status to the value "PIVOT_i_SIGNER_CERT_NOT_AUTHENTICATED_BY_PIVOT_i"; and 4) the processing shall stop the process. PRO-4.1.4-12: If LOTLSO-Cert is not part of LOTL-OJEU-Certs-Set then: a) the processing shall set Authenticated-LOTL to void; b) the processing shall set LOTL-Status to the value "LOTL_VERIFICATION_FAILED"; c) the processing shall set LOTL-Sub-Status to the value "PIVOT_n_LOTLSO_SIGNER_CERT_NOT_AUTHENTICATED_BY_OJEU"; and d) the processing shall stop the process. PRO-4.1.4-13: If the 'Next update' date of LOTL (see clause 5.3.15 of ETSI TS 119 612 [1]) has passed then: a) the processing shall set Authenticated-LOTL to void; b) the processing shall set LOTL-Status to the value "LOTL_VERIFICATION_FAILED"; c) the processing shall set LOTL-Sub-Status the value "LOTL_NEXTUPDATE_PASSED"; and d) the processing shall stop the process. PRO-4.1.4-14: The processing shall set Authenticated-LOTL to LOTL. PRO-4.1.4-15: The processing shall set LOTL-Status to the value "LOTL_VERIFICATION_PASSED". PRO-4.1.4-16: If OJEU-LOTL-Loc is not matching the TSLLocation string available in the tuple from the 'Pointers to other TSLs' field of Authenticated-LOTL (see clause 5.3.13 of ETSI TS 119 612 [1]) whose 'Scheme territory' qualifier has the value "EU", then the processing shall set OJEU-LOTL-Loc to the TSLLocation string available in the tuple from the 'Pointers to other TSLs' field of LOTL (see clause 5.3.13 of ETSI TS 119 612 [1]) whose 'Scheme territory' qualifier has the value "EU". PRO-4.1.4-17: If OJEU-Loc value is not matching the first URI value having an https scheme, an authority, and a non-empty path not ending with the character string ".xml" in the 'Scheme information URI" (see clause 5.3.7 of ETSI TS 119 612 [1]) field of Authenticated-LOTL, then: a) the processing shall set OJEU-Loc to that first URI value; and ETSI ETSI TS 119 615 V1.2.1 (2023-06) 15 b) the processing shall set OJEU-LOTL-Certs-Set: 1) either to the full set of certificates available in the tuple, whose 'Scheme territory' qualifier has the value "EU", from the 'Pointers to other TSLs' field (see clause 5.3.13 of ETSI TS 119 612 [1]) of the pivot LOTL whose location URI is immediately following that first URI value when having an https scheme, an authority, and a non-empty path not ending with the character string ".xml"; or 2) to the full set of certificates used for ensuring authenticity and integrity of the LOTL as provided in the OJEU publication available from that first URI value.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.2 Authenticating an EUMS trusted list
| |
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.2.1 Description
|
The procedure specified in clause 4.2 allows to obtain the authenticated XML version of the national TL of a given EUMS.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.2.2 Inputs
|
Name Description CC Country code of the EUMS for which the trusted list is to be authenticated and whose value is in accordance with the ISO 3166-1 [2] Alpha 2 country code, set in capital letters.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.2.3 Outputs
|
Name Description Authenticated-EUTL The authenticated XML version of the requested TL of EUMS CC. EUTL-Status The status indication of the process of authenticating the requested TL of EUMS CC. EUTL-Sub-Status A list of indications supplementing EUTL-Status indication of the process of authenticating the requested TL of EUMS CC. OUT-4.2.3-01: All above listed output variables shall be initialized to void.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.2.4 Processing
|
PRO-4.2.4-01: The processing shall run the process for authenticating the LOTL as described in clause 4.1 of the present document. PRO-4.2.4-02: If the output Authenticated-LOTL is void as a result of the execution of the process referred in PRO-4.2.4-01, then: a) the processing shall set EUTL-Status to the value "TL_VERIFICATION_FAILED"; b) the processing shall set EUTL-Sub-Status to the values provided by set of values from LOTL-Status and LOTL-Sub-Status; and c) the processing shall stop the process. PRO-4.2.4-03: The processing shall set EUTL-Loc to the URI provided in the tuple from the 'Pointers to other TSLs' field of Authenticated-LOTL (see clause 5.3.13 of ETSI TS 119 612 [1]) for which the 'Scheme territory' qualifier has value CC and for which the 'MIME type' is XML. PRO-4.2.4-04: The processing shall set EUTL to the XML file retrieved from EUTL-Loc. PRO-4.2.4-05: The processing shall set EUTL-Certs-Set to the set of certificates provided in the tuple from the 'Pointers to other TSLs' field of Authenticated-LOTL (see clause 5.3.13 of ETSI TS 119 612 [1]) for which the 'Scheme territory' qualifier has value CC and for which the 'MIME type' is XML. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 16 PRO-4.2.4-06: The processing shall set EUTL-Signer-Cert to the ds:X509Certificate value of the ds:KeyInfo of the ds:Signature of EUTL. PRO-4.2.4-07: If EUTL-Signer-Cert is not part of EUTL-Certs-Set, then: a) the processing shall set Authenticated-EUTL to void; b) the processing shall set EUTL-Status to the value "EUTL_VERIFICATION_FAILED"; c) the processing shall set EUTL-Sub-Status to the value "EUTLSO_SIGNER_CERT_NOT_AUTHENTICATED_BY_LOTL"; and d) the processing shall stop the process. PRO-4.2.4-08: The processing shall validate ds:Signature of EUTL considering EUTL-Signer-Cert as a directly trusted certificate, i.e. as a trust anchor. PRO-4.2.4-09: If the signature validation performed in PRO-4.2.4-08 failed, then: a) the processing shall set Authenticated-EUTL to void; b) the processing shall set EUTL-Status to the value "EUTL_VERIFICATION_FAILED"; c) the processing shall set EUTL-Sub-Status to the set of values provided by the validation procedure together with the value "EUTL_SIGNATURE_VERIFICATION_FAILED"; and d) the processing shall stop the process. PRO-4.2.4-10: If the 'Next update' date of EUTL (see clause 5.3.15 of ETSI TS 119 612 [1]) has passed, then the processing shall add to EUTL-Sub-Status the value "WARNING_EUTL_NEXTUPDATE_PASSED". PRO-4.2.4-11: The processing shall set Authenticated-EUTL to EUTL. PRO-4.2.4-12: The processing shall set EUTL-Status to the value "EUTL_VERIFICATION_PASSED".
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.3 Obtaining listed services matching a certificate
| |
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.3.1 Description
|
The procedure specified in clause 4.3 allows to obtain, from the trusted list of a specific country, matching listed services, associated service information for a certificate for a specific date and time, for a specific service type identifier. NOTE: The difference between a QTS type and a Service type identifier as specified in clause 5.5.1.1 of ETSI TS 119 612 [1] may reside in the sub-definition of that identifier service type into sub-services defined through 'additionalServiceInformation' extensions (see clause 5.5.9.4 of ETSI TS 119 612 [1]).
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.3.2 Inputs
|
Name Description CERT X.509 certificate for which the information is to be obtained (e.g. a ds:X509Certificate value of a ds:KeyInfo of the ds:Signature) TLS-Sti One of the Service type identifier URI values specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. Date-time Date and time indication as specified in clause 5.1.3 of ETSI TS 119 612 [1]. CC Country code value in accordance with the ISO 3166-1 [2] Alpha 2 country code, set in capital letters. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 17
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.3.3 Outputs
|
Name Description SI-Results A set of groups of elements, each group made of: a) SI-full defined as an XML section corresponding to a 'Service information'element as specified in clause 5.5 of ETSI TS 119 612 [1]; b) SI-at-Date-time defined as an XML section corresponding either to the Date-time related 'Service (current) information' element as specified in clause 5.5 of ETSI TS 119 612 [1] with the exception of clause 5.5.10 or to the Date-time related 'Service history instance' element as specified in clause 5.6 of ETSI TS 119 612 [1]; c) TSP-Name defined as a 'TSP name' element as defined in clause 5.4.1 of ETSI TS 119 612 [1]; and d) TSP-Trade-Name defined as a 'TSP trade name' element as defined in clause 5.4.2 of ETSI TS 119 612 [1]. SI-Status The status indication of the process consisting in obtaining for a certificate, for a specific type of 'Service type identifier' URI value specified in clause 5.5.1.1 of ETSI TS 119 612 [1] and for a specific date and time, a matching listed service and its associated service information. SI-Sub-Status A list of indications supplementing SI-Status indication of the process. OUT-4.3.3-01: All above listed output variables shall be initialized to void.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.3.4 Processing
|
PRO-4.3.4-01: If CC represents an EUMS and/or is set to "GB" or "UK": a) then the processing shall run the process for authenticating the EUMS trusted list from CC as described in clause 4.2 of the present document, passing CC as input to the process; b) else: 1) the processing shall set SI-Status to the value "PROCESS_FAILED"; 2) the processing shall set SI-Sub-Status to the value "Provided_country_code_not_representing_an_EU_MS"; and 3) the processing shall stop the process. PRO-4.3.4-02: If the output Authenticated-EUTL is void as a result of the execution of the process referred in PRO-4.3.4-01, then: a) the processing shall set SI-Status to the value "PROCESS_FAILED"; b) the processing shall set SI-Sub-Status to the values provided by set of values from EUTL-Status and EUTL-Sub-Status; and c) the processing shall stop the process. PRO-4.3.4-03: For each 'Service information' entry (see clause 5.5 of ETSI TS 119 612 [1]) within Authenticated-EUTL, the processing shall check whether: i) the 'Service type identifier' (see clause 5.5.1 of ETSI TS 119 612 [1]) matches TLS-Sti; and ii) either a certification path (see IETF RFC 5280 [4]) to CERT is found which, when using the 'Service digital identity' public key and associated subject name of the entry as a trust anchor, validates successfully according to section 6.1 of IETF RFC 5280 [4], with input (b) of section 6.1.1 set to Date-time and inputs (c) and (e) to (i) set to the corresponding default values of the data type PathConstraints specified in Common PKI v2.0 part 5 [5] Table 1; or the 'Service digital identity' public key and associated subject name are identical to the public key and subject name in CERT; NOTE 1: In function of the TLS-Sti value, the length of the certification path can be "0", "1" or longer. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 18 NOTE 2: Name chaining is performed as part of the certificate path validation specified in clause 6 of IETF RFC 5280 [4]. If no valid name chains are found from the subject distinguished name of one of the X.509 certificates present within the above 'Service digital identity' to the issuer distinguished name present within CERT, then no valid certificate path will be built. NOTE 3: Although multiple X.509 certificates can be present within the above 'Service digital identity', they are necessarily representing the same public key and have identical subject names in a trusted list compliant to ETSI TS 119 612 [1]. and, when both checks succeed, shall add a tuple to SI-Results with: a) SI-full set to the entire such 'Service information' entry (see clause 5.5 of ETSI TS 119 612 [1]); and b) SI-at-Date-time set to: - either the entire such 'Service information' entry excepted, if any, the 'Service history' element (see clause 5.5.10 of ETSI TS 119 612 [1]) when Date-time is greater than or equal to 'Current status starting date and time' of that entry (see clause 5.5.5 of ETSI TS 119 612 [1]); - or the first 'Service history instance' (see clause 5.6 of ETSI TS 119 612 [1]) of that entry for which the 'Previous status starting date and time' (see clause 5.6.5 of ETSI TS 119 612 [1]) is less than or equal to Date-time. c) TSP-Name set to the 'TSP name' element (see clause 5.4.1 of ETSI TS 119 612 [1]) associated to that 'Service information' entry; and d) TSP-Trade-Name set to the 'TSP trade name' element (see clause 5.4.2 of ETSI TS 119 612 [1]) associated to that 'Service information' entry. PRO-4.3.4-03A: For each tuple in SI-Results, the processing shall check that the 'Service history instance' elements in the corresponding SI-full element are correctly ordered: a) when this is not the case, the processing shall stop and report the error; b) when 'Service history instance' elements have the exact same 'Previous status starting date and time' value, the processing shall stop and report the error. PRO-4.3.4-04: The processing shall set SI-Status to the value "PROCESS_PASSED". PRO-4.3.4-05: The processing shall add to SI-Sub-Status the indication value "WARNING_T1_DUPLICATION" when two or more of the SI-Results tuples include an SI-at-Date-time XML section for which: a) an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) includes the value http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSignatures; and b) values included in the respective 'Service current status" and/or 'Service previous status' fields (see respectively clauses 5.5.4 and 5.6.4 of ETSI TS 119 612 [1]) are identical. PRO-4.3.4-06: The processing shall add to SI-Sub-Status the indication value "ERROR_T1_DUPLICATION" when two or more of the SI-Results tuples include an SI-at-Date-time XML section for which: a) an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) includes the value http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSignatures; and b) values included in the respective 'Service current status" and/or 'Service previous status' fields (see respectively clauses 5.5.4 and 5.6.4 of ETSI TS 119 612 [1]) are not identical. PRO-4.3.4-07: The processing shall add to SI-Sub-Status the indication value "WARNING_T2_DUPLICATION" when two or more of the SI-Results tuples include an SI-at-Date-time XML section for which: a) an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) includes the value http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSeals; and ETSI ETSI TS 119 615 V1.2.1 (2023-06) 19 b) values included in the respective 'Service current status" and/or 'Service previous status' fields (see respectively clauses 5.5.4 and 5.6.4 of ETSI TS 119 612 [1]) are identical. PRO-4.3.4-08: The processing shall add to SI-Sub-Status the indication value "ERROR_T2_DUPLICATION" when two or more of the SI-Results tuples include an SI-at-Date-time XML section for which: a) an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) includes the value http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSeals; and b) values included in the respective 'Service current status" and/or 'Service previous status' fields (see respectively clauses 5.5.4 and 5.6.4 of ETSI TS 119 612 [1]) are not identical. PRO-4.3.4-09: The processing shall add to SI-Sub-Status the indication value "WARNING_T3_DUPLICATION" when two or more of the SI-Results tuples include an SI-at-Date-time XML section for which: a) an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) includes the value http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForWebSiteAuthentication; and b) values included in the respective 'Service current status" and/or 'Service previous status' fields (see respectively clauses 5.5.4 and 5.6.4 of ETSI TS 119 612 [1]) are identical. PRO-4.3.4-10: The processing shall add to SI-Sub-Status the indication value "ERROR_T3_DUPLICATION" when two or more of the SI-Results tuples include an SI-at-Date-time XML section for which: a) an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) includes the value http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForWebSiteAuthentication; and b) values included in the respective 'Service current status" and/or 'Service previous status' fields (see respectively clauses 5.5.4 and 5.6.4 of ETSI TS 119 612 [1]) are not identical. PRO-4.3.4-11: When two or more of the SI-Results tuples include different TSP-Name values, then: a) the processing shall add to SI-Sub-Status the indication value "ERROR_TSP_CONFLICT"; and b) the processing shall set SI-Status to the value "PROCESS_FAILED".
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.4 EU qualified certificate determination
| |
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.4.1 Description
|
The procedure specified in clause 4.4 allows determining whether a certificate is confirmed by the applicable EUMS trusted list to have been an EU qualified certificate at a specific date and time and for which type.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.4.2 Inputs
|
Name Description of inputs CERT X.509 certificate for which the information is to be obtained (e.g. a ds:X509Certificate value of a ds:KeyInfo of the ds:Signature) Date-time Date and time indication as specified in clause 5.1.3 of ETSI TS 119 612 [1]. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 20
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.4.3 Outputs
|
Name Description QC-Results A set of indications of the EU qualified status of CERT through one or more of the following values: a) "Not_Qualified" to indicate that CERT is not an EU qualified certificate according to the EUMS trusted list from CC at Date-time; b) "Not_Qualified_For_eSig" to indicate that CERT is not an EU qualified certificate for electronic signatures according to the EUMS trusted list from CC at Date-time; c) "Not_Qualified_For_eSeal" to indicate that CERT is not an EU qualified certificate for electronic seals according to the EUMS trusted list from CC at Date-time; d) "Not_QWAC" to indicate that CERT is not an EU qualified certificate for website authentication according to the EUMS trusted list from CC at Date-time; e) "QC_For_eSig" to indicate that CERT is an EU qualified certificate for electronic signatures according to the EUMS trusted list from CC at Date- time; f) "QC_For_eSeal" to indicate that CERT is an EU qualified certificate for electronic seals according to the EUMS trusted list from CC at Date-time; g) "QWAC" to indicate that CERT is an EU qualified certificate for web site authentication according to the EUMS trusted list from CC at Date-time; h) "INDET_QC_For_eSig" to indicate that the EUMS trusted list from CC cannot be used to confirm that CERT is a qualified certificate for electronic signatures at Date-time; i) "INDET_QC_For_eSeal" to indicate that the EUMS trusted list from CC cannot be used to confirm that CERT is a qualified certificate for electronic seals at Date-time; j) "INDET_QWAC" to indicate that the EUMS trusted list from CC cannot be used to confirm that CERT is a qualified certificate for website authentication at Date-time; k) "INDETERMINATE"; l) Void. QC-Status The status indication of the process. QC-Sub-Status A list of indications supplementing QC-Status indication. CHECK_1_SET-OF_QE An intermediate result as defined in the process below. CHECK_2_SET-OF_QE An intermediate result as defined in the process below. CHECK_3_SET-OF_QE An intermediate result as defined in the process below. OUT-4.4.3-01: All above listed output variables shall be initialized to void.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.4.4 Processing
|
PRO-4.4.4-01: The processing shall set CC to the country code value of the countryName attribute of the issuer field of the certificate provided in CERT, in capital letters in accordance with the ISO 3166-1 [2] Alpha 2 country code, with, when applicable: a) the country code value "GB" being converted to "UK"; b) the country code value "GR" being converted to "EL". PRO-4.4.4-02: The processing shall set TLS-Sti to the value "http://uri.etsi.org/TrstSvc/Svctype/CA/QC" as specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. PRO-4.4.4-03: The processing shall run the process described in clause 4.3 of the present document, passing the following inputs to the process: a) CERT; b) TLS-Sti; c) Date-time; d) CC. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 21 PRO-4.4.4-04: If the output SI-Status of the process run in PRO-4.4.4-03 has the value "PROCESS_FAILED", then: a) the processing shall set QC-Status to the value "PROCESS_FAILED"; b) the processing shall set QC-Sub-Status to the values provided by set of values from SI-Status and SI-Sub-Status; and c) the processing shall stop the process. PRO-4.4.4-05: If the output SI-Results of the process run in PRO-4.4.4-03 is void, then: a) the processing shall set QC-Status to the value "PROCESS_PASSED"; b) the processing shall set QC-Sub-Status to the value "No_confirmation_found_in_EUMSTL_CC"; c) the processing shall set QC-Results to the value "Not_Qualified"; and d) the processing shall stop the process. PRO-4.4.4-06: When an organizationName attribute is present in the issuerName field of the certificate provided in CERT, and performing matching verification between two names, naming attributes or distinguished names as specified in clause 7.1 of IETF RFC 5280 [4]: a) then if the organizationName attribute of the issuerName field of the certificate provided in CERT is not matching one of the values of TSP-Name or TSP-Trade-Name of the output SI-Results of the process run in PRO-4.4.4-03, then: 1) the processing shall set QC-Status to the value "PROCESS_FAILED"; 2) the processing shall set QC-Results to the value "INDETERMINATE"; 3) the processing shall set QC-Sub-Status to the value "ERROR_TSP_NAME_INCONSISTENCY_BETWEEN_CERT_AND_TL"; and 4) the processing shall stop the process. b) else the processing shall decide the strategy to verify that the legal or natural person having issued CERT is the person identified by one of the values of TSP-Name or TSP-Trade-Name of the output SI-Results of the process run in PRO-4.4.4-03 and in case of failure set QC-Status to the value "PROCESS_FAILED", QC-Results to the value "INDETERMINATE", QC-Sub-Status to the value "ERROR_TSP_NAME_INCONSISTENCY_BETWEEN_CERT_AND_TL" and shall stop the process. EXAMPLE 1: The strategy referred above can include: i) verification of the matching of the commonName attribute of the issuerName field of the certificate provided in CERT with one of the values of TSP-Name or TSP-Trade-Name of the output SI-Results of the process run in PRO-4.4.4-03; or ii verification of the matching of the distinguished name of the issuerName field of the certificate provided in CERT with the distinguished name of the Sdi of the SI-full of the output SI-Results of the process run in PRO-4.4.4-03. PRO-4.4.4-07: When Date-time is before 2016-06-30T22:00:00Z, or when the date and time value of the NotBeforeDate field of CERT is a value before 2016-06-30T22:00:00Z, the processing shall go to PRO-4.4.4-33. PRO-4.4.4-08: The processing shall set the working variable CHECK_1 to void. NOTE 1: CHECK_1 is a variable defined as an indication whose possible values are the values present in Table 1. PRO-4.4.4-09: If the output SI-Sub-Status of the process run in PRO-4.4.4-03 includes the value "ERROR_T1_DUPLICATION", then the processing shall set CHECK_1 to the value "INDET_QC_For_eSig" and shall go to PRO-4.4.4-16. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 22 NOTE 2: The above check could also catch the "WARNING_T1_DUPLICATION" case and treat it the same way i.e. stopping the process and raising the warning. However, considering the trusted lists as legally constitutive information regarding the qualified status of a trust service and hence of one of its output (e.g. certificate, time stamp token, signed evidence), in the case the status information is consistent, the relying party can decide, despite the fact that such a construction of the trusted list is in conflict with CID (EU) 2015/1505 [i.2], to go further and still consider the information in the trusted list, provided no further inconsistency is discovered in the rest of the processing (e.g. conflicting service information qualifications extensions). PRO-4.4.4-10: If none of the SI-at-Date-time element(s) of the SI-Results tuples (from the process run in PRO-4.4.4-03) includes an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSignatures" or if the 'Service current status' or 'Service previous status' field of (any of) the SI-at-Date-time element(s) of the SI-Results tuples (from the process run in PRO-4.4.4-03) that include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSignatures" has the value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn", then the processing shall set CHECK_1 to the value "Not_Qualified_For_eSig" and shall go to PRO-4.4.4-16. PRO-4.4.4-10A: If the 'Service current status' or 'Service previous status' field of (any of) the SI-at-Date-time element(s) of the SI-Results tuples (from the process run in PRO-4.4.4-03) that include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSignatures" has a value different from either "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted" or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn", then: a) the processing shall add to QC-Sub-Status the value "ERROR_Service_Status_ Non- compliance_with_TS119612"; b) the processing shall set CHECK_1 to the value "INDET_QC_For_eSig"; and c) the processing shall go to PRO-4.4.4-16. PRO-4.4.4-11: The processing shall set CHECK_1_SET-OF_QE to the set of all 'QualificationElement' from all 'Qualifications' extensions (see clause 5.5.9.2 of ETSI TS 119 612 [1]) whose 'CriteriaList' element identifies CERT from all SI-at-Date-time elements of the SI-Results tuples (from the process run in PRO-4.4.4-03) that include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSignatures". PRO-4.4.4-12: The processing shall proceed as follows: a) it shall identify, if any, the set of all applicable qualifiers as per the content of the 'Qualifier' descendant elements (see clause 5.5.9.2.3 of ETSI TS 119 612 [1]) of all 'QualificationElement' elements of CHECK_1_SET-OF_QE; In case one of the following qualifier or combinations is found, it shall set CHECK_1 to the value "INDET_QC_For_eSig", it shall add to QC-Sub-Status the value "WARNING_T1_TL_Inconsistency_in_applying_qualifiers", and it shall go to PRO-4.4.4-16: 1) 'QCForESeal' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal"); 2) 'QCForWSA' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA"); 3) 'NotQualified' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/NotQualified") and 'QCStatement' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCStatement"); 4) 'QCForESig' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig") and 'QCForESeal' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal"); 5) 'QCForESig' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig") and 'QCForWSA' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA"); 6) 'QCForESeal' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal") and 'QCForWSA' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA"); or ETSI ETSI TS 119 615 V1.2.1 (2023-06) 23 7) QCForLegalPerson ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForLegalPerson"). PRO-4.4.4-13: The processing shall get the information about the presence and content of the id-etsi-qcs- QcCompliance and id-etsi-qcs-QcType statements (see ETSI EN 319 412-5 [3], hereafter respectively QcCompliance and QcType) in CERT. PRO-4.4.4-14: If it results from PRO-4.4.4-13 that CERT includes more than one QcType identifier in its QcType statement when present, then the processing shall add to QC-Sub-Status the value "WARNING_CERT_Inconsistency_in_QcType_qualifiers_Non-compliance_with_EN319412-5". PRO-4.4.4-15: Using the applicable qualifiers identified in PRO-4.4.4-12.(a): a) the processing shall check whether the following qualifiers are present among them: 'QCForESig' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig"), 'NotQualified' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/NotQualified") and 'QCStatement' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCStatement"); b) the processing shall use the information obtained in PRO-4.4.4-13 to select the appropriate row of Table 1, and shall use the information obtained in above point PRO-4.4.4-15.(a) to select the appropriate column of Table 1; NOTE 3: Information in row1/column0 means, and corresponds to the case where, the QcCompliance statement is present in CERT without any QcType statement being present, or the QcCompliance statement is present in CERT together with QcType 1 statement. The meaning of the other rows of column0 can be deduced accordingly. Information in row0/column1 means, and corresponds to the case where, none of the three qualifiers 'NotQualified', 'QCStatement', 'QCForESig' in the 'Qualifications' extensions (denoted Sie:Q in Table 1) applies to CERT (this also includes the case where no Sie:Q extension is present). Information in row0/column5 means, and corresponds to the case where, both qualifiers 'QCStatement' and 'QCForESig' in the 'Qualifications' extensions (denoted Sie:Q in Table 1) apply to CERT. The meaning of the other columns of row0 can be deduced accordingly. c) the processing shall set CHECK_1 to the value found in the selected cell of Table 1; EXAMPLE 2: If QcCompliance extension is present in CERT together with the QcType 3 and the qualifier 'QCForESig' applies to CERT as per the applicable qualifiers, then the value set to CHECK_1 is "QC_For_eSig" (see row3/column4). d) if row8/column3 of Table 1 was selected in step (b) above, then the processing shall add to QC-Sub-Status the value "WARNING_T1_Not_Enough_Info_on_QC_Type". ETSI ETSI TS 119 615 V1.2.1 (2023-06) 24 Table 1: QC-For-eSig determination PRO-4.4.4-16: The processing shall set the working variable CHECK_2 to void. NOTE 4: CHECK_2 is a variable defined as an indication whose possible values are the values present in Table 2. PRO-4.4.4-17: If the output SI-Sub-Status of the process run in PRO-4.4.4-03 includes the value "ERROR_T2_DUPLICATION", then the processing shall set CHECK_2 to the value "INDET_QC_For_eSeal" and shall go to PRO-4.4.4-24. row0 None of Sie:Q NotQualified QCStatement QCForESig Sie:Q NotQualified (with or without QCForESig) Sie:Q QCStatement Sie:Q QCForESig Sie:Q QCStatement & QCForESig row1 QcCompliance or QcCompliance + QcType 1 “QC_For_eSig” “Not_Qualified_For _eSig” “QC_For_eSig” “QC_For_eSig” “QC_For_eSig” row2 QcCompliance + QcType 2 “Not_Qualified_For _eSig” “Not_Qualified_For _eSig” “Not_Qualified_For_ eSig” “QC_For_eSig” “QC_For_eSig” row3 QcCompliance + QcType 3 “Not_Qualified_For _eSig” “Not_Qualified_For _eSig” “Not_Qualified_For_ eSig” “QC_For_eSig” “QC_For_eSig” row4 QcCompliance + QcType 1 & QcType 2 “INDET_QC_For_eSi g” “Not_Qualified_For _eSig” “INDET_QC_For_eSig ” “QC_For_eSig” “QC_For_eSig” row5 QcCompliance + QcType 1 & QcType 3 “INDET_QC_For_eSi g” “Not_Qualified_For _eSig” “INDET_QC_For_eSig ” “QC_For_eSig” “QC_For_eSig” row6 QcCompliance + QcType 2 & QcType 3 “Not_Qualified_For _eSig” “Not_Qualified_For _eSig” “Not_Qualified_For_ eSig” “QC_For_eSig” “QC_For_eSig” row7 QcCompliance + QcType 1 & QcType 2 & QCType 3 “INDET_QC_For_eSi g” “Not_Qualified_For _eSig” “INDET_QC_For_eSig ” “QC_For_eSig” “QC_For_eSig” row8 no QcCompliance and no QcType “Not_Qualified_For _eSig” “Not_Qualified_For _eSig” “INDET_QC_For_eSig ” “Not_Qualified_For _eSig” “QC_For_eSig” row9 no QcCompliance + QcType 1 “Not_Qualified_For _eSig” “Not_Qualified_For _eSig” “QC_For_eSig” “Not_Qualified_For _eSig” “QC_For_eSig” row10 no QcCompliance + QcType 2 “Not_Qualified_For _eSig” “Not_Qualified_For _eSig” “Not_Qualified_For_ eSig” “Not_Qualified_For _eSig” “QC_For_eSig” row11 no QcCompliance + QcType 3 “Not_Qualified_For _eSig” “Not_Qualified_For _eSig” “Not_Qualified_For_ eSig” “Not_Qualified_For _eSig” “QC_For_eSig” row12 no QcCompliance + QcType 1 & QcType 2 “Not_Qualified_For _eSig” “Not_Qualified_For _eSig” “INDET_QC_For_eSig ” “Not_Qualified_For _eSig” “QC_For_eSig” row13 no QcCompliance + QcType 1 & QcType 3 “Not_Qualified_For _eSig” “Not_Qualified_For _eSig” “INDET_QC_For_eSig ” “Not_Qualified_For _eSig” “QC_For_eSig” row14 no QcCompliance + QcType 2 & QcType 3 “Not_Qualified_For _eSig” “Not_Qualified_For _eSig” “Not_Qualified_For_ eSig” “Not_Qualified_For _eSig” “QC_For_eSig” row15 no QcCompliance + QcType 1 & QcType 2 & QCType 3 “Not_Qualified_For _eSig” “Not_Qualified_For _eSig” “INDET_QC_For_eSig ” “Not_Qualified_For _eSig” “QC_For_eSig” column0 column1 column2 column3 column4 column5 Sie:aSI = ForeSignatures ETSI ETSI TS 119 615 V1.2.1 (2023-06) 25 NOTE 5: The above check could also catch the "WARNING_T2_DUPLICATION" case and treat it the same way i.e. stopping the process and raising the warning. However, considering the trusted lists as legally constitutive information regarding the qualified status of a trust service and hence of one of its output (e.g. certificate, time stamp token, signed evidence), in the case the status information is consistent, the relying party can decide, despite the fact that such a construction of the trusted list is in conflict with CID (EU) 2015/1505 [i.2], to go further and still consider the information in the trusted list, provided no further inconsistency is discovered in the rest of the processing (e.g. conflicting service information qualifications extensions). PRO-4.4.4-18: If none of the SI-at-Date-time element(s) of the SI-Results tuples (from the process run in PRO-4.4.4-03) includes an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSeals" or if the 'Service current status' or 'Service previous status' field of (any of) the SI-at-Date-time elements of the SI-Results tuples (from the process run in PRO-4.4.4-03) that include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSeals" has the value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn", then the processing shall set CHECK_2 to the value "Not_Qualified_For_eSeal" and shall go to PRO-4.4.4-24. PRO-4.4.4-18A: If the 'Service current status' or 'Service previous status' field of (any of) the SI-at-Date-time element(s) of the SI-Results tuples (from the process run in PRO-4.4.4-03) that include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSeals" a value different from either "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted" or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn", then: a) the processing shall add to QC-Sub-Status the value "ERROR_Service_Status_ Non-compliance_with_TS119612"; b) the processing shall set CHECK_1 to the value "INDET_QC_For_eSeal"; and c) the processing shall go to PRO-4.4.4-24. PRO-4.4.4-19: The processing shall set CHECK_2_SET-OF_QE to the set of all 'QualificationElement' from all 'Qualifications' extensions (see clause 5.5.9.2 of ETSI TS 119 612 [1]) whose 'CriteriaList' element identifies CERT from all SI-at-Date-time elements of the SI-Results tuples (from the process run in PRO-4.4.4-03) that include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSeals". PRO-4.4.4-20: The processing shall proceed as follows: a) it shall identify, if any, the set of all applicable qualifiers as per the content of the 'Qualifier' descendant elements (see clause 5.5.9.2.3 of ETSI TS 119 612 [1]) of all 'QualificationElement' elements of CHECK_2_SET-OF_QE; b) in case one of the following qualifier or combinations is found, it shall set CHECK_2 to the value "INDET_QC_For_eSeal", it shall add to QC-Sub-Status the value "WARNING_T2_TL_Inconsistency_in_applying_qualifiers", and it shall go to PRO-4.4.4-24: 1) 'QCForESig' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig"); 2) 'QCForWSA' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA"); 3) 'NotQualified' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/NotQualified") and 'QCStatement' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCStatement"); 4) 'QCForESig' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig") and 'QCForESeal' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal"); 5) 'QCForESig' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig") and 'QCForWSA' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA"); or 6) 'QCForESeal' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal") and 'QCForWSA' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA"). ETSI ETSI TS 119 615 V1.2.1 (2023-06) 26 PRO-4.4.4-21: The processing shall get the information about the presence and content of the QcCompliance and QcType statements (see ETSI EN 319 412-5 [3]) in CERT. PRO-4.4.4-22: If it results from PRO-4.4.4-21 that CERT includes more than one QcType identifier in its QcType statement when present, then the processing shall add to QC-Sub-Status the value "WARNING_CERT_Inconsistency_in_QcType_qualifiers_Non-compliance_with_EN319412-5". PRO-4.4.4-23: Using the applicable qualifiers identified in PRO-4.4.4-20.(a): a) the processing shall check whether the following qualifiers are present among them: 'QCForESeal' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal"), 'NotQualified' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/NotQualified") and 'QCStatement' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCStatement"); b) the processing shall use the information obtained in PRO-4.4.4-21 to select the appropriate row of Table 2, and shall use the information obtained in above point PRO-4.4.4-23.(a) to select the appropriate column of Table 2; NOTE 6: Information in row1/column0 means, and corresponds to the case where, the QcCompliance statement is present in CERT without any QcType statement being present, or the QcCompliance statement is present in CERT together with QcType 1 statement. The meaning of the other rows of column0 can be deduced accordingly. Information in row0/column1 means, and corresponds to the case where, none of the three qualifiers 'NotQualified', 'QCStatement', 'QCForESeal' in the 'Qualifications' extensions (denoted Sie:Q in Table 2) applies to CERT (this also includes the case where no Sie:Q extension is present). Information in row0/column5 means, and corresponds to the case where, both qualifiers 'QCStatement' and 'QCForESeal' in the 'Qualifications' extensions apply to CERT. The meaning of the other columns of row0 can be deduced accordingly. c) the processing shall set CHECK_2 to the value found in the selected cell of Table 2; EXAMPLE 3: If QcCompliance extension is present in CERT together with the QcType 3 and the qualifier 'QCForESeal' applies to CERT as per the applicable qualifiers, then the value set to CHECK_2 is "QC_For_eSeal" (see row3/column4). d) if row8/column3 of Table 2 was selected in step (b) above, then the processing shall add to QC-Sub-Status the value "WARNING_T2_Not_Enough_Info_on_QC_Type". ETSI ETSI TS 119 615 V1.2.1 (2023-06) 27 Table 2: QC-For-eSeal determination PRO-4.4.4-24: The processing shall set the working variable CHECK_3 to void. NOTE 7: CHECK_3 is a variable defined as an indication whose possible values are the values present in Table 3. PRO-4.4.4-25: If the output SI-Sub-Status of the process run in PRO-4.4.4-03 includes the value "ERROR_T3_DUPLICATION", then the processing shall set CHECK_3 to the value "INDET_QWAC" and shall go to PRO-4.4.4-32. row0 None of Sie:Q NotQualified QCStatement QCForESeal Sie:Q NotQualified (with or without QCForESeal) Sie:Q QCStatement Sie:Q QCForESeal Sie:Q QCStatement & QCForESeal row1 QcCompliance or QcCompliance + QcType 1 “Not_Qualified_For _eSeal” “Not_Qualified_For _eSeal” “Not_Qualified_For_ eSeal” “QC_For_eSeal” “QC_For_eSeal” row2 QcCompliance + QcType 2 “QC_For_eSeal” “Not_Qualified_For _eSeal” “QC_For_eSeal” “QC_For_eSeal” “QC_For_eSeal” row3 QcCompliance + QcType 3 “Not_Qualified_For _eSeal” “Not_Qualified_For _eSeal” “Not_Qualified_For_ eSeal” “QC_For_eSeal” “QC_For_eSeal” row4 QcCompliance + QcType 1 & QcType 2 “INDET_QC_For_eSe al” “Not_Qualified_For _eSeal” “INDET_QC_For_eSe al” “QC_For_eSeal” “QC_For_eSeal” row5 QcCompliance + QcType 1 & QcType 3 “Not_Qualified_For _eSeal” “Not_Qualified_For _eSeal” “Not_Qualified_For_ eSeal” “QC_For_eSeal” “QC_For_eSeal” row6 QcCompliance + QcType 2 & QcType 3 “INDET_QC_For_eSe al” “Not_Qualified_For _eSeal” “INDET_QC_For_eSe al” “QC_For_eSeal” “QC_For_eSeal” row7 QcCompliance + QcType 1 & QcType 2 & QCType 3 “INDET_QC_For_eSe al” “Not_Qualified_For _eSeal” “INDET_QC_For_eSe al” “QC_For_eSeal” “QC_For_eSeal” row8 no QcCompliance and no QcType “Not_Qualified_For _eSeal” “Not_Qualified_For _eSeal” “INDET_QC_For_eSe al” “Not_Qualified_For _eSeal” “QC_For_eSeal” row9 no QcCompliance + QcType 1 “Not_Qualified_For _eSeal” “Not_Qualified_For _eSeal” “Not_Qualified_For_ eSeal” “Not_Qualified_For _eSeal” “QC_For_eSeal” row10 no QcCompliance + QcType 2 “Not_Qualified_For _eSeal” “Not_Qualified_For _eSeal” “QC_For_eSeal” “Not_Qualified_For _eSeal” “QC_For_eSeal” row11 no QcCompliance + QcType 3 “Not_Qualified_For _eSeal” “Not_Qualified_For _eSeal” “Not_Qualified_For_ eSeal” “Not_Qualified_For _eSeal” “QC_For_eSeal” row12 no QcCompliance + QcType 1 & QcType 2 “Not_Qualified_For _eSeal” “Not_Qualified_For _eSeal” “INDET_QC_For_eSe al” “Not_Qualified_For _eSeal” “QC_For_eSeal” row13 no QcCompliance + QcType 1 & QcType 3 “Not_Qualified_For _eSeal” “Not_Qualified_For _eSeal” “Not_Qualified_For_ eSeal” “Not_Qualified_For _eSeal” “QC_For_eSeal” row14 no QcCompliance + QcType 2 & QcType 3 “Not_Qualified_For _eSeal” “Not_Qualified_For _eSeal” “INDET_QC_For_eSe al” “Not_Qualified_For _eSeal” “QC_For_eSeal” row15 no QcCompliance + QcType 1 & QcType 2 & QCType 3 “Not_Qualified_For _eSeal” “Not_Qualified_For _eSeal” “INDET_QC_For_eSe al” “Not_Qualified_For _eSeal” “QC_For_eSeal” column0 column1 column2 column3 column4 column5 Sie:aSI = ForeSeals ETSI ETSI TS 119 615 V1.2.1 (2023-06) 28 NOTE 8: The above check could also catch the "WARNING_T3_DUPLICATION" case and treat it the same way i.e. stopping the process and raising the warning. However, considering the trusted lists as legally constitutive information regarding the qualified status of a trust service and hence of one of its output (e.g. certificate, time stamp token, signed evidence), in the case the status information is consistent, the relying party can decide, despite the fact that such a construction of the trusted list is in conflict with CID (EU) 2015/1505 [i.2], to go further and still consider the information in the trusted list, provided no further inconsistency is discovered in the rest of the processing (e.g. conflicting service information qualifications extensions). PRO-4.4.4-26: If none of the SI-at-Date-time element(s) of the SI-Results tuples (from the process run in PRO-4.4.4-03) includes an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForWebSiteAuthentication" or if the 'Service current status' or 'Service previous status' field of (any of) the SI-at-Date-time elements of the SI-Results tuples (from the process run in PRO-4.4.4-03) that include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForWebSiteAuthentication" has the value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn", then the processing shall set CHECK_3 to the value "Not_QWAC" and shall go to PRO-4.4.4-32. PRO-4.4.4-26A: If the 'Service current status' or 'Service previous status' field of (any of) the SI-at-Date-time element(s) of the SI-Results tuples (from the process run in PRO-4.4.4-03) that include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForWebSiteAuthentication" or a value different from either "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted" or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn", then: a) the processing shall add to QC-Sub-Status the value "ERROR_Service_Status_ Non- compliance_with_TS119612"; b) the processing shall set CHECK_1 to the value "INDET_QWAC"; and c) the processing shall go to PRO-4.4.4-32. PRO-4.4.4-27: The processing shall set CHECK_3_SET-OF_QE to the set of all 'QualificationElement' from all 'Qualifications' extensions (see clause 5.5.9.2 of ETSI TS 119 612 [1]) whose 'CriteriaList' element identifies CERT from all SI-at-Date-time elements of the SI-Results tuples (from the process run in PRO-4.4.4-03) that include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForWebSiteAuthentication". PRO-4.4.4-28: The processing shall proceed as follows: a) it shall identify, if any, the set of all applicable qualifiers as per the content of the 'Qualifier' descendant elements (see clause 5.5.9.2.3 of ETSI TS 119 612 [1]) of all 'QualificationElement' elements of CHECK_3_SET-OF_QE; b) in case one of the following qualifier or combinations is found, it shall set CHECK_3 to the value "INDET_QWAC", it shall add to QC-Sub-Status the value "WARNING_T3_TL_Inconsistency_in_applying_qualifiers", and it shall go to PRO-4.4.4-32: 1) 'QCForESig' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig"); 2) 'QCForESeal' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal"); 3) 'NotQualified' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/NotQualified") and 'QCStatement' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCStatement"); 4) 'QCForESig' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig") and 'QCForESeal' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal"); 5) 'QCForESig' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESig") and 'QCForWSA' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA"); or 6) 'QCForESeal' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal") and 'QCForWSA' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA"). ETSI ETSI TS 119 615 V1.2.1 (2023-06) 29 PRO-4.4.4-29: The processing shall get the information about the presence and content of the QcCompliance and QcType statements (see ETSI EN 319 412-5 [3]) in CERT. PRO-4.4.4-30: If it results from PRO-4.4.4-29 that CERT includes more than one QcType identifier in its QcType statement when present, then the processing shall add to QC-Sub-Status the value "WARNING_CERT_Inconsistency_in_QcType_qualifiers_Non-compliance_with_EN319412-5". PRO-4.4.4-31: Using the applicable qualifiers identified in PRO-4.4.4-28.(a): a) the processing shall check whether the following qualifiers are present among them: 'QCForWSA' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA"), 'NotQualified' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/NotQualified") and 'QCStatement' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCStatement"); b) the processing shall use the information obtained in PRO-4.4.4-29 to select the appropriate row of Table 3, and it shall use the information obtained in above point PRO-4.4.4-31.(a) to select the appropriate column of Table 3; NOTE 9: Information in row1/column0 means, and corresponds to the case where, the QcCompliance statement is present in CERT without any QcType statement being present, or the QcCompliance statement is present in CERT together with QcType 1 statement. The meaning of the other rows of column0 can be deduced accordingly. Information in row0/column1 means, and corresponds to the case where, none of the three qualifiers 'NotQualified', 'QCStatement', 'QCForWSA' in the 'Qualifications' extensions (denoted Sie:Q in Table 3) applies to CERT (this also includes the case where no Sie:Q extension is present). Information in row0/column5 means, and corresponds to the case where, both qualifiers 'QCStatement' and 'QCForWSA' in the 'Qualifications' extensions apply to CERT. The meaning of the other columns of row0 can be deduced accordingly. c) the processing shall set CHECK_3 to the value found in the selected cell of Table 3; EXAMPLE 4: If QcCompliance extension is present in CERT together with the QcType 3 and the qualifier 'QCForWSA' applies to CERT as per the applicable qualifiers, then the value set to CHECK_3 is "QWAC" (see row3/column4). ETSI ETSI TS 119 615 V1.2.1 (2023-06) 30 Table 3: QC-For-WebSiteAuthentication determination d) if row8/column3 of Table 3 was selected in step (b) above, then the processing shall add to QC-Sub-Status the value "WARNING_T3_Not_Enough_Info_on_QC_Type". PRO-4.4.4-32: The processing shall compare two by two the values of CHECK_1, CHECK_2, and CHECK_3 on the basis of Table 4 as follows: a) when the comparison results in an "error" indication: 1) the processing shall set QC-Status to the value "PROCESS_FAILED"; 2) the processing shall add to QC-Sub-Status appropriate values reflecting the problematic two by two combinations; and 3) the processing shall stop the process. b) the processing shall set QC-Status to the value "PROCESS_PASSED"; row0 None of Sie:Q NotQualified QCStatement QCForWSA Sie:Q NotQualified (with or without QCForWSA) Sie:Q QCStatement Sie:Q QCForWSA Sie:Q QCStatement & QCForWSA row1 QcCompliance or QcCompliance + QcType 1 “Not_QWAC” “Not_QWAC” “Not_QWAC” “QWAC” “QWAC” row2 QcCompliance + QcType 2 “Not_QWAC” “Not_QWAC” “Not_QWAC” “QWAC” “QWAC” row3 QcCompliance + QcType 3 "QWAC" “Not_QWAC” “QWAC” “QWAC” “QWAC” row4 QcCompliance + QcType 1 & QcType 2 “Not_QWAC” “Not_QWAC” “Not_QWAC” “QWAC” “QWAC” row5 QcCompliance + QcType 1 & QcType 3 "INDET_QWAC” “Not_QWAC” "INDET_QWAC” “QWAC” “QWAC” row6 QcCompliance + QcType 2 & QcType 3 "INDET_QWAC” “Not_QWAC” "INDET_QWAC” “QWAC” “QWAC” row7 QcCompliance + QcType 1 & QcType 2 & QCType 3 "INDET_QWAC” “Not_QWAC” "INDET_QWAC” “QWAC” “QWAC” row8 no QcCompliance and no QcType “Not_QWAC” “Not_QWAC” "INDET_QWAC” “Not_QWAC” “QWAC” row9 no QcCompliance + QcType 1 “Not_QWAC” “Not_QWAC” “Not_QWAC” “Not_QWAC” “QWAC” row10 no QcCompliance + QcType 2 “Not_QWAC” “Not_QWAC” “Not_QWAC” “Not_QWAC” “QWAC” row11 no QcCompliance + QcType 3 “Not_QWAC” “Not_QWAC” “QWAC” “Not_QWAC” “QWAC” row12 no QcCompliance + QcType 1 & QcType 2 “Not_QWAC” “Not_QWAC” “Not_QWAC” “Not_QWAC” “QWAC” row13 no QcCompliance + QcType 1 & QcType 3 “Not_QWAC” “Not_QWAC” "INDET_QWAC” “Not_QWAC” “QWAC” row14 no QcCompliance + QcType 2 & QcType 3 “Not_QWAC” “Not_QWAC” "INDET_QWAC” “Not_QWAC” “QWAC” row15 no QcCompliance + QcType 1 & QcType 2 & QCType 3 “Not_QWAC” “Not_QWAC” "INDET_QWAC” “Not_QWAC” “QWAC” column0 column1 column2 column3 column4 column5 Sie:aSI = ForWebSiteAuthentication ETSI ETSI TS 119 615 V1.2.1 (2023-06) 31 c) the processing shall set QC-Results to the set of indications provided in CHECK_1, in CHECK_2, and in CHECK_3; d) when the comparison results in one or more "warning" indications: 1) the processing shall set QC-Status to the value "PROCESS_PASSED_WITH_WARNING"; 2) the processing shall add to QC-Sub-Status appropriate values reflecting the problematic two by two combinations. Table 4: QC status check e) the processing shall go to PRO-4.4.4-34. PRO-4.4.4-33: Proceed as follows: a) the processing shall set CHECK_2 to the value "Not_Qualified_For_eSeal"; b) the processing shall set CHECK_3 to the value "Not_QWAC"; c) if there are two or more of the SI-Results tuples (from the process run in PRO-4.4.4-03) that include an SI-at-Date-time XML section for which the values included in the 'Service previous status' fields (see clause 5.6.4 of ETSI TS 119 612 [1]) are identical, then the processing shall add to QC-Sub-Status the indication value "WARNING_TL-SERVICE-ENTRY-SDI_DUPLICATION"; d) if there are two or more of the SI-Results tuples that include an SI-at-Date-time XML section for which the values included in the 'Service previous status' fields (see clause 5.6.4 of ETSI TS 119 612 [1]) are not identical, then: 1) the processing shall add to QC-Sub-Status the indication value "ERROR_TL-SERVICE-ENTRY- SDI_DUPLICATION_STATUS_CONFLICT"; 2) the processing shall set QC-Status to the value "PROCESS_FAILED"; 3) the processing shall stop the process. e) the processing shall set CHECK_1 to void; ETSI ETSI TS 119 615 V1.2.1 (2023-06) 32 f) the processing shall proceed as follow: 1) When Date-time is before 2016-06-30T22:00:00Z, the processing shall check if the 'Service previous status' field of (any of) the SI-at-Date-time element(s) of the SI-Results tuples has one of the values "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionceased", "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/supervisionrevoked", "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/accreditationceased", or "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/accreditationrevoked"; 2) When Date-time is after 2016-06-30T22:00:00Z, the processing shall check if none of the SI-at-Date-time element(s) of the SI-Results tuples (from the process run in PRO-4.4.4-03) includes an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSignatures" or if the 'Service current status' or 'Service previous status' field of (any of) the SI-at-Date-time element(s) of the SI-Results tuples (from the process run in PRO-4.4.4-03) that include an 'additionalServiceInformation' extension (see clause 5.5.9.4 of ETSI TS 119 612 [1]) having the value "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/ForeSignatures" has the value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/withdrawn"; 3) if the check performed in point 1) or 2) above was successful, then: i) the processing shall set CHECK_1 to the value "Not_Qualified_For_eSig"; ii) the processing shall set QC-Status to the value "PROCESS_PASSED"; iii) the processing shall stop the process. g) The processing shall set CHECK_1_SET-OF_QE to the set of all 'QualificationElement' from all 'Qualifications' extensions (see clause 5.5.9.2 of ETSI TS 119 612 [1]) whose 'CriteriaList' element identifies CERT from all SI-at-Date-time elements of the SI-Results tuples (from the process run in PRO-4.4.4-03). h) The processing shall proceed as follows: 1) it shall identify the set of all applicable qualifiers as per the content of the 'Qualifier' descendant elements (see clause 5.5.9.2.3 of ETSI TS 119 612 [1]) of all 'QualificationElement' elements of CHECK_1_SET- OF_QE; 2) in case the qualifier "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForESeal", the qualifier "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCForWSA", and/or combination of the qualifiers "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/NotQualified" and "http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCStatement" is/are found, then: i) the processing shall set CHECK_1 to the value "INDET_QC_For_eSig"; ii) the processing shall add to QC-Sub-Status the value "ERROR_T1_TL_Inconsistency_in_applying_qualifiers"; iii) the processing shall set QC-Status to the value "PROCESS_FAILED"; iv) the processing shall stop the process. i) the processing shall get the information about the presence in CERT of the id-etsi-qcs-QcCompliance statement (see ETSI EN 319 412-5 [3]), the 0.4.0.1456.1.1 (QCP+) ETSI defined certificate policy OID, and/or the 0.4.0.1456.1.2 (QCP) ETSI defined certificate policy OID; j) the processing shall use the applicable qualifiers identified in PRO-4.4.4-33.(h).a to select the appropriate column of Table 5, and shall use the information obtained in PRO-4.4.4-33.(i) to select the appropriate row of Table 5; ETSI ETSI TS 119 615 V1.2.1 (2023-06) 33 Table 5: QC-For-eSig determination under Directive 1999/93/EC [i.7] NOTE 10: Information in row1/column0 means, and corresponds to the case where, the QcCompliance statement is present in CERT. The meaning of the other rows of column0 can be deduced accordingly. Information in row0/column1 means, and corresponds to the case where, none of the qualifiers 'NotQualified' or 'QCStatement' in the 'Qualifications' extensions (denoted Sie:Q in Table 5) applies to CERT. The meaning of the other columns of row0 can be deduced accordingly. k) the processing shall set CHECK_1 to the value found in the selected cell of Table 5; l) the processing shall set QC-Status to the value "PROCESS_PASSED"; m) the processing shall set QC-Results to the set of indications provided in CHECK_1, in CHECK_2, and in CHECK_3. PRO-4.4.4-34: The processing shall run the process described in clause 4.4 of the present document, until either PRO-4.4.4-32 step is completed or PRO-4.4.4-33 step is completed, passing the following inputs to the process: a) CERT; b) the date and time value of the NotBeforeDate field of CERT. PRO-4.4.4-35: If the output QC-Status of the process run in PRO-4.4.4-34 has the value "PROCESS_FAILED", then: a) the processing shall set QC-Status to the value "PROCESS_FAILED"; b) the processing shall add to QC-Sub-Status the values provided by set of values from QC-Status and QC-Sub-Status from the process run in PRO-4.4.4-34; and c) the processing shall stop the process. PRO-4.4.4-36: The processing shall compare the values of QC-Results obtained after the first run of process 4.4 (with Date-time from the input) and after the second run of process 4.4 (with the NotBeforeDate): a) when the two results do not contain the exact same set of indications then: 1) the processing shall set QC-Status to the value "PROCESS_FAILED"; 2) the processing shall add to QC-Sub-Status appropriate values reflecting the problematic comparison(s); and row0 None of Sie:Q NotQualified QCStatement Sie:Q NotQualified Sie:Q QCStatement row1 QcCompliance “QC_For_eSig” “Not_Qualified_For_eSig” “QC_For_eSig” row2 PolicyId QCP (qcp-public) “QC_For_eSig” “Not_Qualified_For_eSig” “QC_For_eSig” row3 PolicyId QCP+ (qcp-public-with-sscd) “QC_For_eSig” “Not_Qualified_For_eSig” “QC_For_eSig” row4 Any combination of QcCompliance, PolicyId QCP, PolicyId QCP+ “QC_For_eSig” “Not_Qualified_For_eSig” “QC_For_eSig” row5 None “Not_Qualified_For_eSig” “Not_Qualified_For_eSig” “QC_For_eSig” column0 column1 column2 column3 Sti = CA/QC ETSI ETSI TS 119 615 V1.2.1 (2023-06) 34 3) the processing shall stop the process. NOTE 11: When QC-Results include either "QC_For_eSig", or "QC_For_eSeal" or "QWAC", then CERT can be considered, at Date-time, respectively as an EU qualified certificate for electronic signatures, an EU qualified certificate for electronic seals, or an EU qualified certificate for website authentication. b) when the QC-Sub-Status returned by the process run in PRO-4.4.4-34 contains one or more "warning" indications: 1) the processing shall set QC-Status to the value "PROCESS_PASSED_WITH_WARNING"; 2) the processing shall add to QC-Sub-Status the values provided by the set of values from QC-Status and QC-Sub-Status from the process run in PRO-4.4.4-34.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.5 QSCD determination
| |
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.5.1 Description
|
The procedure specified in clause 4.5 allows determining whether an EU qualified certificate is confirmed by the applicable EUMS trusted list to have had its private key residing in a QSCD at a specific date and time. NOTE: As the EUMS trusted list provides such information only for qualified certificates of a certain type, the process will first determine whether or not the certificate is a qualified certificate and for which type.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.5.2 Inputs
|
Name Description of inputs CERT X.509 certificate for which the information is to be obtained (e.g. a ds:X509Certificate value of a ds:KeyInfo of the ds:Signature) Date-time Date and time indication as specified in clause 5.1.3 of ETSI TS 119 612 [1].
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.5.3 Outputs
|
Name Description QSCD-Results An indication on whether CERT had its private key residing in a QSCD in accordance with the trusted lists, through one of the following values: a) "QSCD_YES" to indicate that CERT had its private key residing in a QSCD at Date-time according to the EUMS trusted lists; b) "QSCD_NO" to indicate that CERT did not have its private key residing in a QSCD at Date-time according to the EUMS trusted lists; c) "QSCD_INDETERMINATE" to indicate that the EUMS trusted lists cannot be used to confirm whether CERT had its private key residing in a QSCD at Date-time; d) Void. QSCD-Status The status indication of the process. QSCD-Sub-Status A list of indications supplementing QSCD-Status indication. OUT-4.5.3-01: All above listed output variables shall be initialized to void.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.5.4 Processing
|
PRO-4.5.4-01: The processing shall run the process described in clause 4.4 of the present document, passing the following inputs to the process: a) CERT; b) Date-time. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 35 PRO-4.5.4-02: If the output QC-Status of the process run in PRO-4.5.4-01 has the value "PROCESS_FAILED", then: a) the processing shall set QSCD-Status to the value "PROCESS_FAILED"; b) the processing shall set QSCD-Sub-Status to the values provided by set of values from QC-Status and QC-Sub-Status; and c) the processing shall stop the process. PRO-4.5.4-03: When Date-time is strictly before 2016-06-30T22:00:00Z: a) If QC_Results includes the value "QC_For_eSig", then considering CHECK_1_SET-OF_QE as part of the outputs of the process run in PRO-4.5.4-01: 1) the processing shall identify the set of all applicable qualifiers as per the content of the 'Qualifier' descendant elements (see clause 5.5.9.2.3 of ETSI TS 119 612 [1]) of all 'QualificationElement' elements of CHECK_1_SET-OF_QE, and shall check whether the following qualifiers are present among them: 'QCWithSSCD' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCWithSSCD"), 'QCNoSSCD' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCNoSSCD"), and 'QCSSCDStatusAsInCert' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCSSCDStatusAsInCert"); 2) in case one of the following combinations is found, the processing shall set QSCD-Results to the value "QSCD_INDETERMINATE", shall set QSCD-Status to the value "PROCESS_PASSED_WITH_WARNING", shall add to QSCD-Sub-Status the value "WARNING_Inconsistency_in_applying_qualifiers_for_SSCD_status", and shall stop the process: i) 'QCWithSSCD' and 'QCNoSSCD'; ii) 'QCSSCDStatusAsInCert' and 'QCWithSSCD'; iii) 'QCSSCDStatusAsInCert' and 'QCNoSSCD'. 3) the processing shall identify the presence of the 0.4.0.1456.1.1 (QCP+) ETSI defined certificate policy OID in the CertificatePolicies extension and the presence of the QcSSCD statement in the QCStatements extension (see ETSI EN 319 412-5 [3]) in CERT; 4) the processing shall use the information obtained in above point PRO-4.5.4-03.(a).a. to select the appropriate column of Table 6, and shall use the information obtained in above point PRO-4.5.4-03.(a).c. to select the appropriate row of Table 6, and shall set QSCD-Results to the value found in the selected cell; Table 6: QSCD status check (Directive regime) 5) the processing shall set QSCD-Status to the value "PROCESS_PASSED"; and 6) the processing shall stop the process. b) the processing shall set QSCD-Results to the value "QSCD_INDETERMINATE"; Sie:Q CERT QcSSCD present and/or PolicyId QCP+ (qcp-public-with-sscd) present QSCD_YES QSCD_YES QSCD_NO QcSSCD not present and PolicyId QCP+ (qcp-public-with-sscd) not present QSCD_YES QSCD_NO QSCD_NO "QCWithSSCD" "QCSSCDStatusAsInCert" or no indication “QCNoSSCD” ETSI ETSI TS 119 615 V1.2.1 (2023-06) 36 c) the processing shall set QSCD-Status to the value "PROCESS_PASSED"; and d) the processing shall stop the process. PRO-4.5.4-04: If QC_Results includes the value "QC_For_eSig" or "QC_For_eSeal", then considering respectively CHECK_1_SET-OF_QE or CHECK_2_SET-OF_QE as part of the outputs of the process run in PRO-4.5.4-01: a) the processing shall identify the set of all applicable qualifiers as per the content of the 'Qualifier' descendant elements (see clause 5.5.9.2.3 of ETSI TS 119 612 [1]) of all 'QualificationElement' elements of the considered output variable, and shall check whether the following qualifiers are present among them: 'QCWithQSCD' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCWithQSCD"), 'QCNoQSCD' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCNoQSCD"), 'QCQSCDStatusAsInCert' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCQSCDStatusAsInCert"), and 'QCQSCDManagedOnBehalf' ("http://uri.etsi.org/TrstSvc/TrustedList/SvcInfoExt/QCQSCDManagedOnBehalf"); b) in case one of the applicable qualifiers is not known by the processing, then: 1) if the 'Qualifications' extension from which this qualifier was retrieved is marked "critical", the processing shall set QSCD-Status to the value "PROCESS_FAILED", shall add to QSCD-Sub-Status the value "ERROR_Unknown_critical_qualifiers_for_QSCD_status", and shall stop the process; 2) else the processing shall add to QSCD-Sub-Status the value "WARNING_Unknown_qualifiers_for_QSCD_status"; NOTE: The set of qualifiers that are known by the processing is implementation dependent. In the context of EU qualified certificates, the set of qualifiers that can be used when the type of the service to which it applies is "CA/QC" is specified in clause 5.5.9.2.3 of ETSI TS 119 612 [1]. c) in case one of the following qualifier or combinations is found, the processing shall set QSCD-Results to the value "QSCD_INDETERMINATE", shall set QSCD-Status to the value "PROCESS_PASSED_WITH_WARNING", shall add to QSCD-Sub-Status the value "WARNING_Inconsistency_in_applying_qualifiers_for_QSCD_status", and shall stop the process: 1) 'QCWithSSCD' and absence of 'QCWithQSCD'; 2) 'QCNoSSCD' and absence of 'QCNoQSCD'; 3) 'QCWithQSCD' and 'QCNoQSCD'; 4) 'QCQSCDManagedOnBehalf' and 'QCNoQSCD'; 5) 'QCQSCDStatusAsInCert' and any one of the other qualifiers listed in PRO-4.5.4-04.(a). d) the processing shall identify the presence of the QcSSCD statement in the QCStatements extension (see ETSI EN 319 412-5 [3]) in CERT; e) the processing shall use the information obtained in above point PRO-4.5.4-04.(a) to select the appropriate column of Table 7, shall use the information obtained in above point PRO-4.5.4-04.(c) to select the appropriate row of Table 7, and shall set QSCD-Results to the value found in the selected cell. Table 7: QSCD status check (Regulation regime) Sie:Q CERT QcSSCD present QSCD_YES QSCD_YES QSCD_NO QcSSCD not present QSCD_YES QSCD_NO QSCD_NO "QCWithQSCD" or "QCQSCDManagedOnBehalf" "QCQSCDStatusAsInCert" or no indication "QCNoQSCD" ETSI ETSI TS 119 615 V1.2.1 (2023-06) 37 f) the processing shall set QSCD-Status to the value "PROCESS_PASSED"; and g) the processing shall stop the process. PRO-4.5.4-05: If QC_Results does not include the value "QC_For_eSig" nor the value "QC_For_eSeal" then: a) the processing shall set QSCD-Results to the value "QSCD_INDETERMINATE"; b) the processing shall set QSCD-Status to the value "PROCESS_PASSED"; and c) the processing shall stop the process.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.6 EU qualified time stamp determination
| |
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.6.1 Description
|
The procedure specified in clause 4.6 allows determining whether a time stamp token is confirmed by the applicable EUMS trusted list to have been an EU qualified time stamp at its generation time, provided that the timestamp is valid.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.6.2 Inputs
|
Name Description of inputs TST The time stamp token for which the information is to be obtained. Date-time Date and time indication as specified in clause 5.1.3 of ETSI TS 119 612 [1].
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.6.3 Outputs
|
Name Description QTST-Results An indication of the EU qualified status of TST through one of the following values: a) "Not_Qualified" to indicate that TST is not an EU qualified time stamp according to the EUMS trusted list from CC at Date-time; b) "Qualified" to indicate that TST is an EU qualified time stamp according to the EUMS trusted list from CC at Date-time; c) "Indeterminate" to indicate that the EUMS trusted list from CC cannot be used to confirm that TST is an EU qualified time stamp at Date-time. QTST-Status The status indication of the process. QTST-Sub-Status A list of indications supplementing QTST-Status indication. CC The country code of the EUMS trusted list being used to obtain the above listed three other outputs. OUT-4.6.3-01: All above listed output variables shall be initialized to void.
|
b1b8bc5f0b45e4938939217539aab50d
|
119 615
|
4.6.4 Processing
|
PRO-4.6.4-01: Void. PRO-4.6.4-02: If Date-time is before "2016-06-30T22:00:00Z", then: a) the processing shall set QTST-Status to the value "PROCESS_PASSED"; b) the processing shall set QTST-Results to the value "Not_Qualified"; and c) the processing shall stop the process. PRO-4.6.4-03: The processing shall set CERT to the X.509 certificate supporting the validation of the digital signature on TST. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 38 PRO-4.6.4-04: The processing shall set CC to the country code value of the countryName attribute of the subjectName field of the certificate provided in CERT, in capital letters in accordance with the ISO 3166-1 [2] Alpha 2 country code, with, when applicable: a) the country code value "GB" being converted to "UK"; b) the country code value "GR" being converted to "EL". PRO-4.6.4-05: The processing shall set TLS-Sti to the value "http://uri.etsi.org/TrstSvc/Svctype/TSA/QTST" as specified in clause 5.5.1.1 of ETSI TS 119 612 [1]. PRO-4.6.4-06: The processing shall run the process described in clause 4.3 of the present document, passing the following inputs to the process: a) CERT; b) TLS-Sti; c) Date-time; d) CC. PRO-4.6.4-07: If the output SI-Status of the process run in PRO-4.6.4-06 has the value "PROCESS_FAILED", then: a) the processing shall set QTST-Status to the value "PROCESS_FAILED"; b) the processing shall set QTST-Results to the value "Indeterminate"; c) the processing shall set QTST-Sub-Status to the set of values from SI-Status and SI-Sub-Status; and d) the processing shall stop the process. PRO-4.6.4-08: If the output SI-Results of the process run in PRO-4.6.4-06 is void, then: a) the processing shall set QTST-Status to the value "PROCESS_PASSED"; b) the processing shall set QTST-Results to the value "Not_Qualified"; and c) the processing shall stop the process. PRO-4.6.4-09: If the output SI-Results of the process run in PRO-4.6.4-06 includes more than one tuple for which the SI-at-Date-time respective parts include different values for their respective 'Service current status' or 'Service previous status' field, then: a) the processing shall set QTST-Status to the value "PROCESS_FAILED"; b) the processing shall set QTST-Results to the value "Indeterminate"; c) the processing shall set QTST-Sub-Status to the value "ERROR_INCONSISTENCY_IN_TL_ON_TST_STATUS"; and d) the processing shall stop the process. PRO-4.6.4-10: If the output SI-Results of the process run in PRO-4.6.4-06 includes more than one tuple for which the SI-at-Date-time respective parts include different public key values for their 'Service digital identifier' field (see clause 5.5.3 of ETSI TS 119 612 [1]), then the processing shall add to QTST-Sub-Status the value "WARNING_DUPLICATION_OF_SERVICE_INFORMATION_IN_TL_REGARDING_TST". PRO-4.6.4-11: If the organizationName attribute of the subjectName field of the certificate provided in CERT is not matching one of the values of TSP-Name or TSP-Trade-Name of the output SI-Results of the process run in PRO-4.6.4-06, then: a) the processing shall set QTST-Status to the value "PROCESS_FAILED"; ETSI ETSI TS 119 615 V1.2.1 (2023-06) 39 b) the processing shall set QTST-Results to the value "Indeterminate"; c) the processing shall set QTST-Sub-Status to the value "ERROR_TSP_NAME_INCONSISTENCY_BETWEEN_CERT_AND_TL"; and d) the processing shall stop the process. PRO-4.6.4-12: If the 'Service current status' or 'Service previous status' field of the SI-at-Date-time part(s) of the output SI-Results of the process run in PRO-4.6.4-06 has the value "http://uri.etsi.org/TrstSvc/TrustedList/Svcstatus/granted": a) then: 1) the processing shall set QTST-Status to the value "PROCESS_PASSED"; 2) the processing shall set QTST-Results to the value "Qualified". b) else: 1) the processing shall set QTST-Status to the value "PROCESS_PASSED"; 2) the processing shall set QTST-Results to the value "Not_Qualified". PRO-4.6.4-13: The processing shall run the process described in clause 4.6 of the present document, until PRO-4.6.4-12 step is completed, passing the following inputs to the process: a) TST; b) the date and time value as specified in TST and expressed as specified in clause 5.1.3 of ETSI TS 119 612 [1]. EXAMPLE: This date and time indication can be genTime from TSTInfo as specified in IETF RFC 3161 [i.6]. PRO-4.4.4-14: If the output QTST-Status of the process run in PRO-4.6.4-13 has the value "PROCESS_FAILED", then: a) the processing shall set QTST-Status to the value "PROCESS_FAILED"; b) the processing shall add to QTST-Sub-Status the values provided by set of values from QTST-Status and QTST-Sub-Status from the process run in PRO-4.6.4-13; and c) the processing shall stop the process. PRO-4.6.4-15: The processing shall compare the values of QTST-Results obtained after the first run of process 4.6 (with Date-time from the input) and after the second run of process 4.6 (with the date and time value as specified in TST): a) when the two results do not contain the exact same indication then: 1) the processing shall set QTST-Status to the value "PROCESS_FAILED"; 2) the processing shall add to QTST-Sub-Status appropriate values reflecting the problematic comparison(s); and 3) the processing shall stop the process. ETSI ETSI TS 119 615 V1.2.1 (2023-06) 40
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.