Subject: Re: [quicwg/base-drafts] Certificate compression (#134)
From: Alessandro Ghedini <[email-masked]>
To: quicwg/base-drafts <[email-masked]>
Cc: Subscribed <[email-masked]>
Date: Tue, 10 Jan 2017 03:27:19 -0800
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>

FTR I raised the issue on the TLS list [here](https://www.ietf.org/mail-archive/web/tls/current/msg22065.html), however the main response was "compression is scary", but it could just be due to lack of details on my part.

Unfortunately I haven't been able to find the time to do any experimenting (or indeed reply to the mail thread), and haven't heard from Victor.

As for caching, it seems to me RFC7924 is quite a bit less flexible than what we have in Google QUIC (namely, you can only cache full chains, not single entries AFAICT, so e.g. you can't just cache intermediates), but again haven't been able to do any experimenting.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/134#issuecomment-271552046