I support adoption, and I am willing to review.
I note that this document defines the Certificate structure as:
struct {
uint24 uncompressed_length;
opaque compressed_certificate_message<1..2^24-1>;
} Certificate;
However, the current TLS 1.3 already defines a Certificate structure as:
struct {
opaque certificate_request_context<0..2^8-1>;
CertificateEntry certificate_list<0..2^24-1>;
} Certificate;
I think the one in this document should be renamed.
Russ
> On May 16, 2017, at 8:52 AM, Sean Turner <[email protected]> wrote:
>
> All,
>
> At the IETF 98 meeting in Chicago, there was support in the room to adopt
> https://datatracker.ietf.org/doc/draft-ghedini-tls-certificate-compression/.
> We are looking for feedback on adopting this draft form the list. Please
> respond if you support the draft and are willing to review it. If you object
> to its adoption, please let us know why. Please respond to the list by
> 20170530.
>
> Cheers,
>
> J&S
>
> Apologies - we dropped the ball on this adoption call, the call should have
> gone out with the others.
> _______________________________________________
> TLS mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/tls
_______________________________________________
TLS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tls
