Re: [quicwg/base-drafts] 5tuple routing (#3536)

martinduke <notifications@github.com> Fri, 27 March 2020 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 78B153A0E0F for <quic-issues@ietfa.amsl.com>; Fri, 27 Mar 2020 09:37:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.482
X-Spam-Level:
X-Spam-Status: No, score=-1.482 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, 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 ARQ8YweyKu8D for <quic-issues@ietfa.amsl.com>; Fri, 27 Mar 2020 09:37:19 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE3B63A0BCB for <quic-issues@ietf.org>; Fri, 27 Mar 2020 09:33:56 -0700 (PDT)
Date: Fri, 27 Mar 2020 09:33:55 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1585326835; bh=QvUbw7WTBLmnDjiDNjEcRn/Ml4Dnj2OOsQZLPyt0bxE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=L/I7V0Woziq5zkPSMLnfLfrdCfJRWa3uR57dgF2UPh6X4r1w3oWKmKX9UQpRseHTt QDkFtmreWjmuXtq0vPu5rPo29Frd84eZGQkNo6kHaw4dEJawIJofR/nzfPkBWx1iky 1Ubh9YGCGQWIV6KCPvnmtqhCTnJZJall6zY39gQc=
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK34YMXBS3HBM63MV254RIF7HEVBNHHCFYX2PM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3536/c605097700@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3536@github.com>
References: <quicwg/base-drafts/pull/3536@github.com>
Subject: Re: [quicwg/base-drafts] 5tuple routing (#3536)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e7e2af3d298b_726a3f8d25ccd96c265372"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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/v-DtftK1KpznNTm8Ro8G3GUwZjU>
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: Fri, 27 Mar 2020 16:37:21 -0000

Unfortunately, some of the reviews are hidden as obsolete. I want to respond to this by @martinthomson about disable_migration

> 
> I agree with Ian. If this is the concrete recommendation, then advise that the idle timeout is set accordingly.
> 
> I don't think that this should be on the client to recognize.
> 
> The problem with a recommendation like this is that it could lead to terrible battery performance on devices. Client's now need to recognize that.

I tried to not recommend anything here except to send disable_migration. The client is going to decide what to do with regard to NAT rebinding. If wired, I probably send more PINGs or something. If wireless, maybe not. If I'm quite sure I'm not behind a NAT, I probably do nothing. There's nothing normative here but to send the TP, so if people hate this I can just delete the explanation.


-- 
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/3536#issuecomment-605097700