hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.2 Functional goals | Different scenarios for preservation services can be distinguished, each having specific security and policy requirements. A preservation service can provide: 1) the provision of proofs of existence over long periods of time of general data whether this data is signed or not; 2) the preservation over long periods of ti... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.3 Preservation service applicable documentation | |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.3.1 Preservation service practice statement | The PSP develops, implements, enforces, and updates a preservation practice statements which is a trust service practice statement such as defined in ETSI EN 319 401 [1], instantiated for a preservation service. See clause 6.1. The preservation service practice statements describe how the PSP operates its service and i... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.3.2 Preservation service policy | A preservation service policy describes what is offered and can contain diverse information beyond the scope of the present document to indicate the applicability of the service. The recipients of the service policy can be auditors, the subscribers and the relying parties. It contains the rules to follow in providing t... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.3.3 Preservation schemes and preservation profiles | A preservation scheme is a generic set of procedures and rules pertinent to a preservation storage model and one or more preservation goals which outlines how preservation evidences are created and validated. It can be supported by one or more preservation profiles. A preservation profile identifies a set of implementa... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.3.4 Preservation evidence policy | The preservation evidence policy is referenced by the preservation profile. It contains all the information about how preservation evidences are created and how they can be validated. NOTE: See OVR-6.4-04 c)-a. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.3.5 Signature validation policy | In case of preservation of digital signatures where the preservation service collects the validation data needed to determine the status of the digital signature, the signature validation policy is referenced in the preservation profile. In this case, the validation policy describes the rules followed to obtain the val... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.4 Expected evidence duration | The expected evidence duration applies for a preservation service with temporary storage or without storage. It is a duration during which or a date until which, the preservation service expects that a preservation evidence can be used to achieve the preservation goal. This means that the preservation evidence can stil... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 4.5 Preservation period | In the case of a preservation service with storage [WST], the preservation period is the duration during which the preservation service preserves the preservation objects (POs). The POs may consist of the submitted data objects (SubDO) and POs derived from the submitted data objects by augmentation or by building a POC... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 5 Risk assessment | OVR-5-01: The requirements specified in ETSI EN 319 401 [1], clause 5 shall apply. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 6 Policies and practices | |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 6.1 Preservation service practice statement | OVR-6.1-01: The requirements specified in ETSI EN 319 401 [1], clause 6.1 shall apply. In addition, the following particular requirements apply: OVR-6.1-02: The preservation service provider (PSP) should list or make reference to (e.g. through OIDs), and briefly describe the supported preservation service policies in i... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 6.2 Terms and Conditions | OVR-6.2-01: The requirements specified in ETSI EN 319 401 [1], clause 6.2 shall apply. In addition, the following particular requirements apply for the PSP: OVR-6.2-02: The PSP shall list in the terms and conditions all the preservation service policies it supports. OVR-6.2-03: The PSP shall state where to find informa... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 6.3 Information security policy | OVR-6.3-01: The requirements specified in ETSI EN 319 401 [1], clause 6.3 shall apply. ETSI ETSI TS 119 511 V1.1.1 (2019-06) 23 |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 6.4 Preservation profiles | OVR-6.4-01: A preservation service shall support at least one preservation profile. OVR-6.4-02: A preservation service may support more than one preservation profile. OVR-6.4-03: A preservation profile shall be uniquely identified. OVR-6.4-04: A preservation profile: a) Shall contain the identifier which uniquely ident... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 6.5 Preservation evidence policy | OVR-6.5-01: The preservation evidence policy which is referenced by the preservation profile (see OVR-6.4-04) may be in human readable form. OVR-6.5-02 [CONDITIONAL]: If there are different formats or languages of the preservation evidence policy, the PSP shall state which version takes precedence. OVR-6.5-03: The pres... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 6.6 Signature validation policy | OVR-6.6-01: The signature validation policy contained in the preservation profile (see OVR-6.4-04) may be in human readable form. OVR-6.6-02 [CONDITIONAL]: If there are different formats or languages of the signature validation policy, the PSP shall state which version takes precedence. OVR-6.6-03 [CONDITIONAL]: If pre... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 6.7 Subscriber agreement | OVR-6.7-01: The PSP shall provide a subscriber agreement which shall include an acceptance of the terms and conditions. OVR-6.7-02 [CONDITIONAL]: If the preservation service provides a notification protocol, the PSP shall state in the subscriber agreement whether and how the subscriber would like to be notified. OVR-6.... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7 PSP management and operation | |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.1 Internal organization | OVR-7.1-01: The requirements specified in ETSI EN 319 401 [1], clause 7.1 shall apply. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.2 Human resources | OVR-7.2-01: The requirements specified in ETSI EN 319 401 [1], clause 7.2 shall apply. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.3 Asset management | OVR-7.3-01: The requirements specified in ETSI EN 319 401 [1], clause 7.3 shall apply. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.4 Access control | OVR-7.4-01: The requirements specified in ETSI EN 319 401 [1], clause 7.4 shall apply. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.5 Cryptographic controls | OVR-7.5-01: The requirements specified in ETSI EN 319 401 [1], clause 7.5 shall apply. ETSI ETSI TS 119 511 V1.1.1 (2019-06) 26 In addition, the following particular requirements apply for the management of the keys used to generate and to validate the evidences: OVR-7.5-02: The PSP shall insure that the time-stamps us... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.6 Physical and environmental security | OVR-7.6-01: The requirements specified in ETSI EN 319 401 [1], clause 7.6 shall apply. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.7 Operation security | OVR-7.7-01: The requirements specified in ETSI EN 319 401 [1], clause 7.7 shall apply. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.8 Network security | OVR-7.8-01: The requirements specified in ETSI EN 319 401 [1], clause 7.8 shall apply. OVR-7.8-02 [WST]: The preservation service shall be integrated in the IT environment implemented in such a way that all storage access by the preservation client changing the content of the storage shall only be done by the preservat... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.9 Incident management | OVR-7.9-01: The requirements specified in ETSI EN 319 401 [1], clause 7.9 shall apply. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.10 Collection of evidence | OVR-7.10-01: The requirements specified in ETSI EN 319 401 [1], clause 7.10 shall apply. OVR-7.10-02: The preservation service shall implement event logs to establish information needed for later proofs. ETSI ETSI TS 119 511 V1.1.1 (2019-06) 27 |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.11 Business continuity management | OVR-7.11-01: The requirements specified in ETSI EN 319 401 [1], clause 7.11 shall apply. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.12 TSP termination and termination plans | OVR-7.12-01: The requirements specified in ETSI EN 319 401 [1], clause 7.12 shall apply. In addition, the following particular requirements apply: OVR-7.12-02 [WST]: The termination plan shall include what happens with the stored POs at the termination of the preservation service. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.13 Compliance | OVR-7.13-01: The requirements specified in ETSI EN 319 401 [1], clause 7.13 shall apply. |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.14 Cryptographic monitoring | OVR-7.14-01: For every supported active preservation profile, the TSP shall monitor the strength of every cryptographic algorithm that was used in connection with this profile. In case, one of the used algorithms or parameters is thought to become less secure or the validity of a relevant certificate is going to expire... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.15 Augmentation of preservation evidences | OVR-7.15-01 [WST]: During the preservation period, the preservation service shall make sure that the preservation evidence can be used to achieve the corresponding preservation goal. OVR-7.15-02 [WTS]: During the preservation evidence retention period, the preservation service shall make sure that the preservation evid... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 7.16 Export-import package | OVR-7.16-01 [WST]: The PSP shall allow the preservation client or another authorized preservation service to request the export-import package(s), containing the preserved data, the evidences and all information needed to validate the evidences. NOTE 1: The export-import package(s) can be used to move the preserved dat... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 8 Operational and notification protocols | |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 8.1 Preservation protocol | PRP-8.1-01: The communication channel between the preservation client and the PSP shall be secured; i.e. the PSP shall offer a way to be authenticated by the client and the confidentiality of the data shall be ensured. PRP-8.1-02: The preservation protocol as defined in ETSI TS 119 512 [i.13] should be used. PRP-8.1-03... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 8.2 Notification protocol | OVR-8.2-01: The preservation service may define a notification protocol in order to be able to send messages or information to its subscribers. NOTE: The way how this notification is done is out of the scope of this policy. ETSI ETSI TS 119 511 V1.1.1 (2019-06) 30 OVR-8.2-02 [CONDITONAL]: When the preservation service ... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 9 Preservation process | |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 9.1 Storage of preserved data and evidences | OVR-9.1-01 [WOS] [WTS]: A preservation service without storage or with temporary storage should not store the data to be preserved after the evidence has been created. OVR-9.1-02 [WOS] [WTS][CONDITIONAL]: A preservation service without storage or with temporary storage which stores the data to be preserved after the ev... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 9.2 Preservation evidences | OVR-9.2-01 [CONDITIONAL]: If the preservation service uses a time-stamp token it shall conform to IETF RFC 3161 [i.18] and updated by IETF RFC 5816 [i.22]. OVR-9.2-02 [CONDITIONAL]: If the preservation service uses a time-stamp token it should conform to the time- stamping protocol and time-stamp token profiles as defi... |
4968c07ddf31b0134f1264dc69e760bd | 119 511 | 9.3 Preservation of digital signatures | OVR-9.3-01 [PDS][PDS+PGD] [CONDITIONAL]: If the validation data is not submitted by the preservation client, the preservation service shall make its best efforts to collect and verify the validation data according to the signature validation policy supported by the preservation profile (see clause 6.6). OVR-9.3-02 [PDS... |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 1 Scope | The present document describes the root Uniform Resource Identifier (URI) http://uri.etsi.org/ades and sub branches that allow to define URI applicable for more than one AdES signature format and/or the ASiC signature container. The present document describes how to define URIs to reference a specific version and/speci... |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 2 References | |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 3 Definition of terms, symbols and abbreviations | |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.3] and the following apply: AdES (digital) signature: digital signature that is either a CAdES signature, a PAdES signature, a XAdES signature, or a JAdES signature JAdES signature: JSON Web Signature NOTE: As defined in ETSI TS 119 182-1 [... |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 3.2 Symbols | Void. |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TR 119 001 [i.3] and the following apply: CID Commission Implementation Decision URI Uniform Resource Identifier ETSI ETSI TS 119 192 V1.2.1 (2023-02) 7 |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 4 URI namespaces | |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 4.1 The main branch | Any URI under the root http://uri.etsi.org/ades shall be used to describe URIs applicable for all types of AdES signatures. |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 4.2 URIs used to describe signature levels | 4.2.1 Baseline signature and container levels as defined in the standardization framework for signatures ETSI TR 119 000 A URI describing a baseline signature level which is defined in ETSI EN 319 122-1 [5] (CAdES), ETSI EN 319 132-1 [8] (XAdES) and ETSI EN 319 142-1 [11] (PAdES) or a baseline container level which is ... |
1f0eea917a618045ce22f119edbd92bc | 119 192 | 4.3 How to reference specific signature format version | To reference a specific version of a signature format or an ASiC container the URI shall have the following structure: http://uri.etsi.org/<number_of_the_document >/<specific_version> The number_of_the_document shall be the five-digit number obtained by removing the first digit of the ETSI document number, and any part... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 1 Scope | The present document: 1) Specifies a JSON [1] format for AdES signatures (JAdES signatures hereinafter) built on JSON Web Signatures (JWS hereinafter) as specified in IETF RFC 7515 [2]. For this, the present document: - Extends the JSON Web Signatures specified in IETF RFC 7515 [2] by defining an additional set of JSON... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 2 References | |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TR 119 001 [i.5], IETF RFC 7515 [2] and the following apply: JAdES signature: JSON Web Signature NOTE: As specified in IETF RFC 7515 [2], or other parts of this multi-part deliverable. JWS Signature Value: digital signature cryptographic value calculated... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 3.2 Symbols | Void. |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASCII American Standard Code For Information Interchange ASN.1 Abstract Syntax Notation 1 CA Certification Authority CRL Certificate Revocation List FIPS Federal Information Processing Standards HTTP Hyper Text Transfer Protocol IETF Internet ... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 3.4 Terminology | The present document adopts, wherever it is possible the same terminology as the terminology used in IETF RFC 7515 [2] and in IETF RFC 8259 [1]. Therefore, within the present document, the term "JSON Web Signature" shall denote the JSON structure specified in IETF RFC 7515 [2]. The present document uses the term "JSON ... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 4 General Requirements | The JAdES components defined in the present document shall be carried within the JOSE header as specified in IETF RFC 7515 [2]. All the JAdES signed header parameters specified in clause 5.2 of the present document, as well as: cty, kid, crit, and x5u header parameters specified in IETF RFC 7515 [2] and further profile... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5 Header parameters semantics and syntax | 5.1 Use of header parameters defined in IETF RFC 7515 and IETF RFC 7797 |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.1.1 Introduction | This clause defines additional requirements for the use of some of header parameters specified in IETF RFC 7515 [2]. JAdES signatures may incorporate any of the header parameters specified in IETF RFC 7515 [2] and IETF RFC 7797 [14]. NOTE: Clause 6.3 also specifies requirements (mainly of presence and cardinality), for... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.1.2 The alg (X.509 URL) header parameter | Semantics The alg header parameter shall be a signed header parameter that qualifies the signature. The alg header parameter shall have the semantics specified in IETF RFC 7515 [2], clause 4.1.1. Syntax The alg header parameter shall have the syntax specified in IETF RFC 7515 [2], clause 4.1.1. Its value should be one ... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.1.3 The cty (content type) header parameter | Semantics The cty header parameter shall be a signed header parameter that qualifies the JWS Payload. The cty header parameter shall have the semantics specified in IETF RFC 7515 [2], clause 4.1.10. The cty header parameter should not be present if the sigD header parameter, specified in clause 5.2.8 of the present doc... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.1.4 The kid (key identifier) header parameter | Semantics The kid header parameter shall be a signed header parameter that qualifies the signature. The kid header parameter shall have the semantics specified in IETF RFC 7515 [2], clause 4.1.4. ETSI ETSI TS 119 182-1 V1.1.1 (2021-03) 14 The content of kid header parameter shall be the base64 (IETF RFC 4648 [12]) enco... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.1.5 The x5u (X.509 URL) header parameter | Semantics The x5u header parameter shall be a signed header parameter that qualifies the signature. The x5u header parameter shall have the semantics specified in IETF RFC 7515 [2], clause 4.1.5. The x5u member shall be used as a hint, as implementations can have alternative ways for retrieving the referenced certifica... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.1.6 The x5t (X.509 Certificate SHA-1 Thumbprint) header parameter | JAdES signatures shall not contain the x5t header parameter specified in clause 4.1.7 of IETF RFC 7515 [2]. 5.1.7 The x5t#S256 (X.509 Certificate SHA-256 Thumbprint) header parameter Semantics The x5t#S256 shall be a signed header parameter that qualifies the signature. The x5t#S256 header parameter shall have the sema... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.1.8 The x5c (X.509 Certificate Chain) header parameter | Semantics The x5c header parameter shall be a signed header parameter. The x5c header parameter shall have the semantics specified in IETF RFC 7515 [2], clause 4.1.6. Syntax The x5c header parameter shall have the syntax specified in IETF RFC 7515 [2], clause 4.1.6. ETSI ETSI TS 119 182-1 V1.1.1 (2021-03) 15 |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.1.9 The crit (critical) header parameter | Semantics The crit header parameter shall be a signed header parameter that qualifies the signature. The crit header parameter shall have the semantics specified in IETF RFC 7515 [2], clause 4.1.11. The JAdES signatures incorporating any signed header parameter specified in clause 5.2 shall incorporate the signed crit ... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.1.10 The b64 header parameter | Semantics The b64 header parameter shall be a signed header parameter. The b64 header parameter shall have the semantics specified in IETF RFC 7797 [14], clause 3. Syntax The b64 header parameter shall have the syntax specified in IETF RFC 7797 [14], clause 3. If the sigD header parameter is present with its member set... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2 New signed header parameters | |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.1 The sigT (claimed signing time) header parameter | Semantics The sigT header parameter shall be a signed header parameter that qualifies the signature. The sigT header parameter's value shall specify the time at which the signer claims to have performed the signing process. Syntax The sigT header parameter shall be defined as in the JSON Schema file whose location is d... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.2 Header parameters for certificate references | |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.2.1 Introduction | The present clause defines two new signed parameters namely, the x5t#o, which extends the semantics of x5t#S256 for allowing different digest algorithms than the SHA256, and the sigX5ts, which contains references to several certificates within the certification path, including one reference to the signing certificate, ... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.2.2 The x5t#o (X509 certificate digest) header parameter | Semantics The x5t#o header parameter shall be a signed header parameter that qualifies the signature. The x5t#o header parameter shall contain an identifier of a digest algorithm different than the identifier of SHA-256, and the digest value of the referenced certificate. NOTE 1: For instance, the signature validation ... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.2.3 The sigX5ts (X509 certificates digests) header parameter | Semantics The sigX5ts header parameter shall be a signed header parameter that qualifies the signature. The sigX5ts header parameter shall contain several references of certificates within the certification path of the signing certificate, each one formed by the identifier of a digest algorithm and the digest value of ... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.3 The srCms (signer commitments) header parameter | Semantics The srCms header parameter shall be a signed header parameter that qualifies JWS Payload. The srCms header parameter shall indicate the commitment made by the signer when signing. The srCms header parameter shall express the commitment type with a URI. The srCms header parameter may contain a sequence of qual... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.4 The sigPl (signature production place) header parameter | Semantics The sigPl header parameter shall be a signed header parameter that qualifies the signer. The sigPl header parameter shall specify an address associated with the signer at a particular geographical (e.g. city) location. Syntax This header parameter shall be carried in the JWS Protected Header. The sigPl header... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.5 The srAts (signer attributes) header parameter | Semantics The srAts header parameter shall be a signed header parameter that qualifies the signer. The srAts header parameter shall encapsulate signer attributes (e.g. role). This header parameter may encapsulate the following types of attributes: • attributes claimed by the signer; • attributes certified in attribute ... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.6 The adoTst (signed data time-stamp) header parameter | Semantics The adoTst header parameter shall be a signed header parameter that qualifies the JWS Payload. The adoTst header parameter shall encapsulate one or more electronic time-stamps, generated before the signature production, whose message imprint computation input shall be the JWS Payload of the JAdES signature. S... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.7 The sigPId (signature policy identifier) header parameter | |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.7.1 Semantics and syntax | Semantics The sigPId header parameter shall be a signed header parameter qualifying the signature. The sigPId header parameter shall contain either an explicit identifier of a signature policy or an indication that there is an implied signature policy that the relying party should be aware of. NOTE: ETSI TS 119 172-1 [... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.7.2 Signature policy qualifiers | Semantics This clause specifies the following three qualifiers for the signature policy: • A URL where a copy of the signature policy document can be obtained (spURI choice). • A user notice that should be displayed when the signature is validated (spUserNotice choice). • An identifier of the technical specification th... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.8 The sigD header parameter | |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.8.1 Semantics and Syntax | Semantics The sigD header parameter shall be a signed header parameter. The sigD header parameter shall not appear in JAdES signatures whose JWS Payload is attached. The sigD header parameter may appear in JAdES signatures whose JWS Payload is detached. A JAdES signature shall have at most one sigD header parameter. Th... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.8.2 Mechanism HttpHeaders | The URL identifying this referencing mechanism shall be "http://uri.etsi.org/19182/HttpHeaders". If this mechanism is used, then the b64 header parameter shall be present and set to "false". For this referencing mechanism, neither hashV, neither hashM member, nor ctys shall be present. Using this referencing mechanism,... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.8.3 Mechanisms supported by URI references | |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.8.3.1 General requirements | This clause specifies two mechanisms that use URIs for referencing the data objects contributing to build the JWS Payload. For these referencing mechanisms, the contents of the pars member shall be an array of strings. Each string shall be an URI, appertaining to the group of URIs that can be classified as locators acc... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.8.3.2 Mechanism ObjectIdByURI | The URI identifying this referencing mechanism shall be "http://uri.etsi.org/19182/ObjectIdByURI". For this referencing mechanism, neither hashV , nor hashM shall be present. Member ctys may be present. The semantics and syntax of ctys shall be as specified in clause 5.2.8.1 of the present document. The stream of octet... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.2.8.3.3 Mechanism ObjectIdByURIHash | The URL identifying this referencing mechanism shall be "http://uri.etsi.org/19182/ObjectIdByURIHash". For this referencing mechanism, the hashV, and the hashM members shall be present. Member ctys may be present. The semantics and syntax of hashM, hashV ,and ctys shall be as specified in clause 5.2.8.1 of the present ... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.3 New unsigned header parameter | |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.3.1 The etsiU header parameter | Semantics The etsiU unprotected header parameter shall be a JSON array whose elements contain JSON values that are not signed by the JAdES signature. NOTE 1: The rationale for this is as follows: the computation of certain time-stamp tokens message imprints is performed by digesting the concatenation of sets of unsigne... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.3.2 The cSig (counter signature) JSON object | Semantics The cSig JSON object shall contain one counter signature of the JAdES signature where cSig is incorporated. This counter signature may also be a JAdES signature. Syntax The cSig JSON object contains either a JSON Web Signature or a JAdES signature that signs the JWS Signature Value of the embedding JAdES sign... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.3.3 The sigPSt JSON object | Semantics The sigPSt JSON object shall contain either: • the signature policy document which is referenced in the sigPId JSON object so that the signature policy document can be used for offline and long-term validation; or • a URI referencing a local store where the signature policy document can be retrieved. Syntax T... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.3.4 The sigTst JSON object | Semantics The sigTst JSON object shall encapsulate one or more electronic time-stamps time-stamping the JWS Signature Value. Syntax This JSON object shall be carried in the JWS Unprotected Header. The sigTst JSON object shall be defined as in the JSON Schema file whose location is detailed in clause B.1, and is copied ... |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.3.5 JSON objects for validation data values | |
a6087cb71cc81e5365840ed061a4efb1 | 119 182-1 | 5.3.5.1 The xVals JSON array | Semantics The xVals JSON array: 1) Shall contain the certificate of the trust anchor, if such certificate does exist and if it is not already present within other component of the underlying JSON Web Signature. If this certificate is present within another component of the underlying JSON Web Signature, it should not b... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.