As I commented in the mic line, add me! And Corey too.
-Tim From: Acme <[email protected]> On Behalf Of Mike Ounsworth Sent: Monday, November 27, 2023 4:50 PM To: [email protected]; Paul van Brouwershaven <[email protected]> Subject: [Acme] Starting a design team for draft-vanbrouwershaven-acme-auto-discovery Hey ACME! We are following up on the discussion related to draft-vanbrouwershaven-acme-auto-discovery. Before doing a call-for-adoption, Deb asked us to form a design team to resolve the open design questions. Anyone who is interested in participating in this design group, please reply to this email, or to Paul or I directly. Agenda for first design team meeting: 1. Security Considerations review of the current draft; particularly when the ACME account initiating the request is owned by a cloud service provider and is shared across multiple subscribers. Would a DV-based mechanism to authorize that the ACME account has control over the domain be sufficient to meet the security goals of this auto-discovery draft? See: https://github.com/vanbroup/acme-auto-discovery/issues/18 2. Review of open github issues. See https://github.com/vanbroup/acme-auto-discovery/issues Mike Ounsworth [email protected] <mailto:[email protected]> Paul van Brouwershaven [email protected] <mailto:[email protected]> - - - Mike Ounsworth Software Security Architect (pronouns: he/him)
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
