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

Kazuho Oku <notifications@github.com> Thu, 24 October 2019 02:25 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 31B5A120122 for <quic-issues@ietfa.amsl.com>; Wed, 23 Oct 2019 19:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Status: No, score=-6.382 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_24=1.618, 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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id aE061xTjUReL for <quic-issues@ietfa.amsl.com>; Wed, 23 Oct 2019 19:25:30 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F17112010D for <quic-issues@ietf.org>; Wed, 23 Oct 2019 19:25:30 -0700 (PDT)
Received: from github-lowworker-c53a806.ac4-iad.github.net (github-lowworker-c53a806.ac4-iad.github.net []) by smtp.github.com (Postfix) with ESMTP id 75603C61F90 for <quic-issues@ietf.org>; Wed, 23 Oct 2019 19:25:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571883929; bh=tlZxkxVhPdEWqgtf5kxupUZP778HIqnxKKm6CvKkjMI=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=pAXm22DNNmJd4iHLRqGfs23l1ka6b667h5ZJbl2x+hcAnXcto2rkVbvzSXD8y7k28 v/JRnx+52q6gc46soK4tyg/z29ILg5tsRJiVtY99g8N9v3J4UngObwKzwSn/nhqn+x w19ygfcbCt7CNPXu65wyCQsVlVK/NlNmh3uaEz84=
Date: Wed, 23 Oct 2019 19:25:29 -0700
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2XPN5LFQ2EB7UMA5F3XY7BTEVBNHHB473CTE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3142@github.com>
Subject: [quicwg/base-drafts] It is unspecified how a server should send Handshake packets during / after migration (#3142)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db10b99661f3_61673f9d70ccd95c2905f"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Nm7CxICTwuHUhCcyqze79yYO0vw>
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: Thu, 24 Oct 2019 02:25:32 -0000

At the moment, each endpoint reaches handshake confirmed by it's own.

That means that, a client might confirm the handshake and initiate a migration, and that migration might complete, while the server is transmitting Handshake packets, in case the 1-RTT acks sent by the client is repeatedly lost. This is a possibility, as we do not require 1-RTT acks to be bundled with packets carrying PATH_CHALLENGE or PATH_RESPONSE frames.

However, we do not specify if the path used for sending Handshake packets migrate or continue to use the old path. In case it is the former, we also need to specify how the server fills in the SCID field of the Handshake packets it sends.

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