On 03/12/2017 12:50 PM, Salz, Rich wrote: > What about saying each certificate SHOULD be a signer on *A* preceding > certificate? This allows us to serve a single cert chain for both MD5 and > SHA1, for example. (Contrived examples of course.) I think the current language (copied from TLS 1.3) conveys that, though it's a bit subtle:
> Each following certificate SHOULD directly certify one preceding it. _______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
