Torsten Lodderstedt

I guess this issue is about the verifier to wallet communication (presentation), specifically the callback from the wallet to the verifier at the request_uri. MSFT currently passes additional information in...

Isn't the question whether which request_uri_method(s) we define as MTI and which we recommend to be used?

I think the profile with key resolution and identifier authentication adds a lot in terms of interoperability. On the other hand, there are so many different technical means to manage...

One step after the other. Our first concern is to provide interoperability across implementations of OID4VC with SD-JWT on a global basis. And as always, interoperability means to reduce optionality....

I have come to the conclusion that we should support multiple credentials in a response (for now at least). There are examples being discussed in the LSPs (PID + mDL)...

"Electronic attestations of attributes" sounds good. However in the eIDAS context is one category of credentials whereas the other one is called "Person Identification Data" - so EAA would not...

Would that be a DPoP extension?

Where would we use this client id scheme?

In my opinion, `client_id_scheme` and `client_assertion_type` serve the same purpose. > maybe the question is, when client_assertion_type is wallet attestation, do we expect client metadata to be obtained from wallet...

@paulbastian correct me if I'm wrong. This PR makes clear that scope and authorization_details are equivalent and none of it is mandatory?