Re: [quicwg/base-drafts] Can PATH_RESPONSE be sent on a different path than PATH_CHALLENGE? (#4064)

Martin Thomson <> Wed, 02 September 2020 02:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F02303A09EB for <>; Tue, 1 Sep 2020 19:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Status: No, score=-2.009 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, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 DhGOjlW7vHDE for <>; Tue, 1 Sep 2020 19:01:39 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D72753A09E8 for <>; Tue, 1 Sep 2020 19:01:39 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 28CF890265A for <>; Tue, 1 Sep 2020 19:01:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1599012099; bh=M2Y6lK98Mm8GsNrHbrM1RtiRfCsxpCIVeaBmczNMeKw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=mmkoflovytfP7GIPNXwrmXwaE8nIAivHmsO58rXfpLwOy5dEZhZCO+7nLI5wG8WFp pqTjMhdrRY5u1FWaT1BmCN02IqPIdRP0v1P4Qc/5Rx4Pvnj0CNeRSUuucY4WWJwM9C hKoe6jpy1YV8zUvl1tY4d3odKpsFWe7S3q3tKrqg=
Date: Tue, 01 Sep 2020 19:01:39 -0700
From: Martin Thomson <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/4064/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Can PATH_RESPONSE be sent on a different path than PATH_CHALLENGE? (#4064)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f4efd031969d_2828196428789"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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: Wed, 02 Sep 2020 02:01:41 -0000

Thanks for being so prompt David.  I will leave this for a bit to allow others a chance to spot errors, but I plan to merge this before we publish -30 (real soon now, I hope).

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