Skip to content

Commit

Permalink
Merge pull request #199 from kernoelpanic/Typo-in-Annex-2,-WSC-->-WSCA
Browse files Browse the repository at this point in the history
Fixed missing character in annex-2-high-level-requirements.md
  • Loading branch information
digeorgi committed Jun 28, 2024
2 parents 666be84 + bec13dd commit 39bf7d9
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/annexes/annex-2/annex-2-high-level-requirements.md
Original file line number Diff line number Diff line change
Expand Up @@ -302,7 +302,7 @@ A. Creating the WTE during Wallet Instance activation
| WTE_08 | The Commission SHALL take measures to ensure that the contents, format and encoding of the Wallet Trust Evidence is specified in a technical specification. Each WTE SHALL describe the Wallet Instance and a certified WSCA available to that Wallet Instance, in such a way that a PID Provider or Attestation Provider processing the WTE is able to take a well-grounded decision on whether to issue an attestation to that Wallet Instance and WSCA. <br>Notes: <ul><li>In general, a PID Provider or Attestation Provider will also need information about the User. Such information is not contained in the WTE.</li><li>The WTE does not contain information allowing a PID Provider or Attestation Provider to verify whether the WTE (and by extension the Wallet Instance) is revoked. Revocation information for the Wallet Instance is instead included in the WIA defined in \[[Topic 38](#a2338-topic-38---wallet-instance-revocation)\].</li></ul> |
| WTE_09 | A Wallet Provider SHALL consider all relevant factors, including the risk of a WTE public key becoming a vector to track the User, when deciding on the validity period of a WTE. A Wallet Provider MAY use short-lived WTEs to mitigate such risks. |
| WTE_10 | A WSCA SHALL generate a new key pair for a new WTE on request of the Wallet Provider via the Wallet Instance. The WSCA SHALL register the new key as a WTE key in an internal registry. The WSCA SHALL register the WTE key as an independent (i.e., non-associated) key in an internal registry. <p><br>Note: A WTE key can be associated later with a PID or attestation key when that PID or attestation key is created, see WTE_13. |
| WTE_11 | A WTE SHALL contain a public key, and the corresponding private key SHALL be generated by the WSC described in the WTE. <p><br>Note: A WTE key pair is generated as per WTE_10. |
| WTE_11 | A WTE SHALL contain a public key, and the corresponding private key SHALL be generated by the WSCA described in the WTE. <p><br>Note: A WTE key pair is generated as per WTE_10. |
| WTE_12 | In case the Wallet Provider must update the WTE because the information in the WTE is outdated, the Wallet Provider SHALL ensure that the Wallet Instance only releases the latest version of a WTE to an Attestation Provider. |


Expand Down

0 comments on commit 39bf7d9

Please sign in to comment.