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

Eric Kinnear <> Thu, 24 October 2019 05:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B01E112000F for <>; Wed, 23 Oct 2019 22:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RLHqoA3Lmmp7 for <>; Wed, 23 Oct 2019 22:56:45 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id ECFB61207FE for <>; Wed, 23 Oct 2019 22:56:44 -0700 (PDT)
Date: Wed, 23 Oct 2019 22:56:43 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1571896604; bh=JM/qeBXY3L9jzMFoh3cwtARLzw8SK/8DR5jHJjSVMgc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wsL1sguP9wuu919A+duwPKaI5yj7XeFkH1pZZLhOUuo+b60AwTQm9dTmlnKI9kcVZ C9UnMuAxQMJjyate+BIxAppr9adTaUU9dEiH0ImjpwPigxYvzvE0gw7Q5xJZ5Lr5Jf Cy5LqrO16ts0NPBzC/hbzQ6yqF67E484TZP6DXpk=
From: Eric Kinnear <>
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_5db13d1be486f_23eb3ffa6a0cd95c3074bc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: erickinnear
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 05:56:47 -0000

I think this comes back to a lot of what @huitema was bringing up during the interim -- there are other things that rely on having a explicit signal for the handshake being entirely complete, and this is one of them. 

Having a well-defined moment where we're entirely done and can move on from Handshake packets would make this a lot nicer.

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