Re: [quicwg/base-drafts] Discard Initial keys as soon as possible (#2045)

Christian Huitema <notifications@github.com> Mon, 26 November 2018 19:15 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 01F4F130F59 for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 11:15:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 EmOs79jCrv9e for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 11:15:55 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CBF7130E9E for <quic-issues@ietf.org>; Mon, 26 Nov 2018 11:15:55 -0800 (PST)
Date: Mon, 26 Nov 2018 11:15:54 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543259754; bh=GBlkR6dZVIj76ity00UuaiXn5pju1io4lMUIsQHSRvc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=s8C7Ov4n+yIEdSuW/a626W3XhvHOace6XFK6B6rjDURpqGYXvHvvW7He27iLAnyUu O+kHyajHuYFxTfTqj6zzeRyYFOdrrRFH/NuLMUtumfBd4nmoHtht6Xu84hcDMU+6rc c3Uoxer5f0BGHwRUURZ3/Cjy6o6PzvMlfVQd5y6I=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abce129fdd9f3e6fa6e06d53d9cf6728c36b77a35a92cf000000011814086a92a169ce16de7e61@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2045/c441761641@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2045@github.com>
References: <quicwg/base-drafts/pull/2045@github.com>
Subject: Re: [quicwg/base-drafts] Discard Initial keys as soon as possible (#2045)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bfc466acc7a7_50663fa5e3ad45bc6044af"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/JgKlEVF9YwMZNA8VNGVQJ47g5Ok>
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: Mon, 26 Nov 2018 19:15:57 -0000

@ianswett the main problem with "no ACK" is that we will need special handling of retransmissions on the server. The server would need to trigger retransmission of Initial packets upon reception of a duplicate CH, and that's clearly some new ad hoc code. 

Also, what if the server does not like any of the key shares proposed in the Client Hello? Client sends CH1, server replies with HRR, client sends a modified CH2, server sends SH. If the client repeats CH1, the server should repeat HRR; if the client repeats CH2, the server needs to repeat the CH. I assume this could work if the client always coalesced an ACK with CH2, but this coalescing is optional, not mandated.

-- 
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/pull/2045#issuecomment-441761641