-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify ISO mdoc Handover structure #415
Comments
@davidz25 It is essentially what -7 rev2 is doing and -7 rev2 has similar language and CDDL. I remember that in the past somebody in ISO made a comment that it was not clear what Re |
Fixes openid#415. Signed-off-by: David Zeuthen <[email protected]>
Hi, thanks for looking. As for the text, I missed that in my original read-through (fixating on the CDDL), I think that could also be more crisp. I'm uploaded a PR with the changes, we can discuss there maybe. |
Fixes openid#415. Signed-off-by: David Zeuthen <[email protected]>
In B.3.4 it's defined how each side must construct the
SessionTranscript
using a handover defined in the following wayThere's a couple of problems here
tstr
are Unicode strings, it's meaningless to say "UTF-8 encoded string" because it's already tstr. Should just remove those comments.OpenID4VPDCAPIHandoverInfoHash
is defined as the "sha-256 hash of OpenID4VPDCAPIHandoverInfo" but doesn't make sense as you can only hash bytes (e.g. the encoded version of CBOR), not CBOR itself.Here's what I would replace it with
I think this achieves what was originally intended and is more crisp. It's also consistent with what other standards are doing, for example see
empty_or_serialized_map
in COSE (RFC 9052).The text was updated successfully, but these errors were encountered: