Hi ACME, We have submitted draft-ietf-acme-openid-federation-00 to the Datatracker [1] and the repository has been transferred into the ietf-wg-acme GitHub organization [2]. I encourage everyone to file issues or open pull requests there, though of course we welcome discussion on-list as well. In particular, please let us know if there are any broken links or other lingering references to the pre-adoption draft name.
Thanks everyone, Tim [1]: https://datatracker.ietf.org/doc/draft-ietf-acme-openid-federation/00/ [2]: https://github.com/ietf-wg-acme/draft-ietf-acme-openid-federation On Wed, Dec 10, 2025 at 6:05 AM Mike Ounsworth <[email protected]> wrote: > Hi ACME, > > There is consensus to adopt. Authors, please submit > draft-ietf-acme-openid-federation-00. > > I think the challenge in moving this document through WG will be in > bridging the two knowledge domains -- making sure that the OIDF folks > describe the ACME parts accurately, and making sure the PKI folks > understand enough of the OIDF parts to provide meaningful technical review > of how they interact in terms of interop and security. This probably means > that the authors need to do a little more "tutorial style content" in both > the draft's intro as well as in WG presentations than we do with most > drafts. > > On Thu, 4 Dec 2025 at 15:17, Brandon Pitman <[email protected]> wrote: > >> As an author, I support adoption of this draft. >> >> Thanks, >> Brandon >> >> On Thu, Dec 4, 2025 at 7:32 AM Sven A Rajala <[email protected]> >> wrote: >> >>> I support adoption for this. >>> >>> Kindly, >>> >>> Sven Rajala >>> >>> International PKI Man of Mystery >>> >>> >>> >>> *M:* +1 540 687 0761 >>> >>> sven.rajala@*keyfactor.com <https://www.keyfactor.com/>* >>> >>> >>> *From: *Giuseppe De Marco <[email protected]> >>> *Date: *Thursday, 2025 December 4 at 10:29 >>> *To: *Mike Ounsworth <[email protected]> >>> *Cc: *[email protected] <[email protected]>, [email protected] < >>> [email protected]>, [email protected] < >>> [email protected]> >>> *Subject: *[Acme] Re: Call for adoption: >>> draft-demarco-acme-openid-federation-01 (Ends 2025-12-10) >>> >>> This Message Is From an External Sender >>> This message came from outside your organization. >>> Report Suspicious >>> <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/BjbSd3t9V7AnTp3tuV-82YaK!_uQhDAxHOJmOFwIZWX3Y-GhbSwku5ncvYJPGfmkrO6fDhwdcqZ8r9uq6ZIdAC5VsaUz53LPLzauHbGsJidWt-NGnp4HCkPccnmrK4V0ZWJdNfz23zO_7Rs219km1e8Qh$> >>> >>> Hi, >>> >>> Since I am the author and I am now fully supporting the editors and the >>> contributors in this work and according to their implementative claims, I >>> fully support the adoption >>> >>> regards >>> >>> Il giorno gio 27 nov 2025 alle ore 01:36 Mike Ounsworth via Datatracker < >>> [email protected]> ha scritto: >>> >>> >>> 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/ >>> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-demarco-acme-openid-federation/__;!!BjbSd3t9V7AnTp3tuV-82YaK!yZl6RhBSidetINs9j1O88YysoKaqoUVJpiHyG02-Q_jIfskR35y8BLFBePjuWMejJQsAYgcCK1b5Nrx6xyjOKm0W$> >>> >>> 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/ >>> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp78/__;!!BjbSd3t9V7AnTp3tuV-82YaK!yZl6RhBSidetINs9j1O88YysoKaqoUVJpiHyG02-Q_jIfskR35y8BLFBePjuWMejJQsAYgcCK1b5Nrx6x-T6Uqn3$> >>> [2] https://datatracker.ietf.org/doc/bcp79/ >>> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/bcp79/__;!!BjbSd3t9V7AnTp3tuV-82YaK!yZl6RhBSidetINs9j1O88YysoKaqoUVJpiHyG02-Q_jIfskR35y8BLFBePjuWMejJQsAYgcCK1b5Nrx6x7eZYNo3$> >>> [3] https://datatracker.ietf.org/doc/rfc6701/ >>> <https://urldefense.com/v3/__https://datatracker.ietf.org/doc/rfc6701/__;!!BjbSd3t9V7AnTp3tuV-82YaK!yZl6RhBSidetINs9j1O88YysoKaqoUVJpiHyG02-Q_jIfskR35y8BLFBePjuWMejJQsAYgcCK1b5Nrx6x8ksRsFw$> >>> >>> >>> >>> _______________________________________________ >> 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] >
_______________________________________________ Acme mailing list -- [email protected] To unsubscribe send an email to [email protected]
