Re: [quicwg/base-drafts] It is unspecified how a server sends Handshake packets during / after migration (#3142)

Kazuho Oku <> Thu, 24 October 2019 03:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D4038120178 for <>; Wed, 23 Oct 2019 20:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Status: No, score=-6.596 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, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 o7soWPLhpFQn for <>; Wed, 23 Oct 2019 20:21:17 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0EA2E12010D for <>; Wed, 23 Oct 2019 20:21:17 -0700 (PDT)
Date: Wed, 23 Oct 2019 20:21:15 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571887275; bh=QGn0/6y/haNC3gqL+5L/RY3/I8WsTTiRFGnUeaKlgkU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=TmA+dFgTVfULxak+rMOx3lzrZib3QlKvOFdbENovdGDmefQ2DG6INRYmcWCD9RrYe unQG68iTd64WOIsjOQNIbuJF3fra3YPmgNOoEMl4FRjEq2eI6rHjCICYYd1c5KE5pD 0ipmnfAfzrcVf96sYyRXz89lSwEl2WTKN3lNqyXw=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3142/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] It is unspecified how a server sends Handshake packets during / after migration (#3142)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db118abcb2a5_55853f81af6cd96c2263c"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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: Thu, 24 Oct 2019 03:21:19 -0000

> The 5-tuple doesn't change during the handshake. That means we should not send Handshake packets down the new path.

I agree.

Assuming that is the case, we need to define a mechanism that allows the server to drop Handshake keys and the path before migration completes, or even better before the sends the first packet in response to a migration attempt. Otherwise, the server would be required to have a special-case for handle the original path.

Proposed solution is #3141.

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