Scope: High Level Requirements on Wallet Trust Evidence (Topic 9)
Summary: The ARF prescribes the WSCA to centrally manage dedicated key pairs for PID and attestations. This is costly, since the WSCA is a certified application running on a WSCD which is often resource-constrained. Instead, with approaches such as HDK, it is possible to distribute key management across the WSCA and the Wallet Instance. The requirements should reflect that.
Detailed suggestions and rationale:HDK v0.1.0 feedback on Topic 9 regarding WTE_10, WTE_13, WTE_14, WTE_17, WTE_18, WTE_19, WTE_31, WTE_33, WTE_35, WTE_36.
Context: https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/discussions/282
Scope: High Level Requirements on Wallet Trust Evidence (Topic 9)
Summary: The ARF prescribes the WSCA to centrally manage dedicated key pairs for PID and attestations. This is costly, since the WSCA is a certified application running on a WSCD which is often resource-constrained. Instead, with approaches such as HDK, it is possible to distribute key management across the WSCA and the Wallet Instance. The requirements should reflect that.
Detailed suggestions and rationale: HDK v0.1.0 feedback on Topic 9 regarding WTE_10, WTE_13, WTE_14, WTE_17, WTE_18, WTE_19, WTE_31, WTE_33, WTE_35, WTE_36.
ARF version: 1.4.0