IETF Logo Mail Archive

[quicwg/base-drafts] I am concerned the congestion control text is too permissive. (#3247)

Gorry Fairhurst <notifications@github.com> Sun, 17 November 2019 05:08 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 78CF1120043 for <quic-issues@ietfa.amsl.com>; Sat, 16 Nov 2019 21:08:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 9BRqwrWbNtJO for <quic-issues@ietfa.amsl.com>; Sat, 16 Nov 2019 21:08:20 -0800 (PST)
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 D27F4120018 for <quic-issues@ietf.org>; Sat, 16 Nov 2019 21:08:19 -0800 (PST)
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 2BC82C60588 for <quic-issues@ietf.org>; Sat, 16 Nov 2019 21:08:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573967299; bh=0XM/R2XeoUJ6BBGezRlUiw46v5dGVeYC30KfbxoFnj8=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Tl/ihX1xJApaG9MbqkhGWhRwCAYQpg9LmcUGgnI0YprGPOzpQYGSiwO5jrgoFcEnn WvNaF6POKgALxYrXk33olQX/+QaMobJyrftcQef90LQnI153lwHclTQvaMp6J4jMZ1 SVZtrK69uA2cwpRT5R8eYKl7PoAnUG0G2DLhYjQ8=
Date: Sat, 16 Nov 2019 21:08:19 -0800
From: Gorry Fairhurst <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK4YT3FJ3SNI4FVFHKF33YEEHEVBNHHB6OVDVY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3247@github.com>
Subject: [quicwg/base-drafts] I am concerned the congestion control text is too permissive. (#3247)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dd0d5c31df08_1ef93fa8ec6cd96c2616c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: gorryfair
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/1RwFh0e4FTp_vAn9s-rB8wgvNeg>
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: Sun, 17 Nov 2019 05:08:21 -0000

The docs call out that the design is based on (new)Reno. That is good and suitable for a PS. I have no problem here.

However, there are several places where the text is very permissive "MAY..." that suggests the PS can implement this or anything else. This combination seems awkward for a PS. I'd hoped that we could allow experimentation with new CC's but say SHOULD use an IETF-specified congestion control method, or something text close to that, and change the MAYs into something more helpful. I think this is an easy piece of text to get correct.

-- 
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/3247

v2.23.0 | Report a Bug | By Email