Hey Simo, Can you say which format you prefer for proposed HPKE algorithms? It is not clear which shortened proposal you are objecting to here.
OS On Tue, Dec 10, 2024 at 9:44 AM Simo Sorce <[email protected]> wrote: > This would be a net regression, > these areas are complicated enough that we do not need to add confusion > to save a couple of bytes. > > On Fri, 2024-12-06 at 12:06 +0530, tirumal reddy wrote: > > We can consider the short-form HPKE-P2-S2-A1. > > > > -Tiru > > > > On Fri, 6 Dec 2024 at 01:45, Michael Jones <[email protected]> > > wrote: > > > > > Please see the discussion in the issue > > > https://github.com/ietf-wg-jose/draft-ietf-jose-hpke-encrypt/issues/8 > (*Algorithm > > > identifiers like HPKE-P256-SHA256-A128GCM are overly verbose*) and add > > > your thoughts there. > > > > > > > > > > > > Thanks! > > > > > > -- Mike > > > > > > > > > _______________________________________________ > > > jose mailing list -- [email protected] > > > To unsubscribe send an email to [email protected] > > > > > _______________________________________________ > > jose mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > > -- > Simo Sorce > Distinguished Engineer > RHEL Crypto Team > Red Hat, Inc > > _______________________________________________ > jose mailing list -- [email protected] > To unsubscribe send an email to [email protected] > -- ORIE STEELE Chief Technology Officer www.transmute.industries <https://transmute.industries>
_______________________________________________ jose mailing list -- [email protected] To unsubscribe send an email to [email protected]
