Unless someone else in the group objects, I will change the text in Section 3.4
("Info Structure") to say that the aad and the info structures for SealBase()
and OpenBase() functions are empty unless specified by an application-specific
profile of the COSE-HPKE specification.
Ciao
Hannes
-----Original Message-----
From: COSE <[email protected]> On Behalf Of Ilari Liusvaara
Sent: Friday, July 8, 2022 6:30 PM
To: cose <[email protected]>
Subject: Re: [COSE] COSE-HPKE COSE_KDF_Context
On Fri, Jul 08, 2022 at 03:53:42PM +0000, Hannes Tschofenig wrote:
> Hi Ilari,
>
> The problem is that we couldn't find out what Those use cases are that
> would benefit from using this structure. Even without this structure,
> HPKE already utilizes all the relevant information in is key
> derivation.
Well, if no general-purpose usecase can be defined, it yes, makes sense to just
set app_ad and info to blank unless application uses those for something (there
is already stuff with similar interop impact in RFC8152).
However, the part where by-default blank ad and info is specified could use
some word-smithing to avoid misinterpretations similar to mine.
I changed my test implementation to pass empty info (the app_ad was already
empty).
-Ilari
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the sender immediately and do not disclose the contents to any
other person, use it for any purpose, or store or copy the information in any
medium. Thank you.
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
