You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Section B.3.1 defines the doctype_value and intent_to_retain fields. In the ISO/IEC 18013-5 specification, both of these fields are mandatory. Unless there is a strong reason to not have the same requirements, these should be mandatory when an mdoc is requested when using OpenID.
The text was updated successfully, but these errors were encountered:
there was a pretty strong pushback mandating intent_to_retain in openid4vp when we introduced the mechanism. I think this issue belongs in HAIP, where we could discuss making both mandatory with less resistance?
Whenever possible we should guarantee interoperability on the OpenID4VP layer, I can understand some of the concerns with mandating the intent_to_retain field, but I don't see the same opposition for the doctype field, especially because the behavior for it not being present is undefined. Would there be any objection to at least mandate the doctype field in the OpenID4VP specification?
Section B.3.1 defines the doctype_value and intent_to_retain fields. In the ISO/IEC 18013-5 specification, both of these fields are mandatory. Unless there is a strong reason to not have the same requirements, these should be mandatory when an mdoc is requested when using OpenID.
The text was updated successfully, but these errors were encountered: