Torsten Lodderstedt

I think the deferred credential response should have been extended to support batches in the same way as the credential response when the batch option was introduced there. Let's do...

I think this issue is about different things: 1. Split wallet attestation into wallet instance attestation and issuer trust evidence (basically an interoperable key attestation) 2. Use the wallet instance...

After the discussion in the WG meeting on Tue, I have come to the following conclusions: I think it suffices to add a new header `attestation` with the key attestation...

@alenhorvat I have never seen key attestations in the QTSP context. Can you please refer to solutions for this problem in the x.509 world?

@ssanchocanela WTE/ITEs shall be presented with the credential request (at the issuer). The WIA shall be presented to the AS with the token request.

@andprian thanks a lot! I think the PoP requirements are fulfilled by credential request as is today. This issue is about adding the key attestation (WSCD info) to the process....

split the discussion about the optimization to https://github.com/openid/OpenID4VCI/issues/368

@alenhorvat this issue is about key attestations. My question was: Where QTSPs use key attestations today?

Summary: after we have split the optimization from this issue, the focus is on - adding the wallet attestation to the token endpoint (already exists in HAIP) - integration of...

Example of a simple, interoperable key attestation that would go into a new header `attestation` parameter in jwt proof type: ``` { "typ": "ite+jwt", "alg": "ES256", "x5c": } . {...