Hi,

I read the document and believe that it addresses an important use case.

I have some reservations about the assumed trust and freshness models,
though, but I am sure that a viable solution can be sorted uot.

I support adoption of this document in ACME, and I am happy to assist
with design, reviews and whatever else is useful.

cheers!

On Thu, 27 Nov 2025 at 01:38, Mike Ounsworth via Datatracker
<[email protected]> wrote:
>
>
> Subject: Call for adoption: draft-liu-acme-rats-02  (Ends 2025-12-10)
>
> This message starts a 2-week Call for Adoption for this document.
>
> Abstract:
>    This document describes an approach where an ACME Server can
>    challenge an ACME Client to provide a Remote Attestation Evidence or
>    Remote Attestation Result in any format supported by the Conceptual
>    Message Wrapper.
>
>    The ACME Server can optionally challenge the Client for specific
>    claims that it wishes attestation for.
>
> File can be retrieved from:
> https://datatracker.ietf.org/doc/draft-liu-acme-rats/
>
> Please reply to this message keeping [email protected] in copy by indicating
> whether you support or not the adoption of this draft as a WG document.
> Comments to motivate your preference are highly appreciated.
>
> Authors, and WG participants in general, are reminded of the Intellectual
> Property Rights (IPR) disclosure obligations described in BCP 79 [2].
> Appropriate IPR disclosures required for full conformance with the provisions
> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
> Sanctions available for application to violators of IETF IPR Policy can be
> found at [3].
>
> Thank you.
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
>
>
>
> _______________________________________________
> Acme mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
Acme mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to