Re: [quicwg/base-drafts] TP to disable migration (#1447)

Martin Thomson <notifications@github.com> Fri, 15 June 2018 16:37 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 CE850130E22 for <quic-issues@ietfa.amsl.com>; Fri, 15 Jun 2018 09:37:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 3wi0PDIWiw5j for <quic-issues@ietfa.amsl.com>; Fri, 15 Jun 2018 09:37:01 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DCD5130DC0 for <quic-issues@ietf.org>; Fri, 15 Jun 2018 09:37:01 -0700 (PDT)
Date: Fri, 15 Jun 2018 09:37:00 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1529080620; bh=d5hn2yELAvt7hCymTXupzfzQCEsJEFy4s5JXbTctisg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=QP4qcBdPZGlOyFpJjgC/J/Kh3f58T/9N9yAXF5+QwyfwLqfrvLMdIhGrdidsF2gyd ce02rnv37m2MpIdLOLyp4Q2/di/rLv8o1l+1tMKdGl0IEWFHYzWIxbI0h6Zi4I8ylV mhKLijnsprftrnkWzmmZW6FCPvO+eHBad3Q/o8ZQ=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf588122e200c8248c4e2bc00f35494b2dd48d81892cf00000001173bad2c92a169ce13d3250f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1447/c397676602@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1447@github.com>
References: <quicwg/base-drafts/pull/1447@github.com>
Subject: Re: [quicwg/base-drafts] TP to disable migration (#1447)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b23eb2c866b3_5b2e2b2222eeef5c347270"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/8qgwo6XazQfAfzq6L8q9rn8S6m4>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.26
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: Fri, 15 Jun 2018 16:37:03 -0000

@pravb, I didn't say anything about multiple connection IDs on the same address.  I'm not sure how it has any bearing on this, other than to say that if you don't provide connection IDs, this won't happen.  But here's the thing I don't get: if you are routing based solely on 5-tuple, why use connection IDs at all?

If we want a keep-alive function, then we should explicitly build one.

-- 
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/1447#issuecomment-397676602