On Tue, 6 Jun 2017 09:20:03 +0200 Sean Turner <s...@sn3rd.com> wrote:
> I appears that we’ve got enough consensus/interest to adopt > draft-ghedini-tls-certificate-compression-00 based on the WG session > in Chicago and this thread: Hi, one aspects brought up in that thread was that there is already RFC 7924, which allows certificate caching. There's also AIA, which allows a client to fetch intermediate certificates, however as far as I can see there's no way for a server to decide whether a client supports AIA. All of these technologies seem to try to tackle the same problem: reduce the burden of transmitting certificates. I wonder if there should be more a big picture discussion here. If clients have a good way of caching certificates - would that mean transmitting them is so rare that compressing becomes unnecessary? Also regarding 7924: I tried to find out what server and client software supports that. I didn't find anything. One could see that as an indication that it's not a big deal after all. If people are concerned about the data wasted by transmitting certificates, I wonder if it wouldn't be a more important issue to implement the already existing tech that's available instead of inventing new tech. -- Hanno Böck https://hboeck.de/ mail/jabber: ha...@hboeck.de GPG: FE73757FA60E4E21B937579FA5880072BBB51E42 _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
