Re: [quicwg/base-drafts] PATH_* frames are not ACK-eliciting (#2372)

Rui Paulo <> Mon, 28 January 2019 01:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1907B130F2C for <>; Sun, 27 Jan 2019 17:42:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -12.551
X-Spam-Status: No, score=-12.551 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 GquAoPU6EbHe for <>; Sun, 27 Jan 2019 17:42:48 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 71F19130EA4 for <>; Sun, 27 Jan 2019 17:42:48 -0800 (PST)
Date: Sun, 27 Jan 2019 17:42:47 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1548639767; bh=DVbRnD7/PUWcW4y51VshtQ4c9Hq9j12CmG4LEbYODjo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bwkP6VRm47YgRxeZLT0NrOPvxtixuvMx/hRgx3P/IaT7lh9nn40NbOZRPjtNNquaZ zulpB5qoZOHagHB+2xIQqCp52EUc9ynxSq0VocUukREfWFq24u376tP1fBIbSpM/5o Eujlury2ZGq6s+dVn6bze6tYg2YY9YKA+dy/syAc=
From: Rui Paulo <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2372/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] PATH_* frames are not ACK-eliciting (#2372)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c4e5e176ddf3_7f433fb5268d45bc163483f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: rpaulo
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: Mon, 28 Jan 2019 01:42:50 -0000

> Ack-eliciting Frames: All frames besides ACK or PADDING are considered ack-eliciting

I don't know how connection migration would work if PATH_CHALLENGE triggers PATH_RESPONSE+ACK since ACK is a non-probing frame (i.e., it triggers migration).

Or does this mean the PATH_CHALLENGE will be ACK'ed on the "main" path and the PATH_RESPONSE will be sent on the alternative path?

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