Subject: Call for adoption: draft-sheurich-acme-dns-persist-01  (Ends
2025-10-10)

This message starts a 2-week Call for Adoption for this document.

Abstract:
   This document specifies "dns-persist-01", a new validation method for
   the Automated Certificate Management Environment (ACME) protocol.
   This method allows a Certification Authority (CA) to verify control
   over a domain by confirming the presence of a persistent DNS TXT
   record containing CA and account identification information.  This
   method is particularly suited for environments where traditional
   challenge methods are impractical, such as IoT deployments, multi-
   tenant platforms, and scenarios requiring batch certificate
   operations.  The validation method is designed with a strong focus on
   security and robustness, incorporating widely adopted industry best
   practices for persistent domain control validation.  This design aims
   to make it suitable for Certification Authorities operating under
   various policy environments, including those that align with the CA/
   Browser Forum Baseline Requirements.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-sheurich-acme-dns-persist/

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]

Reply via email to