Re: [quicwg/base-drafts] Improve Large Server Certificate Scenario (#3784)
Jana Iyengar <notifications@github.com> Fri, 26 June 2020 01:19 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 641453A10C7 for <quic-issues@ietfa.amsl.com>; Thu, 25 Jun 2020 18:19:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.483
X-Spam-Level:
X-Spam-Status: No, score=-1.483 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 3QKnfaoIYVKi for <quic-issues@ietfa.amsl.com>; Thu, 25 Jun 2020 18:19:29 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE2353A10C0 for <quic-issues@ietf.org>; Thu, 25 Jun 2020 18:19:28 -0700 (PDT)
Received: from github-lowworker-5825cd4.ac4-iad.github.net (github-lowworker-5825cd4.ac4-iad.github.net [10.52.22.68]) by smtp.github.com (Postfix) with ESMTP id 0F5AB660090 for <quic-issues@ietf.org>; Thu, 25 Jun 2020 18:19:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1593134368; bh=uShuQdjAM+NzPBXwtuxGFuIroL/BToRgs82dsUA7Gsk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=uPmRNc0CtuCLwStwhtKv6C2+aUTdYG18afXICIMpWJqSGGNaKgU7vZBuKwzzrf3mZ /UEY8cc2g2SQx8yZFHtC5jGx1eTlciHwDWFRHAKJGSwtWsROjM4N+Wd3OHH8dS0lt/ rpKQTB0DQRMuLk3g/4qbKOxW1gN9QsPUJlHN2J3k=
Date: Thu, 25 Jun 2020 18:19:27 -0700
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6YT63GSR2EGEYQVV55AEXB7EVBNHHCMZSKYY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3784/649895802@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3784@github.com>
References: <quicwg/base-drafts/issues/3784@github.com>
Subject: Re: [quicwg/base-drafts] Improve Large Server Certificate Scenario (#3784)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ef54d1ff3b94_68143f7e936cd9681354c1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/EwKSMShI8stcmUkwK_AH4toLoBU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jun 2020 01:19:31 -0000
(I'll invoke the @mcmanus for his thoughts, since he wrote that article.) At a high level, we should be working on reducing the handshake size, for two reasons: reduced packet loss, and reduced network load. Fewer packets in the handshake is generally good. Compression is aligned with this outcome, and it is not a steep hill. Simply inflating the client's hello goes in exactly the opposite direction. I would suggest that simply moving to QUIC without cert compression was not expected to reduce handshake latency. It was always a critical part of gQUIC, and was always considered a part of the equation for realizing QUIC's potential. That is how I read the article -- that to realize QUIC's promise, cert compression is necessary. Perhaps it might be useful to mention this somewhere in the TLS draft? -- 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/3784#issuecomment-649895802
- [quicwg/base-drafts] Improve Large Server Certifi… Nick Banks
- Re: [quicwg/base-drafts] Improve Large Server Cer… Martin Thomson
- Re: [quicwg/base-drafts] Improve Large Server Cer… Nick Banks
- Re: [quicwg/base-drafts] Improve Large Server Cer… Jana Iyengar
- Re: [quicwg/base-drafts] Improve Large Server Cer… Martin Thomson
- Re: [quicwg/base-drafts] Improve Large Server Cer… Lars Eggert
- Re: [quicwg/base-drafts] Improve Large Server Cer… Lucas Pardue
- Re: [quicwg/base-drafts] Improve Large Server Cer… Lars Eggert
- Re: [quicwg/base-drafts] Improve Large Server Cer… Martin Thomson
- Re: [quicwg/base-drafts] Improve Large Server Cer… Martin Thomson