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 14:13 UTC

Return-Path: <toke@toke.dk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46A5B12DBC4; Thu, 24 Mar 2016 07:13:28 -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 aH3soCwh6Vd9; Thu, 24 Mar 2016 07:13:26 -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 279AA12DBBF; Thu, 24 Mar 2016 07:05:25 -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=1458828321; bh=XKKZG1CZ3kmj+N+md2VshrgCJP3yZQGzaNwjORoj2io=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=MIFS1zyjGHh54K/UPIVCcxaMT1P/3SvtIwSssE4hmFLrfD9hINf+4KjkfMvw2R0uI RgKuxPlaMtroSBr97gHjajPZAeLotiVS8Rg9T7fGcHU5bmb5Tvx+/4KHRsTzAk7Zxz AgYJSyb5U38pc7X6/kb7r0L527GgFiXuZVk4LIZ4=
Received: by alrua-kau.kau.toke.dk (Postfix, from userid 1000) id AA098C40251; Thu, 24 Mar 2016 15:05:20 +0100 (CET)
From: Toke Høiland-Jørgensen <toke@toke.dk>
To: Dave Cridland <dave@cridland.net>
Subject: Re: [aqm] Last Call: <draft-ietf-aqm-fq-codel-05.txt> (FlowQueue-Codel) to Experimental RFC
References: <20160303172022.12971.79276.idtracker@ietfa.amsl.com> <56EBDA04.3020500@bobbriscoe.net> <56F3587D.5070000@swin.edu.au> <CAKHUCzz=9zORizo2qp6-hLrd-S2zm_aVaLPhH60HZLKQDEOfvQ@mail.gmail.com> <87twjwb1zs.fsf@toke.dk> <CAKHUCzzoGYUOQiQ4nsiWhTV9JooRNCcSwErhss5ajG0C-tYLFg@mail.gmail.com> <87fuvgav2k.fsf@toke.dk> <CAKHUCzzoPDLmHF1AWAYFaa1OeJbFfa5v9UUYbwdnHE1ODK6sKg@mail.gmail.com>
Date: Thu, 24 Mar 2016 15:05:20 +0100
In-Reply-To: <CAKHUCzzoPDLmHF1AWAYFaa1OeJbFfa5v9UUYbwdnHE1ODK6sKg@mail.gmail.com> (Dave Cridland's message of "Thu, 24 Mar 2016 13:44:34 +0000")
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <877fgsas4f.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/L37-tqvYB34bAssDUhns-ANiYVg>
X-Mailman-Approved-At: Thu, 24 Mar 2016 08:05:48 -0700
Cc: draft-ietf-aqm-fq-codel@ietf.org, Bob Briscoe <research@bobbriscoe.net>, grenville armitage <garmitage@swin.edu.au>, aqm-chairs@ietf.org, mls.ietf@gmail.com, aqm@ietf.org, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2016 14:13:28 -0000

Dave Cridland <dave@cridland.net> writes:

> If this isn't standards track because there's no WG consensus for a single
> algorithm (and we'll argue over whether a queueing algorithm is a protocol or
> not some other time), then I think this WG document should reflect that
> consensus and hold back on the recommendations, then, unless you really have WG
> consensus for that position.
>
> If this were an individual submission, it'd be different, but a WG document must
> reflect the Working Group as a whole and not just the authors.

Yes, well, ensuring that it does is what the WG last call and review
process is for, isn't it? Which the draft has been through without
anyone taking issue with it. Not even sure what (if any) the proper
process for handling this is at this time (the tracker lists the status
as "Submitted to IESG for Publication")...?

I explained the reasoning behind the current language in a previous
email. The only proposal for alternative language has been from
Grenville, and as I said I can live with that. However, I'm not terribly
inclined to spend more time editing this until I'm sure that it will
actually put the issue to rest.

-Toke

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