Re: [quicwg/base-drafts] Stop requiring remote address to match during path validation (#2637)

Eric Kinnear <> Wed, 08 May 2019 01:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7775F12006E for <>; Tue, 7 May 2019 18:08:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 V9gJDKOmwXrZ for <>; Tue, 7 May 2019 18:08:07 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CBD7B12004D for <>; Tue, 7 May 2019 18:08:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=FWB2OoYj0oNNoJ8XueCeFk9tJl4=; b=IkCkmD35KhVu5m2h 9BQ1A6aDOCfUOD9EemdQk2bz4C7tP6RZAD4xxoHKyrMtOx3hTTB4MZY9GHTun1dz HuQVYFoWMwfmquHljEEJIP1GMYvgi27RoB2a9lIL+1m4E9/lox01SnkqFFJOWo9L bJuMt9dInrbw+NbOcBLXcCZu/NY=
Received: by with SMTP id filter0326p1iad2-6452-5CD22BF5-1E 2019-05-08 01:08:05.51612338 +0000 UTC m=+1050475.484487757
Received: from (unknown []) by (SG) with ESMTP id DK_xWiviR2Comnd-MPrIBg for <>; Wed, 08 May 2019 01:08:05.618 +0000 (UTC)
Received: from (localhost []) by (Postfix) with ESMTP id 9778E160318 for <>; Tue, 7 May 2019 18:08:05 -0700 (PDT)
Date: Wed, 08 May 2019 01:08:05 +0000
From: Eric Kinnear <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2637/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Stop requiring remote address to match during path validation (#2637)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cd22bf595eaf_716f3ff5af0cd96c1086e8"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak38tarqBcVTIhy/clfBqr2deAOSWgYSl+qzMD f9cuPvp0VcUVExMMQC5RrRJJluW0GPxIhHyB95RV9BD6Ed15pEJFwgzgihwiiqwQKkhC6ZVKJDwtL+ GhFJ8oSbxa9hV3IMIs51R2hF3oWghhQMkIOQ4XTDFK98iLsS3s/IKRxO35WTsR/TBN8lfKZXY4INAJ 8=
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, 08 May 2019 01:08:08 -0000

One other section, can we leave this as-is?
Section 8.4
To ensure that packets can be both sent to and received from the peer, the 
PATH_RESPONSE MUST be sent on the same path as the triggering 
PATH_CHALLENGE. That is, from the same local address on which
 the PATH_CHALLENGE was received, to the same remote address 
from which the PATH_CHALLENGE was received.

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