Re: [TLS] Certificate Compression: Add Zstd Code Point?

"W. Felix Handte" <w@felixhandte.com> Mon, 13 May 2019 16:55 UTC

Return-Path: <w@felixhandte.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 016D5120135 for <tls@ietfa.amsl.com>; Mon, 13 May 2019 09:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I-WQ_H7yp3s3 for <tls@ietfa.amsl.com>; Mon, 13 May 2019 09:55:18 -0700 (PDT)
Received: from mail.felixhandte.com (felixhandte.com [54.172.180.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D46412004F for <tls@ietf.org>; Mon, 13 May 2019 09:55:18 -0700 (PDT)
Received: from [172.30.220.221] (unknown [163.114.130.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.felixhandte.com (Postfix) with ESMTPSA id 0990E2EAFD; Mon, 13 May 2019 16:55:16 +0000 (UTC)
To: Alessandro Ghedini <alessandro@ghedini.me>, Victor Vasiliev <vasilvv@google.com>
Cc: "tls@ietf.org" <tls@ietf.org>
References: <270001f2-1b81-652c-8f43-f03d9b00ac2a@felixhandte.com> <CAAZdMaet_vUGN-iz5uuErhuNf71DbT57Wq6wJ+bsCcMJuqEWjg@mail.gmail.com> <20190404204542.GA7403@pinky.flat11.house>
From: "W. Felix Handte" <w@felixhandte.com>
Message-ID: <aec9bcc8-a107-0e6c-df97-bb648fab4955@felixhandte.com>
Date: Mon, 13 May 2019 12:55:16 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <20190404204542.GA7403@pinky.flat11.house>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/idYj6mgvrlYBbdSfAOcw19pOv4A>
Subject: Re: [TLS] Certificate Compression: Add Zstd Code Point?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2019 16:55:20 -0000

Hey all,

In case anyone is interested in testing inter-operability:

I've landed support for Zstd certificate compression in Facebook's 
implementation of TLS 1.3 [1]. I've also deployed that support to 
Facebook's servers.

Best,
Felix

[1] https://github.com/facebookincubator/fizz

On 4/4/19 4:45 PM, Alessandro Ghedini wrote:
> On Mon, Apr 01, 2019 at 06:09:16PM -0400, Victor Vasiliev wrote:
>> This sounds reasonable to me.  I currently don't have a plan for
>> implementing this, but since zstd is well-defined and has an RFC published
>> (that I can easily cite), I see no reason not to add it.
>>
>> I wrote up a PR: https://github.com/tlswg/certificate-compression/pull/26.
>> I will merge it before the last call, unless there are objections.
> 
> This seems pretty inoffensive (just one more allocated codepoint), and it's
> already been a few days and nobody seems to object.
> 
> We'd like to submit a new draft version so we can finally go to WGLC, so if
> nobody objects by tomorrow I'll just merge the PR and upload the draft.
> 
> Cheers
>