Re: [Rats] PKIX Attestation design group meeting notes 2024-01-29

[Michael Richardson <[e-mail]>]

Mike Ounsworth <Mike.Ounsworth=[e-mail]> wrote:
    > certificate management protocol -- ex.: one HSM vendor may use an
    > Epoch-based freshness mechanism, while another uses a clock-based mechanism;
    > or a cert management protocol like ACME or CMP might build in their own
    > freshness mechanism -- so Evidence freshness really does not belong at the
    > CSR wrapper layer specified in this I-D.

So, just consider the freshness to be Evidence that might be proprietary.
I'm happy with that.

    > Discussed at some length the OID references registry
    > https://github.com/lamps-wg/csr-attestation/pull/83

    > Basically, implementors writing Relying Parties against this spec will ask
    > "Ok, but where can I find a list of all the OIDs that I can expect to see
    > show up in EvidenceStatement.type?".

    > So this document will instruct IANA to create a new registry that is a
    > collection of, and references to, Attestation Evidence format OIDs that have
    > been registered elsewhere. The proposed format for the table is:

I started a thread on this topic.
My question was whether this was just a list of OIDs, or if there was a place
to get OIDs (an arc).  I think that asking for an arc is not that much a request.

    > We really want to get the CSR draft shipped so that we can dedicate more
    > time to the x509-evidence draft than just the last 8 minutes of every
    > meeting.

:-)
Running code?
Hackathon in Vancouver?

--
Michael Richardson <[e-mail]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide