Ah, thanks for the feedback! The certificates in Appendix A aren't showing anything particularly unique to the new protocol, they exist solely to be referenced by Section 4.1 <https://www.ietf.org/archive/id/draft-aaron-acme-ari-03.html#section-4.1> so that a reader can confirm that the request path used in the example there is properly constructed. I'd be happy to drop them entirely if there's a better way to provide data to build examples from.
Aaron On Sat, Jul 30, 2022 at 1:31 PM Russ Housley <[email protected]> wrote: > I have no objection to adoption, but I do think that Appendix A needs more > explanatory text to tell what these examples are showing. > > Russ > > > > On Jul 28, 2022, at 8:12 PM, Deb Cooley <[email protected]> wrote: > > > > At the working group session today, we did a quick count for those who > agreed to adopt this draft. This message is to follow up on this list. If > anyone disagrees with adoption of this draft, please speak up by 12 August. > > > > Many thanks, > > > > Deb Cooley > > _______________________________________________ > > 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
