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

Jana Iyengar <notifications@github.com> Fri, 17 July 2020 02:10 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 A925E3A0F46 for <quic-issues@ietfa.amsl.com>; Thu, 16 Jul 2020 19:10:09 -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 f5VTScF-iEd2 for <quic-issues@ietfa.amsl.com>; Thu, 16 Jul 2020 19:10:08 -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 6276F3A0F45 for <quic-issues@ietf.org>; Thu, 16 Jul 2020 19:10:08 -0700 (PDT)
Received: from github-lowworker-2e54e43.va3-iad.github.net (github-lowworker-2e54e43.va3-iad.github.net [10.48.17.27]) by smtp.github.com (Postfix) with ESMTP id B293A8C1106 for <quic-issues@ietf.org>; Thu, 16 Jul 2020 19:10:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594951807; bh=Zzo0+B+LCLnQFn6NYvnNriXkzS3apGfQDn1MXjEgaiM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nnIHiiDJSUcnzzgpeP4mlEUGkZvEN+3gH0wCdZKquqndBcABhz0SxF8fdXFxlMHJo t845tFp4T4EkbFdfi9168NOyLaj3kTexAzYwB4TQLenb1p3CykSTRYsP5UWc6kKSKj SF1Maokf61HQdptY1FdK8J9XOXAbBvkLOE30hopo=
Date: Thu, 16 Jul 2020 19:10:07 -0700
From: Jana Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6Y4VEQKVXQMV25ENV5DTUX7EVBNHHCN2JJGQ@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/659789324@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_5f11087fa3752_74c13f9af5ccd95c749e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: janaiyengar
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/c6CFrWD0qMgASjL7F8l4-NWwypM>
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, 17 Jul 2020 02:10:10 -0000

The amplification limit can probably be used, but it's likely going to not be good enough, since you probably just received a request after a long pause and not a full sized packet. 

@DavidSchinazi: Does GQUIC have this amplification protection at the moment?

-- 
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-659789324