Christian Amsüss wrote:
> Hello T2TRG (because of its researchy character), hello ACE (because
> this is applied to your ecosystem),
I don't think this belongs in t2trg, but I don't object.
maybe it goes into ACE or IOTOPS.
> motivated by project requirements, I've written a draft[1
Hi Christian, I'm excited by your document.
First some editorial suggestions. IN section 1.1, without having given a
picture of what you are doing you start to say:
"The alternative to this constraint is to declare this a blob"
and this is really distracting to understanding what you *ARE
Hello T2TRG (because of its researchy character),
hello ACE (because this is applied to your ecosystem),
motivated by project requirements, I've written a draft[1] on how
devices without reliable Internet connectivity (and thus time source)
can deal with time limited tokens.
> Abstract:
>When
Hello ACE and ANIMA groups,
hello Ben, Michael and Russ,
taking input from the "ANIMA and ACE, IDevID terminology" thread[1],
where the discussion was lacking a concrete proposal, I've written up
things at [2].
I'd appreciate the one or other pair of eyes, and feedback both on the
direction and t
Hi all,
As you could notice from the IETF 117 agenda, LAKE will be meeting on Monday,
24 July 2023 at 16:30 UTC. We will be sharing a 2-hour slot with ACE in the
following format:
- LAKE session will take place during the first hour, 16:30-17:30 UTC
- ACE session will take place during the seco
