digital-credentials
digital-credentials copied to clipboard
Fold in Mobile Document Request API into spec, so we can do requests
I wonder if the HPKE part of this will consume https://www.iana.org/assignments/hpke/hpke.xhtml directly, or establish a new "named suites" registry specific to the protocol, like https://www.iana.org/assignments/mls/mls.xhtml#mls-ciphersuites
why do we need this if OID4VP supports mdocs?
why do we need this if OID4VP supports mdocs?
I think the intention here was to figure out how to present mdocs while we are working with the OID4VP community to support the browser API?
The main thing that needs to be figured out on OID4VP front is how the OID4VP request over browser API looks like. I thought the agreement was to sort that out (still waiting for the issue/contribution in OID4VP repo). This feels like a diversion.
also this is probably just terminology, but the framing of how browser api supports oid4vp feels more natural.
@Sakurann lee kicked this off to get the ball rolling. Does this help?
https://github.com/openid/OpenID4VP/issues/90
yes, thank you!
Cleaning up old issues. This was addressed in OID4VP.