Below...
> On Nov 1, 2022, at 2:21 AM, Ilari Liusvaara wrote:
>
> On Mon, Oct 31, 2022 at 11:45:51AM -0700, Laurence Lundblade wrote:
>>> On Oct 31, 2022, at 2:50 AM, Ilari Liusvaara
>>> wrote:
>>>
>>> On Sun, Oct 30, 2022 at 11:29:46PM -0700, Laurence Lundblade wrote:
Jumping into
On Mon, Oct 31, 2022 at 11:45:51AM -0700, Laurence Lundblade wrote:
> > On Oct 31, 2022, at 2:50 AM, Ilari Liusvaara
> > wrote:
> >
> > On Sun, Oct 30, 2022 at 11:29:46PM -0700, Laurence Lundblade wrote:
> >> Jumping into this… hopefully I’m up to speed enough to not say
> >> something dumb….
>
Hi Ilari,
Below.
> On Oct 31, 2022, at 2:50 AM, Ilari Liusvaara wrote:
>
> On Sun, Oct 30, 2022 at 11:29:46PM -0700, Laurence Lundblade wrote:
>> Jumping into this… hopefully I’m up to speed enough to not say
>> something dumb….
>>
>> The pkE starts out on the sender side represented in the
On Sun, Oct 30, 2022 at 11:29:46PM -0700, Laurence Lundblade wrote:
> Jumping into this… hopefully I’m up to speed enough to not say
> something dumb….
>
> The pkE starts out on the sender side represented in the internal
> data structure that the crypto library likes. It has to be because
> it
, October 31, 2022 7:30 AM
To: cose
Subject: [COSE] Format of pkE/enc in HPKE
Jumping into this… hopefully I’m up to speed enough to not say something dumb….
The pkE starts out on the sender side represented in the internal data
structure that the crypto library likes. It has to be because
Jumping into this… hopefully I’m up to speed enough to not say something dumb….
The pkE starts out on the sender side represented in the internal data
structure that the crypto library likes. It has to be because it is input the
the DH function. This is neither a COSE_Key nor the byte string
