Re: [Ace] Proposed document: draft-amsuess-t2trg-raytime-01

2023-07-20 Thread Michael Richardson
Christian Amsüss wrote: >> 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

Re: [Ace] Proposed document: draft-amsuess-t2trg-raytime-01

2023-07-20 Thread Christian Amsüss
Hello Michael, On Wed, Jul 12, 2023 at 06:57:38PM -0400, Michael Richardson wrote: > I don't think this belongs in t2trg, but I don't object. > maybe it goes into ACE or IOTOPS. I'll appreciate if any of those wanted it; first people I've talked to about it pointed me to T2TRG. I'll try to get a

Re: [Ace] Proposed document: draft-amsuess-t2trg-raytime-01

2023-07-12 Thread Michael Richardson
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