
From nobody Tue Aug  5 03:18:44 2014
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 6672A1B2964; Tue,  5 Aug 2014 03:18:40 -0700 (PDT)
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 Q371hKLwOZVu; Tue,  5 Aug 2014 03:18:38 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D02CD1B2959; Tue,  5 Aug 2014 03:18:38 -0700 (PDT)
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.6.2.p5
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140805101838.24981.28443.idtracker@ietfa.amsl.com>
Date: Tue, 05 Aug 2014 03:18:38 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/yykR2NWFf-Sqjs4yCjUwy5wdpdM
Cc: aqm@ietf.org
Subject: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Tue, 05 Aug 2014 10:18:40 -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-07.txt
	Pages           : 28
	Date            : 2014-08-05

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 largely repeats the recommendations of RFC 2309, and
   replaces these after 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-07

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


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 Tue Aug  5 03:24:01 2014
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 001591B296B for <aqm@ietfa.amsl.com>; Tue,  5 Aug 2014 03:24:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 7Cw66UO9W_JU for <aqm@ietfa.amsl.com>; Tue,  5 Aug 2014 03:23:58 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id B97491B296F for <aqm@ietf.org>; Tue,  5 Aug 2014 03:23:55 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 3AB062B41E7 for <aqm@ietf.org>; Tue,  5 Aug 2014 11:23:54 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Tue, 5 Aug 2014 11:23:54 +0100
Message-ID: <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <20140805101838.24981.28443.idtracker@ietfa.amsl.com>
References: <20140805101838.24981.28443.idtracker@ietfa.amsl.com>
Date: Tue, 5 Aug 2014 11:23:54 +0100
From: gorry@erg.abdn.ac.uk
To: aqm@ietf.org
User-Agent: SquirrelMail/1.4.22
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/r7EGq-ShDMAMJQXXhO9BXaOf2SQ
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Tue, 05 Aug 2014 10:24:01 -0000

I've posted a new revision of the draft. This contains a reworked
introduction by Fred & I, which seeks to clarify the intended status of
RFC 2309, and addresses all issues that we planned to address.  We think
this is ready to proceed.

Gorry

>
> 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-07.txt
> 	Pages           : 28
> 	Date            : 2014-08-05
>
> 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 largely repeats the recommendations of RFC 2309, and
>    replaces these after 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-07
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-recommendation-07
>
>
> 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/
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>


From nobody Fri Aug  8 06:25:06 2014
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 197911B2BF4 for <aqm@ietfa.amsl.com>; Fri,  8 Aug 2014 06:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.903
X-Spam-Level: 
X-Spam-Status: No, score=-6.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 dOhQaQ4O7smA for <aqm@ietfa.amsl.com>; Fri,  8 Aug 2014 06:25:03 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84DF81B2C1F for <aqm@ietf.org>; Fri,  8 Aug 2014 06:25:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.01,825,1400050800"; d="scan'208";a="180768990"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx12-out.netapp.com with ESMTP; 08 Aug 2014 06:25:01 -0700
Received: from HIOEXCMBX01-PRD.hq.netapp.com (10.122.105.34) by vmwexceht01-prd.hq.netapp.com (10.106.76.239) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 8 Aug 2014 06:24:44 -0700
Received: from HIOEXCMBX05-PRD.hq.netapp.com (10.122.105.38) by hioexcmbx01-prd.hq.netapp.com (10.122.105.34) with Microsoft SMTP Server (TLS) id 15.0.913.22; Fri, 8 Aug 2014 06:24:44 -0700
Received: from HIOEXCMBX05-PRD.hq.netapp.com ([::1]) by hioexcmbx05-prd.hq.netapp.com ([fe80::c1bc:1fd5:922:886d%21]) with mapi id 15.00.0913.011; Fri, 8 Aug 2014 06:24:44 -0700
From: "Scheffenegger, Richard" <rs@netapp.com>
To: "Bob Briscoe (bob.briscoe@bt.com)" <bob.briscoe@bt.com>, "John Leslie (john@jlc.net)" <john@jlc.net>
Thread-Topic: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.txt
Thread-Index: AQHPsJaig1GsqSTSHkOXUx43HvPaSpvCQuIAgARz/HA=
Date: Fri, 8 Aug 2014 13:24:43 +0000
Message-ID: <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp.com>
References: <20140805101838.24981.28443.idtracker@ietfa.amsl.com> <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk>
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/IVWPUwXJKQ8emxhb6qdzKNSDplU
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Fri, 08 Aug 2014 13:25:05 -0000

John, Bob,

had you the chance to review this new revision, which should address the co=
mments you had?

Best regards,

Richard Scheffenegger




> -----Original Message-----
> From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of gorry@erg.abdn.ac.uk
> Sent: Dienstag, 05. August 2014 12:24
> To: aqm@ietf.org
> Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.txt
>=20
> I've posted a new revision of the draft. This contains a reworked
> introduction by Fred & I, which seeks to clarify the intended status of
> RFC 2309, and addresses all issues that we planned to address.  We think
> this is ready to proceed.
>=20
> Gorry
>=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.
> >
> >         Title           : IETF Recommendations Regarding Active Queue
> > Management
> >         Authors         : Fred Baker
> >                           Godred Fairhurst
> > 	Filename        : draft-ietf-aqm-recommendation-07.txt
> > 	Pages           : 28
> > 	Date            : 2014-08-05
> >
> > Abstract:
> >    This memo presents recommendations to the Internet community
> >    concerning measures to improve and preserve Internet performance.  I=
t
> >    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 largely repeats the recommendations of RFC 2309, and
> >    replaces these after 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-07
> >
> > A diff from the previous version is available at:
> > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-aqm-recommendation-07
> >
> >
> > 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/
> >
> > _______________________________________________
> > 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


From nobody Fri Aug  8 07:58:41 2014
Return-Path: <john@jlc.net>
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 1E8621B2AF2 for <aqm@ietfa.amsl.com>; Fri,  8 Aug 2014 07:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 A6fXqy1M88zi for <aqm@ietfa.amsl.com>; Fri,  8 Aug 2014 07:58:37 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 393441B2B07 for <aqm@ietf.org>; Fri,  8 Aug 2014 07:58:37 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 09F5FC94A8; Fri,  8 Aug 2014 10:58:35 -0400 (EDT)
Date: Fri, 8 Aug 2014 10:58:35 -0400
From: John Leslie <john@jlc.net>
To: "Scheffenegger, Richard" <rs@netapp.com>
Message-ID: <20140808145834.GF45982@verdi>
References: <20140805101838.24981.28443.idtracker@ietfa.amsl.com> <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk> <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp.com>
User-Agent: Mutt/1.4.1i
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/GFz0MwNvj6ulK_P6GRTQW3q5IRw
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "aqm@ietf.org" <aqm@ietf.org>, "Bob Briscoe \(bob.briscoe@bt.com\)" <bob.briscoe@bt.com>, "John Leslie \(john@jlc.net\)" <john@jlc.net>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Fri, 08 Aug 2014 14:58:39 -0000

Scheffenegger, Richard <rs@netapp.com> wrote:
> 
> had you the chance to review this new revision, which should address the comments you had?

   I expect to defer to Bob on this; but I read quite a few subtle changes
to 2309 in the restatement here, none of which I believe represent true
consensus of this WG (because they're not our intended subject).

   This is what I was trying to avoid by my suggestion of text to "update"
instead of "obsolete" 2309.

   There's no real show-stopper here -- folks undoubtedly will ignore
these for the most part.

   Nonetheless, it still bothers me to have no definition for terms like
"network device" and "congestive collapse". I tried to roughly define
"network device" in my suggested text; and avoided "congestion collapse"
(the term used in 2309) entirely.

--
John Leslie <john@jlc.net>


From nobody Fri Aug  8 09:04:40 2014
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 BA9B51B2C53 for <aqm@ietfa.amsl.com>; Fri,  8 Aug 2014 09:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 6q-6qPvjTZ5L for <aqm@ietfa.amsl.com>; Fri,  8 Aug 2014 09:04:34 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 0099C1B28DC for <aqm@ietf.org>; Fri,  8 Aug 2014 09:04:33 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 6F06C2B435B; Fri,  8 Aug 2014 17:04:31 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Fri, 8 Aug 2014 17:04:31 +0100
Message-ID: <e56b46c9c6e1d4424ad7e1560fae57b8.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <20140808145834.GF45982@verdi>
References: <20140805101838.24981.28443.idtracker@ietfa.amsl.com> <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk> <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp.com> <20140808145834.GF45982@verdi>
Date: Fri, 8 Aug 2014 17:04:31 +0100
From: gorry@erg.abdn.ac.uk
To: "John Leslie" <john@jlc.net>
User-Agent: SquirrelMail/1.4.22
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/bFz2iT6ezHaZN7NaSSZ6W331s-o
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "Scheffenegger, Richard" <rs@netapp.com>, "aqm@ietf.org" <aqm@ietf.org>, "Bob Briscoe \(bob.briscoe@bt.com\)" <bob.briscoe@bt.com>, "John Leslie \(john@jlc.net\)" <john@jlc.net>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Fri, 08 Aug 2014 16:04:38 -0000

> Scheffenegger, Richard <rs@netapp.com> wrote:
>>
>> had you the chance to review this new revision, which should address the
>> comments you had?
>
>    I expect to defer to Bob on this;
>
>but I read quite a few subtle changes
> to 2309 in the restatement here, none of which I believe represent true
> consensus of this WG (because they're not our intended subject).
>
>    This is what I was trying to avoid by my suggestion of text to "update"
> instead of "obsolete" 2309.
>
>    There's no real show-stopper here -- folks undoubtedly will ignore
> these for the most part.
>
>    Nonetheless, it still bothers me to have no definition for terms like
> "network device" and "congestive collapse". I tried to roughly define
> "network device" in my suggested text; and avoided "congestion collapse"
> (the term used in 2309) entirely.
>
> --
> John Leslie <john@jlc.net>
>
If you see ambiguity in "network device", by all means send us propose
text again (I must have missed that detail.

Apart from that, does this mean you have no specific comments on this
version?

Gorry



From nobody Sat Aug  9 04:28:05 2014
Return-Path: <john@jlc.net>
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 97F091B27B6 for <aqm@ietfa.amsl.com>; Sat,  9 Aug 2014 04:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 myKOAEUxxzMB for <aqm@ietfa.amsl.com>; Sat,  9 Aug 2014 04:28:00 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 333061B27B7 for <aqm@ietf.org>; Sat,  9 Aug 2014 04:28:00 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 0DE8FC94A8; Sat,  9 Aug 2014 07:27:48 -0400 (EDT)
Date: Sat, 9 Aug 2014 07:27:48 -0400
From: John Leslie <john@jlc.net>
To: gorry@erg.abdn.ac.uk
Message-ID: <20140809112747.GI45982@verdi>
References: <20140805101838.24981.28443.idtracker@ietfa.amsl.com> <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk> <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp.com> <20140808145834.GF45982@verdi> <e56b46c9c6e1d4424ad7e1560fae57b8.squirrel@www.erg.abdn.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e56b46c9c6e1d4424ad7e1560fae57b8.squirrel@www.erg.abdn.ac.uk>
User-Agent: Mutt/1.4.1i
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/Azks7ZbMPxvZiK_KS0KZ8jlZ4ok
Cc: "Scheffenegger, Richard" <rs@netapp.com>, "aqm@ietf.org" <aqm@ietf.org>, "Bob Briscoe \(bob.briscoe@bt.com\)" <bob.briscoe@bt.com>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Sat, 09 Aug 2014 11:28:03 -0000

gorry@erg.abdn.ac.uk <gorry@erg.abdn.ac.uk> wrote:
> 
> If you see ambiguity in "network device", by all means send us propose
> text again (I must have missed that detail.

   You're welcome to my text from July 2:

http://www.ietf.org/mail-archive/web/aqm/current/msg00701.html

   I don't know whether that matches your intent: I have no desire to
change your intent.

> Apart from that, does this mean you have no specific comments on this
> version?

   If Bob makes any fuss about "congestive collapse" I support him.
Otherwise, I make a strong request that you add a definition of that
term: I have no idea what you mean that's consistent with what you
wrote and the way the Internet works.

   I do remain convinced that the charter wording calling for
obsoleting RFC 2309 was ill-advised, and is not what this WG actually
chose to do. I'd much prefer to fix the charter milestone language;
but I detect no enthusiasm for that. I'll settle for being listed
"in the rough" in the Shepherd's writeup.

   My thorough review was of version -05. Since then, I note the
change in the Abstract from "updated" to "and replaces these"
[recommendations of 2309]. I don't see any particular reason for
that change, but won't fuss over it if nobody else cares.

   I note the addition of a section header for "1.1 Congestion
Collapse" which correctly includes "fix for Internet meltdown"; but
I think the switching between "Congestion Collapse" and "congestive
collapse" is confusing. ("Congestion Collapse" is a well-defined
term of art; and wouldn't need a definiton unless you think you
can write one which will make the usage of that term correct in
this document.)

   Most of my comments about version -05 can simply be listed as
"ignored" or perhaps "considered and ignored"; but a few never made
it onto the list because I thought the change from "obsoletes" to
"updates" needed to be discussed first.

   In Section 3 subsection 3, I would prefer that we not perpetuate
the idea that flows must be "TCP-friendly". While there are indeed
cases of unfriendly-to-TCP flows, that really isn't an AQM issue.

   In Section 4.6, in talking of "elastic transport congestion
control", I fail to see how this relates to AQM; and I'd prefer
not jawboning about how transports "should" function. (This sort
of text would be entirely proper in an IRTF document; but we're
now doing an IETF BCP concerned with queue management in network
devices.)

   Section 4.7 returns to 2309's "need further research" conclusion.
It seems to me out-of-place to list these things in a BCP.

   In Section 8 Acknowledgements, I don't think it correct to say,
"This is an edited version of that document". (I agree it started
that way, but I find that not an acceptable basis for a BCP.)

====

   You have every right to say I should have raised these points
earlier; but that's a poor substitute for evaluating their merit.
It is the intent of a Working Group Last Call to solicit thorough
reviews by WG participants -- and follow through on those with
merit.

   The habit of tossing the WGLC comments at the authors and
marginalizing any further comments to the authors' response is
a bad habit. I wish we would break it.

--
John Leslie <john@jlc.net>


From nobody Mon Aug 11 02:09:41 2014
Return-Path: <bob.briscoe@bt.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 EFA781A0391 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 02:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.269
X-Spam-Level: 
X-Spam-Status: No, score=-3.269 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.668, 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 SWPBKzr0Qsee for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 02:09:37 -0700 (PDT)
Received: from hubrelay-by-03.bt.com (hubrelay-by-03.bt.com [62.7.242.139]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43D7C1A0392 for <aqm@ietf.org>; Mon, 11 Aug 2014 02:09:36 -0700 (PDT)
Received: from EVMHR72-UKRD.domain1.systemhost.net (10.36.3.110) by EVMHR03-UKBR.bt.com (10.216.161.35) with Microsoft SMTP Server (TLS) id 8.3.348.2; Mon, 11 Aug 2014 10:09:32 +0100
Received: from EPHR02-UKIP.domain1.systemhost.net (147.149.100.81) by EVMHR72-UKRD.domain1.systemhost.net (10.36.3.110) with Microsoft SMTP Server (TLS) id 8.3.348.2; Mon, 11 Aug 2014 10:09:34 +0100
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR02-UKIP.domain1.systemhost.net (147.149.100.81) with Microsoft SMTP Server id 14.3.181.6; Mon, 11 Aug 2014 10:09:32 +0100
Received: from BTP075694.jungle.bt.co.uk ([10.111.123.255])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id s7B99U7v020486;	Mon, 11 Aug 2014 10:09:31 +0100
Message-ID: <201408110909.s7B99U7v020486@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 11 Aug 2014 10:09:30 +0100
To: "Scheffenegger, Richard" <rs@netapp.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp .com>
References: <20140805101838.24981.28443.idtracker@ietfa.amsl.com> <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk> <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/X0t1We-Bd00PowvfhVuw6RX4uPE
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Mon, 11 Aug 2014 09:09:40 -0000

RIchard,

All my points have been addressed, except one (below). Thank you, Fred & Gorry.


The one about the 3 types of flows has missed my point in a couple of 
ways, (A) & (B) explained below.


Section 3 divides flows into 3 types:
(1) TCP Friendly flows,
(2) unresponsive flows, i.e., flows that do not slow down when 
congestion occurs, and
(3) flows that are responsive but are not TCP-friendly.


A) It might seem obvious to some that "not friendly", means "less 
than friendly", but given the definition of TCP-friendly, "not 
TCP-friendly" is ambiguous and could also mean "more friendly than 
TCP" (e.g. scavenger transports).

Therefore, I suggest changing "not TCP-friendly" and 
"Non-TCP-friendly"  to "less responsive than TCP-Friendly" or some 
similar phrase.

B) My main point was that (1) and (2) are points on a spectrum, and 3 
is a region that spans the whole of the spectrum between these 
points. Then the rest of the doc talks about all three as if they are 
in the same set of types.

That's not a useful classification. Previous docs in the RFC series 
have been careful not to overclaim the importance of precise 
TCP-friendliness. It's not helpful to suggest that anything to the 
left of TCP-Friendly "clearly poses a threat to future Internet 
stability". It would be more useful to describe it as a spectrum with 
two reference points on it (as shown). Then say the closer to the 
unresponsive end that a flow is, the more it could pose a threat to 
the performance of other flows during times of excessive contention.

           Unresponsive                     TCP-Friendly
           |                                     |
           v                                     v
5 5 5 5 5 2 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 1 4 4 4 4 4 4 4 4 4 4 
4 4 4 4 4 4 4 4
<-Beyond-> <---responsive but less than TCP----> <--responsive but 
more than TCP--->
Unrespons-
   ive

In fact, there is (fairly common) behaviour to the left of 
unresponsive, where a flow adds redundancy. By turning the 
classification into a spectrum, it would be fairly natural to include 
that as well.

Other than this, I don't want to tamper with the text on whether AQMs 
have a role in flow isolation, because it does well to leave the question open.


C) Also (a new point I didn't mention before), the alarmist language 
in two places is rather over-the-top:
* "The last two classes contain more aggressive flows that pose 
significant threats to Internet performance"
* "The projected increase in the fraction of total Internet traffic 
for more aggressive flows in classes 2 and 3 clearly poses a threat 
to future Internet stability"

Suggested text, respectively:
* "The last two classes contain more aggressive flows that can pose 
significant threats to Internet performance"
* "The projected increase in the fraction of total Internet traffic 
for more aggressive flows in classes 2 and 3 could pose a threat to 
future Internet performance"

Note, I've also suggested changing 'stability' to 'performance' - 
this doc has nothing to do with oscillations, etc.

For instance, does VoIP pose a significant threat to Internet 
performance? Nah. Still in some places maybe, but the Internet is 
generally coping. When the Internet was growing up we thought VoIP 
might cause collapse, but our concerns have waned as link capacities 
have grown. So the perception of threat depends on the bit-rate of 
the flow relative to average link capacities.

Responsiveness is important, but I believe it is OK for unresponsive 
flows that are small in relative terms to only be responsive at very 
long timescales (even solely at flow set up - self-admission 
control). This even applies to aggregates of unresponsive flows, 
because they will tend to be deployed where even the aggregate is 
small relative to the link capacity. See 
http://tools.ietf.org/html/draft-ietf-pwe3-congcons-02.pdf (comments 
to the PWE3 list pls).



Bob

At 14:24 08/08/2014, Scheffenegger, Richard wrote:
>John, Bob,
>
>had you the chance to review this new revision, which should address 
>the comments you had?
>
>Best regards,
>
>Richard Scheffenegger
>
>
>
>
> > -----Original Message-----
> > From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of gorry@erg.abdn.ac.uk
> > Sent: Dienstag, 05. August 2014 12:24
> > To: aqm@ietf.org
> > Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.txt
> >
> > I've posted a new revision of the draft. This contains a reworked
> > introduction by Fred & I, which seeks to clarify the intended status of
> > RFC 2309, and addresses all issues that we planned to address.  We think
> > this is ready to proceed.
> >
> > Gorry
> >
> > >
> > > 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-07.txt
> > >     Pages           : 28
> > >     Date            : 2014-08-05
> > >
> > > 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 largely repeats the recommendations of RFC 2309, and
> > >    replaces these after 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-07
> > >
> > > A diff from the previous version is available at:
> > > http://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-recommendation-07
> > >
> > >
> > > 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/
> > >
> > > _______________________________________________
> > > 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
>
>_______________________________________________
>aqm mailing list
>aqm@ietf.org
>https://www.ietf.org/mailman/listinfo/aqm

________________________________________________________________
Bob Briscoe,                                                  BT 


From nobody Mon Aug 11 02:50:50 2014
Return-Path: <dros@simula.no>
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 D3B761A03A0 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 02:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 UzP0K48-G9hb for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 02:50:47 -0700 (PDT)
Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACED61A03A4 for <aqm@ietf.org>; Mon, 11 Aug 2014 02:50:46 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id l18so8141244wgh.13 for <aqm@ietf.org>; Mon, 11 Aug 2014 02:50:45 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from:date:cc :content-transfer-encoding:message-id:references:to; bh=EXGQA75xhkA5WteH3evL0HLQQSb1wdJq8ycdkv3kLI4=; b=BbGlw3F+CwYangKVdqjTr93LDAD2fd/FsG/FeGJ4HBxDqq+4vfDE0Wvz51UUoYg/0Q D255IK4P1DWgSEE7F4JiiUPZrgzUmntdHYPY78UnJLkTQfktfQ+8lAoUNZdu8GDCQpDb InKKgp3t26Amm1Wfcv/YJk8FrFpI11OUITox9Ot3NKv1k+pILdjJSo6pG+AJY7O2ye7K 7sPMQWjjUiK2J6c1FcgvWQjn5IrR1oCUfsP97n8OISrPxJTK+2ud+qz4AH3+YTGGlJty PV8jxx/vOlBC294Z6n2sPjsn21tZ+miP+VqhmTbMftOQGI/dSJAJQMJGys9ygTbJEFb2 7ajg==
X-Gm-Message-State: ALoCoQkDFiqWo3S/shQeub7kYx7LNnwzxLTQSh4vzwZQ/NSLmqvOKjC46zxCpM5ryd3fGSBOj1Pr
X-Received: by 10.194.78.170 with SMTP id c10mr25681159wjx.22.1407750645296; Mon, 11 Aug 2014 02:50:45 -0700 (PDT)
Received: from [192.168.0.88] (ARennes-653-1-299-226.w109-218.abo.wanadoo.fr. [109.218.138.226]) by mx.google.com with ESMTPSA id vn10sm245252wjc.28.2014.08.11.02.50.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Aug 2014 02:50:44 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: David Ros <dros@simula.no>
Date: Mon, 11 Aug 2014 11:50:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <06ED6855-4053-489F-AC60-4E88BF8141A6@simula.no>
References: <20140811093358.6685.2342.idtracker@ietfa.amsl.com>
To: aqm@ietf.org
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/f4uE-C9nvCLnfSvoCNb8-P8BKx0
Cc: Nicolas Kuhn <nicolas.kuhn@telecom-bretagne.eu>, Naeem Khademi <naeemk@ifi.uio.no>, "Preethi Natarajan \(prenatar\)" <prenatar@cisco.com>
Subject: [aqm] Fwd: New Version Notification for draft-kuhn-aqm-eval-guidelines-02.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: Mon, 11 Aug 2014 09:50:49 -0000

Dear all,

We've posted an update of draft-kuhn-aqm-eval-guidelines. It's a minor =
update:

- a couple of nits fixed,
- title changed from "evaluation guidelines" to "characterisation =
guidelines" as suggested by Fred Baker,
- tries to separate more clearly AQM from scheduling,
- changes on the ECN-related text (it now points to =
draft-ietf-aqm-recommendation).

Feedback welcome.

Thanks,

David

Begin forwarded message:

> From: internet-drafts@ietf.org
> Subject: New Version Notification for =
draft-kuhn-aqm-eval-guidelines-02.txt
> Date: 11 Aug 2014 11:33:58 GMT+2
> To: Nicolas Kuhn <nicolas.kuhn@telecom-bretagne.eu>, "David Ros" =
<dros@simula.no>, David Ros <dros@simula.no>, "Preethi Natarajan" =
<prenatar@cisco.com>, "Naeem Khademi" <naeemk@ifi.uio.no>, "Nicolas =
Kuhn" <nicolas.kuhn@telecom-bretagne.eu>, Preethi Natarajan =
<prenatar@cisco.com>, Naeem Khademi <naeemk@ifi.uio.no>
>=20
>=20
> A new version of I-D, draft-kuhn-aqm-eval-guidelines-02.txt
> has been successfully submitted by David Ros and posted to the
> IETF repository.
>=20
> Name:		draft-kuhn-aqm-eval-guidelines
> Revision:	02
> Title:		AQM Characterization Guidelines
> Document date:	2014-08-11
> Group:		Individual Submission
> Pages:		23
> URL:            =
http://www.ietf.org/internet-drafts/draft-kuhn-aqm-eval-guidelines-02.txt
> Status:         =
https://datatracker.ietf.org/doc/draft-kuhn-aqm-eval-guidelines/
> Htmlized:       =
http://tools.ietf.org/html/draft-kuhn-aqm-eval-guidelines-02
> Diff:           =
http://www.ietf.org/rfcdiff?url2=3Ddraft-kuhn-aqm-eval-guidelines-02
>=20
> Abstract:
>   Unmanaged large buffers in today's networks have given rise to a =
slew
>   of performance issues.  These performance issues can be addressed by
>   some form of Active Queue Management (AQM), optionally in =
combination
>   with a packet scheduling scheme such as fair queuing.  The IETF AQM
>   and packet scheduling working group was formed to standardize AQM
>   schemes that are robust, easily implemented, and successfully
>   deployed in today's networks.  This document describes various
>   criteria for performing precautionary characterizations of AQM
>   proposals.  This document also helps in ascertaining whether any
>   given AQM proposal should be taken up for standardization by the AQM
>   WG.
>=20
>=20
>=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
> The IETF Secretariat
>=20


From nobody Mon Aug 11 06:46:07 2014
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 00D651A02D9 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 06:46:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level: 
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 Hxlh_WoBG0Ev for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 06:45:59 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 6381A1A02F6 for <aqm@ietf.org>; Mon, 11 Aug 2014 06:45:59 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 7E4DD2B427B; Mon, 11 Aug 2014 14:45:58 +0100 (BST)
Received: from 139.133.204.3 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Mon, 11 Aug 2014 14:45:58 +0100
Message-ID: <ff5e927945a46a39559fbb25b0ede6bc.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <201408110909.s7B99U7v020486@bagheera.jungle.bt.co.uk>
References: <20140805101838.24981.28443.idtracker@ietfa.amsl.com> <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk> <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp.com> <201408110909.s7B99U7v020486@bagheera.jungle.bt.co.uk>
Date: Mon, 11 Aug 2014 14:45:58 +0100
From: gorry@erg.abdn.ac.uk
To: "Bob Briscoe" <bob.briscoe@bt.com>
User-Agent: SquirrelMail/1.4.22
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/9_lEKkd2gQmP6HunawQuH2TI6vs
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "Scheffenegger, Richard" <rs@netapp.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Mon, 11 Aug 2014 13:46:06 -0000

Bob, I see several issues that can easily be resolved by a very minor
revision to take care of this, and my suggested plan is below:

...

> The one about the 3 types of flows has missed my point in a
> couple of  ways, (A) & (B) explained below.

> Section 3 divides flows into 3 types:
> (1) TCP Friendly flows,
> (2) unresponsive flows, i.e., flows that do not slow
> down when congestion occurs, and
> (3) flows that are responsive but are not TCP-friendly.

> A) It might seem obvious to some that "not friendly", means "less
> than friendly", but given the definition of TCP-friendly, "not
> TCP-friendly" is ambiguous and could also mean "more friendly
> than TCP" (e.g. scavenger transports).

> Therefore, I suggest changing "not TCP-friendly" and
>”Non-TCP-friendly"  to "less responsive than TCP-Friendly" or some
>similar phrase.
>

+GF: Perfect, I like this a lot, and can use "less responsive than TCP" as
a basis for making this better.

> B) My main point was that (1) and (2) are points on a spectrum, and
> 3 is a region that spans the whole of the spectrum between these
> points. Then the rest of the doc talks about all three as if they
> are in the same set of types.
>
+GF: If we change the language above, we can explicitly say this, and I’ll
add text.

————>

> That's not a useful classification. Previous docs in the RFC series
> have been careful not to overclaim the importance of precise
> TCP-friendliness. It's not helpful to suggest that anything to the
> left of TCP-Friendly "clearly poses a threat to future Internet
> stability". It would be more useful to describe it as a spectrum
> with two reference points on it (as shown).

> Then say the closer to the
> unresponsive end that a flow is, the more it could pose a threat to
> the performance of other flows during times of excessive contention.
>
>          Unresponsive                     TCP-Friendly
>           |                                     |
>           v                                     v
> 5 5 5 5 5 2 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 1 4 4 4 4 4 4 4 4 4 4
4 4 4 4 4 4 4 4
<-Beyond-> <---responsive but less than TCP----> <--responsive but
more than TCP--->
Unrespons-
   ive

> In fact, there is (fairly common) behaviour to the left of
> unresponsive, where a flow adds redundancy. By turning the
> classification into a spectrum, it would be fairly natural
> to include that as well.
>
+GF: I think the new test should be closer, and I added this to the
"unresponsive" case to explicitly call this out:

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.

> Other than this, I don't want to tamper with the text on whether AQMs
> have a role in flow isolation, because it does well to leave the
> question open.
>
+GF: That was intended, good.

> C) Also (a new point I didn't mention before), the alarmist
> language in two places is rather over-the-top:
> * "The last two classes contain more aggressive flows that pose
> significant threats to Internet performance"
> * "The projected increase in the fraction of total Internet traffic
> for more aggressive flows in classes 2 and 3 clearly poses a threat
> to future Internet stability"
>
> Suggested text, respectively:
> * "The last two classes contain more aggressive flows
> that can pose  significant threats to Internet performance"
> * "The projected increase in the fraction of total Internet
> traffic for more aggressive flows in classes 2 and 3 could
> pose a threat to
> future Internet performance"

> Note, I've also suggested changing 'stability' to 'performance' -
> this doc has nothing to do with oscillations, etc.

+GF: Agree, this text was directly taken from RFC 2309… let's change it
... but how about “dependable performance”? (i'd like to capture that this
isn't performance tuning - but more expectation of performance.

> For instance, does VoIP pose a significant threat to
> Internet  performance? Nah. Still in some places maybe,
> but the Internet is generally coping. When the Internet was
> growing up we thought VoIP might cause collapse, but our
> concerns have waned as link capacities have grown. So the
> perception of threat depends on the bit-rate of
> the flow relative to average link capacities.
>

——

> Responsiveness is important, but I believe it is OK for unresponsive
> flows that are small in relative terms to only be responsive at very
> long timescales (even solely at flow set up - self-admission
> control). This even applies to aggregates of unresponsive flows,
> because they will tend to be deployed where even the aggregate is
> small relative to the link capacity.
> See http://tools.ietf.org/html/draft-ietf-pwe3-congcons-02.pdf
> (comments to the PWE3 list pls).

+GF: I don’t see this needed in this draft.

> Bob

——

+GF: I’m also considering replacing /congestive collapse/ by /congestion
collapse/ which seems a more common term, as noted by John L.

+GF: And I'll rewrite the Acknowledgement text relating to RFC 2309, as
noted by John L.



From nobody Mon Aug 11 07:09:05 2014
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 3AF891A01A5 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:08:56 -0700 (PDT)
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 GbA7tYnNry85 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:08:54 -0700 (PDT)
Received: from atl4mhob11.myregisteredsite.com (atl4mhob11.myregisteredsite.com [209.17.115.49]) by ietfa.amsl.com (Postfix) with ESMTP id 225B01A03D0 for <aqm@ietf.org>; Mon, 11 Aug 2014 07:08:54 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob11.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s7BE8qQX001979 for <aqm@ietf.org>; Mon, 11 Aug 2014 10:08:52 -0400
Received: (qmail 6899 invoked by uid 0); 11 Aug 2014 14:08:52 -0000
X-TCPREMOTEIP: 69.81.143.143
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.108?) (wes@mti-systems.com@69.81.143.143) by 0 with ESMTPA; 11 Aug 2014 14:08:52 -0000
Message-ID: <53E8CE68.5090004@mti-systems.com>
Date: Mon, 11 Aug 2014 10:08:40 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: gorry@erg.abdn.ac.uk, Bob Briscoe <bob.briscoe@bt.com>
References: <20140805101838.24981.28443.idtracker@ietfa.amsl.com> <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk> <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp.com> <201408110909.s7B99U7v020486@bagheera.jungle.bt.co.uk> <ff5e927945a46a39559fbb25b0ede6bc.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <ff5e927945a46a39559fbb25b0ede6bc.squirrel@www.erg.abdn.ac.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/QDzYvLoSkCJ-7OzVvg4pKR_tENQ
Cc: "Scheffenegger, Richard" <rs@netapp.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Mon, 11 Aug 2014 14:08:56 -0000

On 8/11/2014 9:45 AM, gorry@erg.abdn.ac.uk wrote:
> 
>> Responsiveness is important, but I believe it is OK for unresponsive
>> flows that are small in relative terms to only be responsive at very
>> long timescales (even solely at flow set up - self-admission
>> control). This even applies to aggregates of unresponsive flows,
>> because they will tend to be deployed where even the aggregate is
>> small relative to the link capacity.
>> See http://tools.ietf.org/html/draft-ietf-pwe3-congcons-02.pdf
>> (comments to the PWE3 list pls).
> 
> +GF: I don’t see this needed in this draft.
> 


I agree; this BCP is about AQM behavior, and not the right place to
hide recommendations or requirements on flow sources.


> +GF: I’m also considering replacing /congestive collapse/ by /congestion
> collapse/ which seems a more common term, as noted by John L.


I agree with this too.


-- 
Wes Eddy
MTI Systems


From nobody Mon Aug 11 07:25:28 2014
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 C1EBC1A03E9 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:25:25 -0700 (PDT)
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 VAkewVGrBOCK for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:25:23 -0700 (PDT)
Received: from atl4mhob10.myregisteredsite.com (atl4mhob10.myregisteredsite.com [209.17.115.48]) by ietfa.amsl.com (Postfix) with ESMTP id 171191A03F2 for <aqm@ietf.org>; Mon, 11 Aug 2014 07:25:23 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob10.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s7BEPLII011084 for <aqm@ietf.org>; Mon, 11 Aug 2014 10:25:21 -0400
Received: (qmail 1274 invoked by uid 0); 11 Aug 2014 14:25:21 -0000
X-TCPREMOTEIP: 69.81.143.143
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.108?) (wes@mti-systems.com@69.81.143.143) by 0 with ESMTPA; 11 Aug 2014 14:25:21 -0000
Message-ID: <53E8D248.4050509@mti-systems.com>
Date: Mon, 11 Aug 2014 10:25:12 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "aqm@ietf.org" <aqm@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/0N6r1u69pZl7CUw65_sV1xhciqY
Subject: [aqm] adoption call: draft-baker-aqm-sfq-implementation
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, 11 Aug 2014 14:25:26 -0000

Based on feedback we've seen, it looks like there is significant
value in progressing draft-baker-aqm-sfq-implementation as a
working group document.

Assuming there is WG consensus and we have AD-approval, we would
like to add a milestone to develop this towards an Informational
RFC within ~6 months.

Please provide any comments, questions, support, or criticism for
adopting this within the next few weeks.

-- 
Wes Eddy
MTI Systems


From nobody Mon Aug 11 07:26:22 2014
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 2D0E91A03F0 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:26:21 -0700 (PDT)
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 kmXKNjSUgWrA for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:26:20 -0700 (PDT)
Received: from atl4mhob06.myregisteredsite.com (atl4mhob06.myregisteredsite.com [209.17.115.44]) by ietfa.amsl.com (Postfix) with ESMTP id 156811A03E5 for <aqm@ietf.org>; Mon, 11 Aug 2014 07:26:20 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.203]) by atl4mhob06.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s7BEQIlU025578 for <aqm@ietf.org>; Mon, 11 Aug 2014 10:26:18 -0400
Received: (qmail 12023 invoked by uid 0); 11 Aug 2014 14:26:18 -0000
X-TCPREMOTEIP: 69.81.143.143
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.108?) (wes@mti-systems.com@69.81.143.143) by 0 with ESMTPA; 11 Aug 2014 14:26:18 -0000
Message-ID: <53E8D281.8040705@mti-systems.com>
Date: Mon, 11 Aug 2014 10:26:09 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "aqm@ietf.org" <aqm@ietf.org>
References: <53E8D248.4050509@mti-systems.com>
In-Reply-To: <53E8D248.4050509@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/abvSojCxpUwCvpbJYxb5An-ttHI
Subject: Re: [aqm] adoption call: draft-baker-aqm-sfq-implementation
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, 11 Aug 2014 14:26:21 -0000

For reference, the draft is at:
http://tools.ietf.org/html/draft-baker-aqm-sfq-implementation-00

On 8/11/2014 10:25 AM, Wesley Eddy wrote:
> Based on feedback we've seen, it looks like there is significant
> value in progressing draft-baker-aqm-sfq-implementation as a
> working group document.
> 
> Assuming there is WG consensus and we have AD-approval, we would
> like to add a milestone to develop this towards an Informational
> RFC within ~6 months.
> 
> Please provide any comments, questions, support, or criticism for
> adopting this within the next few weeks.
> 


-- 
Wes Eddy
MTI Systems


From nobody Mon Aug 11 07:32:04 2014
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 F38E01A03D8 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.553
X-Spam-Level: 
X-Spam-Status: No, score=-0.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347] 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 CQhZm7MtO6OJ for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:32:02 -0700 (PDT)
Received: from atl4mhob16.myregisteredsite.com (atl4mhob16.myregisteredsite.com [209.17.115.109]) by ietfa.amsl.com (Postfix) with ESMTP id 247621A03D0 for <aqm@ietf.org>; Mon, 11 Aug 2014 07:32:02 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.208]) by atl4mhob16.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s7BEW0PX007583 for <aqm@ietf.org>; Mon, 11 Aug 2014 10:32:00 -0400
Received: (qmail 14658 invoked by uid 0); 11 Aug 2014 14:32:00 -0000
X-TCPREMOTEIP: 69.81.143.143
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.108?) (wes@mti-systems.com@69.81.143.143) by 0 with ESMTPA; 11 Aug 2014 14:31:59 -0000
Message-ID: <53E8D3C9.4050100@mti-systems.com>
Date: Mon, 11 Aug 2014 10:31:37 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "aqm@ietf.org" <aqm@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/maQawrrCfzVuOKXEvcuKp2D8LeU
Subject: [aqm] adoption call: draft-kuhn-aqm-eval-guidelines
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, 11 Aug 2014 14:32:03 -0000

We have a milestone in the charter to produce an Informational RFC
on AQM evaluation guidelines.

We believe there is only one draft that has been targeting this so
far, that folks are reading and commenting on it, and that the
comments recently have been more about tweaking it than major rework.

We'd like to adopt draft-kuhn-aqm-eval-guidelines as a working group
item and develop it into an Informational RFC:

http://tools.ietf.org/html/draft-kuhn-aqm-eval-guidelines-02

Please let use know in the next few weeks if you have any comments,
questions, concerns, etc. about this.

-- 
Wes Eddy
MTI Systems


From nobody Mon Aug 11 07:36:13 2014
Return-Path: <michawe@ifi.uio.no>
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 DB5AB1A03D0 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:36:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level: 
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.668] 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 Nkoj_bVT8LIf for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:36:08 -0700 (PDT)
Received: from mail-out4.uio.no (mail-out4.uio.no [IPv6:2001:700:100:10::15]) (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 D4FA21A0386 for <aqm@ietf.org>; Mon, 11 Aug 2014 07:36:07 -0700 (PDT)
Received: from mail-mx2.uio.no ([129.240.10.30]) by mail-out4.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1XGqhh-0005fT-U0; Mon, 11 Aug 2014 16:36:05 +0200
Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx2.uio.no with esmtpsa (TLSv1:AES128-SHA:128) user michawe (Exim 4.80) (envelope-from <michawe@ifi.uio.no>) id 1XGqhh-0004dg-HE; Mon, 11 Aug 2014 16:36:05 +0200
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <53E8D3C9.4050100@mti-systems.com>
Date: Mon, 11 Aug 2014 16:36:04 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <5DAA5307-2DE8-4D9B-BB46-AF41907A8980@ifi.uio.no>
References: <53E8D3C9.4050100@mti-systems.com>
To: Wesley Eddy <wes@mti-systems.com>
X-Mailer: Apple Mail (2.1283)
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 2 msgs/h 1 sum rcpts/h 6 sum msgs/h 3 total rcpts 19111 max rcpts/h 44 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-6.1, required=5.0, autolearn=disabled, RP_MATCHES_RCVD=-1.051, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO,  uiouri=NO)
X-UiO-Scanned: 027060EFB9C6403BC540B6189D413CA5AFD2AE43
X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -60 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 5726 max/h 17 blacklist 0 greylist 0 ratelimit 0
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/JHZmW30uC6rquc-6DreIE1dhKFc
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] adoption call: draft-kuhn-aqm-eval-guidelines
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, 11 Aug 2014 14:36:10 -0000

On 11. aug. 2014, at 16:31, Wesley Eddy wrote:

> We have a milestone in the charter to produce an Informational RFC
> on AQM evaluation guidelines.
> 
> We believe there is only one draft that has been targeting this so
> far, that folks are reading and commenting on it, and that the
> comments recently have been more about tweaking it than major rework.
> 
> We'd like to adopt draft-kuhn-aqm-eval-guidelines as a working group
> item and develop it into an Informational RFC:
> 
> http://tools.ietf.org/html/draft-kuhn-aqm-eval-guidelines-02
> 
> Please let use know in the next few weeks if you have any comments,
> questions, concerns, etc. about this.

I support this decision.

Cheers,
Michael


From nobody Mon Aug 11 07:48:37 2014
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 4F9BF1A0444 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:48:28 -0700 (PDT)
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 Gl7TBBz4Ro4c for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:48:27 -0700 (PDT)
Received: from atl4mhob07.myregisteredsite.com (atl4mhob07.myregisteredsite.com [209.17.115.45]) by ietfa.amsl.com (Postfix) with ESMTP id DCEF01A040D for <aqm@ietf.org>; Mon, 11 Aug 2014 07:48:26 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.205]) by atl4mhob07.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s7BEmPXb025364 for <aqm@ietf.org>; Mon, 11 Aug 2014 10:48:25 -0400
Received: (qmail 23338 invoked by uid 0); 11 Aug 2014 14:48:25 -0000
X-TCPREMOTEIP: 69.81.143.143
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.108?) (wes@mti-systems.com@69.81.143.143) by 0 with ESMTPA; 11 Aug 2014 14:48:25 -0000
Message-ID: <53E8D7B0.9040007@mti-systems.com>
Date: Mon, 11 Aug 2014 10:48:16 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "aqm@ietf.org" <aqm@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/eInJNunxs_lxgdkzdZv-X8hK6Fk
Subject: [aqm] adoption call: draft-welzl-ecn-benefits
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, 11 Aug 2014 14:48:28 -0000

This draft has been discussed a bit here and in TSVWG:

http://tools.ietf.org/html/draft-welzl-ecn-benefits-01

As I understand, the IAB has also discussed it a bit, and would
be happy if this was something that an IETF working group
published.  I believe the TSVWG chairs also discussed this and
would be fine if the AQM working group adopted it.

That said, there have only been a small number of mail list
comments here about it, and we (unfortunately) didn't devote
much of any meeting time to it in Toronto.

So, *please* let us know your thoughts on this in the next few
weeks.  I believe we would try to complete it relatively quickly
(e.g. 6 months) as an Informational RFC, assuming there is
consensus and AD approval to add the milestone.

I personally would like to see some stronger support for it from
this working group in order to feel good about adopting it, though
I think it is correct and may be "motherhood and apple pie" to
many of us.

-- 
Wes Eddy
MTI Systems


From nobody Mon Aug 11 07:56:07 2014
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 709F81A03DE for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:56:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level: 
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 SsbkgQOznk9Y for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 07:56:03 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id DF6861A03D8 for <aqm@ietf.org>; Mon, 11 Aug 2014 07:56:02 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 113142B427B; Mon, 11 Aug 2014 15:56:02 +0100 (BST)
Received: from 139.133.204.3 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Mon, 11 Aug 2014 15:56:02 +0100
Message-ID: <c0a80f238c591322aa19b6fab3cee310.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <20140809112747.GI45982@verdi>
References: <20140805101838.24981.28443.idtracker@ietfa.amsl.com> <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk> <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp.com> <20140808145834.GF45982@verdi> <e56b46c9c6e1d4424ad7e1560fae57b8.squirrel@www.erg.abdn.ac.uk> <20140809112747.GI45982@verdi>
Date: Mon, 11 Aug 2014 15:56:02 +0100
From: gorry@erg.abdn.ac.uk
To: "John Leslie" <john@jlc.net>, "aqm@ietf.org"" <aqm@ietf.org>
User-Agent: SquirrelMail/1.4.22
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/tZKdtqNyJDRf_yzoiHphqgz5evo
Cc: gorry@erg.abdn.ac.uk
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Mon, 11 Aug 2014 14:56:06 -0000

John,

Thanks for getting back, this is helpful and I can prepare a new revision
to cover the feedback from you and Bob, see below:

gorry@erg.abdn.ac.uk <gorry@erg.abdn.ac.uk> wrote:
>
> If you see ambiguity in "network device", by all means send us propose
> text again (I must have missed that detail.

   You're welcome to my text from July 2:

http://www.ietf.org/mail-archive/web/aqm/current/msg00701.html

I don't know whether that matches your intent: I have no desire to
change your intent.

GF: I looked, and didn't find a specific definition. The text in the
present draft says (there since -00), which I think is at least a
clarification of what was intended:
"These mechanisms may be implemented in network devices that include
   routers, switches, and other network middleboxes."

> Apart from that, does this mean you have no specific comments on this
> version?

   If Bob makes any fuss about "congestive collapse" I support him.
Otherwise, I make a strong request that you add a definition of that
term: I have no idea what you mean that's consistent with what you
wrote and the way the Internet works.

GF: The present document uses both "congestion collapse" and "congestive
collapse". I am OK with you proposal:
s/congestive/congestion/g: 4 instances
---
   I do remain convinced that the charter wording calling for
obsoleting RFC 2309 was ill-advised, and is not what this WG actually
chose to do. I'd much prefer to fix the charter milestone language;
but I detect no enthusiasm for that. I'll settle for being listed
"in the rough" in the Shepherd's writeup.

   My thorough review was of version -05. Since then, I note the
change in the Abstract from "updated" to "and replaces these"
[recommendations of 2309]. I don't see any particular reason for
that change, but won't fuss over it if nobody else cares.

GF: This is what I hear was the result of the consensus call by the Chairs
when the proposed future status for RFC 2309 was agreed.
---
   I note the addition of a section header for "1.1 Congestion
Collapse" which correctly includes "fix for Internet meltdown"; but
I think the switching between "Congestion Collapse" and "congestive
collapse" is confusing. ("Congestion Collapse" is a well-defined
term of art; and wouldn't need a definiton unless you think you
can write one which will make the usage of that term correct in
this document.)

GF: See above change.
---
   Most of my comments about version -05 can simply be listed as
"ignored" or perhaps "considered and ignored"; but a few never made
it onto the list because I thought the change from "obsoletes" to
"updates" needed to be discussed first.

GF: No No that was not the case - The new text was at least "considered"
in some detail, we went through both the text from Wes, your text and
others line by line before formulating the new revision.
----
   In Section 3 subsection 3, I would prefer that we not perpetuate
the idea that flows must be "TCP-friendly". While there are indeed
cases of unfriendly-to-TCP flows, that really isn't an AQM issue.

GF: I think scheduling and isolation have been discussed within the group,
so I personally don't agree with your view that this is out of scope.
Although I’m no fan of Non-TCP friendly, and would like to replace this
with less responsive that TCP.
---
   In Section 4.6, in talking of "elastic transport congestion
control", I fail to see how this relates to AQM; and I'd prefer
not jawboning about how transports "should" function. (This sort
of text would be entirely proper in an IRTF document; but we're
now doing an IETF BCP concerned with queue management in network
devices.)

GF: I’m thinking CC reacts to AQM to reduce the rate.
---
   Section 4.7 returns to 2309's "need further research" conclusion.
It seems to me out-of-place to list these things in a BCP.

GF: Others have not said this.

---
   In Section 8 Acknowledgements, I don't think it correct to say,
"This is an edited version of that document". (I agree it started
that way, but I find that not an acceptable basis for a BCP.)

GF: Indeed, I think we should change this now the document is nearly
ready.  I propose something more like:

NEW:
The original version of this document describing best current practice was
based on the informational text of [RFC2309]. This was written by the
End-to-End Research Group, which is to say Bob Braden, Dave Clark, Jon
Crowcroft, Bruce Davie, Steve Deering, Deborah Estrin, Sally Floyd, Van
Jacobson, Greg Minshall, Craig Partridge, Larry Peterson, KK Ramakrishnan,
Scott Shenker, John Wroclawski, and Lixia Zhang.  Although there are
important differences, many of the key arguments in the present document
remain unchanged from those in RFC 2309.

====

   You have every right to say I should have raised these points
earlier; but that's a poor substitute for evaluating their merit.
It is the intent of a Working Group Last Call to solicit thorough
reviews by WG participants -- and follow through on those with
merit.

   The habit of tossing the WGLC comments at the authors and
marginalizing any further comments to the authors' response is
a bad habit. I wish we would break it.

GF: This is more of comment about the IETF contributions, we also in
general benefit when there are more WG contributions to calls for inputs,
instead of leaving review to during or following of WGLC. However, I
personally  think all inputs are valuable, if they present ideas for
improving a document!

--
John Leslie <john@jlc.net>

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


From nobody Mon Aug 11 08:12:32 2014
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 99A661A03DE for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 08:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, 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 DHXepMC85D33 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 08:12:30 -0700 (PDT)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D3D01A03EB for <aqm@ietf.org>; Mon, 11 Aug 2014 08:12:30 -0700 (PDT)
Received: by mail-ob0-f169.google.com with SMTP id nu7so6136892obb.14 for <aqm@ietf.org>; Mon, 11 Aug 2014 08:12:29 -0700 (PDT)
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=5xOoXr/TFOc9PHCBvJOsXNmDPzb4b3LtbV0KH//283k=; b=06HEkBEPIfWGD8SkOWESrxz1Y1iH+YhXxPv90l92iQQzY4/ByoDi6gN1LZbP0fU/aa h1FpJ4529XH4IxEST2Xko6EJzGRCeNB+GSNYv/Pa+k5bLY+sFUVFn+PjNcmJn68oHQXN vPHp65VP57lF3MRi324K/PM/j5WaxpUt3SQd0TphRNBwsjE0GRxRg0OaixtuAx6kyoxa pXif8HeBIKC94t5yZEBvJAqr/259PqeBluZYuTp2rLqhdLTlN680gG7QQDAhNaZNf2uE I6HFZKmfTMG0nbeRQg5kKII+sL1jO7UNY2GylFDhW2xQ2YXht7G6XBbKTP9hM40WFV06 7bnA==
MIME-Version: 1.0
X-Received: by 10.60.135.233 with SMTP id pv9mr9566150oeb.75.1407769949725; Mon, 11 Aug 2014 08:12:29 -0700 (PDT)
Received: by 10.202.93.69 with HTTP; Mon, 11 Aug 2014 08:12:29 -0700 (PDT)
Received: by 10.202.93.69 with HTTP; Mon, 11 Aug 2014 08:12:29 -0700 (PDT)
In-Reply-To: <5DAA5307-2DE8-4D9B-BB46-AF41907A8980@ifi.uio.no>
References: <53E8D3C9.4050100@mti-systems.com> <5DAA5307-2DE8-4D9B-BB46-AF41907A8980@ifi.uio.no>
Date: Mon, 11 Aug 2014 08:12:29 -0700
Message-ID: <CAA93jw7SwEA-d7p2vkxrR=YL5nDSyV+n=KVK_QiEmJvTRWXsiQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Michael Welzl <michawe@ifi.uio.no>
Content-Type: multipart/alternative; boundary=047d7b41cd04c7726d05005bfb7d
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/j3_wAwL_T35jtFxiAE10qyWxRBE
Cc: Wesley Eddy <wes@mti-systems.com>, aqm@ietf.org
Subject: Re: [aqm] adoption call: draft-kuhn-aqm-eval-guidelines
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, 11 Aug 2014 15:12:31 -0000

--047d7b41cd04c7726d05005bfb7d
Content-Type: text/plain; charset=UTF-8

My suggestion at the mic was that the writing process for this be opened up
to more participants as we did in https://github.com/dtaht/bufferbloat-rfcs

... as it needs so much work.

--047d7b41cd04c7726d05005bfb7d
Content-Type: text/html; charset=UTF-8

<p dir="ltr">My suggestion at the mic was that the writing process for this be opened up <br>
to more participants as we did in <a href="https://github.com/dtaht/bufferbloat-rfcs">https://github.com/dtaht/bufferbloat-rfcs</a></p>
<p dir="ltr">... as it needs so much work.<br>
 </p>

--047d7b41cd04c7726d05005bfb7d--


From nobody Mon Aug 11 11:19:41 2014
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 6B3211A0733 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 11:19:38 -0700 (PDT)
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 UjAq61KM_kFg for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 11:19:36 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF2D21A06F6 for <aqm@ietf.org>; Mon, 11 Aug 2014 11:19:36 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id wp4so6407109obc.1 for <aqm@ietf.org>; Mon, 11 Aug 2014 11:19:36 -0700 (PDT)
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=uSlzdrISjcVYhopaFrqU14/LdamSUqIq2NA3KYjbJg4=; b=O7zy5fpPWfBvBtMhD62BiEt7RvmS3RTseBMVQVWi5VRWt5scuS/0/DlGGJ38BZPfV7 txH4x2Eoc6WfAnmedoB5ACRAOXDuAWmyFXvAgNW2tfNK+FGiu7bGP4Aq5JqMtX+fmQDU 8+Oc5qCDZ+rGotYHKONqiCQ4Pkz0Douf8DOX1lsOp3jiLMxvWi0Dj5rWCGGlOnHB57Vd Y31VfyIjru6rv5VxcHdTK6R2Z/Bg9QKDqpBuVSgJR0oKVVDltOhd64XAnczOPbCJZdaK hLl9MF+VxjWgi9klooa4X711MRoMOfrHWXlDw7w6PGv3cDpUCHxTDvMTfImS8RSzBKG/ OL2g==
MIME-Version: 1.0
X-Received: by 10.60.102.74 with SMTP id fm10mr51689233oeb.24.1407781176218; Mon, 11 Aug 2014 11:19:36 -0700 (PDT)
Received: by 10.202.93.69 with HTTP; Mon, 11 Aug 2014 11:19:36 -0700 (PDT)
In-Reply-To: <53E8D7B0.9040007@mti-systems.com>
References: <53E8D7B0.9040007@mti-systems.com>
Date: Mon, 11 Aug 2014 11:19:36 -0700
Message-ID: <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Wesley Eddy <wes@mti-systems.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/ZCt2jhHASR19Qr_gD0fx61P-HrQ
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] adoption call: draft-welzl-ecn-benefits
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, 11 Aug 2014 18:19:38 -0000

On Mon, Aug 11, 2014 at 7:48 AM, Wesley Eddy <wes@mti-systems.com> wrote:
> This draft has been discussed a bit here and in TSVWG:
>
> http://tools.ietf.org/html/draft-welzl-ecn-benefits-01
>
> As I understand, the IAB has also discussed it a bit, and would
> be happy if this was something that an IETF working group
> published.  I believe the TSVWG chairs also discussed this and
> would be fine if the AQM working group adopted it.
>
> That said, there have only been a small number of mail list
> comments here about it, and we (unfortunately) didn't devote
> much of any meeting time to it in Toronto.
>
> So, *please* let us know your thoughts on this in the next few
> weeks.  I believe we would try to complete it relatively quickly
> (e.g. 6 months) as an Informational RFC, assuming there is
> consensus and AD approval to add the milestone.
>
> I personally would like to see some stronger support for it from
> this working group in order to feel good about adopting it, though
> I think it is correct and may be "motherhood and apple pie" to
> many of us.

I don't share the relentless optimism of this document, and would
like it - or a competing document - to go into the potential negatives.

examples of this include the TOS washing problem bob alluded to
in one of the tsvwg meetings (the monday one), the impact on
competing flows, the problem of unresponsive agents or other
misuse,  the deprecation (?) of the nonce mechanism, and how to
properly switch between marking and dropping in an aqm.

There are also the possibilities in new uses for ecn (for example, in
the original rmcat nada proposal), in usages on local links in routing
protocols, and in new protocols such as quic, etc.

> --
> Wes Eddy
> MTI Systems
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm



--=20
Dave T=C3=A4ht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_=
indecent.article


From nobody Mon Aug 11 11:31:21 2014
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 B53FF1A0665 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 11:31:20 -0700 (PDT)
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 03i8u8-x5oIJ for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 11:31:19 -0700 (PDT)
Received: from nm2-vm5.access.bullet.mail.gq1.yahoo.com (nm2-vm5.access.bullet.mail.gq1.yahoo.com [216.39.63.120]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3108E1A0661 for <aqm@ietf.org>; Mon, 11 Aug 2014 11:31:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogers.com; s=s2048; t=1407781878; bh=vKho3T7rscbQbSPUAPHKiooUcyh17vcymVZ4bcZDny8=; h=Received:Received:Received:DKIM-Signature:X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=hptcGv2vxl4PVxO+mXjkxslr1D/41Al3tfNiKyDINoE1rja7+adYoc7k+Ktj5m1YBoQ48l7Z5LyNaHWO5yKHcKAol/zzXhyn/yQhsgAOQNGz7nueGuwLD3SVy0OhnuYmctyNIZZCtNnUEh4elJxzY6gvVPajGg43IDHfEJ7vEcylwIynfbQVnmT9oqo9BXEQpjR7l0rcoCZ/Db6lQDuwO/Tbyc/6i/dusaAxNJGwPSDDDoQVab/RvoTyRimY2YsNRGOMFhHHQV0m0TAfoISHQgddFpterVXKorWafPLJEprKUE1a2sQyJC36TT/UvP5qMNe5yOfiEo6DHnVoDbwWiA==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=rogers.com; b=fnMmp5FXf8Zch0L4ECRUyulVCxC3jnwJSLmhFfV5VhKbo9OytDyr4OULcOVTasYCbvstSNeAYUlbDb9zqN1G+gLCHcs+DXcep+PlV0vWfS6qr07PoeW30xni8AK02gpVu1dwDQTHpQdVPetybpttaWgOvWjiAUivo2CRhj9Q7iiIQ8WmbSEv4HKPIRqH2yvZrcIc13NGanVVV7+y/S5dRF0XVsEvaNI2ClJ69EzV9xg0tZYrt/1VCa2VaBPwmRwZ5vwhPOG7DxW4wEclYqYEJpyL9vyRTx9pfTCr8Pzp7by+LdECOeZdTLG4Ow7vta6YzYheuBdLxTHfaozu5v/U8A==;
Received: from [216.39.60.176] by nm2.access.bullet.mail.gq1.yahoo.com with NNFMP; 11 Aug 2014 18:31:18 -0000
Received: from [67.195.23.146] by tm12.access.bullet.mail.gq1.yahoo.com with NNFMP; 11 Aug 2014 18:31:18 -0000
Received: from [127.0.0.1] by smtp118.sbc.mail.gq1.yahoo.com with NNFMP; 11 Aug 2014 18:31:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogers.com; s=s1024; t=1407781878; bh=vKho3T7rscbQbSPUAPHKiooUcyh17vcymVZ4bcZDny8=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=aB2Ua0yanK9gWTwDTJ4GREwC45QQ7MNSmlBxtRdW3Y3PxOzyMogcvgM6MzlTHpgt4/RdJrkEkSzHkMDAapb/ah3RYTEni8EZHMN010kgQi7qP5jGCL4z0U4x3WIubYWAgX8OBoI0b0VKBfGixUQzRNdRLRjY0XEGvUyJqRlXjtI=
X-Yahoo-Newman-Id: 679649.17240.bm@smtp118.sbc.mail.gq1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: 7YWJ.F0VM1mTkMIX3WsZpLIctfZaOYM57XlwxR8bHhavdPv OOHxYAdR7JuwoWTIOEHjO0pQy_IetiTLpQ3ijKRJMh9bIegVblig4_OEoOCa ZmLk.Fsjj3GMrEsHItFE_mFL3mKZgHD7ndA.5Ikt87mpcGml2dR5VvW0sGk9 GQg08yEEMwCMujjUgxUYKvAUkZ9AAbhdZ0PTC0YpszNCEG8vAbTCbPRx4utJ jKm7Ts11phF2rJcGAnnCIDaCfF1SoVQON7YFgKrqYAGb1v6ycSvviyVX_bdk sPx7rqe21b.MJRWiAxYxkZpk_lz3d9jHzuNxHZGQrdZ_PSFsB4taKKH5wJem md_YmC4zhQy7DR3LftQpk9ikgrgOUeS7LVQaceZz0LXUjnl9NDnPYMljLchK gulnFqtJ9O1kh3OVUMzGk0ppIGEHR4jeEm7N2KuRvy6tNIRP6HKuQzvBjI1y WuroZbwyOHwHk7G4DGfVsmaAZiBvD3XXmylNRuJMCu.3nta7cgy_vLnylrfl H8zSvJqEpE5rSLkyC2X1KHq.4450oiW8y.GLLc34l
X-Yahoo-SMTP: sltvjZWswBCRD.ElTuB1l9j6s9wRYPpuyTNWOE5oEg--
Message-ID: <53E90BF5.3030803@rogers.com>
Date: Mon, 11 Aug 2014 14:31:17 -0400
From: David Collier-Brown <davec-b@rogers.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: aqm@ietf.org
References: <53E8D7B0.9040007@mti-systems.com> <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com>
In-Reply-To: <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/dec0TLPlWbXJeu_muNEaWke_L-U
Subject: Re: [aqm] adoption call: draft-welzl-ecn-benefits
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: Mon, 11 Aug 2014 18:31:20 -0000

+1, and even if some of the branches  of the discussion are "twigs", we
should indicate they're present and we're aware of them.



On 08/11/2014 02:19 PM, Dave Taht wrote:
> On Mon, Aug 11, 2014 at 7:48 AM, Wesley Eddy <wes@mti-systems.com> wrote:
>> This draft has been discussed a bit here and in TSVWG:
>>
>> http://tools.ietf.org/html/draft-welzl-ecn-benefits-01
>>
>> As I understand, the IAB has also discussed it a bit, and would
>> be happy if this was something that an IETF working group
>> published.  I believe the TSVWG chairs also discussed this and
>> would be fine if the AQM working group adopted it.
>>
>> That said, there have only been a small number of mail list
>> comments here about it, and we (unfortunately) didn't devote
>> much of any meeting time to it in Toronto.
>>
>> So, *please* let us know your thoughts on this in the next few
>> weeks.  I believe we would try to complete it relatively quickly
>> (e.g. 6 months) as an Informational RFC, assuming there is
>> consensus and AD approval to add the milestone.
>>
>> I personally would like to see some stronger support for it from
>> this working group in order to feel good about adopting it, though
>> I think it is correct and may be "motherhood and apple pie" to
>> many of us.
> I don't share the relentless optimism of this document, and would
> like it - or a competing document - to go into the potential negatives.
>
> examples of this include the TOS washing problem bob alluded to
> in one of the tsvwg meetings (the monday one), the impact on
> competing flows, the problem of unresponsive agents or other
> misuse,  the deprecation (?) of the nonce mechanism, and how to
> properly switch between marking and dropping in an aqm.
>
> There are also the possibilities in new uses for ecn (for example, in
> the original rmcat nada proposal), in usages on local links in routing
> protocols, and in new protocols such as quic, etc.
>
>> --
>> Wes Eddy
>> MTI Systems
>>
>> _______________________________________________
>> 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 Mon Aug 11 13:46:10 2014
Return-Path: <bob.briscoe@bt.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 0D4C51A00D9 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 13:46:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.269
X-Spam-Level: 
X-Spam-Status: No, score=-3.269 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.668, 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 9xgBtnTuGeJB for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 13:45:57 -0700 (PDT)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.98]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DD621A00D8 for <aqm@ietf.org>; Mon, 11 Aug 2014 13:45:57 -0700 (PDT)
Received: from EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) by EVMHR65-UKRD.bt.com (10.187.101.20) with Microsoft SMTP Server (TLS) id 14.3.181.6; Mon, 11 Aug 2014 21:45:55 +0100
Received: from EPHR02-UKIP.domain1.systemhost.net (147.149.100.81) by EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) with Microsoft SMTP Server (TLS) id 8.3.348.2; Mon, 11 Aug 2014 21:45:54 +0100
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR02-UKIP.domain1.systemhost.net (147.149.100.81) with Microsoft SMTP Server id 14.3.181.6; Mon, 11 Aug 2014 21:45:54 +0100
Received: from BTP075694.jungle.bt.co.uk ([10.109.146.19])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id s7BKjqYm022434;	Mon, 11 Aug 2014 21:45:52 +0100
Message-ID: <201408112045.s7BKjqYm022434@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 11 Aug 2014 21:45:51 +0100
To: <gorry@erg.abdn.ac.uk>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <ff5e927945a46a39559fbb25b0ede6bc.squirrel@www.erg.abdn.ac. uk>
References: <20140805101838.24981.28443.idtracker@ietfa.amsl.com> <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk> <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp.com> <201408110909.s7B99U7v020486@bagheera.jungle.bt.co.uk> <ff5e927945a46a39559fbb25b0ede6bc.squirrel@www.erg.abdn.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/s8642m90wcE6J1m4p6a2eE7o9Hk
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "Scheffenegger, Richard" <rs@netapp.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Mon, 11 Aug 2014 20:46:00 -0000

Gorry,

At 14:45 11/08/2014, gorry@erg.abdn.ac.uk wrote:
> > Suggested text, respectively:
> > * "The last two classes contain more aggressive flows
> > that can pose  significant threats to Internet performance"
> > * "The projected increase in the fraction of total Internet
> > traffic for more aggressive flows in classes 2 and 3 could
> > pose a threat to
> > future Internet performance"
>
> > Note, I've also suggested changing 'stability' to 'performance' -
> > this doc has nothing to do with oscillations, etc.
>
>+GF: Agree, this text was directly taken from RFC 2309=85 let's change it
>... but how about =93dependable performance=94? (i'd like to capture that=
 this
>isn't performance tuning - but more expectation of performance.

Dependable performance isn't right. I'd leave it=20
as just "...threat to ... performance".

Any protocol or algo that gives you k/N share of=20
available capacity doesn't give you dependendable=20
performance, because N isn't under your control, only k.


>=97=97
>
> > Responsiveness is important, but I believe it is OK for unresponsive
> > flows that are small in relative terms to only be responsive at very
> > long timescales (even solely at flow set up - self-admission
> > control). This even applies to aggregates of unresponsive flows,
> > because they will tend to be deployed where even the aggregate is
> > small relative to the link capacity.
> > See http://tools.ietf.org/html/draft-ietf-pwe3-congcons-02.pdf
> > (comments to the PWE3 list pls).
>
>+GF: I don=92t see this needed in this draft.

Sorry, I was just reinforcing my point that "the=20
sky is falling" language isn't necessary. I=20
didn't intend to say there should be anything=20
about any of the specifics in this para in the AQM draft.


> > Bob
>
>=97=97
>
>+GF: I=92m also considering replacing /congestive collapse/ by /congestion
>collapse/ which seems a more common term, as noted by John L.

Works for me.

Regards


Bob




________________________________________________________________
Bob Briscoe,                                                  BT=20


From nobody Mon Aug 11 14:38:16 2014
Return-Path: <michawe@ifi.uio.no>
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 206541A01D8 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 14:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.668] 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 5G6PhpYRdUd7 for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 14:38:12 -0700 (PDT)
Received: from mail-out5.uio.no (mail-out5.uio.no [IPv6:2001:700:100:10::17]) (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 8E3261A014D for <aqm@ietf.org>; Mon, 11 Aug 2014 14:38:11 -0700 (PDT)
Received: from mail-mx2.uio.no ([129.240.10.30]) by mail-out5.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1XGxI9-0006Yz-4u; Mon, 11 Aug 2014 23:38:09 +0200
Received: from 25.71.202.84.customer.cdi.no ([84.202.71.25] helo=[192.168.0.114]) by mail-mx2.uio.no with esmtpsa (TLSv1:AES128-SHA:128) user michawe (Exim 4.80) (envelope-from <michawe@ifi.uio.no>) id 1XGxI8-0005yB-GK; Mon, 11 Aug 2014 23:38:09 +0200
Content-Type: multipart/alternative; boundary="Apple-Mail=_5A90C43A-57AD-4F63-B7B7-6B4405D3D2DD"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com>
Date: Mon, 11 Aug 2014 23:38:09 +0200
Message-Id: <B64C7136-332D-485C-8D7D-CF92AAC4B247@ifi.uio.no>
References: <53E8D7B0.9040007@mti-systems.com> <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.1878.2)
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 4 msgs/h 2 sum rcpts/h 8 sum msgs/h 4 total rcpts 19125 max rcpts/h 44 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, TVD_RCVD_IP=0.001, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: EE4BA5C87796E1D54E75CBB4E773AE492C4BC923
X-UiO-SPAM-Test: remote_host: 84.202.71.25 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 2 total 107 max/h 5 blacklist 0 greylist 0 ratelimit 0
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/cUoQnROQgCt3p7yGjS_dQGpprNI
Cc: Wesley Eddy <wes@mti-systems.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] adoption call: draft-welzl-ecn-benefits
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, 11 Aug 2014 21:38:15 -0000

--Apple-Mail=_5A90C43A-57AD-4F63-B7B7-6B4405D3D2DD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

Thanks for your feedback! More below:


On 11. aug. 2014, at 20:19, Dave Taht <dave.taht@gmail.com> wrote:

> On Mon, Aug 11, 2014 at 7:48 AM, Wesley Eddy <wes@mti-systems.com> =
wrote:
>> This draft has been discussed a bit here and in TSVWG:
>>=20
>> http://tools.ietf.org/html/draft-welzl-ecn-benefits-01
>>=20
>> As I understand, the IAB has also discussed it a bit, and would
>> be happy if this was something that an IETF working group
>> published.  I believe the TSVWG chairs also discussed this and
>> would be fine if the AQM working group adopted it.
>>=20
>> That said, there have only been a small number of mail list
>> comments here about it, and we (unfortunately) didn't devote
>> much of any meeting time to it in Toronto.
>>=20
>> So, *please* let us know your thoughts on this in the next few
>> weeks.  I believe we would try to complete it relatively quickly
>> (e.g. 6 months) as an Informational RFC, assuming there is
>> consensus and AD approval to add the milestone.
>>=20
>> I personally would like to see some stronger support for it from
>> this working group in order to feel good about adopting it, though
>> I think it is correct and may be "motherhood and apple pie" to
>> many of us.
>=20
> I don't share the relentless optimism of this document, and would
> like it - or a competing document - to go into the potential =
negatives.
>=20
> examples of this include the TOS washing problem bob alluded to
> in one of the tsvwg meetings (the monday one),

This is an interesting point. I was somewhat torn about this document =
myself, in that it recommends to "turn on ECN", but doesn't say how - =
personally, in fact, I'd not want to recommend using it like it's been =
used on up to now, but I also have no clear recommendation yet.

Meanwhile, we (authors) have agreed that we'd rather stay away from =
recommending to "turn on ECN", but rather use the document to recommend =
to "be compatible" with it - i.e. *not* wash the TOS bits, and if you're =
a server, correctly reflect the bits.

This makes the TOS washing problem not a negative point of ECN, but the =
behavior that the document recommends against.


> the impact on
> competing flows,

This gets into the specific congestion control response to ECN, and the =
rules for ECN-marking. We try to stay away from such specifics in this =
document because we don't want to recommend one particular behavior =
here. I'd agree that not going into such specifics is wrong for a =
document that recommends to "turn on ECN", but we intend to no longer do =
that.


> the problem of unresponsive agents or other
> misuse,  the deprecation (?) of the nonce mechanism,

Not deprecated (yet?) AFAIK.


> and how to
> properly switch between marking and dropping in an aqm.
> There are also the possibilities in new uses for ecn (for example, in
> the original rmcat nada proposal), in usages on local links in routing
> protocols, and in new protocols such as quic, etc.

Again, specific congestion control reactions.

Cheers,
Michael


--Apple-Mail=_5A90C43A-57AD-4F63-B7B7-6B4405D3D2DD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;">Hi,<div><br></div><div>Thanks for your feedback! =
More below:</div><div><br></div><div><br><div><div>On 11. aug. 2014, at =
20:19, Dave Taht &lt;<a =
href=3D"mailto:dave.taht@gmail.com">dave.taht@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;">On Mon, Aug 11, 2014 at 7:48 AM, =
Wesley Eddy &lt;<a =
href=3D"mailto:wes@mti-systems.com">wes@mti-systems.com</a>&gt; =
wrote:<br><blockquote type=3D"cite">This draft has been discussed a bit =
here and in TSVWG:<br><br><a =
href=3D"http://tools.ietf.org/html/draft-welzl-ecn-benefits-01">http://too=
ls.ietf.org/html/draft-welzl-ecn-benefits-01</a><br><br>As I understand, =
the IAB has also discussed it a bit, and would<br>be happy if this was =
something that an IETF working group<br>published. &nbsp;I believe the =
TSVWG chairs also discussed this and<br>would be fine if the AQM working =
group adopted it.<br><br>That said, there have only been a small number =
of mail list<br>comments here about it, and we (unfortunately) didn't =
devote<br>much of any meeting time to it in Toronto.<br><br>So, *please* =
let us know your thoughts on this in the next few<br>weeks. &nbsp;I =
believe we would try to complete it relatively quickly<br>(e.g. 6 =
months) as an Informational RFC, assuming there is<br>consensus and AD =
approval to add the milestone.<br><br>I personally would like to see =
some stronger support for it from<br>this working group in order to feel =
good about adopting it, though<br>I think it is correct and may be =
"motherhood and apple pie" to<br>many of us.<br></blockquote><br>I don't =
share the relentless optimism of this document, and would<br>like it - =
or a competing document - to go into the potential =
negatives.<br><br>examples of this include the TOS washing problem bob =
alluded to<br>in one of the tsvwg meetings (the monday =
one),</div></blockquote><div><br></div><div>This is an interesting =
point. I was somewhat torn about this document myself, in that it =
recommends to "turn on ECN", but doesn't say how - personally, in fact, =
I'd not want to recommend using it like it's been used on up to now, but =
I also have no clear recommendation =
yet.</div><div><br></div><div>Meanwhile, we (authors) have agreed that =
we'd rather stay away from recommending to "turn on ECN", but rather use =
the document to recommend to "be compatible" with it - i.e. *not* wash =
the TOS bits, and if you're a server, correctly reflect the =
bits.</div><div><br></div>This makes the TOS washing problem not a =
negative point of ECN, but the behavior that the document recommends =
against.</div><div><br></div><div><br><blockquote type=3D"cite"><div =
style=3D"font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"> the impact on<br>competing =
flows,</div></blockquote><div><br></div>This gets into the specific =
congestion control response to ECN, and the rules for ECN-marking. We =
try to stay away from such specifics in this document because we don't =
want to recommend one particular behavior here. I'd agree that not going =
into such specifics is wrong for a document that recommends to "turn on =
ECN", but we intend to no longer do =
that.</div><div><br></div><div><br><blockquote type=3D"cite"><div =
style=3D"font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"> the problem of unresponsive agents or =
other<br>misuse, &nbsp;the deprecation (?) of the nonce =
mechanism,</div></blockquote><div><br></div><div>Not deprecated (yet?) =
AFAIK.</div><div><br></div><br><blockquote type=3D"cite"><div =
style=3D"font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"> and how to<br>properly switch between =
marking and dropping in an aqm.</div></blockquote><blockquote =
type=3D"cite"><div style=3D"font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;">There are also the possibilities =
in new uses for ecn (for example, in<br>the original rmcat nada =
proposal), in usages on local links in routing<br>protocols, and in new =
protocols such as quic, etc.<br></div></blockquote><div><br></div>Again, =
specific congestion control =
reactions.</div><div><br></div><div>Cheers,</div><div>Michael</div><div><b=
r></div></div></body></html>=

--Apple-Mail=_5A90C43A-57AD-4F63-B7B7-6B4405D3D2DD--


From nobody Mon Aug 11 16:39:06 2014
Return-Path: <john@jlc.net>
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 3B2891A071C for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 16:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.868
X-Spam-Level: 
X-Spam-Status: No, score=-4.868 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668] 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 GGZuJOBIDHgb for <aqm@ietfa.amsl.com>; Mon, 11 Aug 2014 16:39:02 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 1279A1A06CF for <aqm@ietf.org>; Mon, 11 Aug 2014 16:39:01 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 8459BC94A8; Mon, 11 Aug 2014 19:38:57 -0400 (EDT)
Date: Mon, 11 Aug 2014 19:38:57 -0400
From: John Leslie <john@jlc.net>
To: Dave Taht <dave.taht@gmail.com>
Message-ID: <20140811233857.GL45982@verdi>
References: <53E8D7B0.9040007@mti-systems.com> <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com>
User-Agent: Mutt/1.4.1i
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/Yw7V-xWPnGwGxq-a6w2TvDp-LlM
Cc: Wesley Eddy <wes@mti-systems.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] adoption call: draft-welzl-ecn-benefits
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, 11 Aug 2014 23:39:04 -0000

   (I have read Michael's reply to this, but I'll respond here.)

Dave Taht <dave.taht@gmail.com> wrote:
> On Mon, Aug 11, 2014 at 7:48 AM, Wesley Eddy <wes@mti-systems.com> wrote:
> 
>> This draft has been discussed a bit here and in TSVWG:
>> http://tools.ietf.org/html/draft-welzl-ecn-benefits-01

   I do think this is the right place to discuss it.

>> As I understand, the IAB has also discussed it a bit, and would
>> be happy if this was something that an IETF working group
>> published.  I believe the TSVWG chairs also discussed this and
>> would be fine if the AQM working group adopted it.

   Thus, I am in favor of adopting it, with the understanding that
it will see significant changes during our discussion.

> I don't share the relentless optimism of this document, and would
> like it - or a competing document - to go into the potential negatives.

   I think it should concentrate on what its name says: the benefits
of ECN, both now and in an expected future; but that it should also
at least mention downsides this WG sees: and that it should avoid any
recommendation stronger than "make ECN available to consenting
applications".

> examples of this include the TOS washing problem bob alluded to
> in one of the tsvwg meetings (the monday one),

   This definitely deserves mention.

> the impact on competing flows,

   That might have to go into a companion document. I think this
document could try to describe the bounds of such issues, but not
the details.

> the problem of unresponsive agents or other misuse,

   I'm not sure what Dave is alluding to here...

> the deprecation (?) of the nonce mechanism,

   I don't accept it as a given that the nonce should be deprecated;
though I do think that discussion will come up.

> and how to properly switch between marking and dropping in an aqm.

   I doubt this document will go into much detail there. Basically,
IMHO, an AQM should mark well before dropping becomes necessary; and
when dropping becomes necessary, ECN-capable packets should be dropped
essentially as often as non-ECN-capable packets.

   I'm not sure this document should say much about that, though...

> There are also the possibilities in new uses for ecn (for example, in
> the original rmcat nada proposal), in usages on local links in routing
> protocols, and in new protocols such as quic, etc.

   Sounds like interesting reading, Dave -- do you want to send pointers?

--
John Leslie <john@jlc.net>


From nobody Tue Aug 12 00:35:13 2014
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 C173F1A076E for <aqm@ietfa.amsl.com>; Tue, 12 Aug 2014 00:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level: 
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 Wl2h0Ggx-K4C for <aqm@ietfa.amsl.com>; Tue, 12 Aug 2014 00:35:08 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 0A2841A033A for <aqm@ietf.org>; Tue, 12 Aug 2014 00:35:08 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 057F22B42E6; Tue, 12 Aug 2014 08:35:07 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Tue, 12 Aug 2014 08:35:07 +0100
Message-ID: <f7fd66505006abb58490a241cba55ee7.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <201408112045.s7BKjqYm022434@bagheera.jungle.bt.co.uk>
References: <20140805101838.24981.28443.idtracker@ietfa.amsl.com> <47c4f0afaec650af659401bf8a701596.squirrel@www.erg.abdn.ac.uk> <eda4a09fc0e144ed99cf9af5f41b6f26@hioexcmbx05-prd.hq.netapp.com> <201408110909.s7B99U7v020486@bagheera.jungle.bt.co.uk> <ff5e927945a46a39559fbb25b0ede6bc.squirrel@www.erg.abdn.ac.uk> <201408112045.s7BKjqYm022434@bagheera.jungle.bt.co.uk>
Date: Tue, 12 Aug 2014 08:35:07 +0100
From: gorry@erg.abdn.ac.uk
To: "Bob Briscoe" <bob.briscoe@bt.com>
User-Agent: SquirrelMail/1.4.22
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/A3FVLW09YivazcN37CVOzfVI8d0
Cc: gorry@erg.abdn.ac.uk, "Scheffenegger, Richard" <rs@netapp.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-07.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: Tue, 12 Aug 2014 07:35:09 -0000

Bob - those changes are aded.

> Gorry,
>
> At 14:45 11/08/2014, gorry@erg.abdn.ac.uk wrote:
>> > Suggested text, respectively:
>> > * "The last two classes contain more aggressive flows
>> > that can pose  significant threats to Internet performance"
>> > * "The projected increase in the fraction of total Internet
>> > traffic for more aggressive flows in classes 2 and 3 could
>> > pose a threat to
>> > future Internet performance"
>>
>> > Note, I've also suggested changing 'stability' to 'performance' -
>> > this doc has nothing to do with oscillations, etc.
>>
>>+GF: Agree, this text was directly taken from RFC 2309… let's change it
>>... but how about “dependable performance”? (i'd like to capture that
>> this
>>isn't performance tuning - but more expectation of performance.
>
> Dependable performance isn't right. I'd leave it
> as just "...threat to ... performance".
>
> Any protocol or algo that gives you k/N share of
> available capacity doesn't give you dependendable
> performance, because N isn't under your control, only k.
>
I wasn't thinking that way - so I won't write that, I was wondering how to
write the opposite of lockout. Because performance is one aspect - but
methods to reduce synch and lockout are important also.

>
>>——
>>
>> > Responsiveness is important, but I believe it is OK for unresponsive
>> > flows that are small in relative terms to only be responsive at very
>> > long timescales (even solely at flow set up - self-admission
>> > control). This even applies to aggregates of unresponsive flows,
>> > because they will tend to be deployed where even the aggregate is
>> > small relative to the link capacity.
>> > See http://tools.ietf.org/html/draft-ietf-pwe3-congcons-02.pdf
>> > (comments to the PWE3 list pls).
>>
>>+GF: I don’t see this needed in this draft.
>
> Sorry, I was just reinforcing my point that "the
> sky is falling" language isn't necessary. I
> didn't intend to say there should be anything
> about any of the specifics in this para in the AQM draft.
>
>
>> > Bob
>>
>>——
>>
>>+GF: I’m also considering replacing /congestive collapse/ by /congestion
>>collapse/ which seems a more common term, as noted by John L.
>
> Works for me.
>
> Regards
>
>
> Bob
>
>
>
>
> ________________________________________________________________
> Bob Briscoe,                                                  BT
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>


From nobody Tue Aug 12 01:04:12 2014
Return-Path: <wolfram.lautenschlaeger@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 A03FE1A0775 for <aqm@ietfa.amsl.com>; Tue, 12 Aug 2014 01:04:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level: 
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.668] 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 1rOC1gcUqJUc for <aqm@ietfa.amsl.com>; Tue, 12 Aug 2014 01:04:06 -0700 (PDT)
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 BE9381A0346 for <aqm@ietf.org>; Tue, 12 Aug 2014 01:04:06 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id EEE591A1E454A for <aqm@ietf.org>; Tue, 12 Aug 2014 08:04:00 +0000 (GMT)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s7C841km020946 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <aqm@ietf.org>; Tue, 12 Aug 2014 10:04:02 +0200
Received: from FR712WXCHMBA13.zeu.alcatel-lucent.com ([169.254.5.172]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Tue, 12 Aug 2014 10:04:01 +0200
From: "LAUTENSCHLAEGER, Wolfram (Wolfram)" <wolfram.lautenschlaeger@alcatel-lucent.com>
To: "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: review draft-kuhn-aqm-eval-guidelines-02
Thread-Index: Ac+2AnjCtkdYocX9S06z/FYkIRNajA==
Date: Tue, 12 Aug 2014 08:04:01 +0000
Message-ID: <0A452E1DADEF254C9A7AC1969B8781280973F8@FR712WXCHMBA13.zeu.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/OwPTGmXLpEmCChpgE7ZFqFnnT64
Subject: [aqm] review draft-kuhn-aqm-eval-guidelines-02
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, 12 Aug 2014 08:04:08 -0000

I agree with most of the suggested features that must be tested=20
for AQM evaluation.

But I have some doubts if the proposed experiments/metrics
are really applicable and able to reveal the required features.

My comments in detail:

Section 2.1: Flow completion time:

Is applicable only for equally sized finite flows.=20
Not really meaningful for variable sized flows, e.g. the Tmix trace.=20
Not applicable to infinite flows.

Section 2.2: Packet loss:=20

- Long term loss probability is meaningful only in a steady state
scenario. And it characterizes the TCP flavor, not the AQM. (Loss
probability remains the same, whatever you do with AQM, as long as you
reach roughly the same throughput.)

- interval between consecutive losses: If the losses are well spaced,
it resembles somehow the loss probability. If not well spaced (bursty),=20
what to record?

- packet loss patterns: Metric is undefined, except the special case=20
"packet loss synchronization", next section, 2.3. It is, indeed, highly=20
interesting qualitatively in non-stationary cases, e.g. abrupt capacity=20
drop. But how to quantify?

Section 2.4: Goodput:=20

- Meaningful only with steady state occupancy by a number of more or=20
less greedy TCP flows. Here it shows, to which extent the AQM is able=20
to keep a link close to the 100% utilization.=20

- With a trace of variable sized flows (Tmix) the goodput resembles the=20
traffic offer (if in total below the link capacity; not overloaded).=20

- The overload scenario does not reach steady state. Goodput in=20
overload cases is highly dependent on other things than AQM, e.g. test=20
duration or shuffling of the trace.

Section 2.6: Trade-off latency vs. goodput:

The section refers to two (x,y) plots of the form:
      X=3Ddelay(parms)
      Y=3Dgoodput(parms)
and
      X=3Ddelay(parms)
      Y=3Ddrop_ratio(parms)
where <parms> are tuples of parameter values, each describing=20
one experimental set-up.

It remains unclear, what <parms> might be in the context of the given=20
document. The cited document [TCPEVAL2013] suggests that one dimension=20
of <parms> might be the scaling of the applied Tmix trace. The other=20
parameters in the cited documents are not applicable here. More on this=20
see below.

Section 4.1: TCP-friendly sender:

Requires the plots according to section 2.6. But at the same time it=20
specifies one single long-lived, non application limited flow - this is=20
one single dot in each of the plots.

Section 4.2: Aggressive Transport Sender: same problem

Section 4.3: Unresponsive Transport: same problem; moreover:

Scenario is only applicable to scheduling, not to AQM. The described=20
traffic simply overloads the link with no response to AQM (that is, to=20
my understanding the meaning of unresponsive traffic). A "long-lived=20
non application limited UDP flow" is somewhat infinite, other than its=20
counterpart TCP.

I would suggest a different test here: In a mixture of responsive and=20
unresponsive traffic do a test, to which extent the AQM scheme is still=20
able to keep the responsive fraction under control. This requires that=20
the unresponsive traffic is well below the capacity limit. The=20
rationale behind this test is that an AQM scheme might under- or=20
over-react if it drops packets but does not see the expected reduction.

Section 4.4: Initial Congestion Window:

Makes sense only with a mix of short lived flows. For long-lived flows=20
the IW does not matter. Alternatively a single experiment of a pre-
existing long-lived flow and a newly appearing IW3/IW10 flow could be=20
executed. But there is no reference to any traffic mix. The table=20
specifies just 2 flows in parallel.

What are the <parms> for graphs according to section 2.6?=20

Section 4.5: Traffic Mix

The section defines its own traffic mixes in a table, but requires the=20
graphs according to 2.6, which somehow implies the Tmix traffic.

Section 6: Burst absorption

Same as above; the test comes with its own traffic mix, but requests=20
graphs according to 2.6, thus implying Tmix.

The proposed bursty scenarios seem to be not specific enough, if=20
compared with 4.5.

I would propose here, for reproducibility, something like UDP on/off=20
background traffic.

Section 7: Stability

This section mixes two different things:=20
(a) The impact of general drop rate by other cross traffic, which is=20
unrelated to the bottleneck link.=20
(b) Reaction to varying link capacity at the bottleneck.

The general drop rate experiment (a) is weakly specified: If the drop=20
rate is too high, the bottleneck capacity cannot be reached; AQM does=20
not matter. Or, the other way round, if the drop rate is too low, the=20
AQM algorithm dominates the drop process, whereas the background drops=20
don't really matter. Only the transition between both regimes could be=20
of interest. But how to get there, and is this of relevance in practice?

The varying capacity experiment (b) is really relevant. I am asking=20
myself, if there could be resonant effects in the AQM parameter=20
adaptation algorithms, and how to test for this?


Wolfram Lautenschl=E4ger
Alcatel-Lucent
Bell Labs



From nobody Tue Aug 12 02:43:38 2014
Return-Path: <bob.briscoe@bt.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 067AE1A0816 for <aqm@ietfa.amsl.com>; Tue, 12 Aug 2014 02:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.269
X-Spam-Level: 
X-Spam-Status: No, score=-3.269 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.668, 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 6MYdL9nw02E7 for <aqm@ietfa.amsl.com>; Tue, 12 Aug 2014 02:43:32 -0700 (PDT)
Received: from hubrelay-by-04.bt.com (hubrelay-by-04.bt.com [62.7.242.140]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA6D51A0815 for <aqm@ietf.org>; Tue, 12 Aug 2014 02:43:31 -0700 (PDT)
Received: from EVMHR72-UKRD.domain1.systemhost.net (10.36.3.110) by EVMHR04-UKBR.bt.com (10.216.161.36) with Microsoft SMTP Server (TLS) id 8.3.348.2; Tue, 12 Aug 2014 10:43:28 +0100
Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR72-UKRD.domain1.systemhost.net (10.36.3.110) with Microsoft SMTP Server (TLS) id 8.3.348.2; Tue, 12 Aug 2014 10:43:29 +0100
Received: from bagheera.jungle.bt.co.uk (132.146.168.158) by EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) with Microsoft SMTP Server id 14.3.181.6; Tue, 12 Aug 2014 10:43:29 +0100
Received: from BTP075694.jungle.bt.co.uk ([10.111.123.46])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id s7C9hRvV024419;	Tue, 12 Aug 2014 10:43:27 +0100
Message-ID: <201408120943.s7C9hRvV024419@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 12 Aug 2014 10:43:26 +0100
To: Wesley Eddy <wes@mti-systems.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <20140811233857.GL45982@verdi>
References: <53E8D7B0.9040007@mti-systems.com> <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com> <20140811233857.GL45982@verdi>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/O4xXRYU7DR3gWeFqmrS2pqEDOzI
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] adoption call: draft-welzl-ecn-benefits
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, 12 Aug 2014 09:43:36 -0000

Wes, and responders so far,

A doc on the benefits and pitfalls of ECN is needed. Personally I 
wouldn't assign much of my own time as a priority for such work; I'd 
rather work on finding the best road through the protocol 
engineering. But I'm glad others are doing this.

We need to be clear that this doc (at the moment) is about the 
benefits of 'something like RFC3168 ECN'. I think that is the right 
direction. I would not be interested in a doc solely about the 
benefits of 'classic' ECN (we had RFC2884 for that).

However, if it is about the benefits of some other ECN-like thing, it 
will not be worth writing unless it is more concrete on what that 
other ECN-like thing is. At present different and sometimes 
conflicting ideas are floating around (I'm to blame for a few).

In order to write about benefits, surely experiments are needed to 
quantify the benefits? Alternatively, this could be a manifesto to 
identify /potential/ benefits of ECN that the current classic ECN is 
failing to give. I think at the moment it's the latter (and that's OK 
given that's where we have reached today).

How about the title "Explicit Congestion Notification (ECN): 
Benefits, Opportunities and Pitfalls" ?

We (in the RITE project) have agreed to start work on an 'ECN 
Roadmap' in order to identify all the potential ideas for using ECN 
coming out of research, and write down whether new standards will be 
needed for some, whether they can evolve without changing standards, 
which are complementary, which conflict, etc.

I don't know whether this ECN benefits doc ought to include this 
detailed ECN roadmap work, but if it's going to talk about "something 
like ECN" I believe it will have to include a summary of the main 
items on such a roadmap to be concrete.


more inline...

At 00:38 12/08/2014, John Leslie wrote:
>    (I have read Michael's reply to this, but I'll respond here.)
>
>Dave Taht <dave.taht@gmail.com> wrote:
> > On Mon, Aug 11, 2014 at 7:48 AM, Wesley Eddy <wes@mti-systems.com> wrote:
> >
> >> This draft has been discussed a bit here and in TSVWG:
> >> http://tools.ietf.org/html/draft-welzl-ecn-benefits-01
>
>    I do think this is the right place to discuss it.
>
> >> As I understand, the IAB has also discussed it a bit, and would
> >> be happy if this was something that an IETF working group
> >> published.  I believe the TSVWG chairs also discussed this and
> >> would be fine if the AQM working group adopted it.
>
>    Thus, I am in favor of adopting it, with the understanding that
>it will see significant changes during our discussion.

I think we can and should agree the direction of those changes in 
this thread. I'd rather not agree to start on a doc and plan to meander.

I don't think this will be a quick (6 months) job, because of the 
problem of being clear about the "things like ECN" that it needs to talk about.


> > I don't share the relentless optimism of this document, and would
> > like it - or a competing document - to go into the potential negatives.
>
>    I think it should concentrate on what its name says: the benefits
>of ECN, both now and in an expected future; but that it should also
>at least mention downsides this WG sees: and that it should avoid any
>recommendation stronger than "make ECN available to consenting
>applications".

I agree it should be informative, rather than making too many 
detailed recommendations.


> > examples of this include the TOS washing problem bob alluded to
> > in one of the tsvwg meetings (the monday one),
>
>    This definitely deserves mention.

I agree it would be useful to write about deployment problems. 
Specifically, a clear explanation of what the deployment problems 
have been, which ones are no longer problems (if any), and which ones 
are still problems, and how prevalent.

Alternatively, folks doing ECN black hole experiments might want to 
write them up in a separate draft, that this one can refer to (there 
are already a few research papers documenting ECN deployment 
experiments). I would be willing to help collect together the history 
that I have on this.


> > the impact on competing flows,
>
>    That might have to go into a companion document. I think this
>document could try to describe the bounds of such issues, but not
>the details.

+1


> > the problem of unresponsive agents or other misuse,
>
>    I'm not sure what Dave is alluding to here...

Dave is alluding to suppression of ECN in the feedback loop (e.g. by 
the receiver) or the sender not responding (the problem space that 
ConEx and the ECN Nonce target).


> > the deprecation (?) of the nonce mechanism,
>
>    I don't accept it as a given that the nonce should be deprecated;
>though I do think that discussion will come up.

It would also be useful to write about cheating problems.

However, an informational doc would not be the right place to 
deprecate the ECN nonce. That needs to be in a doc that offers an 
alternative mechanism (which is where draft-moncaster-tcpm-rcv-cheat 
is heading - we have ideas on how to extend it to ECN cheating).


> > and how to properly switch between marking and dropping in an aqm.
>
>    I doubt this document will go into much detail there. Basically,
>IMHO, an AQM should mark well before dropping becomes necessary; and
>when dropping becomes necessary, ECN-capable packets should be dropped
>essentially as often as non-ECN-capable packets.
>
>    I'm not sure this document should say much about that, though...

This might be relevant if talking about how there could be benefits 
if it were done differently from RFC3168. But otherwise, I agree this 
would not be on-topic for this doc.


> > There are also the possibilities in new uses for ecn (for example, in
> > the original rmcat nada proposal), in usages on local links in routing
> > protocols, and in new protocols such as quic, etc.
>
>    Sounds like interesting reading, Dave -- do you want to send pointers?

<http://tools.ietf.org/html/draft-zhu-rmcat-nada-03>

I assume using ECN on local links in routing protocols is just 
something Dave is saying that operators could do unilaterally.

Given QUIC includes FEC to hide losses, I guess it is a good example 
to consider whether ECN still offers sufficient benefits over and 
above just removing losses.

Cheers


Bob


>--
>John Leslie <john@jlc.net>
>
>_______________________________________________
>aqm mailing list
>aqm@ietf.org
>https://www.ietf.org/mailman/listinfo/aqm

________________________________________________________________
Bob Briscoe,                                                  BT 


From nobody Tue Aug 12 03:24:24 2014
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 0F5081A0839 for <aqm@ietfa.amsl.com>; Tue, 12 Aug 2014 03:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level: 
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 nOk5o0G20KVQ for <aqm@ietfa.amsl.com>; Tue, 12 Aug 2014 03:24:18 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id C1A0B1A0836 for <aqm@ietf.org>; Tue, 12 Aug 2014 03:24:17 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 917F92B448B; Tue, 12 Aug 2014 11:24:16 +0100 (BST)
Received: from ERG-research.local (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 3EA4B2B42E6 for <aqm@ietf.org>; Tue, 12 Aug 2014 11:24:10 +0100 (BST)
Message-ID: <53E9EB49.9040509@erg.abdn.ac.uk>
Date: Tue, 12 Aug 2014 11:24:09 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: aqm@ietf.org
References: <53E8D7B0.9040007@mti-systems.com> <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com> <20140811233857.GL45982@verdi> <201408120943.s7C9hRvV024419@bagheera.jungle.bt.co.uk>
In-Reply-To: <201408120943.s7C9hRvV024419@bagheera.jungle.bt.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/AvyFpIaN8htCikY9rRg-R1xJF0A
Subject: Re: [aqm] adoption call: draft-welzl-ecn-benefits
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
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, 12 Aug 2014 10:24:22 -0000

OK, so I have many comments, see below.

Gorry

On 12/08/2014 10:43, Bob Briscoe wrote:
> Wes, and responders so far,
>
> A doc on the benefits and pitfalls of ECN is needed. Personally I
> wouldn't assign much of my own time as a priority for such work; I'd
> rather work on finding the best road through the protocol engineering.
> But I'm glad others are doing this.
>
> We need to be clear that this doc (at the moment) is about the benefits
> of 'something like RFC3168 ECN'. I think that is the right direction. I
> would not be interested in a doc solely about the benefits of 'classic'
> ECN (we had RFC2884 for that).
>
> However, if it is about the benefits of some other ECN-like thing, it
> will not be worth writing unless it is more concrete on what that other
> ECN-like thing is. At present different and sometimes conflicting ideas
> are floating around (I'm to blame for a few).
>
> In order to write about benefits, surely experiments are needed to
> quantify the benefits? Alternatively, this could be a manifesto to
> identify /potential/ benefits of ECN that the current classic ECN is
> failing to give. I think at the moment it's the latter (and that's OK
> given that's where we have reached today).
>
GF: If someone wishes to write this research paper, I'd be happy to join 
them, but it was not what I had in mind for this ID.

> How about the title "Explicit Congestion Notification (ECN): Benefits,
> Opportunities and Pitfalls" ?
>
GF: I could live with that, if the group wished this!

> We (in the RITE project) have agreed to start work on an 'ECN Roadmap'
> in order to identify all the potential ideas for using ECN coming out of
> research, and write down whether new standards will be needed for some,
> whether they can evolve without changing standards, which are
> complementary, which conflict, etc.
>
> I don't know whether this ECN benefits doc ought to include this
> detailed ECN roadmap work, but if it's going to talk about "something
> like ECN" I believe it will have to include a summary of the main items
> on such a roadmap to be concrete.
>
>
> more inline...
>
> At 00:38 12/08/2014, John Leslie wrote:
>>    (I have read Michael's reply to this, but I'll respond here.)
>>
>> Dave Taht <dave.taht@gmail.com> wrote:
>> > On Mon, Aug 11, 2014 at 7:48 AM, Wesley Eddy <wes@mti-systems.com>
>> wrote:
>> >
>> >> This draft has been discussed a bit here and in TSVWG:
>> >> http://tools.ietf.org/html/draft-welzl-ecn-benefits-01
>>
>>    I do think this is the right place to discuss it.
>>
>> >> As I understand, the IAB has also discussed it a bit, and would
>> >> be happy if this was something that an IETF working group
>> >> published.  I believe the TSVWG chairs also discussed this and
>> >> would be fine if the AQM working group adopted it.
>>
>>    Thus, I am in favor of adopting it, with the understanding that
>> it will see significant changes during our discussion.
>
> I think we can and should agree the direction of those changes in this
> thread. I'd rather not agree to start on a doc and plan to meander.
>
GF: +1, we can add comments to the ID to align to this, personally I've 
already said that I'd like to see text on:
- bleaching and middlebox requirements to deploy.
- Need to verify the paths actually really *do support* ECN (sorry, but 
may be needed).

> I don't think this will be a quick (6 months) job, because of the
> problem of being clear about the "things like ECN" that it needs to talk
> about.
>
GF: That depends also in part on whether these new mechanisms: will 
actually change the message to potential users of transports and people 
considering deployment. In my mind the definition of the protocol 
techniques does not HAVE to be the same document that tells people *HOW* 
to implement this in stacks or network devices. (My own choice would be 
to keep these to research papers and RFCs targeted at their respective 
communities).

>
>> > I don't share the relentless optimism of this document, and would
>> > like it - or a competing document - to go into the potential negatives.
>>
>>    I think it should concentrate on what its name says: the benefits
>> of ECN, both now and in an expected future; but that it should also
>> at least mention downsides this WG sees: and that it should avoid any
>> recommendation stronger than "make ECN available to consenting
>> applications".
>
> I agree it should be informative, rather than making too many detailed
> recommendations.
>
GF: Any other bullets listing additional topics are most welcome!

>
>> > examples of this include the TOS washing problem bob alluded to
>> > in one of the tsvwg meetings (the monday one),
>>
>>    This definitely deserves mention.
>
> I agree it would be useful to write about deployment problems.
> Specifically, a clear explanation of what the deployment problems have
> been, which ones are no longer problems (if any), and which ones are
> still problems, and how prevalent.
>
GF: +1

> Alternatively, folks doing ECN black hole experiments might want to
> write them up in a separate draft, that this one can refer to (there are
> already a few research papers documenting ECN deployment experiments). I
> would be willing to help collect together the history that I have on this.
>
GF: I'm doing these experiments too, happy to work with others.

>
>> > the impact on competing flows,
>>
>>    That might have to go into a companion document. I think this
>> document could try to describe the bounds of such issues, but not
>> the details.
>
> +1
>
GF: +1, I see this as informing the Engineering, not the goals of this 
document.

>
>> > the problem of unresponsive agents or other misuse,
>>
>>    I'm not sure what Dave is alluding to here...
>
> Dave is alluding to suppression of ECN in the feedback loop (e.g. by the
> receiver) or the sender not responding (the problem space that ConEx and
> the ECN Nonce target).
>
GF: I'd be glad to include something on this (not detailing a mechanism, 
but perhaps linked "how do we know the path supports ECN", and perhaps 
if the group is smart - how can the transport actually find this stuff 
out for itself? (sorry to keep returning to this)
>
>> > the deprecation (?) of the nonce mechanism,
>>
>>    I don't accept it as a given that the nonce should be deprecated;
>> though I do think that discussion will come up.
>
> It would also be useful to write about cheating problems.
>
GF: +1

> However, an informational doc would not be the right place to deprecate
> the ECN nonce. That needs to be in a doc that offers an alternative
> mechanism (which is where draft-moncaster-tcpm-rcv-cheat is heading - we
> have ideas on how to extend it to ECN cheating).
>
GF: - I'd be surprised if this document deprecates an EXP RFC (I've said 
this before), normally I'd expect this in the draft that defines the 
replacement technique.
>
>> > and how to properly switch between marking and dropping in an aqm.
>>
>>    I doubt this document will go into much detail there. Basically,
>> IMHO, an AQM should mark well before dropping becomes necessary; and
>> when dropping becomes necessary, ECN-capable packets should be dropped
>> essentially as often as non-ECN-capable packets.
>>
>>    I'm not sure this document should say much about that, though...
>
> This might be relevant if talking about how there could be benefits if
> it were done differently from RFC3168. But otherwise, I agree this would
> not be on-topic for this doc.
>
GF: This could be complicated, but probably depends on how far the WG 
has proceeded in other documents when this document is ready to publish?
>
>> > There are also the possibilities in new uses for ecn (for example, in
>> > the original rmcat nada proposal), in usages on local links in routing
>> > protocols, and in new protocols such as quic, etc.
>>
>>    Sounds like interesting reading, Dave -- do you want to send pointers?
>
> <http://tools.ietf.org/html/draft-zhu-rmcat-nada-03>
>
> I assume using ECN on local links in routing protocols is just something
> Dave is saying that operators could do unilaterally.
>
GF: The IETF has acknowledged alternate ECN semantics via setting the 
DSCP field (RFC4774, I recall some historical discussion of why and 
where), at least something could be said about this. I'd like to add at 
least a pointer.

> Given QUIC includes FEC to hide losses, I guess it is a good example to
> consider whether ECN still offers sufficient benefits over and above
> just removing losses.
>
GF: And then, isn't the implication of AQM to significantly increase the 
number of "losses" unless we use ECN?

Indeed, I have the impression we are confusing many on these points - 
ECN could change the reaction to congestion signal, and FEC (even 
opportunistic CC-friendly FEC) can also change the way things react to 
congestion signals.

> Cheers
>
>
> Bob
>
>
>> --
>> John Leslie <john@jlc.net>
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>
> ________________________________________________________________
> Bob Briscoe,                                                  BT
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>

Gorry

P.S. My proposal is that if this thread converges I intend to parse a 
later version and see if my co-author and I can then add some comments 
to our draft to catalogue a set of issues that we expect to see added in 
future, and an appendix of those we think may be out of scope.


From nobody Wed Aug 13 03:58:19 2014
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 6E77D1A8546; Wed, 13 Aug 2014 03:58:17 -0700 (PDT)
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 lk8l2Cud0Jvz; Wed, 13 Aug 2014 03:58:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A415D1A080F; Wed, 13 Aug 2014 03:58:15 -0700 (PDT)
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.6.2.p5
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140813105815.20391.29619.idtracker@ietfa.amsl.com>
Date: Wed, 13 Aug 2014 03:58:15 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/WocKtjTyqBqoqq-Ir2DfTSZRXJg
Cc: aqm@ietf.org
Subject: [aqm] I-D Action: draft-ietf-aqm-recommendation-08.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, 13 Aug 2014 10:58:18 -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-08.txt
	Pages           : 28
	Date            : 2014-08-13

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 largely repeats the recommendations of RFC 2309, and
   replaces these after 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-08

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


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 Aug 13 04:43:30 2014
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 BD3E11A085C for <aqm@ietfa.amsl.com>; Wed, 13 Aug 2014 04:43:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level: 
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 LirsJbBJWraZ for <aqm@ietfa.amsl.com>; Wed, 13 Aug 2014 04:43:27 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id F28811A0847 for <aqm@ietf.org>; Wed, 13 Aug 2014 04:43:26 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id EA9CA2B41E7; Wed, 13 Aug 2014 12:43:24 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Wed, 13 Aug 2014 12:43:25 +0100
Message-ID: <374e024321469c38402992ae009b365b.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <53E8D281.8040705@mti-systems.com>
References: <53E8D248.4050509@mti-systems.com> <53E8D281.8040705@mti-systems.com>
Date: Wed, 13 Aug 2014 12:43:25 +0100
From: gorry@erg.abdn.ac.uk
To: "Wesley Eddy" <wes@mti-systems.com>
User-Agent: SquirrelMail/1.4.22
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/g8M8AkFRI_Uqk19rXzwFzjA4FTU
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] adoption call: draft-baker-aqm-sfq-implementation
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, 13 Aug 2014 11:43:28 -0000

I support this as a work-item.

Gorry

> For reference, the draft is at:
> http://tools.ietf.org/html/draft-baker-aqm-sfq-implementation-00
>
> On 8/11/2014 10:25 AM, Wesley Eddy wrote:
>> Based on feedback we've seen, it looks like there is significant
>> value in progressing draft-baker-aqm-sfq-implementation as a
>> working group document.
>>
>> Assuming there is WG consensus and we have AD-approval, we would
>> like to add a milestone to develop this towards an Informational
>> RFC within ~6 months.
>>
>> Please provide any comments, questions, support, or criticism for
>> adopting this within the next few weeks.
>>
>
>
> --
> Wes Eddy
> MTI Systems
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>


From nobody Wed Aug 13 04:45:19 2014
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 7F0A71A085C for <aqm@ietfa.amsl.com>; Wed, 13 Aug 2014 04:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level: 
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 rB-Wj4wtQzcx for <aqm@ietfa.amsl.com>; Wed, 13 Aug 2014 04:45:17 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id E95B01A07E1 for <aqm@ietf.org>; Wed, 13 Aug 2014 04:45:16 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 32F7A2B41E7; Wed, 13 Aug 2014 12:45:16 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Wed, 13 Aug 2014 12:45:16 +0100
Message-ID: <c95a2d83248facf67ce7c333a011cb89.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <53E8D281.8040705@mti-systems.com>
References: <53E8D248.4050509@mti-systems.com> <53E8D281.8040705@mti-systems.com>
Date: Wed, 13 Aug 2014 12:45:16 +0100
From: gorry@erg.abdn.ac.uk
To: "aqm@ietf.org" <aqm@ietf.org>
User-Agent: SquirrelMail/1.4.22
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/6vqlxE0LyBgpfbbIEBgCs0l4zNg
Cc: fred@cisco.com
Subject: Re: [aqm] : draft-baker-aqm-sfq-implementation-00, minor comments
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, 13 Aug 2014 11:45:18 -0000

I have a few initial comments from re-reading draft
draft-baker-aqm-sfq-implementation-00. These may be useful in preparing
the next version:

As we noted in other discussions, "SFQ" is not helpful in the title.

Section1
I wonder if the introduction could point to more scheduling algorithm
options than simply the combination of  "SFQ" with an AQM?

Section 2.1
Normally I'd use "kbps" to indicate kilobits per second, to avoid
confusion with the tendency of some TCP researchers to report
kilobytes/sec.

Saying TCP IW can be "any value", could be unpalatable in the RFC series,
this at least needs a pointer to RFCs that specify IW.
Maybe the term TSO is widely used, so you could say /TCP offload/TCP
segment offload/

DSCP probably should be expanded on first use.

2.2.3 There could also be a "defer" processing when using encapsulations
that support a suspend/resume function as in PPP (RFC2687).

Section 3
It seems to suggest that delay (or even packet pair) is used by IETF
transports such as SCTP of TCP - this isn't so for current IETF congestion
controllers.

It also seems (??) to suggest PacketPair is a useful technique in
combination with link scheduling. On this I am not certain this is wise to
say - the experience I recall is that scheduling results in rather
unpredictable on the packet pair algorithm... but maybe I'm misreading
this, and the idea is to suggest this as a measurement tool?

Section 3.2

ECN needs a reference when first used.

/completely separate/ seems to be stated twice in two successive sentences.

Section 4

/It is however incorrect to discuss/ - This seems rather judgmental to
prohibit discussion, is it possible to invert the argument and say what is
useful?

Gorry

> For reference, the draft is at:
> http://tools.ietf.org/html/draft-baker-aqm-sfq-implementation-00
>


From nobody Wed Aug 13 07:18:35 2014
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 461BA1A03EC for <aqm@ietfa.amsl.com>; Wed, 13 Aug 2014 07:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level: 
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 wKw8UcvRFZ8x for <aqm@ietfa.amsl.com>; Wed, 13 Aug 2014 07:18:32 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id CCCF21A03D1 for <aqm@ietf.org>; Wed, 13 Aug 2014 07:18:31 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id E7ECD2B41E7 for <aqm@ietf.org>; Wed, 13 Aug 2014 15:18:30 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Wed, 13 Aug 2014 15:18:31 +0100
Message-ID: <b1526854d130ddc94d0e0de9e05ffb22.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <20140813105816.20391.67904.idtracker@ietfa.amsl.com>
References: <20140813105816.20391.67904.idtracker@ietfa.amsl.com>
Date: Wed, 13 Aug 2014 15:18:31 +0100
From: gorry@erg.abdn.ac.uk
To: aqm@ietf.org
User-Agent: SquirrelMail/1.4.22
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/LAvnSNzFxtbZkaYPd1AFs2i3hMo
Subject: [aqm] New Version 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: Wed, 13 Aug 2014 14:18:33 -0000

The authors have submitted a new version of the draft, this was to resolve
comments on the new text in -07, and adjust to RFC-Ed style US English
spelling of some words.

Gorry

>
> A new version of I-D, draft-ietf-aqm-recommendation-08.txt
> has been successfully submitted by Godred Fairhurst and posted to the
> IETF repository.
>
> Name:		draft-ietf-aqm-recommendation
> Revision:	08
> Title:		IETF Recommendations Regarding Active Queue Management
> Document date:	2014-08-13
> Group:		aqm
> Pages:		28
> URL:
> http://www.ietf.org/internet-drafts/draft-ietf-aqm-recommendation-08.txt
> Status:
> https://datatracker.ietf.org/doc/draft-ietf-aqm-recommendation/
> Htmlized:
> http://tools.ietf.org/html/draft-ietf-aqm-recommendation-08
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-recommendation-08
>
> 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 largely repeats the recommendations of RFC 2309, and
>    replaces these after fifteen years of experience and new research.
>
>
>
>
> 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.
>
> The IETF Secretariat
>


From nobody Thu Aug 21 17:30:35 2014
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 213381A06C1 for <aqm@ietfa.amsl.com>; Thu, 21 Aug 2014 17:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.569
X-Spam-Level: 
X-Spam-Status: No, score=-111.569 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_SUMOF=1, J_CHICKENPOX_45=0.6, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001, 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 ZxuRZ9xChGVz for <aqm@ietfa.amsl.com>; Thu, 21 Aug 2014 17:30:29 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A61E21A03D4 for <aqm@ietf.org>; Thu, 21 Aug 2014 17:30:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=36575; q=dns/txt; s=iport; t=1408667428; x=1409877028; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=j2X8+tAdDT8auHV1ExNhdxPKwUCXvbiYIv2lGZI/BEo=; b=l+b56VVEDk9a7GXxBvKL5/74OXG9bWxXotEnT0W7aVjrOpYyWVsDeU+x 5sokC5vdTUX/SI3qCWrfcRJLysHQUe0189TXEtARQdS6Q3wYcXKBoaAeM YS757O4N/S95hRfz9w4tgYH78jxN2E013t0m9ef6fl2I+YnQx6ikV9B/l w=;
X-Files: draft-ietf-aqm-fq-implementation.txt, signature.asc : 33853, 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFANSO9lOtJV2c/2dsb2JhbABZFoJ3U1cEtHqXXIdOAYENFneEBAEBAgEBGg1HCwULAgEIDgQ0MhcOAgQOBQ4NiB8IDcQEF45fCwsGAQdJB4MvgR0FhQSBDYQbgyeDUoIDgUpcgjqBb4JQgTIljQGGMoFkAhyBXGwBAYEFCBcigQcBAQE
X-IronPort-AV: E=Sophos;i="5.04,376,1406592000";  d="asc'?txt'?scan'208";a="71360483"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-3.cisco.com with ESMTP; 22 Aug 2014 00:30:27 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s7M0URtP032341 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Aug 2014 00:30:27 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.15]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0195.001; Thu, 21 Aug 2014 19:30:26 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Wesley Eddy <wes@mti-systems.com>
Thread-Topic: [aqm] adoption call: draft-baker-aqm-sfq-implementation
Thread-Index: AQHPvaBEaGcGQm5ljUqD4vyK34AtCA==
Date: Fri, 22 Aug 2014 00:30:25 +0000
Message-ID: <FA0CAFF7-54F0-4F62-A138-B45548483542@cisco.com>
References: <53E8D248.4050509@mti-systems.com>
In-Reply-To: <53E8D248.4050509@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.114]
Content-Type: multipart/signed; boundary="Apple-Mail=_75FF9696-6A82-4E33-9A2F-3927EE52BB63"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/9XTRYdlFVHjH_LOzQPZKq65Yp_o
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] adoption call: draft-baker-aqm-sfq-implementation
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, 22 Aug 2014 00:30:33 -0000

--Apple-Mail=_75FF9696-6A82-4E33-9A2F-3927EE52BB63
Content-Type: multipart/mixed;
	boundary="Apple-Mail=_04AEEFAA-5013-4C3C-9D64-F41AF7937725"


--Apple-Mail=_04AEEFAA-5013-4C3C-9D64-F41AF7937725
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Aug 11, 2014, at 7:25 AM, Wesley Eddy <wes@mti-systems.com> wrote:

> Based on feedback we've seen, it looks like there is significant
> value in progressing draft-baker-aqm-sfq-implementation as a
> working group document.
>=20
> Assuming there is WG consensus and we have AD-approval, we would
> like to add a milestone to develop this towards an Informational
> RFC within ~6 months.
>=20
> Please provide any comments, questions, support, or criticism for
> adopting this within the next few weeks.

FYI, Gorry and I discussed the draft off-list. What I have right now is =
attached.


--Apple-Mail=_04AEEFAA-5013-4C3C-9D64-F41AF7937725
Content-Disposition: attachment;
	filename=draft-ietf-aqm-fq-implementation.txt
Content-Type: text/plain;
	x-unix-mode=0644;
	name="draft-ietf-aqm-fq-implementation.txt"
Content-Transfer-Encoding: quoted-printable





Active Queue Management                                         F. Baker
Internet-Draft                                                    R. Pan
Intended status: Informational                             Cisco Systems
Expires: February 14, 2015                               August 13, 2014


                   On Queuing, Marking, and Dropping
                  draft-ietf-aqm-fq-implementation-00

Abstract

   This note discusses implementation strategies for coupled queuing and
   mark/drop algorithms.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 14, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.






Baker & Pan             Expires February 14, 2015               [Page 1]
=0C
Internet-Draft                                               August 2014


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Fair Queuing: Algorithms and History  . . . . . . . . . . . .   2
     2.1.  Generalized Processor Sharing . . . . . . . . . . . . . .   3
       2.1.1.  GPS Comparisons: transmission quanta  . . . . . . . .   3
       2.1.2.  GPS Comparisons: flow definition  . . . . . . . . . .   4
       2.1.3.  GPS Comparisons: unit of measurement  . . . . . . . .   5
     2.2.  GPS Approximations  . . . . . . . . . . . . . . . . . . .   5
       2.2.1.  Definition of a queuing algorithm . . . . . . . . . .   5
       2.2.2.  Round Robin Models  . . . . . . . . . . . . . . . . .   6
       2.2.3.  Calendar Queue Models . . . . . . . . . . . . . . . .   7
       2.2.4.  Work Conserving Models and Stochastic Fairness
               Queuing . . . . . . . . . . . . . . . . . . . . . . .   8
       2.2.5.  Non Work Conserving Models and Virtual Clock  . . . .   9
   3.  Queuing, Marking, and Dropping  . . . . . . . . . . . . . . .  10
     3.1.  Queuing with Tail Mark/Drop . . . . . . . . . . . . . . .  10
     3.2.  Queuing with CoDel Mark/Drop  . . . . . . . . . . . . . .  10
     3.3.  Queuing with PIE Mark/Drop  . . . . . . . . . . . . . . .  11
   4.  Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . .  12
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  13
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  14

1.  Introduction

   In the discussion of Active Queue Management, there has been
   discussion of the coupling of queue management algorithms such as
   Stochastic Fairness Queuing [SFQ], Virtual Clock [VirtualClock], or
   Deficit Round Robin [DRR] with mark/drop algorithms such as CoDel
   [I-D.nichols-tsvwg-codel] or PIE [I-D.pan-aqm-pie].  In the interest
   of clarifying the discussion, we document possible implementation
   approaches to that, and analyze the possible effects and side-
   effects.  The language and model derive from the Architecture for
   Differentiated Services [RFC2475].

2.  Fair Queuing: Algorithms and History

   There is extensive history in the set of algorithms collectively
   referred to as "Fair Queuing".  The model was initially discussed in
   [RFC0970], which proposed it hypothetically as a solution to the TCP
   Silly Window Syndrome issue in BSD 4.1.  The problem was that, due to
   a TCP implementation bug, some senders would settle into sending a



Baker & Pan             Expires February 14, 2015               [Page 2]
=0C
Internet-Draft                                               August 2014


   long stream of very short segments, which unnecessarily consumed
   bandwidth on TCP and IP headers and occupied short packet buffers,
   thereby disrupting competing sessions.  Nagle suggested that if
   packet streams were sorted by their source address and the sources
   treated in a round robin fashion, a sender's effect on end-to-end
   latency and increased loss rate would primarily affect only itself.
   This touched off perhaps a decade of work by various researchers on
   what was and is termed "Fair Queuing," philosophical discussions of
   the meaning of the word "fair," operational reasons that one might
   want a "weighted" or "predictably unfair" queuing algorithm, and so
   on.

2.1.  Generalized Processor Sharing

   Conceptually, any Fair Queuing algorithm attempts to implement some
   approximation to the Generalized Processor Sharing [GPS] model.

   The GPS model, in its essence, presumes that a set of identified data
   streams, called "flows", pass through an interface.  Each flow has a
   rate when measured over a period of time; A voice session might, for
   example, require 64 kbps plus whatever overhead is necessary to
   deliver it, and a TCP session might have variable throughput
   depending on where it is in its evolution.  The premise of
   Generalized Processor Sharing is that on all time scales, the flow
   occupies a predictable bit rate, so that if there is enough bandwidth
   for the flow in the long term, it also lacks nothing in the short
   term.  "All time scales" is obviously untenable in a packet network -
   and even in a traditional TDM circuit switch network - because a
   timescale shorter than he duration of a packet will only see one
   packet at a time.  But it provides an ideal for other models to be
   compared against.

   There are a number of attributes of approximations to the GPS model
   that bear operational consideration, including at least the
   transmission quanta, the definition of a "flow", the unit of
   measurement.  Implementation algorithms have different practical
   impacts as well.

2.1.1.  GPS Comparisons: transmission quanta

   The most obvious comparison between the GPS model and common
   approximations to it is that real world data is not delivered
   uniformly, but in some quantum.  The smallest quantum, in a packet
   network, is a packet.  But quanta can be larger; for example, in
   video applications it is common to describe data flow in frames per
   second, where a frame describes a picture on a screen or the changes
   made from a previous one.  A single video frame is commonly on the
   order of tens of packets.  If a codec is delivering thirty frames per



Baker & Pan             Expires February 14, 2015               [Page 3]
=0C
Internet-Draft                                               August 2014


   second, it is conceivable that the packets comprising a frame might
   be sent as thirty bursts per second, with each burst sent at the
   interface rate of the camera or other sender.  Similarly, TCP
   exchanges have an initial window, common values of which include 1,
   2, 3, 4 [RFC3390], and 10 [RFC6928], and there are also reports of
   bursts of 65K bytes at the relevant MSS, which is to say about 45
   packets in one burst, presumably coming from TCP Segment Offload
   (TSO, also called TOE) engines.  After that initial burst, TCP
   senders commonly send pairs of packets, but may send either smaller
   or larger bursts [RFC5690], and the rate at which they send data is
   governed by the arrival rate of acknowledgements from the receiver.

2.1.2.  GPS Comparisons: flow definition

   An important engineering trade-off relevant to GPS is the definition
   of a "flow".  A flow is, by definition, a defined data stream.
   Common definitions include:

   o  Packets in a single transport layer session ("microflow"),
      identified by a five-tuple [RFC2990],

   o  Packets between a single pair of addresses, identified by a source
      and destination address or prefix,

   o  Packets from a single source address or prefix [RFC0970],

   o  Packets to a single destination address or prefix,

   o  Packets to or from a single subscriber, customer, or peer
      [RFC6057].  In Service Provider operations, this might be a
      neighboring Autonomous System; in broadband, a residential
      customer.

   The difference should be apparent.  Consider a comparison between
   sorting by source address or destination address, to pick two
   examples, in the case that a given router interface has N application
   sessions going through it between N/2 local destinations and N remote
   sources.  Sorting by source, or in this case by source/destination
   pair, would give each remote peer an upper bound guarantee of 1/N of
   the available capacity, which might be distributed very unevenly
   among the local destinations.  Sorting by destination would give each
   local destination an upper bound guarantee of 2/N of the available
   capacity, which might be distributed very unevenly among the remote
   systems and correlated sessions.  Who is one fair to?  In both cases,
   they deliver equal service by their definition, but that might not be
   someone else's definition.





Baker & Pan             Expires February 14, 2015               [Page 4]
=0C
Internet-Draft                                               August 2014


2.1.3.  GPS Comparisons: unit of measurement

   And finally, there is the question of what is measured for rate.  If
   the sole objective is to force packet streams to not dominate each
   other, it is sufficient to count packets.  However, if the issue is
   the bit rate of an SLA, one must consider the sizes of the packets
   (the aggregate throughput of a flow, measured in bits or bytes).  And
   if predictable unfairness is a consideration, the value must be
   weighted accordingly.

2.2.  GPS Approximations

   Carrying the matter further, a queuing algorithm may also be termed
   "Work Conserving" or "Non Work Conserving".  A "work conserving"
   algorithm, by definition, is either empty, in which case no attempt
   is being made to dequeue data from it, or contains something, in
   which case it continuously tries to empty the queue.  A work
   conserving queue that contains queued data, at an interface with a
   given rate, will deliver data at that rate until it empties.  A non-
   work-conserving queue might stop delivering even through it still
   contains data.  A common reason for doing this is to impose an
   artificial upper bound on a class of traffic that is lower than the
   rate of the underlying physical interface.

2.2.1.  Definition of a queuing algorithm

   In the discussion following, we assume a basic definition of a
   queuing algorithm.  A queuing algorithm has, at minimum:

   o  Some form of internal storage for the elements kept in the queue,

   o  If it has multiple internal classifications,

      *  a method for classifying elements,

      *  additional storage for the classifier and implied classes,

   o  a method for creating the queue,

   o  a method for destroying the queue,

   o  a method, called "enqueue", for placing packets into the queue or
      queuing system

   o  a method, called "dequeue", for removing packets from the queue or
      queuing system





Baker & Pan             Expires February 14, 2015               [Page 5]
=0C
Internet-Draft                                               August 2014


   There may also be other information or methods, such as the ability
   to inspect the queue.  It also often has inspectable external
   attributes, such as the total volume of packets or bytes in queue,
   and may have limit thresholds, such as a maximum number of packets or
   bytes the queue might hold.

   For example, a simple FIFO queue has a linear data structure,
   enqueues packets at the tail, and dequeues packets from the head.  It
   might have a maximum queue depth and a current queue depth,
   maintained in packets or bytes.

2.2.2.  Round Robin Models

   One class of implementation approaches, generically referred to as
   "Weighted Round Robin", implements the structure of the queue as an
   array or ring of queues associated with flows, for whatever
   definition of a flow is important.

   On enqueue, the enqueue function classifies a packet and places it
   into a simple FIFO sub-queue.

   On dequeue, the sub-queues are searched in round-robin order, and
   when a sub-queue is identified that contains data, removes a
   specified quantum of data from it.  That quantum is at minimum a
   packet, but it may be more.  If the system is intended to maintain a
   byte rate, there will be memory between searches of the excess
   previously dequeued.

                            +-+
                          +>|1|
                          | +-+
                          |  |
                          | +-+               +-+
                          | |1|             +>|3|
                          | +-+             | +-+
                          |  |              |  |
                          | +-+      +-+    | +-+
                          | |1|    +>|2|    | |3|
                          | +-+    | +-+    | +-+
                          |  A     |  A     |  A
                          |  |     |  |     |  |
                         ++--++   ++--++   ++--++
                      +->| Q  |-->| Q  |-->| Q  |--+
                      |  +----+   +----+   +----+  |
                      +----------------------------+

                       Figure 1: Round Robin Queues




Baker & Pan             Expires February 14, 2015               [Page 6]
=0C
Internet-Draft                                               August 2014


   If a hash is used as a classifier, the modulus of the hash might be
   used as an array index, selecting the sub-queue that the packet will
   go into.  One can imagine other classifiers, such as using a
   Differentiated Services Code Point (DSCP) value as an index into an
   array containing the queue number for a flow, or more complex access
   list implementations.

   In any event, a sub-queue contains the traffic for a flow, and data
   is sent from each sub-queue in succession.

2.2.3.  Calendar Queue Models

   Another class of implementation approaches, generically referred to
   as "Weighted Fair Queues" or "Calendar Queue Implementations",
   implements the structure of the queue as an array or ring of queues
   (often called "buckets") associated with time or sequence; Each
   bucket contains the set of packets, which may be null, intended to be
   sent at a certain time or following the emptying of the previous
   bucket.  The queue structure includes a look-aside table that
   indicates the current depth (which is to say, the next bucket) of any
   given class of traffic, which might similarly be identified using a
   hash, a DSCP, an access list, or any other classifier.  Conceptually,
   the queues each contain zero or more packets from each class of
   traffic.  One is the queue being emptied "now"; the rest are
   associated with some time or sequence in the future.

   On enqueue, the enqueue function classifies a packet and determines
   the current depth of that class, with a view to scheduling it for
   transmission at some time or sequence in the future.  If the unit of
   scheduling is a packet and the queuing quantum is one packet per sub-
   queue, a burst of packets arrives in a given flow, and at the start
   the flow has no queued data, the first packet goes into the "next"
   queue, the second into its successor, and so on; if there was some
   data in the class, the first packet in the burst would go into the
   bucket pointed to by the look-aside table.  If the unit of scheduling
   is time, the explanation in Section 2.2.5 might be simplest to
   follow, but the bucket selected will be the bucket corresponding to a
   given transmission time in the future.  A necessary side-effect,
   memory being finite, is that there exist a finite number of "future"
   buckets.  If enough traffic arrives to cause a class to wrap, one is
   forced to drop something (tail-drop).

   On dequeue, the buckets are searched at their stated times or in
   their stated sequence, and when a bucket is identified that contains
   data, removes a specified quantum of data from it and, by extension,
   from the associated traffic classes.  A single bucket might contain
   data from a number of classes simultaneously.




Baker & Pan             Expires February 14, 2015               [Page 7]
=0C
Internet-Draft                                               August 2014


                             +-+
                           +>|1|
                           | +-+
                           |  |
                           | +-+      +-+
                           | |2|    +>|2|
                           | +-+    | +-+
                           |  |     |  |
                           | +-+    | +-+      +-+
                           | |3|    | |1|    +>|1|
                           | +-+    | +-+    | +-+
                           |  A     |  A     |  A
                           |  |     |  |     |  |
                          ++--++   ++--++   ++--++
                  "now"+->| Q  |-->| Q  |-->| Q  |-->...
                          +----+   +----+   +----+
                             A       A         A
                             |3      |2        |1
                          +++++++++++++++++++++++
                          ||||     Flow      ||||
                          +++++++++++++++++++++++

                         Figure 2: Calendar Queue

   In any event, a sub-queue contains the traffic for a point in time or
   a point in sequence, and data is sent from each sub-queue in
   succession.  If sub-queues are associated with time, an interesting
   end case develops: If the system is draining a given sub-queue, and
   the time of the next sub-queue arrives, what should the system do?
   One potentially valid line of reasoning would have it continue
   delivering the data in the present queue, on the assumption that it
   will likely trade off for time in the next.  Another potentially
   valid line of reasoning would have it discard any waiting data in the
   present queue and move to the next.

2.2.4.  Work Conserving Models and Stochastic Fairness Queuing

   McKenney's Stochastic Fairness Queuing [SFQ] is an example of a work
   conserving algorithm.  This algorithm measures packets, and considers
   a "flow" to be an equivalence class of traffic defined by a hashing
   algorithm over the source and destination IPv4 addresses.  As packets
   arrive, the enqueue function performs the indicated hash and places
   the packet into the indicated sub-queue.  The dequeue function
   operates as described in Section 2.2.2; sub-queues are inspected in
   round-robin sequence, and if they contain one or more packets, a
   packet is removed.





Baker & Pan             Expires February 14, 2015               [Page 8]
=0C
Internet-Draft                                               August 2014


   Shreedhar's Deficit Round Robin [DRR] model modifies the quanta to
   bytes, and deals with variable length packets.  A sub-queue
   descriptor contains a waiting quantum (the amount intended to be
   dequeued on the previous dequeue attempt that was not satisfied), a
   per-round quantum (the sub-queue is intended to dequeue a certain
   number of bytes each round), and a maximum to permit (some multiple
   of the MTU).  In each dequeue attempt, the dequeue method sets the
   waiting quantum to the smaller of the maximum quantum and the sum of
   the waiting and incremental quantum.  It then dequeues up to the
   waiting quantum, in bytes, of packets in the queue, and reduces the
   waiting quantum by the number of bytes dequeued.  Since packets will
   not normally be exactly the size of the quantum, some dequeue
   attempts will dequeue more than others, but they will over time
   average the incremental quantum per round if there is data present.

   McKenny or Shreedhar's models could be implemented as described in
   Section 2.2.3.  The weakness of a WRR approach is the search time
   expended when the queuing system is relatively empty, which the
   calendar queue model obviates.

2.2.5.  Non Work Conserving Models and Virtual Clock

   Zhang's Virtual Clock [VirtualClock] is an example of a non-work-
   conserving algorithm.  It is trivially implemented as described in
   Section 2.2.3.  It associates buckets with intervals in time, with
   durations on the order of microseconds to tens of milliseconds.  Each
   flow is assigned a rate in bytes per interval.  The flow entry
   maintains a point in time the "next" packet in the flow should be
   scheduled.

   On enqueue, the method determines whether the "next schedule" time is
   "in the past"; if so, the packet is scheduled "now", and if not, the
   packet is scheduled at that time.  It then calculates the new "next
   schedule" time, as the current "next schedule" time plus the length
   of the packet divided by the rate; if the resulting time is also in
   the past, the "next schedule" time is set to "now", and otherwise to
   the calculated time.  As noted in Section 2.2.3, there is an
   interesting point regarding "too much time in the future"; if a
   packet is scheduled too far into the future, it may be marked or
   dropped in the AQM procedure, and if it runs beyond the end of the
   queuing system, may be defensively tail dropped.

   On dequeue, the bucket associated with the time "now" is inspected.
   If it contains a packet, the packet is dequeued and transmitted.  If
   the bucket is empty and the time for the next bucket has not arrived,
   the system waits, even if there is a packet in the next bucket.  As
   noted in Section 2.2.3, there is an interesting point regarding the
   queue associated with "now".  If a subsequent bucket, even if it is



Baker & Pan             Expires February 14, 2015               [Page 9]
=0C
Internet-Draft                                               August 2014


   actually empty, would be delayed by the transmission of a packet, one
   could imagine marking the packet ECN CE [RFC3168] [RFC6679] or
   dropping the packet.

3.  Queuing, Marking, and Dropping

   Queuing, marking, and dropping are integrated in any system that has
   a queue.  If nothing else, as memory is finite, a system has to drop
   as discussed in Section 2.2.3 and Section 2.2.5 in order to protect
   itself.  However, host transports interpret drops as signals, so AQM
   algorithms use that as a mechanism to signal.

   It is useful to think of the effects of queuing as a signal as well.
   The receiver sends acknowledgements as data is received, so the
   arrival of acknowledgements at the sender paces the sender at
   approximately the average rate it is able to achieve through the
   network.  This is true even if the sender keeps an arbitrarily large
   amount of data stored in network queues, and is the basis for delay-
   based congestion control algorithms.  So, delaying a packet
   momentarily in order to permit another session to improve its
   operation has the effect of signaling a slightly lower capacity to
   the sender.

3.1.  Queuing with Tail Mark/Drop

   In the default case, in which a FIFO queue is used with defensive
   tail-drop only, the effect is therefore to signal to the sender in
   two ways:

   o  Ack Clocking, pacing the sender to send at approximately the rate
      it can deliver data to the receiver, and

   o  Defensive loss, when a sender sends faster than available capacity
      (such as by probing network capacity when fully utilizing that
      capacity) and overburdens a queue.

3.2.  Queuing with CoDel Mark/Drop

   In any case wherein a queuing algorithm is used along with CoDel
   [I-D.nichols-tsvwg-codel], the sequence of events is that a packet is
   time-stamped, enqueued, dequeued, compared to a subsequent reading of
   the clock, and then acted on, whether by dropping it, marking and
   forwarding it, or simply forwarding it.  This is to say that the only
   drop algorithm inherent in queuing is the defensive drop when the
   queue's resources are overrun.  However, the intention of marking or
   dropping is to signal to the sender much earlier, when a certain
   amount of delay has been observed.  In a FIFO+CoDel, Virtual
   Clock+CoDel, or FlowQueue-Codel



Baker & Pan             Expires February 14, 2015              [Page 10]
=0C
Internet-Draft                                               August 2014


   [I-D.hoeiland-joergensen-aqm-fq-codel] implementation, the queuing
   algorithm is completely separate from the AQM algorithm.  Using them
   in series results in four signals to the sender:

   o  Ack Clocking, pacing the sender to send at approximately the rate
      it can deliver data to the receiver through a queue,

   o  Lossless signaling that a certain delay threshold has been
      reached, if ECN [RFC3168][RFC6679] is in use,

   o  Intentional signaling via loss that a certain delay threshold has
      been reached, if ECN is not in use, and

   o  Defensive loss, when a sender sends faster than available capacity
      (such as by probing network capacity when fully utilizing that
      capacity) and overburdens a queue.

3.3.  Queuing with PIE Mark/Drop

   In any case wherein a queuing algorithm is used along with PIE
   [I-D.pan-aqm-pie], RED, or other such algorithms, the sequence of
   events is that a queue is inspected, a packet is dropped, marked, or
   left unchanged, enqueued, dequeued, compared to a subsequent reading
   of the clock, and then forwarded on.  This is to say that the AQM
   Mark/Drop Algorithm precedes enqueue; if it has not been effective
   and as a result the queue is out of resources anyway, the defensive
   drop algorithm steps in, and failing that, the queue operates in
   whatever way it does.  Hence, in a FIFO+PIE, SFQ+PIE, or Virtual
   Clock+PIE implementation, the queuing algorithm is again completely
   separate from the AQM algorithm.  Using them in series results in
   four signals to the sender:

   o  Ack Clocking, pacing the sender to send at approximately the rate
      it can deliver data to the receiver through a queue,

   o  Lossless signaling that a queue depth that corresponds to a
      certain delay threshold has been reached, if ECN is in use,

   o  Intentional signaling via loss that a queue depth that corresponds
      to a certain delay threshold has been reached, if ECN is not in
      use, and

   o  Defensive loss, when a sender sends faster than available capacity
      (such as by probing network capacity when fully utilizing that
      capacity) and overburdens a queue.






Baker & Pan             Expires February 14, 2015              [Page 11]
=0C
Internet-Draft                                               August 2014


4.  Conclusion

   To summarize, in Section 2, implementation approaches for several
   classes of queueing algorithms were explored.  Queuing algorithms
   such as SFQ, Virtual Clock, and FlowQueue-Codel
   [I-D.hoeiland-joergensen-aqm-fq-codel] have value in the network, in
   that they delay packets to enforce a rate upper bound or to permit
   competing flows to compete more effectively.  ECN Marking and loss
   are also useful signals if used in a manner that enhances TCP/SCTP
   operation or restrains unmanaged UDP data flows.

   Conceptually, queuing algoritms and a mark/drop algorithms operate in
   series, as discussed in Section 3, not as a single algorithm.  The
   observed effects differ: defensive loss protects the intermediate
   system and provides a signal, AQM mark/drop works to reduce mean
   latency, and the scheduling of flows works to modify flow interleave
   and acknowledgement pacing.  Certain features like flow isolation are
   provided by fair queueing related designs, but are not the effect of
   the mark/drop algorithm.

   The authors think highly of queuing algorithms, which can ensure
   certain behaviors, but in this context believe that coupling queuing
   and marking or dropping in an AQM (mark/drop) discussion is
   unwarranted and masks issues with the mark/drop algorithm in
   question.

5.  IANA Considerations

   This memo asks the IANA for no new parameters.

6.  Security Considerations

   This memo adds no new security issues; it observes on implementation
   strategies for Diffserv implementation.

7.  Acknowledgements

   This note grew out of, and is in response to, mailing list
   discussions in AQM, in which some have pushed an algorithm the
   compare to AQM marking and dropping algorithms, but which includes
   Flow Queuing.

8.  References








Baker & Pan             Expires February 14, 2015              [Page 12]
=0C
Internet-Draft                                               August 2014


8.1.  Normative References

   [RFC2475]  Blake, S., Black, D., Carlson, M., Davies, E., Wang, Z.,
              and W. Weiss, "An Architecture for Differentiated
              Services", RFC 2475, December 1998.

8.2.  Informative References

   [DRR]      Microsoft Corporation and Washington University in St.
              Louis, "Efficient fair queueing using deficit round
              robin", ACM SIGCOMM 1995, October 1995,
              <http://ieeexplore.ieee.org/stamp/
              stamp.jsp?tp=3D&arnumber=3D502236>.

   [GPS]      Xerox PARC, University of California, Berkeley, and Xerox
              PARC, "Analysis and simulation of a fair queueing
              algorithm", ACM SIGCOMM 1989, September 1989,
              <http://blizzard.cs.uwaterloo.ca/keshav/home/Papers/data/
              89/fq.pdf>.

   [I-D.hoeiland-joergensen-aqm-fq-codel]
              Hoeiland-Joergensen, T., McKenney, P., Taht, D., Gettys,
              J., and E. Dumazet, "FlowQueue-Codel", draft-hoeiland-
              joergensen-aqm-fq-codel-00 (work in progress), March 2014.

   [I-D.nichols-tsvwg-codel]
              Nichols, K. and V. Jacobson, "Controlled Delay Active
              Queue Management", draft-nichols-tsvwg-codel-01 (work in
              progress), February 2013.

   [I-D.pan-aqm-pie]
              Pan, R., Natarajan, P., Piglione, C., and M. Prabhu, "PIE:
              A Lightweight Control Scheme To Address the Bufferbloat
              Problem", draft-pan-aqm-pie-01 (work in progress),
              February 2014.

   [RFC0970]  Nagle, J., "On packet switches with infinite storage", RFC
              970, December 1985.

   [RFC2990]  Huston, G., "Next Steps for the IP QoS Architecture", RFC
              2990, November 2000.

   [RFC3168]  Ramakrishnan, K., Floyd, S., and D. Black, "The Addition
              of Explicit Congestion Notification (ECN) to IP", RFC
              3168, September 2001.

   [RFC3390]  Allman, M., Floyd, S., and C. Partridge, "Increasing TCP's
              Initial Window", RFC 3390, October 2002.



Baker & Pan             Expires February 14, 2015              [Page 13]
=0C
Internet-Draft                                               August 2014


   [RFC5690]  Floyd, S., Arcia, A., Ros, D., and J. Iyengar, "Adding
              Acknowledgement Congestion Control to TCP", RFC 5690,
              February 2010.

   [RFC6057]  Bastian, C., Klieber, T., Livingood, J., Mills, J., and R.
              Woundy, "Comcast's Protocol-Agnostic Congestion Management
              System", RFC 6057, December 2010.

   [RFC6679]  Westerlund, M., Johansson, I., Perkins, C., O'Hanlon, P.,
              and K. Carlberg, "Explicit Congestion Notification (ECN)
              for RTP over UDP", RFC 6679, August 2012.

   [RFC6928]  Chu, J., Dukkipati, N., Cheng, Y., and M. Mathis,
              "Increasing TCP's Initial Window", RFC 6928, April 2013.

   [SFQ]      SRI International, "Stochastic Fairness Queuing", IEEE
              Infocom 1990, June 1990, <http://www2.rdrop.com/~paulmck/
              scalability/paper/sfq.2002.06.04.pdf>.

   [VirtualClock]
              Xerox PARC, "Virtual Clock", ACM SIGCOMM 1990, September
              1990,
              <http://www.cs.ucla.edu/~lixia/papers/90sigcomm.pdf>.

Appendix A.  Change Log

   Initial Version:  June 2014

Authors' Addresses

   Fred Baker
   Cisco Systems
   Santa Barbara, California  93117
   USA

   Email: fred@cisco.com


   Rong Pan
   Cisco Systems
   Milpitas, California  95035
   USA

   Email: ropan@cisco.com







Baker & Pan             Expires February 14, 2015              [Page 14]

--Apple-Mail=_04AEEFAA-5013-4C3C-9D64-F41AF7937725
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

 

--Apple-Mail=_04AEEFAA-5013-4C3C-9D64-F41AF7937725--

--Apple-Mail=_75FF9696-6A82-4E33-9A2F-3927EE52BB63
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

iD8DBQFT9o8fbjEdbHIsm0MRAmliAKCiwPCHQHt5ae3ilMTM61kgwsqhrQCgjZSl
ibWmUhD5y9TbDR/AQ7DZU48=
=cYot
-----END PGP SIGNATURE-----

--Apple-Mail=_75FF9696-6A82-4E33-9A2F-3927EE52BB63--


From nobody Thu Aug 28 08:39:42 2014
Return-Path: <nicolas.kuhn@telecom-bretagne.eu>
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 A324B1A870C for <aqm@ietfa.amsl.com>; Thu, 28 Aug 2014 08:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35, HTML_MESSAGE=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 HlRgNVnlDYh1 for <aqm@ietfa.amsl.com>; Thu, 28 Aug 2014 08:39:37 -0700 (PDT)
Received: from zproxy210.enst-bretagne.fr (zproxy210.enst-bretagne.fr [192.108.117.8]) by ietfa.amsl.com (Postfix) with ESMTP id 1F72D1A093B for <aqm@ietf.org>; Thu, 28 Aug 2014 08:39:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by zproxy210.enst-bretagne.fr (Postfix) with ESMTP id 3768523258D; Thu, 28 Aug 2014 17:39:36 +0200 (CEST)
Received: from zproxy210.enst-bretagne.fr ([127.0.0.1]) by localhost (zproxy210.enst-bretagne.fr [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id ldI51E5ZtMFE; Thu, 28 Aug 2014 17:39:32 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by zproxy210.enst-bretagne.fr (Postfix) with ESMTP id 0DE96232595; Thu, 28 Aug 2014 17:39:32 +0200 (CEST)
X-Virus-Scanned: amavisd-new at zproxy210.enst-bretagne.fr
Received: from zproxy210.enst-bretagne.fr ([127.0.0.1]) by localhost (zproxy210.enst-bretagne.fr [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id pe_8qzaA5YDg; Thu, 28 Aug 2014 17:39:31 +0200 (CEST)
Received: from [IPv6:2001:660:7301:3728:a419:be66:1a66:cbbf] (passerellev6v4.enst-bretagne.fr [192.108.117.5]) by zproxy210.enst-bretagne.fr (Postfix) with ESMTPSA id D5CEC23258D; Thu, 28 Aug 2014 17:39:31 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_41C43DC1-762C-4400-8721-806DDE526AF9"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Nicolas KUHN <nicolas.kuhn@telecom-bretagne.eu>
In-Reply-To: <0A452E1DADEF254C9A7AC1969B8781280973F8@FR712WXCHMBA13.zeu.alcatel-lucent.com>
Date: Thu, 28 Aug 2014 17:39:33 +0200
Message-Id: <475E4292-47EE-4EEF-A7CE-188F16777EC8@telecom-bretagne.eu>
References: <0A452E1DADEF254C9A7AC1969B8781280973F8@FR712WXCHMBA13.zeu.alcatel-lucent.com>
To: "LAUTENSCHLAEGER, Wolfram (Wolfram)" <wolfram.lautenschlaeger@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1503)
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/FiLbTUXK-FN_wwvawhQUBjZvrRI
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] review draft-kuhn-aqm-eval-guidelines-02
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, 28 Aug 2014 15:39:41 -0000

--Apple-Mail=_41C43DC1-762C-4400-8721-806DDE526AF9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Dear Wolfram,=20

Thanks a lot for your useful feedback.=20
Pleas, have a look at my answer inline.=20

Kind regards,=20

Nicolas

On Aug 12, 2014, at 10:04 AM, "LAUTENSCHLAEGER, Wolfram (Wolfram)" =
<wolfram.lautenschlaeger@alcatel-lucent.com> wrote:

> I agree with most of the suggested features that must be tested=20
> for AQM evaluation.
>=20
> But I have some doubts if the proposed experiments/metrics
> are really applicable and able to reveal the required features.
>=20
> My comments in detail:
>=20
> Section 2.1: Flow completion time:
>=20
> Is applicable only for equally sized finite flows.=20
> Not really meaningful for variable sized flows, e.g. the Tmix trace.=20=

> Not applicable to infinite flows.
>=20

This comment points out that the metrics may not suit to every traffic =
detailed in the rest of the draft.
As, in this Section 2, we just list the metrics that can be measured, I =
propose to add the following paragraph in the beginning of Section 2:
"The metrics listed in this section may not suit every type of traffic =
detailed in the rest of this document: all of the following metrics MAY =
not be measured. For each scenario, the metrics should be selected among =
the following list, depending on the traffic considered."

> Section 2.2: Packet loss:=20
>=20
> - Long term loss probability is meaningful only in a steady state
> scenario. And it characterizes the TCP flavor, not the AQM. (Loss
> probability remains the same, whatever you do with AQM, as long as you
> reach roughly the same throughput.)
>=20

The long term loss probability might not be of interests for all the =
scenarios. In order to make the presentation of this metric more =
general, we could evaluate the packet drop probability over the time of =
the experiment.=20

I propose to replace "the long term packet loss probability" by :
" 	- the packet loss probability: this metric should be frequently =
measured during the experiment as the long term loss probability is of =
interests for steady state scenarios only;"

> - interval between consecutive losses: If the losses are well spaced,
> it resembles somehow the loss probability. If not well spaced =
(bursty),=20
> what to record?
>=20

To illustrate the interval between losses, we could propose to measure =
the time between two losses and provide the minimum, 5%, median, 95%, =
maximum values of the set of "interval times".

I propose to replace "the interval between consecutive losses" by :=20
"	- the interval between consecutive losses: the time between two =
losses should be measured. =46rom the set of interval times, the tester =
should present the median value, the minimum and maximum values and the =
10th and 90th percentiles."=20

> - packet loss patterns: Metric is undefined, except the special case=20=

> "packet loss synchronization", next section, 2.3. It is, indeed, =
highly=20
> interesting qualitatively in non-stationary cases, e.g. abrupt =
capacity=20
> drop. But how to quantify?
>=20

I agree that it will be hard to quantify this metric. The idea behind =
the "packet loss pattern", is to have a  description of the loss =
pattern, that might be obtained by considering the loss probability and =
the interval between consecutive losses. As a result, we will remove the =
"packet loss patterns" for the next version of the document.=20

> Section 2.4: Goodput:=20
>=20
> - Meaningful only with steady state occupancy by a number of more or=20=

> less greedy TCP flows. Here it shows, to which extent the AQM is able=20=

> to keep a link close to the 100% utilization.=20
>=20
> - With a trace of variable sized flows (Tmix) the goodput resembles =
the=20
> traffic offer (if in total below the link capacity; not overloaded).=20=

>=20
> - The overload scenario does not reach steady state. Goodput in=20
> overload cases is highly dependent on other things than AQM, e.g. test=20=

> duration or shuffling of the trace.
>=20

Indeed, some things need to be clarified. I propose to add the following =
paragraph:=20
" The measurement of the goodput let the tester evaluate to which extend =
the AQM is able to keep an high link utilization. This metric should be =
obtained frequently during the experiment: the long term goodput makes =
sense for steady-state scenarios only and may not reflect how the =
introduction of AQM actually impacts on the link utilization. It is =
worth pointing out that the fluctuations of this measurement may depend =
on other things than the introduction of an AQM, such as physical layer =
losses, fluctuating bandwidths (Wi-Fi), heavy congestion levels or =
transport layer congestion controls."

> Section 2.6: Trade-off latency vs. goodput:
>=20
> The section refers to two (x,y) plots of the form:
>     X=3Ddelay(parms)
>     Y=3Dgoodput(parms)
> and
>     X=3Ddelay(parms)
>     Y=3Ddrop_ratio(parms)
> where <parms> are tuples of parameter values, each describing=20
> one experimental set-up.
>=20
> It remains unclear, what <parms> might be in the context of the given=20=

> document. The cited document [TCPEVAL2013] suggests that one dimension=20=

> of <parms> might be the scaling of the applied Tmix trace. The other=20=

> parameters in the cited documents are not applicable here. More on =
this=20
> see below.
>=20

More precisions should have been given on how to generate this graphs.=20=

I propose to add the following paragraph:=20
"Each of the end-to-end delay, goodput and drop probability should be =
measured every second. =46rom each of this sets of measurements, the =
10th and 90th percentile and the median value should be computed. For =
each scenario case, an ellipse can be generated from the measurement of =
the percentiles and a point for the median value can be plotted."

> Section 4.1: TCP-friendly sender:
>=20
> Requires the plots according to section 2.6. But at the same time it=20=

> specifies one single long-lived, non application limited flow - this =
is=20
> one single dot in each of the plots.
>=20

See above

> Section 4.2: Aggressive Transport Sender: same problem
>=20

See above

> Section 4.3: Unresponsive Transport: same problem;

See above

> moreover:
>=20
> Scenario is only applicable to scheduling, not to AQM. The described=20=

> traffic simply overloads the link with no response to AQM (that is, to=20=

> my understanding the meaning of unresponsive traffic). A "long-lived=20=

> non application limited UDP flow" is somewhat infinite, other than its=20=

> counterpart TCP.
>=20
> I would suggest a different test here: In a mixture of responsive and=20=

> unresponsive traffic do a test, to which extent the AQM scheme is =
still=20
> able to keep the responsive fraction under control. This requires that=20=

> the unresponsive traffic is well below the capacity limit. The=20
> rationale behind this test is that an AQM scheme might under- or=20
> over-react if it drops packets but does not see the expected =
reduction.
>=20

I propose the following text:=20
"    The first scenario is the following.  In order to create a test
  environment that results in queue build up, we consider unresponsive
  flow(s) whose sending rate is greater than the bottleneck link
  capacity between routers L and R. This scenario consists of a long-
  lived non application limited UDP flow transmits data between sender
  A and receiver B. Graphs described in Section 2.6 MUST be generated.

  The second scenario is the following.  In order to test to which
  extend the AQM scheme is able to keep responsive fraction under
  control, this scenario considers a mixture of TCP-friendly and
  unresponsive traffics.  This scenario consists of a long-lived non
  application limited UDP flow and a single long-lived, non application
  limited, TCP New Reno flow that transmit data between sender A and
  receiver B. As opposed to the first scenario, the rate of the UDP
  traffic should not be greater than the bottleneck capacity, and
  should not be higher than half of the bottleneck capacity.  For each
  type of traffic, the graphs described in Section 2.6 MUST be
  generated. "

> Section 4.4: Initial Congestion Window:
>=20
> Makes sense only with a mix of short lived flows. For long-lived flows=20=

> the IW does not matter. Alternatively a single experiment of a pre-
> existing long-lived flow and a newly appearing IW3/IW10 flow could be=20=

> executed. But there is no reference to any traffic mix. The table=20
> specifies just 2 flows in parallel.
>=20

New paragraph for this scenario:=20
"    This scenario helps evaluate how an AQM scheme adapts to a traffic
  mix consisting of TCP flows with different values for the initial
  congestion window (IW).

  For this scenario, we consider two types of flow that MUST be
  generated between sender A and receiver B:

  o  a single long-lived non application limited TCP New Reno flow;

  o  a single long-lived application limited TCP New Reno flow, with an
     IW set to 3 or 10 packets.  The size of the data transmitted MUST
     be strictly higher than 10 packets and should be lower than 100
     packets.

	The transmission of both flows must not start simultaneously: a =
steady
	state must be achieved before the transmission of the =
application limited=20
	flow. As a result, the transmission of the non application =
limited flow MUST
	start before the transmission of the application limited flow.

  For each of these scenarios, the graphs described in Section 2.6 MUST
  be generated for each class of traffic.  The completion time of the
  application limited TCP flow could be measured.
"

> What are the <parms> for graphs according to section 2.6?=20
>=20
> Section 4.5: Traffic Mix
>=20
> The section defines its own traffic mixes in a table, but requires the=20=

> graphs according to 2.6, which somehow implies the Tmix traffic.
>=20

Now that the graphs in 2.6 have been more clearly detailed, and saying =
that they must be generated for each class of traffic, is it better ?=20

> Section 6: Burst absorption
>=20
> Same as above; the test comes with its own traffic mix, but requests=20=

> graphs according to 2.6, thus implying Tmix.
>=20

Now that the graphs in 2.6 have been more clearly detailed, and saying =
that they must be generated for each class of traffic, is it better ?

> The proposed bursty scenarios seem to be not specific enough, if=20
> compared with 4.5.
>=20

I do not see an important difference of details between the bursty =
scenario and section 4.5.

> I would propose here, for reproducibility, something like UDP on/off=20=

> background traffic.
>=20

Yes - I have added more cases. =20

> Section 7: Stability
>=20
> This section mixes two different things:=20
> (a) The impact of general drop rate by other cross traffic, which is=20=

> unrelated to the bottleneck link.=20
> (b) Reaction to varying link capacity at the bottleneck.
>=20
> The general drop rate experiment (a) is weakly specified: If the drop=20=

> rate is too high, the bottleneck capacity cannot be reached; AQM does=20=

> not matter. Or, the other way round, if the drop rate is too low, the=20=

> AQM algorithm dominates the drop process, whereas the background drops=20=

> don't really matter. Only the transition between both regimes could be=20=

> of interest. But how to get there, and is this of relevance in =
practice?
>=20

I propose to add the following scenario:
"
 This scenario helps to evaluate how an AQM scheme reacts to incoming
  traffic resulting in various level of congestions during the
  experiment.  In this scenario, the congestion level varies according
  to a large time scale.  The following phases may be considered: phase
  I - mild congestion during 0-5s; phase II - medium congestion during
  5-10s; phase III - heavy congestion during 10-15s; phase I again, ...
  and so on. Each single lived non application limited TCP flow
  transfers data.

  For this scenario, the graphs described in Section 2.6 MUST be
  generated.  Moreover, one graph SHOULD be generated for each of the
  phases previously detailed.
"

> The varying capacity experiment (b) is really relevant. I am asking=20
> myself, if there could be resonant effects in the AQM parameter=20
> adaptation algorithms, and how to test for this?
>=20

This is why we tried to mention in the "parameters sensitivity" section. =
Proposing scenarios for the resonant effects adaptation algorithms of =
AQM is not an easy task.

Thanks a lot for your useful comments.=20
Please let us know if our modifications could assess your remarks.=20

Kind regards,=20

Nicolas Kuhn=

--Apple-Mail=_41C43DC1-762C-4400-8721-806DDE526AF9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Dear Wolfram,&nbsp;</div><div><br></div><div>Thanks a lot for =
your useful feedback.&nbsp;</div><div>Pleas, have a look at my answer =
inline.&nbsp;</div><div><br></div><div>Kind =
regards,&nbsp;</div><div><br></div><div>Nicolas</div><div><br></div><div>O=
n Aug 12, 2014, at 10:04 AM, "LAUTENSCHLAEGER, Wolfram (Wolfram)" &lt;<a =
href=3D"mailto:wolfram.lautenschlaeger@alcatel-lucent.com">wolfram.lautens=
chlaeger@alcatel-lucent.com</a>&gt; wrote:<br><br><blockquote =
type=3D"cite">I agree with most of the suggested features that must be =
tested&nbsp;<br>for AQM evaluation.<br><br>But I have some doubts if the =
proposed experiments/metrics<br>are really applicable and able to reveal =
the required features.<br><br>My comments in detail:<br><br>Section 2.1: =
Flow completion time:<br><br>Is applicable only for equally sized finite =
flows.&nbsp;<br>Not really meaningful for variable sized flows, e.g. the =
Tmix trace.&nbsp;<br>Not applicable to infinite =
flows.<br><br></blockquote><br>This comment points out that the metrics =
may not suit to every traffic detailed in the rest of the draft.<br>As, =
in this Section 2, we just list the metrics that can be measured, I =
propose to add the following paragraph in the beginning of Section =
2:<br>"The metrics listed in this section may not suit every type of =
traffic detailed in the rest of this document: all of the following =
metrics MAY not be measured. For each scenario, the metrics should be =
selected among the following list, depending on the traffic =
considered."<br><br><blockquote type=3D"cite">Section 2.2: Packet =
loss:&nbsp;<br><br>- Long term loss probability is meaningful only in a =
steady state<br>scenario. And it characterizes the TCP flavor, not the =
AQM. (Loss<br>probability remains the same, whatever you do with AQM, as =
long as you<br>reach roughly the same =
throughput.)<br><br></blockquote><br>The long term loss probability =
might not be of interests for all the scenarios. In order to make the =
presentation of this metric more general, we could evaluate the packet =
drop probability over the time of the experiment.&nbsp;<br><br>I propose =
to replace "the long term packet loss probability" by :<br>"&nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- the =
packet loss probability: this metric should be frequently measured =
during the experiment as the long term loss probability is of interests =
for steady state scenarios only;"<br><br><blockquote type=3D"cite">- =
interval between consecutive losses: If the losses are well =
spaced,<br>it resembles somehow the loss probability. If not well spaced =
(bursty),&nbsp;<br>what to record?<br><br></blockquote><br>To illustrate =
the interval between losses, we could propose to measure the time =
between two losses and provide the minimum, 5%, median, 95%, maximum =
values of the set of "interval times".<br><br>I propose to replace "the =
interval between consecutive losses" by :&nbsp;<br>"<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>- the =
interval between consecutive losses: the time between two losses should =
be measured. =46rom the set of interval times, the tester should present =
the median value, the minimum and maximum values and the 10th and 90th =
percentiles."&nbsp;<br><br><blockquote type=3D"cite">- packet loss =
patterns: Metric is undefined, except the special case&nbsp;<br>"packet =
loss synchronization", next section, 2.3. It is, indeed, =
highly&nbsp;<br>interesting qualitatively in non-stationary cases, e.g. =
abrupt capacity&nbsp;<br>drop. But how to =
quantify?<br><br></blockquote><br>I agree that it will be hard to =
quantify this metric. The idea behind the "packet loss pattern", is to =
have a &nbsp;description of the loss pattern, that might be obtained by =
considering the loss probability and the interval between consecutive =
losses. As a result, we will remove the "packet loss patterns" for the =
next version of the document.&nbsp;<br><br><blockquote =
type=3D"cite">Section 2.4: Goodput:&nbsp;<br><br>- Meaningful only with =
steady state occupancy by a number of more or&nbsp;<br>less greedy TCP =
flows. Here it shows, to which extent the AQM is able&nbsp;<br>to keep a =
link close to the 100% utilization.&nbsp;<br><br>- With a trace of =
variable sized flows (Tmix) the goodput resembles the&nbsp;<br>traffic =
offer (if in total below the link capacity; not =
overloaded).&nbsp;<br><br>- The overload scenario does not reach steady =
state. Goodput in&nbsp;<br>overload cases is highly dependent on other =
things than AQM, e.g. test&nbsp;<br>duration or shuffling of the =
trace.<br><br></blockquote><br>Indeed, some things need to be clarified. =
I propose to add the following paragraph:&nbsp;<br>" The measurement of =
the goodput let the tester evaluate to which extend the AQM is able to =
keep an high link utilization. This metric should be obtained frequently =
during the experiment: the long term goodput makes sense for =
steady-state scenarios only and may not reflect how the introduction of =
AQM actually impacts on the link utilization. It is worth pointing out =
that the fluctuations of this measurement may depend on other things =
than the introduction of an AQM, such as physical layer losses, =
fluctuating bandwidths (Wi-Fi), heavy congestion levels or transport =
layer congestion controls."<br><br><blockquote type=3D"cite">Section =
2.6: Trade-off latency vs. goodput:<br><br>The section refers to two =
(x,y) plots of the =
form:<br>&nbsp;&nbsp;&nbsp;&nbsp;X=3Ddelay(parms)<br>&nbsp;&nbsp;&nbsp;&nb=
sp;Y=3Dgoodput(parms)<br>and<br>&nbsp;&nbsp;&nbsp;&nbsp;X=3Ddelay(parms)<b=
r>&nbsp;&nbsp;&nbsp;&nbsp;Y=3Ddrop_ratio(parms)<br>where &lt;parms&gt; =
are tuples of parameter values, each describing&nbsp;<br>one =
experimental set-up.<br><br>It remains unclear, what &lt;parms&gt; might =
be in the context of the given&nbsp;<br>document. The cited document =
[TCPEVAL2013] suggests that one dimension&nbsp;<br>of &lt;parms&gt; =
might be the scaling of the applied Tmix trace. The =
other&nbsp;<br>parameters in the cited documents are not applicable =
here. More on this&nbsp;<br>see below.<br><br></blockquote><br>More =
precisions should have been given on how to generate this =
graphs.&nbsp;<br>I propose to add the following =
paragraph:&nbsp;<br>"Each of the end-to-end delay, goodput and drop =
probability should be measured every second. =46rom each of this sets of =
measurements, the 10th and 90th percentile and the median value should =
be computed. For each scenario case, an ellipse can be generated from =
the measurement of the percentiles and a point for the median value can =
be plotted."<br><br><blockquote type=3D"cite">Section 4.1: TCP-friendly =
sender:<br><br>Requires the plots according to section 2.6. But at the =
same time it&nbsp;<br>specifies one single long-lived, non application =
limited flow - this is&nbsp;<br>one single dot in each of the =
plots.<br><br></blockquote><br>See above<br><br><blockquote =
type=3D"cite">Section 4.2: Aggressive Transport Sender: same =
problem<br><br></blockquote><br>See above<br><br><blockquote =
type=3D"cite">Section 4.3: Unresponsive Transport: same =
problem;<br></blockquote><br>See above<br><br><blockquote =
type=3D"cite">moreover:<br><br>Scenario is only applicable to =
scheduling, not to AQM. The described&nbsp;<br>traffic simply overloads =
the link with no response to AQM (that is, to&nbsp;<br>my understanding =
the meaning of unresponsive traffic). A "long-lived&nbsp;<br>non =
application limited UDP flow" is somewhat infinite, other than =
its&nbsp;<br>counterpart TCP.<br><br>I would suggest a different test =
here: In a mixture of responsive and&nbsp;<br>unresponsive traffic do a =
test, to which extent the AQM scheme is still&nbsp;<br>able to keep the =
responsive fraction under control. This requires that&nbsp;<br>the =
unresponsive traffic is well below the capacity limit. =
The&nbsp;<br>rationale behind this test is that an AQM scheme might =
under- or&nbsp;<br>over-react if it drops packets but does not see the =
expected reduction.<br><br></blockquote><br>I propose the following =
text:&nbsp;<br>" &nbsp;&nbsp;&nbsp;The first scenario is the following. =
&nbsp;In order to create a test<br>&nbsp;&nbsp;environment that results =
in queue build up, we consider unresponsive<br>&nbsp;&nbsp;flow(s) whose =
sending rate is greater than the bottleneck link<br>&nbsp;&nbsp;capacity =
between routers L and R. This scenario consists of a =
long-<br>&nbsp;&nbsp;lived non application limited UDP flow transmits =
data between sender<br>&nbsp;&nbsp;A and receiver B. Graphs described in =
Section 2.6 MUST be generated.<br><br>&nbsp;&nbsp;The second scenario is =
the following. &nbsp;In order to test to which<br>&nbsp;&nbsp;extend the =
AQM scheme is able to keep responsive fraction =
under<br>&nbsp;&nbsp;control, this scenario considers a mixture of =
TCP-friendly and<br>&nbsp;&nbsp;unresponsive traffics. &nbsp;This =
scenario consists of a long-lived non<br>&nbsp;&nbsp;application limited =
UDP flow and a single long-lived, non =
application<br>&nbsp;&nbsp;limited, TCP New Reno flow that transmit data =
between sender A and<br>&nbsp;&nbsp;receiver B. As opposed to the first =
scenario, the rate of the UDP<br>&nbsp;&nbsp;traffic should not be =
greater than the bottleneck capacity, and<br>&nbsp;&nbsp;should not be =
higher than half of the bottleneck capacity. &nbsp;For =
each<br>&nbsp;&nbsp;type of traffic, the graphs described in Section 2.6 =
MUST be<br>&nbsp;&nbsp;generated. "<br><br><blockquote =
type=3D"cite">Section 4.4: Initial Congestion Window:<br><br>Makes sense =
only with a mix of short lived flows. For long-lived flows&nbsp;<br>the =
IW does not matter. Alternatively a single experiment of a =
pre-<br>existing long-lived flow and a newly appearing IW3/IW10 flow =
could be&nbsp;<br>executed. But there is no reference to any traffic =
mix. The table&nbsp;<br>specifies just 2 flows in =
parallel.<br><br></blockquote><br>New paragraph for this =
scenario:&nbsp;<br>" &nbsp;&nbsp;&nbsp;This scenario helps evaluate how =
an AQM scheme adapts to a traffic<br>&nbsp;&nbsp;mix consisting of TCP =
flows with different values for the initial<br>&nbsp;&nbsp;congestion =
window (IW).<br><br>&nbsp;&nbsp;For this scenario, we consider two types =
of flow that MUST be<br>&nbsp;&nbsp;generated between sender A and =
receiver B:<br><br>&nbsp;&nbsp;o &nbsp;a single long-lived non =
application limited TCP New Reno flow;<br><br>&nbsp;&nbsp;o &nbsp;a =
single long-lived application limited TCP New Reno flow, with =
an<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;IW set to 3 or 10 packets. &nbsp;The =
size of the data transmitted MUST<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;be =
strictly higher than 10 packets and should be lower than =
100<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;packets.<br><br><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">	</span>The =
transmission of both flows must not start simultaneously: a =
steady<br><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
</span>state must be achieved before the transmission of the application =
limited&nbsp;<br><span class=3D"Apple-tab-span" style=3D"white-space: =
pre; ">	</span>flow. As a result, the transmission of the non =
application limited flow MUST<br><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>start before the transmission of =
the application limited flow.<br><br>&nbsp;&nbsp;For each of these =
scenarios, the graphs described in Section 2.6 MUST<br>&nbsp;&nbsp;be =
generated for each class of traffic. &nbsp;The completion time of =
the<br>&nbsp;&nbsp;application limited TCP flow could be =
measured.<br>"<br><br><blockquote type=3D"cite">What are the =
&lt;parms&gt; for graphs according to section 2.6?&nbsp;<br><br>Section =
4.5: Traffic Mix<br><br>The section defines its own traffic mixes in a =
table, but requires the&nbsp;<br>graphs according to 2.6, which somehow =
implies the Tmix traffic.<br><br></blockquote><br>Now that the graphs in =
2.6 have been more clearly detailed, and saying that they must be =
generated for each class of traffic, is it better =
?&nbsp;<br><br><blockquote type=3D"cite">Section 6: Burst =
absorption<br><br>Same as above; the test comes with its own traffic =
mix, but requests&nbsp;<br>graphs according to 2.6, thus implying =
Tmix.<br><br></blockquote><br>Now that the graphs in 2.6 have been more =
clearly detailed, and saying that they must be generated for each class =
of traffic, is it better ?<br><br><blockquote type=3D"cite">The proposed =
bursty scenarios seem to be not specific enough, if&nbsp;<br>compared =
with 4.5.<br><br></blockquote><br>I do not see an important difference =
of details between the bursty scenario and section =
4.5.<br><br><blockquote type=3D"cite">I would propose here, for =
reproducibility, something like UDP on/off&nbsp;<br>background =
traffic.<br><br></blockquote><br>Yes - I have added more cases. =
&nbsp;<br><br><blockquote type=3D"cite">Section 7: Stability<br><br>This =
section mixes two different things:&nbsp;<br>(a) The impact of general =
drop rate by other cross traffic, which is&nbsp;<br>unrelated to the =
bottleneck link.&nbsp;<br>(b) Reaction to varying link capacity at the =
bottleneck.<br><br>The general drop rate experiment (a) is weakly =
specified: If the drop&nbsp;<br>rate is too high, the bottleneck =
capacity cannot be reached; AQM does&nbsp;<br>not matter. Or, the other =
way round, if the drop rate is too low, the&nbsp;<br>AQM algorithm =
dominates the drop process, whereas the background drops&nbsp;<br>don't =
really matter. Only the transition between both regimes could =
be&nbsp;<br>of interest. But how to get there, and is this of relevance =
in practice?<br><br></blockquote><br>I propose to add the following =
scenario:<br>"<br>&nbsp;This scenario helps to evaluate how an AQM =
scheme reacts to incoming<br>&nbsp;&nbsp;traffic resulting in various =
level of congestions during the<br>&nbsp;&nbsp;experiment. &nbsp;In this =
scenario, the congestion level varies according<br>&nbsp;&nbsp;to a =
large time scale. &nbsp;The following phases may be considered: =
phase<br>&nbsp;&nbsp;I - mild congestion during 0-5s; phase II - medium =
congestion during<br>&nbsp;&nbsp;5-10s; phase III - heavy congestion =
during 10-15s; phase I again, ...<br>&nbsp;&nbsp;and so on. Each single =
lived non application limited TCP flow<br>&nbsp;&nbsp;transfers =
data.<br><br>&nbsp;&nbsp;For this scenario, the graphs described in =
Section 2.6 MUST be<br>&nbsp;&nbsp;generated. &nbsp;Moreover, one graph =
SHOULD be generated for each of the<br>&nbsp;&nbsp;phases previously =
detailed.<br>"<br><br><blockquote type=3D"cite">The varying capacity =
experiment (b) is really relevant. I am asking&nbsp;<br>myself, if there =
could be resonant effects in the AQM parameter&nbsp;<br>adaptation =
algorithms, and how to test for this?<br><br></blockquote><br>This is =
why we tried to mention in the "parameters sensitivity" section. =
Proposing scenarios for the resonant effects adaptation algorithms of =
AQM is not an easy task.<br><br>Thanks a lot for your useful =
comments.&nbsp;<br>Please let us know if our modifications could assess =
your remarks.&nbsp;<br><br>Kind regards,&nbsp;<br><br>Nicolas =
Kuhn</div></body></html>=

--Apple-Mail=_41C43DC1-762C-4400-8721-806DDE526AF9--


From nobody Fri Aug 29 06:17:48 2014
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 084AF1A02ED for <aqm@ietfa.amsl.com>; Fri, 29 Aug 2014 06:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.57
X-Spam-Level: 
X-Spam-Status: No, score=-7.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-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 ls6V22EJQSwU for <aqm@ietfa.amsl.com>; Fri, 29 Aug 2014 06:17:42 -0700 (PDT)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A63081A030F for <aqm@ietf.org>; Fri, 29 Aug 2014 06:17:42 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.04,424,1406617200"; d="scan'208";a="143002041"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx11-out.netapp.com with ESMTP; 29 Aug 2014 06:17:42 -0700
Received: from HIOEXCMBX05-PRD.hq.netapp.com (10.122.105.38) by vmwexceht06-prd.hq.netapp.com (10.106.77.104) with Microsoft SMTP Server (TLS) id 14.3.123.3; Fri, 29 Aug 2014 06:17:11 -0700
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.913.22; Fri, 29 Aug 2014 06:17:10 -0700
Received: from HIOEXCMBX05-PRD.hq.netapp.com ([fe80::f0a5:80a1:86de:fa66]) by hioexcmbx05-prd.hq.netapp.com ([fe80::f0a5:80a1:86de:fa66%21]) with mapi id 15.00.0913.011; Fri, 29 Aug 2014 06:16:58 -0700
From: "Scheffenegger, Richard" <rs@netapp.com>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] adoption call: draft-welzl-ecn-benefits
Thread-Index: AQHPtXNH7fyT7fWkOEa/SOO/NTHNxZvMLA8AgABZOYCAAKjkAIAAC2GAgBpxuOA=
Date: Fri, 29 Aug 2014 13:16:58 +0000
Message-ID: <16141ccda1c843ab8f03fb5f478db010@hioexcmbx05-prd.hq.netapp.com>
References: <53E8D7B0.9040007@mti-systems.com> <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com> <20140811233857.GL45982@verdi> <201408120943.s7C9hRvV024419@bagheera.jungle.bt.co.uk> <53E9EB49.9040509@erg.abdn.ac.uk>
In-Reply-To: <53E9EB49.9040509@erg.abdn.ac.uk>
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/snbopPe00BJc190vGAEev8fA9BU
Subject: Re: [aqm] adoption call: draft-welzl-ecn-benefits
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, 29 Aug 2014 13:17:46 -0000

Hi Gorry,

> > Given QUIC includes FEC to hide losses, I guess it is a good example to
> > consider whether ECN still offers sufficient benefits over and above
> > just removing losses.
> >
> GF: And then, isn't the implication of AQM to significantly increase the
> number of "losses" unless we use ECN?
>=20
> Indeed, I have the impression we are confusing many on these points -
> ECN could change the reaction to congestion signal, and FEC (even
> opportunistic CC-friendly FEC) can also change the way things react to
> congestion signals.

I don't think that an AQM's implication is automatically to increase the nu=
mber of losses; that may happen to specific flows (in particular, unrespons=
ive ones), but for responsive (non-ECN) ones, the expectation would be to d=
e-correlate the losses, and for TCP, to only have around 1 loss per window =
when necessary - instead of a burst loss of one window and the expensive re=
covery...

Perhaps it's that perception that also poses an obstacle to AQM deployment,=
 because of the believe that a dynamic but lower mark/drop threshold will c=
ause more losses?

Regards,
  Richard


From nobody Fri Aug 29 06:52:36 2014
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 493091A0382 for <aqm@ietfa.amsl.com>; Fri, 29 Aug 2014 06:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level: 
X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  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 z5veAytG0ywb for <aqm@ietfa.amsl.com>; Fri, 29 Aug 2014 06:52:32 -0700 (PDT)
Received: from nm23-vm4.access.bullet.mail.gq1.yahoo.com (nm23-vm4.access.bullet.mail.gq1.yahoo.com [216.39.63.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B3A21A038F for <aqm@ietf.org>; Fri, 29 Aug 2014 06:52:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogers.com; s=s1024; t=1409320352; bh=aNnwIunfo1xKwrrWPRmyHUwGlCRLDROEy7zqu5vFm6A=; h=Received:Received:Received:DKIM-Signature:X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ZgzgrAIw0BXs8dfwvR7LO9xF5m9NI55iv3qEGtuSs+XM3QRlN+DHbOxNLNQN5Oy5dlkC40Na/mNf9YSOHZvbi4S1O6eiegNwXgHF/9AEPnrZ6xFqR2DfNMFcKNzYROFRAM3Z9p+5j1Crmr5rGNiMYh3RsI7xIX2F7EHCw85wjXU=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; b=eo7QsAf9dFNlzRlp8YRAAyZvpqjuZuNgYtjNyQWd8zM9yMI1cRdLxxuHLsnRgdgUioeLr6OB9tVDpkUPUckXuNkzRmn8gWJ6SeSKeIg/5zciUixWPCkTlPiDLKlW1ZO5HGv02TMnD4Q6ROSO9iqYp+9WVZRnbu6m740q8rnRei0=;
Received: from [216.39.60.172] by nm23.access.bullet.mail.gq1.yahoo.com with NNFMP; 29 Aug 2014 13:52:32 -0000
Received: from [67.195.22.116] by tm8.access.bullet.mail.gq1.yahoo.com with NNFMP; 29 Aug 2014 13:52:32 -0000
Received: from [127.0.0.1] by smtp111.sbc.mail.gq1.yahoo.com with NNFMP; 29 Aug 2014 13:52:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rogers.com; s=s1024; t=1409320352; bh=aNnwIunfo1xKwrrWPRmyHUwGlCRLDROEy7zqu5vFm6A=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=UIZeivr61B5ohxJud8hrZsFTXonwlc1demkaTtzoyaNYKl6hfceRKHa3wjKs5DlIX5cqER03HkungYw93mfs2+sQltRVELcMZdd2gynMV5DIf2aB6U3gUGBgHqUaqR18D0eHvpwgUPrZvrDj1a00BaipPt27CTIlPWiQxFu+Lco=
X-Yahoo-Newman-Id: 67672.94784.bm@smtp111.sbc.mail.gq1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: qmeRxwkVM1kMSZ8.Y1ujfKXOrN72iw5TE.vsU7swySlcguJ qc301UAXYwqZ2ZfgO1rUMgZ5_f0yXVB_4C0_E3FMZvfb7sV_yAcd8F5HUyjx DV4es_za2RIb.QXGaImtyxzZ3bvg9oRXngVFaJ7eaBYZre1Y5XMwqZbHNjEb GlE50opoX.0hG_KWSFbsFDUMAlz9owBnWeFmrC0j2tw53339FUN3WqRb6vw0 n02n7S12DYJgYoubeZ.EAzd4JEQwqPdGtJQDK4XjJAvfHOFRpjDF.kkZK0ZU l_uJI3aLZUPiwgNGLnvUTkGQfF.nGphleyOQ2SxFYVQEAB0H1Mn6Yjbl9WQl RHXvCLs32Rzpfzcy2bX4peth54.qli2sJGoyt95_2PidBeFOJYAUGw4m8FPT LGmVUqLLZPb39DjESgXrmGeWBR.bOU0AyEwwfU1JTuC.kXsedcobfAayFrkq 54filSFlT8R1nAHd.Jvu2evONLN6b92nR1REsgl9SadELbZ0kQiq5CS0s_pS jvFSI66qjtGSbS4TMX7T981x2JoWmiASiLg--
X-Yahoo-SMTP: sltvjZWswBCRD.ElTuB1l9j6s9wRYPpuyTNWOE5oEg--
Message-ID: <5400859E.6070202@rogers.com>
Date: Fri, 29 Aug 2014 09:52:30 -0400
From: David Collier-Brown <davec-b@rogers.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: aqm@ietf.org
References: <53E8D7B0.9040007@mti-systems.com> <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com> <20140811233857.GL45982@verdi> <201408120943.s7C9hRvV024419@bagheera.jungle.bt.co.uk> <53E9EB49.9040509@erg.abdn.ac.uk> <16141ccda1c843ab8f03fb5f478db010@hioexcmbx05-prd.hq.netapp.com>
In-Reply-To: <16141ccda1c843ab8f03fb5f478db010@hioexcmbx05-prd.hq.netapp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/ECuk-ZE0g7YVgBFSIySUHvUdZd4
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [aqm] adoption call: draft-welzl-ecn-benefits
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: Fri, 29 Aug 2014 13:52:34 -0000

On 08/29/2014 09:16 AM, Scheffenegger, Richard wrote:
> Hi Gorry,
>
>>> Given QUIC includes FEC to hide losses, I guess it is a good example to
>>> consider whether ECN still offers sufficient benefits over and above
>>> just removing losses.
>>>
>> GF: And then, isn't the implication of AQM to significantly increase the
>> number of "losses" unless we use ECN?
>>
>> Indeed, I have the impression we are confusing many on these points -
>> ECN could change the reaction to congestion signal, and FEC (even
>> opportunistic CC-friendly FEC) can also change the way things react to
>> congestion signals.
> I don't think that an AQM's implication is automatically to increase the number of losses; that may happen to specific flows (in particular, unresponsive ones), but for responsive (non-ECN) ones, the expectation would be to de-correlate the losses, and for TCP, to only have around 1 loss per window when necessary - instead of a burst loss of one window and the expensive recovery...
>
> Perhaps it's that perception that also poses an obstacle to AQM deployment, because of the believe that a dynamic but lower mark/drop threshold will cause more losses?

Goodness gracious, from the point of  view of a queuing network, AQM
reduces losses overall, in the process of minimizing delay and keeping
bandwidth use just below the theoretical maximum.

Oversimplifying, we try to keep the buffers empty, so that if we get a
burst we can handle it without losses and without affecting other
communications. We signal via a loss or other indicator if the
non-bursty flow is enough to cause congestion, which keeps the buffers
near-empty and the system uncongested.

Failing to do so fills the buffers without signalling there is
congestion, and induces delay on everyone who's dependant on the buffer.
Not to mention allowing the congestion to go unreported!

It's not a tradeoff discussion: it's arguably one about correctness.

--dave
[Somebody like Neil Gunther could explain the math of this better, but
the behaviour is well-known in the trade, and cordially hated.
Congestion control is superior to admission control, which is what I
often use to prevent the server equivalent of congestive collapse (:-))]



-- 
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 Aug 29 08:26:49 2014
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 44DC21A04F8 for <aqm@ietfa.amsl.com>; Fri, 29 Aug 2014 08:26:47 -0700 (PDT)
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 0FrVfW5EDIfa for <aqm@ietfa.amsl.com>; Fri, 29 Aug 2014 08:26:42 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF8BC1A04F6 for <aqm@ietf.org>; Fri, 29 Aug 2014 08:26:42 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id wn1so1884889obc.35 for <aqm@ietf.org>; Fri, 29 Aug 2014 08:26:42 -0700 (PDT)
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=swvPrrTtEuf4QDwU+TXIg7RaPpYUelIaEpy/LPckulY=; b=h5GXecMTyNNUQWyvRkEKBhtyHU5JHQI+D6QK0RmDy00YJqjxzwJxPltXakJEtymG1r Yy4JQ56rBtuYY3vySkJo5tfdzd1TBG9/M1/HnGzXFHIZKCIakpIUT+crTKSQIozES5e9 u58sqnyw1VLVIpevsjz86LUlSjR5nZ1ytI+FPkSyAiOOfvOZegAVENNxmLeVEw2FxWVL itLstfewdwjLvjcrnb3P5F1hVPSINaHgaqzuZ3j9dcIlxDNya5LneihI67tYVJqhAatA zqoVWQgMgPA23xWXyJ3sou6UOV1hPtYLc0SsFpJyY41NxjE+2QLw+veXEAQDDbL5wLFw YCwg==
MIME-Version: 1.0
X-Received: by 10.182.129.230 with SMTP id nz6mr11144233obb.16.1409326002074;  Fri, 29 Aug 2014 08:26:42 -0700 (PDT)
Received: by 10.202.227.76 with HTTP; Fri, 29 Aug 2014 08:26:42 -0700 (PDT)
In-Reply-To: <53E9EB49.9040509@erg.abdn.ac.uk>
References: <53E8D7B0.9040007@mti-systems.com> <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com> <20140811233857.GL45982@verdi> <201408120943.s7C9hRvV024419@bagheera.jungle.bt.co.uk> <53E9EB49.9040509@erg.abdn.ac.uk>
Date: Fri, 29 Aug 2014 08:26:42 -0700
Message-ID: <CAA93jw7cc_a5bWw=vJ9jD_LVR0=xKdmvzPv-V7Gvof1xdXiVog@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/zQajLcXfF0crcEFliuupKv3vNB8
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] adoption call: draft-welzl-ecn-benefits
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, 29 Aug 2014 15:26:47 -0000

On Tue, Aug 12, 2014 at 3:24 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wro=
te:
> OK, so I have many comments, see below.
>
> Gorry
>
>
> On 12/08/2014 10:43, Bob Briscoe wrote:
>>
>> Wes, and responders so far,
>>
>> A doc on the benefits and pitfalls of ECN is needed. Personally I
>> wouldn't assign much of my own time as a priority for such work; I'd
>> rather work on finding the best road through the protocol engineering.
>> But I'm glad others are doing this.
>>
>> We need to be clear that this doc (at the moment) is about the benefits
>> of 'something like RFC3168 ECN'. I think that is the right direction. I
>> would not be interested in a doc solely about the benefits of 'classic'
>> ECN (we had RFC2884 for that).
>>
>> However, if it is about the benefits of some other ECN-like thing, it
>> will not be worth writing unless it is more concrete on what that other
>> ECN-like thing is. At present different and sometimes conflicting ideas
>> are floating around (I'm to blame for a few).
>>
>> In order to write about benefits, surely experiments are needed to
>> quantify the benefits?

+10

>> Alternatively, this could be a manifesto to
>> identify /potential/ benefits of ECN that the current classic ECN is
>> failing to give. I think at the moment it's the latter (and that's OK
>> given that's where we have reached today).
>>
> GF: If someone wishes to write this research paper, I'd be happy to join
> them, but it was not what I had in mind for this ID.
>
>
>> How about the title "Explicit Congestion Notification (ECN): Benefits,
>> Opportunities and Pitfalls" ?
>>
> GF: I could live with that, if the group wished this!

+1

>
>
>> We (in the RITE project) have agreed to start work on an 'ECN Roadmap'
>> in order to identify all the potential ideas for using ECN coming out of
>> research, and write down whether new standards will be needed for some,
>> whether they can evolve without changing standards, which are
>> complementary, which conflict, etc.

I'd like to see experiments done through the free.fr network as it's the
only one I know of with ecn enabled along the edge in their revolution
v6 product.

Presently cerowrt ships with ecn enabled on the inbound rate
limiter and disabled on the outbound, I have considered enabling
it by default on the outbound for connections > 4mbits.

(users can override these settings, of course)

>>
>> I don't know whether this ECN benefits doc ought to include this
>> detailed ECN roadmap work, but if it's going to talk about "something
>> like ECN" I believe it will have to include a summary of the main items
>> on such a roadmap to be concrete.
>>
>>
>> more inline...
>>
>> At 00:38 12/08/2014, John Leslie wrote:
>>>
>>>    (I have read Michael's reply to this, but I'll respond here.)
>>>
>>> Dave Taht <dave.taht@gmail.com> wrote:
>>> > On Mon, Aug 11, 2014 at 7:48 AM, Wesley Eddy <wes@mti-systems.com>
>>> wrote:
>>> >
>>> >> This draft has been discussed a bit here and in TSVWG:
>>> >> http://tools.ietf.org/html/draft-welzl-ecn-benefits-01
>>>
>>>    I do think this is the right place to discuss it.
>>>
>>> >> As I understand, the IAB has also discussed it a bit, and would
>>> >> be happy if this was something that an IETF working group
>>> >> published.  I believe the TSVWG chairs also discussed this and
>>> >> would be fine if the AQM working group adopted it.
>>>
>>>    Thus, I am in favor of adopting it, with the understanding that
>>> it will see significant changes during our discussion.
>>
>>
>> I think we can and should agree the direction of those changes in this
>> thread. I'd rather not agree to start on a doc and plan to meander.
>>
> GF: +1, we can add comments to the ID to align to this, personally I've
> already said that I'd like to see text on:
> - bleaching and middlebox requirements to deploy.
> - Need to verify the paths actually really *do support* ECN (sorry, but m=
ay
> be needed).

I agree that verifying that a path can take a congestion notification e2e
is important.

>
>
>> I don't think this will be a quick (6 months) job, because of the
>> problem of being clear about the "things like ECN" that it needs to talk
>> about.
>>
> GF: That depends also in part on whether these new mechanisms: will actua=
lly
> change the message to potential users of transports and people considerin=
g
> deployment. In my mind the definition of the protocol techniques does not
> HAVE to be the same document that tells people *HOW* to implement this in
> stacks or network devices. (My own choice would be to keep these to resea=
rch
> papers and RFCs targeted at their respective communities).
>
>
>>
>>> > I don't share the relentless optimism of this document, and would
>>> > like it - or a competing document - to go into the potential negative=
s.
>>>
>>>    I think it should concentrate on what its name says: the benefits
>>> of ECN, both now and in an expected future; but that it should also
>>> at least mention downsides this WG sees: and that it should avoid any
>>> recommendation stronger than "make ECN available to consenting
>>> applications".
>>
>>
>> I agree it should be informative, rather than making too many detailed
>> recommendations.
>>
> GF: Any other bullets listing additional topics are most welcome!
>
>
>>
>>> > examples of this include the TOS washing problem bob alluded to
>>> > in one of the tsvwg meetings (the monday one),
>>>
>>>    This definitely deserves mention.
>>
>>
>> I agree it would be useful to write about deployment problems.
>> Specifically, a clear explanation of what the deployment problems have
>> been, which ones are no longer problems (if any), and which ones are
>> still problems, and how prevalent.
>>
> GF: +1

+1

>
>> Alternatively, folks doing ECN black hole experiments might want to
>> write them up in a separate draft, that this one can refer to (there are
>> already a few research papers documenting ECN deployment experiments). I
>> would be willing to help collect together the history that I have on thi=
s.
>>
> GF: I'm doing these experiments too, happy to work with others.

I have a couple tools for testing bursty loss and QoS and ecn e2e under
development, they are a little buggy, and all dependent on more
recent linux kernels (amusingingly IPv6 works better than IPv4 until
very recently),  and could be improved.

are there other tools available (scamper?)

>
>>
>>> > the impact on competing flows,
>>>
>>>    That might have to go into a companion document. I think this
>>> document could try to describe the bounds of such issues, but not
>>> the details.
>>
>>
>> +1
>>
> GF: +1, I see this as informing the Engineering, not the goals of this
> document.
>
>
>>
>>> > the problem of unresponsive agents or other misuse,
>>>
>>>    I'm not sure what Dave is alluding to here...
>>
>>
>> Dave is alluding to suppression of ECN in the feedback loop (e.g. by the
>> receiver) or the sender not responding (the problem space that ConEx and
>> the ECN Nonce target).
>>
> GF: I'd be glad to include something on this (not detailing a mechanism, =
but
> perhaps linked "how do we know the path supports ECN", and perhaps if the
> group is smart - how can the transport actually find this stuff out for
> itself? (sorry to keep returning to this)

For TCP it seems rather hard to fix in the field. I could see supplying the
syn/ack with a CE as one example. Newer protocols (quic/nada?) could
do something more robust and periodically probe...

>>
>>> > the deprecation (?) of the nonce mechanism,
>>>
>>>    I don't accept it as a given that the nonce should be deprecated;
>>> though I do think that discussion will come up.
>>
>>
>> It would also be useful to write about cheating problems.
>>
> GF: +1
>
>
>> However, an informational doc would not be the right place to deprecate
>> the ECN nonce. That needs to be in a doc that offers an alternative
>> mechanism (which is where draft-moncaster-tcpm-rcv-cheat is heading - we
>> have ideas on how to extend it to ECN cheating).
>>
> GF: - I'd be surprised if this document deprecates an EXP RFC (I've said
> this before), normally I'd expect this in the draft that defines the
> replacement technique.
>
>>
>>> > and how to properly switch between marking and dropping in an aqm.
>>>
>>>    I doubt this document will go into much detail there. Basically,
>>> IMHO, an AQM should mark well before dropping becomes necessary; and
>>> when dropping becomes necessary, ECN-capable packets should be dropped
>>> essentially as often as non-ECN-capable packets.
>>>
>>>    I'm not sure this document should say much about that, though...
>>
>>
>> This might be relevant if talking about how there could be benefits if
>> it were done differently from RFC3168. But otherwise, I agree this would
>> not be on-topic for this doc.
>>
> GF: This could be complicated, but probably depends on how far the WG has
> proceeded in other documents when this document is ready to publish?
>
>>
>>> > There are also the possibilities in new uses for ecn (for example, in
>>> > the original rmcat nada proposal), in usages on local links in routin=
g
>>> > protocols, and in new protocols such as quic, etc.
>>>
>>>    Sounds like interesting reading, Dave -- do you want to send pointer=
s?
>>
>>
>> <http://tools.ietf.org/html/draft-zhu-rmcat-nada-03>

I like the idea of protecting the main frame (P-frame? can never keep these
straight) with ecn, and allowing for loss on the deltas lacking ecn.

Also don't mind the idea of protecting all of a videoconferencing session
with ecn, and reacting to those congestion notifications appropriately.
(assuming that the other problems involving washing, etc, are licked)

>> I assume using ECN on local links in routing protocols is just something
>> Dave is saying that operators could do unilaterally.

A long running research project of mine (over 15 years running) has been to
find a routing protocol that worked well for wireless, and one more holy gr=
ail
has been to find one that reacted well to congestion and differences in
available bandwidth. Most routing protocols
stop at "reachability", and some conflate packet loss with that.

and: ecn marking bgp tcp sessions would be a good way of making sure ecn
worked right in the core. ;/

Please note that although I think I've got tantalizing hints towards
coming up with better routing metrics for wireless or congested
networks as an outgrowth of the bufferbloat work (examples - the new
babel-rtt metric, some improvements on minstrel algorithm's in-kernel
connectivity and bandwidth reporting, and the idea of throwing a
dropped or  marked packet up to user space where a routing daemon
might take a look at it and  it's path and do something smarter about
it) - I've been at it for a long time without much success and don't
want to hold up more productive research elsewhere.

> GF: The IETF has acknowledged alternate ECN semantics via setting the DSC=
P
> field (RFC4774, I recall some historical discussion of why and where), at
> least something could be said about this. I'd like to add at least a
> pointer.
>
>
>> Given QUIC includes FEC to hide losses, I guess it is a good example to
>> consider whether ECN still offers sufficient benefits over and above
>> just removing losses.
>>
> GF: And then, isn't the implication of AQM to significantly increase the
> number of "losses" unless we use ECN?

I routinely run two wired networks with fq_codel with nearly zero loss
using ecn marking. I am curious as to the mark/drop statistics from
other networks that have deployed ecn.

> Indeed, I have the impression we are confusing many on these points - ECN
> could change the reaction to congestion signal, and FEC (even opportunist=
ic
> CC-friendly FEC) can also change the way things react to congestion signa=
ls.

I'd like to see more hard results from FEC from quic. I'd also love to
see someone trying ECN with bittorrent traffic,
adding it to an existing uTP client like utorrent or transmission
would be straightforward, and an easy way to experiment with ecn from
userspace, and explore the issues with deploying it outside of TCP.

>
>> Cheers
>>
>>
>> Bob
>>
>>
>>> --
>>> John Leslie <john@jlc.net>
>>>
>>> _______________________________________________
>>> aqm mailing list
>>> aqm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/aqm
>>
>>
>> ________________________________________________________________
>> Bob Briscoe,                                                  BT
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>>
>
> Gorry
>
> P.S. My proposal is that if this thread converges I intend to parse a lat=
er
> version and see if my co-author and I can then add some comments to our
> draft to catalogue a set of issues that we expect to see added in future,
> and an appendix of those we think may be out of scope.
>
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm



--=20
Dave T=C3=A4ht

NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_=
indecent.article


From nobody Fri Aug 29 08:43:49 2014
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 2D2611A0649 for <aqm@ietfa.amsl.com>; Fri, 29 Aug 2014 08:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level: 
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 i7THg3C2WeaI for <aqm@ietfa.amsl.com>; Fri, 29 Aug 2014 08:43:40 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 091E21A0535 for <aqm@ietf.org>; Fri, 29 Aug 2014 08:43:39 -0700 (PDT)
Received: by spey.erg.abdn.ac.uk (Postfix, from userid 5001) id 687482B44AD; Fri, 29 Aug 2014 16:43:38 +0100 (BST)
Received: from gorry-mac.erg.abdn.ac.uk (gorry-mac.erg.abdn.ac.uk [139.133.207.5]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 9D6682B4415; Fri, 29 Aug 2014 16:43:37 +0100 (BST)
Message-ID: <54009FA9.2070606@erg.abdn.ac.uk>
Date: Fri, 29 Aug 2014 16:43:37 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: davecb@spamcop.net, aqm@ietf.org
References: <53E8D7B0.9040007@mti-systems.com> <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com> <20140811233857.GL45982@verdi> <201408120943.s7C9hRvV024419@bagheera.jungle.bt.co.uk> <53E9EB49.9040509@erg.abdn.ac.uk> <16141ccda1c843ab8f03fb5f478db010@hioexcmbx05-prd.hq.netapp.com> <5400859E.6070202@rogers.com>
In-Reply-To: <5400859E.6070202@rogers.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/gYtyi6tF-nLuKHknPGDhmpySoks
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [aqm] adoption call: draft-welzl-ecn-benefits
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
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, 29 Aug 2014 15:43:43 -0000

On 29/08/2014 14:52, David Collier-Brown wrote:
> On 08/29/2014 09:16 AM, Scheffenegger, Richard wrote:
>> Hi Gorry,
>>
>>>> Given QUIC includes FEC to hide losses, I guess it is a good example to
>>>> consider whether ECN still offers sufficient benefits over and above
>>>> just removing losses.
>>>>
>>> GF: And then, isn't the implication of AQM to significantly increase the
>>> number of "losses" unless we use ECN?
>>>
>>> Indeed, I have the impression we are confusing many on these points -
>>> ECN could change the reaction to congestion signal, and FEC (even
>>> opportunistic CC-friendly FEC) can also change the way things react to
>>> congestion signals.
>> I don't think that an AQM's implication is automatically to increase the number of losses; that may happen to specific flows (in particular, unresponsive ones), but for responsive (non-ECN) ones, the expectation would be to de-correlate the losses, and for TCP, to only have around 1 loss per window when necessary - instead of a burst loss of one window and the expensive recovery...
>>
>> Perhaps it's that perception that also poses an obstacle to AQM deployment, because of the believe that a dynamic but lower mark/drop threshold will cause more losses?
>
> Goodness gracious, from the point of  view of a queuing network, AQM
> reduces losses overall, in the process of minimizing delay and keeping
> bandwidth use just below the theoretical maximum.
>
> Oversimplifying, we try to keep the buffers empty, so that if we get a
> burst we can handle it without losses and without affecting other
> communications. We signal via a loss or other indicator if the
> non-bursty flow is enough to cause congestion, which keeps the buffers
> near-empty and the system uncongested.
>
Yep that's what I think is the goal.

> Failing to do so fills the buffers without signalling there is
> congestion, and induces delay on everyone who's dependant on the buffer.
> Not to mention allowing the congestion to go unreported!
>
> It's not a tradeoff discussion: it's arguably one about correctness.
>
> --dave
> [Somebody like Neil Gunther could explain the math of this better, but
> the behaviour is well-known in the trade, and cordially hated.
> Congestion control is superior to admission control, which is what I
> often use to prevent the server equivalent of congestive collapse (:-))]
>

I agree that AQM often reduces losses (what I said above didn't say 
this) but it sometimes it can increase loss (e.g.  a large RTT or less 
responsive CC), but I don't recall saying something on this in the 
draft. If you see something in the draft that isn't correct then let us 
know.

Gorry




From nobody Sat Aug 30 00:14:23 2014
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 590F21A8833 for <aqm@ietfa.amsl.com>; Sat, 30 Aug 2014 00:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.869
X-Spam-Level: 
X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 WB5JbQEc6zJv for <aqm@ietfa.amsl.com>; Sat, 30 Aug 2014 00:14:17 -0700 (PDT)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 946151A8830 for <aqm@ietf.org>; Sat, 30 Aug 2014 00:14:16 -0700 (PDT)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 067432B40E9; Sat, 30 Aug 2014 08:13:58 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Sat, 30 Aug 2014 08:13:58 +0100
Message-ID: <60ffb9227af06eaf8e33664e1aa58c0c.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <CAA93jw7cc_a5bWw=vJ9jD_LVR0=xKdmvzPv-V7Gvof1xdXiVog@mail.gmail.com>
References: <53E8D7B0.9040007@mti-systems.com> <CAA93jw7ufoEdfGexKMwkSOGLj7LMYBq-nGVPGJt+5G+OHx+ayA@mail.gmail.com> <20140811233857.GL45982@verdi> <201408120943.s7C9hRvV024419@bagheera.jungle.bt.co.uk> <53E9EB49.9040509@erg.abdn.ac.uk> <CAA93jw7cc_a5bWw=vJ9jD_LVR0=xKdmvzPv-V7Gvof1xdXiVog@mail.gmail.com>
Date: Sat, 30 Aug 2014 08:13:58 +0100
From: gorry@erg.abdn.ac.uk
To: "Dave Taht" <dave.taht@gmail.com>
User-Agent: SquirrelMail/1.4.22
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/ltA6M_DBXGt-Ss48EvPEzx8ni8E
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] adoption call: draft-welzl-ecn-benefits
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, 30 Aug 2014 07:14:20 -0000

Please see some thoughts below.

> On Tue, Aug 12, 2014 at 3:24 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk>
> wrote:
>> OK, so I have many comments, see below.
>>
>> Gorry
>>
>>
>> On 12/08/2014 10:43, Bob Briscoe wrote:
>>>
>>> Wes, and responders so far,
>>>
>>> A doc on the benefits and pitfalls of ECN is needed. Personally I
>>> wouldn't assign much of my own time as a priority for such work; I'd
>>> rather work on finding the best road through the protocol engineering.
>>> But I'm glad others are doing this.
>>>
>>> We need to be clear that this doc (at the moment) is about the benefits
>>> of 'something like RFC3168 ECN'. I think that is the right direction. I
>>> would not be interested in a doc solely about the benefits of 'classic'
>>> ECN (we had RFC2884 for that).
>>>
>>> However, if it is about the benefits of some other ECN-like thing, it
>>> will not be worth writing unless it is more concrete on what that other
>>> ECN-like thing is. At present different and sometimes conflicting ideas
>>> are floating around (I'm to blame for a few).
>>>
>>> In order to write about benefits, surely experiments are needed to
>>> quantify the benefits?
>
> +10
>
GF: Interesting suggestions, thanks. We'd be happy to see research to
quantify the benefits of specific methods in a range of scenarios. 
However, this draft is intended to be a long-lived document that speaks of
the potential benefits that ECN can offer across the Internet in general.

>>> Alternatively, this could be a manifesto to
>>> identify /potential/ benefits of ECN that the current classic ECN is
>>> failing to give. I think at the moment it's the latter (and that's OK
>>> given that's where we have reached today).
>>>
>> GF: If someone wishes to write this research paper, I'd be happy to join
>> them, but it was not what I had in mind for this ID.
>>
>>
>>> How about the title "Explicit Congestion Notification (ECN): Benefits,
>>> Opportunities and Pitfalls" ?
>>>
>> GF: I could live with that, if the group wished this!
>
> +1
>
>>
>>
>>> We (in the RITE project) have agreed to start work on an 'ECN Roadmap'
>>> in order to identify all the potential ideas for using ECN coming out
>>> of
>>> research, and write down whether new standards will be needed for some,
>>> whether they can evolve without changing standards, which are
>>> complementary, which conflict, etc.
>
> I'd like to see experiments done through the free.fr network as it's the
> only one I know of with ecn enabled along the edge in their revolution
> v6 product.
>
> Presently cerowrt ships with ecn enabled on the inbound rate
> limiter and disabled on the outbound, I have considered enabling
> it by default on the outbound for connections > 4mbits.
> (users can override these settings, of course)
>
GF: Understood.


>>>
>>> I don't know whether this ECN benefits doc ought to include this
>>> detailed ECN roadmap work, but if it's going to talk about "something
>>> like ECN" I believe it will have to include a summary of the main items
>>> on such a roadmap to be concrete.
>>>
>>>
>>> more inline...
>>>
>>> At 00:38 12/08/2014, John Leslie wrote:
>>>>
>>>>    (I have read Michael's reply to this, but I'll respond here.)
>>>>
>>>> Dave Taht <dave.taht@gmail.com> wrote:
>>>> > On Mon, Aug 11, 2014 at 7:48 AM, Wesley Eddy <wes@mti-systems.com>
>>>> wrote:
>>>> >
>>>> >> This draft has been discussed a bit here and in TSVWG:
>>>> >> http://tools.ietf.org/html/draft-welzl-ecn-benefits-01
>>>>
>>>>    I do think this is the right place to discuss it.
>>>>
>>>> >> As I understand, the IAB has also discussed it a bit, and would
>>>> >> be happy if this was something that an IETF working group
>>>> >> published.  I believe the TSVWG chairs also discussed this and
>>>> >> would be fine if the AQM working group adopted it.
>>>>
>>>>    Thus, I am in favor of adopting it, with the understanding that
>>>> it will see significant changes during our discussion.
>>>
>>>
>>> I think we can and should agree the direction of those changes in this
>>> thread. I'd rather not agree to start on a doc and plan to meander.
>>>
>> GF: +1, we can add comments to the ID to align to this, personally I've
>> already said that I'd like to see text on:
>> - bleaching and middlebox requirements to deploy.
>> - Need to verify the paths actually really *do support* ECN (sorry, but
>> may be needed).
>
> I agree that verifying that a path can take a congestion notification e2e
> is important.
>
>>> I don't think this will be a quick (6 months) job, because of the
>>> problem of being clear about the "things like ECN" that it needs to
>>> talk
>>> about.
>>>
>> GF: That depends also in part on whether these new mechanisms:
>> will actually change the message
>> to potential users of transports and people considering deployment.
>>
>> In my mind the definition of the protocol techniques does not
>> HAVE to be the same document that tells people *HOW* to implement
>> this in stacks or network devices.
>> (My own choice would be to keep these to research
>> papers and RFCs targeted at their respective communities).
>>
>>>> > I don't share the relentless optimism of this document, and would
>>>> > like it - or a competing document - to go into the potential
>>>> negatives.
>>>>
>>>>    I think it should concentrate on what its name says: the benefits
>>>> of ECN, both now and in an expected future; but that it should also
>>>> at least mention downsides this WG sees: and that it should avoid any
>>>> recommendation stronger than "make ECN available to consenting
>>>> applications".
>>>
>>>
>>> I agree it should be informative, rather than making too many detailed
>>> recommendations.
>>>
>> GF: Any other bullets listing additional topics are most welcome!
>>
>>
>>>> > examples of this include the TOS washing problem bob alluded to
>>>> > in one of the tsvwg meetings (the monday one),
>>>>
>>>>    This definitely deserves mention.
>>>
>>>
>>> I agree it would be useful to write about deployment problems.
>>> Specifically, a clear explanation of what the deployment problems have
>>> been, which ones are no longer problems (if any), and which ones are
>>> still problems, and how prevalent.
>>>
>> GF: +1
>
> +1
>
>>> Alternatively, folks doing ECN black hole experiments might
>>> want to write them up in a separate draft, that this one can
>>> refer to (there are already a few research
>>> papers documenting ECN deployment experiments).  I would be
>>> willing to help collect together the history that I have on
>>> this.
>>>
>> GF: I'm doing these experiments too, happy to work with others.
>
> I have a couple tools for testing bursty loss and QoS and ecn e2e under
> development, they are a little buggy, and all dependent on more
> recent linux kernels (amusingingly IPv6 works better than IPv4 until
> very recently),  and could be improved.
>
> are there other tools available (scamper?)
>
>>>> > the impact on competing flows,
>>>>
>>>>    That might have to go into a companion document. I think this
>>>> document could try to describe the bounds of such issues, but not
>>>> the details.
>>>
>>> +1
>>>
>> GF: +1, I see this as informing the Engineering, not the goals of this
>> document.
>>
>>>> > the problem of unresponsive agents or other misuse,
>>>>
>>>>    I'm not sure what Dave is alluding to here...
>>>
>>> Dave is alluding to suppression of ECN in the feedback loop
>>> (e.g. by the receiver) or the
>>> sender not responding (the problem space that ConEx and
>>> the ECN Nonce target).
>>>
>> GF: I'd be glad to include something on this (not detailing a,
>> mechanism but perhaps linked to
>> "how do we know the path supports ECN", and perhaps if
>> the
>> group is smart - how can the transport actually find this stuff out for
>> itself? (sorry to keep returning to this)
>
> For TCP it seems rather hard to fix in the field. I could
> see supplying the syn/ack with a CE as
> one example. Newer protocols (quic/nada?) could
> do something more robust and periodically probe...
>
>>>> > the deprecation (?) of the nonce mechanism,
>>>>
>>>>I don't accept it as a given that the nonce should be deprecated;
>>>> though I do think that discussion will come up.
>>>
>>> It would also be useful to write about cheating problems.
>>>
>> GF: +1
>>
>>
>>> However, an informational doc would not be the right place to deprecate
>>> the ECN nonce. That needs to be in a doc that offers an alternative
>>> mechanism (which is where draft-moncaster-tcpm-rcv-cheat is heading -
>>> we have ideas on how to extend it to ECN cheating).
>>>
>> GF: - I'd be surprised if this document deprecates an EXP RFC (I've said
>> this before), normally I'd expect this in the draft that defines the
>> replacement technique.
>>
>>>
>>>> > and how to properly switch between marking and dropping in an aqm.
>>>>
>>>>    I doubt this document will go into much detail there. Basically,
>>>> IMHO, an AQM should mark well before dropping becomes necessary; and
>>>> when dropping becomes necessary, ECN-capable packets should be dropped
>>>> essentially as often as non-ECN-capable packets.
>>>>
>>>>    I'm not sure this document should say much about that, though...
>>>
>>>
>>> This might be relevant if talking about how there could be benefits if
>>> it were done differently from RFC3168. But otherwise, I agree this
>>> would
>>> not be on-topic for this doc.
>>>
>> GF: This could be complicated, but probably depends on how
>> far the WG has proceeded in other
>> documents when this document is ready to publish?
>>
>>>> > There are also the possibilities in new uses for ecn
>>>>  (for example, in the original rmcat
>>>> > nada proposal), in usages on local links in routing
>>>> > protocols, and in new protocols such as quic, etc.
>>>>
>>>>    Sounds like interesting reading, Dave -- do you want to send
>>>> pointers?
>>>
>>> <http://tools.ietf.org/html/draft-zhu-rmcat-nada-03>
>
> I like the idea of protecting the main frame (P-frame?
> can never keep these
> straight) with ecn, and allowing for loss on the deltas lacking ecn.
>
> Also don't mind the idea of protecting all of a videoconferencing session
> with ecn, and reacting to those congestion notifications appropriately.
> (assuming that the other problems involving washing, etc, are licked)
>
>>> I assume using ECN on local links in routing protocols is just
>>> something
>>> Dave is saying that operators could do unilaterally.
>
> A long running research project of mine (over 15 years running)
> has been to find a routing protocol
> that worked well for wireless, and one more holy grail
> has been to find one that reacted well to congestion and differences in
> available bandwidth. Most routing protocols
> stop at "reachability", and some conflate packet loss with that.
>
> and: ecn marking bgp tcp sessions would be a good way of making sure ecn
> worked right in the core. ;/
>
> Please note that although I think I've got tantalizing hints towards
> coming up with better routing metrics for wireless or congested
> networks as an outgrowth of the bufferbloat work (examples - the new
> babel-rtt metric, some improvements on minstrel algorithm's in-kernel
> connectivity and bandwidth reporting, and the idea of throwing a
> dropped or  marked packet up to user space where a routing daemon
> might take a look at it and  it's path and do something smarter about
> it) - I've been at it for a long time without much success and don't
> want to hold up more productive research elsewhere.
>
>> GF: The IETF has acknowledged alternate ECN semantics via setting the
>> DSCP  field (RFC4774, I recall some historical discussion of why
>> and where), at least something
>> could be said about this. I'd like to add at least a pointer.
>>
>>> Given QUIC includes FEC to hide losses, I guess it is a good example to
>>> consider whether ECN still offers sufficient benefits over and above
>>> just removing losses.
>>>
>> GF: And then, isn't the implication of AQM to significantly increase the
>> number of "losses" unless we use ECN?
>
GF: I replied in another thread - what I wrote wasn't what I intended to say.

> I routinely run two wired networks with fq_codel with nearly zero loss
> using ecn marking. I am curious as to the mark/drop statistics from
> other networks that have deployed ecn.
>
>> Indeed, I have the impression we are confusing many on
>> these points - ECN
>> could change the reaction to congestion signal, and FEC
>> (even opportunistic CC-friendly FEC)
>> can also change the way things react to congestion signals.
>
> I'd like to see more hard results from FEC from quic. I'd also love to
> see someone trying ECN with bittorrent traffic,
> adding it to an existing uTP client like utorrent or transmission
> would be straightforward, and an easy way to experiment with ecn from
> userspace, and explore the issues with deploying it outside of TCP.
>
>>> Cheers
>>>
>>> Bob
>>>
>>>> --
>>>> John Leslie <john@jlc.net>
>>>>
>>>> _______________________________________________
>>>> aqm mailing list
>>>> aqm@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/aqm
>>>
>>> ________________________________________________________________
>>> Bob Briscoe,                                                  BT
>>> _______________________________________________
>>> aqm mailing list
>>> aqm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/aqm
>>
>> Gorry
>>
>> P.S. My proposal is that if this thread converges I intend to
>> parse a later version and see if my co-author
>> and I can then add some comments to our draft
>> to catalogue a set of issues that we expect to see added in
>> future, and an appendix of those we think may be out of scope.
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>
> --
> Dave TÃ¤ht
>
> NSFW:
> https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>

So, back to this specific draft.

We (the authors) have already stated that we think this particular draft
should not recommend a specific way of using ECN  and we therefore do not
expect the next version will conclude that "some specific version should
be turned on", but we do expect to more clearly state that ECN marking
should not be violated, i.e. routers / middleboxes shouldn't delete the
codepoint and servers should respond.

Gorry




