IETF Logo Mail Archive

Re: [aqm] Last Call: <draft-ietf-aqm-fq-codel-05.txt> (FlowQueue-Codel) to Experimental RFC

Toke Høiland-Jørgensen <toke@toke.dk> Thu, 24 March 2016 10:28 UTC

Return-Path: <toke@toke.dk>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8CB812D1D5; Thu, 24 Mar 2016 03:28:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-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=toke.dk
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 yiN06apiQ8ts; Thu, 24 Mar 2016 03:28:13 -0700 (PDT)
Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F2F6112D0AB; Thu, 24 Mar 2016 03:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at mail2.tohojo.dk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1458815290; bh=lqZTpI5Fy6HNpLEa9O30ivMLoQ88GCM7jrzPfb2jedI=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=DwZCcTyWzegohEmXDIkBJETxb5W1VFBZj3y8C8m4RIsV/7B/n1CZcoYp1auM37aXZ wDhMeEIx1/LPun+WSncyVM1YWFuo0EVeKf48cwE6Qo7Cf7KxvEUjGE22GULBIshOIb DB+z/1LnHutT6SVcfVI6Nd/mPmQFBNrrPBQLIxNA=
Sender: toke@toke.dk
Received: by alrua-kau.kau.toke.dk (Postfix, from userid 1000) id 2478CC40251; Thu, 24 Mar 2016 11:28:09 +0100 (CET)
From: Toke Høiland-Jørgensen <toke@toke.dk>
To: grenville armitage <garmitage@swin.edu.au>
References: <20160303172022.12971.79276.idtracker@ietfa.amsl.com> <56EBDA04.3020500@bobbriscoe.net> <56F3587D.5070000@swin.edu.au>
Date: Thu, 24 Mar 2016 11:28:09 +0100
In-Reply-To: <56F3587D.5070000@swin.edu.au> (grenville armitage's message of "Thu, 24 Mar 2016 14:01:17 +1100")
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87y498b26e.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/5OiwxDN5A_3nE7Puks6gEB4LeFM>
Cc: draft-ietf-aqm-fq-codel@ietf.org, Bob Briscoe <research@bobbriscoe.net>, aqm-chairs@ietf.org, mls.ietf@gmail.com, aqm@ietf.org, ietf@ietf.org
Subject: Re: [aqm] Last Call: <draft-ietf-aqm-fq-codel-05.txt> (FlowQueue-Codel) to Experimental RFC
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2016 10:28:15 -0000

grenville armitage <garmitage@swin.edu.au> writes:

> What about:
>
> Section 1: "...and we believe it to be safe to turn on by default, ..." ->
> "...and we believe it to be significantly beneficial to turn on by default, ..."
> Section 7: "We believe it to be a safe default and ..." -> "We believe it to be
> a significantly beneficial default and ..."

Aha! Finally someone is being constructive! Thank you!

> (Yes, this is going to be an Experimental RFC. And yes, turning on FQ_CoDel
> generally results in awesome improvements wrt pfifo. But the two instances of
> "safe" in draft-ietf-aqm-fq-codel-05.txt do imply to me a wider degree of
> applicability than is probably warranted at this juncture. I just hadn't noticed
> until Bob mentioned it.)

Still not sure I agree that having the word 'safe' in there is such a
big deal, but, well, if multiple people think it's an issue that in
itself might be reason enough to change it. And I can live with your
alternative formulation. :)

-Toke

v2.23.0 | Report a Bug | By Email