The chairs' analysis of the consensus call responses is that, unfortunately, 
the consensus call was inconclusive.  While more support was expressed for 
option 1 (Continuing to use COSE_Key) than the other options, there was also 
some support for the other two options.

The chairs do appreciate the useful and informative discussion that resulted 
from the consensus call.

Since there is not yet working group consensus on what other key representation 
should be used and there was more support for COSE_Key than other 
representations, the chairs ask that the editors leave the COSE_Key 
representation in place in the draft until such time as a clear consensus 
emerges as to what should replace it.  The chairs are willing to run another 
consensus call between COSE_Key and the new proposed key representation to 
determine consensus, should that be useful, once it appears to be time to do so.

Thanks to all who participated!

                                         -- Mike (for the COSE chairs)

From: Mike Jones
Sent: Thursday, September 22, 2022 10:09 AM
To: [email protected]
Subject: COSE HPKE Public Key Format Consensus Call

As discussed at IETF 114, the HPKE draft uses the COSE_Key public key 
representation.  The authors described that Ilari Liusvaara had proposed using 
a different public key representation, which is detailed in Slide 2 of 
https://datatracker.ietf.org/meeting/114/materials/slides-114-cose-cose-hpke-00.
  As recorded in the 
minutes<https://datatracker.ietf.org/doc/minutes-114-cose/>, consensus during 
the meeting appeared to be in favor of continuing to use COSE_Key.

This note initiates a consensus call by the chairs on the topic of what public 
key format the COSE HPKE specification will use.  Working group members are 
requested to express their preferences within two weeks of this note (by 
Thursday, September 6th) for either:

1.  Continuing to use COSE_Key
2.  Using the different format proposed by Ilari Liusvaara
3.  Other (please describe in sufficient detail to enable its specification)

                                                       Thank you,
                                         -- Mike (for the COSE chairs)

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

Reply via email to