Hi Michel. The chairs see your request for a Call-For-Adoption. This is an -00 draft, tagged as Proposed Standard, that I imagine will generate quite a bit of discussion; I don't claim to be an expert on the interactions between SRV DNS records and X.509 Certificates, but the Introduction of your draft certainly gives me the impression that this is a workaround to be able to get certificates for a domain that you're not authorized to get certificates for, which I imagine will generate a fair amount of discussion. Since this is a brand new draft, I don't see much discussion on the list about it yet.
We could do a Call-For-Adoption if you like, which may generate some discussion, but it also has a good chance of failing. Since you are submitting this as Standards Track, I think you would be in a stronger position for a CfA if you can get some large deployers (for example, cloud service providers or ACME operators) to come to the list saying that this draft solves a real-world problem they have, and they are interested in deploying this. Maybe waiting and presenting this at IETF 124 in Montreal would be a good way to generate discussion on this draft? On Wed, 3 Sept 2025 at 12:47, Michel Le Bihan <[email protected]> wrote: > Dear ACME WG, > > I would like to request that the working group consider adopting my draft, > draft-lebihan-srv-identifier-validation-extension-00 ( > https://datatracker.ietf.org/doc/draft-lebihan-srv-identifier-validation-extension/), > “Automated Certificate Management Environment (ACME) SRV Identifier > Validation Extension”, as a WG document. > > The draft extends ACME to cover SRV identifiers in a way that I believe is > consistent with the WG’s scope and useful for real deployment scenarios. I > would welcome a call for adoption and feedback from the group. > > Best regards, > Michel Le Bihan > > _______________________________________________ > 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]
