Hello,

I support adoption of this draft by ACME. We've got some working
implementations and there are concrete use cases that would imminently make
use of this work. We heard a bit about that during the ACME WG session in
Montreal, and I think we'll hear a bit more here in this thread.

I wrote a bunch of this document and will continue to contribute reviews
and changes. Additionally, we will maintain our implementation
<https://github.com/abetterinternet/oidf-box> of this challenge type
throughout development of the document.

Thanks,
Tim

On Wed, Nov 26, 2025 at 4:37 PM Mike Ounsworth via Datatracker <
[email protected]> wrote:

>
> Subject: Call for adoption: draft-demarco-acme-openid-federation-01  (Ends
> 2025-12-10)
>
> This message starts a 2-week Call for Adoption for this document.
>
> Abstract:
>    The Automatic Certificate Management Environment (ACME) protocol
>    allows server operators to obtain TLS certificates for their
>    websites, based on a demonstration of control over the website's
>    domain via a fully-automated challenge/response protocol.
>
>    OpenID Federation 1.0 defines how to build a trust infrastructure
>    using a trusted third-party model.  It uses a trust evaluation
>    mechanism to attest to the possession of private keys, protocol
>    specific metadata and miscellaneous administrative and technical
>    information related to a specific entity.
>
>    This document defines how X.509 certificates associated with a given
>    OpenID Federation Entity can be issued by an X.509 Certification
>    Authority through the ACME protocol to the organizations which are
>    part of a federation built on top of OpenID Federation 1.0.
>
> File can be retrieved from:
> https://datatracker.ietf.org/doc/draft-demarco-acme-openid-federation/
>
> 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