Re: [quicwg/base-drafts] Describe PMTU probing that includes source connection ID for routing … (#2402)

MikkelFJ <> Tue, 05 February 2019 14:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E5AC3130E5D for <>; Tue, 5 Feb 2019 06:34:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -11.149
X-Spam-Status: No, score=-11.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, 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 FAhYivJ0q92k for <>; Tue, 5 Feb 2019 06:34:45 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3D7D41310C1 for <>; Tue, 5 Feb 2019 06:34:45 -0800 (PST)
Date: Tue, 05 Feb 2019 06:34:44 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1549377284; bh=w3Y6TH4qGt/z3gCL6fZnXIXymTyC/3TBqwdIWSgAbD8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tn6AvJo/I68RWPrrwI7j0BsZGNxhCXrAXYlvACrnLcgoSQFNZO1+7Ht6oSpTYXZhW j2bTiRrdik/LB7ISIEqpCCABosDxujfxnF6RnBXeI3mLOuGnIWB+VzRBan29uq3zTV /CKoRm58yzlaKzOzeacWp1JfzwVqvkmcxZQknHOc=
From: MikkelFJ <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2402/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Describe PMTU probing that includes source connection ID for routing … (#2402)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c599f043d908_63083fb1902d45c030357c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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: Tue, 05 Feb 2019 14:34:47 -0000

Better, you cannot send Handshake packets at all when you no longer have the keys, and if you could, they would be open to MiTM because they keys aren't really that secure since the handshake as already been accepted and therefore cannot fail.

So that leaves sending handshake packets with 1-RTT keys, and I couldn't really find where this is prohibited, but I believe the idea is that each packet type identifies an encryption level.

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