hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.7 EAA issuance | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.7.1 General requirements | 4.2. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 7.1 General requirements | EAA-4.2.7.1-01: The EAA issuance data shall unambiguously identify either the date, or the date and time instant when the EAA was issued. EAA-4.2.7.1-02: An EAA may incorporate the EAA issuance data. EAA-4.2.7.1-03: The incorporation and placement of the EAA issuance data shall depend on the specific EAA implementation... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.7.2 Time indication content | EAA-4.2.7.2-01: A time instant: 1) Shall be expressed as an instant time in Coordinated Universal Time (UTC); 2) Shall include indication of seconds, even when the number of seconds is zero; 3) Shall not include fractions of seconds; and 4) Shall not use local offset from UTC. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.8 EAA validity periods | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.8.1 Introduction | The present clause specifies requirements for the two types of EAA validity periods, namely: the administrative validity period, and the technical validity period. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.8.2 Common requirements for administrative and technical validity periods | EAA-4.2.8.2-01: A validity period shall be expressed by two instant times in Coordinated Universal Time (UTC). EAA-4.2.8.2-02: The content of each instant time shall meet the requirements specified in clause 4.2.7.2 of the present document. EAA-4.2.8.2-03: The incorporation and placement of the information on validity ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.8.3 Specific requirements for the EAA technical validity period | EAA-4.2.8.3-01: An EAA shall incorporate the EAA technical validity period. NOTE 1: This requirement meets the requirement (e) in Annex V of Regulation (EU) 2024/1183 [i.2] for QEAA, which requires the presence of "(e) details of the beginning and end of the attestation's period of validity". NOTE 2: This requirement m... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.8.4 Specific requirements for the EAA administrative validity period | EAA-4.2.8.4-01: An EAA may incorporate the EAA administrative validity period. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.9 Data constraining the usage of EAA | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.9.1 Introduction | The present clause specifies semantics for data providing details on the terms under which the EAA has been issued and may be used by relying parties. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.9.2 EAA audience | EAA-4.2.9.2-01: The EAA audience shall identify the set of relying parties the EAA is intended for. NOTE 1: This restriction is added to the restrictions imposed by any Embedded Disclosure Policy existing for the EAA and the restrictions established for the Relying Parties during their registration. EAA-4.2.9.2-02: An ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.9.3 Signal of one-time use | EAA-4.2.9.3-01: An EAA may incorporate the signal of one-time-use within the EAA. EAA-4.2.9.3-02: The presence of this signal shall indicate that the EAA shall be used only once, and that it shall not be retained for future use. EAA-4.2.9.3-03: Its absence shall indicate that the aforementioned constraint shall not app... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.10 Attributes evidence | EAA-4.2.10-01: The attributes evidence shall contain a set of evidence from the EAA subject (and the attribute subjects when required) that the EAA issuer used for completing the issuance of the EAA. NOTE 1: The attributes evidence can be used by the relying party in asserting whether the EAA issuer met its expectation... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.11 EAA status service | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.11.1 General requirements | EAA-4.2.11.1-01: The EAA status service shall contain details of the services (including its location), that can be used to enquire about the validity status of the EAA. EAA-4.2.11.1-02: An EAA may incorporate the EAA status service. EAA-4.2.11.1-03: An EAA that incorporates the EAA short-lived component (clause 4.2.13... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.11.2 Requirements for EU Qualified EAA (QEAA) | QEAA-4.2.11.2-01: If a QEAA does not contain the EAA short-lived component, it shall include the EAA status service. NOTE: This requirement meets the requirement (i) in Annex V of Regulation (EU) 2024/1183 [i.2] for QEAA, which requires the presence of "(i) the information or location of the services that can be used t... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.12 EAA renewal service | EAA-4.2.12-01: The EAA renewal service shall contain details allowing to request to renew the EAA to a renewal service. EAA-4.2.12-02: An EAA may incorporate EAA renewal service data. EAA-4.2.12-03: The attestation renewal service data: 1) Shall include a URI to the service. 2) May also include an identifier of the typ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.2.13 EAA short-lived | EAA-4.2.13-01: An EAA may contain the EAA short-lived component. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 24 EAA-4.2.13-02: The presence of the EAA short-lived component shall indicate that the validity period of the EAA is so short that it shall not be necessary to check its revocation status. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.3 Attested attributes | EAA-4.3-01: Each attribute within an EAA shall have an attribute identifier, which uniquely and unambiguously identifies the attribute itself within the environment where the EAA is used. EXAMPLE: This can be, for instance, the environment identified in the EAA context, if present, or implicitly known for all the parti... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.4 Attested attributes metadata | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.4.1 Introduction | The present clause specifies the semantics of a set of data that support the disclosure of attested attributes. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.4.2 Support to selective disclosure of attested attributes | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.4.2.1 Introduction | Clause 4.4.2 specifies the semantics of: • The identifier of the selective disclosure schema used in the EAA. This identifier may appear explicitly within the EAA or be implicit (clause 4.4.2.2 of the present document). • The disclosure, which is a structure that contains, among other data, the attested attribute to be... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.4.2.2 Disclosure schema identifier | EAA-4.4.2.2-01: An EAA may incorporate the disclosure schema. EAA-4.4.2.2-02: This disclosure schema identifier: 1) Shall univocally identify the mechanism used within the EAA for making certain attested attributes disclosable. 2) May also contain an identifier or reference to the standard/specification that defines th... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.4.2.3 Disclosure | EAA-4.4.2.3-01: An EAA may have one or more disclosures. EAA-4.4.2.3-02: Each disclosure: 1) Shall contain the disclosed attested attribute. 2) Shall contain additional data that allows to bind one disclosure with a disclosure reference. 3) May include an identifier of its version. EAA-4.4.2.3-03: The incorporation and... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.4.2.4 Disclosure reference | EAA-4.4.2.4-01: Each disclosure reference shall be unambiguously bound to one disclosure. EAA-4.4.2.4-02: Each disclosure reference shall be built in such a way that this binding can be ascertained using a certain algorithm. EAA-4.4.2.4-03: The EAA may include information on the validity of a set of disclosure referenc... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.4.2.5 Disclosure algorithm identifier | EAA-4.4.2.5-01: The disclosure algorithm identifier shall identify the algorithm for ascertaining the binding between a disclosure reference and its bound disclosure. EAA-4.4.2.5-02: An EAA may incorporate the disclosure algorithm identifier. EAA-4.4.2.5-03: The disclosure algorithm identifier: 1) Shall contain an iden... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.5 EAA data for key binding | EAA-4.5-01: An EAA should incorporate a component proving that a certain public key is in possession of the EAA subject. NOTE 1: If this component is present within the EAA, the EAA subject can use the private key corresponding to this public key for signing an EAA presentation. NOTE 2: In some specific cases, the EAA ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.6 EAA digital signature | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.6.1 General requirements | 4. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.1 General requirements | EAA-4.6.1-01: An EAA shall incorporate a digital signature generated by the EAA issuer using its private key. EAA-4.6.1-02: Where the syntax used for the digital signature makes it possible, the digital signature shall be an AdES- B-B digital signature in that syntax. EAA-4.6.1-03: If the EAA includes selective disclos... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 4.6.2 Requirements for EU Qualified EAA (QEAA) | QEAA-4.6.2-01: The QEAA digital signature shall be a qualified electronic signature or a qualified electronic seal. NOTE 1: This requirement meets requirement (g) in Annex V of Regulation (EU) 2024/1183 [i.2] for QEAA, which requires the presence of "(g) the qualified electronic signature or qualified electronic seal o... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5 Implementation of EAA based on SD-JWT VC | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.1 General requirements | Clause 5 subclauses specify a realization of EAA that implements EAA as a JSON Web Signature as specified in IETF RFC 7515 [8], built on IETF SD-JWT VC [3], which further profiles a Selective Disclosure JSON Web Token as specified in IETF SD-JWT draft-ietf-oauth-selective-disclosure-jwt-22 [5]. The EAAs implemented acc... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2 EAA metadata | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.1 EAA specification | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.1.1 Introduction | Clause 6 of IETF SD-JWT VC [3] defines the SD-JWT VC Type Metadata, how it is associated with a specific SD- JWT VC type, and the methods for its retrieval and processing. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.1.2 EAA type | EAA-5.2.1.2-01: A SD-JWT VC EAA shall include the vct claim as specified in IETF SD-JWT VC [3], which shall implement the semantics specified in clause 4.2.1.2 of the present document, and that shall be associated to the SD-JWT VC Type Metadata. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 28 EAA-5.2.1.2-02: The vct claim s... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.1.3 EAA context | The information of the context of a SD-JWT VC EAA can be included in the SD-JWT VC Type Metadata. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.1.4 EAA schema | NOTE: See [i.6], which specifies among other things "a data model for catalogue of attributes, guidance on Attestation Rulebooks, attestation type data models and applicable Application Programming Interface (API) for management of machine-readable attestation schemas". |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.2 EAA category | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.2.1 General requirements | EAA-5.2.2.1-01: SD-JWT VC EAAs issued by EAAs issuers registered in the European Union, which are neither SD- JWT VC QEAAs nor SD-JWT VC PuB-EAAs, shall not include the category claim. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.2.2 Requirements for EU Qualified EAA (QEAA) | QEAA-5.2.2.2-01: An SD-JWT VC QEAA shall include the category claim, which shall implement the semantics specified in clause 4.2.2 of the present document. QEAA-5.2.2.2-02: The value of the category claim in a SD-JWT VC QEAA shall be the URN defined in requirement QEAA-4.2.2.2-02 (urn:etsi:esi:eaa:eu:qualified). 5.2.2.... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.3 EAA identifier | EAA-5.2.3-01: The jti component specified in IETF RFC 7519 [4], clause 4.1.7, shall implement the semantics specified in clause 4.2.3 of the present document. EAA-5.2.3-02: A SD-JWT VC EAA may incorporate the jti component. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.4 EAA issuer identifier | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.4.1 General requirements | Common requirements to both types of EAA Issuer (natural or legal person) EAA-5.2.4.1-01: A SD-JWT VC EAA may include the issuing_authority claim, specified in CIR (EU) 2024/2977 [i.3], table 5 Annex I, containing the name of the SD-JWT VC EAA issuer. EAA-5.2.4.1-02: The issuing_authority claim shall be a JSON String. ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.4.2 Requirements for EU Qualified EAA (QEAA) | QEAA-5.2.4.2-01: A SD-JWT VC QEAA shall include the name of its Issuer either within the issuing_authority claim, or within the qualified certificate supporting its signature. NOTE: The issuing_authority claim is specified in CIR (EU) 2024/2977 [i.3], table 5 Annex I. QEAA-5.2.4.2-02: A SD-JWT VC QEAA shall include the... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.5 EAA and attribute subject identifiers and pseudonyms | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.5.1 The EAA subject identifier | EAA-5.2.5.1-01: The sub claim specified in IETF RFC 7519 [4], clause 4.1.2, and further profiled in clause 3.2.2.2 of IETF SD-JWT VC [3], shall implement the semantics specified in clause 4.2.6.2 of the present document. EAA-5.2.5.1-02: A SD-JWT VC EAA may include the sub claim, or the also_known_as claim, or none of t... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.5.2 The EAA subject pseudonym | EAA-5.2.5.2-01: The also_known_as claim shall implement the semantics specified in clause 4.2.6.3 of the present document. EAA-5.2.5.2-02: The also_known_as claim shall be a JSON String. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.5.3 The attribute subject identifier | EAA-5.2.5.3-01: A SD-JWT VC EAA may contain attributes referring to different entities. EAA-5.2.5.3-02: In a SD-JWT VC EAA each attribute not associated to the EAA subject shall be associated either to an attribute subject identifier or to an attribute subject pseudonym. EAA-5.2.5.3-03: An SD-JWT VC EAA may associate a... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.5.4 The attribute subject pseudonym | EAA-5.2.5.4-01: A SD-JWT VC EAA may associate a set of attributes to the pseudonym of an entity different than the EAA subject using the type specified in clause 5.3 of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.5.5 Requirements for EU Qualified EAA (QEAA) | QEAA-5.2.5.5-01: In a SD-JWT VC QEAA all the attributes shall refer to the EAA subject. 5.2.5.6 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-5.2.5.6-01: In a SD-JWT PuB-EAA all the attributes shall refer to the EAA subject. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.6 EAA issuance | EAA-5.2.6-01: The iat claim, specified in IETF RFC 7519 [4] clause 4.1.6, and further profiled in IETF SD-JWT VC [3] clause 3.2.2.2, shall implement semantics specified in clause 4.2.7 of the present document. EAA-5.2.6-02: A SD-JWT VC EAA may incorporate the iat claim. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 31 NOTE: ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.7 EAA validity periods | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.7.1 Specific requirements for the EAA technical validity period | EAA-5.2.7.1-01: A SD-JWT VC EAA shall include the nbf claim specified in IETF RFC 7519 [4], clause 4.1.5, and further profiled in IETF SD-JWT VC [3], clause 3.2.2.2. EAA-5.2.7.1-02: The nbf claim shall implement the semantics of the first time instant of the SD-JWT VC EAA technical validity period. EAA-5.2.7.1-03: A SD... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.7.2 Specific requirements for the EAA administrative validity period | EAA-5.2.7.2-01: A SD-JWT VC EAA may include the adm_nbf claim specified in IETF RFC 7519 [4], clause 4.1.5, and further profiled in IETF SD-JWT VC [3], clause 3.2.2.2. EAA-5.2.7.2-02: The adm_nbf claim shall implement the semantics of the first time instant of the SD-JWT VC EAA administrative validity period. EAA-5.2.7... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.8 Components constraining the usage of EAA | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.8.1 EAA audience | EAA-5.2.8.1-01: A SD-JWT VC EAA shall not incorporate any component implementing the semantics specified in clause 4.2.9.2 of the present document. NOTE: The restrictions mentioned in clause 4.2.9.2 of the present document can be imposed by Embedded Disclosure Policy existing for the EAA and the restrictions establishe... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.8.2 Signal of one-time use | EAA-5.2.8.2-01: The oneTime claim shall implement the semantics specified in clause 4.2.9.3 of the present document. EAA-5.2.8.2-02: A SD-JWT VC EAA may incorporate the oneTime claim. EAA-5.2.8.2-03: The presence of the oneTime claim shall indicate that the EAA shall be used only once, and that it shall not be retained... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.9 Attributes evidence | EAA-5.2.9-01: A SD-JWT VC EAA may incorporate the evidence claim specified in [31] implementing the semantics specified in clause 4.2.10 of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.10 EAA status service | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.10.1 General requirements | EAA-5.2.10.1-01: The status component shall implement the semantics specified in clause 4.2.11 of the present document. EAA-5.2.10.1-02: A SD-JWT VC EAA may incorporate the status component. EAA-5.2.10.1-03: The status component shall be a JSON Object. EAA-5.2.10.1-04: The status JSON Object shall have the type member.... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.10.2 Requirements for EU Qualified EAA (QEAA) | QEAA-5.2.10.2-01: If a SD-JWT VC QEAA does not contain the shortLived claim, it shall include the EAA status claim. 5.2.10.3 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-5.2.10.3-01: If a SD-JWT VC PuB-EAA does not contain the shortLived claim, it... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.11 EAA renewal service | EAA-5.2.11-01: A SD-JWT VC EAA shall not incorporate any component implementing the semantics specified in clause 4.2.12 of the present document. ETSI ETSI TS 119 472-1 V1.2.1 (2026-02) 33 |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.2.12 EAA short-lived (shortLived) | EAA-5.2.12-01: A SD-JWT VC EAA may incorporate the shortLived claim implementing the semantics specified in clause 4.2.13 of the present document. EAA-5.2.12-02: The shortLived claim shall have the null JSON primitive type. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.3 Attested Attributes | EAA-5.3-01: If disclosure of attributes are required, the SD-JWT VC EAA shall incorporate the corresponding disclosures as specified in clause 5.4.1 of the present document. EAA-5.3-02: For associating a set of attributes to one entity different than the EAA subject, the SD-JWT VC EAA shall include the subAttrs claim. ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.4 Attested Attributes metadata | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.4.1 Support to selective disclosure of attested attributes | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.4.1.1 General requirements | EAA-5.4.1.1-01: A SD-JWT VC EAA shall support the selective disclosure of attributes using components specified in IETF SD-JWT VC [3] and IETF SD-JWT [5]. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.4.1.2 Disclosure schema identifier | EAA-5.4.1.2-01: A SD-JWT VC EAA shall not incorporate any component for identifying the disclosure schema. NOTE: The information about the schema used for implementing selective disclosure of attested attributes is implicit in the media type of the SD-JWT. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.4.1.3 Disclosure | EAA-5.4.1.3-01: A SD-JWT VC EAA shall contain one disclosure for each selectively disclosable attested attribute. EAA-5.4.1.3-02: When a SD-JWT VC EAA is serialized, the disclosures shall be incorporated in the SD-JWT VC EAA as specified in IETF SD-JWT [5]. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.4.1.4 Disclosure reference | EAA-5.4.1.4-01: A SD-JWT VC EAA containing one or more selectively disclosable attested attributes that are JSON Properties (clause 4.2.1 of IETF SD-JWT [5]), shall include the _sd component containing their disclosure digests computed as specified in clause 5.2.4.1 of IETF SD-JWT [5]. ETSI ETSI TS 119 472-1 V1.2.1 (20... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.4.1.5 Disclosure algorithm identifier (_sd_alg) | EAA-5.4.1.5-01: The _sd_alg component, specified in IETF SD-JWT [5], and further profiled in IETF SD-JWT VC [3], shall implement the semantics specified in clause 4.4.2.5 of the present document. EAA-5.4.1.5-02: If the SD-JWT VC EAA contains one or more disclosures, then the _sd_alg component shall be present. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.5 EAA data for key binding | EAA-5.5-01: A SD-JWT VC EAA should incorporate the cnf claim as specified in IETF SD-JWT [5], implementing the semantics specified in clause 4.5 of the present document. EAA-5.5-02: The cnf claim may only contain either a representation of the EAA subject public key or a representation of the EAA subject certificate as... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.6 EAA digital signature | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.6.1 General requirements | EAA-5.6.1-01: If the SD-JWT VC EAA is not serialized using compact serialization, its digital signature shall be a JAdES digital signature as specified in ETSI TS 119 182-1 [11]. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 5.6.2 Requirements for EU Qualified EAA (QEAA) | QEAA-5.6.2-01: The digital signature signing a SD-JWT VC QEAA shall be a qualified electronic signature or a qualified electronic seal. QEAA-5.6.2-02: The Protected Header of the digital signature signing a SD-JWT VC QEAA shall contain the x5u and the x5t#S256 header parameters, specified in IETF RFC 7515 [8]. NOTE 1: ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6 Implementation of EAA based on ISO/IEC-mdoc | 6.1 General requirements Clause 6 of the present document specifies a realization of EAA designated as ISO/IEC-mdoc EAA hereinafter. EAA-6.1-01: The data structures of the EAA shall be the data structures defined in ISO/IEC 18013-5 [12], extended with some structures defined in the present document for meeting specific... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2 EAA metadata | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.1 EAA specification | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.1.1 EAA type | There is no need to define any data element for indicating the type of the ISO/IEC-mdoc EAA. The rationale is explained below. When the wallet requests the issuance of an ISO/IEC-mdoc EAA, it knows the EAA type, so that when the ISO/IEC-mdoc EAA issuer issues the ISO/IEC-mdoc EAA (an instance of IssuerSigned type) the ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.1.2 EAA context | There is no need to define any data element for indicating the context because the data elements namespaces appear within the ISO/IEC-mdoc EAA regardless its type. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.1.3 EAA schema | NOTE: See [i.6], which specifies among other things "a data model for catalogue of attributes, guidance on Attestation Rulebooks, attestation type data models and applicable Application Programming Interface (API) for management of machine-readable attestation schemas". |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.2 EAA category | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.2.1 General requirements | EAA-6.2.2.1-01: ISO/IEC-mdoc EAAs issued by EAAs issuers registered in the European Union, which are neither ISO/IEC-mdoc QEAAs nor ISO/IEC-mdoc PuB-EAAs, shall not include the category data element. NOTE: As the category data element is defined in the present document its namespace is "org.etsi.01947201.010101". EAA-6... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.2.2 Requirements for EU Qualified EAA (QEAA) | QEAA-6.2.2.2-01: An ISO/IEC-mdoc QEAA shall include the category data element, which shall implement the semantics specified in clause 4.2.2 of the present document. QEAA-6.2.2.2-02: The value of the category data element in an ISO/IEC-mdoc QEAA shall be the URN defined in requirement QEAA-4.2.2.2-02 (urn:etsi:esi:eaa:... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.3 EAA identifier | EAA-6.2.3-01: An ISO/IEC-mdoc EAA shall incorporate the document_number data element. EAA-6.2.3-02: The document_number data element shall implement the semantics of clause 4.2.3 of the present document. EAA-6.2.3-03: If the ISO/IEC-mdoc EAA is a mDL, then the document_number data element shall be as specified in Table... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.4 EAA issuer identifier | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.4.1 General requirements | Common requirements to both types of EAA Issuer (natural or legal person) EAA-6.2.4.1-01: If an ISO/IEC-mdoc EAA is a mDL it shall include the issuing_authority component, specified in Table 5 of clause 7.2.1 of ISO/IEC 18013-5 [12]. EAA-6.2.4.1-02: The issuing_authority data element shall implement the semantics of cl... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.4.2 Requirements for EU Qualified EAA (QEAA) | QEAA-6.2.4.2-01: If the issuer of the ISO/IEC-mdoc QEAA is a legal person and if a registration identifier is applicable, an ISO/IEC-mdoc QEAA shall include the registration identifier either in the iss_reg_id data element or within the qualified certificate supporting its signature. QEAA-6.2.4.2-02: The value of the i... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5 EAA subject and attribute subject identifiers and pseudonyms | |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5.1 EAA subject identifier | EAA-6.2.5.1-01: If an ISO/IEC-mdoc EAA requires that the EAA subject (the holder of the mDL) is identified, the ISO/IEC-mdoc EAA shall include the following data elements, specified in Table 5 of clause 7.2.1 of ISO/IEC 18013-5 [12]: given_name and family_name, and document_number. EAA-6.2.5.1-02: An ISO/IEC-mdoc EAA t... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5.2 EAA subject pseudonym | EAA-6.2.5.2-01: An ISO/IEC-mdoc EAA may contain the also_known_as data element, which shall contain the pseudonym of the EAA, and therefore shall implement the semantics specified in clause 4.2.6.3 of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5.3 Attribute subject identifier | EAA-6.2.5.3-01: An ISO/IEC-mdoc EAA may include attributes that refer to entities that are not the EAA subject: the attribute subjects. EAA-6.2.5.3-02: For each attribute subject, an ISO/IEC-mdoc EAA may include the attribute subject identifier or the attribute subject pseudonym. EAA-6.2.5.3-03: In an ISO/IEC-mdoc EAA ... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5.4 Attribute subject pseudonym | EAA-6.2.5.4-01: An ISO/IEC-mdoc EAA may include pseudonyms of attribute subjects. EAA-6.2.5.4-02: In an ISO/IEC-mdoc EAA, the pseudonyms of the attribute subjects shall be associated with their corresponding attributes as specified in clause 6.3 of the present document. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.5.5 Requirements for EU Qualified EAA (QEAA) | QEAA-6.2.5.5-01: In an ISO/IEC-mdoc QEAA all the attributes shall refer to the EAA subject. 6.2.5.6 Requirements for EU EAA issued by or on behalf of a public body responsible for an authentic source (PuB-EAA) PuB-EAA-6.2.5.6-01: In an ISO/IEC-mdoc PuB-EAA all the attributes shall refer to the EAA subject. |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.6 EAA issuance | EAA-6.2.6-01: An ISO/IEC-mdoc EAA shall incorporate the issue_date data element. EAA-6.2.6-02: The issue_date data element shall indicate the issuance date according to the semantics of clause 4.2.7 of the present document. EAA-6.2.6-03: If the ISO/IEC-mdoc EAA is a mDL, then the issue_date data element shall be as spe... |
2ff4614073883a446d4efbaf91ace636 | 119 472-1 | 6.2.7 EAA validity periods |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.