Hi Marco,
I created potential resolutions for the remaining open points in this draft in
a series of short PRs in the current repository. Could you take a look at these
and see if these resolve your comments?
@chairs: Could you create a repository for “est-oscore” under github.com/ace-wg
Benjamin Kaduk wrote:
> On Mon, May 01, 2023 at 12:09:03PM +0200, Christian Amsüss wrote:
>> Hi Michael, (CC'ing ACE list because what I think will be the larger
>> part of the thread is hopefully relevant)
>>
>> > > there a generalization of the IEEE identifiers that also mak
Christian Amsüss wrote:
> Yes, that's the way I'd hope they could be used. For example, if a
> device were onboarded into an ACE domain with three AS that's using the
> ACE-OSCORE profile with the devices, they'd obtain three symmetric keys
> with a key identifier h'00', h'01' and
Hi Mališa,
I've reviewed them and they look overall good to me.
Please check the comments I left on PR #10, PR #14, and PR #15.
Best,
/Marco
On 2023-05-26 17:24, Mališa Vučinić wrote:
Hi Marco,
I created potential resolutions for the remaining open points in this
draft in a series of short
> On May 26, 2023, at 1:18 PM, Michael Richardson wrote:
>
>> Is that identity now an LDevID (even though it has a completely
>> different shape than the IDevID), or is a certificate based LDevID
>> still created as part of the process, or can the device happily
>> complete the ANIMA processes
On Thu, May 25, 2023 at 1:15 PM Mohit Sahni wrote:
> Hi Paul,
> I think you may be looking at the older version of the draft. (Please
> check
> https://datatracker.ietf.org/doc/html/draft-ietf-ace-cmpv2-coap-transport)
>
Odd, I was and I wasn't. Maybe a caching issue. Thanks for pointing out
mos
Thanks Paul and others for moving this document forward!
Yours,
Daniel
From: Ace on behalf of Paul Wouters
Sent: Friday, May 26, 2023 3:33 PM
To: Mohit Sahni
Cc: Daniel Migault; Brockhaus, Hendrik; ace@ietf.org
Subject: Re: [Ace] I-D Action: draft-ietf-
Russ Housley wrote:
>>> Is that identity now an LDevID (even though it has a completely
>>> different shape than the IDevID), or is a certificate based LDevID
>>> still created as part of the process, or can the device happily
>>> complete the ANIMA processes without an LDevID?