Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Specify in terms of Seal() and Open APIs #42

Open
laurencelundblade opened this issue Oct 12, 2023 · 2 comments
Open

Specify in terms of Seal() and Open APIs #42

laurencelundblade opened this issue Oct 12, 2023 · 2 comments

Comments

@laurencelundblade
Copy link
Contributor

As an implementor, what I really want to know is how COSE data structures go in and out of the HPKE Seal() and Open() APIs. These APIs are THE definition of HPKE.

I would write a section, maybe as a table with one Seal() parameter per row and describe how to construct them.
@dajiaji
Copy link
Contributor

dajiaji commented Nov 4, 2023

I think it's a good idea. It would be helpful to the implementors. I support adding this kind of description to the spec.

@hannestschofenig
Copy link
Collaborator

We had this type of description in an earlier version of the spec, see https://www.ietf.org/archive/id/draft-ietf-cose-hpke-05.html#name-hpke-encryption-and-decrypt

Is this what you are asking for?

@laurencelundblade laurencelundblade mentioned this issue Feb 11, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hannestschofenig @dajiaji @laurencelundblade