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 13:02 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 B81E712DB1F; Thu, 24 Mar 2016 06:02:21 -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 foC6m0IkfcMB; Thu, 24 Mar 2016 06:02:14 -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 35CE412D0C6; Thu, 24 Mar 2016 06:01:48 -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=1458824499; bh=zbxffKoZVnPtyQtwuMczkAEgs7LTXfUzXci6KwSEeUo=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=AybdU6VygUrlydfNEEAbWk/UnYzfp9ObMopsF0EV76TlcCXM0Uo96+htq79r+BUqm r2WfbAJTWTen0ou033Zj/aRBnLYguV+i/6NmZFuqHSEl/BnRgX4eq3Uoa6+Vl5clTf c4Cn9ZzbaDY6GzJ8vdHpVGDFrCif7IWkTeHeFyZ8=
Received: by alrua-kau.kau.toke.dk (Postfix, from userid 1000) id 07B32C40251; Thu, 24 Mar 2016 14:01:39 +0100 (CET)
From: Toke Høiland-Jørgensen <toke@toke.dk>
To: Dave Cridland <dave@cridland.net>
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>
Date: Thu, 24 Mar 2016 14:01:39 +0100
In-Reply-To: <CAKHUCzzoGYUOQiQ4nsiWhTV9JooRNCcSwErhss5ajG0C-tYLFg@mail.gmail.com> (Dave Cridland's message of "Thu, 24 Mar 2016 10:56:15 +0000")
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87fuvgav2k.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/PBMmC2GsJLkYTjwnP6nwBO0QTcw>
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>
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 13:02:22 -0000

Dave Cridland <dave@cridland.net> writes:

>     What we meant to say was something along the lines of "You want to turn
>     this on; it'll do you good, so get on with it! You won't regret it! Now
>     go fix the next 100 million devices!". The current formulation in the
>     draft is an attempt to be slightly less colloquial about it... ;)
>
> Well, I have to ask why, in this case, it's Experimental and not
> Standards-Track?

Heh. Well, I guess the short answer is "because there wasn't WG
consensus to do that". Basically, the working group decided that all the
algorithms we are describing will be experimental rather than standards
track, at least for now. Because they are queueing algorithms and not
protocols (and so do not have the same interoperability requirements),
this was deemed an acceptable way forward, and a way to get it "out
there" without having to have to agree to push for The One True AQM(tm).

(This is my understanding; I'm sure someone will chime in and correct me
if I'm wrong).


Personally, I would have no problem with this being standards track :)

-Toke