On 2023-06-29, at 22:41, Ilari Liusvaara <[email protected]> wrote: > > COSE has always been frameworky. For such specifications, > restrictions for interop are inapporiate. Instead, the specs are > intended to be profiled down or specialized for applications, and in > that process, appriate restrictions are defined for interoperability. > > The programming saying is "mechanism, not policy".
This. My proposal to encode HPKE registry entries in `alg` retains this. It also removes an unnecessary threshold (i.e., “batteries included”) that would be needed to encode the a-la-carte selection in `alg`, which is the preferred way to keep things compact and compatible. For those why think my proposal is too hacky: Today’s hack is tomorrow's best current practice is next week’s cherished design principle. Grüße, Carsten _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
