We at Telia Company are working on an ACME server implementation that is going to integrate with an existing CA system using external account binding. We're planning on using the OOB challenge type to signify pre-authorized domains (in the existing CA system) as already validated challenges in the ACME response, as described in section 7.4.1 Pre-authorization [0]. This is planned for the first release of the ACME service.
Another use for it we're planning is to support validating EV and OV certificates using an OOB href/URL. [0] https://ietf-wg-acme.github.io/acme/draft-ietf-acme-acme.html#rfc.section.7.4.1 regards, Robert Kästel On Fri, Dec 1, 2017 at 12:07 AM, Andrew Ayer <[email protected]> wrote: > No objections here. > > Regards, > Andrew > > On Thu, 30 Nov 2017 10:22:56 -0800 > Jacob Hoffman-Andrews <[email protected]> wrote: > > > I agree with this change. It's a good plan to not try and pre-specify > > things like OOB that aren't on anyone's roadmap, because that leaves > > the space open for a better specification once someone wants to > > implement it. > > > > On 11/30/2017 09:39 AM, Clint Wilson wrote: > > > > > > I agree with the reasoning and decision to remove this. > > > While I think it's possible for this challenge type to become useful > > > in the future, I don't have any justification for keeping it in in > > > the meantime. As Daniel notes, it's straightforward to add it back > > > if needed. > > > > > > > > > On Thu, Nov 30, 2017, 10:25 AM Daniel McCarney <[email protected] > > > <mailto:[email protected]>> wrote: > > > > > > > Daniel, please do not merge this until we determine WG > > > >consensus > > > > > > Of course :-) I don't have any merge privileges! > > > > > > On Thu, Nov 30, 2017 at 11:42 AM, Salz, Rich <[email protected] > > > <mailto:[email protected]>> wrote: > > > > > > Does anyone disagree with Daniel’s reasoning? If so, please > > > speak up before next Friday. > > > > > > > > > > > > Daniel, please do not merge this until we determine WG > > > consensus. > > > > > > > > > _______________________________________________ > > > Acme mailing list > > > [email protected] <mailto:[email protected]> > > > https://www.ietf.org/mailman/listinfo/acme > > > > > > > > > > > > _______________________________________________ > > > Acme mailing list > > > [email protected] > > > https://www.ietf.org/mailman/listinfo/acme > > > > _______________________________________________ > Acme mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/acme >
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
