I agree.

It might be helpful to have a recap of the topic, so that any new attendees
can see the arguments presented.

With the chair's approval, I'm happy to send a *short* recap to the list of
my views on the topic.

OS


On Fri, Jul 14, 2023 at 6:38 AM Henk Birkholz <
[email protected]> wrote:

> Hi Hannes,
> dear chairs,
>
> I concur that we have to resolve the effective blocker highlighted by
> Hannes and would like to add a request of agenda time to discuss the
> results of the consensus building procedure.
>
> Viele Grüße,
>
> Henk
>
> On 13.07.23 11:41, Hannes Tschofenig wrote:
> > Hi all,
> >
> > to update the COSE-HPKE draft for the deadline I re-read all the emails
> from the most recent discussion.
> > Unlike the discussion last year, several new people jumped into the
> debate and provided their feedback. The additional feedback changed the
> view on the topic.
> >
> > The following people expressed their preference for a single algorithm
> to express the HPKE combination of KEM/KDF/AEAD*:
> >
> > - Laurence
> > - Michael
> > - Carsten
> > - Orie
> > - Chris
> > - Jeremy
> >
> > Ilari and Daisuke were against the single algorithm approach.
> >
> > I wasn't quite sure about the preference of John based on his email
> feedback.
> >
> > I would prefer to have the chairs declare consensus on this topic,
> particularly since this topic seems to polarize.
> >
> > Ciao
> > Hannes
> >
> > *: Various ways for registering this combination have been mentioned and
> discussed. I leave those details for later.
> >
> >
> > _______________________________________________
> > COSE mailing list
> > [email protected]
> > https://www.ietf.org/mailman/listinfo/cose
>
> _______________________________________________
> COSE mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/cose
>


-- 


ORIE STEELE
Chief Technology Officer
www.transmute.industries

<https://transmute.industries>
_______________________________________________
COSE mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/cose

Reply via email to