On Thu, 23 Sep 2021 09:39:24 -0400 Andrew Ayer <[email protected]> wrote:
> > This sounds to me like a point in favor of having the proposal > > specify how the renewalInfo url is constructed, such that clients > > don't have to cache it on-disk, and such that it could be > > constructed by third parties as well. > > Correct. I received a comment off-list that mandating a URL format would run afoul of BCP 190. Fortunately, that restriction was loosened in 2020 by RFC 8820, and it's now acceptable for protocols to specify a URL structure as long as it's under a path that the server is allowed to pick. For instance, it would be fine to specify that the ARI URL is constructed by appending the certificate serial number to a URL specified in the ACME directory. Regards, Andrew _______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
