Hi Ilari,
I can certainly add text based on your suggestion below.
Ciao
Hannes
Am 13.03.2023 um 13:03 schrieb Ilari Liusvaara:
On Mon, Mar 13, 2023 at 12:11:35PM +0100, Hannes Tschofenig wrote:
Hi Ilari,
However, for interop, one
needs to specify that info is empty unless specified otherwise.
When you say "interop" are you talking about testing? We could include
test cases into the appendix of the draft. Thereby we do not necessarily
have to leave the info and the AAD fields empty. We could populate them
with some made-up values. This would allow us to verify implementations.
I mean doing similarly as what RFC 9052 does with the external_aad,
which is also application-specific and interop-critical:
"The externally supplied data from the application encoded in a bstr
type. If this field is not supplied, it defaults to a zero-length byte
string."
Similarly, with info, one wants the field to default to zero-length
byte string if not suppiled. Then if some application wants to use
info for something, it can supply that field. Or if the application
does not use info, it can just forget about it and things still work.
And with regards to test vectors with non-default external_aad, or
non-default info, I don't think that there is need for more than one
example of each.
-Ilari
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose
