Re: [quicwg/base-drafts] Improve Large Server Certificate Scenario (#3784)
Martin Thomson <notifications@github.com> Wed, 24 June 2020 01:35 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 7AAF13A0D72 for <quic-issues@ietfa.amsl.com>; Tue, 23 Jun 2020 18:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Level:
X-Spam-Status: No, score=-2.008 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_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 YZKZHAmK44hP for <quic-issues@ietfa.amsl.com>; Tue, 23 Jun 2020 18:35:09 -0700 (PDT)
Received: from out-9.smtp.github.com (out-9.smtp.github.com [192.30.254.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6777C3A0D71 for <quic-issues@ietf.org>; Tue, 23 Jun 2020 18:35:09 -0700 (PDT)
Received: from github-lowworker-e8b54ca.ac4-iad.github.net (github-lowworker-e8b54ca.ac4-iad.github.net [10.52.23.39]) by smtp.github.com (Postfix) with ESMTP id C1744261572 for <quic-issues@ietf.org>; Tue, 23 Jun 2020 18:35:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1592962508; bh=4USYUWPN48cRJ0gRwDL8QrDkxPEuUITfOvbdQB0m15Q=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=sjew6PdFfMI/BNNzGSHYnQxGqia4MatOZWthN523wH9EuDikCCXYBpEQWcdg/NJOx 2LFMbnsnrWsjUlUDAMmxKdFD4ojChAnJsAwcywyDcRfzr7w37UsGx+4JIHF+81GmeQ 6dTGy2/v/9dQXaFkTmFXUzBFooUErBaFCDC7BYtw=
Date: Tue, 23 Jun 2020 18:35:08 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6KKMULQHFE5TOA3YF472HMZEVBNHHCMZSKYY@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/648530057@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_5ef2adcc9c37e_311b3fe766ccd96c6327b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/3EwiQEpwWYgfNgrYWBnfkYKJF_o>
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: Wed, 24 Jun 2020 01:35:10 -0000
How much of this requires specification, as opposed to clients just doing stuff? And how much would relieving this pressure just remove an incentive on servers to have smaller certificates? I mean, if you have a giant certificate, then you get TCP-level performance, maybe that's OK. -- 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-648530057
- [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