IETF Logo Mail Archive

Re: [quicwg/base-drafts] Do I need to reset congestion info when the port changes? (#3842)

Christian Huitema <notifications@github.com> Mon, 13 July 2020 00:45 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 953843A0BF7 for <quic-issues@ietfa.amsl.com>; Sun, 12 Jul 2020 17:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level:
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[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_20=0.7, 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 oWszumQD7oLk for <quic-issues@ietfa.amsl.com>; Sun, 12 Jul 2020 17:45:30 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79D723A0BF4 for <quic-issues@ietf.org>; Sun, 12 Jul 2020 17:45:30 -0700 (PDT)
Received: from github-lowworker-cd7bc13.ac4-iad.github.net (github-lowworker-cd7bc13.ac4-iad.github.net [10.52.25.102]) by smtp.github.com (Postfix) with ESMTP id 95FAF6A1020 for <quic-issues@ietf.org>; Sun, 12 Jul 2020 17:45:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594601129; bh=5RCBY7oAGT95a1VnO5/RKmhSa84D6sFrLclPW7i3KcQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WltLVvWqiTSRcy4rxFR+4P7NYy9KM9Py8+J9jQ4KtM0/k6DyBN3AqUSht2swLlAYi NN8lz20k8GftC3Sd6szgvAAtbe5okJ3DlNDtCnoTrANKQSCHyAgrcnRrlDvCVe1edx /2cuAFyi9D5isUKxAgYmdBLSHk6YXAAnI3D/wbow=
Date: Sun, 12 Jul 2020 17:45:29 -0700
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3GWUQFDR6CQ6K7S6N5C6H2TEVBNHHCN2JJGQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3842/657303214@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3842@github.com>
References: <quicwg/base-drafts/issues/3842@github.com>
Subject: Re: [quicwg/base-drafts] Do I need to reset congestion info when the port changes? (#3842)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f0baea986e17_75443fab8d2cd9682964b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/H_Ee5TuijBGXI20DctkQMv__Ijw>
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: Mon, 13 Jul 2020 00:45:36 -0000

@janaiyengar we might debate how safe it is to keep sending as if nothing changed. There is some risk of creating a spike of congestion on the new path if the assessment was wrong. On the other hand, doing that when "just the port changed" will work most of the time, especially if the congestion controller already shrinks the window after the link goes idle, which many do. So in the hand I agree that we are probably better off just keeping the existing text.

-- 
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/3842#issuecomment-657303214

v2.27.6 | Report a Bug | By Email | System Status