Re: [quicwg/base-drafts] Integrate QUIC text from DPLPMTUD (#3693)

Martin Thomson <notifications@github.com> Tue, 26 May 2020 23:50 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 DD8E93A0BDF for <quic-issues@ietfa.amsl.com>; Tue, 26 May 2020 16:50:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 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_28=1.404, 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 Pi-J_FDxbK80 for <quic-issues@ietfa.amsl.com>; Tue, 26 May 2020 16:50:01 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7131F3A0BDD for <quic-issues@ietf.org>; Tue, 26 May 2020 16:50:01 -0700 (PDT)
Received: from github-lowworker-39ac79b.ac4-iad.github.net (github-lowworker-39ac79b.ac4-iad.github.net [10.52.18.15]) by smtp.github.com (Postfix) with ESMTP id A630796049A for <quic-issues@ietf.org>; Tue, 26 May 2020 16:49:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1590536999; bh=ymVvUHs6CfQbNCXfoM9k6IXf0n4LNn/dTwrw1FQgodo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kYVp9B5ElPUzyqCQcflgFJBw8NeJ50K0jYkBZ16MOMByw7rHQMUQDbzSBYXFXoW14 TIUi4ovrAen2ayhA7Y2WGVS67T7WVxKd6vyPoUhvhuWtmlda3SMqraKRXdwG0USl+p qOqc2mhk3vhgj6w5/yE0DfQeWrpDtSB2ZkIVYKhg=
Date: Tue, 26 May 2020 16:49:59 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY6445FAZ3YZA7MP6F43GGCPEVBNHHCKNQYNU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3693/review/418753038@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3693@github.com>
References: <quicwg/base-drafts/pull/3693@github.com>
Subject: Re: [quicwg/base-drafts] Integrate QUIC text from DPLPMTUD (#3693)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ecdab2796ae9_ca23fbc2e4cd964370be"; 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/Y2XekrsAf57Zbc3aInZi_2GG8sw>
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: Tue, 26 May 2020 23:50:03 -0000

@martinthomson commented on this pull request.



> +state when the QUIC connection handshake has been completed and
+the endpoint has established a 1-RTT key.

@gorryfair replies (below, repeated to keep the thread intact):

> The reason why we didn't suggest this within DPLPMTUD, was two things:
>
> * Using the limited for IW for packet probes rapidly consumes the current IW space in bytes, and we were unconvinced of the importance to tenatively try a large PMTU during the first RTT.
> 
> * I was not aware of measurement data about how changing the initial flight of data would impact congestion collapse, since at this point there is no feedback from the receiver, and it seems, at least to me, to raise questions regarding stability with large numbers of flows and also as you note, the potential DoS opportunities.
>
> So, I'd be interested in what people think about this, and see any analysis and experience.

-- 
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/3693#discussion_r430768205