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

[Christian Amsüss <[e-mail]>]

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 hold of the chairs on
the virtual hallways.

> 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!

Does either of those have a versioned history? Without a change log in
them, and no mention of the example DOS epoch discoverable in either, I
couldn't find what was there.

(8366 has a section on clock sensitivity, but that is explicitly listing
required-verification-of-expiry, nonce-based and
never-expiring-vouchers, without touching the middle ground.) 

> {There is a Doctor Who and/or Blakes Seven and/or Stargate plot here though.}

Yes, but I think I only get away with one toy reference per document ;-)

Thanks for your points and the issue
Christian

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom