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

ekr <> Wed, 12 December 2018 02:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 78D2F131048 for <>; Tue, 11 Dec 2018 18:35:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -9.46
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nFWhMcymksJO for <>; Tue, 11 Dec 2018 18:35:09 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7859C131060 for <>; Tue, 11 Dec 2018 18:35:09 -0800 (PST)
Date: Tue, 11 Dec 2018 18:35:08 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1544582108; bh=H2wHV2EksA/m/DWr139Ao7/05W6yiFPj8jGV4YMMXic=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gv1e9iyVb3wEO7XJdEHWPOPJ3izzuz4dtYUo6TEde1QAk4f292lm758WrVhrxN9kT w/4qD53QMcWqdeiu/Hh930+LCKZ53pKFvHxBmpsKQTn8unFfBYkS4eWUPL/34zSbXy mwc4LAxVEIOzGIqMReupxdFiRj8o8PSb9dufvVb0=
From: ekr <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2045/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Discard Initial keys as soon as possible (#2045)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1073dc182e8_2b8b3f974ced45b83773bd"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 12 Dec 2018 02:35:19 -0000

I'm not sure we need to address it in QUICv1 at all. Rather than piecemeal
fixes, I'd like to start with a clear agreement about what the proposed
threat model is for man on the side attacks. Once we've got consensus on
that, we can then fix all the attacks that are implicated by that threat

On Tue, Dec 11, 2018 at 6:31 PM ianswett <> wrote:

> @ekr <> Clarification question: Do you think this
> is an issue we should just not address in QUIC v1 or there are other
> solutions not in this PR?
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <>,
> or mute the thread
> <>
> .

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: