Define usage of HPKE and info structure to be used.#703
Define usage of HPKE and info structure to be used.#703GarethCOliver wants to merge 3 commits intomainfrom
info structure to be used.#703Conversation
GarethCOliver
requested review from
awoie,
bc-pi,
c2bo,
jogu and
martijnharing
and removed request for
awoie
|
WG discussion in #692 (comment) said no to jwkthumbprint and yes to hash. However, after a discussion in the WG, given the changes in the jose-hpke specification, we have a choice as a wg and there is a preference not to hash, but want to check first if widely used libraries restrict the length or not. we will come back to it next wg call. WG discussion today: yes to use separator bytes. |
|
Updated to remove thumbprint. My review of documentation of existing HPKE implementations is that they currently don't enforce the recommended interop limit. Given the upcoming change to text to remove that implementation I think it's safe to leave as is (but will let @martijnharing chime in once he does his research). |
c2bo
left a comment
c2bo
left a comment
There was a problem hiding this comment.
I'd feel more comfortable if we get rid of the space, but i can also live with this. I checked the examples and everything looks good
| When the response mode is `direct_post.jwt` the encoding is as follows: | ||
|
|
||
| ```example | ||
| session_info = ASCII("OpenID4VP si") || |
There was a problem hiding this comment.
I know that it shouldn't really matter, but the space in OpenID4D4VP si makes me somewhat nervous. Would people be fine to instead use OpenID4VP-si?
3 participants
Resolve #692
This specifies how to user JOSE HPKE in OpenId4VP by defining a 'session_info' structure to be included in the info parameter.
It uses a byte structure, following the pattern JOSE HPKE uses for the recipient structure.
Open Questions: