Re: [quicwg/base-drafts] Move/duplicate no server migration text (#4063)

Mike Bishop <notifications@github.com> Wed, 02 September 2020 19:21 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 ADB623A0CF8 for <quic-issues@ietfa.amsl.com>; Wed, 2 Sep 2020 12:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
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: 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 w00AWPfJdrZQ for <quic-issues@ietfa.amsl.com>; Wed, 2 Sep 2020 12:21:03 -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 C35853A0CE9 for <quic-issues@ietf.org>; Wed, 2 Sep 2020 12:21:03 -0700 (PDT)
Received: from github-lowworker-6349a71.ac4-iad.github.net (github-lowworker-6349a71.ac4-iad.github.net [10.52.18.20]) by smtp.github.com (Postfix) with ESMTP id 1439F5E005C for <quic-issues@ietf.org>; Wed, 2 Sep 2020 12:21:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1599074463; bh=FmdPSjY04ZOBdXAGUE3TaKt51/xq41HIb7YUIp+8Lc8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NVuS+GQnzJeiW+hFCAWtGpcaLehBSDHFNmuz4RKDh/QJ7WcCizBbAboB2Foyl19xe 2dV3wpHVZNGXseTwt2p+G0twS10FFjN+fPaTBeW7JhdU7Dcx1YphqjCBYfks+Uxy8V ybCktGyKalrZKHHvZr4CdIqNHK5E5FwDR3GRAxj8=
Date: Wed, 02 Sep 2020 12:21:03 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZ3H7FR7S5WB5LR6EF5LPIZ7EVBNHHCSFTCVQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4063/685945667@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4063@github.com>
References: <quicwg/base-drafts/issues/4063@github.com>
Subject: Re: [quicwg/base-drafts] Move/duplicate no server migration text (#4063)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f4ff09f4b7a_5b0e19f02948c1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/oNh6cdHfG2uF8xolHu33F-LQIzU>
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: Wed, 02 Sep 2020 19:21:07 -0000

The intent was to keep the path validation mechanisms generic so that an extension could potentially introduce server migration later.  It's stated in 9.6 and the top of 9; before and after the generic part seems sufficient to me.  That said, I think the server migration extension would still require that the client be the one to actually make the change.  Only clients should ever spontaneously send from a new address.  (P2P scenarios notwithstanding....)

-- 
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/issues/4063#issuecomment-685945667