
From nobody Tue Feb  3 16:05:51 2015
Return-Path: <fred@cisco.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA5E91A1AAF for <aqm@ietfa.amsl.com>; Tue,  3 Feb 2015 16:05:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 8xf5EBMUSfgZ for <aqm@ietfa.amsl.com>; Tue,  3 Feb 2015 16:05:48 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38D841A1AAE for <aqm@ietf.org>; Tue,  3 Feb 2015 16:05:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3311; q=dns/txt; s=iport; t=1423008348; x=1424217948; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=zRSZLHso6RRXaQyxO/C94JnhRP6LG0OibBpJb64y5oM=; b=AOtwd9TWpGXZHIh6kOpXmIW2cfcJRJSpwPmr2SfAhKS3mzCWOYdPZq8A vdLCAQBkbjvx7Ius576OHPUk4JeURWFSwReuDhbslqke2l0MRRk2ZQEOY VjMKmGvpX9CQCYAD1oqE2MTPnZ0U3D9LMFCI3O68MDmbfHJC43VZ6+s3+ c=;
X-Files: signature.asc : 487
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CCBQAGYtFU/4ENJK1agwZSWQSCfcIKhXECgRhDAQEBAQF9hAwBAQEDASNWBQsCAQgOCioCAjIlAgQOBQ6IFwgNwBKWVQEBAQEBAQEBAQEBAQEBAQEBAQEBARePeAeCaC6BEwWPDIFUgStPhViBFzaCTYgLhjoig25vgUR+AQEB
X-IronPort-AV: E=Sophos;i="5.09,516,1418083200";  d="asc'?scan'208";a="120204515"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-8.cisco.com with ESMTP; 04 Feb 2015 00:05:44 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t1405iY3023851 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Feb 2015 00:05:44 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.211]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0195.001; Tue, 3 Feb 2015 18:05:44 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Wesley Eddy <wes@mti-systems.com>
Thread-Topic: [aqm] working group status
Thread-Index: AQHQQA5Rg/51KpgBf0GlQPwoHq/Fzg==
Date: Wed, 4 Feb 2015 00:05:43 +0000
Message-ID: <64841AAA-30BF-4786-A046-D2FE146A954C@cisco.com>
References: <54B518F1.9050005@mti-systems.com>
In-Reply-To: <54B518F1.9050005@mti-systems.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.121]
Content-Type: multipart/signed; boundary="Apple-Mail=_79977EBA-6E3A-4518-80ED-DBF24FA53DCC"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/m_LmRLY2mDtam2b7T4Ki2TKBmjM>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] working group status
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 04 Feb 2015 00:05:50 -0000

--Apple-Mail=_79977EBA-6E3A-4518-80ED-DBF24FA53DCC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Jan 13, 2015, at 5:09 AM, Wesley Eddy <wes@mti-systems.com> wrote:
>=20
> Hi, to get 2015 started, Richard and I as chairs put together a set of
> milestone status notes for the AQM working group items.
>=20
> Please note, that there are a few relatively short drafts that should
> not require much work, but which haven't been very actively discussed
> on the list.  Comments on these will be extremely useful in =
accelerating
> them forward.
>=20
>=20
> - WG Milestones:
>  - Submit AQM recommendations to IESG for publication, obsoleting
>    RFC 2309
>    - http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/
>    - This has been in IETF Last Call and some notes are being
>      discussed from the last call comments

My understanding is that the GEN-ART review came in on 1/9, and Gorry =
filed an update 1/13. What is the status of the draft now?

>  - Submit first algorithm specification to IESG for publication as
>    Proposed Standard
>    - http://datatracker.ietf.org/doc/draft-ietf-aqm-codel/
>    - http://datatracker.ietf.org/doc/draft-ietf-aqm-pie/
>    - These algorithm drafts have been around for some time now, and
>      it would be good to get some comments on the present revisions
>      posted to the list (following up the Honolulu meeting threads).
>      There are some known updates planned for the CoDel draft.

Looking forward to the comments. At this point, I don=E2=80=99t see an =
obvious reason to hold the drafts up.

>      - =
http://datatracker.ietf.org/doc/draft-ietf-aqm-fq-implementation/
>        - This draft is short and was well-received initially as a
>          clarification to how AQM relates to FQ techniques.  Some
>          references are to older drafts, but otherwise it seems like
>          it may be complete enough to last call.  ***Further input and
>          reviews would be really helpful on this.***

It was originally posted as a predecessor to a discussion, the point =
being that AQM and scheduling disciplines are orthoganal topics (can be =
implemented together, but our fq_pie implementation is simply the two =
behaviors in series), and intended to end with the discussion. The WG =
decided it wanted to do more with it. Happy to do that, but I need =
guidance as to what the working group wants.

--Apple-Mail=_79977EBA-6E3A-4518-80ED-DBF24FA53DCC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEVAwUBVNFiVp9ieig10VPpAQLDxwf/eL8DETfRu75c/XZZbdhLReTifgfLH5QD
LZgVOhjGsJAgVqiv9fPqJN83jsIYKNWE3Bt23E1y3qxoYtmZQCd69SLzLUq745y7
c/zQdiFAyD2Ep9iVnMZCePJr3PiO8ZzmxD5DjtVGSxmTIETwEerJlQce9ZWDMjiP
7c2/IXpO/5mw9tr1Zef09Cud+lRyjJaiQmmvETVaV97mBXA4PNvUQNaUXbMmc+Jl
bCbrV5ZFcOjk+p3nyEAVPw5IP2lCBT1tIlzVmdZ32l3ZpiTeNoetB/91+tynxhkk
pt9GEFji21u95NBd8vNL3lD83VKTVzzqGEq5wC5zw7w/So+4I2xN7A==
=WXDQ
-----END PGP SIGNATURE-----

--Apple-Mail=_79977EBA-6E3A-4518-80ED-DBF24FA53DCC--


From nobody Fri Feb  6 03:48:15 2015
Return-Path: <acmorton@att.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A26B1A00B8; Wed,  4 Feb 2015 16:07:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 uUKpzVlWfCmG; Wed,  4 Feb 2015 16:07:29 -0800 (PST)
Received: from mail-pink.research.att.com (mail-pink.research.att.com [204.178.8.22]) by ietfa.amsl.com (Postfix) with ESMTP id 39B6B1A00B1; Wed,  4 Feb 2015 16:07:24 -0800 (PST)
Received: from mail-azure.research.att.com (unknown [135.207.255.18]) by mail-pink.research.att.com (Postfix) with ESMTP id 9EF96D84AD; Wed,  4 Feb 2015 19:22:07 -0500 (EST)
Received: from exchange.research.att.com (njfpsrvexg0.research.att.com [135.207.240.40]) by mail-azure.research.att.com (Postfix) with ESMTP id 567A0E06F5; Wed,  4 Feb 2015 19:07:22 -0500 (EST)
Received: from NJFPSRVEXG0.research.att.com ([fe80::c5dd:2310:7197:58ea]) by NJFPSRVEXG0.research.att.com ([fe80::c5dd:2310:7197:58ea%17]) with mapi; Wed, 4 Feb 2015 19:07:04 -0500
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: "bmwg@ietf.org" <bmwg@ietf.org>, "aqm@ietf.org" <aqm@ietf.org>
Date: Wed, 4 Feb 2015 19:07:02 -0500
Thread-Topic: Third WGLC on draft-ietf-bmwg-traffic-management
Thread-Index: AdBA1pZDS6SHgtRkT3iKb5AXaGQPug==
Message-ID: <4AF73AA205019A4C8A1DDD32C034631D876E60FE@NJFPSRVEXG0.research.att.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/WR5M7VhbBPvCYARKSMSsvi71BX8>
X-Mailman-Approved-At: Fri, 06 Feb 2015 03:48:08 -0800
Subject: [aqm] Third WGLC on draft-ietf-bmwg-traffic-management
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Feb 2015 00:07:31 -0000

BMWG (and AQM):

A WG Last Call period for the Internet-Draft on
Traffic Management Benchmarking:

   http://tools.ietf.org/html/draft-ietf-bmwg-traffic-management

will be open from 4 February 2015 through 19 February 2015.

Please note that the RFC diff for this version indicates the=20
introduction of many new instances of RFC 2119 Requirements Language:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-bmwg-traffic-management-02
Past reviewers should check the current draft and indicate their=20
current opinion or support.

The second WGLC (on -01) closed on 6 January, 2015 with substantial=20
comments and the authors believe they are now addressed.

The first WGLC (on -00) closed October 21 2014, with substantial=20
comments.

This draft is continuing the BMWG Last Call Process. See
http://www1.ietf.org/mail-archive/web/bmwg/current/msg00846.html

Please read and express your opinion on whether or not this
Internet-Draft should be forwarded to the Area Directors for
publication as an Informational RFC.  Send your comments
to this list or acmorton@att.com and sbanks@encrypted.net

Al
bmwg co-chair
 =20
 =20


From nobody Mon Feb  9 11:07:29 2015
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA86B1A1B75 for <aqm@ietfa.amsl.com>; Mon,  9 Feb 2015 10:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 NDmUhsS1mtpF for <aqm@ietfa.amsl.com>; Mon,  9 Feb 2015 10:40:51 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E33FE1A1B5E for <aqm@ietf.org>; Mon,  9 Feb 2015 10:40:50 -0800 (PST)
Received: from brdgfw.folly.org.uk ([81.187.254.242] helo=[192.168.0.128]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1YKtGH-00067u-In; Mon, 09 Feb 2015 18:40:48 +0000
Message-ID: <54D8FF32.9020701@dial.pipex.com>
Date: Mon, 09 Feb 2015 18:40:50 +0000
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>,  "gorry@erg.abdn.ac.uk (erg)" <gorry@erg.abdn.ac.uk>
References: <54947DCF.3030601@scss.tcd.ie> <40842d620667e7d2a33f451dcd8f502b.squirrel@spey.erg.abdn.ac.uk> <30819CFE-21D3-4EF8-ABFE-4C01940399B7@cisco.com> <54ADC3F5.3040706@dial.pipex.com>
In-Reply-To: <54ADC3F5.3040706@dial.pipex.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/xsFlcJLwU_nx_FmKWMdrPd_4PoM>
Cc: aqm@ietf.org
Subject: Re: [aqm] Gen-art LC review of draft-ietf-aqm-recommendation-08
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 09 Feb 2015 18:40:53 -0000

Hi.

I have been putting off responding to the last email in the chain of our 
discussions from before Christmas while I went and did a bit of 
background reading.  Having done this and reread the latest draft, I get 
the impression that I was having a bad hair day/week or some such when I 
wrote the previous review and discussed it with you. Apologies for some 
rather inappropriate comments on things that I now realize were actually 
pretty well covered.

Having got various other things of a gen-art nature off my job list, I 
got back to AQM.  I have resubmitted the review deleting the stuff about 
bufferbloat, but I do think that some words about checking that 
combinations of mechanisms don't mess with each other would be a good idea.

Incidentally, I thought that CableLabs report of comparative simulations 
of the various proposals in train at the moment was a nice piece of 
work.  The background material is a useful tutorial, the analysis of the 
requirements of gaming users is helpful and the comparative analysis is 
very helpful.   It was mentioned a couple of days ago  in a thread on 
IETF Discuss on a slightly related matter :
http://www.cablelabs.com/wp-content/uploads/2013/11/Active_Queue_Management_Algorithms_DOCSIS_3_0.pdf

Regards,
Elwyn


From nobody Tue Feb 10 23:51:54 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C4961A86EE; Tue, 10 Feb 2015 23:51:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 xwtcDFrklsf1; Tue, 10 Feb 2015 23:51:50 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 637201A8549; Tue, 10 Feb 2015 23:51:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211075149.13561.79776.idtracker@ietfa.amsl.com>
Date: Tue, 10 Feb 2015 23:51:49 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/GtNGFBS1kEnJhWv5XTECBszgqNA>
Subject: [aqm] ID Tracker State Update Notice: <draft-ietf-aqm-recommendation-09.txt>
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Feb 2015 07:51:52 -0000

IESG state changed to Waiting for AD Go-Ahead from Waiting for Writeup
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/


From nobody Tue Feb 10 23:51:56 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 9FDFE1A86FC; Tue, 10 Feb 2015 23:51:52 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C4961A86EE; Tue, 10 Feb 2015 23:51:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 xwtcDFrklsf1; Tue, 10 Feb 2015 23:51:50 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 637201A8549; Tue, 10 Feb 2015 23:51:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211075149.13561.79776.idtracker@ietfa.amsl.com>
Date: Tue, 10 Feb 2015 23:51:49 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/GtNGFBS1kEnJhWv5XTECBszgqNA>
Subject: [aqm] ID Tracker State Update Notice: <draft-ietf-aqm-recommendation-09.txt>
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Feb 2015 07:51:52 -0000

IESG state changed to Waiting for AD Go-Ahead from Waiting for Writeup
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/


From nobody Tue Feb 10 23:55:28 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38FCE1A86E5; Tue, 10 Feb 2015 23:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] autolearn=ham
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 7W9R8ReLry5j; Tue, 10 Feb 2015 23:55:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 312641A86FC; Tue, 10 Feb 2015 23:55:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rs@netapp.com>, <iesg-secretary@ietf.org>, <iesg@ietf.org>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm-chairs@ietf.org>, <aqm@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211075521.14672.68587.idtracker@ietfa.amsl.com>
Date: Tue, 10 Feb 2015 23:55:21 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/ApNPC1jUmbaaJyj879bkAtyzM9s>
Subject: [aqm] Telechat update notice: <draft-ietf-aqm-recommendation-09.txt>
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Feb 2015 07:55:26 -0000

Placed on agenda for telechat - 2015-02-19
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/


From nobody Tue Feb 10 23:55:31 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id BEBFB1A8714; Tue, 10 Feb 2015 23:55:26 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38FCE1A86E5; Tue, 10 Feb 2015 23:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] autolearn=ham
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 7W9R8ReLry5j; Tue, 10 Feb 2015 23:55:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 312641A86FC; Tue, 10 Feb 2015 23:55:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rs@netapp.com>, <iesg-secretary@ietf.org>, <iesg@ietf.org>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm-chairs@ietf.org>, <aqm@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211075521.14672.68587.idtracker@ietfa.amsl.com>
Date: Tue, 10 Feb 2015 23:55:21 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/ApNPC1jUmbaaJyj879bkAtyzM9s>
Subject: [aqm] Telechat update notice: <draft-ietf-aqm-recommendation-09.txt>
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Feb 2015 07:55:27 -0000

Placed on agenda for telechat - 2015-02-19
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/


From nobody Tue Feb 10 23:55:41 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09D121A875A; Tue, 10 Feb 2015 23:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 2Ov1M4Nw6UK1; Tue, 10 Feb 2015 23:55:31 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 700311A873C; Tue, 10 Feb 2015 23:55:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211075531.22129.76548.idtracker@ietfa.amsl.com>
Date: Tue, 10 Feb 2015 23:55:31 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/_2-kWvGhffX9Cl3O230M9dHG1zM>
Subject: [aqm] ID Tracker State Update Notice: <draft-ietf-aqm-recommendation-09.txt>
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Feb 2015 07:55:33 -0000

IESG state changed to IESG Evaluation from Waiting for AD Go-Ahead
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/


From nobody Tue Feb 10 23:55:42 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 45FA41A873C; Tue, 10 Feb 2015 23:55:33 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09D121A875A; Tue, 10 Feb 2015 23:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 2Ov1M4Nw6UK1; Tue, 10 Feb 2015 23:55:31 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 700311A873C; Tue, 10 Feb 2015 23:55:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211075531.22129.76548.idtracker@ietfa.amsl.com>
Date: Tue, 10 Feb 2015 23:55:31 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/_2-kWvGhffX9Cl3O230M9dHG1zM>
Subject: [aqm] ID Tracker State Update Notice: <draft-ietf-aqm-recommendation-09.txt>
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Feb 2015 07:55:33 -0000

IESG state changed to IESG Evaluation from Waiting for AD Go-Ahead
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/


From nobody Wed Feb 11 00:00:57 2015
Return-Path: <mls.ietf@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 600261A8035; Wed, 11 Feb 2015 00:00:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001] autolearn=ham
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 LcWZvw0eHY3f; Wed, 11 Feb 2015 00:00:53 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 033241A7034; Wed, 11 Feb 2015 00:00:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Martin Stiemerling" <mls.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211080053.22607.80734.idtracker@ietfa.amsl.com>
Date: Wed, 11 Feb 2015 00:00:53 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/U6DhjG7sDQmBcKx7sBO6mXss1_U>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Martin Stiemerling's Yes on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Feb 2015 08:00:54 -0000

Martin Stiemerling has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

The authors have acknowledged Elwyn's GEN-ART review [1] and they will
integrate the comments in an updated version after the IESG review. 

[1]
https://mailarchive.ietf.org/arch/msg/ietf/gHzWBxmv64q6PkbQ0AFW5q6TvpU



From nobody Wed Feb 11 00:00:58 2015
Return-Path: <mls.ietf@gmail.com>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 9BD191A86EC; Wed, 11 Feb 2015 00:00:54 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 600261A8035; Wed, 11 Feb 2015 00:00:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001] autolearn=ham
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 LcWZvw0eHY3f; Wed, 11 Feb 2015 00:00:53 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 033241A7034; Wed, 11 Feb 2015 00:00:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Martin Stiemerling" <mls.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211080053.22607.80734.idtracker@ietfa.amsl.com>
Date: Wed, 11 Feb 2015 00:00:53 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/U6DhjG7sDQmBcKx7sBO6mXss1_U>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Martin Stiemerling's Yes on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Feb 2015 08:00:54 -0000

Martin Stiemerling has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

The authors have acknowledged Elwyn's GEN-ART review [1] and they will
integrate the comments in an updated version after the IESG review. 

[1]
https://mailarchive.ietf.org/arch/msg/ietf/gHzWBxmv64q6PkbQ0AFW5q6TvpU



From nobody Wed Feb 11 10:06:22 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB991A8957; Wed, 11 Feb 2015 10:06:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 0uOvFwgFZgi9; Wed, 11 Feb 2015 10:06:11 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 14B121A1A59; Wed, 11 Feb 2015 10:06:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211180607.23753.24555.idtracker@ietfa.amsl.com>
Date: Wed, 11 Feb 2015 10:06:07 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/dwhXkpc3kzDX4cJhpKfU1pamTA8>
Subject: [aqm] ID Tracker State Update Notice: <draft-ietf-aqm-recommendation-09.txt>
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Feb 2015 18:06:14 -0000

IANA review state changed to IANA OK - No Actions Needed
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/


From nobody Wed Feb 11 10:06:31 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 6C35C1A89A7; Wed, 11 Feb 2015 10:06:14 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB991A8957; Wed, 11 Feb 2015 10:06:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 0uOvFwgFZgi9; Wed, 11 Feb 2015 10:06:11 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 14B121A1A59; Wed, 11 Feb 2015 10:06:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150211180607.23753.24555.idtracker@ietfa.amsl.com>
Date: Wed, 11 Feb 2015 10:06:07 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/dwhXkpc3kzDX4cJhpKfU1pamTA8>
Subject: [aqm] ID Tracker State Update Notice: <draft-ietf-aqm-recommendation-09.txt>
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 11 Feb 2015 18:06:14 -0000

IANA review state changed to IANA OK - No Actions Needed
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/


From nobody Fri Feb 13 07:53:48 2015
Return-Path: <shahid.akhtar@alcatel-lucent.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 666081A8744 for <aqm@ietfa.amsl.com>; Fri, 13 Feb 2015 07:53:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.51
X-Spam-Level: 
X-Spam-Status: No, score=-5.51 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 K2fclCtPq8t5 for <aqm@ietfa.amsl.com>; Fri, 13 Feb 2015 07:53:44 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 10DDD1A0358 for <aqm@ietf.org>; Fri, 13 Feb 2015 07:53:43 -0800 (PST)
Received: from us70uusmtp3.zam.alcatel-lucent.com (unknown [135.5.2.65]) by Websense Email Security Gateway with ESMTPS id 37FF6A845E989; Fri, 13 Feb 2015 15:53:38 +0000 (GMT)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id t1DFrdNZ025998 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 13 Feb 2015 10:53:39 -0500
Received: from US70UWXCHMBA01.zam.alcatel-lucent.com ([169.254.7.190]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.03.0195.001; Fri, 13 Feb 2015 10:53:39 -0500
From: "Akhtar, Shahid (Shahid)" <shahid.akhtar@alcatel-lucent.com>
To: "Scheffenegger, Richard" <rs@netapp.com>, Martin Stiemerling <mls.ietf@gmail.com>, "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] analysis paper on PIE...
Thread-Index: AQHP/tL0evjHW4yrRkuErsO0PG9eAJxeAL8AgJFLMbA=
Date: Fri, 13 Feb 2015 15:53:39 +0000
Message-ID: <C0611F522A6FA9498A044C36073E4965C3169371@US70UWXCHMBA01.zam.alcatel-lucent.com>
References: <D086F727.B6AF%ropan@cisco.com> <5463F169.6020805@gmail.com> <cf344e47f30e4cd49afa04280b4cbeef@hioexcmbx05-prd.hq.netapp.com>
In-Reply-To: <cf344e47f30e4cd49afa04280b4cbeef@hioexcmbx05-prd.hq.netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/GrWZCBeEgzE9LmpVvqdaMFBPN1A>
Subject: Re: [aqm] analysis paper on PIE...
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 13 Feb 2015 15:53:46 -0000

Hi All,

The work we presented at ICCRG in Vancouver was published and is available =
at:

http://ieeexplore.ieee.org/xpl/articleDetails.jsp?tp=3D&arnumber=3D7036963&=
queryText%3Dglobecom+2014+aqm

It does not have any analysis of PIE, but does discuss CoDel.

-Shahid Akhtar.

-----Original Message-----
From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Scheffenegger, Richard
Sent: Wednesday, November 12, 2014 6:04 PM
To: Martin Stiemerling; aqm@ietf.org
Subject: Re: [aqm] analysis paper on PIE...

Hi Martin,

I believe these papers may qualify that requirement:

http://ipv6.cablelabs.com/wp-content/uploads/2014/06/DOCSIS-AQM_May2014.pdf
http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=3D6925768
https://www.duo.uio.no/handle/10852/37381

tl;dr - both pie and codel camps did some independent implementations and t=
esting of the respective other algorithm, with discussions and denting out =
some poorly described aspects in that process. It's my understanding that t=
his lead to a better quality of the drafts in both instances.



Richard Scheffenegger




> -----Original Message-----
> From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Martin=20
> Stiemerling
> Sent: Mittwoch, 12. November 2014 13:47
> To: aqm@ietf.org
> Subject: Re: [aqm] analysis paper on PIE...
>=20
> [writing not as AD, but as random IETF participant]
>=20
> Sorry for this blunt question:
>=20
> Is there any other analysis made by an independent source, i.e., where=20
> not the PIE authors are running an analysis of PIE?
>=20
> Thanks,
>=20
>    Martin
>=20
> Am 10.11.14 um 21:15 schrieb Rong Pan (ropan):
> > Please see our analysis paper on PIE...
> >
> > Thanks,
> >
> > Rong
> >
> >
> >
> > _______________________________________________
> > aqm mailing list
> > aqm@ietf.org
> > https://www.ietf.org/mailman/listinfo/aqm
> >
>=20
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm

_______________________________________________
aqm mailing list
aqm@ietf.org
https://www.ietf.org/mailman/listinfo/aqm


From nobody Sun Feb 15 10:59:09 2015
Return-Path: <dave.taht@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1AB1A3B9F for <aqm@ietfa.amsl.com>; Sun, 15 Feb 2015 10:59:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 z8pEEUVaARU2 for <aqm@ietfa.amsl.com>; Sun, 15 Feb 2015 10:58:59 -0800 (PST)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 594321A6EF9 for <aqm@ietf.org>; Sun, 15 Feb 2015 10:58:55 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id uz6so35764883obc.9 for <aqm@ietf.org>; Sun, 15 Feb 2015 10:58:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=IOySUgj0QEsPC0bFZch5nWjpqyVmSZIt4WNFvPoR4Hg=; b=TCwUIyX7ysdFQjD1qJZ6E/ab4QzN6A/S2IDJpAlV0nrsXMZRa/VVIssOGfFl7lT9HV JCQhnwaQa13WgkSBGcwOAndaL0Q2lnnnKGcJTBuCqM5VZlffxqd2yR4m4iCFDMXdyhCu eu2URDG1IpX/L2WT6fLqn+S7vvJXz5WAt8QTsW5WDzaB2H+RLKL0BfRwn26J1VYwu/4r WrS4yEF3cdx+alkoQQnWwMYzidfCpl/7tTDwSeWCOv7suDg4/XrmFm85dqWDM0/uoF98 jaGCRlr0jfZkrxJ1r2XQZCk0en41RpypCMvd3gyqv2xkU+C/tqJMKK/HX7jnb9HtoN+l 5Z4Q==
MIME-Version: 1.0
X-Received: by 10.202.62.70 with SMTP id l67mr12329465oia.59.1424026734212; Sun, 15 Feb 2015 10:58:54 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Sun, 15 Feb 2015 10:58:54 -0800 (PST)
Date: Sun, 15 Feb 2015 10:58:54 -0800
Message-ID: <CAA93jw5NS3BNW8e4a92j0T-i9feODmg08PnB=pxpVdvhMhcA0Q@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: "aqm@ietf.org" <aqm@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Content-Type: multipart/alternative; boundary=001a113ce09aa4bc63050f250fba
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/v8v3FzsjJD2aAjikno0GJGMRhLg>
Subject: [aqm] anybody working on aqm and/or bufferbloat attending IEEE infocom 15 in Hong Kong?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sun, 15 Feb 2015 18:59:02 -0000

--001a113ce09aa4bc63050f250fba
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

judging from the:
http://infocom2015.ieee-infocom.org/program/main-technical-program

there is simply an extraordinary amount of work being presented on issues
of concern to us
- 3 entire sessions on scheduling and buffer management, one on flow and
access control, 2 mac technologies, some stuff on monitoring and
measurement....

--=20
Dave T=C3=A4ht

http://www.bufferbloat.net
<http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks>

--001a113ce09aa4bc63050f250fba
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>judging from the: <a href=3D"http://infocom2015.=
ieee-infocom.org/program/main-technical-program">http://infocom2015.ieee-in=
focom.org/program/main-technical-program</a><br clear=3D"all"><br></div>the=
re is simply an extraordinary amount of work being presented on issues of c=
oncern to us<br></div>- 3 entire sessions on scheduling and buffer manageme=
nt, one on flow and access control, 2 mac technologies, some stuff on monit=
oring and measurement....<br><div><br></div><div><div>-- <br><div class=3D"=
gmail_signature">Dave T=C3=A4ht<br><br><a href=3D"http://www.bufferbloat.ne=
t">http://www.bufferbloat.net</a><a href=3D"http://www.bufferbloat.net/proj=
ects/bloat/wiki/Upcoming_Talks" target=3D"_blank"></a></div>
</div></div></div>

--001a113ce09aa4bc63050f250fba--


From nobody Mon Feb 16 12:41:48 2015
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0B021A88B4; Mon, 16 Feb 2015 12:41:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001] autolearn=ham
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 hSfQOAZc6Fxp; Mon, 16 Feb 2015 12:41:43 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D69071A88AF; Mon, 16 Feb 2015 12:41:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150216204143.14904.65612.idtracker@ietfa.amsl.com>
Date: Mon, 16 Feb 2015 12:41:43 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/de9_PuN880kcjQ9KRT5-EmzXIRk>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Spencer Dawkins' Yes on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 16 Feb 2015 20:41:46 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I appreciate very much the work on this document. I'm a Yes, with some
niggling.

In this text:

Abstract

   The note largely repeats the recommendations of RFC 2309, and
   replaces these after fifteen years of experience and new research.
   
I'm thinking that doesn't match the "replaces" language in section 1.4,
which I think is about right. Perhaps something like

   The note replaces the recommendations of RFC 2309 based on 
   fifteen years of experience and new research.

In this text:

1.1.  Congestion Collapse

   The original fix for Internet meltdown was provided by Van Jacobsen.
   Beginning in 1986, Jacobsen developed the congestion avoidance
   mechanisms [Jacobson88] that are now required for implementations of
   the Transport Control Protocol (TCP) [RFC0768] [RFC1122].  

I'm wondering if RFC 7414 would be a helpful reference here, and
elsewhere in the document. I'm bemused by the use of RFC 793 as the
reference for TCP later in this document, since RFC 793 TCP behaves
nothing like TCP as characterized here. 

I know I'm confused by the reference to RFC 768 - that's UDP, as cited
correctly elsewhere in the document.

In this text:

   2.  Non-Responsive Flows

       The User Datagram Protocol (UDP) [RFC0768] provides a minimal,
       best-effort transport to applications and upper-layer protocols
       (both simply called "applications" in the remainder of this
       document) and does not itself provide mechanisms to prevent
       congestion collapse and establish a degree of fairness [RFC5405].

I'm not entirely comfortable with the idea that non-responsive flows use
UDP transport (especially in our tunneled world). If you guys think this
is OK, I'll hold my nose, but if you wanted to say anything about "other
flows that are as non-responsive as UDP transport", I'd think that would
be helpful. 

It certainly fits at least as well as the "large number of short-lived
TCP flows that are much less responsive" paragraph that you end this
section with, which probably fits better under the following list item, 

   3.  Transport Flows that are less responsive than TCP
   
In this text:

   It is essential that all Internet hosts respond to loss [RFC5681],
   [RFC5405][RFC4960][RFC4340].  Packet dropping by network devices that
   are under load has two effects: It protects the network, which is the
   primary reason that network devices drop packets.  The detection of
   loss also provides a signal to a reliable transport (e.g.  TCP, SCTP)
   that there is potential congestion using a pragmatic heuristic; "when
   the network discards a message in flight, it may imply the presence
   of faulty equipment or media in a path, and it may imply the presence
   of congestion.  To be conservative, a transport must assume it may be
   the latter."  Unreliable transports (e.g. using UDP) need to
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   similarly react to loss [RFC5405]
   ^^^^^^^^^^^^^^^^^^^^^^^
   
would it be more correct to say "Applications using unreliable transports
(e.g. UDP)"?



From nobody Mon Feb 16 12:41:52 2015
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 7A8551A88B9; Mon, 16 Feb 2015 12:41:46 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0B021A88B4; Mon, 16 Feb 2015 12:41:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001] autolearn=ham
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 hSfQOAZc6Fxp; Mon, 16 Feb 2015 12:41:43 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D69071A88AF; Mon, 16 Feb 2015 12:41:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150216204143.14904.65612.idtracker@ietfa.amsl.com>
Date: Mon, 16 Feb 2015 12:41:43 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/de9_PuN880kcjQ9KRT5-EmzXIRk>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Spencer Dawkins' Yes on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 16 Feb 2015 20:41:47 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I appreciate very much the work on this document. I'm a Yes, with some
niggling.

In this text:

Abstract

   The note largely repeats the recommendations of RFC 2309, and
   replaces these after fifteen years of experience and new research.
   
I'm thinking that doesn't match the "replaces" language in section 1.4,
which I think is about right. Perhaps something like

   The note replaces the recommendations of RFC 2309 based on 
   fifteen years of experience and new research.

In this text:

1.1.  Congestion Collapse

   The original fix for Internet meltdown was provided by Van Jacobsen.
   Beginning in 1986, Jacobsen developed the congestion avoidance
   mechanisms [Jacobson88] that are now required for implementations of
   the Transport Control Protocol (TCP) [RFC0768] [RFC1122].  

I'm wondering if RFC 7414 would be a helpful reference here, and
elsewhere in the document. I'm bemused by the use of RFC 793 as the
reference for TCP later in this document, since RFC 793 TCP behaves
nothing like TCP as characterized here. 

I know I'm confused by the reference to RFC 768 - that's UDP, as cited
correctly elsewhere in the document.

In this text:

   2.  Non-Responsive Flows

       The User Datagram Protocol (UDP) [RFC0768] provides a minimal,
       best-effort transport to applications and upper-layer protocols
       (both simply called "applications" in the remainder of this
       document) and does not itself provide mechanisms to prevent
       congestion collapse and establish a degree of fairness [RFC5405].

I'm not entirely comfortable with the idea that non-responsive flows use
UDP transport (especially in our tunneled world). If you guys think this
is OK, I'll hold my nose, but if you wanted to say anything about "other
flows that are as non-responsive as UDP transport", I'd think that would
be helpful. 

It certainly fits at least as well as the "large number of short-lived
TCP flows that are much less responsive" paragraph that you end this
section with, which probably fits better under the following list item, 

   3.  Transport Flows that are less responsive than TCP
   
In this text:

   It is essential that all Internet hosts respond to loss [RFC5681],
   [RFC5405][RFC4960][RFC4340].  Packet dropping by network devices that
   are under load has two effects: It protects the network, which is the
   primary reason that network devices drop packets.  The detection of
   loss also provides a signal to a reliable transport (e.g.  TCP, SCTP)
   that there is potential congestion using a pragmatic heuristic; "when
   the network discards a message in flight, it may imply the presence
   of faulty equipment or media in a path, and it may imply the presence
   of congestion.  To be conservative, a transport must assume it may be
   the latter."  Unreliable transports (e.g. using UDP) need to
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   similarly react to loss [RFC5405]
   ^^^^^^^^^^^^^^^^^^^^^^^
   
would it be more correct to say "Applications using unreliable transports
(e.g. UDP)"?



From nobody Mon Feb 16 14:54:04 2015
Return-Path: <alissa@cooperw.in>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFA601A88D1; Mon, 16 Feb 2015 14:54:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8] autolearn=no
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 SG5wIPDDd0gh; Mon, 16 Feb 2015 14:54:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AF5901A88BD; Mon, 16 Feb 2015 14:54:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alissa Cooper" <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150216225400.2953.87114.idtracker@ietfa.amsl.com>
Date: Mon, 16 Feb 2015 14:54:00 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/HWBiAZZ3-MJwLQ5nqvTPh5_Xedk>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Alissa Cooper's Yes on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 16 Feb 2015 22:54:02 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for the hard work on this document. I have a few comments below.

-- General:
I think it would be useful to define "network devices" up front, and in
particular to clarify whether endpoint devices are subsumed in this
category. Are the recommendations in this document meant to apply to
queues in tablet/smartphone/laptop OSes as well as in routers, switches,
etc.?

-- Sec 1.2:
"instead it provides recommendations on how to select appropriate
   algorithms and recommends that algorithms should be used that a
   recommended algorithm is able to automate any required tuning for
   common deployment scenarios."

Seems like there are some extra words here.

-- Sec 3:
"There is a growing set of UDP-based applications whose congestion
       avoidance algorithms are inadequate or nonexistent (i.e, a flow
       that does not throttle its sending rate when it experiences
       congestion).  Examples include some UDP streaming applications
       for packet voice and video, and some multicast bulk data
       transport.  If no action is taken, such unresponsive flows could
       lead to a new congestion collapse.  Some applications can even
       increase their traffic volume in response to congestion (e.g. by
       adding forward error correction when loss is experienced), with
       the possibility that they contribute to congestion collapse."

Would be nice to have a citation or two in this paragraph (though I can
see why you might not want to).

"Lastly, some applications (e.g. current web browsers) open a
       large numbers of short TCP flows for a single session.  This can
       lead to each individual flow spending the majority of time in the
       exponential TCP slow start phase, rather than in TCP congestion
       avoidance.  The resulting traffic aggregate can therefore be much
       less responsive than a single standard TCP flow."

I note that HTTP/2 is on its way to publication and there are a large
number of existing implementations, so the characterization of "current
web browsers" seems a bit off. I would suggest something like "(e.g. web
browsers primarily supporting HTTP 1.1)."

-- Sec 7:
I think there's actually a really important privacy aspect that should be
called out here, which is that by virtue of recommending that AQM
algorithms not be dependent on specific transport or application
behaviors, network devices need not gain insight into upper layer
protocol information for the purpose of supporting AQM. That is, the
document's explicit recommendation for algorithms to be able to operate
in a transport- and application-agnostic fashion is a privacy-enhancing
feature.

-- Sec 9:
I'm a little surprised that almost all of the research referenced in this
document is from the 1990s, given recent attention that has been paid to
this topic.



From nobody Mon Feb 16 14:54:07 2015
Return-Path: <alissa@cooperw.in>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 368B41A88D9; Mon, 16 Feb 2015 14:54:02 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFA601A88D1; Mon, 16 Feb 2015 14:54:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8] autolearn=no
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 SG5wIPDDd0gh; Mon, 16 Feb 2015 14:54:00 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AF5901A88BD; Mon, 16 Feb 2015 14:54:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Alissa Cooper" <alissa@cooperw.in>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150216225400.2953.87114.idtracker@ietfa.amsl.com>
Date: Mon, 16 Feb 2015 14:54:00 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/HWBiAZZ3-MJwLQ5nqvTPh5_Xedk>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Alissa Cooper's Yes on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 16 Feb 2015 22:54:02 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for the hard work on this document. I have a few comments below.

-- General:
I think it would be useful to define "network devices" up front, and in
particular to clarify whether endpoint devices are subsumed in this
category. Are the recommendations in this document meant to apply to
queues in tablet/smartphone/laptop OSes as well as in routers, switches,
etc.?

-- Sec 1.2:
"instead it provides recommendations on how to select appropriate
   algorithms and recommends that algorithms should be used that a
   recommended algorithm is able to automate any required tuning for
   common deployment scenarios."

Seems like there are some extra words here.

-- Sec 3:
"There is a growing set of UDP-based applications whose congestion
       avoidance algorithms are inadequate or nonexistent (i.e, a flow
       that does not throttle its sending rate when it experiences
       congestion).  Examples include some UDP streaming applications
       for packet voice and video, and some multicast bulk data
       transport.  If no action is taken, such unresponsive flows could
       lead to a new congestion collapse.  Some applications can even
       increase their traffic volume in response to congestion (e.g. by
       adding forward error correction when loss is experienced), with
       the possibility that they contribute to congestion collapse."

Would be nice to have a citation or two in this paragraph (though I can
see why you might not want to).

"Lastly, some applications (e.g. current web browsers) open a
       large numbers of short TCP flows for a single session.  This can
       lead to each individual flow spending the majority of time in the
       exponential TCP slow start phase, rather than in TCP congestion
       avoidance.  The resulting traffic aggregate can therefore be much
       less responsive than a single standard TCP flow."

I note that HTTP/2 is on its way to publication and there are a large
number of existing implementations, so the characterization of "current
web browsers" seems a bit off. I would suggest something like "(e.g. web
browsers primarily supporting HTTP 1.1)."

-- Sec 7:
I think there's actually a really important privacy aspect that should be
called out here, which is that by virtue of recommending that AQM
algorithms not be dependent on specific transport or application
behaviors, network devices need not gain insight into upper layer
protocol information for the purpose of supporting AQM. That is, the
document's explicit recommendation for algorithms to be able to operate
in a transport- and application-agnostic fashion is a privacy-enhancing
feature.

-- Sec 9:
I'm a little surprised that almost all of the research referenced in this
document is from the 1990s, given recent attention that has been paid to
this topic.



From nobody Wed Feb 18 11:34:16 2015
Return-Path: <adrian@olddog.co.uk>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61F521A014C; Wed, 18 Feb 2015 11:34:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 Mfj-MqtTv0lx; Wed, 18 Feb 2015 11:34:11 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 161FE1A011D; Wed, 18 Feb 2015 11:34:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218193405.17233.32610.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 11:34:05 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/j48O4JbWfCAx_K1pbRb13Dvg16w>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Adrian Farrel's No Objection on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 19:34:12 -0000

Adrian Farrel has entered the following ballot position for
draft-ietf-aqm-recommendation-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Very readable. Thanks.



From nobody Wed Feb 18 11:34:17 2015
Return-Path: <adrian@olddog.co.uk>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 7AAAA1A015F; Wed, 18 Feb 2015 11:34:12 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61F521A014C; Wed, 18 Feb 2015 11:34:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 Mfj-MqtTv0lx; Wed, 18 Feb 2015 11:34:11 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 161FE1A011D; Wed, 18 Feb 2015 11:34:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218193405.17233.32610.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 11:34:05 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/j48O4JbWfCAx_K1pbRb13Dvg16w>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Adrian Farrel's No Objection on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 19:34:12 -0000

Adrian Farrel has entered the following ballot position for
draft-ietf-aqm-recommendation-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Very readable. Thanks.



From nobody Wed Feb 18 14:43:30 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A327B1A1B47; Wed, 18 Feb 2015 14:43:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 P2rnAWYRZ5vG; Wed, 18 Feb 2015 14:43:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 522901A0113; Wed, 18 Feb 2015 14:43:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218224325.29443.89305.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 14:43:25 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/SLEI58o5-zKsWqIkZcVkamK5-aU>
Cc: mehmet.ersue@nsn.com, rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Benoit Claise's Discuss on draft-ietf-aqm-recommendation-09: (with DISCUSS and COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 22:43:27 -0000

Benoit Claise has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Hopefully an easy DISCUSS.
  3.  The algorithms that the IETF recommends SHOULD NOT require
       operational (especially manual) configuration or tuning.

This sentence above could be understood in different ways. For example,
that any configuration is wrong. 
The ability to activate AQM is a good thing IMO. 
The section 4.3 title is closer to what you intend to say: "AQM
algorithms deployed SHOULD NOT require operational tuning"
The issue is that you only define what you mean by "operational
configuration" in section 4.3

Proposal:

OLD:
  3.  The algorithms that the IETF recommends SHOULD NOT require
       operational (especially manual) configuration or tuning.

NEW: 
  3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
configuration parameters. 

OLD:
4.3 AQM algorithms deployed SHOULD NOT require operational tuning

NEW:
4.3 AQM algorithm deployment SHOULD NOT require tuning


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

- RFC 2309 introduced the concept of "Active Queue Management" (AQM), a
   > class of technologies that, by signaling to common congestion-
   controlled transports such as TCP, manages the size of queues that

Remove >


-
  Network devices SHOULD use an AQM algorithm to measure local local
   congestion 

local local



From nobody Wed Feb 18 14:43:33 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id CF8A91A1B59; Wed, 18 Feb 2015 14:43:27 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A327B1A1B47; Wed, 18 Feb 2015 14:43:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 P2rnAWYRZ5vG; Wed, 18 Feb 2015 14:43:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 522901A0113; Wed, 18 Feb 2015 14:43:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218224325.29443.89305.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 14:43:25 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/SLEI58o5-zKsWqIkZcVkamK5-aU>
Cc: mehmet.ersue@nsn.com, rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Benoit Claise's Discuss on draft-ietf-aqm-recommendation-09: (with DISCUSS and COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 22:43:28 -0000

Benoit Claise has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Hopefully an easy DISCUSS.
  3.  The algorithms that the IETF recommends SHOULD NOT require
       operational (especially manual) configuration or tuning.

This sentence above could be understood in different ways. For example,
that any configuration is wrong. 
The ability to activate AQM is a good thing IMO. 
The section 4.3 title is closer to what you intend to say: "AQM
algorithms deployed SHOULD NOT require operational tuning"
The issue is that you only define what you mean by "operational
configuration" in section 4.3

Proposal:

OLD:
  3.  The algorithms that the IETF recommends SHOULD NOT require
       operational (especially manual) configuration or tuning.

NEW: 
  3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
configuration parameters. 

OLD:
4.3 AQM algorithms deployed SHOULD NOT require operational tuning

NEW:
4.3 AQM algorithm deployment SHOULD NOT require tuning


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

- RFC 2309 introduced the concept of "Active Queue Management" (AQM), a
   > class of technologies that, by signaling to common congestion-
   controlled transports such as TCP, manages the size of queues that

Remove >


-
  Network devices SHOULD use an AQM algorithm to measure local local
   congestion 

local local



From nobody Wed Feb 18 20:51:29 2015
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2BD01A8749; Wed, 18 Feb 2015 20:51:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 CC2IfLsnVH29; Wed, 18 Feb 2015 20:51:26 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D6EB1A86E0; Wed, 18 Feb 2015 20:51:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150219045126.9881.4231.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 20:51:26 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/zenlF5bV9q9MRJn1BgNPiRedQhM>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Pete Resnick's No Objection on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 04:51:28 -0000

Pete Resnick has entered the following ballot position for
draft-ietf-aqm-recommendation-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

This document does not have the pre-5378 boilerplate. Have all of the
authors of 2309 actually signed the appropriate things, or does this
document need the pre-5378 boilerplate?



From nobody Wed Feb 18 20:51:34 2015
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 227341A86E0; Wed, 18 Feb 2015 20:51:28 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2BD01A8749; Wed, 18 Feb 2015 20:51:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 CC2IfLsnVH29; Wed, 18 Feb 2015 20:51:26 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D6EB1A86E0; Wed, 18 Feb 2015 20:51:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150219045126.9881.4231.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 20:51:26 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/zenlF5bV9q9MRJn1BgNPiRedQhM>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Pete Resnick's No Objection on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 04:51:28 -0000

Pete Resnick has entered the following ballot position for
draft-ietf-aqm-recommendation-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

This document does not have the pre-5378 boilerplate. Have all of the
authors of 2309 actually signed the appropriate things, or does this
document need the pre-5378 boilerplate?



From nobody Thu Feb 19 04:26:08 2015
Return-Path: <mls.ietf@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74D7F1A8A4E; Thu, 19 Feb 2015 04:26:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 4W40BasjkTnP; Thu, 19 Feb 2015 04:26:02 -0800 (PST)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 156EF1A8A46; Thu, 19 Feb 2015 04:25:56 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id em10so47723688wid.1; Thu, 19 Feb 2015 04:25:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=vFSS9muLr4CqyHPSnFbRf4XJfKpIs4r+Hjs+Dk8H3dY=; b=YIpWfYfBUhqN1ChvIqvluk+ZoEcjCJjEvxj4QBgi6J9roMYQDHl3Rl3rAaHUGmxi8Y EZBMTcu+S9nTJYepLA2+nsOWPAbthASBpzdVYNtciepwgToJzYBrkWiKVDAdsIr6QOW5 DRfnLDUvmZSDME/JSuQUeFUF5YaXqwk5QkhuzgGCxOe6KDgLFYgyHBUZUZDmXvEFTiui w2YY3Q3FhuKT4UvRY5ojp0H3vQGK0jvlGOe34C+fa0hwQ6xZe0y3Lroq2ubFpZNO8k99 9y/qBnE1y2f84nkTkJjjhK6KEegL5ZgTh6XSPGsbOE/uetlvv+bXCyFPM+m8vsQEFcTI sDgA==
X-Received: by 10.194.20.67 with SMTP id l3mr8643918wje.94.1424348754805; Thu, 19 Feb 2015 04:25:54 -0800 (PST)
Received: from Martins-MBP.fritz.box ([2001:1a80:2807:cb00:74cc:baad:e00d:f46]) by mx.google.com with ESMTPSA id dt7sm23909719wib.19.2015.02.19.04.25.53 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Feb 2015 04:25:54 -0800 (PST)
Message-ID: <54E5D651.2050005@gmail.com>
Date: Thu, 19 Feb 2015 13:25:53 +0100
From: Martin Stiemerling <mls.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>, The IESG <iesg@ietf.org>,  rs@netapp.com, aqm-chairs@ietf.org
References: <20150219045126.9881.4231.idtracker@ietfa.amsl.com>
In-Reply-To: <20150219045126.9881.4231.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/Vips8r6fddc3IH2jwTMOJbRZm40>
Cc: draft-ietf-aqm-recommendation.all@ietf.org, aqm@ietf.org
Subject: Re: [aqm] Pete Resnick's No Objection on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 12:26:04 -0000

Pete,

Good catch!

Authors & doc shepherd: Did the author sign anything?

If not, we need the pre-5378 boiler plate.

Thanks,

   Martin

Am 19.02.15 um 05:51 schrieb Pete Resnick:
> Pete Resnick has entered the following ballot position for
> draft-ietf-aqm-recommendation-09: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> This document does not have the pre-5378 boilerplate. Have all of the
> authors of 2309 actually signed the appropriate things, or does this
> document need the pre-5378 boilerplate?
>
>


From nobody Thu Feb 19 04:26:09 2015
Return-Path: <mls.ietf@gmail.com>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 93DB41A8A46; Thu, 19 Feb 2015 04:26:04 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74D7F1A8A4E; Thu, 19 Feb 2015 04:26:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 4W40BasjkTnP; Thu, 19 Feb 2015 04:26:02 -0800 (PST)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 156EF1A8A46; Thu, 19 Feb 2015 04:25:56 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id em10so47723688wid.1; Thu, 19 Feb 2015 04:25:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=vFSS9muLr4CqyHPSnFbRf4XJfKpIs4r+Hjs+Dk8H3dY=; b=YIpWfYfBUhqN1ChvIqvluk+ZoEcjCJjEvxj4QBgi6J9roMYQDHl3Rl3rAaHUGmxi8Y EZBMTcu+S9nTJYepLA2+nsOWPAbthASBpzdVYNtciepwgToJzYBrkWiKVDAdsIr6QOW5 DRfnLDUvmZSDME/JSuQUeFUF5YaXqwk5QkhuzgGCxOe6KDgLFYgyHBUZUZDmXvEFTiui w2YY3Q3FhuKT4UvRY5ojp0H3vQGK0jvlGOe34C+fa0hwQ6xZe0y3Lroq2ubFpZNO8k99 9y/qBnE1y2f84nkTkJjjhK6KEegL5ZgTh6XSPGsbOE/uetlvv+bXCyFPM+m8vsQEFcTI sDgA==
X-Received: by 10.194.20.67 with SMTP id l3mr8643918wje.94.1424348754805; Thu, 19 Feb 2015 04:25:54 -0800 (PST)
Received: from Martins-MBP.fritz.box ([2001:1a80:2807:cb00:74cc:baad:e00d:f46]) by mx.google.com with ESMTPSA id dt7sm23909719wib.19.2015.02.19.04.25.53 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Feb 2015 04:25:54 -0800 (PST)
Message-ID: <54E5D651.2050005@gmail.com>
Date: Thu, 19 Feb 2015 13:25:53 +0100
From: Martin Stiemerling <mls.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>, The IESG <iesg@ietf.org>,  rs@netapp.com, aqm-chairs@ietf.org
References: <20150219045126.9881.4231.idtracker@ietfa.amsl.com>
In-Reply-To: <20150219045126.9881.4231.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/Vips8r6fddc3IH2jwTMOJbRZm40>
Cc: draft-ietf-aqm-recommendation.all@ietf.org, aqm@ietf.org
Subject: Re: [aqm] Pete Resnick's No Objection on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 12:26:04 -0000

Pete,

Good catch!

Authors & doc shepherd: Did the author sign anything?

If not, we need the pre-5378 boiler plate.

Thanks,

   Martin

Am 19.02.15 um 05:51 schrieb Pete Resnick:
> Pete Resnick has entered the following ballot position for
> draft-ietf-aqm-recommendation-09: No Objection
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> This document does not have the pre-5378 boilerplate. Have all of the
> authors of 2309 actually signed the appropriate things, or does this
> document need the pre-5378 boilerplate?
>
>


From nobody Thu Feb 19 04:30:46 2015
Return-Path: <mls.ietf@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A3B01A8F42; Thu, 19 Feb 2015 04:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 ODogHBNZhbVN; Thu, 19 Feb 2015 04:30:37 -0800 (PST)
Received: from mail-we0-f178.google.com (mail-we0-f178.google.com [74.125.82.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73C931A889C; Thu, 19 Feb 2015 04:30:37 -0800 (PST)
Received: by wesq59 with SMTP id q59so7033985wes.1; Thu, 19 Feb 2015 04:30:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=PsN634AtOtHW8KxwGmQa7z69Er7UG5HP6U7t4eA6o4I=; b=khQLZQLw7Obtdnl/LXTcEeO77huPiiTY6yqK25wn8K5OUhrP/vIwjKjlUsmhI8wVDk Yz1Hf+ol5CsLCLl7aEIZUn1rwQd/LGwPAAtfkwYHqvmde6BuC7fu4rAlWPrBbww+USzj 1MjZOzyY5I76ygpe8391pDry/arodKmGe9K3YdsXIozCU2GhsKg1Sw3inZdoCJOaN68J J9jjPzvIzpLUDbCi/iHJd9/W6+q/ZA6CT/Y44JX4fXxgNaeByXomUAMXW6rJ2IQISROe agiympvW8RhKWa95+ozDIS011516Z8xyLLvtT3hvm2VJUfr8TJT/B8QEy9y0sokO7vaj 9WKQ==
X-Received: by 10.180.107.71 with SMTP id ha7mr12773751wib.23.1424349036231; Thu, 19 Feb 2015 04:30:36 -0800 (PST)
Received: from Martins-MBP.fritz.box (port-92-202-26-143.dynamic.qsc.de. [92.202.26.143]) by mx.google.com with ESMTPSA id pp10sm37201827wjc.31.2015.02.19.04.30.35 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Feb 2015 04:30:35 -0800 (PST)
Message-ID: <54E5D76A.7070603@gmail.com>
Date: Thu, 19 Feb 2015 13:30:34 +0100
From: Martin Stiemerling <mls.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
References: <20150218224325.29443.89305.idtracker@ietfa.amsl.com>
In-Reply-To: <20150218224325.29443.89305.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/oW-36aUWYmBA_LsPBJ6lMhMlXHk>
Cc: mehmet.ersue@nsn.com, rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: Re: [aqm] Benoit Claise's Discuss on draft-ietf-aqm-recommendation-09: (with DISCUSS and COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 12:30:42 -0000

Hi Benoit,


>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Hopefully an easy DISCUSS.
>    3.  The algorithms that the IETF recommends SHOULD NOT require
>         operational (especially manual) configuration or tuning.
>
> This sentence above could be understood in different ways. For example,
> that any configuration is wrong.
> The ability to activate AQM is a good thing IMO.
> The section 4.3 title is closer to what you intend to say: "AQM
> algorithms deployed SHOULD NOT require operational tuning"
> The issue is that you only define what you mean by "operational
> configuration" in section 4.3
>
> Proposal:
>
> OLD:
>    3.  The algorithms that the IETF recommends SHOULD NOT require
>         operational (especially manual) configuration or tuning.
>
> NEW:
>    3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
> configuration parameters.

I do not see how your proposal is better than the original text.
The original text says that the IETF is not recommending any operational 
configuration or tuning. You proposal is globally saying that AQM 
algorithms should not require tuning, etc.

>
> OLD:
> 4.3 AQM algorithms deployed SHOULD NOT require operational tuning
>
> NEW:
> 4.3 AQM algorithm deployment SHOULD NOT require tuning

I see even less why this change is required and it makes an even 
stronger case. The first statement says that tuning in operations should 
not happen while your statement is saying that in general no tuning is 
required (even before going for operational).

   Martin


From nobody Thu Feb 19 04:30:54 2015
Return-Path: <mls.ietf@gmail.com>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id C54E61A8FD7; Thu, 19 Feb 2015 04:30:42 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A3B01A8F42; Thu, 19 Feb 2015 04:30:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 ODogHBNZhbVN; Thu, 19 Feb 2015 04:30:37 -0800 (PST)
Received: from mail-we0-f178.google.com (mail-we0-f178.google.com [74.125.82.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73C931A889C; Thu, 19 Feb 2015 04:30:37 -0800 (PST)
Received: by wesq59 with SMTP id q59so7033985wes.1; Thu, 19 Feb 2015 04:30:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=PsN634AtOtHW8KxwGmQa7z69Er7UG5HP6U7t4eA6o4I=; b=khQLZQLw7Obtdnl/LXTcEeO77huPiiTY6yqK25wn8K5OUhrP/vIwjKjlUsmhI8wVDk Yz1Hf+ol5CsLCLl7aEIZUn1rwQd/LGwPAAtfkwYHqvmde6BuC7fu4rAlWPrBbww+USzj 1MjZOzyY5I76ygpe8391pDry/arodKmGe9K3YdsXIozCU2GhsKg1Sw3inZdoCJOaN68J J9jjPzvIzpLUDbCi/iHJd9/W6+q/ZA6CT/Y44JX4fXxgNaeByXomUAMXW6rJ2IQISROe agiympvW8RhKWa95+ozDIS011516Z8xyLLvtT3hvm2VJUfr8TJT/B8QEy9y0sokO7vaj 9WKQ==
X-Received: by 10.180.107.71 with SMTP id ha7mr12773751wib.23.1424349036231; Thu, 19 Feb 2015 04:30:36 -0800 (PST)
Received: from Martins-MBP.fritz.box (port-92-202-26-143.dynamic.qsc.de. [92.202.26.143]) by mx.google.com with ESMTPSA id pp10sm37201827wjc.31.2015.02.19.04.30.35 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Feb 2015 04:30:35 -0800 (PST)
Message-ID: <54E5D76A.7070603@gmail.com>
Date: Thu, 19 Feb 2015 13:30:34 +0100
From: Martin Stiemerling <mls.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>, The IESG <iesg@ietf.org>
References: <20150218224325.29443.89305.idtracker@ietfa.amsl.com>
In-Reply-To: <20150218224325.29443.89305.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/oW-36aUWYmBA_LsPBJ6lMhMlXHk>
Cc: mehmet.ersue@nsn.com, rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: Re: [aqm] Benoit Claise's Discuss on draft-ietf-aqm-recommendation-09: (with DISCUSS and COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 12:30:42 -0000

Hi Benoit,


>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Hopefully an easy DISCUSS.
>    3.  The algorithms that the IETF recommends SHOULD NOT require
>         operational (especially manual) configuration or tuning.
>
> This sentence above could be understood in different ways. For example,
> that any configuration is wrong.
> The ability to activate AQM is a good thing IMO.
> The section 4.3 title is closer to what you intend to say: "AQM
> algorithms deployed SHOULD NOT require operational tuning"
> The issue is that you only define what you mean by "operational
> configuration" in section 4.3
>
> Proposal:
>
> OLD:
>    3.  The algorithms that the IETF recommends SHOULD NOT require
>         operational (especially manual) configuration or tuning.
>
> NEW:
>    3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
> configuration parameters.

I do not see how your proposal is better than the original text.
The original text says that the IETF is not recommending any operational 
configuration or tuning. You proposal is globally saying that AQM 
algorithms should not require tuning, etc.

>
> OLD:
> 4.3 AQM algorithms deployed SHOULD NOT require operational tuning
>
> NEW:
> 4.3 AQM algorithm deployment SHOULD NOT require tuning

I see even less why this change is required and it makes an even 
stronger case. The first statement says that tuning in operations should 
not happen while your statement is saying that in general no tuning is 
required (even before going for operational).

   Martin


From nobody Thu Feb 19 04:54:44 2015
Return-Path: <ted.lemon@nominum.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 035481A903E; Thu, 19 Feb 2015 04:54:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 S9cPKZwTfEdp; Thu, 19 Feb 2015 04:54:41 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 508FC1A87A2; Thu, 19 Feb 2015 04:54:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Ted Lemon" <ted.lemon@nominum.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150219125441.21996.18652.idtracker@ietfa.amsl.com>
Date: Thu, 19 Feb 2015 04:54:41 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/6DBKOpA5__3vegGH7qh-quWN3dM>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Ted Lemon's Yes on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 12:54:43 -0000

Ted Lemon has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I'm quite surprised that the introduction doesn't mention the problems
that high or unpredictable latency can cause with flows that are
attempting to do congestion control at the ends (e.g., TCP).   If I were
reading this without already knowing about that, I would assume that the
goal of this document is to reduce latency for the benefit of
applications that require low latency, like VoIP and gaming.   It would
be nice if the introduction made mention of the issue of high latency as
it affects TCP flows.

The document also talks about congestion collapse as a future risk to be
prevented, but I think that this isn't telling the whole story: users of
the Internet see localized congestion collapse quite frequently, and have
done for quite some time.   It's essentially normal network behavior in
hotels, cafes and on airplanes: anywhere where available bandwidth is
substantially short of demand.   I don't think this is a problem with
technical accuracy, but I think someone reading this document who isn't
an expert on congestion control might not realize that this document is
talking about that specific sort of failure mode as well as failures deep
in the network.

I'm really happy to see this document being published.  The above
comments are just suggestions based on my particular concerns about
congestion, and do not reflect any degree of expertise, so if they seem
exceptionally clueless you should just ignore them.



From nobody Thu Feb 19 04:54:47 2015
Return-Path: <ted.lemon@nominum.com>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 3181B1A87A2; Thu, 19 Feb 2015 04:54:43 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 035481A903E; Thu, 19 Feb 2015 04:54:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 S9cPKZwTfEdp; Thu, 19 Feb 2015 04:54:41 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 508FC1A87A2; Thu, 19 Feb 2015 04:54:41 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Ted Lemon" <ted.lemon@nominum.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150219125441.21996.18652.idtracker@ietfa.amsl.com>
Date: Thu, 19 Feb 2015 04:54:41 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/6DBKOpA5__3vegGH7qh-quWN3dM>
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Ted Lemon's Yes on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 12:54:43 -0000

Ted Lemon has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I'm quite surprised that the introduction doesn't mention the problems
that high or unpredictable latency can cause with flows that are
attempting to do congestion control at the ends (e.g., TCP).   If I were
reading this without already knowing about that, I would assume that the
goal of this document is to reduce latency for the benefit of
applications that require low latency, like VoIP and gaming.   It would
be nice if the introduction made mention of the issue of high latency as
it affects TCP flows.

The document also talks about congestion collapse as a future risk to be
prevented, but I think that this isn't telling the whole story: users of
the Internet see localized congestion collapse quite frequently, and have
done for quite some time.   It's essentially normal network behavior in
hotels, cafes and on airplanes: anywhere where available bandwidth is
substantially short of demand.   I don't think this is a problem with
technical accuracy, but I think someone reading this document who isn't
an expert on congestion control might not realize that this document is
talking about that specific sort of failure mode as well as failures deep
in the network.

I'm really happy to see this document being published.  The above
comments are just suggestions based on my particular concerns about
congestion, and do not reflect any degree of expertise, so if they seem
exceptionally clueless you should just ignore them.



From nobody Thu Feb 19 08:23:12 2015
Return-Path: <wes@mti-systems.com>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 99D891A9153; Thu, 19 Feb 2015 08:23:11 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AECA1A897D for <xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com>; Thu, 19 Feb 2015 08:23:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable
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 Ut8gyOGlracE for <xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com>; Thu, 19 Feb 2015 08:23:10 -0800 (PST)
Received: from atl4mhob09.myregisteredsite.com (atl4mhob09.myregisteredsite.com [209.17.115.47]) by ietfa.amsl.com (Postfix) with ESMTP id 0F64F1A9153 for <draft-ietf-aqm-recommendation.all@ietf.org>; Thu, 19 Feb 2015 08:23:00 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob09.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id t1JGMx6p018491 for <draft-ietf-aqm-recommendation.all@ietf.org>; Thu, 19 Feb 2015 11:22:59 -0500
Received: (qmail 11959 invoked by uid 0); 19 Feb 2015 16:22:59 -0000
X-TCPREMOTEIP: 207.54.183.210
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.112?) (wes@mti-systems.com@207.54.183.210) by 0 with ESMTPA; 19 Feb 2015 16:22:59 -0000
Message-ID: <54E60DD9.6010409@mti-systems.com>
Date: Thu, 19 Feb 2015 11:22:49 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Martin Stiemerling <mls.ietf@gmail.com>, Pete Resnick <presnick@qti.qualcomm.com>, The IESG <iesg@ietf.org>, rs@netapp.com, aqm-chairs@ietf.org
References: <20150219045126.9881.4231.idtracker@ietfa.amsl.com> <54E5D651.2050005@gmail.com>
In-Reply-To: <54E5D651.2050005@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/rra-_TGDn0zKDKCVJSvnQBQPuH8>
Cc: draft-ietf-aqm-recommendation.all@ietf.org, aqm@ietf.org
Subject: Re: [aqm] Pete Resnick's No Objection on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 16:23:11 -0000

On 2/19/2015 7:25 AM, Martin Stiemerling wrote:
> Pete,
> 
> Good catch!
> 
> Authors & doc shepherd: Did the author sign anything?
> 
> If not, we need the pre-5378 boiler plate.
> 


No they didn't sign anything.  In fact many of them have been
difficult/impossible to reach, and the author list on 2309 was the
entire end-to-end RG at the time, so it's quite long.

It seems to me that we certainly need to use the pre-5378 boilerplate.
Thanks for catching this, Pete!


-- 
Wes Eddy
MTI Systems


From nobody Thu Feb 19 08:23:20 2015
Return-Path: <wes@mti-systems.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDD8D1A9238 for <aqm@ietfa.amsl.com>; Thu, 19 Feb 2015 08:23:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable
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 0X7txwXY2nqm for <aqm@ietfa.amsl.com>; Thu, 19 Feb 2015 08:23:12 -0800 (PST)
Received: from atl4mhob03.myregisteredsite.com (atl4mhob03.myregisteredsite.com [209.17.115.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0481C1A923C for <aqm@ietf.org>; Thu, 19 Feb 2015 08:23:01 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob03.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id t1JGMxWB005022 for <aqm@ietf.org>; Thu, 19 Feb 2015 11:23:00 -0500
Received: (qmail 11959 invoked by uid 0); 19 Feb 2015 16:22:59 -0000
X-TCPREMOTEIP: 207.54.183.210
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.112?) (wes@mti-systems.com@207.54.183.210) by 0 with ESMTPA; 19 Feb 2015 16:22:59 -0000
Message-ID: <54E60DD9.6010409@mti-systems.com>
Date: Thu, 19 Feb 2015 11:22:49 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Martin Stiemerling <mls.ietf@gmail.com>, Pete Resnick <presnick@qti.qualcomm.com>, The IESG <iesg@ietf.org>, rs@netapp.com, aqm-chairs@ietf.org
References: <20150219045126.9881.4231.idtracker@ietfa.amsl.com> <54E5D651.2050005@gmail.com>
In-Reply-To: <54E5D651.2050005@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/rra-_TGDn0zKDKCVJSvnQBQPuH8>
Cc: draft-ietf-aqm-recommendation.all@ietf.org, aqm@ietf.org
Subject: Re: [aqm] Pete Resnick's No Objection on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 16:23:14 -0000

On 2/19/2015 7:25 AM, Martin Stiemerling wrote:
> Pete,
> 
> Good catch!
> 
> Authors & doc shepherd: Did the author sign anything?
> 
> If not, we need the pre-5378 boiler plate.
> 


No they didn't sign anything.  In fact many of them have been
difficult/impossible to reach, and the author list on 2309 was the
entire end-to-end RG at the time, so it's quite long.

It seems to me that we certainly need to use the pre-5378 boilerplate.
Thanks for catching this, Pete!


-- 
Wes Eddy
MTI Systems


From nobody Thu Feb 19 08:24:16 2015
Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B0851A8853; Wed, 18 Feb 2015 08:42:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001] autolearn=ham
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 Cbkb2UOrASsu; Wed, 18 Feb 2015 08:42:52 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB991A8852; Wed, 18 Feb 2015 08:42:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218164252.28369.52537.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 08:42:52 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/O2zQw-oQeFbSz3X7iZ_oBbNnnJk>
X-Mailman-Approved-At: Thu, 19 Feb 2015 08:24:09 -0800
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Kathleen Moriarty's No Objection on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 16:42:54 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-aqm-recommendation-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for your work on this draft, it looks good.  There are some tiny
nits that the SecDir reviewer found that you might want to consider:
https://www.ietf.org/mail-archive/web/secdir/current/msg05357.html



From nobody Thu Feb 19 08:24:19 2015
Return-Path: <Kathleen.Moriarty.ietf@gmail.com>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 48B631A8852; Wed, 18 Feb 2015 08:42:54 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B0851A8853; Wed, 18 Feb 2015 08:42:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001] autolearn=ham
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 Cbkb2UOrASsu; Wed, 18 Feb 2015 08:42:52 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB991A8852; Wed, 18 Feb 2015 08:42:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Kathleen Moriarty" <Kathleen.Moriarty.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150218164252.28369.52537.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 08:42:52 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/O2zQw-oQeFbSz3X7iZ_oBbNnnJk>
X-Mailman-Approved-At: Thu, 19 Feb 2015 08:24:11 -0800
Cc: rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Kathleen Moriarty's No Objection on draft-ietf-aqm-recommendation-09: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 16:42:54 -0000

Kathleen Moriarty has entered the following ballot position for
draft-ietf-aqm-recommendation-09: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for your work on this draft, it looks good.  There are some tiny
nits that the SecDir reviewer found that you might want to consider:
https://www.ietf.org/mail-archive/web/secdir/current/msg05357.html



From nobody Thu Feb 19 11:26:38 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 664391A0039; Thu, 19 Feb 2015 11:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] autolearn=ham
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 J-QTSVMvDfQw; Thu, 19 Feb 2015 11:26:35 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 486A21A003A; Thu, 19 Feb 2015 11:26:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150219192625.24511.15182.idtracker@ietfa.amsl.com>
Date: Thu, 19 Feb 2015 11:26:25 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/pW9Cj9CWtYclGXH01QXZZ06MJ6M>
Subject: [aqm] ID Tracker State Update Notice: <draft-ietf-aqm-recommendation-09.txt>
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:26:36 -0000

IESG state changed to IESG Evaluation::AD Followup from IESG Evaluation
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/


From nobody Thu Feb 19 11:26:39 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 8439B1A00A2; Thu, 19 Feb 2015 11:26:36 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 664391A0039; Thu, 19 Feb 2015 11:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] autolearn=ham
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 J-QTSVMvDfQw; Thu, 19 Feb 2015 11:26:35 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 486A21A003A; Thu, 19 Feb 2015 11:26:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150219192625.24511.15182.idtracker@ietfa.amsl.com>
Date: Thu, 19 Feb 2015 11:26:25 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/pW9Cj9CWtYclGXH01QXZZ06MJ6M>
Subject: [aqm] ID Tracker State Update Notice: <draft-ietf-aqm-recommendation-09.txt>
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:26:36 -0000

IESG state changed to IESG Evaluation::AD Followup from IESG Evaluation
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/


From nobody Mon Feb 23 01:18:16 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90E9D1A0358; Mon, 23 Feb 2015 01:18:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.012
X-Spam-Level: 
X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 b1Xc9meK_flt; Mon, 23 Feb 2015 01:18:09 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 5D8881A014C; Mon, 23 Feb 2015 01:18:09 -0800 (PST)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 3CA5E1B00199; Mon, 23 Feb 2015 09:18:24 +0000 (GMT)
Received: from 139.133.204.3 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Mon, 23 Feb 2015 09:17:49 -0000
Message-ID: <9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk>
In-Reply-To: <20150218224325.29443.89305.idtracker@ietfa.amsl.com>
References: <20150218224325.29443.89305.idtracker@ietfa.amsl.com>
Date: Mon, 23 Feb 2015 09:17:49 -0000
From: gorry@erg.abdn.ac.uk
To: "Benoit Claise" <bclaise@cisco.com>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/KEauFBxzKDYTERBXKM1I3kUSmqc>
Cc: rs@netapp.com, aqm-chairs@ietf.org, mehmet.ersue@nsn.com, The IESG <iesg@ietf.org>, draft-ietf-aqm-recommendation.all@ietf.org, aqm@ietf.org, fred@cisco.com
Subject: Re: [aqm] Benoit Claise's Discuss on draft-ietf-aqm-recommendation-09: (with DISCUSS and COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 23 Feb 2015 09:18:11 -0000

Benoit,

We think we have resolved the remaining issues and would like to propose
text that we think could address you DISCUSS:

We think our point was that tuning should not be required
*in*the*normal*case*, not
that they should *never* require tuning (I'm not sure we have created
anything that
is 100% auto-tuning). I'm OK with his phrasing in both cases, but would
suggest the
words "in common use cases" should be added:

  3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
configuration
parameters in common use cases.

4.3 AQM algorithm deployment SHOULD NOT require tuning in common use cases.

Please let us know your thoughts,

Fred & Gorry

> Benoit Claise has entered the following ballot position for
> draft-ietf-aqm-recommendation-09: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Hopefully an easy DISCUSS.
>   3.  The algorithms that the IETF recommends SHOULD NOT require
>        operational (especially manual) configuration or tuning.
>
> This sentence above could be understood in different ways. For example,
> that any configuration is wrong.
> The ability to activate AQM is a good thing IMO.
> The section 4.3 title is closer to what you intend to say: "AQM
> algorithms deployed SHOULD NOT require operational tuning"
> The issue is that you only define what you mean by "operational
> configuration" in section 4.3
>
> Proposal:
>
> OLD:
>   3.  The algorithms that the IETF recommends SHOULD NOT require
>        operational (especially manual) configuration or tuning.
>
> NEW:
>   3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
> configuration parameters.
>
> OLD:
> 4.3 AQM algorithms deployed SHOULD NOT require operational tuning
>
> NEW:
> 4.3 AQM algorithm deployment SHOULD NOT require tuning
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> - RFC 2309 introduced the concept of "Active Queue Management" (AQM), a
>    > class of technologies that, by signaling to common congestion-
>    controlled transports such as TCP, manages the size of queues that
>
> Remove >
>
>
> -
>   Network devices SHOULD use an AQM algorithm to measure local local
>    congestion
>
> local local
>
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>



From nobody Mon Feb 23 01:18:18 2015
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id B70061A014C; Mon, 23 Feb 2015 01:18:11 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90E9D1A0358; Mon, 23 Feb 2015 01:18:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.012
X-Spam-Level: 
X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 b1Xc9meK_flt; Mon, 23 Feb 2015 01:18:09 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 5D8881A014C; Mon, 23 Feb 2015 01:18:09 -0800 (PST)
Received: from erg.abdn.ac.uk (galactica.erg.abdn.ac.uk [139.133.210.32]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 3CA5E1B00199; Mon, 23 Feb 2015 09:18:24 +0000 (GMT)
Received: from 139.133.204.3 (SquirrelMail authenticated user gorry) by erg.abdn.ac.uk with HTTP; Mon, 23 Feb 2015 09:17:49 -0000
Message-ID: <9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk>
In-Reply-To: <20150218224325.29443.89305.idtracker@ietfa.amsl.com>
References: <20150218224325.29443.89305.idtracker@ietfa.amsl.com>
Date: Mon, 23 Feb 2015 09:17:49 -0000
From: gorry@erg.abdn.ac.uk
To: "Benoit Claise" <bclaise@cisco.com>
User-Agent: SquirrelMail/1.4.23 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/KEauFBxzKDYTERBXKM1I3kUSmqc>
Cc: rs@netapp.com, aqm-chairs@ietf.org, mehmet.ersue@nsn.com, The IESG <iesg@ietf.org>, draft-ietf-aqm-recommendation.all@ietf.org, aqm@ietf.org, fred@cisco.com
Subject: Re: [aqm] Benoit Claise's Discuss on draft-ietf-aqm-recommendation-09: (with DISCUSS and COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 23 Feb 2015 09:18:11 -0000

Benoit,

We think we have resolved the remaining issues and would like to propose
text that we think could address you DISCUSS:

We think our point was that tuning should not be required
*in*the*normal*case*, not
that they should *never* require tuning (I'm not sure we have created
anything that
is 100% auto-tuning). I'm OK with his phrasing in both cases, but would
suggest the
words "in common use cases" should be added:

  3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
configuration
parameters in common use cases.

4.3 AQM algorithm deployment SHOULD NOT require tuning in common use cases.

Please let us know your thoughts,

Fred & Gorry

> Benoit Claise has entered the following ballot position for
> draft-ietf-aqm-recommendation-09: Discuss
>
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
>
>
> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
>
>
> The document, along with other ballot positions, can be found here:
> http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/
>
>
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> Hopefully an easy DISCUSS.
>   3.  The algorithms that the IETF recommends SHOULD NOT require
>        operational (especially manual) configuration or tuning.
>
> This sentence above could be understood in different ways. For example,
> that any configuration is wrong.
> The ability to activate AQM is a good thing IMO.
> The section 4.3 title is closer to what you intend to say: "AQM
> algorithms deployed SHOULD NOT require operational tuning"
> The issue is that you only define what you mean by "operational
> configuration" in section 4.3
>
> Proposal:
>
> OLD:
>   3.  The algorithms that the IETF recommends SHOULD NOT require
>        operational (especially manual) configuration or tuning.
>
> NEW:
>   3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
> configuration parameters.
>
> OLD:
> 4.3 AQM algorithms deployed SHOULD NOT require operational tuning
>
> NEW:
> 4.3 AQM algorithm deployment SHOULD NOT require tuning
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> - RFC 2309 introduced the concept of "Active Queue Management" (AQM), a
>    > class of technologies that, by signaling to common congestion-
>    controlled transports such as TCP, manages the size of queues that
>
> Remove >
>
>
> -
>   Network devices SHOULD use an AQM algorithm to measure local local
>    congestion
>
> local local
>
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>



From nobody Mon Feb 23 10:40:29 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A08E81A1EEC; Mon, 23 Feb 2015 10:40:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 OJZcp5BhD_uv; Mon, 23 Feb 2015 10:40:24 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B1D431A1B87; Mon, 23 Feb 2015 10:40:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150223184024.28534.95922.idtracker@ietfa.amsl.com>
Date: Mon, 23 Feb 2015 10:40:24 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/Y6OXTvyZgjgGCFJ85BkBdLkJSZo>
Cc: aqm@ietf.org
Subject: [aqm] I-D Action: draft-ietf-aqm-recommendation-10.txt
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 23 Feb 2015 18:40:26 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Active Queue Management and Packet Scheduling Working Group of the IETF.

        Title           : IETF Recommendations Regarding Active Queue Management
        Authors         : Fred Baker
                          Godred Fairhurst
	Filename        : draft-ietf-aqm-recommendation-10.txt
	Pages           : 31
	Date            : 2015-02-23

Abstract:
   This memo presents recommendations to the Internet community
   concerning measures to improve and preserve Internet performance.  It
   presents a strong recommendation for testing, standardization, and
   widespread deployment of active queue management (AQM) in network
   devices, to improve the performance of today's Internet.  It also
   urges a concerted effort of research, measurement, and ultimate
   deployment of AQM mechanisms to protect the Internet from flows that
   are not sufficiently responsive to congestion notification.

   The note replaces the recommendations of RFC 2309 based on fifteen
   years of experience and new research.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-aqm-recommendation-10

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-recommendation-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Feb 23 10:40:45 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C4EE1A1F70; Mon, 23 Feb 2015 10:40:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 FlkGBqE7r6xT; Mon, 23 Feb 2015 10:40:26 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E3B581A1BE4; Mon, 23 Feb 2015 10:40:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>, <mls.ietf@gmail.com>, <bclaise@cisco.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150223184024.28534.17222.idtracker@ietfa.amsl.com>
Date: Mon, 23 Feb 2015 10:40:24 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/M1b11oshHjyihK8PAlXaNdJqBO0>
Subject: [aqm] New Version Notification - draft-ietf-aqm-recommendation-10.txt
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 23 Feb 2015 18:40:36 -0000

A new version (-10) has been submitted for draft-ietf-aqm-recommendation:
http://www.ietf.org/internet-drafts/draft-ietf-aqm-recommendation-10.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-recommendation-10

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.


From nobody Mon Feb 23 10:40:46 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 4AD6F1A212D; Mon, 23 Feb 2015 10:40:36 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C4EE1A1F70; Mon, 23 Feb 2015 10:40:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 FlkGBqE7r6xT; Mon, 23 Feb 2015 10:40:26 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E3B581A1BE4; Mon, 23 Feb 2015 10:40:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>, <mls.ietf@gmail.com>, <bclaise@cisco.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150223184024.28534.17222.idtracker@ietfa.amsl.com>
Date: Mon, 23 Feb 2015 10:40:24 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/M1b11oshHjyihK8PAlXaNdJqBO0>
Subject: [aqm] New Version Notification - draft-ietf-aqm-recommendation-10.txt
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 23 Feb 2015 18:40:36 -0000

A new version (-10) has been submitted for draft-ietf-aqm-recommendation:
http://www.ietf.org/internet-drafts/draft-ietf-aqm-recommendation-10.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-recommendation-10

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.


From nobody Mon Feb 23 19:40:11 2015
Return-Path: <wes@mti-systems.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFE11A00F6 for <aqm@ietfa.amsl.com>; Mon, 23 Feb 2015 19:40:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 jGzxPLDzftie for <aqm@ietfa.amsl.com>; Mon, 23 Feb 2015 19:40:08 -0800 (PST)
Received: from atl4mhob06.myregisteredsite.com (atl4mhob06.myregisteredsite.com [209.17.115.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2612E1A009E for <aqm@ietf.org>; Mon, 23 Feb 2015 19:40:07 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob06.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id t1O3e6pW030134 for <aqm@ietf.org>; Mon, 23 Feb 2015 22:40:06 -0500
Received: (qmail 17793 invoked by uid 0); 24 Feb 2015 03:40:06 -0000
X-TCPREMOTEIP: 69.81.157.169
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.112?) (wes@mti-systems.com@69.81.157.169) by 0 with ESMTPA; 24 Feb 2015 03:40:06 -0000
Message-ID: <54EBF293.3030105@mti-systems.com>
Date: Mon, 23 Feb 2015 22:40:03 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "aqm@ietf.org" <aqm@ietf.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/rVQEu5kt_egr0aDdteqka3PsQE0>
Subject: [aqm] agenda for IETF 92 / Dallas
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 03:40:10 -0000

Greetings AQMers!  We requested a short AQM meeting slot at the upcoming
IETF 92 meeting in Dallas, and we received a 1-hour slot on Tuesday:
https://datatracker.ietf.org/meeting/92/agenda.html

Since this is not a lot of time, we'll need to prioritize the work that
is discussed to what requires the face-to-face time in order to make
progress on.

For active draft editors, please let us know via this list or
aqm-chairs@tools.ietf.org what you think your meeting time needs are,
so we can put together an agenda.  If you don't need meeting time now,
or would like to use an interim telecon to assist in gathering
feedback, please also let us know.

For others, please read the drafts, comment on this mailing list, and
help us to review and complete them:
https://datatracker.ietf.org/wg/aqm/documents/

Thanks in advance!

-- 
Wes Eddy
MTI Systems


From nobody Tue Feb 24 02:04:35 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 168231A6F34; Tue, 24 Feb 2015 02:04:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 xzkBvlPwuiuj; Tue, 24 Feb 2015 02:04:28 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0C7E1A0379; Tue, 24 Feb 2015 02:04:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10947; q=dns/txt; s=iport; t=1424772268; x=1425981868; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=7h/NEaZ5uOaEEMYs3MHh5MAzTFB7kPvLMGVFCBpc2Rg=; b=d8AhdvIiDclDPhEoAT6QUdFv4NYyRIIIt1L1K7BnM6mXKnl2oe66lp80 /936TPXWSEqo4F8Obgg5NBOTtRq/argAh0+F3Va2In1bNnLJ5w3ZKXyfq KDIplNlW2CYWOMtQ0chkCF8UqO4nTRZhzmAqWfJ0F+58x9QcSR0OaniKo g=;
X-IronPort-AV: E=Sophos;i="5.09,637,1418083200";  d="scan'208,217";a="354720204"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 24 Feb 2015 10:04:26 +0000
Received: from [10.60.67.91] (ams-bclaise-89110.cisco.com [10.60.67.91]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t1OA4PnN005735; Tue, 24 Feb 2015 10:04:25 GMT
Message-ID: <54EC4CA9.8060600@cisco.com>
Date: Tue, 24 Feb 2015 11:04:25 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: gorry@erg.abdn.ac.uk
References: <20150218224325.29443.89305.idtracker@ietfa.amsl.com> <9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk>
In-Reply-To: <9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk>
Content-Type: multipart/alternative; boundary="------------020509080906010502040201"
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/-CY5EmunTVTZ8ba3lKUH5lbdN1M>
Cc: rs@netapp.com, aqm-chairs@ietf.org, mehmet.ersue@nsn.com, The IESG <iesg@ietf.org>, me <bclaise@cisco.com>, draft-ietf-aqm-recommendation.all@ietf.org, aqm@ietf.org, fred@cisco.com
Subject: Re: [aqm] Benoit Claise's Discuss on draft-ietf-aqm-recommendation-09: (with DISCUSS and COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 10:04:31 -0000

This is a multi-part message in MIME format.
--------------020509080906010502040201
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Hi Gorry,

Thanks for engaging.
> Benoit,
>
> We think we have resolved the remaining issues and would like to propose
> text that we think could address you DISCUSS:
>
> We think our point was that tuning should not be required
> *in*the*normal*case*, not
> that they should *never* require tuning (I'm not sure we have created
> anything that
> is 100% auto-tuning).
If it was a never, then the sentence would be

   3.  AQM algorithm deployment MUST NOT require tuning of initial or
configuration parameters.

> I'm OK with his phrasing in both cases, but would
> suggest the
> words "in common use cases" should be added:
>
>    3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
> configuration
I believe that the "in common use case" is redundant (and somehow 
confusing) with the SHOULD in your proposal.
SHOULD (RFC 2119):

    3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
        may exist valid reasons in particular circumstances to ignore a
        particular item, but the full implications must be understood and
        carefully weighed before choosing a different course.

However, I don't want to be picky on that point. I'll let your 
responsible AD decide.
My main point is covered. I'll clear that DISCUSS point.

> parameters in common use cases.
>
> 4.3 AQM algorithm deployment SHOULD NOT require tuning in common use cases.
I don't see this change in the v10.
There is an important word in here "deployment" as opposed to "deployed" 
in the current 4.3 section title (4.3. AQM algorithms deployed SHOULD 
NOT require operational tuning)
"Deployment" brings to the notion of initial deployment as opposed to 
"deployed".
This is the reason why I propose:

NEW:
4.3 AQM algorithm deployment SHOULD NOT require operational tuning

I hope you will include this change, but it's not DISCUSS-worth IMO.
Same remark as above regarding "AQM algorithm deployment"

Regards, Benoit
>
> Please let us know your thoughts,
>
> Fred & Gorry
>
>> Benoit Claise has entered the following ballot position for
>> draft-ietf-aqm-recommendation-09: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> Hopefully an easy DISCUSS.
>>    3.  The algorithms that the IETF recommends SHOULD NOT require
>>         operational (especially manual) configuration or tuning.
>>
>> This sentence above could be understood in different ways. For example,
>> that any configuration is wrong.
>> The ability to activate AQM is a good thing IMO.
>> The section 4.3 title is closer to what you intend to say: "AQM
>> algorithms deployed SHOULD NOT require operational tuning"
>> The issue is that you only define what you mean by "operational
>> configuration" in section 4.3
>>
>> Proposal:
>>
>> OLD:
>>    3.  The algorithms that the IETF recommends SHOULD NOT require
>>         operational (especially manual) configuration or tuning.
>>
>> NEW:
>>    3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
>> configuration parameters.
>>
>> OLD:
>> 4.3 AQM algorithms deployed SHOULD NOT require operational tuning
>>
>> NEW:
>> 4.3 AQM algorithm deployment SHOULD NOT require tuning
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> - RFC 2309 introduced the concept of "Active Queue Management" (AQM), a
>>     > class of technologies that, by signaling to common congestion-
>>     controlled transports such as TCP, manages the size of queues that
>>
>> Remove >
>>
>>
>> -
>>    Network devices SHOULD use an AQM algorithm to measure local local
>>     congestion
>>
>> local local
>>
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>>
>
> .
>


--------------020509080906010502040201
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Gorry, <br>
      <br>
      Thanks for engaging.<br>
    </div>
    <blockquote
      cite="mid:9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk"
      type="cite">
      <pre wrap="">
Benoit,

We think we have resolved the remaining issues and would like to propose
text that we think could address you DISCUSS:

We think our point was that tuning should not be required
*in*the*normal*case*, not
that they should *never* require tuning (I'm not sure we have created
anything that
is 100% auto-tuning). </pre>
    </blockquote>
    If it was a never, then the sentence would be
    <pre wrap="">  3.  AQM algorithm deployment MUST NOT require tuning of initial or
configuration parameters.
</pre>
    <blockquote
      cite="mid:9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk"
      type="cite">
      <pre wrap="">I'm OK with his phrasing in both cases, but would
suggest the
words "in common use cases" should be added:</pre>
    </blockquote>
    <blockquote
      cite="mid:9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk"
      type="cite">
      <pre wrap="">

  3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
configuration</pre>
    </blockquote>
    I believe that the "in common use case" is redundant (and somehow
    confusing) with the SHOULD in your proposal.<br>
    SHOULD (RFC 2119): <br>
    <blockquote>
      <pre>3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.</pre>
    </blockquote>
    However, I don't want to be picky on that point. I'll let your
    responsible AD decide.<br>
    My main point is covered. I'll clear that DISCUSS point.<br>
    <br>
    <blockquote
      cite="mid:9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk"
      type="cite">
      <pre wrap="">
parameters in common use cases.

4.3 AQM algorithm deployment SHOULD NOT require tuning in common use cases.</pre>
    </blockquote>
    I don't see this change in the v10.<br>
    There is an important word in here "deployment" as opposed to
    "deployed" in the current 4.3 section title (4.3. AQM algorithms
    deployed SHOULD NOT require operational tuning) <br>
    "Deployment" brings to the notion of initial deployment as opposed
    to "deployed".<br>
    This is the reason why I propose:<br>
    <pre wrap="">NEW:
4.3 AQM algorithm deployment SHOULD NOT require operational tuning</pre>
    I hope you will include this change, but it's not DISCUSS-worth IMO.<br>
    Same remark as above regarding "AQM algorithm deployment" <br>
    <br>
    Regards, Benoit<br>
    <blockquote
      cite="mid:9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk"
      type="cite">
      <pre wrap="">

Please let us know your thoughts,

Fred &amp; Gorry

</pre>
      <blockquote type="cite">
        <pre wrap="">Benoit Claise has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to <a class="moz-txt-link-freetext" href="http://www.ietf.org/iesg/statement/discuss-criteria.html">http://www.ietf.org/iesg/statement/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/">http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/</a>



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Hopefully an easy DISCUSS.
  3.  The algorithms that the IETF recommends SHOULD NOT require
       operational (especially manual) configuration or tuning.

This sentence above could be understood in different ways. For example,
that any configuration is wrong.
The ability to activate AQM is a good thing IMO.
The section 4.3 title is closer to what you intend to say: "AQM
algorithms deployed SHOULD NOT require operational tuning"
The issue is that you only define what you mean by "operational
configuration" in section 4.3

Proposal:

OLD:
  3.  The algorithms that the IETF recommends SHOULD NOT require
       operational (especially manual) configuration or tuning.

NEW:
  3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
configuration parameters.

OLD:
4.3 AQM algorithms deployed SHOULD NOT require operational tuning

NEW:
4.3 AQM algorithm deployment SHOULD NOT require tuning


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

- RFC 2309 introduced the concept of "Active Queue Management" (AQM), a
   &gt; class of technologies that, by signaling to common congestion-
   controlled transports such as TCP, manages the size of queues that

Remove &gt;


-
  Network devices SHOULD use an AQM algorithm to measure local local
   congestion

local local


_______________________________________________
aqm mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aqm@ietf.org">aqm@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/aqm">https://www.ietf.org/mailman/listinfo/aqm</a>

</pre>
      </blockquote>
      <pre wrap="">

.

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------020509080906010502040201--


From nobody Tue Feb 24 02:04:36 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 3D9421A0379; Tue, 24 Feb 2015 02:04:31 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 168231A6F34; Tue, 24 Feb 2015 02:04:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 xzkBvlPwuiuj; Tue, 24 Feb 2015 02:04:28 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0C7E1A0379; Tue, 24 Feb 2015 02:04:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10947; q=dns/txt; s=iport; t=1424772268; x=1425981868; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=7h/NEaZ5uOaEEMYs3MHh5MAzTFB7kPvLMGVFCBpc2Rg=; b=d8AhdvIiDclDPhEoAT6QUdFv4NYyRIIIt1L1K7BnM6mXKnl2oe66lp80 /936TPXWSEqo4F8Obgg5NBOTtRq/argAh0+F3Va2In1bNnLJ5w3ZKXyfq KDIplNlW2CYWOMtQ0chkCF8UqO4nTRZhzmAqWfJ0F+58x9QcSR0OaniKo g=;
X-IronPort-AV: E=Sophos;i="5.09,637,1418083200";  d="scan'208,217";a="354720204"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 24 Feb 2015 10:04:26 +0000
Received: from [10.60.67.91] (ams-bclaise-89110.cisco.com [10.60.67.91]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t1OA4PnN005735; Tue, 24 Feb 2015 10:04:25 GMT
Message-ID: <54EC4CA9.8060600@cisco.com>
Date: Tue, 24 Feb 2015 11:04:25 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: gorry@erg.abdn.ac.uk
References: <20150218224325.29443.89305.idtracker@ietfa.amsl.com> <9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk>
In-Reply-To: <9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk>
Content-Type: multipart/alternative; boundary="------------020509080906010502040201"
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/-CY5EmunTVTZ8ba3lKUH5lbdN1M>
Cc: rs@netapp.com, aqm-chairs@ietf.org, mehmet.ersue@nsn.com, The IESG <iesg@ietf.org>, me <bclaise@cisco.com>, draft-ietf-aqm-recommendation.all@ietf.org, aqm@ietf.org, fred@cisco.com
Subject: Re: [aqm] Benoit Claise's Discuss on draft-ietf-aqm-recommendation-09: (with DISCUSS and COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 10:04:31 -0000

This is a multi-part message in MIME format.
--------------020509080906010502040201
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Hi Gorry,

Thanks for engaging.
> Benoit,
>
> We think we have resolved the remaining issues and would like to propose
> text that we think could address you DISCUSS:
>
> We think our point was that tuning should not be required
> *in*the*normal*case*, not
> that they should *never* require tuning (I'm not sure we have created
> anything that
> is 100% auto-tuning).
If it was a never, then the sentence would be

   3.  AQM algorithm deployment MUST NOT require tuning of initial or
configuration parameters.

> I'm OK with his phrasing in both cases, but would
> suggest the
> words "in common use cases" should be added:
>
>    3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
> configuration
I believe that the "in common use case" is redundant (and somehow 
confusing) with the SHOULD in your proposal.
SHOULD (RFC 2119):

    3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
        may exist valid reasons in particular circumstances to ignore a
        particular item, but the full implications must be understood and
        carefully weighed before choosing a different course.

However, I don't want to be picky on that point. I'll let your 
responsible AD decide.
My main point is covered. I'll clear that DISCUSS point.

> parameters in common use cases.
>
> 4.3 AQM algorithm deployment SHOULD NOT require tuning in common use cases.
I don't see this change in the v10.
There is an important word in here "deployment" as opposed to "deployed" 
in the current 4.3 section title (4.3. AQM algorithms deployed SHOULD 
NOT require operational tuning)
"Deployment" brings to the notion of initial deployment as opposed to 
"deployed".
This is the reason why I propose:

NEW:
4.3 AQM algorithm deployment SHOULD NOT require operational tuning

I hope you will include this change, but it's not DISCUSS-worth IMO.
Same remark as above regarding "AQM algorithm deployment"

Regards, Benoit
>
> Please let us know your thoughts,
>
> Fred & Gorry
>
>> Benoit Claise has entered the following ballot position for
>> draft-ietf-aqm-recommendation-09: Discuss
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/
>>
>>
>>
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>>
>> Hopefully an easy DISCUSS.
>>    3.  The algorithms that the IETF recommends SHOULD NOT require
>>         operational (especially manual) configuration or tuning.
>>
>> This sentence above could be understood in different ways. For example,
>> that any configuration is wrong.
>> The ability to activate AQM is a good thing IMO.
>> The section 4.3 title is closer to what you intend to say: "AQM
>> algorithms deployed SHOULD NOT require operational tuning"
>> The issue is that you only define what you mean by "operational
>> configuration" in section 4.3
>>
>> Proposal:
>>
>> OLD:
>>    3.  The algorithms that the IETF recommends SHOULD NOT require
>>         operational (especially manual) configuration or tuning.
>>
>> NEW:
>>    3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
>> configuration parameters.
>>
>> OLD:
>> 4.3 AQM algorithms deployed SHOULD NOT require operational tuning
>>
>> NEW:
>> 4.3 AQM algorithm deployment SHOULD NOT require tuning
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> - RFC 2309 introduced the concept of "Active Queue Management" (AQM), a
>>     > class of technologies that, by signaling to common congestion-
>>     controlled transports such as TCP, manages the size of queues that
>>
>> Remove >
>>
>>
>> -
>>    Network devices SHOULD use an AQM algorithm to measure local local
>>     congestion
>>
>> local local
>>
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>>
>
> .
>


--------------020509080906010502040201
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Gorry, <br>
      <br>
      Thanks for engaging.<br>
    </div>
    <blockquote
      cite="mid:9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk"
      type="cite">
      <pre wrap="">
Benoit,

We think we have resolved the remaining issues and would like to propose
text that we think could address you DISCUSS:

We think our point was that tuning should not be required
*in*the*normal*case*, not
that they should *never* require tuning (I'm not sure we have created
anything that
is 100% auto-tuning). </pre>
    </blockquote>
    If it was a never, then the sentence would be
    <pre wrap="">  3.  AQM algorithm deployment MUST NOT require tuning of initial or
configuration parameters.
</pre>
    <blockquote
      cite="mid:9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk"
      type="cite">
      <pre wrap="">I'm OK with his phrasing in both cases, but would
suggest the
words "in common use cases" should be added:</pre>
    </blockquote>
    <blockquote
      cite="mid:9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk"
      type="cite">
      <pre wrap="">

  3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
configuration</pre>
    </blockquote>
    I believe that the "in common use case" is redundant (and somehow
    confusing) with the SHOULD in your proposal.<br>
    SHOULD (RFC 2119): <br>
    <blockquote>
      <pre>3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.</pre>
    </blockquote>
    However, I don't want to be picky on that point. I'll let your
    responsible AD decide.<br>
    My main point is covered. I'll clear that DISCUSS point.<br>
    <br>
    <blockquote
      cite="mid:9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk"
      type="cite">
      <pre wrap="">
parameters in common use cases.

4.3 AQM algorithm deployment SHOULD NOT require tuning in common use cases.</pre>
    </blockquote>
    I don't see this change in the v10.<br>
    There is an important word in here "deployment" as opposed to
    "deployed" in the current 4.3 section title (4.3. AQM algorithms
    deployed SHOULD NOT require operational tuning) <br>
    "Deployment" brings to the notion of initial deployment as opposed
    to "deployed".<br>
    This is the reason why I propose:<br>
    <pre wrap="">NEW:
4.3 AQM algorithm deployment SHOULD NOT require operational tuning</pre>
    I hope you will include this change, but it's not DISCUSS-worth IMO.<br>
    Same remark as above regarding "AQM algorithm deployment" <br>
    <br>
    Regards, Benoit<br>
    <blockquote
      cite="mid:9e5393f59950a047bdcc4cc5dde50259.squirrel@erg.abdn.ac.uk"
      type="cite">
      <pre wrap="">

Please let us know your thoughts,

Fred &amp; Gorry

</pre>
      <blockquote type="cite">
        <pre wrap="">Benoit Claise has entered the following ballot position for
draft-ietf-aqm-recommendation-09: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to <a class="moz-txt-link-freetext" href="http://www.ietf.org/iesg/statement/discuss-criteria.html">http://www.ietf.org/iesg/statement/discuss-criteria.html</a>
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/">http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/</a>



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

Hopefully an easy DISCUSS.
  3.  The algorithms that the IETF recommends SHOULD NOT require
       operational (especially manual) configuration or tuning.

This sentence above could be understood in different ways. For example,
that any configuration is wrong.
The ability to activate AQM is a good thing IMO.
The section 4.3 title is closer to what you intend to say: "AQM
algorithms deployed SHOULD NOT require operational tuning"
The issue is that you only define what you mean by "operational
configuration" in section 4.3

Proposal:

OLD:
  3.  The algorithms that the IETF recommends SHOULD NOT require
       operational (especially manual) configuration or tuning.

NEW:
  3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
configuration parameters.

OLD:
4.3 AQM algorithms deployed SHOULD NOT require operational tuning

NEW:
4.3 AQM algorithm deployment SHOULD NOT require tuning


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

- RFC 2309 introduced the concept of "Active Queue Management" (AQM), a
   &gt; class of technologies that, by signaling to common congestion-
   controlled transports such as TCP, manages the size of queues that

Remove &gt;


-
  Network devices SHOULD use an AQM algorithm to measure local local
   congestion

local local


_______________________________________________
aqm mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aqm@ietf.org">aqm@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/aqm">https://www.ietf.org/mailman/listinfo/aqm</a>

</pre>
      </blockquote>
      <pre wrap="">

--------------020509080906010502040201--

From nobody Tue Feb 24 02:05:13 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5F1F1A0379; Tue, 24 Feb 2015 02:05:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 S2_Xs2PI8np6; Tue, 24 Feb 2015 02:05:06 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 52FF31A6F34; Tue, 24 Feb 2015 02:05:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150224100506.30747.44853.idtracker@ietfa.amsl.com>
Date: Tue, 24 Feb 2015 02:05:06 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/d0WKoSYNibXO7-OXglIqwQvFmjU>
Cc: mehmet.ersue@nsn.com, rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Benoit Claise's No Objection on draft-ietf-aqm-recommendation-10: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 10:05:10 -0000

Benoit Claise has entered the following ballot position for
draft-ietf-aqm-recommendation-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi Gorry,

Thanks for engaging.
>
> Benoit,
>
> We think we have resolved the remaining issues and would like to
propose
> text that we think could address you DISCUSS:
>
> We think our point was that tuning should not be required
> *in*the*normal*case*, not
> that they should *never* require tuning (I'm not sure we have created
> anything that
> is 100% auto-tuning). 
If it was a never, then the sentence would be

  3.  AQM algorithm deployment MUST NOT require tuning of initial or
configuration parameters.

> I'm OK with his phrasing in both cases, but would
> suggest the
> words "in common use cases" should be added:
>
>
>   3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
> configuration
I believe that the "in common use case" is redundant (and somehow
confusing) with the SHOULD in your proposal.
SHOULD (RFC 2119):

    3. SHOULD   This word, or the adjective "RECOMMENDED", mean that
there
       may exist valid reasons in particular circumstances to ignore a
       particular item, but the full implications must be understood and
       carefully weighed before choosing a different course.

However, I don't want to be picky on that point. I'll let your
responsible AD decide.
My main point is covered. I'll clear that DISCUSS point.
>
> parameters in common use cases.
>
> 4.3 AQM algorithm deployment SHOULD NOT require tuning in common use
cases.
I don't see this change in the v10.
There is an important word in here: "deployment" as opposed to "deployed"
in the current 4.3 section title (4.3. AQM algorithms deployed SHOULD NOT
require operational tuning)
"Deployment" brings to the notion of initial deployment as opposed to
"deployed".
This is the reason why I propose:

NEW:
4.3 AQM algorithm deployment SHOULD NOT require operational tuning

I hope you will include this change, but it's not DISCUSS-worth IMO.
Same remark as above regarding "AQM algorithm deployment"

Regards, Benoit



From nobody Tue Feb 24 02:05:14 2015
Return-Path: <bclaise@cisco.com>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id E0F701A8763; Tue, 24 Feb 2015 02:05:10 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5F1F1A0379; Tue, 24 Feb 2015 02:05:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 S2_Xs2PI8np6; Tue, 24 Feb 2015 02:05:06 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 52FF31A6F34; Tue, 24 Feb 2015 02:05:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Benoit Claise" <bclaise@cisco.com>
To: "The IESG" <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150224100506.30747.44853.idtracker@ietfa.amsl.com>
Date: Tue, 24 Feb 2015 02:05:06 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/d0WKoSYNibXO7-OXglIqwQvFmjU>
Cc: mehmet.ersue@nsn.com, rs@netapp.com, aqm-chairs@ietf.org, aqm@ietf.org, draft-ietf-aqm-recommendation.all@ietf.org
Subject: [aqm] Benoit Claise's No Objection on draft-ietf-aqm-recommendation-10: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 10:05:11 -0000

Benoit Claise has entered the following ballot position for
draft-ietf-aqm-recommendation-10: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
http://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi Gorry,

Thanks for engaging.
>
> Benoit,
>
> We think we have resolved the remaining issues and would like to
propose
> text that we think could address you DISCUSS:
>
> We think our point was that tuning should not be required
> *in*the*normal*case*, not
> that they should *never* require tuning (I'm not sure we have created
> anything that
> is 100% auto-tuning). 
If it was a never, then the sentence would be

  3.  AQM algorithm deployment MUST NOT require tuning of initial or
configuration parameters.

> I'm OK with his phrasing in both cases, but would
> suggest the
> words "in common use cases" should be added:
>
>
>   3.  AQM algorithm deployment SHOULD NOT require tuning of initial or
> configuration
I believe that the "in common use case" is redundant (and somehow
confusing) with the SHOULD in your proposal.
SHOULD (RFC 2119):

    3. SHOULD   This word, or the adjective "RECOMMENDED", mean that
there
       may exist valid reasons in particular circumstances to ignore a
       particular item, but the full implications must be understood and
       carefully weighed before choosing a different course.

However, I don't want to be picky on that point. I'll let your
responsible AD decide.
My main point is covered. I'll clear that DISCUSS point.
>
> parameters in common use cases.
>
> 4.3 AQM algorithm deployment SHOULD NOT require tuning in common use
cases.
I don't see this change in the v10.
There is an important word in here: "deployment" as opposed to "deployed"
in the current 4.3 section title (4.3. AQM algorithms deployed SHOULD NOT
require operational tuning)
"Deployment" brings to the notion of initial deployment as opposed to
"deployed".
This is the reason why I propose:

NEW:
4.3 AQM algorithm deployment SHOULD NOT require operational tuning

I hope you will include this change, but it's not DISCUSS-worth IMO.
Same remark as above regarding "AQM algorithm deployment"

Regards, Benoit



From nobody Wed Feb 25 02:00:56 2015
Return-Path: <rs@netapp.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89E9A1A872B for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 02:00:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level: 
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 FoIdIObPq__6 for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 02:00:53 -0800 (PST)
Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C19361A870D for <aqm@ietf.org>; Wed, 25 Feb 2015 02:00:30 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.09,643,1418112000"; d="scan'208";a="26559486"
Received: from hioexcmbx02-prd.hq.netapp.com ([10.122.105.35]) by mx141-out.netapp.com with ESMTP; 25 Feb 2015 01:55:32 -0800
Received: from HIOEXCMBX05-PRD.hq.netapp.com (10.122.105.38) by hioexcmbx02-prd.hq.netapp.com (10.122.105.35) with Microsoft SMTP Server (TLS) id 15.0.995.29; Wed, 25 Feb 2015 01:55:29 -0800
Received: from HIOEXCMBX05-PRD.hq.netapp.com ([::1]) by hioexcmbx05-prd.hq.netapp.com ([fe80::c4b3:e711:88fe:6ce%21]) with mapi id 15.00.0995.031; Wed, 25 Feb 2015 01:55:29 -0800
From: "Scheffenegger, Richard" <rs@netapp.com>
To: "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] I-D Action: draft-ietf-aqm-ecn-benefits-00.txt
Thread-Index: AQHP720lSp5KkDElEkGOkiSU5MFZZZ0B4h+Q
Date: Wed, 25 Feb 2015 09:55:29 +0000
Message-ID: <384483c0c4fc474c82dac550ac3ef751@hioexcmbx05-prd.hq.netapp.com>
References: <20141024092948.9876.61739.idtracker@ietfa.amsl.com>
In-Reply-To: <20141024092948.9876.61739.idtracker@ietfa.amsl.com>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.120.60.36]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/Pnnb9u9CXhhuWJvGJP3wU9MbS-4>
Cc: "'gorry@erg.abdn.ac.uk'" <gorry@erg.abdn.ac.uk>, "steve@wreck.net" <steve@wreck.net>, "'mirja.kuehlewind@tik.ee.ethz.ch'" <mirja.kuehlewind@tik.ee.ethz.ch>, "Michael Welzl \(michawe@ifi.uio.no\)" <michawe@ifi.uio.no>, "'Andrew McGregor' \(andrewmcgr@gmail.com\)" <andrewmcgr@gmail.com>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-ecn-benefits-00.txt
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 10:00:54 -0000

Hi,


As discussed during IETF91, we are aiming to get a WGLC on this document.

Please review this rather short draft - there has been some feedback in Hon=
olulu, which should have been addressed in the adoped version already.

Please review this document in preparation for the Dallas meeting, and prov=
ide feedback!

Thanks,
  Richard (AQM Co-Chair)



> -----Original Message-----
> From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of internet-
> drafts@ietf.org
> Sent: Freitag, 24. Oktober 2014 11:30
> To: i-d-announce@ietf.org
> Cc: aqm@ietf.org
> Subject: [aqm] I-D Action: draft-ietf-aqm-ecn-benefits-00.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Active Queue Management and Packet
> Scheduling Working Group of the IETF.
>=20
>         Title           : The Benefits and Pitfalls of using Explicit
> Congestion Notification (ECN)
>         Authors         : Michael Welzl
>                           Godred Fairhurst
> 	Filename        : draft-ietf-aqm-ecn-benefits-00.txt
> 	Pages           : 11
> 	Date            : 2014-10-24
>=20
> Abstract:
>    This document describes the potential benefits and pitfalls when
>    applications enable Explicit Congestion Notification (ECN).  It
>    outlines the principal gains in terms of increased throughput,
>    reduced delay and other benefits when ECN is used over network paths
>    that include equipment that supports ECN-marking.  It also lists
>    potential problems that might occur when ECN is used.  The document
>    does not propose new algorithms that may be able to use ECN or
>    describe the details of implementation of ECN in endpoint devices,
>    routers and other network devices.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-aqm-ecn-benefits/
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-aqm-ecn-benefits-00
>=20
>=20
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm


From nobody Wed Feb 25 09:13:44 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D23B81A1AA2; Wed, 25 Feb 2015 09:13:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 NcaK9sMe-ZDC; Wed, 25 Feb 2015 09:13:39 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 989FA1A01AA; Wed, 25 Feb 2015 09:13:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150225171339.18661.12825.idtracker@ietfa.amsl.com>
Date: Wed, 25 Feb 2015 09:13:39 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/3MWif-xHAwSPGpqGc7FuVgFf1_M>
Cc: aqm@ietf.org
Subject: [aqm] I-D Action: draft-ietf-aqm-recommendation-11.txt
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 17:13:42 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Active Queue Management and Packet Scheduling Working Group of the IETF.

        Title           : IETF Recommendations Regarding Active Queue Management
        Authors         : Fred Baker
                          Godred Fairhurst
	Filename        : draft-ietf-aqm-recommendation-11.txt
	Pages           : 30
	Date            : 2015-02-25

Abstract:
   This memo presents recommendations to the Internet community
   concerning measures to improve and preserve Internet performance.  It
   presents a strong recommendation for testing, standardization, and
   widespread deployment of active queue management (AQM) in network
   devices, to improve the performance of today's Internet.  It also
   urges a concerted effort of research, measurement, and ultimate
   deployment of AQM mechanisms to protect the Internet from flows that
   are not sufficiently responsive to congestion notification.

   The note replaces the recommendations of RFC 2309 based on fifteen
   years of experience and new research.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-aqm-recommendation-11

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-recommendation-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Feb 25 09:13:46 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13A521A1B83; Wed, 25 Feb 2015 09:13:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 FllWDi-t6MpO; Wed, 25 Feb 2015 09:13:40 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C769E1A1B34; Wed, 25 Feb 2015 09:13:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>, <mls.ietf@gmail.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150225171339.18661.90078.idtracker@ietfa.amsl.com>
Date: Wed, 25 Feb 2015 09:13:39 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/fX4K6L8fuPx_SORBZnZ96LKeZTE>
Subject: [aqm] New Version Notification - draft-ietf-aqm-recommendation-11.txt
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 17:13:42 -0000

A new version (-11) has been submitted for draft-ietf-aqm-recommendation:
http://www.ietf.org/internet-drafts/draft-ietf-aqm-recommendation-11.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-recommendation-11

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.


From nobody Wed Feb 25 09:13:48 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: expand-draft-ietf-aqm-recommendation.all@virtual.ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: by ietfa.amsl.com (Postfix, from userid 65534) id 320461A1AFB; Wed, 25 Feb 2015 09:13:42 -0800 (PST)
X-Original-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Delivered-To: xfilter-draft-ietf-aqm-recommendation.all@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13A521A1B83; Wed, 25 Feb 2015 09:13:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 FllWDi-t6MpO; Wed, 25 Feb 2015 09:13:40 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C769E1A1B34; Wed, 25 Feb 2015 09:13:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <rs@netapp.com>, <draft-ietf-aqm-recommendation.all@ietf.org>, <aqm@ietf.org>, <aqm-chairs@ietf.org>, <mls.ietf@gmail.com>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150225171339.18661.90078.idtracker@ietfa.amsl.com>
Date: Wed, 25 Feb 2015 09:13:39 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/fX4K6L8fuPx_SORBZnZ96LKeZTE>
Subject: [aqm] New Version Notification - draft-ietf-aqm-recommendation-11.txt
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 17:13:42 -0000

A new version (-11) has been submitted for draft-ietf-aqm-recommendation:
http://www.ietf.org/internet-drafts/draft-ietf-aqm-recommendation-11.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-recommendation-11

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.


From prvs=491389fee=rpdoyle@live.unc.edu  Wed Feb 25 09:53:41 2015
Return-Path: <prvs=491389fee=rpdoyle@live.unc.edu>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 562BC1A0015 for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 09:53:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.791
X-Spam-Level: 
X-Spam-Status: No, score=0.791 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4GaTCz8FaaHP for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 09:53:36 -0800 (PST)
Received: from mxip11i.isis.unc.edu (mxip11i.isis.unc.edu [152.2.0.32]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA7931A035F for <aqm@ietf.org>; Wed, 25 Feb 2015 09:53:32 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2CmBQB+Ce5U/8BPAphbgj9DAYYFrxFLjSyBKYc3OBQBAQEBAQEBfIQGIoEFAYEfNYd4ARStNoN/AY0zkk6EfyCTH4EUBYogLpUojGkjhAyDFAEBAQ
X-IPAS-Result: A2CmBQB+Ce5U/8BPAphbgj9DAYYFrxFLjSyBKYc3OBQBAQEBAQEBfIQGIoEFAYEfNYd4ARStNoN/AY0zkk6EfyCTH4EUBYogLpUojGkjhAyDFAEBAQ
X-IronPort-AV: E=Sophos; i="5.09,646,1418101200"; d="scan'208,217"; a="39046749"
Received: from its-msxht7f.ad.unc.edu ([152.2.79.192]) by mxip11o.isis.unc.edu with ESMTP/TLS/AES128-SHA; 25 Feb 2015 12:53:31 -0500
Received: from mail.hotmail.com (172.22.44.33) by smtp.unc.edu (152.2.79.192) with Microsoft SMTP Server id 14.3.224.2; Wed, 25 Feb 2015 12:53:31 -0500
Received: from BAY176-W35 ([157.56.23.7]) by COL004-WSS1S2.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 25 Feb 2015 09:53:30 -0800
X-TMN: [CpXa0gnhj0/y09tWLGpQnd/V9qro5O5H]
Message-ID: <BAY176-W35105790F5BC047AA12309A5170@phx.gbl>
Content-Type: multipart/alternative; boundary="_fccfeaf6-2d6e-45e5-91a2-e821c3cc0559_"
From: Ryan Doyle <rpdoyle@live.unc.edu>
To: "aqm@ietf.org" <aqm@ietf.org>
Date: Wed, 25 Feb 2015 12:53:29 -0500
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 25 Feb 2015 17:53:30.0190 (UTC) FILETIME=[F6E8C6E0:01D05123]
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/QAAsYGwD0B3mPaDSkL0fOe_KjP8>
X-Mailman-Approved-At: Wed, 25 Feb 2015 09:59:40 -0800
Subject: [aqm] Gathering Queue Length Statistics
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 17:55:29 -0000

--_fccfeaf6-2d6e-45e5-91a2-e821c3cc0559_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello=2C

I am a senior undergraduate student at the University of North Carolina at =
Chapel Hill and am studying the effectiveness of AQMs. I have set up a lab =
network and plan on running different sets of experiments with different AQ=
Ms. My router machines are running Linux kernel version 3.16.0.

I am using the fq_codel=2C codel=2C and pie qdiscs for my research and am w=
ondering if there is a way to collect statistics regarding the average queu=
e length since a qdisc was enabled? I have looked at tc's "-s" flag for sta=
tistics=2C but they show nothing about queue length and I have been unable =
to find anything else that might help me get queue length statistics.

Best=2C
Ryan Doyle 		 	   		  =

--_fccfeaf6-2d6e-45e5-91a2-e821c3cc0559_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>Hello=2C<br><br>I am a senior un=
dergraduate student at the University of North Carolina at Chapel Hill and =
am studying the effectiveness of AQMs. I have set up a lab network and plan=
 on running different sets of experiments with different AQMs. My router ma=
chines are running Linux kernel version 3.16.0.<br><br>I am using the fq_co=
del=2C codel=2C and pie qdiscs for my research and am wondering if there is=
 a way to collect statistics regarding the average queue length since a qdi=
sc was enabled? I have looked at tc's "-s" flag for statistics=2C but they =
show nothing about queue length and I have been unable to find anything els=
e that might help me get queue length statistics.<br><br>Best=2C<br>Ryan Do=
yle 		 	   		  </div></body>
</html>=

--_fccfeaf6-2d6e-45e5-91a2-e821c3cc0559_--


From nobody Wed Feb 25 10:20:46 2015
Return-Path: <fred@cisco.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1154C1A079A for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 10:20:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.51
X-Spam-Level: 
X-Spam-Status: No, score=-114.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 RIeuQ4SzOK0g for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 10:20:43 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CE691A0470 for <aqm@ietf.org>; Wed, 25 Feb 2015 10:20:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3706; q=dns/txt; s=iport; t=1424888444; x=1426098044; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=UQwCXXEaRIcZd66Ue5GYtpzBW9ogFc08TMo/XhxhgaQ=; b=Ci0mS4gTxKxIIvJPhdFsJV3fpbTUJHNygAPcZ4iNJAcE6oz6Ltd8dRGw uUBp+88Xq+VMI3mJ225txdg+o1/o/IgSCgzoO5Q0Y352Tp5t23clL55Ra aaI5UEESy/2YOnUDE8a2+Rr+ITBxzcS6nD4qk7/L94bAAHkq5h5hiJoL3 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ByBQAmEu5U/5tdJa1bDoIxQ4EsBMkPAoEoQwEBAQEBAXyEDwEBAQSBCQIBCAQKAwQBAQskMh0IAgQBEgiIEwMR1igBAQEBAQEBAQEBAQEBAQEBAQEBAQEXixOCRIF5OIMXgRQFiiCFPJ0DIoMxPW+BRH8BAQE
X-IronPort-AV: E=Sophos;i="5.09,646,1418083200";  d="scan'208,217";a="126890187"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP; 25 Feb 2015 18:20:34 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t1PIKXvA029450 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 25 Feb 2015 18:20:33 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.149]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0195.001; Wed, 25 Feb 2015 12:20:33 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Ryan Doyle <rpdoyle@live.unc.edu>, "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] Gathering Queue Length Statistics
Thread-Index: AQHQUSTW7yjx4Dm+TkiQ7sDnsvQovZ0BqxdA
Date: Wed, 25 Feb 2015 18:20:33 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B0612FC9A@xmb-rcd-x09.cisco.com>
References: <BAY176-W35105790F5BC047AA12309A5170@phx.gbl>
In-Reply-To: <BAY176-W35105790F5BC047AA12309A5170@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.24.214.118]
Content-Type: multipart/alternative; boundary="_000_8C48B86A895913448548E6D15DA7553B0612FC9Axmbrcdx09ciscoc_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/8dMQjVZ0nNprzHF5D6PL7q5LR0M>
Subject: Re: [aqm] Gathering Queue Length Statistics
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 18:20:45 -0000

--_000_8C48B86A895913448548E6D15DA7553B0612FC9Axmbrcdx09ciscoc_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'd suggest looking at netperf. It doesn't measure the queue directly; it m=
easures the latency that queue occupancy induces. However, at least in comm=
ercial equipment, this thing we call "the queue" may not be all in the same=
 place...

________________________________
From: aqm [aqm-bounces@ietf.org] on behalf of Ryan Doyle [rpdoyle@live.unc.=
edu]
Sent: Wednesday, February 25, 2015 9:53 AM
To: aqm@ietf.org
Subject: [aqm] Gathering Queue Length Statistics

Hello,

I am a senior undergraduate student at the University of North Carolina at =
Chapel Hill and am studying the effectiveness of AQMs. I have set up a lab =
network and plan on running different sets of experiments with different AQ=
Ms. My router machines are running Linux kernel version 3.16.0.

I am using the fq_codel, codel, and pie qdiscs for my research and am wonde=
ring if there is a way to collect statistics regarding the average queue le=
ngth since a qdisc was enabled? I have looked at tc's "-s" flag for statist=
ics, but they show nothing about queue length and I have been unable to fin=
d anything else that might help me get queue length statistics.

Best,
Ryan Doyle

--_000_8C48B86A895913448548E6D15DA7553B0612FC9Axmbrcdx09ciscoc_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style>=0A=
<!--=0A=
.hmmessage p=0A=
	{margin:0px;=0A=
	padding:0px}=0A=
body.hmmessage=0A=
	{font-size:12pt;=0A=
	font-family:Calibri}=0A=
-->=0A=
</style><style type=3D"text/css" id=3D"owaParaStyle"></style><style type=3D=
"text/css"></style><style type=3D"text/css"></style>
</head>
<body class=3D"hmmessage" fpstyle=3D"1" ocsi=3D"0">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">I'd suggest looking at netperf. It doesn't measure the queue directl=
y; it measures the latency that queue occupancy induces. However, at least =
in commercial equipment, this thing
 we call &quot;the queue&quot; may not be all in the same place...
<div><br>
<div style=3D"font-family: Times New Roman; color: #000000; font-size: 16px=
">
<hr tabindex=3D"-1">
<div id=3D"divRpF188474" style=3D"direction: ltr;"><font face=3D"Tahoma" si=
ze=3D"2" color=3D"#000000"><b>From:</b> aqm [aqm-bounces@ietf.org] on behal=
f of Ryan Doyle [rpdoyle@live.unc.edu]<br>
<b>Sent:</b> Wednesday, February 25, 2015 9:53 AM<br>
<b>To:</b> aqm@ietf.org<br>
<b>Subject:</b> [aqm] Gathering Queue Length Statistics<br>
</font><br>
</div>
<div></div>
<div>
<div dir=3D"ltr">Hello,<br>
<br>
I am a senior undergraduate student at the University of North Carolina at =
Chapel Hill and am studying the effectiveness of AQMs. I have set up a lab =
network and plan on running different sets of experiments with different AQ=
Ms. My router machines are running
 Linux kernel version 3.16.0.<br>
<br>
I am using the fq_codel, codel, and pie qdiscs for my research and am wonde=
ring if there is a way to collect statistics regarding the average queue le=
ngth since a qdisc was enabled? I have looked at tc's &quot;-s&quot; flag f=
or statistics, but they show nothing about
 queue length and I have been unable to find anything else that might help =
me get queue length statistics.<br>
<br>
Best,<br>
Ryan Doyle </div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_8C48B86A895913448548E6D15DA7553B0612FC9Axmbrcdx09ciscoc_--


From nobody Wed Feb 25 10:24:53 2015
Return-Path: <dave.taht@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A7FE1A037D for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 10:24:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 MMGVD2qodKpZ for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 10:24:50 -0800 (PST)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE8291A1AA1 for <aqm@ietf.org>; Wed, 25 Feb 2015 10:24:45 -0800 (PST)
Received: by mail-oi0-f50.google.com with SMTP id v1so4864025oia.9 for <aqm@ietf.org>; Wed, 25 Feb 2015 10:24:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=y4honxBn3fcSQpS/CSKrGkAxHn5njeU58DGryL/naA4=; b=Xov00oEO8bbbHePMYXdpggwprgvekrozl8OdoWFldkiNj+yKVVQ8ciV5XwvynHmoQE v3PgsfA2FEBWKtkJ7ZcBNHyDBmkYzm8857k1Dq3uyCrijJw09lrBd1rE8NBfcGMTBphG iGqyLYossoxvGdEGcSteixOFjzpt0FIRMwka7EILXKi9uPgASXxUmvL6qayFT6mRqjec Tejolh9sRTh2YQFRIpspQFFwJM4H2tAhJQdLk8VhgDhGx8u1gxCqoxCZhRxRLbVyrS9l pDhgMIQbrv+YwiSXUcftjEvKZsx95DUdI0PBH68cehFVHZc0IzjaY2iiq5t3Q+PRFQAo WhzA==
MIME-Version: 1.0
X-Received: by 10.60.57.9 with SMTP id e9mr3257126oeq.24.1424888685290; Wed, 25 Feb 2015 10:24:45 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Wed, 25 Feb 2015 10:24:45 -0800 (PST)
In-Reply-To: <BAY176-W35105790F5BC047AA12309A5170@phx.gbl>
References: <BAY176-W35105790F5BC047AA12309A5170@phx.gbl>
Date: Wed, 25 Feb 2015 10:24:45 -0800
Message-ID: <CAA93jw5dPhLmamcSHxD92b50XxmkkZNy28SWMkOSRFzBY3keBA@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Ryan Doyle <rpdoyle@live.unc.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/JKQKZxDHbG_Ps7k6PzFI6BUlnWY>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] Gathering Queue Length Statistics
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 18:24:52 -0000

On Wed, Feb 25, 2015 at 9:53 AM, Ryan Doyle <rpdoyle@live.unc.edu> wrote:
> Hello,
>
> I am a senior undergraduate student at the University of North Carolina a=
t
> Chapel Hill and am studying the effectiveness of AQMs. I have set up a la=
b
> network and plan on running different sets of experiments with different
> AQMs. My router machines are running Linux kernel version 3.16.0.
>
> I am using the fq_codel, codel, and pie qdiscs for my research and am
> wondering if there is a way to collect statistics regarding the average
> queue length since a qdisc was enabled? I have looked at tc's "-s" flag f=
or
> statistics, but they show nothing about queue length and I have been unab=
le
> to find anything else that might help me get queue length statistics.

Oh, god. I am getting incredibly sensitive about average queue length,
and I realize that that is not what you meant. But since not enough
people have seemingly read this or any of the related materials, here
it is again.

http://www.pollere.net/Pdfdocs/QrantJul06.pdf

And I of course always recommend van=C2=B4s talk on the fountain model for
thinking about closed loop servo systems.

http://www.bufferbloat.net/projects/cerowrt/wiki/Bloat-videos

In the bufferbloat project...

We have developed many tools that drive aqms hard, see netperf-wrapper
on github for that, which measures e2e delay without requiring any
tools on the routers inbetween. e2e delay in my mind is way more
important than average queue length. And you can derive the queue
length(s) from tcp timestamps in those netperf-wrapper tests, from
additional packet captures, if you must.

If you absolutely MUST derive average queue length from the box, you
can poll the interface frequently with tc -s qdisc show as well as
with ifconfig- and parse out the number of packets and the number of
bytes. But you can do MUCH more valid statistical analysis than that,
with that sort of data set - and if you poll too frequently you will
heisenbug your tests, as those data collection calls take locks that
interfere with the path. and we have all sorts of advice about traps
for the unwary here:

http://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmark=
ing_Codel_and_FQ_Codel


Please use things like CDFs to see the range of delays, rather than
averages. It is what happens at above 90% of the range that makes
bufferbloat maddening to ordinary users.

I am summarily rejecting any papers that I review that report average
queue length as if it meant anything. And for a few other reasons. You
have been warned. I really lost my temper after the last paper I
reviewed last weekend and the resulting flamage is all over the bloat
list and codel lists, and starts here:

https://lists.bufferbloat.net/pipermail/codel/2015-February/000872.html


> Best,
> Ryan Doyle
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>



--=20
Dave T=C3=A4ht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb


From nobody Wed Feb 25 11:17:49 2015
Return-Path: <dhavey@yahoo.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFAB21A7022 for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 11:17:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.71
X-Spam-Level: 
X-Spam-Status: No, score=-0.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_ILLEGAL_IP=1.3, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 Mfmv1Jnl3Bnc for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 11:17:40 -0800 (PST)
Received: from nm45-vm1.bullet.mail.bf1.yahoo.com (nm45-vm1.bullet.mail.bf1.yahoo.com [216.109.115.60]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 219191A8758 for <aqm@ietf.org>; Wed, 25 Feb 2015 11:16:50 -0800 (PST)
Received: from [66.196.81.171] by nm45.bullet.mail.bf1.yahoo.com with NNFMP; 25 Feb 2015 19:16:49 -0000
Received: from [98.139.212.226] by tm17.bullet.mail.bf1.yahoo.com with NNFMP;  25 Feb 2015 19:16:49 -0000
Received: from [127.0.0.1] by omp1035.mail.bf1.yahoo.com with NNFMP; 25 Feb 2015 19:16:40 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 886713.22029.bm@omp1035.mail.bf1.yahoo.com
Received: (qmail 39896 invoked by uid 60001); 25 Feb 2015 19:16:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1424891800; bh=KQvrhxTUbnIIg1kXdVuFRG2i8Aqf+s7E7MGR2z8EZUI=; h=Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=JCu/iqMQztjE2YDWbYWZ2ve7xteZvRKiSBDShLpI6lqjqpw8u6I/cf09wULFDl905gpVo5AIuAPRaC6nlMUuDatZ9Y2oPJ/sIKf5QVz20rH1g1QvazBG9WnOWJvdkWzn6N5i5MlDqH8EB8raJ4khnsldaSAjSi6L93nWZ5XdUW0=
X-YMail-OSG: Uua5NhwVM1mc2hknbvrG3Pz_q.W_3HSt.vH4xgDWFn9YBB8 Q1bSkv.kbFEOauxDDkDp9Sxa8brjP1nDJVytFo_8r2RcL2MOBSbQZr1rM75H aBvAy8XAyT8vox_d32tBhxrSxLglHtA2JOUuBjpUzBqGEsdrSt2YVyfZYeGA MGU9U3bkH58kePcgwyoJXLff4PMq5_vZ2d0VqsGw8NYzbzcnpB4.Nf6UNodp k0422RWaZxEo5XgvadFxc4vEDhxTfuIr.Nk5ZZsrpbv8KPUDncN2qF9jyloG sSuW3cU2TIcQQRVU5dIH.Q5MYewsaJ5HjfeUN7OcbdOjTerSFdprRc.c0Oiy dyCXedbHeLiQ_TmFjS8jdIiC2MDt_erIFA6g8eApl.oyBwvDQj7_Fvousd0a p53oKqkcel6g1J6hOvEq9OY.6YNCS5dMdGGHEYrLmfF1tuGX0uCFbTn.yna6 mWr09RG.zRVGd3DlPhVf9bn_YX4Ifmz.Ra0qKOpoT6v7nS_rG7RFqQwdaLvn 3Dk9Af3ooRkrfffYFhq6zODsXD5CsoXdppbRRPI4JTRKHfsC0XgxxwpPBeB1 rJs500cSHLhcRCuUnZuXC9aSVQPJb5Jjsv_cv3To03.cbnxOv5KwTw_Y0ri2 YMb389kPA3H5uxz70Y4KLKkrwcGipkDd.34OcSe1ZEGX9BWYxUhJjCf28xl5 MW9B4qmXOcsz8THdIyWEhhStUMC7RZGtBrR.wGEa6d4mSeej8lDLmMWUEQ9T Q9uSISdGF1W4Rr_kA.xQwFVfpb5lXjZ2G2tJ6HzYQhrzUXImtZDqfoWTSHiH jdHo1KPaGC9Qru6Cv.uCKB39mkf8tiI4IW83lenDKt0SvLqq.3tE.uWh5qZY K5M2c2xbW9GRQQ8vyP8opP21AC.vzwY.dk92rLamBtBsf
Received: from [238.183.110.161] by web141601.mail.bf1.yahoo.com via HTTP; Wed, 25 Feb 2015 11:16:40 PST
X-Rocket-MIMEInfo: 002.001, SmVleiBEYXZlLCBkb24ndCBzY2FyZSB0aGUga2lkISAgOl4pICBIZSdzIG9ubHkgYW4gdW5kZXJncmFkIQ0KDQpMb29rIFJ5YW4sIERhdmUgcmVhbGx5IGRvZXMgaGF2ZSB5b3VyIGJlc3QgaW50ZXJlc3QgYXQgaGVhcnQgYW5kIHRoYXQgaXMgd2h5IGhlIHdhbnRzIHlvdSB0byB1c2UgQ0RGcyBpbnN0ZWFkIG9mIGF2ZXJhZ2VzLiAgQW5kIGhlIGlzIHJpZ2h0LCBJIHRoaW5rIHlvdSBzaG91bGQgdXNlIENERnMgYWxzby4gIEluIGZhY3QsIHNhdmUgeW91cnNlbGYgYSBwaWxlIG9mIHJlcGV0aXR2ZSB3b3JrIGEBMAEBAQE-
X-Mailer: YahooMailClassic/377 YahooMailWebService/0.8.203.740
Message-ID: <1424891800.38947.YahooMailBasic@web141601.mail.bf1.yahoo.com>
Date: Wed, 25 Feb 2015 11:16:40 -0800
From: Daniel Havey <dhavey@yahoo.com>
To: Ryan Doyle <rpdoyle@live.unc.edu>, Dave Taht <dave.taht@gmail.com>
In-Reply-To: <CAA93jw5dPhLmamcSHxD92b50XxmkkZNy28SWMkOSRFzBY3keBA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/Znr93MnmpQqdFqaOV298AenY8YI>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] Gathering Queue Length Statistics
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dhavey@yahoo.com
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 19:17:42 -0000

Jeez Dave, don't scare the kid!  :^)  He's only an undergrad!

Look Ryan, Dave really does have your best interest at heart and that is wh=
y he wants you to use CDFs instead of averages.  And he is right, I think y=
ou should use CDFs also.  In fact, save yourself a pile of repetitve work a=
nd just use Toke's tools.  They will produce better results and require les=
s work from you :)

Trust me on this.  I have done both and Toke's tools are waaaaay better and=
 easier than anything you (or I) will come up with.  Install Toke's tools a=
nd then you will have a cornucopia of awesome and repeatable results that y=
ou can just plug in to your final paper.  Go for it :^)

thanxs ;^)
...Daniel


--------------------------------------------
On Wed, 2/25/15, Dave Taht <dave.taht@gmail.com> wrote:

 Subject: Re: [aqm] Gathering Queue Length Statistics
 To: "Ryan Doyle" <rpdoyle@live.unc.edu>
 Cc: "aqm@ietf.org" <aqm@ietf.org>
 Date: Wednesday, February 25, 2015, 10:24 AM
=20
 On Wed, Feb 25, 2015 at
 9:53 AM, Ryan Doyle <rpdoyle@live.unc.edu>
 wrote:
 > Hello,
 >
 > I am a senior undergraduate student at the
 University of North Carolina at
 > Chapel
 Hill and am studying the effectiveness of AQMs. I have set
 up a lab
 > network and plan on running
 different sets of experiments with different
 > AQMs. My router machines are running Linux
 kernel version 3.16.0.
 >
 > I am using the fq_codel, codel, and pie
 qdiscs for my research and am
 > wondering
 if there is a way to collect statistics regarding the
 average
 > queue length since a qdisc was
 enabled? I have looked at tc's "-s" flag
 for
 > statistics, but they show nothing
 about queue length and I have been unable
 > to find anything else that might help me
 get queue length statistics.
=20
 Oh, god. I am getting incredibly sensitive
 about average queue length,
 and I realize
 that that is not what you meant. But since not enough
 people have seemingly read this or any of the
 related materials, here
 it is again.
=20
 http://www.pollere.net/Pdfdocs/QrantJul06.pdf
=20
 And I of course always
 recommend van=B4s talk on the fountain model for
 thinking about closed loop servo systems.
=20
 http://www.bufferbloat.net/projects/cerowrt/wiki/Bloat-videos
=20
 In the bufferbloat
 project...
=20
 We have
 developed many tools that drive aqms hard, see
 netperf-wrapper
 on github for that, which
 measures e2e delay without requiring any
 tools on the routers inbetween. e2e delay in my
 mind is way more
 important than average
 queue length. And you can derive the queue
 length(s) from tcp timestamps in those
 netperf-wrapper tests, from
 additional
 packet captures, if you must.
=20
 If you absolutely MUST derive average queue
 length from the box, you
 can poll the
 interface frequently with tc -s qdisc show as well as
 with ifconfig- and parse out the number of
 packets and the number of
 bytes. But you can
 do MUCH more valid statistical analysis than that,
 with that sort of data set - and if you poll
 too frequently you will
 heisenbug your
 tests, as those data collection calls take locks that
 interfere with the path. and we have all sorts
 of advice about traps
 for the unwary
 here:
=20
 http://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchmar=
king_Codel_and_FQ_Codel
=20
=20
 Please use
 things like CDFs to see the range of delays, rather than
 averages. It is what happens at above 90% of
 the range that makes
 bufferbloat maddening
 to ordinary users.
=20
 I am
 summarily rejecting any papers that I review that report
 average
 queue length as if it meant
 anything. And for a few other reasons. You
 have been warned. I really lost my temper after
 the last paper I
 reviewed last weekend and
 the resulting flamage is all over the bloat
 list and codel lists, and starts here:
=20
 https://lists.bufferbloat.net/pipermail/codel/2015-February/000872.html
=20
=20
 > Best,
 > Ryan Doyle
 >
 >
 _______________________________________________
 > aqm mailing list
 > aqm@ietf.org
 > https://www.ietf.org/mailman/listinfo/aqm
 >
=20
=20
=20
 --=20
 Dave
 T=E4ht
 Let's make wifi fast, less jittery
 and reliable again!
=20
 https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
=20
 _______________________________________________
 aqm mailing list
 aqm@ietf.org
 https://www.ietf.org/mailman/listinfo/aqm
 


From nobody Wed Feb 25 13:15:31 2015
Return-Path: <brouer@redhat.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8761A8775 for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 13:15:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.012
X-Spam-Level: 
X-Spam-Status: No, score=-6.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_32=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Qmy8wRwlyd31 for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 13:15:27 -0800 (PST)
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (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 765801A88A7 for <aqm@ietf.org>; Wed, 25 Feb 2015 13:15:21 -0800 (PST)
Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t1PLFJmg001127 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 25 Feb 2015 16:15:19 -0500
Received: from localhost (ovpn-112-47.phx2.redhat.com [10.3.112.47]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t1PLFEK6004538; Wed, 25 Feb 2015 16:15:15 -0500
Date: Thu, 26 Feb 2015 10:15:12 +1300
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Daniel Havey <dhavey@yahoo.com>, Toke =?UTF-8?B?SMO4aWxhbmQtSsO4cmdl?= =?UTF-8?B?bnNlbg==?= <toke@toke.dk>
Message-ID: <20150226101512.6bbcc126@redhat.com>
In-Reply-To: <1424891800.38947.YahooMailBasic@web141601.mail.bf1.yahoo.com>
References: <CAA93jw5dPhLmamcSHxD92b50XxmkkZNy28SWMkOSRFzBY3keBA@mail.gmail.com> <1424891800.38947.YahooMailBasic@web141601.mail.bf1.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/HW7QJGiZZQL8r5OjUssJz02GJHM>
Cc: Ryan Doyle <rpdoyle@live.unc.edu>, "aqm@ietf.org" <aqm@ietf.org>, Dave Taht <dave.taht@gmail.com>, brouer@redhat.com
Subject: Re: [aqm] Gathering Queue Length Statistics
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 21:15:30 -0000

Hi Ryan,

Follow Daniel's advice, just use netperf-wrapper. I wrote an easy setup
guide for netperf-wrapper here:
 http://netoptimizer.blogspot.co.nz/2014/09/mini-tutorial-for-netperf-wrapp=
er-setup.html

You will love the GUI mode:
 netperf-wrapper --gui

Most powerful thing in the GUI is that you can easy "load" result sets
on-top-of each-other, which allow you to easy compare. And you can save
these as PNG and add them easily to your report :-)

And the secret to (solving) bufferbloat is not the queue length, but
the time-spend in the queue, which is actually easier to derive ;-)=20

--=20
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Sr. Network Kernel Developer at Red Hat
  Author of http://www.iptv-analyzer.org
  LinkedIn: http://www.linkedin.com/in/brouer



On Wed, 25 Feb 2015 11:16:40 -0800 Daniel Havey <dhavey@yahoo.com> wrote:

> Jeez Dave, don't scare the kid!  :^)  He's only an undergrad!
>=20
> Look Ryan, Dave really does have your best interest at heart and that
> is why he wants you to use CDFs instead of averages.  And he is
> right, I think you should use CDFs also.  In fact, save yourself a
> pile of repetitve work and just use Toke's tools.  They will produce
> better results and require less work from you :)
>=20
> Trust me on this.  I have done both and Toke's tools are waaaaay
> better and easier than anything you (or I) will come up with.
> Install Toke's tools and then you will have a cornucopia of awesome
> and repeatable results that you can just plug in to your final
> paper.  Go for it :^)
>=20
> thanxs ;^)
> ...Daniel
>=20
>=20
> --------------------------------------------
> On Wed, 2/25/15, Dave Taht <dave.taht@gmail.com> wrote:
>=20
>  Subject: Re: [aqm] Gathering Queue Length Statistics
>  To: "Ryan Doyle" <rpdoyle@live.unc.edu>
>  Cc: "aqm@ietf.org" <aqm@ietf.org>
>  Date: Wednesday, February 25, 2015, 10:24 AM
> =20
>  On Wed, Feb 25, 2015 at
>  9:53 AM, Ryan Doyle <rpdoyle@live.unc.edu>
>  wrote:
>  > Hello,
>  >
>  > I am a senior undergraduate student at the
>  University of North Carolina at
>  > Chapel
>  Hill and am studying the effectiveness of AQMs. I have set
>  up a lab
>  > network and plan on running
>  different sets of experiments with different
>  > AQMs. My router machines are running Linux
>  kernel version 3.16.0.
>  >
>  > I am using the fq_codel, codel, and pie
>  qdiscs for my research and am
>  > wondering
>  if there is a way to collect statistics regarding the
>  average
>  > queue length since a qdisc was
>  enabled? I have looked at tc's "-s" flag
>  for
>  > statistics, but they show nothing
>  about queue length and I have been unable
>  > to find anything else that might help me
>  get queue length statistics.
> =20
>  Oh, god. I am getting incredibly sensitive
>  about average queue length,
>  and I realize
>  that that is not what you meant. But since not enough
>  people have seemingly read this or any of the
>  related materials, here
>  it is again.
> =20
>  http://www.pollere.net/Pdfdocs/QrantJul06.pdf
> =20
>  And I of course always
>  recommend van=C2=B4s talk on the fountain model for
>  thinking about closed loop servo systems.
> =20
>  http://www.bufferbloat.net/projects/cerowrt/wiki/Bloat-videos
> =20
>  In the bufferbloat
>  project...
> =20
>  We have
>  developed many tools that drive aqms hard, see
>  netperf-wrapper
>  on github for that, which
>  measures e2e delay without requiring any
>  tools on the routers inbetween. e2e delay in my
>  mind is way more
>  important than average
>  queue length. And you can derive the queue
>  length(s) from tcp timestamps in those
>  netperf-wrapper tests, from
>  additional
>  packet captures, if you must.
> =20
>  If you absolutely MUST derive average queue
>  length from the box, you
>  can poll the
>  interface frequently with tc -s qdisc show as well as
>  with ifconfig- and parse out the number of
>  packets and the number of
>  bytes. But you can
>  do MUCH more valid statistical analysis than that,
>  with that sort of data set - and if you poll
>  too frequently you will
>  heisenbug your
>  tests, as those data collection calls take locks that
>  interfere with the path. and we have all sorts
>  of advice about traps
>  for the unwary
>  here:
> =20
>  http://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchm=
arking_Codel_and_FQ_Codel
> =20
> =20
>  Please use
>  things like CDFs to see the range of delays, rather than
>  averages. It is what happens at above 90% of
>  the range that makes
>  bufferbloat maddening
>  to ordinary users.
> =20
>  I am
>  summarily rejecting any papers that I review that report
>  average
>  queue length as if it meant
>  anything. And for a few other reasons. You
>  have been warned. I really lost my temper after
>  the last paper I
>  reviewed last weekend and
>  the resulting flamage is all over the bloat
>  list and codel lists, and starts here:
> =20
>  https://lists.bufferbloat.net/pipermail/codel/2015-February/000872.html
> =20
> =20
>  > Best,
>  > Ryan Doyle
>  >
>  >
>  _______________________________________________
>  > aqm mailing list
>  > aqm@ietf.org
>  > https://www.ietf.org/mailman/listinfo/aqm
>  >
> =20
> =20
> =20
>  --=20
>  Dave
>  T=C3=A4ht
>  Let's make wifi fast, less jittery
>  and reliable again!
> =20
>  https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
> =20
>  _______________________________________________
>  aqm mailing list
>  aqm@ietf.org
>  https://www.ietf.org/mailman/listinfo/aqm
> =20
>=20
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm




--=20
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Sr. Network Kernel Developer at Red Hat
  Author of http://www.iptv-analyzer.org
  LinkedIn: http://www.linkedin.com/in/brouer


From nobody Wed Feb 25 15:00:10 2015
Return-Path: <dave.taht@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70CB91A904F for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 15:00:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_32=0.6, SPF_PASS=-0.001] autolearn=no
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 stJfayI1B9UR for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 15:00:06 -0800 (PST)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED15C1A904C for <aqm@ietf.org>; Wed, 25 Feb 2015 15:00:05 -0800 (PST)
Received: by mail-oi0-f50.google.com with SMTP id v1so6203655oia.9 for <aqm@ietf.org>; Wed, 25 Feb 2015 15:00:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=K1JNbHLagpxkhgnxgkMC1y2WIX4fenL165l7nssIiMA=; b=AL9GMD6yJp3qJ00K/Aj7dPPKF82OZTufEz6HF9dwzquxf0lLJBlio6zLQUywWCJRyV 0CEu3U87eilxj2DUjZamU68nCZFXNN62WhzvWnNH0nnJlUTKqWRBV243t+FS0pRocxjB EFpAp2XxOg25Z4cQT+eTQ7KLLHPVDmbwK8OxPBsmJHRTgFoY4TFGOIoc5rjHpt/ISc8o mUCqFZdi2u4PhOJRvdSCCfyb2bkigndGU4uMcvHL0pZ70WA4js2jil9e3VDH5eTWFVSZ lH3c/T1Ja4cUbLtwmvz5g3468pIN8V3TzOWk2Vo9pda3RUB0SwwVaFoOr5yym6s2Q3+A ilBQ==
MIME-Version: 1.0
X-Received: by 10.202.62.70 with SMTP id l67mr3729603oia.59.1424905205178; Wed, 25 Feb 2015 15:00:05 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Wed, 25 Feb 2015 15:00:05 -0800 (PST)
In-Reply-To: <20150226101512.6bbcc126@redhat.com>
References: <CAA93jw5dPhLmamcSHxD92b50XxmkkZNy28SWMkOSRFzBY3keBA@mail.gmail.com> <1424891800.38947.YahooMailBasic@web141601.mail.bf1.yahoo.com> <20150226101512.6bbcc126@redhat.com>
Date: Wed, 25 Feb 2015 15:00:05 -0800
Message-ID: <CAA93jw7STEyw5227jLu9_COXY_5PQ5+FBPWszXw9wTQknSr1Dw@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/Pi7wufG10pz9gD3KCdlLCswOS1s>
Cc: Ryan Doyle <rpdoyle@live.unc.edu>, "aqm@ietf.org" <aqm@ietf.org>, Daniel Havey <dhavey@yahoo.com>
Subject: Re: [aqm] Gathering Queue Length Statistics
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 23:00:08 -0000

On Wed, Feb 25, 2015 at 1:15 PM, Jesper Dangaard Brouer
<brouer@redhat.com> wrote:
> Hi Ryan,
>
> Follow Daniel's advice, just use netperf-wrapper. I wrote an easy setup
> guide for netperf-wrapper here:
>  http://netoptimizer.blogspot.co.nz/2014/09/mini-tutorial-for-netperf-wra=
pper-setup.html

In looking at your tutorial I note that netperf in svn has added a new
EXTREMELY nice feature (that netperf-wrapper does not use yet),
notably

d@nuc-client:~/git/netperf$ DUMP_TCP_INFO=3D1 netperf -H 172.21.2.1
MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
172.21.2.1 () port 0 AF_INET : demo
tcpi_rto 202000 tcpi_ato 0 tcpi_pmtu 1500 tcpi_rcv_ssthresh 29200
tcpi_rtt 1558 tcpi_rttvar 290 tcpi_snd_ssthresh 52 tpci_snd_cwnd 54
tcpi_reordering 3 tcpi_total_retrans 7
Recv   Send    Send
Socket Socket  Message  Elapsed
Size   Size    Size     Time     Throughput
bytes  bytes   bytes    secs.    10^6bits/sec

 87380  16384  16384    10.03     320.94


So I would kind of recommend using the svn version rather than the 2.6
version at this point. (big thanks to eric dumazet for the suggestion)

I also note that netperf-wrapper has a man page, which apparently a
few have missed.

Patches are always welcomed to improve the documentation. Also there
are a whole bunch of new tests that I would like to add (or prefer!
find people to write and add) involving wrapping a few other tools
that are easier to use and more robust than dit-g, which I can write
up specs for up here if anyone is interested... and some new stuff for
wifi.

and I have a new analytical model for looking the bifurcation
characteristics of multiple flows moving in and out of slow start...
(but I will be damned if I publish the core ideas at the moment, or
explain less obliquely, as I hope to finally get a paper out of it in
collaboration with someone willing to do the experiments. :)
Volunteers?


)

> You will love the GUI mode:
>  netperf-wrapper --gui


> Most powerful thing in the GUI is that you can easy "load" result sets
> on-top-of each-other, which allow you to easy compare. And you can save
> these as PNG and add them easily to your report :-)

I so love being able to compare noisy data from multiple test runs...

And I tend to use .svgs or .eps or .pdf rather than .pngs as you
capture more scalable detail that works better at multiple
resolutions. At least some latex tools can deal with that well.

>
> And the secret to (solving) bufferbloat is not the queue length, but
> the time-spend in the queue, which is actually easier to derive ;-)

+10, but it is mildly more tricky than that. ;)

> --
> Best regards,
>   Jesper Dangaard Brouer
>   MSc.CS, Sr. Network Kernel Developer at Red Hat
>   Author of http://www.iptv-analyzer.org
>   LinkedIn: http://www.linkedin.com/in/brouer
>
>
>
> On Wed, 25 Feb 2015 11:16:40 -0800 Daniel Havey <dhavey@yahoo.com> wrote:
>
>> Jeez Dave, don't scare the kid!  :^)  He's only an undergrad!
>>
>> Look Ryan, Dave really does have your best interest at heart and that
>> is why he wants you to use CDFs instead of averages.  And he is
>> right, I think you should use CDFs also.  In fact, save yourself a
>> pile of repetitve work and just use Toke's tools.  They will produce
>> better results and require less work from you :)
>>
>> Trust me on this.  I have done both and Toke's tools are waaaaay
>> better and easier than anything you (or I) will come up with.
>> Install Toke's tools and then you will have a cornucopia of awesome
>> and repeatable results that you can just plug in to your final
>> paper.  Go for it :^)
>>
>> thanxs ;^)
>> ...Daniel
>>
>>
>> --------------------------------------------
>> On Wed, 2/25/15, Dave Taht <dave.taht@gmail.com> wrote:
>>
>>  Subject: Re: [aqm] Gathering Queue Length Statistics
>>  To: "Ryan Doyle" <rpdoyle@live.unc.edu>
>>  Cc: "aqm@ietf.org" <aqm@ietf.org>
>>  Date: Wednesday, February 25, 2015, 10:24 AM
>>
>>  On Wed, Feb 25, 2015 at
>>  9:53 AM, Ryan Doyle <rpdoyle@live.unc.edu>
>>  wrote:
>>  > Hello,
>>  >
>>  > I am a senior undergraduate student at the
>>  University of North Carolina at
>>  > Chapel
>>  Hill and am studying the effectiveness of AQMs. I have set
>>  up a lab
>>  > network and plan on running
>>  different sets of experiments with different
>>  > AQMs. My router machines are running Linux
>>  kernel version 3.16.0.
>>  >
>>  > I am using the fq_codel, codel, and pie
>>  qdiscs for my research and am
>>  > wondering
>>  if there is a way to collect statistics regarding the
>>  average
>>  > queue length since a qdisc was
>>  enabled? I have looked at tc's "-s" flag
>>  for
>>  > statistics, but they show nothing
>>  about queue length and I have been unable
>>  > to find anything else that might help me
>>  get queue length statistics.
>>
>>  Oh, god. I am getting incredibly sensitive
>>  about average queue length,
>>  and I realize
>>  that that is not what you meant. But since not enough
>>  people have seemingly read this or any of the
>>  related materials, here
>>  it is again.
>>
>>  http://www.pollere.net/Pdfdocs/QrantJul06.pdf
>>
>>  And I of course always
>>  recommend van=C2=B4s talk on the fountain model for
>>  thinking about closed loop servo systems.
>>
>>  http://www.bufferbloat.net/projects/cerowrt/wiki/Bloat-videos
>>
>>  In the bufferbloat
>>  project...
>>
>>  We have
>>  developed many tools that drive aqms hard, see
>>  netperf-wrapper
>>  on github for that, which
>>  measures e2e delay without requiring any
>>  tools on the routers inbetween. e2e delay in my
>>  mind is way more
>>  important than average
>>  queue length. And you can derive the queue
>>  length(s) from tcp timestamps in those
>>  netperf-wrapper tests, from
>>  additional
>>  packet captures, if you must.
>>
>>  If you absolutely MUST derive average queue
>>  length from the box, you
>>  can poll the
>>  interface frequently with tc -s qdisc show as well as
>>  with ifconfig- and parse out the number of
>>  packets and the number of
>>  bytes. But you can
>>  do MUCH more valid statistical analysis than that,
>>  with that sort of data set - and if you poll
>>  too frequently you will
>>  heisenbug your
>>  tests, as those data collection calls take locks that
>>  interfere with the path. and we have all sorts
>>  of advice about traps
>>  for the unwary
>>  here:
>>
>>  http://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_bench=
marking_Codel_and_FQ_Codel
>>
>>
>>  Please use
>>  things like CDFs to see the range of delays, rather than
>>  averages. It is what happens at above 90% of
>>  the range that makes
>>  bufferbloat maddening
>>  to ordinary users.
>>
>>  I am
>>  summarily rejecting any papers that I review that report
>>  average
>>  queue length as if it meant
>>  anything. And for a few other reasons. You
>>  have been warned. I really lost my temper after
>>  the last paper I
>>  reviewed last weekend and
>>  the resulting flamage is all over the bloat
>>  list and codel lists, and starts here:
>>
>>  https://lists.bufferbloat.net/pipermail/codel/2015-February/000872.html
>>
>>
>>  > Best,
>>  > Ryan Doyle
>>  >
>>  >
>>  _______________________________________________
>>  > aqm mailing list
>>  > aqm@ietf.org
>>  > https://www.ietf.org/mailman/listinfo/aqm
>>  >
>>
>>
>>
>>  --
>>  Dave
>>  T=C3=A4ht
>>  Let's make wifi fast, less jittery
>>  and reliable again!
>>
>>  https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
>>
>>  _______________________________________________
>>  aqm mailing list
>>  aqm@ietf.org
>>  https://www.ietf.org/mailman/listinfo/aqm
>>
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>
>
>
>
> --
> Best regards,
>   Jesper Dangaard Brouer
>   MSc.CS, Sr. Network Kernel Developer at Red Hat
>   Author of http://www.iptv-analyzer.org
>   LinkedIn: http://www.linkedin.com/in/brouer



--=20
Dave T=C3=A4ht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb


From nobody Wed Feb 25 20:19:22 2015
Return-Path: <garmitage@swin.edu.au>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B39F21A19EC for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 20:19:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.506
X-Spam-Level: 
X-Spam-Status: No, score=-0.506 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 nSt1PTW1Z0HD for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 20:19:18 -0800 (PST)
Received: from gpo1.cc.swin.edu.au (gpo1.cc.swin.edu.au [136.186.1.30]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 260D31A01AA for <aqm@ietf.org>; Wed, 25 Feb 2015 20:19:17 -0800 (PST)
Received: from [136.186.229.37] (garmitage.caia.swin.edu.au [136.186.229.37]) by gpo1.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id t1Q4JF6V010274 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);  Thu, 26 Feb 2015 15:19:16 +1100
Message-ID: <54EE9EC3.30902@swin.edu.au>
Date: Thu, 26 Feb 2015 15:19:15 +1100
From: grenville armitage <garmitage@swin.edu.au>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121107 Thunderbird/16.0.2
MIME-Version: 1.0
To: aqm@ietf.org
References: <BAY176-W35105790F5BC047AA12309A5170@phx.gbl>
In-Reply-To: <BAY176-W35105790F5BC047AA12309A5170@phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/4Tx7wa64YZ-fLFM47it2DocvLME>
Subject: Re: [aqm] Gathering Queue Length Statistics
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 26 Feb 2015 04:19:20 -0000

On 02/26/2015 04:53, Ryan Doyle wrote:
	[..]
> I am using the fq_codel, codel, and pie qdiscs for my research and am
> wondering if there is a way to collect statistics regarding the
> average queue length since a qdisc was enabled? I have looked at tc's
> "-s" flag for statistics, but they show nothing about queue length
> and I have been unable to find anything else that might help me get
> queue length statistics.

Perhaps off on a tangent, but you might find http://caia.swin.edu.au/tools/spp/ a useful complement to your measurements. If you tcpdump the packets going in and out either side of your router, spp can take the two dump files and estimate the instantaneous RTT (itself a reflection of instantaneous queue depth) over time between said router ports. Use this to validate/contrast with RTT estimates you extract from TCP timestamps.

cheers,
gja



From nobody Wed Feb 25 20:40:45 2015
Return-Path: <prvs=4924feaa2=rpdoyle@live.unc.edu>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15C691A00F9 for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 20:40:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 UxyuhEh4Qn3M for <aqm@ietfa.amsl.com>; Wed, 25 Feb 2015 20:40:36 -0800 (PST)
Received: from mxip11i.isis.unc.edu (mxip11i.isis.unc.edu [152.2.0.32]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46C9C1A000F for <aqm@ietf.org>; Wed, 25 Feb 2015 20:40:35 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2C7BQC2oO5U/8BPAphbgj9DUlqEWr0NgR8dAQuFbgKBKjgUAQEBAQEBAXyEDwEBAQEBAQEBAQEPXAsFCwsRAwECAS4hBgEnCAYOBSKHeAEDCQgNsEoBjTORTQ1FhHsBAQEBAQEBAQEBAQEBAQEBAQEBAQEXixOCRCaBcAMRB4MXgRQFiiIuiHODRlmCYYMagiEwhjOCSoM+I4F/AxyBblEBgkIBAQE
X-IPAS-Result: A2C7BQC2oO5U/8BPAphbgj9DUlqEWr0NgR8dAQuFbgKBKjgUAQEBAQEBAXyEDwEBAQEBAQEBAQEPXAsFCwsRAwECAS4hBgEnCAYOBSKHeAEDCQgNsEoBjTORTQ1FhHsBAQEBAQEBAQEBAQEBAQEBAQEBAQEXixOCRCaBcAMRB4MXgRQFiiIuiHODRlmCYYMagiEwhjOCSoM+I4F/AxyBblEBgkIBAQE
X-IronPort-AV: E=Sophos; i="5.09,650,1418101200"; d="scan'208,217"; a="39209003"
Received: from its-msxht7f.ad.unc.edu ([152.2.79.192]) by mxip11o.isis.unc.edu with ESMTP/TLS/AES128-SHA; 25 Feb 2015 23:40:34 -0500
Received: from mail.hotmail.com (172.22.44.34) by smtp.unc.edu (152.2.79.192) with Microsoft SMTP Server id 14.3.224.2; Wed, 25 Feb 2015 23:40:34 -0500
Received: from BAY176-W51 ([157.56.23.7]) by COL004-WSS1S6.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 25 Feb 2015 20:40:32 -0800
X-TMN: [K43ntQlD2W+T+TOpy6fxITjdGRqfLPV4]
Message-ID: <BAY176-W5148D8EFEF0CCC5D1E94FBA5140@phx.gbl>
Content-Type: multipart/alternative; boundary="_a682fc52-8933-41a6-802f-ab6a55edd62e_"
From: Ryan Doyle <rpdoyle@live.unc.edu>
To: Dave Taht <dave.taht@gmail.com>
Date: Wed, 25 Feb 2015 23:40:31 -0500
Importance: Normal
In-Reply-To: <CAA93jw5dPhLmamcSHxD92b50XxmkkZNy28SWMkOSRFzBY3keBA@mail.gmail.com>
References: <BAY176-W35105790F5BC047AA12309A5170@phx.gbl>, <CAA93jw5dPhLmamcSHxD92b50XxmkkZNy28SWMkOSRFzBY3keBA@mail.gmail.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 26 Feb 2015 04:40:32.0532 (UTC) FILETIME=[5AD40D40:01D0517E]
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/sR6XAdYkWIYdfbelEv2czJpWbgk>
Cc: "brouer@redhat.com" <brouer@redhat.com>, "aqm@ietf.org" <aqm@ietf.org>, "dhavey@yahoo.com" <dhavey@yahoo.com>, "fred@cisco.com" <fred@cisco.com>
Subject: Re: [aqm] Gathering Queue Length Statistics
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 26 Feb 2015 04:40:44 -0000

--_a682fc52-8933-41a6-802f-ab6a55edd62e_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thank you very much for taking the time to write your response and link me =
to the resources.=20

I am planning on creating CDFs and have no intention of using average queue=
 length as a primary statistic in my research. I am putting much more empha=
sis on end to end delays. That said=2C I am interested in taking sample mea=
surements of instantaneous queue length=2C but am really looking for any qu=
eue-length statistics the AQMs may measure.

Best=2C
Ryan Doyle

p.s. Thank you to everyone else that responded as well. I will be sure to l=
ook at all of the links=2C but can't respond to everything individually.

> Date: Wed=2C 25 Feb 2015 10:24:45 -0800
> From: dave.taht@gmail.com
> To: rpdoyle@live.unc.edu
> CC: aqm@ietf.org
> Subject: Re: [aqm] Gathering Queue Length Statistics
>=20
> On Wed=2C Feb 25=2C 2015 at 9:53 AM=2C Ryan Doyle <rpdoyle@live.unc.edu> =
wrote:
> > Hello=2C
> >
> > I am a senior undergraduate student at the University of North Carolina=
 at
> > Chapel Hill and am studying the effectiveness of AQMs. I have set up a =
lab
> > network and plan on running different sets of experiments with differen=
t
> > AQMs. My router machines are running Linux kernel version 3.16.0.
> >
> > I am using the fq_codel=2C codel=2C and pie qdiscs for my research and =
am
> > wondering if there is a way to collect statistics regarding the average
> > queue length since a qdisc was enabled? I have looked at tc's "-s" flag=
 for
> > statistics=2C but they show nothing about queue length and I have been =
unable
> > to find anything else that might help me get queue length statistics.
>=20
> Oh=2C god. I am getting incredibly sensitive about average queue length=
=2C
> and I realize that that is not what you meant. But since not enough
> people have seemingly read this or any of the related materials=2C here
> it is again.
>=20
> http://www.pollere.net/Pdfdocs/QrantJul06.pdf
>=20
> And I of course always recommend van=B4s talk on the fountain model for
> thinking about closed loop servo systems.
>=20
> http://www.bufferbloat.net/projects/cerowrt/wiki/Bloat-videos
>=20
> In the bufferbloat project...
>=20
> We have developed many tools that drive aqms hard=2C see netperf-wrapper
> on github for that=2C which measures e2e delay without requiring any
> tools on the routers inbetween. e2e delay in my mind is way more
> important than average queue length. And you can derive the queue
> length(s) from tcp timestamps in those netperf-wrapper tests=2C from
> additional packet captures=2C if you must.
>=20
> If you absolutely MUST derive average queue length from the box=2C you
> can poll the interface frequently with tc -s qdisc show as well as
> with ifconfig- and parse out the number of packets and the number of
> bytes. But you can do MUCH more valid statistical analysis than that=2C
> with that sort of data set - and if you poll too frequently you will
> heisenbug your tests=2C as those data collection calls take locks that
> interfere with the path. and we have all sorts of advice about traps
> for the unwary here:
>=20
> http://www.bufferbloat.net/projects/codel/wiki/Best_practices_for_benchma=
rking_Codel_and_FQ_Codel
>=20
>=20
> Please use things like CDFs to see the range of delays=2C rather than
> averages. It is what happens at above 90% of the range that makes
> bufferbloat maddening to ordinary users.
>=20
> I am summarily rejecting any papers that I review that report average
> queue length as if it meant anything. And for a few other reasons. You
> have been warned. I really lost my temper after the last paper I
> reviewed last weekend and the resulting flamage is all over the bloat
> list and codel lists=2C and starts here:
>=20
> https://lists.bufferbloat.net/pipermail/codel/2015-February/000872.html
>=20
>=20
> > Best=2C
> > Ryan Doyle
> >
> > _______________________________________________
> > aqm mailing list
> > aqm@ietf.org
> > https://www.ietf.org/mailman/listinfo/aqm
> >
>=20
>=20
>=20
> --=20
> Dave T=E4ht
> Let's make wifi fast=2C less jittery and reliable again!
>=20
> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
>=20
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
 		 	   		  =

--_a682fc52-8933-41a6-802f-ab6a55edd62e_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>Thank you very much for taking t=
he time to write your response and link me to the resources. <br><br>I am p=
lanning on creating CDFs and have no intention of using average queue lengt=
h as a primary statistic in my research. I am putting much more emphasis on=
 end to end delays. That said=2C I am interested in taking sample measureme=
nts of instantaneous queue length=2C but am really looking for any queue-le=
ngth statistics the AQMs may measure.<br><br>Best=2C<br>Ryan Doyle<br><br>p=
.s. Thank you to everyone else that responded as well. I will be sure to lo=
ok at all of the links=2C but can't respond to everything individually.<br>=
<br><div>&gt=3B Date: Wed=2C 25 Feb 2015 10:24:45 -0800<br>&gt=3B From: dav=
e.taht@gmail.com<br>&gt=3B To: rpdoyle@live.unc.edu<br>&gt=3B CC: aqm@ietf.=
org<br>&gt=3B Subject: Re: [aqm] Gathering Queue Length Statistics<br>&gt=
=3B <br>&gt=3B On Wed=2C Feb 25=2C 2015 at 9:53 AM=2C Ryan Doyle &lt=3Brpdo=
yle@live.unc.edu&gt=3B wrote:<br>&gt=3B &gt=3B Hello=2C<br>&gt=3B &gt=3B<br=
>&gt=3B &gt=3B I am a senior undergraduate student at the University of Nor=
th Carolina at<br>&gt=3B &gt=3B Chapel Hill and am studying the effectivene=
ss of AQMs. I have set up a lab<br>&gt=3B &gt=3B network and plan on runnin=
g different sets of experiments with different<br>&gt=3B &gt=3B AQMs. My ro=
uter machines are running Linux kernel version 3.16.0.<br>&gt=3B &gt=3B<br>=
&gt=3B &gt=3B I am using the fq_codel=2C codel=2C and pie qdiscs for my res=
earch and am<br>&gt=3B &gt=3B wondering if there is a way to collect statis=
tics regarding the average<br>&gt=3B &gt=3B queue length since a qdisc was =
enabled? I have looked at tc's "-s" flag for<br>&gt=3B &gt=3B statistics=2C=
 but they show nothing about queue length and I have been unable<br>&gt=3B =
&gt=3B to find anything else that might help me get queue length statistics=
.<br>&gt=3B <br>&gt=3B Oh=2C god. I am getting incredibly sensitive about a=
verage queue length=2C<br>&gt=3B and I realize that that is not what you me=
ant. But since not enough<br>&gt=3B people have seemingly read this or any =
of the related materials=2C here<br>&gt=3B it is again.<br>&gt=3B <br>&gt=
=3B http://www.pollere.net/Pdfdocs/QrantJul06.pdf<br>&gt=3B <br>&gt=3B And =
I of course always recommend van=B4s talk on the fountain model for<br>&gt=
=3B thinking about closed loop servo systems.<br>&gt=3B <br>&gt=3B http://w=
ww.bufferbloat.net/projects/cerowrt/wiki/Bloat-videos<br>&gt=3B <br>&gt=3B =
In the bufferbloat project...<br>&gt=3B <br>&gt=3B We have developed many t=
ools that drive aqms hard=2C see netperf-wrapper<br>&gt=3B on github for th=
at=2C which measures e2e delay without requiring any<br>&gt=3B tools on the=
 routers inbetween. e2e delay in my mind is way more<br>&gt=3B important th=
an average queue length. And you can derive the queue<br>&gt=3B length(s) f=
rom tcp timestamps in those netperf-wrapper tests=2C from<br>&gt=3B additio=
nal packet captures=2C if you must.<br>&gt=3B <br>&gt=3B If you absolutely =
MUST derive average queue length from the box=2C you<br>&gt=3B can poll the=
 interface frequently with tc -s qdisc show as well as<br>&gt=3B with ifcon=
fig- and parse out the number of packets and the number of<br>&gt=3B bytes.=
 But you can do MUCH more valid statistical analysis than that=2C<br>&gt=3B=
 with that sort of data set - and if you poll too frequently you will<br>&g=
t=3B heisenbug your tests=2C as those data collection calls take locks that=
<br>&gt=3B interfere with the path. and we have all sorts of advice about t=
raps<br>&gt=3B for the unwary here:<br>&gt=3B <br>&gt=3B http://www.bufferb=
loat.net/projects/codel/wiki/Best_practices_for_benchmarking_Codel_and_FQ_C=
odel<br>&gt=3B <br>&gt=3B <br>&gt=3B Please use things like CDFs to see the=
 range of delays=2C rather than<br>&gt=3B averages. It is what happens at a=
bove 90% of the range that makes<br>&gt=3B bufferbloat maddening to ordinar=
y users.<br>&gt=3B <br>&gt=3B I am summarily rejecting any papers that I re=
view that report average<br>&gt=3B queue length as if it meant anything. An=
d for a few other reasons. You<br>&gt=3B have been warned. I really lost my=
 temper after the last paper I<br>&gt=3B reviewed last weekend and the resu=
lting flamage is all over the bloat<br>&gt=3B list and codel lists=2C and s=
tarts here:<br>&gt=3B <br>&gt=3B https://lists.bufferbloat.net/pipermail/co=
del/2015-February/000872.html<br>&gt=3B <br>&gt=3B <br>&gt=3B &gt=3B Best=
=2C<br>&gt=3B &gt=3B Ryan Doyle<br>&gt=3B &gt=3B<br>&gt=3B &gt=3B _________=
______________________________________<br>&gt=3B &gt=3B aqm mailing list<br=
>&gt=3B &gt=3B aqm@ietf.org<br>&gt=3B &gt=3B https://www.ietf.org/mailman/l=
istinfo/aqm<br>&gt=3B &gt=3B<br>&gt=3B <br>&gt=3B <br>&gt=3B <br>&gt=3B -- =
<br>&gt=3B Dave T=E4ht<br>&gt=3B Let's make wifi fast=2C less jittery and r=
eliable again!<br>&gt=3B <br>&gt=3B https://plus.google.com/u/0/10794217561=
5993706558/posts/TVX3o84jjmb<br>&gt=3B <br>&gt=3B _________________________=
______________________<br>&gt=3B aqm mailing list<br>&gt=3B aqm@ietf.org<br=
>&gt=3B https://www.ietf.org/mailman/listinfo/aqm<br></div> 		 	   		  </di=
v></body>
</html>=

--_a682fc52-8933-41a6-802f-ab6a55edd62e_--


From nobody Thu Feb 26 02:30:06 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29BE71A2130 for <aqm@ietfa.amsl.com>; Thu, 26 Feb 2015 02:30:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.961
X-Spam-Level: 
X-Spam-Status: No, score=-3.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 iA7lmun3Gf3r for <aqm@ietfa.amsl.com>; Thu, 26 Feb 2015 02:30:03 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A043E1A3BA4 for <aqm@ietf.org>; Thu, 26 Feb 2015 02:30:02 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id A24F2A3; Thu, 26 Feb 2015 11:30:00 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424946600; bh=/VMiQSwwNQuny+zfvaBvW0aMJ2WBlisyEy76gvE8kHQ=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=4eIluKHXZQwblU4JIibehp3j9Jb5nHwf1WBFXW6Xq5q3yHVb21YoGImTaw7bQnhCo uhQHUmmFFUxPJSaL0cRTH6VyBDoYmZhww/QLeBAPRXEzWG9O++bSAJrHNea9he4Ju+ MS2r9YOZqe9uKFoDVUuVNCaSvqN5mhkw3mZjL+xA=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 99759A2; Thu, 26 Feb 2015 11:30:00 +0100 (CET)
Date: Thu, 26 Feb 2015 11:30:00 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
In-Reply-To: <CAA93jw5dPhLmamcSHxD92b50XxmkkZNy28SWMkOSRFzBY3keBA@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1502261125510.4007@uplift.swm.pp.se>
References: <BAY176-W35105790F5BC047AA12309A5170@phx.gbl> <CAA93jw5dPhLmamcSHxD92b50XxmkkZNy28SWMkOSRFzBY3keBA@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/TimViQKo0NzxmDhVHlB_8_9NcXg>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] Gathering Queue Length Statistics
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 26 Feb 2015 10:30:05 -0000

On Wed, 25 Feb 2015, Dave Taht wrote:

> Oh, god. I am getting incredibly sensitive about average queue length, 
> and I realize that that is not what you meant. But since not enough 
> people have seemingly read this or any of the related materials, here it 
> is again.

But it would be valuable to see "instant current length" and other types 
of statistics if they were collected once per second and the per-second 
values were kept for 30 values back in time (ie 30 seconds worth of data)?

I know some commercial routers will have the possibility of showing the 
current percentage queue fill on the device. I don't know how the Linux 
AQM system works, but exposing some of these counters through the proc 
subsystem (or something else), might work, and then a userspace daemon 
could poll this data as often as it wanted, then you don't even need the 
kernel to do averaging and keeping the data.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Thu Feb 26 02:36:14 2015
Return-Path: <toke@toke.dk>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDFBD1A1EE8 for <aqm@ietfa.amsl.com>; Thu, 26 Feb 2015 02:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.693
X-Spam-Level: 
X-Spam-Status: No, score=-0.693 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_DK=1.009, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
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 unFy5pi33sFr for <aqm@ietfa.amsl.com>; Thu, 26 Feb 2015 02:36:12 -0800 (PST)
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 B612B1A3BA4 for <aqm@ietf.org>; Thu, 26 Feb 2015 02:36:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at mail2.tohojo.dk
Sender: toke@toke.dk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toke.dk; s=201310; t=1424946964; bh=j7cgQgXK0BuaL84JKzxMiQwjqZEb3CpQLjtNAf902h0=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=j7nlp90+PApOhil1aKBaERvUWgTZDOPsNdVd+84WhGdzmEGRSwiancLyqsiFhcRMi Yhbd2dfertyD4rQrfVG9ssBxwxaZ1CkLp/7YzR8Ps0jQj/E9P1XqCrGPZSB4YTkddN Kzw1zdvBqE79YDw60KXkpXswG3ZV++0mqiuONSw0=
Received: by alrua-kau.kau.toke.dk (Postfix, from userid 1000) id EBF033E3766; Thu, 26 Feb 2015 11:36:03 +0100 (CET)
From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <BAY176-W35105790F5BC047AA12309A5170@phx.gbl> <CAA93jw5dPhLmamcSHxD92b50XxmkkZNy28SWMkOSRFzBY3keBA@mail.gmail.com> <alpine.DEB.2.02.1502261125510.4007@uplift.swm.pp.se>
Date: Thu, 26 Feb 2015 11:36:03 +0100
In-Reply-To: <alpine.DEB.2.02.1502261125510.4007@uplift.swm.pp.se> (Mikael Abrahamsson's message of "Thu, 26 Feb 2015 11:30:00 +0100 (CET)")
Message-ID: <87k2z5ot7w.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/-Ts6gHfMSQVKA5Zpxx5bsYjGKFs>
Cc: Dave Taht <dave.taht@gmail.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] Gathering Queue Length Statistics
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 26 Feb 2015 10:36:13 -0000

Mikael Abrahamsson <swmike@swm.pp.se> writes:

> I don't know how the Linux AQM system works, but exposing some of
> these counters through the proc subsystem (or something else), might
> work, and then a userspace daemon could poll this data as often as it
> wanted, then you don't even need the kernel to do averaging and
> keeping the data.

It's exposed via the Netlink interface, which is what `tc -s` shows:

qdisc fq_codel 110: dev enp2s0 parent 1:10 limit 1000p flows 1014 quantum 500 target 5.0ms interval 100.0ms ecn 
 Sent 16981968691 bytes 17816348 pkt (dropped 8, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0 
  maxpacket 13216 drop_overlimit 0 new_flow_count 6502039 ecn_mark 0
  new_flows_len 1 old_flows_len 5

The 'backlog 0b 0p' shows that the queue is currently empty, while the
lines below show qdisc-specific stats. But as Dave said, getting the
statistics has some locking issues that may (or will, probably) cause
trouble if trying to poll it too frequently...

-Toke


From nobody Thu Feb 26 06:50:38 2015
Return-Path: <rs@netapp.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F1CF1A0187 for <aqm@ietfa.amsl.com>; Thu, 26 Feb 2015 06:50:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level: 
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 RTpFc43VTVyB for <aqm@ietfa.amsl.com>; Thu, 26 Feb 2015 06:50:31 -0800 (PST)
Received: from mx144.netapp.com (mx144.netapp.com [216.240.21.25]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62E981A0162 for <aqm@ietf.org>; Thu, 26 Feb 2015 06:50:31 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.09,652,1418112000"; d="scan'208";a="26299450"
Received: from hioexcmbx05-prd.hq.netapp.com ([10.122.105.38]) by mx144-out.netapp.com with ESMTP; 26 Feb 2015 06:45:31 -0800
Received: from HIOEXCMBX05-PRD.hq.netapp.com (10.122.105.38) by hioexcmbx05-prd.hq.netapp.com (10.122.105.38) with Microsoft SMTP Server (TLS) id 15.0.995.29; Thu, 26 Feb 2015 06:45:30 -0800
Received: from HIOEXCMBX05-PRD.hq.netapp.com ([::1]) by hioexcmbx05-prd.hq.netapp.com ([fe80::c4b3:e711:88fe:6ce%21]) with mapi id 15.00.0995.031; Thu, 26 Feb 2015 06:45:30 -0800
From: "Scheffenegger, Richard" <rs@netapp.com>
To: Greg White <g.white@CableLabs.com>, "'aqm@ietf.org'" <aqm@ietf.org>
Thread-Topic: [aqm] adoption of draft-white-aqm-docsis-pie-01
Thread-Index: AdBR0qmLD+JlLAXWSZym1tRD+kojwQ==
Date: Thu, 26 Feb 2015 14:45:29 +0000
Message-ID: <96cffe6791f54a67ae6b6359de6a3d6e@hioexcmbx05-prd.hq.netapp.com>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.122.56.79]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/_ei_ZYQ_-xpFN2t-_b_20uXsSBA>
Cc: "Rong Pan \(ropan\)" <ropan@cisco.com>, "aqm-chairs@tools.ietf.org" <aqm-chairs@tools.ietf.org>
Subject: Re: [aqm] adoption of draft-white-aqm-docsis-pie-01
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 26 Feb 2015 14:50:34 -0000

Hi Greg, group,



Regarding the adoption call, this is something we can actually (and should)=
 start on the list.

We can confirm that during the Dallas meeting in the room, but even before =
that, we'd like to get responses on the list now...

Perhaps we have some volunteers to review this new version as well...


Best regards,
  Richard



> -----Original Message-----
> From: Greg White [mailto:g.white@CableLabs.com]
> Sent: Donnerstag, 26. Februar 2015 01:13
> To: aqm-chairs@tools.ietf.org
> Cc: Rong Pan (ropan)
> Subject: Re: [aqm] agenda for IETF 92 / Dallas
>=20
> Wes & Richard,
>=20
> Unfortunately I will not be at IETF92 in person, but will attend remotely=
.
>  For draft-white-aqm-docsis-pie, Rong & I updated it in January and
> included a new appendix to give a change log, which reads:
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Appendix B.  Change Log
> B.1.  Since draft-white-aqm-docsis-pie-01
>=20
>    Added Change Log.
>=20
>    Removed discussion of Packet drop de-randomization, Enhanced burst
>    protection, and 16ms update interval, as these are now included in
>    [I-D.ietf-aqm-pie].
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>=20
> Regarding WG adoption, I saw some support from Lars (and no objections) t=
o
> adopting it on an Informational track.   Will you do an official adoption
> call at the Dallas meeting?
>=20
> -Greg
>=20
>=20
> On 2/23/15, 8:40 PM, "Wesley Eddy" <wes@mti-systems.com> wrote:
>=20
> >Greetings AQMers!  We requested a short AQM meeting slot at the upcoming
> >IETF 92 meeting in Dallas, and we received a 1-hour slot on Tuesday:
> >https://datatracker.ietf.org/meeting/92/agenda.html
> >
> >Since this is not a lot of time, we'll need to prioritize the work that
> >is discussed to what requires the face-to-face time in order to make
> >progress on.
> >
> >For active draft editors, please let us know via this list or
> >aqm-chairs@tools.ietf.org what you think your meeting time needs are,
> >so we can put together an agenda.  If you don't need meeting time now,
> >or would like to use an interim telecon to assist in gathering
> >feedback, please also let us know.
> >
> >For others, please read the drafts, comment on this mailing list, and
> >help us to review and complete them:
> >https://datatracker.ietf.org/wg/aqm/documents/
> >
> >Thanks in advance!
> >
> >--
> >Wes Eddy
> >MTI Systems
> >
> >_______________________________________________
> >aqm mailing list
> >aqm@ietf.org
> >https://www.ietf.org/mailman/listinfo/aqm


From nobody Thu Feb 26 11:44:26 2015
Return-Path: <dhavey@yahoo.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F70F1A1B85 for <aqm@ietfa.amsl.com>; Thu, 26 Feb 2015 11:44:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.59
X-Spam-Level: ***
X-Spam-Status: No, score=3.59 tagged_above=-999 required=5 tests=[BAYES_99=3.5, BAYES_999=0.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 pmjSpHXhGUyO for <aqm@ietfa.amsl.com>; Thu, 26 Feb 2015 11:44:23 -0800 (PST)
Received: from nm29-vm1.bullet.mail.bf1.yahoo.com (nm29-vm1.bullet.mail.bf1.yahoo.com [98.139.213.144]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 802EA1A1BB1 for <aqm@ietf.org>; Thu, 26 Feb 2015 11:44:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1424979860; bh=f9nuNhesCnqjus7wOFkOPBi0dqAYAT64K8NYFL2k6bg=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=a3JtPjmZgEre8SHcnVu7s/7O+x2K/8UwwNoICJWhJqceju7t0srFmPB9gGGbCDYa2T2i+Lm45DpqxdCWKOPt3Q5zbL8T0c8xEG0u+bohj/7J2qpQysaqGXBjfLUbzEKz1g1eKyUE6tsK9dSGqO9eBBHNNUw+CTxBdmRG7vHw8SuQlqaU++ku6mREl5zjNkABlgIEP5z2jPz2iM/jNU7CUgwlHTEQFu80FfnSKD4OZxEDkPFN/37mzAAvDkXN+7In6f/IaD4SXAru5fKxpzDrFAhC/1/eaQckvSUl+bMJWmRIcHJDbyQzQBVLkuJnM0jbGzIaW4Hzn3+k7Ip58E0tJg==
Received: from [66.196.81.174] by nm29.bullet.mail.bf1.yahoo.com with NNFMP; 26 Feb 2015 19:44:20 -0000
Received: from [98.139.212.215] by tm20.bullet.mail.bf1.yahoo.com with NNFMP;  26 Feb 2015 19:44:20 -0000
Received: from [127.0.0.1] by omp1024.mail.bf1.yahoo.com with NNFMP; 26 Feb 2015 19:44:20 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 11340.13543.bm@omp1024.mail.bf1.yahoo.com
X-YMail-OSG: ehO3blsVM1kFhbDQeDKvGLREPY_evCiu_2mU_AHJXCZpAyev9JK7wGMKpCsK8Vl F76N6.uFS8pmFxC1UQtTkS5EtI3KiAARnwjh1owWMcoE_6a6XvNXSuzQg.GDqgX6w3UAI0vmrEtK 1oNJjmEJ4qZSZbOdvQl6nzrm2lNah21PQ02iW3kdTpQotKBY34OF8u40W4e9T33reZC4Vqc7myQh 48KVFE3Y9hzA2R0uWomhFxsfkXN20Nrotx1LOhsQpxmy3Shtqd.qbVQPfBiwjfJpfV4L0eZujaKY ZIkEzgr56ee3yLRyYlq_Q6pNCqlcU9k.6xUltWMLqKzaaRzmkSJUMPN6v2fIjURI_pptJof_7CFi F0K.0qfy0Ezyo1GWtpEwXP2PiOXSmmYbvK_BETGz5KLDJ_OfXfJnw6efPtJe3SgFxsAA4fUbM20f zqdABFrgiZ6bbxcr2yUEtYjU.58NlsvfBfhiVDr1Iy.Vv4eYwgQzOSvqAQherQpXWmwZkyvP5bHm z7O6sl6tMWTUpwSEWd3403A--
Received: by 76.13.26.142; Thu, 26 Feb 2015 19:44:19 +0000 
Date: Thu, 26 Feb 2015 19:44:18 +0000 (UTC)
From: Daniel Havey <dhavey@yahoo.com>
To: "aqm@ietf.org" <aqm@ietf.org>
Message-ID: <2134947047.1078309.1424979858723.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <87k2z5ot7w.fsf@toke.dk>
References: <87k2z5ot7w.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/C2GNqJi_ZlqEAzHq4OpD0c7fL8o>
Subject: [aqm] Is bufferbloat a real problem?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Daniel Havey <dhavey@yahoo.com>
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: <http://www.ietf.org/mail-archive/web/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, 26 Feb 2015 19:44:24 -0000

I know that this question is a bit ridiculous in this community.  Of course bufferbloat is a real problem.  However, it would be nice to formally address the question and I think this community is the right place to do so.

Does anybody have a measurement study?  I have some stuff from the FCC Measuring Broadband in America studies, but, that doesn't address bufferbloat directly.

Let me repeat for clarity.  I don't need to be convinced.  I need evidence that I can use to convince my committee.

...Daniel


From nobody Fri Feb 27 10:52:55 2015
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 873241AD0BA for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 10:52:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.788
X-Spam-Level: 
X-Spam-Status: No, score=0.788 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 aJAKuLSHrbDe for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 10:52:51 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 6C8C11A911D for <aqm@ietf.org>; Fri, 27 Feb 2015 10:52:51 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t1RIqekh018253; Fri, 27 Feb 2015 13:52:40 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201502271852.t1RIqekh018253@maildrop31.somerville.occnc.com>
To: Daniel Havey <dhavey@yahoo.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Thu, 26 Feb 2015 19:44:18 +0000." <2134947047.1078309.1424979858723.JavaMail.yahoo@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18251.1425063159.1@harbor31.somerville.occnc.com>
Date: Fri, 27 Feb 2015 13:52:39 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/SDzXNovqdFD7WOWznBUiEPjiCHs>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] Is bufferbloat a real problem?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
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: <http://www.ietf.org/mail-archive/web/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: Fri, 27 Feb 2015 18:52:54 -0000

In message <2134947047.1078309.1424979858723.JavaMail.yahoo@mail.yahoo.com>
Daniel Havey writes:
 
>  
> I know that this question is a bit ridiculous in this community.  Of
> course bufferbloat is a real problem.  However, it would be nice to
> formally address the question and I think this community is the right
> place to do so.
>  
> Does anybody have a measurement study?  I have some stuff from the FCC
> Measuring Broadband in America studies, but, that doesn't address
> bufferbloat directly.
>  
> Let me repeat for clarity.  I don't need to be convinced.  I need
> evidence that I can use to convince my committee.
>  
> ...Daniel
>  
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm


Daniel,

You are convinced.  So am I but we need to temper the message to avoid
going too far in the opposite direction - too little buffer.

If you are not interested in the details, just skip to the last
paragraph.

Bufferbloat should in principle only be a problem for interactive
realtime traffic.  Interactive means two way or multiway.  This is
SIP, Skype, audio and video conferencing, etc.  In practice it is also
bad for TCP flows with short RTT and max window set small.

One way realtime (such as streaming audio and video) should be
unnafected by all but huge bufferbloat.  That is should be.  For
example, youtube video is carried over TCP and is typically either way
ahead of the playback or choppy (inadequate aggregate bandwidth or
marigninal and/or big drop with TCP stall).  It would be nice if
marginal aggregate bandwidth was dealt with by switching to a lower
bandwidth encoding, but too often this is not the case.  This doesn't
mean that some streaming formats don't manage to get this wrong and
end up delay sensitive.

TCP needs buffering to function correctly.  Huge bufferbloat is bad
for TCP, particularly for small transfers that never get out of TCP
slow start and for short RTT flows.  For long RTT flows too little
buffer causes problems.

[ aside: For example, if TCP starts with 4 segments at 1K segment
size, it will take 4 RTT to hit 64KB window, the typical max window
without TCP large window (TCPLW) option.  During that time, 60KB will
be sent.  After that 64KB will be sent each RTT.  With geographic RTT
is 70 msec (approximate US continental RTT due to finite speed of
light in fiber and fiber distance), 60 KB is sent in the first 280
msec and 64KB gets sent every 70 msec yielding 7 mb/s.  OTOH if there
is a server 2 msec RTT away (1 msec one way is 125mi = 200km), then
60KB in first 8 msec and 256 Mb/s after that.  If there is 100 msec
buffer at a bottleneck, then this low RTT TCP flow will be slowed by a
factor of 50.  OTOH, if bottlenecks have a lot less than 1 RTT of
buffer, then the long TCP flows will get even further slowed. ]

One of the effects of some buffer, but not excessive, is short RTT
flows which given the no-TCPLW max window get slowed down while longer
RTT are less affected.  This becomes more fair wrt to transfer rates
among TCP flows.  The same holds true if TCPLW gets turned on in
commodity gadgets and the commonly deploed max window increases, but
the number change.

If the buffer grows a little and the deployed window sizes become the
limiting factor, then this is very light congestion with delay but
absolutely zero loss due to queue drops (not considering AQM for the
moment).

Some uses of TCP increase the window to work better over long RTT.  It
takes a bit longer to hit the max window but the rate once it has been
hit is greater.  Setting TCP window large on short RTT flows is
counterproductive since one or a small number of flows can cause a
bottleneck on a slow provider link (ie: 10-100 Mb/s range typical of
home use).  On a LAN RTT can be well under 1 msec on Ethernet and
highly variable on WiFi.  On WiFi larger window can contribute to some
real trouble.  So best that the default window be changed.  

[ Note that the work on automatic sizing of tcp_sndbuf and scp_recvbuf
may create a tendency to saturate links as the window can go up to 2MB
with default parameters.  Has this hit consumer devices yet?  This
could be bad it this rolls out before widespread use of AQM. ]

When a small amount of loss occurs, such as one or much less than the
current window size, TCP cuts the current window size in half and
retransmits the packet for the window in flight (ignoring selective
acknowledgment extension aka SACK for the moment).

If the buffer is way too small, then a large amount of premature drop
occurs when the buffer limit is hit.  Lots of TCP flows slow down.
The long RTT flows slow down the most.  Some retransmission occurs
(which doesn't help congestion).  If there is a long period of drop
relative to a short RTT, then a entire window can be dropped and this
is terrible for TCP (slow start is initiated after delay based on an
estimate of RTT and RTT stdev, or 3 sec if RTT estimate is stale -
this is a TCP stall).  So with too little buffer some TCP flows get
hammered and stall.  TCP flows with long RTT tend to stall less but
are more sensitve to the frequency of drop events and can get
extremely slow due to successively cutting window in half and then
growing the window linearly rather than exponentially.

With tiny buffers really bad things tend to happen.  The rate of
retransmission can drive goodput (the amount of non-retransmit traffic
per time) can drop substantially.  Long RTT flows can become
hopelessly slow.  Stalls become more common.  In the worst case (which
has been observed in a ISP network during a tiny buffer experiment
about a decade ago, details in private email) TCP synchronization can
occur, and utilization and goodput drop dramatically.

A moderate amount of buffer is good for all TCP.  A large buffer is
good for long RTT TCP flows, particularly those that have increased
max window.  As mentioned before, any but a very small buffer is bad
for interactive real time applications.

Enter AQM.  A large buffer can be used but with a lower target delay
and some form of AQM to introduce a low rate of isolated drops as
needed to slow the senders.  Avoiding queue tail drop events where a
lot of drops occur over an interval lowers the amount of
retransmission and avoids stalls.  Long RTT flows tend to get
penalized the most.

Fairness is not great with a single queue and AQM but this is much
better than a single queue with either small or large buffer and tail
drop.  Fairness is greatly improved with some form of FQ or SFQ.

Ideally with FQ each flow would get its own queue.  In practice this
is not the case but the situation is greatly improved.  A real time
flow, which is inherently rate limited, would see minimal delay and no
loss.  A short RTT flow would see a moderate increase in delay and a
low level of loss (ie: typically much less than 1%) enough to slow it
down enough to avoid congestion.  a long RTT flow would see a moderate
increase in delay and no loss if still running slower than the small
RTT flows.  This does wonders for fairness and provides the best
possible service for each service type.

In practice, some FQ or SFQ queues have a mix of real time, low RTT
TCP, and high RTT TCP.  If any such queue is taking a smaller share
than other queues, delay is low and loss is low or zero.  If such a
queue is taking more than its share, then the situation is similar to
the single queue case.  Less flows end up in such a queue.  Cascaded
queues have been proposed and in some cases (no longer existing) have
been implemented.  In a cascaded SFQ scheme, the queues taking more
than their share are further subdivied.  Repeat the subdivision a few
times and you can end up with the large bandwidth contributors in
their own queue and getting a fair share of capacity.

So excuse the length of this but solving bufferbloat is *not* a silver
bullet.  Not understanding that point and just making buffers really
small could result in an even worse situation than we have now.

Curtis

ps - Some aspects of this may not reflect WG direction.  IMHO- the
down sides of just making buffers smaller and/or setting low delay
targets may not be getting enough (or any) attention in the WG.  Maybe
discussion wouldn't hurt.


From nobody Fri Feb 27 11:09:45 2015
Return-Path: <dhavey@yahoo.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 392F21AD0B1 for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 11:09:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.61
X-Spam-Level: 
X-Spam-Status: No, score=-0.61 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 0atvjLIv_BJG for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 11:09:40 -0800 (PST)
Received: from nm44-vm7.bullet.mail.bf1.yahoo.com (nm44-vm7.bullet.mail.bf1.yahoo.com [216.109.115.31]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 471371A90C6 for <aqm@ietf.org>; Fri, 27 Feb 2015 11:09:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1425064179; bh=2tqBpDZ/FhHjEiBBmbw9V0YeJfLxyCZvmrp2X7grj78=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=Ls3gqaJJ6LQ0dXqylTIzGYxf2YnYUflVIZ8uiHVOp0pYKcnYNq5Zds/a/CecVdracxJ/l8abmwtT5Bnwwp+TkqykWgx3LFvX5Qb+qKZObFiDbXKtWA021o941XsEccuihO3No9hKX82Fk+3IIF7ojKgP9cduqDVSfuD/GKAPXryJywJ4F2ucgtY9Jq5alYMGbq137pgAGnJ/jXu05bMB3+LJ1u3xnOnWa3KUniXmDWSQ1zc9pqqR1T7+1hmbUXu3Olmhn5R/xbpiGnv0HkpbD1CEcOIpgJpvrV94p52dDNYXK8v3X8nM3qtti3KjO0PsIdbCGmWNBwsG5OHguPaJNA==
Received: from [98.139.214.32] by nm44.bullet.mail.bf1.yahoo.com with NNFMP; 27 Feb 2015 19:09:39 -0000
Received: from [98.139.215.253] by tm15.bullet.mail.bf1.yahoo.com with NNFMP;  27 Feb 2015 19:09:39 -0000
Received: from [127.0.0.1] by omp1066.mail.bf1.yahoo.com with NNFMP; 27 Feb 2015 19:09:39 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 399191.28383.bm@omp1066.mail.bf1.yahoo.com
X-YMail-OSG: h42H1.YVM1ndy3v021dBfr8Ow2wCaXInyLxRSJgArdQLOYBaqu5n3hoiLwTvM2I 4Did6zk9.7xjtPuAkjjNlhqUzOQDrQ4mm9MKDxKpC6tRRdD0Vw.7mcmDQ0nd2NvME0k_SrbuxpDu gv.akv74z0anLOy0cNVsj_RUSD5ak0Q9t_J1izPq1QuCU7d8GHFLbUp2hVWlOpmpRIY_fBEYHLza blfUoVLdO04NAMVwxrLZZCm9LmPWBbB58cUZfMi_XTr.OPKfvyjvaDnr224.qpKl7mrE0o_HemQv yZnUjG0Ef9aXvC55okauNtV9CGoMIklOsPnSFgkFUUoS1.y9.9ythva8ufVxwAn7Z8XcBxAX6VPu z0pm8mJtZiBmOVNM3Ck6EzStQpf2ulCDv44CVPbs_MYfBgHLMI3KN0x1Dx2cXhnbbLnuxpd_kXWg NAc7KH3w6OfQdtBlGVj_FLCmEBgPXGjMrAoJeHeShYewCCsQndd9iCekfEZ1RZolPS7M5hTTQJ2L .BeBCQh_8_v8BfnAywJpOZWvYe28b
Received: by 66.196.81.118; Fri, 27 Feb 2015 19:09:38 +0000 
Date: Fri, 27 Feb 2015 19:09:37 +0000 (UTC)
From: Daniel Havey <dhavey@yahoo.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Message-ID: <1276981593.2139890.1425064177824.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <201502271852.t1RIqekh018253@maildrop31.somerville.occnc.com>
References: <201502271852.t1RIqekh018253@maildrop31.somerville.occnc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/-BQC-koeqE9_JMHgTUxvuO1l-_Y>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] Is bufferbloat a real problem?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Daniel Havey <dhavey@yahoo.com>
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: <http://www.ietf.org/mail-archive/web/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: Fri, 27 Feb 2015 19:09:43 -0000

Have to hop on a plane soon.  But yes and yes!  I think you are talking about the queue sizing problem as I like to call it instead of bufferbloat.  I have some work in that direction in my dissertation defense that I am about to give.

However, I also have an exigent problem.  In that same defense I will undoubtedly be asked, "Do you have evidence to prove that queue sizing is a significant problem?"

The fact is that I do not.  I have a train of logic that indicates the problem is significant, but, that is not the same as a study.  Isn't there something from cablelabs?

Eeeeeeerrrrrrrgggggghhhhhh!  I am glad I will only have to defend once in my lifetime.

...Daniel

________________________________
From: Curtis Villamizar <curtis@ipv6.occnc.com>
To: Daniel Havey <dhavey@yahoo.com> 
Cc: "aqm@ietf.org" <aqm@ietf.org> 
Sent: Friday, February 27, 2015 10:52 AM
Subject: Re: [aqm] Is bufferbloat a real problem?


In message <2134947047.1078309.1424979858723.JavaMail.yahoo@mail.yahoo.com>
Daniel Havey writes:

>  
> I know that this question is a bit ridiculous in this community.  Of
> course bufferbloat is a real problem.  However, it would be nice to
> formally address the question and I think this community is the right
> place to do so.
>  
> Does anybody have a measurement study?  I have some stuff from the FCC
> Measuring Broadband in America studies, but, that doesn't address
> bufferbloat directly.
>  
> Let me repeat for clarity.  I don't need to be convinced.  I need
> evidence that I can use to convince my committee.
>  
> ...Daniel
>  
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm


Daniel,

You are convinced.  So am I but we need to temper the message to avoid
going too far in the opposite direction - too little buffer.

If you are not interested in the details, just skip to the last
paragraph.

Bufferbloat should in principle only be a problem for interactive
realtime traffic.  Interactive means two way or multiway.  This is
SIP, Skype, audio and video conferencing, etc.  In practice it is also
bad for TCP flows with short RTT and max window set small.

One way realtime (such as streaming audio and video) should be
unnafected by all but huge bufferbloat.  That is should be.  For
example, youtube video is carried over TCP and is typically either way
ahead of the playback or choppy (inadequate aggregate bandwidth or
marigninal and/or big drop with TCP stall).  It would be nice if
marginal aggregate bandwidth was dealt with by switching to a lower
bandwidth encoding, but too often this is not the case.  This doesn't
mean that some streaming formats don't manage to get this wrong and
end up delay sensitive.

TCP needs buffering to function correctly.  Huge bufferbloat is bad
for TCP, particularly for small transfers that never get out of TCP
slow start and for short RTT flows.  For long RTT flows too little
buffer causes problems.

[ aside: For example, if TCP starts with 4 segments at 1K segment
size, it will take 4 RTT to hit 64KB window, the typical max window
without TCP large window (TCPLW) option.  During that time, 60KB will
be sent.  After that 64KB will be sent each RTT.  With geographic RTT
is 70 msec (approximate US continental RTT due to finite speed of
light in fiber and fiber distance), 60 KB is sent in the first 280
msec and 64KB gets sent every 70 msec yielding 7 mb/s.  OTOH if there
is a server 2 msec RTT away (1 msec one way is 125mi = 200km), then
60KB in first 8 msec and 256 Mb/s after that.  If there is 100 msec
buffer at a bottleneck, then this low RTT TCP flow will be slowed by a
factor of 50.  OTOH, if bottlenecks have a lot less than 1 RTT of
buffer, then the long TCP flows will get even further slowed. ]

One of the effects of some buffer, but not excessive, is short RTT
flows which given the no-TCPLW max window get slowed down while longer
RTT are less affected.  This becomes more fair wrt to transfer rates
among TCP flows.  The same holds true if TCPLW gets turned on in
commodity gadgets and the commonly deploed max window increases, but
the number change.

If the buffer grows a little and the deployed window sizes become the
limiting factor, then this is very light congestion with delay but
absolutely zero loss due to queue drops (not considering AQM for the
moment).

Some uses of TCP increase the window to work better over long RTT.  It
takes a bit longer to hit the max window but the rate once it has been
hit is greater.  Setting TCP window large on short RTT flows is
counterproductive since one or a small number of flows can cause a
bottleneck on a slow provider link (ie: 10-100 Mb/s range typical of
home use).  On a LAN RTT can be well under 1 msec on Ethernet and
highly variable on WiFi.  On WiFi larger window can contribute to some
real trouble.  So best that the default window be changed.  

[ Note that the work on automatic sizing of tcp_sndbuf and scp_recvbuf
may create a tendency to saturate links as the window can go up to 2MB
with default parameters.  Has this hit consumer devices yet?  This
could be bad it this rolls out before widespread use of AQM. ]

When a small amount of loss occurs, such as one or much less than the
current window size, TCP cuts the current window size in half and
retransmits the packet for the window in flight (ignoring selective
acknowledgment extension aka SACK for the moment).

If the buffer is way too small, then a large amount of premature drop
occurs when the buffer limit is hit.  Lots of TCP flows slow down.
The long RTT flows slow down the most.  Some retransmission occurs
(which doesn't help congestion).  If there is a long period of drop
relative to a short RTT, then a entire window can be dropped and this
is terrible for TCP (slow start is initiated after delay based on an
estimate of RTT and RTT stdev, or 3 sec if RTT estimate is stale -
this is a TCP stall).  So with too little buffer some TCP flows get
hammered and stall.  TCP flows with long RTT tend to stall less but
are more sensitve to the frequency of drop events and can get
extremely slow due to successively cutting window in half and then
growing the window linearly rather than exponentially.

With tiny buffers really bad things tend to happen.  The rate of
retransmission can drive goodput (the amount of non-retransmit traffic
per time) can drop substantially.  Long RTT flows can become
hopelessly slow.  Stalls become more common.  In the worst case (which
has been observed in a ISP network during a tiny buffer experiment
about a decade ago, details in private email) TCP synchronization can
occur, and utilization and goodput drop dramatically.

A moderate amount of buffer is good for all TCP.  A large buffer is
good for long RTT TCP flows, particularly those that have increased
max window.  As mentioned before, any but a very small buffer is bad
for interactive real time applications.

Enter AQM.  A large buffer can be used but with a lower target delay
and some form of AQM to introduce a low rate of isolated drops as
needed to slow the senders.  Avoiding queue tail drop events where a
lot of drops occur over an interval lowers the amount of
retransmission and avoids stalls.  Long RTT flows tend to get
penalized the most.

Fairness is not great with a single queue and AQM but this is much
better than a single queue with either small or large buffer and tail
drop.  Fairness is greatly improved with some form of FQ or SFQ.

Ideally with FQ each flow would get its own queue.  In practice this
is not the case but the situation is greatly improved.  A real time
flow, which is inherently rate limited, would see minimal delay and no
loss.  A short RTT flow would see a moderate increase in delay and a
low level of loss (ie: typically much less than 1%) enough to slow it
down enough to avoid congestion.  a long RTT flow would see a moderate
increase in delay and no loss if still running slower than the small
RTT flows.  This does wonders for fairness and provides the best
possible service for each service type.

In practice, some FQ or SFQ queues have a mix of real time, low RTT
TCP, and high RTT TCP.  If any such queue is taking a smaller share
than other queues, delay is low and loss is low or zero.  If such a
queue is taking more than its share, then the situation is similar to
the single queue case.  Less flows end up in such a queue.  Cascaded
queues have been proposed and in some cases (no longer existing) have
been implemented.  In a cascaded SFQ scheme, the queues taking more
than their share are further subdivied.  Repeat the subdivision a few
times and you can end up with the large bandwidth contributors in
their own queue and getting a fair share of capacity.

So excuse the length of this but solving bufferbloat is *not* a silver
bullet.  Not understanding that point and just making buffers really
small could result in an even worse situation than we have now.

Curtis

ps - Some aspects of this may not reflect WG direction.  IMHO- the
down sides of just making buffers smaller and/or setting low delay
targets may not be getting enough (or any) attention in the WG.  Maybe
discussion wouldn't hurt.

_______________________________________________
aqm mailing list
aqm@ietf.org
https://www.ietf.org/mailman/listinfo/aqm


From dhavey@gmail.com  Fri Feb 27 11:29:06 2015
Return-Path: <dhavey@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C5511AC3CE for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 11:29:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 5YxDUtZ1NGpv for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 11:29:00 -0800 (PST)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB1CE1AC3D0 for <aqm@ietf.org>; Fri, 27 Feb 2015 11:28:59 -0800 (PST)
Received: by mail-qg0-f50.google.com with SMTP id e89so15808720qgf.9 for <aqm@ietf.org>; Fri, 27 Feb 2015 11:28:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=01jrgYFt8pq4KOhVouJdbgAJOgMHi+vJmly12dVPs5Y=; b=P8n5n5wFKVh+4BE5gvk4PGCOfMkQ0eEezI8hgFapIF0IdvXs5Fme9UwJOopy8wLkGv XXqjJDA0Ui87FhhhlW+KVKDGR+zBrmr1ZWMDOF35qghO9CkxojkbOKHN3B3FK5oc+TNv gYp/QlaAxMvswP0xxorlbrW0p0gxCoEJFTKn3Uwo1l0uhO3KVAUt1kIKLYtWqPdquFtM AKWJfk9jF0X07aaLgeUtvvgxYIn2cmlgM/e8tFF7fhoISRihxJsvlIn8qZqIjvAgxtOd +Ja/uSSY9uBsaEANAP7JV/OIY8dRT/1R01DOTzezv3vgVjnhp6bViW05vTMEpyG46KZ9 tmVQ==
MIME-Version: 1.0
X-Received: by 10.140.31.246 with SMTP id f109mr30260059qgf.23.1425065338912;  Fri, 27 Feb 2015 11:28:58 -0800 (PST)
Received: by 10.140.104.102 with HTTP; Fri, 27 Feb 2015 11:28:58 -0800 (PST)
In-Reply-To: <201502271852.t1RIqekh018253@maildrop31.somerville.occnc.com>
References: <2134947047.1078309.1424979858723.JavaMail.yahoo@mail.yahoo.com> <201502271852.t1RIqekh018253@maildrop31.somerville.occnc.com>
Date: Fri, 27 Feb 2015 11:28:58 -0800
Message-ID: <CAO1c0ARbAt4H5AupHMSa7ziL6JZXJEw-kxbua2xz3QAHt4UgiA@mail.gmail.com>
From: Daniel Havey <dhavey@gmail.com>
To: curtis@ipv6.occnc.com
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/BZYHYEiN4tgCqxz5meE1f552Sgw>
Cc: "aqm@ietf.org" <aqm@ietf.org>, Daniel Havey <dhavey@yahoo.com>
Subject: Re: [aqm] Is bufferbloat a real problem?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 27 Feb 2015 19:30:16 -0000

Switching to gmail because Yahoo is too horrible to use.

Like I said, I agree that bufferbloat is only 1 part of a two sided
problem.  The queue with respect to each flow can be either two large
or too small (and sometimes just right?).  Anyways, I'm just wondering
if there are any measurement studies out there that show the effects
of this problem in a formal way.

It might be an impossible problem.  What provider is going to want to
help publish data that shows they have poor queue sizing?  Anyways,
I'm looking for a way to demonstrate that this is a real problem in a
dissertation defense.  Perhaps when asked the question I should just
launch into a long explanation about how the queue can be too small or
too large or even both if there are multiple flows in the queue and
that solving the problem requires more than just shortening the queues
or using AQM to tune them to a particular RTT?  I dunno.

It would be nice if we had some measurement studies, but, that might
not be possible given the realities that we face on the Internet
today.

...Daniel





On Fri, Feb 27, 2015 at 10:52 AM, Curtis Villamizar
<curtis@ipv6.occnc.com> wrote:
> In message <2134947047.1078309.1424979858723.JavaMail.yahoo@mail.yahoo.com>
> Daniel Havey writes:
>
>>
>> I know that this question is a bit ridiculous in this community.  Of
>> course bufferbloat is a real problem.  However, it would be nice to
>> formally address the question and I think this community is the right
>> place to do so.
>>
>> Does anybody have a measurement study?  I have some stuff from the FCC
>> Measuring Broadband in America studies, but, that doesn't address
>> bufferbloat directly.
>>
>> Let me repeat for clarity.  I don't need to be convinced.  I need
>> evidence that I can use to convince my committee.
>>
>> ...Daniel
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>
>
> Daniel,
>
> You are convinced.  So am I but we need to temper the message to avoid
> going too far in the opposite direction - too little buffer.
>
> If you are not interested in the details, just skip to the last
> paragraph.
>
> Bufferbloat should in principle only be a problem for interactive
> realtime traffic.  Interactive means two way or multiway.  This is
> SIP, Skype, audio and video conferencing, etc.  In practice it is also
> bad for TCP flows with short RTT and max window set small.
>
> One way realtime (such as streaming audio and video) should be
> unnafected by all but huge bufferbloat.  That is should be.  For
> example, youtube video is carried over TCP and is typically either way
> ahead of the playback or choppy (inadequate aggregate bandwidth or
> marigninal and/or big drop with TCP stall).  It would be nice if
> marginal aggregate bandwidth was dealt with by switching to a lower
> bandwidth encoding, but too often this is not the case.  This doesn't
> mean that some streaming formats don't manage to get this wrong and
> end up delay sensitive.
>
> TCP needs buffering to function correctly.  Huge bufferbloat is bad
> for TCP, particularly for small transfers that never get out of TCP
> slow start and for short RTT flows.  For long RTT flows too little
> buffer causes problems.
>
> [ aside: For example, if TCP starts with 4 segments at 1K segment
> size, it will take 4 RTT to hit 64KB window, the typical max window
> without TCP large window (TCPLW) option.  During that time, 60KB will
> be sent.  After that 64KB will be sent each RTT.  With geographic RTT
> is 70 msec (approximate US continental RTT due to finite speed of
> light in fiber and fiber distance), 60 KB is sent in the first 280
> msec and 64KB gets sent every 70 msec yielding 7 mb/s.  OTOH if there
> is a server 2 msec RTT away (1 msec one way is 125mi = 200km), then
> 60KB in first 8 msec and 256 Mb/s after that.  If there is 100 msec
> buffer at a bottleneck, then this low RTT TCP flow will be slowed by a
> factor of 50.  OTOH, if bottlenecks have a lot less than 1 RTT of
> buffer, then the long TCP flows will get even further slowed. ]
>
> One of the effects of some buffer, but not excessive, is short RTT
> flows which given the no-TCPLW max window get slowed down while longer
> RTT are less affected.  This becomes more fair wrt to transfer rates
> among TCP flows.  The same holds true if TCPLW gets turned on in
> commodity gadgets and the commonly deploed max window increases, but
> the number change.
>
> If the buffer grows a little and the deployed window sizes become the
> limiting factor, then this is very light congestion with delay but
> absolutely zero loss due to queue drops (not considering AQM for the
> moment).
>
> Some uses of TCP increase the window to work better over long RTT.  It
> takes a bit longer to hit the max window but the rate once it has been
> hit is greater.  Setting TCP window large on short RTT flows is
> counterproductive since one or a small number of flows can cause a
> bottleneck on a slow provider link (ie: 10-100 Mb/s range typical of
> home use).  On a LAN RTT can be well under 1 msec on Ethernet and
> highly variable on WiFi.  On WiFi larger window can contribute to some
> real trouble.  So best that the default window be changed.
>
> [ Note that the work on automatic sizing of tcp_sndbuf and scp_recvbuf
> may create a tendency to saturate links as the window can go up to 2MB
> with default parameters.  Has this hit consumer devices yet?  This
> could be bad it this rolls out before widespread use of AQM. ]
>
> When a small amount of loss occurs, such as one or much less than the
> current window size, TCP cuts the current window size in half and
> retransmits the packet for the window in flight (ignoring selective
> acknowledgment extension aka SACK for the moment).
>
> If the buffer is way too small, then a large amount of premature drop
> occurs when the buffer limit is hit.  Lots of TCP flows slow down.
> The long RTT flows slow down the most.  Some retransmission occurs
> (which doesn't help congestion).  If there is a long period of drop
> relative to a short RTT, then a entire window can be dropped and this
> is terrible for TCP (slow start is initiated after delay based on an
> estimate of RTT and RTT stdev, or 3 sec if RTT estimate is stale -
> this is a TCP stall).  So with too little buffer some TCP flows get
> hammered and stall.  TCP flows with long RTT tend to stall less but
> are more sensitve to the frequency of drop events and can get
> extremely slow due to successively cutting window in half and then
> growing the window linearly rather than exponentially.
>
> With tiny buffers really bad things tend to happen.  The rate of
> retransmission can drive goodput (the amount of non-retransmit traffic
> per time) can drop substantially.  Long RTT flows can become
> hopelessly slow.  Stalls become more common.  In the worst case (which
> has been observed in a ISP network during a tiny buffer experiment
> about a decade ago, details in private email) TCP synchronization can
> occur, and utilization and goodput drop dramatically.
>
> A moderate amount of buffer is good for all TCP.  A large buffer is
> good for long RTT TCP flows, particularly those that have increased
> max window.  As mentioned before, any but a very small buffer is bad
> for interactive real time applications.
>
> Enter AQM.  A large buffer can be used but with a lower target delay
> and some form of AQM to introduce a low rate of isolated drops as
> needed to slow the senders.  Avoiding queue tail drop events where a
> lot of drops occur over an interval lowers the amount of
> retransmission and avoids stalls.  Long RTT flows tend to get
> penalized the most.
>
> Fairness is not great with a single queue and AQM but this is much
> better than a single queue with either small or large buffer and tail
> drop.  Fairness is greatly improved with some form of FQ or SFQ.
>
> Ideally with FQ each flow would get its own queue.  In practice this
> is not the case but the situation is greatly improved.  A real time
> flow, which is inherently rate limited, would see minimal delay and no
> loss.  A short RTT flow would see a moderate increase in delay and a
> low level of loss (ie: typically much less than 1%) enough to slow it
> down enough to avoid congestion.  a long RTT flow would see a moderate
> increase in delay and no loss if still running slower than the small
> RTT flows.  This does wonders for fairness and provides the best
> possible service for each service type.
>
> In practice, some FQ or SFQ queues have a mix of real time, low RTT
> TCP, and high RTT TCP.  If any such queue is taking a smaller share
> than other queues, delay is low and loss is low or zero.  If such a
> queue is taking more than its share, then the situation is similar to
> the single queue case.  Less flows end up in such a queue.  Cascaded
> queues have been proposed and in some cases (no longer existing) have
> been implemented.  In a cascaded SFQ scheme, the queues taking more
> than their share are further subdivied.  Repeat the subdivision a few
> times and you can end up with the large bandwidth contributors in
> their own queue and getting a fair share of capacity.
>
> So excuse the length of this but solving bufferbloat is *not* a silver
> bullet.  Not understanding that point and just making buffers really
> small could result in an even worse situation than we have now.
>
> Curtis
>
> ps - Some aspects of this may not reflect WG direction.  IMHO- the
> down sides of just making buffers smaller and/or setting low delay
> targets may not be getting enough (or any) attention in the WG.  Maybe
> discussion wouldn't hurt.
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm


From nobody Fri Feb 27 12:06:33 2015
Return-Path: <dpreed@reed.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F3CC1A0058 for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 12:06:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level: 
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
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 G--aaFIFknr9 for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 12:06:31 -0800 (PST)
Received: from smtp102.iad3a.emailsrvr.com (smtp102.iad3a.emailsrvr.com [173.203.187.102]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C916A1A0053 for <aqm@ietf.org>; Fri, 27 Feb 2015 12:06:30 -0800 (PST)
Received: from smtp13.relay.iad3a.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp13.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 153581001B6 for <aqm@ietf.org>; Fri, 27 Feb 2015 15:06:30 -0500 (EST)
Received: from app55.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by smtp13.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id F2D0D1003AD for <aqm@ietf.org>; Fri, 27 Feb 2015 15:06:29 -0500 (EST)
X-Sender-Id: dpreed@reed.com
Received: from app55.wa-webapps.iad3a (relay-webapps.rsapps.net [172.27.255.140]) by 0.0.0.0:25 (trex/5.4.2); Fri, 27 Feb 2015 20:06:30 GMT
Received: from reed.com (localhost.localdomain [127.0.0.1]) by app55.wa-webapps.iad3a (Postfix) with ESMTP id DD19B80069; Fri, 27 Feb 2015 15:06:29 -0500 (EST)
Received: by apps.rackspace.com (Authenticated sender: dpreed@reed.com, from: dpreed@reed.com)  with HTTP; Fri, 27 Feb 2015 15:06:29 -0500 (EST)
Date: Fri, 27 Feb 2015 15:06:29 -0500 (EST)
From: dpreed@reed.com
To: aqm@ietf.org
Cc: aqm@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Importance: Normal
X-Priority: 3 (Normal)
X-Type: plain
In-Reply-To: <mailman.1502.1425065417.2864.aqm@ietf.org>
References: <mailman.1502.1425065417.2864.aqm@ietf.org>
X-Auth-ID: dpreed@reed.com
Message-ID: <1425067589.903626768@apps.rackspace.com>
X-Mailer: webmail/11.3.13-RC
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/fDliWzdGvMQG-91hsrNsalx2er4>
Subject: Re: [aqm] aqm Digest, Vol 24, Issue 18
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 27 Feb 2015 20:06:33 -0000

Having done many experiments in many locations, I can tell you it is a real=
 problem and a severe problem, in the real world.=0A=0AI can observe it eve=
ry time I fly from Boston to San Jose and back (which I do once per month).=
  If you use Gogo (the provider that supports several airlines' network acc=
ess), all you need to do is measure either the uplink or downlink queue, an=
d you find the typical symptom: a buffer that has multiple seconds of backl=
og, and no packet loss whatsoever (using either ICMP or UDP).  That's prett=
y severe - what it means is that the probability that "ssh" times out is no=
n zero, not because of lost packets or lost carrier, but because of the def=
ault timeout in ssh being exceeded.=0A=0ANow why is this a serious problem?=
  Well, think about it.  If packets sit in queues for 4 seconds, what impac=
t does that have on people using HTTP?  Well, they think a website is down,=
 so within a couple of seconds, they switch to surfing some other web site.=
  Meanwhile, the downloaded packets (pictures or whatever, which are in tra=
nsit because of a relatively long TCP window that has built up in HTTP 1.1/=
TCP/IP, which supports all consecutive HTTP requests to the same server, be=
cause the service was temporarily OK), are filling up the download queue - =
even though the user(s) have moved on and probably even closed their connec=
tions on their end).  Does this happen?  Of course it does.  Since I'm in t=
he airplane with these guys, I've run wireshark on the WiFi network, record=
ed TCP packet streams (headers only), and observed exactly this behavior - =
very delayed HTTP 1.1 packets (many seconds of delay between request and re=
sponse).=0A=0AI don't intend to publish this data for one key reason: it do=
es not meet the standards of academic research publication. Why? because I =
can't get the data that only Gogo has in its network administration.  Eithe=
r they will measure and publish or they will not. I suspect they will do th=
e latter. Only Comcast has been willing to publish at all - and that is in =
a CableLabs tech report by a Sr. VP I know at Comcast, who has the authorit=
y to make the decision to reveal Comcast "trade secrets" to some extent.  A=
TT Wireless had this problem on half of its HSPA+ access networks, but it w=
ill never publish - it's embarrassing (and would make people switch to an a=
lternate provider, probably, too).  Instead they have blamed "wireless inte=
rference" and "badly designed iOS apps", anything other than their network =
operations.  (I told ATT about this, not under non-disclosure, when I first=
 measured it.  Their network operations people actually measured the proble=
m, I was told, but I don't know if they fixed it. All I know is that they b=
lamed a subcontractor, without naming that subcontractor in my phone call).=
=0A=0ASo there's nothing for an academic to cite, unfortunately. Sorry.=0A=
=0AIt's actually quite hard to do research on whether a problem is real - i=
f it is a problem the operator or vendor will not allow you to publish, or =
worse, will claim that you didn't measure the right thing or are lying or m=
isleading people.  Thank goodness for Comcast's engineers, who were honest.=
 (after their top management started an aggressive attack on those who obse=
rved that their initial solution, an attempt to disrupt "pirate traffic" by=
 TCP RST injection, caused the US FCC to slap them on the wrist.=0A=0ABut t=
he problem is real, and quite prevalent.  I carry around gear and software =
that I use whenever I am in a new location to detect both the "overbufferin=
g" that may be there, and ALSO, by running tests for 24 hours every hour, h=
ow it affects usability over a 24 hour period.=0A=0AI assure you it is a re=
al problem in practice, and also that it affect others than "gamers".  HTTP=
 based services suck badly when the problem arises. In the ATT case, when I=
 was measuring the problem in a Chicago office building where I was doing o=
ther consulting work, every iPhone user was complaining that their iPhone d=
ata services were not working.=0A=0A=0A=0A=0A=0A=0AOn Friday, February 27, =
2015 2:30pm, aqm-request@ietf.org said:=0A=0A> Send aqm mailing list submis=
sions to=0A> =09aqm@ietf.org=0A> =0A> To subscribe or unsubscribe via the W=
orld Wide Web, visit=0A> =09https://www.ietf.org/mailman/listinfo/aqm=0A> o=
r, via email, send a message with subject or body 'help' to=0A> =09aqm-requ=
est@ietf.org=0A> =0A> You can reach the person managing the list at=0A> =09=
aqm-owner@ietf.org=0A> =0A> When replying, please edit your Subject line so=
 it is more specific=0A> than "Re: Contents of aqm digest..."=0A> Today's T=
opics:=0A> =0A>    1. Re: Is bufferbloat a real problem? (Curtis Villamizar=
)=0A>    2. Re: Is bufferbloat a real problem? (Daniel Havey)=0A>    3. Re:=
 Is bufferbloat a real problem? (Daniel Havey)=0A> ________________________=
_______________________=0A> aqm mailing list=0A> aqm@ietf.org=0A> https://w=
ww.ietf.org/mailman/listinfo/aqm=0A> =0A


From nobody Fri Feb 27 18:00:21 2015
Return-Path: <davec-b@rogers.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 977241A1AA7 for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 18:00:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 W_4MEzJo6Fbn for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 18:00:18 -0800 (PST)
Received: from nm12-vm9.access.bullet.mail.bf1.yahoo.com (nm12-vm9.access.bullet.mail.bf1.yahoo.com [216.109.114.248]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B17111A1A27 for <aqm@ietf.org>; Fri, 27 Feb 2015 18:00:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogers.com; s=s2048; t=1425088816; bh=we46P+4OHfK609asFF+sd+f3sXdKaM3D6siqLmF72pg=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To:From:Subject; b=tQl0LOp/ZAmf23lMgdvSImkhoC8DMdk6PZqaE9adtVufIPQ8gnpbOaQ9vBq3JZePKP9QnPnOXeOh2wy3JHeS8ZlkhdJ8bXKI9puXuKCkNw16AR9cKFqZ40d8esYXpuNpyzNG1k5jQJnuzii+naTemhzbCpokeT6VA9SKqpSMBXTimGuUC9Ragf0VNqU9uhV4BpEwKjsoj0jUoR1E7U4iyX5CS8gKoTV3CG8T/M+sLirYyzc8RQ0mWhmgBctC9jauNnwssAUx7fE/pEdImSIC9/3qgQRhA4q4Zz8Z9ZxqGSAn0JWVUcaNj+y7nCIT6oxmjipBYYFbcB9KGfGMM4f46g==
Received: from [66.196.81.159] by nm12.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Feb 2015 02:00:16 -0000
Received: from [98.138.226.240] by tm5.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Feb 2015 02:00:16 -0000
Received: from [127.0.0.1] by smtp111.sbc.mail.ne1.yahoo.com with NNFMP; 28 Feb 2015 02:00:16 -0000
X-Yahoo-Newman-Id: 353474.73495.bm@smtp111.sbc.mail.ne1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: UHt2_WoVM1mDH.lzp_k2.lZEXEXaxfCQUNn4Lyezm00Nvyc PdnjGc5dRQH58qgtO2DYOxy.x_bvcEHnxcabrCfwuJWKpImgNknnT6LWJ4__ kXsOsSqsl1ibh_UZ8DYXpIEObb42cG4zSyzlmxzCQLnIkOVo1wTdWwQD8.oJ 55ouTVZgn3lLJqEyyh2Zk2cK9lcJZH0vx_0vbYqPK2M6H8ynnKYN2UBD1V.x tmeHu3G1rZ04d3komagz20SLXVlEEbm4jDYi6TcNmISZ64j8vtmRcLJFkBDz o1NEWn6l3Ijux7Zn4j0npoyYei0D23ahYttl_7PWwhbwHRtKfh3Yjvf53Upo mH.z1KfBRWhpEAEpD_ANcOcyTeqW9i1cqpJUGl4h6oL1tV3owvIZxNUHrhtq iontJFPk_yCL0GzWmE6z_ybnKqcvJXqb4Yi4J2DJrDM6M6GD.UMhJeOdiym_ YlGZPUjflr3uUxVJQMJEhKWuXk292iTeVaOdk90c9JK35gwEGtnKq1.9e7hE bTyX5NTiM7PCv86sTHpNKuheTJ2qMyNohDw--
X-Yahoo-SMTP: sltvjZWswBCRD.ElTuB1l9j6s9wRYPpuyTNWOE5oEg--
Message-ID: <54F1212D.3040703@rogers.com>
Date: Fri, 27 Feb 2015 21:00:13 -0500
From: David Collier-Brown <davec-b@rogers.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: aqm@ietf.org
References: <201502271852.t1RIqekh018253@maildrop31.somerville.occnc.com>
In-Reply-To: <201502271852.t1RIqekh018253@maildrop31.somerville.occnc.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/rsfuXJfD-c78N8excSayh2NO6wk>
Subject: Re: [aqm] Is bufferbloat a real problem?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: davecb@spamcop.net
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: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 02:00:20 -0000

IMHO, removing latency is the aim of FQ. Once done, buffer sizes can be 
unbounded (save by price (;-))

--dave

On 02/27/2015 01:52 PM, Curtis Villamizar wrote:
> In message <2134947047.1078309.1424979858723.JavaMail.yahoo@mail.yahoo.com>
> Daniel Havey writes:
>   
>>   
>> I know that this question is a bit ridiculous in this community.  Of
>> course bufferbloat is a real problem.  However, it would be nice to
>> formally address the question and I think this community is the right
>> place to do so.
>>   
>> Does anybody have a measurement study?  I have some stuff from the FCC
>> Measuring Broadband in America studies, but, that doesn't address
>> bufferbloat directly.
>>   
>> Let me repeat for clarity.  I don't need to be convinced.  I need
>> evidence that I can use to convince my committee.
>>   
>> ...Daniel
>>   
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>
> Daniel,
>
> You are convinced.  So am I but we need to temper the message to avoid
> going too far in the opposite direction - too little buffer.
>
> If you are not interested in the details, just skip to the last
> paragraph.
>
> Bufferbloat should in principle only be a problem for interactive
> realtime traffic.  Interactive means two way or multiway.  This is
> SIP, Skype, audio and video conferencing, etc.  In practice it is also
> bad for TCP flows with short RTT and max window set small.
>
> One way realtime (such as streaming audio and video) should be
> unnafected by all but huge bufferbloat.  That is should be.  For
> example, youtube video is carried over TCP and is typically either way
> ahead of the playback or choppy (inadequate aggregate bandwidth or
> marigninal and/or big drop with TCP stall).  It would be nice if
> marginal aggregate bandwidth was dealt with by switching to a lower
> bandwidth encoding, but too often this is not the case.  This doesn't
> mean that some streaming formats don't manage to get this wrong and
> end up delay sensitive.
>
> TCP needs buffering to function correctly.  Huge bufferbloat is bad
> for TCP, particularly for small transfers that never get out of TCP
> slow start and for short RTT flows.  For long RTT flows too little
> buffer causes problems.
>
> [ aside: For example, if TCP starts with 4 segments at 1K segment
> size, it will take 4 RTT to hit 64KB window, the typical max window
> without TCP large window (TCPLW) option.  During that time, 60KB will
> be sent.  After that 64KB will be sent each RTT.  With geographic RTT
> is 70 msec (approximate US continental RTT due to finite speed of
> light in fiber and fiber distance), 60 KB is sent in the first 280
> msec and 64KB gets sent every 70 msec yielding 7 mb/s.  OTOH if there
> is a server 2 msec RTT away (1 msec one way is 125mi = 200km), then
> 60KB in first 8 msec and 256 Mb/s after that.  If there is 100 msec
> buffer at a bottleneck, then this low RTT TCP flow will be slowed by a
> factor of 50.  OTOH, if bottlenecks have a lot less than 1 RTT of
> buffer, then the long TCP flows will get even further slowed. ]
>
> One of the effects of some buffer, but not excessive, is short RTT
> flows which given the no-TCPLW max window get slowed down while longer
> RTT are less affected.  This becomes more fair wrt to transfer rates
> among TCP flows.  The same holds true if TCPLW gets turned on in
> commodity gadgets and the commonly deploed max window increases, but
> the number change.
>
> If the buffer grows a little and the deployed window sizes become the
> limiting factor, then this is very light congestion with delay but
> absolutely zero loss due to queue drops (not considering AQM for the
> moment).
>
> Some uses of TCP increase the window to work better over long RTT.  It
> takes a bit longer to hit the max window but the rate once it has been
> hit is greater.  Setting TCP window large on short RTT flows is
> counterproductive since one or a small number of flows can cause a
> bottleneck on a slow provider link (ie: 10-100 Mb/s range typical of
> home use).  On a LAN RTT can be well under 1 msec on Ethernet and
> highly variable on WiFi.  On WiFi larger window can contribute to some
> real trouble.  So best that the default window be changed.
>
> [ Note that the work on automatic sizing of tcp_sndbuf and scp_recvbuf
> may create a tendency to saturate links as the window can go up to 2MB
> with default parameters.  Has this hit consumer devices yet?  This
> could be bad it this rolls out before widespread use of AQM. ]
>
> When a small amount of loss occurs, such as one or much less than the
> current window size, TCP cuts the current window size in half and
> retransmits the packet for the window in flight (ignoring selective
> acknowledgment extension aka SACK for the moment).
>
> If the buffer is way too small, then a large amount of premature drop
> occurs when the buffer limit is hit.  Lots of TCP flows slow down.
> The long RTT flows slow down the most.  Some retransmission occurs
> (which doesn't help congestion).  If there is a long period of drop
> relative to a short RTT, then a entire window can be dropped and this
> is terrible for TCP (slow start is initiated after delay based on an
> estimate of RTT and RTT stdev, or 3 sec if RTT estimate is stale -
> this is a TCP stall).  So with too little buffer some TCP flows get
> hammered and stall.  TCP flows with long RTT tend to stall less but
> are more sensitve to the frequency of drop events and can get
> extremely slow due to successively cutting window in half and then
> growing the window linearly rather than exponentially.
>
> With tiny buffers really bad things tend to happen.  The rate of
> retransmission can drive goodput (the amount of non-retransmit traffic
> per time) can drop substantially.  Long RTT flows can become
> hopelessly slow.  Stalls become more common.  In the worst case (which
> has been observed in a ISP network during a tiny buffer experiment
> about a decade ago, details in private email) TCP synchronization can
> occur, and utilization and goodput drop dramatically.
>
> A moderate amount of buffer is good for all TCP.  A large buffer is
> good for long RTT TCP flows, particularly those that have increased
> max window.  As mentioned before, any but a very small buffer is bad
> for interactive real time applications.
>
> Enter AQM.  A large buffer can be used but with a lower target delay
> and some form of AQM to introduce a low rate of isolated drops as
> needed to slow the senders.  Avoiding queue tail drop events where a
> lot of drops occur over an interval lowers the amount of
> retransmission and avoids stalls.  Long RTT flows tend to get
> penalized the most.
>
> Fairness is not great with a single queue and AQM but this is much
> better than a single queue with either small or large buffer and tail
> drop.  Fairness is greatly improved with some form of FQ or SFQ.
>
> Ideally with FQ each flow would get its own queue.  In practice this
> is not the case but the situation is greatly improved.  A real time
> flow, which is inherently rate limited, would see minimal delay and no
> loss.  A short RTT flow would see a moderate increase in delay and a
> low level of loss (ie: typically much less than 1%) enough to slow it
> down enough to avoid congestion.  a long RTT flow would see a moderate
> increase in delay and no loss if still running slower than the small
> RTT flows.  This does wonders for fairness and provides the best
> possible service for each service type.
>
> In practice, some FQ or SFQ queues have a mix of real time, low RTT
> TCP, and high RTT TCP.  If any such queue is taking a smaller share
> than other queues, delay is low and loss is low or zero.  If such a
> queue is taking more than its share, then the situation is similar to
> the single queue case.  Less flows end up in such a queue.  Cascaded
> queues have been proposed and in some cases (no longer existing) have
> been implemented.  In a cascaded SFQ scheme, the queues taking more
> than their share are further subdivied.  Repeat the subdivision a few
> times and you can end up with the large bandwidth contributors in
> their own queue and getting a fair share of capacity.
>
> So excuse the length of this but solving bufferbloat is *not* a silver
> bullet.  Not understanding that point and just making buffers really
> small could result in an even worse situation than we have now.
>
> Curtis
>
> ps - Some aspects of this may not reflect WG direction.  IMHO- the
> down sides of just making buffers smaller and/or setting low delay
> targets may not be getting enough (or any) attention in the WG.  Maybe
> discussion wouldn't hurt.
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>


-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |                      -- Mark Twain


From nobody Fri Feb 27 18:10:37 2015
Return-Path: <kk@cs.ucr.edu>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDC731A1B2C for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 18:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 gQr_n7V6_PXc for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 18:10:33 -0800 (PST)
Received: from send.cs.ucr.edu (send.cs.ucr.edu [169.235.30.36]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 543B91A00D1 for <aqm@ietf.org>; Fri, 27 Feb 2015 18:10:33 -0800 (PST)
Received: from [138.23.169.174] (dhcp-169-174.cs.ucr.edu [138.23.169.174]) (using TLSv1 with cipher DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by send.cs.ucr.edu (Postfix) with ESMTP id 17FCE1FA0495; Fri, 27 Feb 2015 18:10:33 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.4.8.150116
Date: Fri, 27 Feb 2015 18:16:12 -0800
From: KK <kk@cs.ucr.edu>
To: <davecb@spamcop.net>, <aqm@ietf.org>
Message-ID: <D11664D4.2EEC%kk@cs.ucr.edu>
Thread-Topic: [aqm] Is bufferbloat a real problem?
References: <201502271852.t1RIqekh018253@maildrop31.somerville.occnc.com> <54F1212D.3040703@rogers.com>
In-Reply-To: <54F1212D.3040703@rogers.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/rHteORwHgShKRPO5yWSUQXJB9II>
Subject: Re: [aqm] Is bufferbloat a real problem?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 02:10:36 -0000

This could also be done by not having to depend on =8Closs=B9 as the primary
source of feedback...
--=20
K. K. Ramakrishnan
Professor
Dept. of Computer Science and Engineering
University of California, Riverside
Rm. 332, Winston Chung Hall
Tel: (951) 827-2480


Web Page: http://www.cs.ucr.edu/~kk/




On 2/27/15, 6:00 PM, "David Collier-Brown" <davec-b@rogers.com> wrote:

>IMHO, removing latency is the aim of FQ. Once done, buffer sizes can be
>unbounded (save by price (;-))
>
>--dave
>
>On 02/27/2015 01:52 PM, Curtis Villamizar wrote:
>> In message=20
>><2134947047.1078309.1424979858723.JavaMail.yahoo@mail.yahoo.com>
>> Daniel Havey writes:
>>  =20
>>>  =20
>>> I know that this question is a bit ridiculous in this community.  Of
>>> course bufferbloat is a real problem.  However, it would be nice to
>>> formally address the question and I think this community is the right
>>> place to do so.
>>>  =20
>>> Does anybody have a measurement study?  I have some stuff from the FCC
>>> Measuring Broadband in America studies, but, that doesn't address
>>> bufferbloat directly.
>>>  =20
>>> Let me repeat for clarity.  I don't need to be convinced.  I need
>>> evidence that I can use to convince my committee.
>>>  =20
>>> ...Daniel
>>>  =20
>>> _______________________________________________
>>> aqm mailing list
>>> aqm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/aqm
>>
>> Daniel,
>>
>> You are convinced.  So am I but we need to temper the message to avoid
>> going too far in the opposite direction - too little buffer.
>>
>> If you are not interested in the details, just skip to the last
>> paragraph.
>>
>> Bufferbloat should in principle only be a problem for interactive
>> realtime traffic.  Interactive means two way or multiway.  This is
>> SIP, Skype, audio and video conferencing, etc.  In practice it is also
>> bad for TCP flows with short RTT and max window set small.
>>
>> One way realtime (such as streaming audio and video) should be
>> unnafected by all but huge bufferbloat.  That is should be.  For
>> example, youtube video is carried over TCP and is typically either way
>> ahead of the playback or choppy (inadequate aggregate bandwidth or
>> marigninal and/or big drop with TCP stall).  It would be nice if
>> marginal aggregate bandwidth was dealt with by switching to a lower
>> bandwidth encoding, but too often this is not the case.  This doesn't
>> mean that some streaming formats don't manage to get this wrong and
>> end up delay sensitive.
>>
>> TCP needs buffering to function correctly.  Huge bufferbloat is bad
>> for TCP, particularly for small transfers that never get out of TCP
>> slow start and for short RTT flows.  For long RTT flows too little
>> buffer causes problems.
>>
>> [ aside: For example, if TCP starts with 4 segments at 1K segment
>> size, it will take 4 RTT to hit 64KB window, the typical max window
>> without TCP large window (TCPLW) option.  During that time, 60KB will
>> be sent.  After that 64KB will be sent each RTT.  With geographic RTT
>> is 70 msec (approximate US continental RTT due to finite speed of
>> light in fiber and fiber distance), 60 KB is sent in the first 280
>> msec and 64KB gets sent every 70 msec yielding 7 mb/s.  OTOH if there
>> is a server 2 msec RTT away (1 msec one way is 125mi =3D 200km), then
>> 60KB in first 8 msec and 256 Mb/s after that.  If there is 100 msec
>> buffer at a bottleneck, then this low RTT TCP flow will be slowed by a
>> factor of 50.  OTOH, if bottlenecks have a lot less than 1 RTT of
>> buffer, then the long TCP flows will get even further slowed. ]
>>
>> One of the effects of some buffer, but not excessive, is short RTT
>> flows which given the no-TCPLW max window get slowed down while longer
>> RTT are less affected.  This becomes more fair wrt to transfer rates
>> among TCP flows.  The same holds true if TCPLW gets turned on in
>> commodity gadgets and the commonly deploed max window increases, but
>> the number change.
>>
>> If the buffer grows a little and the deployed window sizes become the
>> limiting factor, then this is very light congestion with delay but
>> absolutely zero loss due to queue drops (not considering AQM for the
>> moment).
>>
>> Some uses of TCP increase the window to work better over long RTT.  It
>> takes a bit longer to hit the max window but the rate once it has been
>> hit is greater.  Setting TCP window large on short RTT flows is
>> counterproductive since one or a small number of flows can cause a
>> bottleneck on a slow provider link (ie: 10-100 Mb/s range typical of
>> home use).  On a LAN RTT can be well under 1 msec on Ethernet and
>> highly variable on WiFi.  On WiFi larger window can contribute to some
>> real trouble.  So best that the default window be changed.
>>
>> [ Note that the work on automatic sizing of tcp_sndbuf and scp_recvbuf
>> may create a tendency to saturate links as the window can go up to 2MB
>> with default parameters.  Has this hit consumer devices yet?  This
>> could be bad it this rolls out before widespread use of AQM. ]
>>
>> When a small amount of loss occurs, such as one or much less than the
>> current window size, TCP cuts the current window size in half and
>> retransmits the packet for the window in flight (ignoring selective
>> acknowledgment extension aka SACK for the moment).
>>
>> If the buffer is way too small, then a large amount of premature drop
>> occurs when the buffer limit is hit.  Lots of TCP flows slow down.
>> The long RTT flows slow down the most.  Some retransmission occurs
>> (which doesn't help congestion).  If there is a long period of drop
>> relative to a short RTT, then a entire window can be dropped and this
>> is terrible for TCP (slow start is initiated after delay based on an
>> estimate of RTT and RTT stdev, or 3 sec if RTT estimate is stale -
>> this is a TCP stall).  So with too little buffer some TCP flows get
>> hammered and stall.  TCP flows with long RTT tend to stall less but
>> are more sensitve to the frequency of drop events and can get
>> extremely slow due to successively cutting window in half and then
>> growing the window linearly rather than exponentially.
>>
>> With tiny buffers really bad things tend to happen.  The rate of
>> retransmission can drive goodput (the amount of non-retransmit traffic
>> per time) can drop substantially.  Long RTT flows can become
>> hopelessly slow.  Stalls become more common.  In the worst case (which
>> has been observed in a ISP network during a tiny buffer experiment
>> about a decade ago, details in private email) TCP synchronization can
>> occur, and utilization and goodput drop dramatically.
>>
>> A moderate amount of buffer is good for all TCP.  A large buffer is
>> good for long RTT TCP flows, particularly those that have increased
>> max window.  As mentioned before, any but a very small buffer is bad
>> for interactive real time applications.
>>
>> Enter AQM.  A large buffer can be used but with a lower target delay
>> and some form of AQM to introduce a low rate of isolated drops as
>> needed to slow the senders.  Avoiding queue tail drop events where a
>> lot of drops occur over an interval lowers the amount of
>> retransmission and avoids stalls.  Long RTT flows tend to get
>> penalized the most.
>>
>> Fairness is not great with a single queue and AQM but this is much
>> better than a single queue with either small or large buffer and tail
>> drop.  Fairness is greatly improved with some form of FQ or SFQ.
>>
>> Ideally with FQ each flow would get its own queue.  In practice this
>> is not the case but the situation is greatly improved.  A real time
>> flow, which is inherently rate limited, would see minimal delay and no
>> loss.  A short RTT flow would see a moderate increase in delay and a
>> low level of loss (ie: typically much less than 1%) enough to slow it
>> down enough to avoid congestion.  a long RTT flow would see a moderate
>> increase in delay and no loss if still running slower than the small
>> RTT flows.  This does wonders for fairness and provides the best
>> possible service for each service type.
>>
>> In practice, some FQ or SFQ queues have a mix of real time, low RTT
>> TCP, and high RTT TCP.  If any such queue is taking a smaller share
>> than other queues, delay is low and loss is low or zero.  If such a
>> queue is taking more than its share, then the situation is similar to
>> the single queue case.  Less flows end up in such a queue.  Cascaded
>> queues have been proposed and in some cases (no longer existing) have
>> been implemented.  In a cascaded SFQ scheme, the queues taking more
>> than their share are further subdivied.  Repeat the subdivision a few
>> times and you can end up with the large bandwidth contributors in
>> their own queue and getting a fair share of capacity.
>>
>> So excuse the length of this but solving bufferbloat is *not* a silver
>> bullet.  Not understanding that point and just making buffers really
>> small could result in an even worse situation than we have now.
>>
>> Curtis
>>
>> ps - Some aspects of this may not reflect WG direction.  IMHO- the
>> down sides of just making buffers smaller and/or setting low delay
>> targets may not be getting enough (or any) attention in the WG.  Maybe
>> discussion wouldn't hurt.
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>>
>
>
>--=20
>David Collier-Brown,         | Always do right. This will gratify
>System Programmer and Author | some people and astonish the rest
>davecb@spamcop.net           |                      -- Mark Twain
>
>_______________________________________________
>aqm mailing list
>aqm@ietf.org
>https://www.ietf.org/mailman/listinfo/aqm



From nobody Fri Feb 27 18:45:25 2015
Return-Path: <davec-b@rogers.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 714A81A1B64 for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 18:45:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 POrXUFRMW4Aw for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 18:45:23 -0800 (PST)
Received: from nm19-vm4.access.bullet.mail.bf1.yahoo.com (nm19-vm4.access.bullet.mail.bf1.yahoo.com [216.109.115.99]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 321D01A1B60 for <aqm@ietf.org>; Fri, 27 Feb 2015 18:45:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogers.com; s=s2048; t=1425091522; bh=sfJOw/xd/rz81VvjTnn3+n7/gNkVR1eE8hK4GRDTLZo=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To:From:Subject; b=PQgGwo89Hm8ysvL12wJN3wmMt86ZWlWpNeA2EWg9HCO6vLtnO961DX3suMidYLcO7PUg3EzJjL/QIAKp85VCA3wsTmzsLI+ydHOdGNMSj2mXIHWlqGQtNYmk49TVLVnak+82gsWrmn+4GZuoPQe1HANX+/6JntrRdOhPkWhoFNjR0c0ZP7dWae3PSzbC5n+d8jpxGQS9nlahT3aXkXYKuu+ovFYOugCp2cfgrdxfFJ9ly21M7j2Vh084iIchl2AEysDLt1DyhFP/LLNmg8wvO5THBb/vSAhatVunb4Fw8UpcXizrc0q+KVTeEK3EbgdsaTWBfRkVxMoLoIqmGxTNww==
Received: from [66.196.81.158] by nm19.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Feb 2015 02:45:22 -0000
Received: from [98.138.226.242] by tm4.access.bullet.mail.bf1.yahoo.com with NNFMP; 28 Feb 2015 02:45:22 -0000
Received: from [127.0.0.1] by smtp113.sbc.mail.ne1.yahoo.com with NNFMP; 28 Feb 2015 02:45:22 -0000
X-Yahoo-Newman-Id: 331779.64886.bm@smtp113.sbc.mail.ne1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: QsUKg3oVM1mki9uUje..PuEkQFi.XO0LjzNQVC13VMwP2eZ 3P_Df4rZ_iFtAvv0M5HYXV5nxmt99F.c5R72C2O2JNBzdICgRjSsoW1hCp4i 5W8GiCM8vlz2pLkHSu3L1Vjn0Vb.RkYD75z.CHW9D2s8ji1Yp_.bi2rgXxfQ OaUyHom7hxwiSs.E9BWY7F4ENf74lj5ViqoxNU.L9H0IcxCFi8CfzjdqBB.R wEPNRO_mvV8.432sZ2A389JNNeX.opKoHZ4Hq5P9MvCwFc.9UaHPt.6.jHbf hr72kcGJCs1x.IfTSWuZgXRab6.aoWovmBPLUeUw4uPWgwgV_YSfpqxtz0mv jCPggTfx7GtCUtR6xJZ1xZoPvEMkyYNhE565c469lpX5b7VnbfGK5W.OPPtZ y4bCSehgfZqD8os9Sui5Xpht9CovcpaGTr5ZYIcblRyAVOVGfEAhMLH9J2BW v.hGLI9QBDxbq0._B9s3AsWFrYogNPPGq0g0tNN5wNjdf1TTdeqGLIWi1rTV RVU0r2Tbdf873Y_pTNSuf5C24eHg472dszCPy
X-Yahoo-SMTP: sltvjZWswBCRD.ElTuB1l9j6s9wRYPpuyTNWOE5oEg--
Message-ID: <54F12BBF.4050503@rogers.com>
Date: Fri, 27 Feb 2015 21:45:19 -0500
From: David Collier-Brown <davec-b@rogers.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: KK <kk@cs.ucr.edu>, davecb@spamcop.net, aqm@ietf.org
References: <201502271852.t1RIqekh018253@maildrop31.somerville.occnc.com> <54F1212D.3040703@rogers.com> <D11664D4.2EEC%kk@cs.ucr.edu>
In-Reply-To: <D11664D4.2EEC%kk@cs.ucr.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/oS83Gc4ZOErTwwD-IcZDF3kRi_E>
Subject: Re: [aqm] Is bufferbloat a real problem?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: davecb@spamcop.net
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: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 02:45:24 -0000

Yup!

Loss is a bit of like hitting someone with  a 2 x 4" as a clue-stick. It 
hurts, but it sure does work!

--dave


On 02/27/2015 09:16 PM, KK wrote:
> This could also be done by not having to depend on Ślossą as the primary
> source of feedback...

On 2/27/15, 6:00 PM, "David Collier-Brown" <davec-b@rogers.com> wrote:

> IMHO, removing latency is the aim of FQ. Once done, buffer sizes can be
> unbounded (save by price (;-))

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |                      -- Mark Twain


From nobody Fri Feb 27 21:45:16 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF5B1A1BA4 for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 21:45:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 EedddTDKdM_y for <aqm@ietfa.amsl.com>; Fri, 27 Feb 2015 21:45:13 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F07751A1BA3 for <aqm@ietf.org>; Fri, 27 Feb 2015 21:45:12 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 41DC6A3; Sat, 28 Feb 2015 06:45:09 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1425102309; bh=NH3s9vi65GfQnSisZzSTEjFeoTjlTBQraS18upoKOfQ=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=I/wseSBUDHEaobPSInR29E760RpxWslib088zuVm4HZu2OFLbLo3P7nRD2C66wm4+ VhXHBBoYUxIlZNbHpg2fu2KmNLEjxystnYH3sOyR90ErdWVuyLWhHLNbx/wS3TxZNW PAiXxr6aXAyyo/AOEGl4QHMtYKLq77xh3Y70ZgCs=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 3D6D0A2; Sat, 28 Feb 2015 06:45:09 +0100 (CET)
Date: Sat, 28 Feb 2015 06:45:09 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Daniel Havey <dhavey@gmail.com>
In-Reply-To: <CAO1c0ARbAt4H5AupHMSa7ziL6JZXJEw-kxbua2xz3QAHt4UgiA@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1502280641270.4007@uplift.swm.pp.se>
References: <2134947047.1078309.1424979858723.JavaMail.yahoo@mail.yahoo.com> <201502271852.t1RIqekh018253@maildrop31.somerville.occnc.com> <CAO1c0ARbAt4H5AupHMSa7ziL6JZXJEw-kxbua2xz3QAHt4UgiA@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/Gut_1KN4O2I3p6jHPjY7TZ4z27Q>
Cc: "aqm@ietf.org" <aqm@ietf.org>, Daniel Havey <dhavey@yahoo.com>, curtis@ipv6.occnc.com
Subject: Re: [aqm] Is bufferbloat a real problem?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 05:45:15 -0000

On Fri, 27 Feb 2015, Daniel Havey wrote:

> Like I said, I agree that bufferbloat is only 1 part of a two sided 
> problem.  The queue with respect to each flow can be either two large or 
> too small (and sometimes just right?).  Anyways, I'm just wondering if 
> there are any measurement studies out there that show the effects of 
> this problem in a formal way.

There are even videos showing this on youtube, where downloading at the 
same time as doing video conferencing means the video conferencing works a 
lot worse, and also that loading a web page takes a lot longer (due to DNS 
resolving packets, SYNs etc being stuck behind a lot of data packets).

https://www.youtube.com/watch?v=-D-cJNtKwuw for instance.

Jim Gettys and Dave Taht (and others) have done wonderful jobs in 
demonstrating that this is indeed a problem. I know gobs of users who know 
this is a problem as well, but they don't know how to fix it. People 
active in the bufferbloat movement have shown that there are solutions, 
and have shown these to work. There are papers and there are videos to 
show this. Even the RRUL test tool kit shows this very well if you 
understand what "500ms add latency" will mean to your Internet experience.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Sat Feb 28 09:47:19 2015
Return-Path: <dave.taht@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C3461A7028; Sat, 28 Feb 2015 09:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 E2ekt3troMtZ; Sat, 28 Feb 2015 09:47:15 -0800 (PST)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB54B1A7021; Sat, 28 Feb 2015 09:47:15 -0800 (PST)
Received: by mail-oi0-f45.google.com with SMTP id i138so20766881oig.4; Sat, 28 Feb 2015 09:47:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=H1OBaaXJhSIyjpUV/hlQM3LXRO4HiqZhiNJh0/+ahzo=; b=ZZqZ4Bn8UALPzQLgANHu7qrf6ggF9A7vt9ojAoR6WtgATsfgxxE7gCRbgm9ReTzRAh 2NG8tRX/M3ZHDyaTeCCauHsNBzOkk9OxbernDS8rEaKIv+Mqe8eHC4C8TUbyR+EnnS4M lfaLkH1X0eoc3CqJ7wbK9viGW16UWwd65Noqmbvh2UOPq3Cx/lgFbmgp7uwWDhWXuDCD un5o7TnIsqPGKX1k2L/JBXRHL+jyCsI9UZkxwR/x1TGQEjYiyto+yRIhVZlWmLuPSyf5 BxJ+rbCFkHBqtvHEWLnvH2F6ZZtxkBDQbxWtEowEZXB9Ule99nGYMxNTmOZ2/1gmEBg7 fDzQ==
MIME-Version: 1.0
X-Received: by 10.60.103.234 with SMTP id fz10mr13964579oeb.11.1425145634997;  Sat, 28 Feb 2015 09:47:14 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Sat, 28 Feb 2015 09:47:14 -0800 (PST)
In-Reply-To: <54F1F630.3080902@wlan-si.net>
References: <54F1F630.3080902@wlan-si.net>
Date: Sat, 28 Feb 2015 09:47:14 -0800
Message-ID: <CAA93jw5pXS5jBwp9w6vAyjpwOgvg40=e864uMfwjRqc=eF1Y_g@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>,  "cerowrt-devel@lists.bufferbloat.net" <cerowrt-devel@lists.bufferbloat.net>, "aqm@ietf.org" <aqm@ietf.org>,  HOMENET <homenet@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/E4WNodWcP7r3GLt03mDfT5EuQaA>
Subject: Re: [aqm] [Battlemesh] Battlemesh V8 Logo
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 17:47:17 -0000

On Sat, Feb 28, 2015 at 9:09 AM, Musti <musti@wlan-si.net> wrote:
> Hi folks,
>
> I am happy to present the new logo for Battlemesh V8 in Maribor,
> designed by Barbara :)
>
> http://battlemesh.org/BattleMeshV8/PosterDesign
>
> Comments appreciated!

That is a truly awesome poster! I hope you line up more sponsors for
this conference!

>
> Kind regards,
> Musti
> _______________________________________________
> Battlemesh mailing list
> Battlemesh@ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh



--=20
Dave T=C3=A4ht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb


From nobody Sat Feb 28 14:32:16 2015
Return-Path: <dave.taht@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE661A0023 for <aqm@ietfa.amsl.com>; Sat, 28 Feb 2015 14:32:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 sxez0XkslE27 for <aqm@ietfa.amsl.com>; Sat, 28 Feb 2015 14:32:14 -0800 (PST)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D59951A0019 for <aqm@ietf.org>; Sat, 28 Feb 2015 14:32:13 -0800 (PST)
Received: by mail-oi0-f54.google.com with SMTP id v63so21319965oia.13 for <aqm@ietf.org>; Sat, 28 Feb 2015 14:32:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=WotcV7IT6ymOQ4hz/fuKYf/2yuQ9Yt0fqh7eVVOY6QY=; b=qXtQbouZGbwwNC9+54Wwh2V7byjzXDzQ2raZovXyQjOR+7loLKn5V2Sxj7LoMCyqt7 6StUzZZDOWt6ecnfS4no/7uewwmmIv7oLOWX6+BpEM3zLR8y7Dgvvq8ftQmV93FVqv4v h4znhuY4bEhf7tRP4cSd+HRMKUU++g6zHIkNlV0nlAVdlHRAOJrgy7nOySPryZj87r24 Hix+1Fh1Gb+SPLCecYMf6/2FFPaWLPRDKmR7dJLi/bpfeXFKCE122TnTzH9rKSVF9Tuj 9wvlkQRpuPc2xsDgEnKOOTRjuvm4PJeCngBVpn1pLHiSu0y3pqJyPWp0nHyET07gqTyq 2PGw==
MIME-Version: 1.0
X-Received: by 10.182.1.202 with SMTP id 10mr14540979obo.56.1425162733171; Sat, 28 Feb 2015 14:32:13 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Sat, 28 Feb 2015 14:32:13 -0800 (PST)
Date: Sat, 28 Feb 2015 14:32:13 -0800
Message-ID: <CAA93jw6rE2QBsnrptH_QCsVHu6PyATtdDE_fVnw8y-UeWdsRdA@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, "aqm@ietf.org" <aqm@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/LTWMcq3WncH534q-O1EY8lo9e64>
Subject: [aqm] speedtest-like results for 3g and 4g at ofcom
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 22:32:15 -0000

Anybody know anybody here that could ask them to run a valid latency
under load test?

http://media.ofcom.org.uk/news/2014/3g-4g-bb-speeds/



--=20
Dave T=C3=A4ht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb


From nobody Sat Feb 28 17:12:36 2015
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1EE1A0126 for <aqm@ietfa.amsl.com>; Sat, 28 Feb 2015 17:12:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.013
X-Spam-Level: 
X-Spam-Status: No, score=-0.013 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 5bnTe6R-02mi for <aqm@ietfa.amsl.com>; Sat, 28 Feb 2015 17:12:33 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 E65831A00E6 for <aqm@ietf.org>; Sat, 28 Feb 2015 17:12:32 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t211CKl6042392; Sat, 28 Feb 2015 20:12:21 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201503010112.t211CKl6042392@maildrop31.somerville.occnc.com>
To: dpreed@reed.com
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Fri, 27 Feb 2015 15:06:29 -0500." <1425067589.903626768@apps.rackspace.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <42390.1425172340.1@harbor31.somerville.occnc.com>
Date: Sat, 28 Feb 2015 20:12:20 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/XY4sGr-IIy6676TkJosrXFDa6As>
Cc: aqm@ietf.org
Subject: Re: [aqm] aqm Digest, Vol 24, Issue 18
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
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: <http://www.ietf.org/mail-archive/web/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: Sun, 01 Mar 2015 01:12:35 -0000

In message <1425067589.903626768@apps.rackspace.com>
dpreed@reed.com writes:
 
> Having done many experiments in many locations, I can tell you it is a
> real problem and a severe problem, in the real world.
>  
> I can observe it every time I fly from Boston to San Jose and back
> (which I do once per month).  If you use Gogo (the provider that
> supports several airlines' network access), all you need to do is
> measure either the uplink or downlink queue, and you find the typical
> symptom: a buffer that has multiple seconds of backlog, and no packet
> loss whatsoever (using either ICMP or UDP).  That's pretty severe -
> what it means is that the probability that "ssh" times out is non
> zero, not because of lost packets or lost carrier, but because of the
> default timeout in ssh being exceeded.
>  
> Now why is this a serious problem?  Well, think about it.  If packets
> sit in queues for 4 seconds, what impact does that have on people
> using HTTP?  Well, they think a website is down, so within a couple of
> seconds, they switch to surfing some other web site.  Meanwhile, the
> downloaded packets (pictures or whatever, which are in transit because
> of a relatively long TCP window that has built up in HTTP 1.1/TCP/IP,
> which supports all consecutive HTTP requests to the same server,
> because the service was temporarily OK), are filling up the download
> queue - even though the user(s) have moved on and probably even closed
> their connections on their end).  Does this happen?  Of course it
> does.  Since I'm in the airplane with these guys, I've run wireshark
> on the WiFi network, recorded TCP packet streams (headers only), and
> observed exactly this behavior - very delayed HTTP 1.1 packets (many
> seconds of delay between request and response).
>  
> I don't intend to publish this data for one key reason: it does not
> meet the standards of academic research publication. Why? because I
> can't get the data that only Gogo has in its network administration.
> Either they will measure and publish or they will not. I suspect they
> will do the latter. Only Comcast has been willing to publish at all -
> and that is in a CableLabs tech report by a Sr. VP I know at Comcast,
> who has the authority to make the decision to reveal Comcast "trade
> secrets" to some extent.  ATT Wireless had this problem on half of
> its HSPA+ access networks, but it will never publish - it's
> embarrassing (and would make people switch to an alternate provider,
> probably, too).  Instead they have blamed "wireless interference" and
> "badly designed iOS apps", anything other than their network
> operations.  (I told ATT about this, not under non-disclosure, when I
> first measured it.  Their network operations people actually measured
> the problem, I was told, but I don't know if th ey fixed it. All I
> know is that they blamed a subcontractor, without naming that
> subcontractor in my phone call).
>  
> So there's nothing for an academic to cite, unfortunately. Sorry.
>  
> It's actually quite hard to do research on whether a problem is real -
> if it is a problem the operator or vendor will not allow you to
> publish, or worse, will claim that you didn't measure the right thing
> or are lying or misleading people.  Thank goodness for Comcast's
> engineers, who were honest. (after their top management started an
> aggressive attack on those who observed that their initial solution,
> an attempt to disrupt "pirate traffic" by TCP RST injection, caused
> the US FCC to slap them on the wrist.
>  
> But the problem is real, and quite prevalent.  I carry around gear and
> software that I use whenever I am in a new location to detect both the
> "overbuffering" that may be there, and ALSO, by running tests for 24
> hours every hour, how it affects usability over a 24 hour period.
>  
> I assure you it is a real problem in practice, and also that it affect
> others than "gamers".  HTTP based services suck badly when the problem
> arises. In the ATT case, when I was measuring the problem in a Chicago
> office building where I was doing other consulting work, every iPhone
> user was complaining that their iPhone data services were not working.


Yes [unnamed person] you are certainly citing a specific service which
is severely broken as a result of having no clue whatsoever about
bufferbloat.  I will also point out that some frame relay switches of
ancient times also buffered for tens of seconds.  Not so good for
people in Ameritec land that had Internet service over FR in the late
1990s or anyone using PSI prior to the demise of PSI.

Hopefully severe cluelessness is still the exception (though there
seem to be a few repeat offenders).

My caution in
Message-Id: <201502271852.t1RIqekh018253@maildrop31.somerville.occnc.com>
was:

  You are convinced.  So am I but we need to temper the message to avoid
  going too far in the opposite direction - too little buffer.

  [...]

  So excuse the length of this but solving bufferbloat is *not* a silver
  bullet.  Not understanding that point and just making buffers really
  small could result in an even worse situation than we have now.

There was a brief (well years actually) push for tiny buffers or none
at all.  Some wanted to push this to make optical burst switching
seems more feasible.  This was an equally clueless idea and I'm hoping
we don't emphasize bufferbloat so much that some not so cluefuls go
too far in the direction of tiny buffers rather than reasonably sized
buffers with AQM or better yet some flavor of FQ and AQM.

Curtis



> On Friday, February 27, 2015 2:30pm, aqm-request@ietf.org said:
>  
> > Send aqm mailing list submissions to
> > 	aqm@ietf.org
> > 
> > To subscribe or unsubscribe via the World Wide Web, visit
> > 	https://www.ietf.org/mailman/listinfo/aqm
> > or, via email, send a message with subject or body 'help' to
> > 	aqm-request@ietf.org
> > 
> > You can reach the person managing the list at
> > 	aqm-owner@ietf.org
> > 
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of aqm digest..."
> > Today's Topics:
> > 
> >    1. Re: Is bufferbloat a real problem? (Curtis Villamizar)
> >    2. Re: Is bufferbloat a real problem? (Daniel Havey)
> >    3. Re: Is bufferbloat a real problem? (Daniel Havey)
> > _______________________________________________
> > aqm mailing list
> > aqm@ietf.org
> > https://www.ietf.org/mailman/listinfo/aqm
> > 
>  
>  
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm


From nobody Sat Feb 28 17:35:05 2015
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E63B91A1A02 for <aqm@ietfa.amsl.com>; Sat, 28 Feb 2015 17:35:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 T6cYZO4AcQ6S for <aqm@ietfa.amsl.com>; Sat, 28 Feb 2015 17:35:01 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 433D61A036C for <aqm@ietf.org>; Sat, 28 Feb 2015 17:35:00 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t211Yiid042569; Sat, 28 Feb 2015 20:34:45 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201503010134.t211Yiid042569@maildrop31.somerville.occnc.com>
To: davecb@spamcop.net
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Fri, 27 Feb 2015 21:00:13 -0500." <54F1212D.3040703@rogers.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <42567.1425173684.1@harbor31.somerville.occnc.com>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 28 Feb 2015 20:34:44 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/5MgEI9WbeMpWoPyAdOoOjqQ5ScA>
Cc: aqm@ietf.org
Subject: Re: [aqm] Is bufferbloat a real problem?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
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: <http://www.ietf.org/mail-archive/web/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: Sun, 01 Mar 2015 01:35:04 -0000

In message <54F1212D.3040703@rogers.com>
David Collier-Brown writes:
 =

> IMHO, removing latency is the aim of FQ. Once done, buffer sizes can be =

> unbounded (save by price (;-))
>  =

> --dave


FQ and truly huge buffers and no AQM would also be seriously broken
and qualify as a bufferbloat problem.  Realtime would be OK if it were
rate limited by audio or video encoding.  A TCP flow would keep
filling its FQ buffer until RTT was absurdly large and other timers
kicked in.  Poor real time flow that had the bad luck to get stuck in
the same FQ queue as a long lived TCP flow.

FQ is also not a silver bullet but it is part of some good solutions,
perhaps the best solutions we know of at this point.

Curtis


> On 02/27/2015 01:52 PM, Curtis Villamizar wrote:
> > In message <2134947047.1078309.1424979858723.JavaMail.yahoo@mail.yahoo=
.com>
> > Daniel Havey writes:
> >   =

> >>   =

> >> I know that this question is a bit ridiculous in this community.  Of
> >> course bufferbloat is a real problem.  However, it would be nice to
> >> formally address the question and I think this community is the right
> >> place to do so.
> >>   =

> >> Does anybody have a measurement study?  I have some stuff from the FC=
C
> >> Measuring Broadband in America studies, but, that doesn't address
> >> bufferbloat directly.
> >>   =

> >> Let me repeat for clarity.  I don't need to be convinced.  I need
> >> evidence that I can use to convince my committee.
> >>   =

> >> ...Daniel
> >>   =

> >> _______________________________________________
> >> aqm mailing list
> >> aqm@ietf.org
> >> https://www.ietf.org/mailman/listinfo/aqm
> >
> > Daniel,
> >
> > You are convinced.  So am I but we need to temper the message to avoid
> > going too far in the opposite direction - too little buffer.
> >
> > If you are not interested in the details, just skip to the last
> > paragraph.
> >
> > Bufferbloat should in principle only be a problem for interactive
> > realtime traffic.  Interactive means two way or multiway.  This is
> > SIP, Skype, audio and video conferencing, etc.  In practice it is also
> > bad for TCP flows with short RTT and max window set small.
> >
> > One way realtime (such as streaming audio and video) should be
> > unnafected by all but huge bufferbloat.  That is should be.  For
> > example, youtube video is carried over TCP and is typically either way
> > ahead of the playback or choppy (inadequate aggregate bandwidth or
> > marigninal and/or big drop with TCP stall).  It would be nice if
> > marginal aggregate bandwidth was dealt with by switching to a lower
> > bandwidth encoding, but too often this is not the case.  This doesn't
> > mean that some streaming formats don't manage to get this wrong and
> > end up delay sensitive.
> >
> > TCP needs buffering to function correctly.  Huge bufferbloat is bad
> > for TCP, particularly for small transfers that never get out of TCP
> > slow start and for short RTT flows.  For long RTT flows too little
> > buffer causes problems.
> >
> > [ aside: For example, if TCP starts with 4 segments at 1K segment
> > size, it will take 4 RTT to hit 64KB window, the typical max window
> > without TCP large window (TCPLW) option.  During that time, 60KB will
> > be sent.  After that 64KB will be sent each RTT.  With geographic RTT
> > is 70 msec (approximate US continental RTT due to finite speed of
> > light in fiber and fiber distance), 60 KB is sent in the first 280
> > msec and 64KB gets sent every 70 msec yielding 7 mb/s.  OTOH if there
> > is a server 2 msec RTT away (1 msec one way is 125mi =3D 200km), then
> > 60KB in first 8 msec and 256 Mb/s after that.  If there is 100 msec
> > buffer at a bottleneck, then this low RTT TCP flow will be slowed by a
> > factor of 50.  OTOH, if bottlenecks have a lot less than 1 RTT of
> > buffer, then the long TCP flows will get even further slowed. ]
> >
> > One of the effects of some buffer, but not excessive, is short RTT
> > flows which given the no-TCPLW max window get slowed down while longer
> > RTT are less affected.  This becomes more fair wrt to transfer rates
> > among TCP flows.  The same holds true if TCPLW gets turned on in
> > commodity gadgets and the commonly deploed max window increases, but
> > the number change.
> >
> > If the buffer grows a little and the deployed window sizes become the
> > limiting factor, then this is very light congestion with delay but
> > absolutely zero loss due to queue drops (not considering AQM for the
> > moment).
> >
> > Some uses of TCP increase the window to work better over long RTT.  It
> > takes a bit longer to hit the max window but the rate once it has been
> > hit is greater.  Setting TCP window large on short RTT flows is
> > counterproductive since one or a small number of flows can cause a
> > bottleneck on a slow provider link (ie: 10-100 Mb/s range typical of
> > home use).  On a LAN RTT can be well under 1 msec on Ethernet and
> > highly variable on WiFi.  On WiFi larger window can contribute to some
> > real trouble.  So best that the default window be changed.
> >
> > [ Note that the work on automatic sizing of tcp_sndbuf and scp_recvbuf
> > may create a tendency to saturate links as the window can go up to 2MB
> > with default parameters.  Has this hit consumer devices yet?  This
> > could be bad it this rolls out before widespread use of AQM. ]
> >
> > When a small amount of loss occurs, such as one or much less than the
> > current window size, TCP cuts the current window size in half and
> > retransmits the packet for the window in flight (ignoring selective
> > acknowledgment extension aka SACK for the moment).
> >
> > If the buffer is way too small, then a large amount of premature drop
> > occurs when the buffer limit is hit.  Lots of TCP flows slow down.
> > The long RTT flows slow down the most.  Some retransmission occurs
> > (which doesn't help congestion).  If there is a long period of drop
> > relative to a short RTT, then a entire window can be dropped and this
> > is terrible for TCP (slow start is initiated after delay based on an
> > estimate of RTT and RTT stdev, or 3 sec if RTT estimate is stale -
> > this is a TCP stall).  So with too little buffer some TCP flows get
> > hammered and stall.  TCP flows with long RTT tend to stall less but
> > are more sensitve to the frequency of drop events and can get
> > extremely slow due to successively cutting window in half and then
> > growing the window linearly rather than exponentially.
> >
> > With tiny buffers really bad things tend to happen.  The rate of
> > retransmission can drive goodput (the amount of non-retransmit traffic
> > per time) can drop substantially.  Long RTT flows can become
> > hopelessly slow.  Stalls become more common.  In the worst case (which
> > has been observed in a ISP network during a tiny buffer experiment
> > about a decade ago, details in private email) TCP synchronization can
> > occur, and utilization and goodput drop dramatically.
> >
> > A moderate amount of buffer is good for all TCP.  A large buffer is
> > good for long RTT TCP flows, particularly those that have increased
> > max window.  As mentioned before, any but a very small buffer is bad
> > for interactive real time applications.
> >
> > Enter AQM.  A large buffer can be used but with a lower target delay
> > and some form of AQM to introduce a low rate of isolated drops as
> > needed to slow the senders.  Avoiding queue tail drop events where a
> > lot of drops occur over an interval lowers the amount of
> > retransmission and avoids stalls.  Long RTT flows tend to get
> > penalized the most.
> >
> > Fairness is not great with a single queue and AQM but this is much
> > better than a single queue with either small or large buffer and tail
> > drop.  Fairness is greatly improved with some form of FQ or SFQ.
> >
> > Ideally with FQ each flow would get its own queue.  In practice this
> > is not the case but the situation is greatly improved.  A real time
> > flow, which is inherently rate limited, would see minimal delay and no
> > loss.  A short RTT flow would see a moderate increase in delay and a
> > low level of loss (ie: typically much less than 1%) enough to slow it
> > down enough to avoid congestion.  a long RTT flow would see a moderate
> > increase in delay and no loss if still running slower than the small
> > RTT flows.  This does wonders for fairness and provides the best
> > possible service for each service type.
> >
> > In practice, some FQ or SFQ queues have a mix of real time, low RTT
> > TCP, and high RTT TCP.  If any such queue is taking a smaller share
> > than other queues, delay is low and loss is low or zero.  If such a
> > queue is taking more than its share, then the situation is similar to
> > the single queue case.  Less flows end up in such a queue.  Cascaded
> > queues have been proposed and in some cases (no longer existing) have
> > been implemented.  In a cascaded SFQ scheme, the queues taking more
> > than their share are further subdivied.  Repeat the subdivision a few
> > times and you can end up with the large bandwidth contributors in
> > their own queue and getting a fair share of capacity.
> >
> > So excuse the length of this but solving bufferbloat is *not* a silver
> > bullet.  Not understanding that point and just making buffers really
> > small could result in an even worse situation than we have now.
> >
> > Curtis
> >
> > ps - Some aspects of this may not reflect WG direction.  IMHO- the
> > down sides of just making buffers smaller and/or setting low delay
> > targets may not be getting enough (or any) attention in the WG.  Maybe
> > discussion wouldn't hurt.


From nobody Sat Feb 28 17:42:46 2015
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1681A1B00 for <aqm@ietfa.amsl.com>; Sat, 28 Feb 2015 17:42:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 huX0ub00yTUt for <aqm@ietfa.amsl.com>; Sat, 28 Feb 2015 17:42:42 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 184801A1ADF for <aqm@ietf.org>; Sat, 28 Feb 2015 17:42:41 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t211gR3Y042620; Sat, 28 Feb 2015 20:42:27 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201503010142.t211gR3Y042620@maildrop31.somerville.occnc.com>
To: KK <kk@cs.ucr.edu>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Fri, 27 Feb 2015 18:16:12 -0800." <D11664D4.2EEC%kk@cs.ucr.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <42618.1425174147.1@harbor31.somerville.occnc.com>
Date: Sat, 28 Feb 2015 20:42:27 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/Llf2LcfTWKFNwOhgY6FprP1lcxk>
Cc: aqm@ietf.org, davecb@spamcop.net
Subject: Re: [aqm] Is bufferbloat a real problem?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
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: <http://www.ietf.org/mail-archive/web/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: Sun, 01 Mar 2015 01:42:44 -0000

In message <D11664D4.2EEC%kk@cs.ucr.edu>
KK writes:
 
> This could also be done by not having to depend on "loss" as the primary
> source of feedback...
>  
> -- 
> K. K. Ramakrishnan
> Professor
> Dept. of Computer Science and Engineering
> University of California, Riverside
> Rm. 332, Winston Chung Hall
> Tel: (951) 827-2480
>  
> Web Page: http://www.cs.ucr.edu/~kk/


DECBit was a disaster.

Is there something else you had in mind?

Curtis


From nobody Sat Feb 28 17:52:38 2015
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 890F71A1AFF for <aqm@ietfa.amsl.com>; Sat, 28 Feb 2015 17:52:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.312
X-Spam-Level: 
X-Spam-Status: No, score=-1.312 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_12=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 laP_4HwcCbOy for <aqm@ietfa.amsl.com>; Sat, 28 Feb 2015 17:52:36 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 9E4481A1ADF for <aqm@ietf.org>; Sat, 28 Feb 2015 17:52:36 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t211qQc5042719; Sat, 28 Feb 2015 20:52:26 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201503010152.t211qQc5042719@maildrop31.somerville.occnc.com>
To: davecb@spamcop.net
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Fri, 27 Feb 2015 21:45:19 -0500." <54F12BBF.4050503@rogers.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <42717.1425174746.1@harbor31.somerville.occnc.com>
Date: Sat, 28 Feb 2015 20:52:26 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/6g3gunmwE_yCZKK0BE1ILOAYaNI>
Cc: KK <kk@cs.ucr.edu>, aqm@ietf.org
Subject: Re: [aqm] Is bufferbloat a real problem?
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
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: <http://www.ietf.org/mail-archive/web/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: Sun, 01 Mar 2015 01:52:37 -0000

In message <54F12BBF.4050503@rogers.com>
David Collier-Brown writes:
 
> Yup!
>  
> Loss is a bit of like hitting someone with  a 2 x 4" as a clue-stick. It 
> hurts, but it sure does work!
>  
> --dave

ECN might be a touch gentler.  But loss on the order of 10^-4 or less
doesn't hurt too bad.

With classsic TCP (ie: newreno or older and anything newer but not
hyper-aggresive) the estimates of the amount of loss per D*BW product
done by Matt Mathis still hold.  Now if I could just remember what
that estimate was ... in any case you get to extremely tiny loss with
anything over a few Mb/s and it goes up with square of D*BW.

Hyper-aggresive TCP (ie: CUBIC) need to be hit a lot harder.  This is
where FQ/SFQ really comes in handy.

Curtis


> On 02/27/2015 09:16 PM, KK wrote:
> > This could also be done by not having to depend on "loss" as the primary
> > source of feedback...
>  
> On 2/27/15, 6:00 PM, "David Collier-Brown" <davec-b@rogers.com> wrote:
>  
> > IMHO, removing latency is the aim of FQ. Once done, buffer sizes can be
> > unbounded (save by price (;-))

