Ciphersuite (fully specified) approach strongly preferred. LL
On Sep 5, 2023, at 10:31 AM, Ivaylo Petrov <[email protected]> wrote: Dear all, We had long discussions on the mailing list (see [COSE] COSE-HPKE and the Single Algorithm Discussion (ietf.org)<https://mailarchive.ietf.org/arch/msg/cose/_GQXXpltAgXNozXIFC9z1yY1CCM/>) and a summary presentation at the last IETF meeting (see slides-117-code-updated-hike-summary-notes-from-hannes (ietf.org)<https://datatracker.ietf.org/meeting/117/materials/slides-117-cose-updated-hpke-summary-notes-from-hannes> and COSE IETF 117 - HedgeDoc<https://notes.ietf.org/notes-ietf-117-cose>) about the question whether algorithm combinations should be presented in an “a la carte” style or as a “ciphersuite” in draft-ietf-cose-hpke (“A la carte” corresponds to “polymorphic” in https://www.ietf.org/archive/id/draft-jones-jose-fully-specified-algorithms-01.html and “ciphersuite” corresponds to “fully specified”). On the mailing list and during the face to face meeting there was a strong consensus to use the ciphersuite (fully specified) approach. The chairs would like to confirm this decision. You have 2 weeks till Tuesday, the 19th of September to provide your final feedback. Please reply-all indicating your preference for either: * ciphersuite (fully specified) approach * A la carte (polymorphic) approach The authors will be then instructed to update the COSE-HPKE working group draft accordingly. Best wishes, Ivaylo on behalf of the COSE chairs _______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
_______________________________________________ COSE mailing list [email protected] https://www.ietf.org/mailman/listinfo/cose
