Torsten Lodderstedt
Torsten Lodderstedt
Here is the PR openid/OpenID4VP#308.
I don't feel we have enough information to properly design a solution. I'm concerned this feature will make the spec much more complex and I don't fully understand the benefit...
Can you shed some light on the use case? I see use cases for requesting a credential in two formats for issuance, I would like to understand why a verifier...
WG Call 19.6 - Add description of the reasons/limitation for this mechanism - Add differentiation to DC API (for getting the credential presentation) - this mechanism is for the classical...
I expect the credential to contain the issuer policy and the issuer decides what policy to add to which credential. I also agree with your observation there is no solution...
I agree with @jogu. I would also like to understand the problem to be solved and the concrete solution proposal. The verifier attestation method has a certain behavior and defines...
@babisRoutis > > VCI is all about allowing wallet to place a credential request. It doesn't seem consistent that throughout the issuance process (offer, `authorization_details`, auth. req) an unambiguous identifier...
In the most general case, every issuer has its own credential configuration ids. Implementation experience will tell whether there are situations with shared credential configuration definitions.
WG call: Mike explained the errata process to us. We need to decide whether this issue will be fixed in an VCI 1.0 errata.
@paulbastian will check back with the ETSi editor to figure out the best way to refer to the VCI from the ETSi spec.