Brian Campbell <bcampb...@pingidentity.com> wrote:
> My aim with something-something-
>
<https://datatracker.ietf.org/doc/draft-bdc-something-something-certificate/>
> certificate
>
<https://datatracker.ietf.org/doc/draft-bdc-something-something-certificate/>
> is/was to address a narrow but existing need by documenting current
> practice while introducing enough commonality to the header name and its
> content/encoding so as to facilitate relatively simple interoperability
> between independently developed systems. I see where you are going with
> this boiling of a small lake but it's well beyond the scope of the kind of
> solution I'd envisioned or think would be practically deployed and useful
> in any meaningful numbers.I agree with you. I think it's useful to think about what the next step of complexity would be in order to understand the ROI for this simiplicity. I think that a key line is figuring out how/if the certificate chain will be provided with the simplest design. -- Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
_______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
