Re: [quicwg/base-drafts] 5-tuple routing and SPA (#3608)
David Schinazi <notifications@github.com> Tue, 05 May 2020 20:19 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 B0ED13A09D9 for <quic-issues@ietfa.amsl.com>; Tue, 5 May 2020 13:19:14 -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 QejaToPYK0hB for <quic-issues@ietfa.amsl.com>; Tue, 5 May 2020 13:19:12 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B430A3A09D6 for <quic-issues@ietf.org>; Tue, 5 May 2020 13:19:12 -0700 (PDT)
Received: from github-lowworker-edec459.ac4-iad.github.net (github-lowworker-edec459.ac4-iad.github.net [10.52.18.32]) by smtp.github.com (Postfix) with ESMTP id E972D6602AD for <quic-issues@ietf.org>; Tue, 5 May 2020 13:19:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1588709951; bh=IHh3xBgjCpLEaNef5hqiW8yG5So5XMQVZu1hIYX8dhk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VTLcNM2d+fFHDRZ31jPop6weQ0SnydpUnvSx78vM9L7zLDEhmbyJ1pNDvVtSCLhIn gLM+DWRG1kFHDBO7YlnirewkzhOLFzAb3LWAZiLkY+tWs83584XbgFf5uSTteAnBA9 1AFZhOb0x1UUMyWTesHV5gyE0BwRa3liSvPoW5Wg=
Date: Tue, 05 May 2020 13:19:11 -0700
From: David Schinazi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7LGXUL3YGY2OJQULV4XWVT7EVBNHHCITYZTQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3608/624283935@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3608@github.com>
References: <quicwg/base-drafts/issues/3608@github.com>
Subject: Re: [quicwg/base-drafts] 5-tuple routing and SPA (#3608)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5eb1ca3fda01a_28d23ff9046cd96810786ea"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
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/8rKMKO5OQorUYscrz0aq3tu6TVA>
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, 05 May 2020 20:19:15 -0000
I personally find the proposed change confusing. I'm not sure I find the use-case of "my original address doesn't support migration but my preferred address does" compelling. Since this can be easily solved by an extension with no downside over it being in the core docs, I don't see a reason to change the spec at this point in the process. -- 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/3608#issuecomment-624283935
- [quicwg/base-drafts] 5-tuple routing and SPA (#36… Mike Bishop
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … ianswett
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Eric Kinnear
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Eric Kinnear
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Kazuho Oku
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Mike Bishop
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Kazuho Oku
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … ianswett
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Kazuho Oku
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Martin Thomson
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … ianswett
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Martin Thomson
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … ianswett
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Mike Bishop
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … ianswett
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … David Schinazi
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Martin Thomson
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Kazuho Oku
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … ianswett
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … ianswett
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Jana Iyengar
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … David Schinazi
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Kazuho Oku
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … David Schinazi
- Re: [quicwg/base-drafts] 5-tuple routing and SPA … Martin Thomson