IETF Logo Mail Archive

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

ekr <notifications@github.com> Wed, 08 July 2020 12:41 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 ED2DE3A099B for <quic-issues@ietfa.amsl.com>; Wed, 8 Jul 2020 05:41:55 -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 irnzhkgi6WcM for <quic-issues@ietfa.amsl.com>; Wed, 8 Jul 2020 05:41:54 -0700 (PDT)
Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EED63A0995 for <quic-issues@ietf.org>; Wed, 8 Jul 2020 05:41:54 -0700 (PDT)
Received: from github-lowworker-2300405.va3-iad.github.net (github-lowworker-2300405.va3-iad.github.net [10.48.17.39]) by smtp.github.com (Postfix) with ESMTP id 58E8E8C05E4 for <quic-issues@ietf.org>; Wed, 8 Jul 2020 05:41:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594212113; bh=fUFWnLm/4j+bnb1J+25DfIkNuy1VWuCC/X7Bi6Y5WQ4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=y+j25BuyHQi1iYElmsHXRfKX9VMyvyZotrQ4TTNPJ3ZvQXgODo76uWzwMNPb0PLyS hNEWMI5IpCVgcxOWWcsNBelgpB1i8wLha8wdSKSN7VhByfVGX6FCGZJkwgEGZ+lxv4 rzLSymfHV3zajty9/YSp/GLVQ4COdYX7zcO82d5o=
Date: Wed, 08 Jul 2020 05:41:53 -0700
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4CIORZPEZICDQA2W55CGQBDEVBNHHCN2JJGQ@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/655494462@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_5f05bf1148ec3_3cef3fcd50acd96c839a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/zlhCw_TDbSd0oBvgNkL1zc6SQ0E>
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, 08 Jul 2020 12:41:56 -0000

I see what you mean, but I think that this kind of hinting at the user without explicitly stating it does a disservice to the implementor, who then needs to figure it out for themselves. IMO we should explicitly state the exceptions that the WG believes are permissible and then add this escape hatch 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-655494462

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