Christian Amsüss <christ...@amsuess.com> 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] on how
> devices without reliable Internet connectivity (and thus time source)
> can deal with time limited tokens.
I like your document.
We wrote something similiar for RFC8366 or 8995, but I think we ripped most
of it out. For instance, if a device had a valid IDevID with a notBefore of
2021-02-01, and the RTC said 1980-01-01 [good old DOS epoch], then one could
be sure it was at least 2021-02-01!
You are just advancing the raytime based upon verified information from the
AS. I definitely like that.
{There is a Doctor Who and/or Blakes Seven and/or Stargate plot here though.}
> The concept and trade-offs will not be surprising to many, but to my
> knowledge they have not been written up. In addition, this document
> lists the mechanisms a device can use to reject outdated tokens on a
> best effort base.
> I'd appreciate the group's input on the document, in particular in the
> area of previous work there.
I opened an issue in your gitlab.
--
Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
