IETF Logo Mail Archive

Re: [quicwg/base-drafts] Clarify path validation and connection migration (#4102)

ianswett <notifications@github.com> Tue, 22 September 2020 22:05 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C7F63A09D6 for <quic-issues@ietfa.amsl.com>; Tue, 22 Sep 2020 15:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.177
X-Spam-Level:
X-Spam-Status: No, score=-3.177 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.695, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, 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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mGzt7LoJx8vA for <quic-issues@ietfa.amsl.com>; Tue, 22 Sep 2020 15:05:46 -0700 (PDT)
Received: from out-26.smtp.github.com (out-26.smtp.github.com [192.30.252.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C2DC3A0A78 for <quic-issues@ietf.org>; Tue, 22 Sep 2020 15:05:46 -0700 (PDT)
Received: from github-lowworker-292e294.va3-iad.github.net (github-lowworker-292e294.va3-iad.github.net [10.48.102.70]) by smtp.github.com (Postfix) with ESMTP id 4A1B35E00AA for <quic-issues@ietf.org>; Tue, 22 Sep 2020 15:05:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1600812345; bh=PZMa5kWTMUX+0NJul5QiZhOZmuOCByAIexCJ0osCz7M=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lADthoemlpEg+Rh8BMI+7bc+klqVoFnTh3YdHXGNYZYbxcwYlR30mCV8laN4sEBfo H6YN+TPDL9a1lU/aF3M05uNGAK+PQM/G+UKkKD3tVo06aXQ2L1NhXlhwQVNkiIdyeM 14uyHFavt6DEpoUwFC2xa61YDA0uxuktwR1xz1Gw=
Date: Tue, 22 Sep 2020 15:05:45 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6O73PU66IYNQ7QUJ55OZLDTEVBNHHCTXOHHI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/4102/review/493879328@github.com>
In-Reply-To: <quicwg/base-drafts/pull/4102@github.com>
References: <quicwg/base-drafts/pull/4102@github.com>
Subject: Re: [quicwg/base-drafts] Clarify path validation and connection migration (#4102)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f6a75393adbe_7e1919f03772c4"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/68ocgiAidWwp-7XVuhqdRaUzXZE>
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: Tue, 22 Sep 2020 22:05:47 -0000

@ianswett commented on this pull request.



> @@ -2314,33 +2320,31 @@ Therefore, a migrating endpoint can send to its peer knowing that the peer is
 willing to receive at the peer's current address. Thus an endpoint can migrate
 to a new local address without first validating the peer's address.
 
+To establish reachability on the new path, an endpoint initiates path
+validation ({{migrate-validate}}) on the new path.  An endpoint MAY defer path
+validation until after a peer sends the next non-probing frame to its new
+address.

Agreed. @ekinnear if you have text in mind, would you mind writing a PR to add your preferred clarification?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/4102#discussion_r493060202

v2.23.0 | Report a Bug | By Email