
From nobody Sun May  4 19:35:59 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 552721A0213 for <aqm@ietfa.amsl.com>; Sun,  4 May 2014 19:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 fqeF2fZhjS-4 for <aqm@ietfa.amsl.com>; Sun,  4 May 2014 19:35:54 -0700 (PDT)
Received: from atl4mhob03.myregisteredsite.com (atl4mhob03.myregisteredsite.com [209.17.115.41]) by ietfa.amsl.com (Postfix) with ESMTP id BBE6F1A0210 for <aqm@ietf.org>; Sun,  4 May 2014 19:35:54 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.205]) by atl4mhob03.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s452Zo8X022789 for <aqm@ietf.org>; Sun, 4 May 2014 22:35:50 -0400
Received: (qmail 2312 invoked by uid 0); 5 May 2014 02:35:50 -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; 5 May 2014 02:35:50 -0000
Message-ID: <5366F905.7060905@mti-systems.com>
Date: Sun, 04 May 2014 22:35:49 -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.4.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/YmvUlqE9Ms_ZzWkEL4apzLaURLk
Subject: [aqm] last call results on draft-ietf-aqm-recommendation
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, 05 May 2014 02:35:57 -0000

Hello AQMers, the WG last call on the 2309bis / AQM
recommendation draft has turned up a couple of reviews that
said the document isn't quite ready.  I think some of the
comments could be resolved relatively easily with an update,
though others might take some discussion to converge on what
really is needed to say or not say in this document.

There haven't been any responses to these yet that I've seen,
nor a solid set of positive comments.  So, we're not going to
advance this quite yet.

We do want to make progress between now and the next meeting.

We thought that perhaps a webex / teleconference "side meeting"
would give people a chance to talk about next steps and help
to advance this.

If you're interested in participating in this, please respond
to this poll on some possible times:

http://doodle.com/ng3y444te6mbendx

Assuming there's a critical mass of responses, we'll try to
pick a time that's least inconvenient, though guaranteed to
be terrible for some.

Thanks for your feedback on this, and help towards finishing
the document.

-- 
Wes Eddy
MTI Systems


From nobody Wed May 14 11:00:43 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 3771C1A0147; Wed, 14 May 2014 11:00:41 -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 7dZ4jS9v_Ziu; Wed, 14 May 2014 11:00:39 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BDA351A013E; Wed, 14 May 2014 11:00:39 -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.4.2.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140514180039.16149.79444.idtracker@ietfa.amsl.com>
Date: Wed, 14 May 2014 11:00:39 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/KZwqubOSWgqFeIPEMEeLs71rPbg
Cc: aqm@ietf.org
Subject: [aqm] I-D Action: draft-ietf-aqm-recommendation-04.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, 14 May 2014 18:00:41 -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-04.txt
	Pages           : 25
	Date            : 2014-05-14

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, updated
   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-04

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


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 May 14 11:07:52 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 0004E1A0139 for <aqm@ietfa.amsl.com>; Wed, 14 May 2014 11:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level: 
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 tFrJLlElISFz for <aqm@ietfa.amsl.com>; Wed, 14 May 2014 11:07: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 65D211A0124 for <aqm@ietf.org>; Wed, 14 May 2014 11:07:40 -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 6C0CF2B4075 for <aqm@ietf.org>; Wed, 14 May 2014 19:07:33 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Wed, 14 May 2014 19:07:33 +0100
Message-ID: <31c829e1ab82a2426a44c05dca00fffe.squirrel@www.erg.abdn.ac.uk>
Date: Wed, 14 May 2014 19:07:33 +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/_qkmEvzUSMy3YLmxFURnkUFu96U
Subject: [aqm] [Fwd:  I-D Action: draft-ietf-aqm-recommendation-04.txt]
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 May 2014 18:07:44 -0000

There was quite a few comments during WGLC and we have been working from
these to:
- provide some introductory subsections to help people (with subsections
and better text).
- Written more on the role scheduling / multiple queues.
- Clarified  that ECN mark threshold needs to be configurable.
- Reworked the  "knee" para.  Various updates in response to feedback.

We have just posted a new version of the ID that we think addresses the
comments
made during the WGLC.  If you made comments please check this version and
see if you are comfortable with the updated text.


Best wishes,

Gorry & Fred
--------------------------------------------------------------------------


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-04.txt
	Pages           : 25
	Date            : 2014-05-14

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, updated
   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-04

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


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 Wed May 14 18:18:25 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 975CE1A01D5 for <aqm@ietfa.amsl.com>; Wed, 14 May 2014 18:18:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 1zO9ID10hbFM for <aqm@ietfa.amsl.com>; Wed, 14 May 2014 18:18:20 -0700 (PDT)
Received: from atl4mhob05.myregisteredsite.com (atl4mhob05.myregisteredsite.com [209.17.115.43]) by ietfa.amsl.com (Postfix) with ESMTP id BE61E1A00F9 for <aqm@ietf.org>; Wed, 14 May 2014 18:18:20 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob05.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s4F1ICtk006060 for <aqm@ietf.org>; Wed, 14 May 2014 21:18:12 -0400
Received: (qmail 21725 invoked by uid 0); 15 May 2014 01:18:12 -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; 15 May 2014 01:18:12 -0000
Message-ID: <537415CE.20106@mti-systems.com>
Date: Wed, 14 May 2014 21:18:06 -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.5.0
MIME-Version: 1.0
To: "aqm@ietf.org" <aqm@ietf.org>
References: <5366F905.7060905@mti-systems.com>
In-Reply-To: <5366F905.7060905@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/44tOlJ2u0lZvu_3p6v5DWvooF2g
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 15 May 2014 01:18:22 -0000

On 5/4/2014 10:35 PM, Wesley Eddy wrote:
>
> ...
> 
> We thought that perhaps a webex / teleconference "side meeting"
> would give people a chance to talk about next steps and help
> to advance this.
> 
> If you're interested in participating in this, please respond
> to this poll on some possible times:
> 
> http://doodle.com/ng3y444te6mbendx
> 
> Assuming there's a critical mass of responses, we'll try to
> pick a time that's least inconvenient, though guaranteed to
> be terrible for some.


There was a pretty light response to this, which I interpret to mean
that most people aren't too interested in participating in a side
meeting on the draft.  Since this is a long IETF "break" between F2F
meetings, and we want to make progress, we may instead setup a call
sometime in June on all of the working group "business" in order to
get some momentum up and better prepare for the Toronto IETF meeting.

Since the updated draft is now out (thanks Gorry & Fred!), it
would be helpful if the folks who commented on it could glance
at the diffs, and let us know if it meets at least some of the
points made.


-- 
Wes Eddy
MTI Systems


From nobody Thu May 15 02:10:15 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 911F81A0277 for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 02:10:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.252
X-Spam-Level: 
X-Spam-Status: No, score=-3.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, 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 UjeKJ7gsw1SW for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 02:10:12 -0700 (PDT)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.99]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 024BF1A0275 for <aqm@ietf.org>; Thu, 15 May 2014 02:10:11 -0700 (PDT)
Received: from EVMHR72-UKRD.domain1.systemhost.net (10.36.3.110) by EVMHR68-UKRD.bt.com (10.187.101.23) with Microsoft SMTP Server (TLS) id 8.3.279.1; Thu, 15 May 2014 10:10:03 +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.279.1; Thu, 15 May 2014 10:10:02 +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; Thu, 15 May 2014 10:09:58 +0100
Received: from BTP075694.jungle.bt.co.uk ([10.109.228.92])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id s4F99uTx026736;	Thu, 15 May 2014 10:09:56 +0100
Message-ID: <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 15 May 2014 10:09:55 +0100
To: Wesley Eddy <wes@mti-systems.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <537415CE.20106@mti-systems.com>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.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/XXJmIg5gLnerwW17zvwgMrnKmeI
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 15 May 2014 09:10:14 -0000

Wes,

I assume you also want comments on the new version. Is there a 
deadline for comments?

I prepared comments on the previous version, but didn't get the time 
to type them up. So I want to try to remedy this with the new version 
(that I haven't read yet).


Bob

At 02:18 15/05/2014, Wesley Eddy wrote:
>On 5/4/2014 10:35 PM, Wesley Eddy wrote:
> >
> > ...
> >
> > We thought that perhaps a webex / teleconference "side meeting"
> > would give people a chance to talk about next steps and help
> > to advance this.
> >
> > If you're interested in participating in this, please respond
> > to this poll on some possible times:
> >
> > http://doodle.com/ng3y444te6mbendx
> >
> > Assuming there's a critical mass of responses, we'll try to
> > pick a time that's least inconvenient, though guaranteed to
> > be terrible for some.
>
>
>There was a pretty light response to this, which I interpret to mean
>that most people aren't too interested in participating in a side
>meeting on the draft.  Since this is a long IETF "break" between F2F
>meetings, and we want to make progress, we may instead setup a call
>sometime in June on all of the working group "business" in order to
>get some momentum up and better prepare for the Toronto IETF meeting.
>
>Since the updated draft is now out (thanks Gorry & Fred!), it
>would be helpful if the folks who commented on it could glance
>at the diffs, and let us know if it meets at least some of the
>points made.
>
>
>--
>Wes Eddy
>MTI Systems
>
>_______________________________________________
>aqm mailing list
>aqm@ietf.org
>https://www.ietf.org/mailman/listinfo/aqm

________________________________________________________________
Bob Briscoe,                                                  BT 


From nobody Thu May 15 05:14:14 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 259E11A03D4 for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 05:14:12 -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 KPW1eJInouLM for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 05:14:10 -0700 (PDT)
Received: from atl4mhob13.myregisteredsite.com (atl4mhob13.myregisteredsite.com [209.17.115.51]) by ietfa.amsl.com (Postfix) with ESMTP id 276181A029A for <aqm@ietf.org>; Thu, 15 May 2014 05:14:10 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.205]) by atl4mhob13.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s4FCE1hv016272 for <aqm@ietf.org>; Thu, 15 May 2014 08:14:01 -0400
Received: (qmail 22285 invoked by uid 0); 15 May 2014 12:14:01 -0000
X-TCPREMOTEIP: 107.46.168.216
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@107.46.168.216) by 0 with ESMTPA; 15 May 2014 12:14:01 -0000
Message-ID: <5374AF87.5080607@mti-systems.com>
Date: Thu, 15 May 2014 08:13:59 -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.5.0
MIME-Version: 1.0
To: Bob Briscoe <bob.briscoe@bt.com>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk>
In-Reply-To: <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/PvOzpeNRVP1ydR7UhOBcHO4jWuE
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 15 May 2014 12:14:12 -0000

On 5/15/2014 5:09 AM, Bob Briscoe wrote:
> Wes,
> 
> I assume you also want comments on the new version. Is there a deadline
> for comments?


Absolutely, yes.  There's no "deadline" at the moment, but it would
be good to get any out sooner rather than later, especially if they're
likely to need more discussion or are asking for major changes.


> I prepared comments on the previous version, but didn't get the time to
> type them up. So I want to try to remedy this with the new version (that
> I haven't read yet).


The diffs aren't huge, so many of your comments on the previous
revision might still be valid.


-- 
Wes Eddy
MTI Systems


From nobody Thu May 15 07:33:24 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 6AD0B1A0515 for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 07:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.252
X-Spam-Level: 
X-Spam-Status: No, score=-3.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, 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 EGfhSN8nrpYH for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 07:33:09 -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 7C8671A00B7 for <aqm@ietf.org>; Thu, 15 May 2014 07:32:55 -0700 (PDT)
Received: from EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) by EVMHR04-UKBR.bt.com (10.216.161.36) with Microsoft SMTP Server (TLS) id 8.3.297.1; Thu, 15 May 2014 15:32:44 +0100
Received: from EPHR01-UKIP.domain1.systemhost.net (147.149.196.177) by EVMHR71-UKRD.domain1.systemhost.net (10.36.3.109) with Microsoft SMTP Server (TLS) id 8.3.279.1; Thu, 15 May 2014 15:32:43 +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; Thu, 15 May 2014 15:32:43 +0100
Received: from BTP075694.jungle.bt.co.uk ([10.109.135.46])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id s4FEWeGd027834;	Thu, 15 May 2014 15:32:41 +0100
Message-ID: <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 15 May 2014 15:32:06 +0100
To: Wesley Eddy <wes@mti-systems.com>, Fred Baker <fred@cisco.com>, "Gorry Fairhurst" <gorry@erg.abdn.ac.uk>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <5374AF87.5080607@mti-systems.com>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk> <5374AF87.5080607@mti-systems.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/SOPaOs029M1mz6cszK75Ktd-5vc
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 15 May 2014 14:33:13 -0000

Wes,

Thx. In case I don't get time to read, then type, I'll shoot my mouth 
off anyway...

Sorry this is a bit rushed and dismissive. That's not my intention - 
I'm v supportive of the recommendations that have now been carefully 
and nicely worded. I will give more detailed comments, but these are the MSBs.

1) My main concern: The two halves of the document seemed nearly 
unrelated (at least in draft-03 and it looks like draft-04 hasn't 
changed this). The first half (Sections 1,2,&3) framed the problem as 
primarily about preventing congestion collapse and preventing 
flow-unfairness, while the recommendations (section 4) were about 
AQM. The irony of this sentence is deliberate.

I had few concerns about the recommendations text (section 4), which 
we've all been focusing on, including me. But I hadn't realised the 
introductory text was so out of kilter with the recommendations.

Sections 1,2 and 3 seemed to focus on problems that I wouldn't even 
address with AQM (from a quick scan it looks like these sections 
haven't changed in this respect for draft-04):

a) Congestion collapse: An AQM cannot prevent congestion collapse - 
that is the job of congestion control and, failing that, of policing. 
Even isolation (e.g. flow separation) doesn't prevent congestion 
collapse, because collapse is caused by the load from new flow 
arrivals exceeding the ability of the system to serve and clear load 
from existing flows, most likely because many existing flows are not 
sufficiently responsive to congestion, so retransmissions dominate 
over goodput (even if each unresponsive flow is in an isolated silo). 
Flow separation doesn't help when the problem is too many flows.

b) Flow fairness (or user-fairness etc): this is a policy issue that 
needs to be built in a modular way, for optional addition to AQM. 
Therefore an AQM must also work well without fairness mechanisms. 
This conclusion was actually reached in the early sections, but it's 
not carried forward into the recommendations in section 4.

If the conclusion is that AQM isn't intended to solve these two 
problems, we need to clearly say so. Most people who need to read 
this will be confused, so we shouldn't confuse them further!


2) There's no statement of scope.
Can we really make all these recommendations irrespective of whether 
we're talking about high stat-mux core links, low stat-mux access 
links, low-stat-mux data centre links, or host buffers? Are there 
different recommendations for edge links (on trust boundaries) vs 
interior links? Does AQM apply at L2 as well as L3 (of course it 
does)? Which recommendations are different for each layer? Does AQM 
apply for middleboxes (firewalls, NATs etc) as much as for switches 
and routers? If not why not (only need AQM if there can be queuing - 
perhaps due to processor overload)?

To illustrate the problem, our goal should be AQM in every buffer. 
But we really don't need and shouldn't have policing or isolation in 
every buffer.

4) Because sections 1,2,3 focused heavily on the above two problems 
(collapse and fairness) that can't really be addressed by AQM, these 
sections also gave insufficient attention to problems that AQM does 
address (and should address), E.g.:

* synchronisation and lock-out were both described as vaguely the 
same problem,
* synchronisation wasn't explained,
* lock-out wasn't explained but it was said to be vaguely to do with 
synchronisation and solving it would help low capacity bursty flows,
* large-packet lock-out problems weren't mentioned, only flow-level lock-out.

Perhaps as a result, there's no recommendation on avoiding 
synchronisation (e.g. using randomness).

5) I said these are the MSB's only, but allow me one nit about the Intro:

"  there is currently no consensus solution to controlling the
    congestion caused by such aggressive flows; significant research and
    engineering will be required before any solution will be available.
    It is imperative that this work be energetically pursued, to ensure
    the future stability of the Internet.
"
The draft could at least mention congestion policing and ConEx RFCs 
coming out of the IETF right now (e.g. RFC6789 and 
draft-ietf-conex-abstract-mech, which is with the IESG).


I promise I'll do a proper detailed review of the new text ASAP.


Bob

At 13:13 15/05/2014, Wesley Eddy wrote:
>On 5/15/2014 5:09 AM, Bob Briscoe wrote:
> > Wes,
> >
> > I assume you also want comments on the new version. Is there a deadline
> > for comments?
>
>
>Absolutely, yes.  There's no "deadline" at the moment, but it would
>be good to get any out sooner rather than later, especially if they're
>likely to need more discussion or are asking for major changes.
>
>
> > I prepared comments on the previous version, but didn't get the time to
> > type them up. So I want to try to remedy this with the new version (that
> > I haven't read yet).
>
>
>The diffs aren't huge, so many of your comments on the previous
>revision might still be valid.
>
>
>--
>Wes Eddy
>MTI Systems
>
>_______________________________________________
>aqm mailing list
>aqm@ietf.org
>https://www.ietf.org/mailman/listinfo/aqm

________________________________________________________________
Bob Briscoe,                                                  BT 


From nobody Thu May 15 08:56:15 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 4E9C11A064F for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 08:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level: 
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 IlZ_ZxvZKbZi for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 08:56:05 -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 2310F1A064B for <aqm@ietf.org>; Thu, 15 May 2014 08:56:05 -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 30D3B2B451F; Thu, 15 May 2014 16:55:57 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Thu, 15 May 2014 16:55:57 +0100
Message-ID: <914ee79e5406e90207a8d78cb1196470.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk> <5374AF87.5080607@mti-systems.com> <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk>
Date: Thu, 15 May 2014 16:55:57 +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/Lm7yw8IAuUfS5_m7wTwglu5t5VI
Cc: Wesley Eddy <wes@mti-systems.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Fred Baker <fred@cisco.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 15 May 2014 15:56:12 -0000

Great, I look forward to comments on the actual text. I agree the front
part needs more structure and more topics called out. i started adding
that in -04 and would be pleased to add a few more subsections if we get
agreement.

I'll wait until I see comments before looking at updating the text with Fred.

Gorry

> Wes,
>
> Thx. In case I don't get time to read, then type, I'll shoot my mouth
> off anyway...
>
> Sorry this is a bit rushed and dismissive. That's not my intention -
> I'm v supportive of the recommendations that have now been carefully
> and nicely worded. I will give more detailed comments, but these are the
> MSBs.
>
> 1) My main concern: The two halves of the document seemed nearly
> unrelated (at least in draft-03 and it looks like draft-04 hasn't
> changed this). The first half (Sections 1,2,&3) framed the problem as
> primarily about preventing congestion collapse and preventing
> flow-unfairness, while the recommendations (section 4) were about
> AQM. The irony of this sentence is deliberate.
>
> I had few concerns about the recommendations text (section 4), which
> we've all been focusing on, including me. But I hadn't realised the
> introductory text was so out of kilter with the recommendations.
>
> Sections 1,2 and 3 seemed to focus on problems that I wouldn't even
> address with AQM (from a quick scan it looks like these sections
> haven't changed in this respect for draft-04):
>
> a) Congestion collapse: An AQM cannot prevent congestion collapse -
> that is the job of congestion control and, failing that, of policing.
> Even isolation (e.g. flow separation) doesn't prevent congestion
> collapse, because collapse is caused by the load from new flow
> arrivals exceeding the ability of the system to serve and clear load
> from existing flows, most likely because many existing flows are not
> sufficiently responsive to congestion, so retransmissions dominate
> over goodput (even if each unresponsive flow is in an isolated silo).
> Flow separation doesn't help when the problem is too many flows.
>
That would seem OK to call-out, at least to me.

> b) Flow fairness (or user-fairness etc): this is a policy issue that
> needs to be built in a modular way, for optional addition to AQM.
> Therefore an AQM must also work well without fairness mechanisms.
> This conclusion was actually reached in the early sections, but it's
> not carried forward into the recommendations in section 4.
>
> If the conclusion is that AQM isn't intended to solve these two
> problems, we need to clearly say so. Most people who need to read
> this will be confused, so we shouldn't confuse them further!
>
OK - as long as we get agreement from the various AQM proposals, some
methods rely heavily on flow isolation to achieve their wanted behaviour.

>
> 2) There's no statement of scope.
> Can we really make all these recommendations irrespective of whether
> we're talking about high stat-mux core links, low stat-mux access
> links, low-stat-mux data centre links, or host buffers? Are there
> different recommendations for edge links (on trust boundaries) vs
> interior links? Does AQM apply at L2 as well as L3 (of course it
> does)? Which recommendations are different for each layer? Does AQM
> apply for middleboxes (firewalls, NATs etc) as much as for switches
> and routers? If not why not (only need AQM if there can be queuing -
> perhaps due to processor overload)?
>
> To illustrate the problem, our goal should be AQM in every buffer.
> But we really don't need and shouldn't have policing or isolation in
> every buffer.
>
Hmmm... that will be interesting - suggest a para or two please?

> 4) Because sections 1,2,3 focused heavily on the above two problems
> (collapse and fairness) that can't really be addressed by AQM, these
> sections also gave insufficient attention to problems that AQM does
> address (and should address), E.g.:
>
> * synchronisation and lock-out were both described as vaguely the
> same problem,
> * synchronisation wasn't explained,

yes, agree completely should be added as a subsection in section 2 - This
was overlooked.

> * lock-out wasn't explained but it was said to be vaguely to do with
> synchronisation and solving it would help low capacity bursty flows,
Comment on bullet 3 in Sect 2.

> * large-packet lock-out problems weren't mentioned, only flow-level
> lock-out.
>
OK - suggest a line or two of text please:-)

> Perhaps as a result, there's no recommendation on avoiding
> synchronisation (e.g. using randomness).
>
There should be.

> 5) I said these are the MSB's only, but allow me one nit about the Intro:
>
> "  there is currently no consensus solution to controlling the
>     congestion caused by such aggressive flows; significant research and
>     engineering will be required before any solution will be available.
>     It is imperative that this work be energetically pursued, to ensure
>     the future stability of the Internet.
> "
> The draft could at least mention congestion policing and ConEx RFCs
> coming out of the IETF right now (e.g. RFC6789 and
> draft-ietf-conex-abstract-mech, which is with the IESG).
>
>
> I promise I'll do a proper detailed review of the new text ASAP.
>
>
> Bob
>
> At 13:13 15/05/2014, Wesley Eddy wrote:
>>On 5/15/2014 5:09 AM, Bob Briscoe wrote:
>> > Wes,
>> >
>> > I assume you also want comments on the new version. Is there a
>> deadline
>> > for comments?
>>
>>
>>Absolutely, yes.  There's no "deadline" at the moment, but it would
>>be good to get any out sooner rather than later, especially if they're
>>likely to need more discussion or are asking for major changes.
>>
>>
>> > I prepared comments on the previous version, but didn't get the time
>> to
>> > type them up. So I want to try to remedy this with the new version
>> (that
>> > I haven't read yet).
>>
>>
>>The diffs aren't huge, so many of your comments on the previous
>>revision might still be valid.
>>
>>
>>--
>>Wes Eddy
>>MTI Systems
>>
>>_______________________________________________
>>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
>



From nobody Thu May 15 09:18:21 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 5EFB61A02A1 for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 09:18:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.252
X-Spam-Level: 
X-Spam-Status: No, score=-3.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, 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 Z7Lm4BDBhGp2 for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 09:18:15 -0700 (PDT)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.99]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 323561A02D0 for <aqm@ietf.org>; Thu, 15 May 2014 09:18:14 -0700 (PDT)
Received: from EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) by EVMHR68-UKRD.bt.com (10.187.101.23) with Microsoft SMTP Server (TLS) id 8.3.279.1; Thu, 15 May 2014 17:18:06 +0100
Received: from EPHR02-UKIP.domain1.systemhost.net (147.149.100.81) by EVMHR01-UKBR.domain1.systemhost.net (193.113.108.40) with Microsoft SMTP Server (TLS) id 8.3.297.1; Thu, 15 May 2014 17:18:04 +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; Thu, 15 May 2014 17:18:02 +0100
Received: from BTP075694.jungle.bt.co.uk ([10.109.135.46])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id s4FGHs2Q028155;	Thu, 15 May 2014 17:17:55 +0100
Message-ID: <201405151617.s4FGHs2Q028155@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 15 May 2014 17:17:54 +0100
To: <gorry@erg.abdn.ac.uk>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <914ee79e5406e90207a8d78cb1196470.squirrel@www.erg.abdn.ac. uk>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk> <5374AF87.5080607@mti-systems.com> <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk> <914ee79e5406e90207a8d78cb1196470.squirrel@www.erg.abdn.ac.uk>
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/1hwm8n-Iw6ScVM75-U7uJUzVVF0
Cc: Wesley Eddy <wes@mti-systems.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Fred Baker <fred@cisco.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 15 May 2014 16:18:19 -0000

Gorry,

At 16:55 15/05/2014, gorry@erg.abdn.ac.uk wrote:
>Great, I look forward to comments on the actual text. I agree the front
>part needs more structure and more topics called out. i started adding
>that in -04 and would be pleased to add a few more subsections if we get
>agreement.
>
>I'll wait until I see comments before looking at updating the text with Fred.
>
>Gorry
>
> > Wes,
> >
> > Thx. In case I don't get time to read, then type, I'll shoot my mouth
> > off anyway...
> >
> > Sorry this is a bit rushed and dismissive. That's not my intention -
> > I'm v supportive of the recommendations that have now been carefully
> > and nicely worded. I will give more detailed comments, but these are the
> > MSBs.
> >
> > 1) My main concern: The two halves of the document seemed nearly
> > unrelated (at least in draft-03 and it looks like draft-04 hasn't
> > changed this). The first half (Sections 1,2,&3) framed the problem as
> > primarily about preventing congestion collapse and preventing
> > flow-unfairness, while the recommendations (section 4) were about
> > AQM. The irony of this sentence is deliberate.
> >
> > I had few concerns about the recommendations text (section 4), which
> > we've all been focusing on, including me. But I hadn't realised the
> > introductory text was so out of kilter with the recommendations.
> >
> > Sections 1,2 and 3 seemed to focus on problems that I wouldn't even
> > address with AQM (from a quick scan it looks like these sections
> > haven't changed in this respect for draft-04):
> >
> > a) Congestion collapse: An AQM cannot prevent congestion collapse -
> > that is the job of congestion control and, failing that, of policing.
> > Even isolation (e.g. flow separation) doesn't prevent congestion
> > collapse, because collapse is caused by the load from new flow
> > arrivals exceeding the ability of the system to serve and clear load
> > from existing flows, most likely because many existing flows are not
> > sufficiently responsive to congestion, so retransmissions dominate
> > over goodput (even if each unresponsive flow is in an isolated silo).
> > Flow separation doesn't help when the problem is too many flows.
> >
>That would seem OK to call-out, at least to me.

My concern is that it's wrong to introduce a doc with a description 
of a problem that we're not addressing in the body of the doc (even 
tho collapse is an important problem, AQM doesn't address it, so why 
is it even relevant at all?). E.g. we could also add world hunger to 
the introduction, but it wouldn't be relevant.


> > b) Flow fairness (or user-fairness etc): this is a policy issue that
> > needs to be built in a modular way, for optional addition to AQM.
> > Therefore an AQM must also work well without fairness mechanisms.
> > This conclusion was actually reached in the early sections, but it's
> > not carried forward into the recommendations in section 4.
> >
> > If the conclusion is that AQM isn't intended to solve these two
> > problems, we need to clearly say so. Most people who need to read
> > this will be confused, so we shouldn't confuse them further!
> >
>OK - as long as we get agreement from the various AQM proposals, some
>methods rely heavily on flow isolation to achieve their wanted behaviour.

Indeed, my point about fairness is different from my point about 
collapse (which just isn't even relevant). Fairness isn't strictly 
relevant to AQM, but flow isolation is used to complement AQMs. And 
flow isolation (which the doc calls 'scheduling') can't be done 
without affecting fairness.

So 2.1 concludes:
"  In short, scheduling algorithms and queue management should be seen
    as complementary, not as replacements for each other.
"
This is a conclusion that should be reflected in the recommendations 
and conclusions. I.e. if they are complements, they need to be 
separable, not integrated. Because scheduling requires policy and AQM 
doesn't. So operators don't want to have to face the dilemma of 
needing the AQM part, but not being able to have it because they 
don't want the policy implicit in the scheduling part.

This is critical for fq_codel, because apparently CoDel alone is not 
recommended (which I would agree with). This means that we really 
need fq_X, where X is something that can be recommended either alone 
or with fq.



> >
> > 2) There's no statement of scope.
> > Can we really make all these recommendations irrespective of whether
> > we're talking about high stat-mux core links, low stat-mux access
> > links, low-stat-mux data centre links, or host buffers? Are there
> > different recommendations for edge links (on trust boundaries) vs
> > interior links? Does AQM apply at L2 as well as L3 (of course it
> > does)? Which recommendations are different for each layer? Does AQM
> > apply for middleboxes (firewalls, NATs etc) as much as for switches
> > and routers? If not why not (only need AQM if there can be queuing -
> > perhaps due to processor overload)?
> >
> > To illustrate the problem, our goal should be AQM in every buffer.
> > But we really don't need and shouldn't have policing or isolation in
> > every buffer.
> >
>Hmmm... that will be interesting - suggest a para or two please?

I'll try - but I'm having to write an ETSI doc at the mo (which is 
why I'm preferring to get distracted by AQM :)


> > 4) Because sections 1,2,3 focused heavily on the above two problems
> > (collapse and fairness) that can't really be addressed by AQM, these
> > sections also gave insufficient attention to problems that AQM does
> > address (and should address), E.g.:
> >
> > * synchronisation and lock-out were both described as vaguely the
> > same problem,
> > * synchronisation wasn't explained,
>
>yes, agree completely should be added as a subsection in section 2 - This
>was overlooked.
>
> > * lock-out wasn't explained but it was said to be vaguely to do with
> > synchronisation and solving it would help low capacity bursty flows,
>Comment on bullet 3 in Sect 2.
>
> > * large-packet lock-out problems weren't mentioned, only flow-level
> > lock-out.
> >
>OK - suggest a line or two of text please:-)

Will do.


> > Perhaps as a result, there's no recommendation on avoiding
> > synchronisation (e.g. using randomness).
> >
>There should be.
>
> > 5) I said these are the MSB's only, but allow me one nit about the Intro:
> >
> > "  there is currently no consensus solution to controlling the
> >     congestion caused by such aggressive flows; significant research and
> >     engineering will be required before any solution will be available.
> >     It is imperative that this work be energetically pursued, to ensure
> >     the future stability of the Internet.
> > "
> > The draft could at least mention congestion policing and ConEx RFCs
> > coming out of the IETF right now (e.g. RFC6789 and
> > draft-ietf-conex-abstract-mech, which is with the IESG).
> >
> >
> > I promise I'll do a proper detailed review of the new text ASAP.

Cheers


Bob

> >
> >
> > Bob
> >
> > At 13:13 15/05/2014, Wesley Eddy wrote:
> >>On 5/15/2014 5:09 AM, Bob Briscoe wrote:
> >> > Wes,
> >> >
> >> > I assume you also want comments on the new version. Is there a
> >> deadline
> >> > for comments?
> >>
> >>
> >>Absolutely, yes.  There's no "deadline" at the moment, but it would
> >>be good to get any out sooner rather than later, especially if they're
> >>likely to need more discussion or are asking for major changes.
> >>
> >>
> >> > I prepared comments on the previous version, but didn't get the time
> >> to
> >> > type them up. So I want to try to remedy this with the new version
> >> (that
> >> > I haven't read yet).
> >>
> >>
> >>The diffs aren't huge, so many of your comments on the previous
> >>revision might still be valid.
> >>
> >>
> >>--
> >>Wes Eddy
> >>MTI Systems
> >>
> >>_______________________________________________
> >>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
> >

________________________________________________________________
Bob Briscoe,                                                  BT 


From nobody Thu May 15 09:27:46 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 6CD961A02CE for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 09:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level: 
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 iQBsHdSaYTib for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 09:27:43 -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 E5C721A00DA for <aqm@ietf.org>; Thu, 15 May 2014 09:27:42 -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 3C75C2B44CB; Thu, 15 May 2014 17:27:35 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Thu, 15 May 2014 17:27:35 +0100
Message-ID: <b5bc1495b54673f9a69d0675776cfa48.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <201405151617.s4FGHs2Q028155@bagheera.jungle.bt.co.uk>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk> <5374AF87.5080607@mti-systems.com> <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk> <914ee79e5406e90207a8d78cb1196470.squirrel@www.erg.abdn.ac.uk> <201405151617.s4FGHs2Q028155@bagheera.jungle.bt.co.uk>
Date: Thu, 15 May 2014 17:27:35 +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/OsRZ5v90wAxG2k4tO1UXV6Jh5DM
Cc: gorry@erg.abdn.ac.uk, Wesley Eddy <wes@mti-systems.com>, Fred Baker <fred@cisco.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 15 May 2014 16:27:44 -0000

> Gorry,

And just on this...

>> > a) Congestion collapse: An AQM cannot prevent congestion collapse -
>> > that is the job of congestion control and, failing that, of policing.
>> > Even isolation (e.g. flow separation) doesn't prevent congestion
>> > collapse, because collapse is caused by the load from new flow
>> > arrivals exceeding the ability of the system to serve and clear load
>> > from existing flows, most likely because many existing flows are not
>> > sufficiently responsive to congestion, so retransmissions dominate
>> > over goodput (even if each unresponsive flow is in an isolated silo).
>> > Flow separation doesn't help when the problem is too many flows.
>> >
>>That would seem OK to call-out, at least to me.
>
> My concern is that it's wrong to introduce a doc with a description
> of a problem that we're not addressing in the body of the doc (even
> tho collapse is an important problem, AQM doesn't address it, so why
> is it even relevant at all?). E.g. we could also add world hunger to
> the introduction, but it wouldn't be relevant.
>

So, we will find some way on this topic - the current editors did not
start this...  the document we update uses this language and I think in
the update it needs to be confined to the early sections, possibly with
your text on why there is not mention elsewhere.

We look forward to the detailed comments.

Gorry


From nobody Thu May 15 13:25:38 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 AEDD51A0343 for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 13:25:35 -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 huXMA2q8jXFY for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 13:25:31 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8633D1A02F3 for <aqm@ietf.org>; Thu, 15 May 2014 13:25:30 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id k48so1614694wev.19 for <aqm@ietf.org>; Thu, 15 May 2014 13:25:22 -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=xTrw0tqNVvoi+QmCqbvbaD8Al1USvUmN6JZ75wgTAAY=; b=xKz/fcUWCae+WTi8vRm5rV9NEXVmVmWx2PSu5ULwh3a+bj9bM49EWT0g3ldSJUEM4G 5djZyOw/bZt82wzAgvdtVt810Sgev7PAACmPxdBt368vBMwqTf5e8+vbOF54I5rm4pGi 6Lq2vugnNVZsulhwf+0/N3sIwoMRKwg79sd95ADde3qvTY6IhZKotPmG5Hl1eTT/Vasw Mi4zevKOjERCKcLLifkXp70C4Yzc2cKMcE3o2HItpvMVoDsAMmF1x69CRyxF1UGK4O/A 0CGat47aohACPigRJR1GqBT/MDMX2WSYlhddENy9LOD1jRf2YcE41kYlwbONAWIOK7lw FnBA==
MIME-Version: 1.0
X-Received: by 10.194.250.68 with SMTP id za4mr37310wjc.89.1400185522134; Thu, 15 May 2014 13:25:22 -0700 (PDT)
Received: by 10.216.207.82 with HTTP; Thu, 15 May 2014 13:25:21 -0700 (PDT)
In-Reply-To: <201405151617.s4FGHs2Q028155@bagheera.jungle.bt.co.uk>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk> <5374AF87.5080607@mti-systems.com> <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk> <914ee79e5406e90207a8d78cb1196470.squirrel@www.erg.abdn.ac.uk> <201405151617.s4FGHs2Q028155@bagheera.jungle.bt.co.uk>
Date: Thu, 15 May 2014 13:25:21 -0700
Message-ID: <CAA93jw77Dr4=+DvTjHV_Jx6dC5Y69mU8whZy5GOkcHBWdtnsJg@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Bob Briscoe <bob.briscoe@bt.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/WlAhjkN4oKCI6Sw3w_KvkLWz62Y
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Wesley Eddy <wes@mti-systems.com>, Fred Baker <fred@cisco.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 15 May 2014 20:25:35 -0000

On Thu, May 15, 2014 at 9:17 AM, Bob Briscoe <bob.briscoe@bt.com> wrote:
> Gorry,
>
>
> At 16:55 15/05/2014, gorry@erg.abdn.ac.uk wrote:
>>
>> Great, I look forward to comments on the actual text. I agree the front
>> part needs more structure and more topics called out. i started adding
>> that in -04 and would be pleased to add a few more subsections if we get
>> agreement.
>>
>> I'll wait until I see comments before looking at updating the text with
>> Fred.
>>
>> Gorry
>>
>> > Wes,
>> >
>> > Thx. In case I don't get time to read, then type, I'll shoot my mouth
>> > off anyway...
>> >
>> > Sorry this is a bit rushed and dismissive. That's not my intention -
>> > I'm v supportive of the recommendations that have now been carefully
>> > and nicely worded. I will give more detailed comments, but these are t=
he
>> > MSBs.

I had hoped we were done.

My only major objection at this point was that I would like *all* the refer=
ences
to have hyperlinks to the referenced material. Getting them online would
be a few days work for someone willing to make a few phone calls and
interlibrary loans.


>> > 1) My main concern: The two halves of the document seemed nearly
>> > unrelated (at least in draft-03 and it looks like draft-04 hasn't
>> > changed this). The first half (Sections 1,2,&3) framed the problem as
>> > primarily about preventing congestion collapse and preventing
>> > flow-unfairness, while the recommendations (section 4) were about
>> > AQM. The irony of this sentence is deliberate.
>> >
>> > I had few concerns about the recommendations text (section 4), which
>> > we've all been focusing on, including me. But I hadn't realised the
>> > introductory text was so out of kilter with the recommendations.

Well as it built on the original document, it retains its structure
and concerns,
and is an easy read for those that had read the original.

As apparently, not enough people paid attention to it the first time around=
,
perhaps more rewriting is required. I would certainly like to expose it to
an audience of CTOs as a use test, and ask for their feedback.

>> > Sections 1,2 and 3 seemed to focus on problems that I wouldn't even
>> > address with AQM (from a quick scan it looks like these sections
>> > haven't changed in this respect for draft-04):
>> >
>> > a) Congestion collapse: An AQM cannot prevent congestion collapse -
>> > that is the job of congestion control and, failing that, of policing.

I note that I explicitly deprecated conventional policing (a fixed size
buffer on ingress) in the home-gateway draft I've been meaning to finish
and keep thinking needs to be expanded into a
"need-for-comprehensive-queue-management"
draft. All these (aqm/fq/htb/policing/qos) concepts impact each other.

running an aqm/packet scheduler/rate limiter on inbound makes more sense th=
an
buffer limits, and indeed, works better while achieving the desired result.

http://www.bufferbloat.net/projects/cerowrt/wiki/Wondershaper_Must_Die#Benc=
hmarking-Wondershaper-vs-CeroWrts-SQM

As another example, how does the competing qos vs ecn enabled schemes
for webrtc fit into our big picture?

http://tools.ietf.org/html/draft-dhesikan-tsvwg-rtcweb-qos-01

vs

https://datatracker.ietf.org/doc/draft-zhu-rmcat-nada/

>> > Even isolation (e.g. flow separation) doesn't prevent congestion
>> > collapse, because collapse is caused by the load from new flow
>> > arrivals exceeding the ability of the system to serve and clear load
>> > from existing flows, most likely because many existing flows are not
>> > sufficiently responsive to congestion, so retransmissions dominate
>> > over goodput (even if each unresponsive flow is in an isolated silo).
>> > Flow separation doesn't help when the problem is too many flows.
>> >
>> That would seem OK to call-out, at least to me.

Not sure where this goes in the text.

>
>
> My concern is that it's wrong to introduce a doc with a description of a
> problem that we're not addressing in the body of the doc (even tho collap=
se
> is an important problem, AQM doesn't address it, so why is it even releva=
nt
> at all?). E.g. we could also add world hunger to the introduction, but it
> wouldn't be relevant.

Well, a collapse concern that AQM solves is where buffering is so
extreme as to start defeating
that native retry/retransmit logic built into many protocols. Fred has
shown pictures of TCP RTOs coming from excessive buffering fooling
tcp, the early bufferbloat work was all showing tcp getting fooled on
the overlong path, and there are plenty of other examples where
excessive buffering leads to excessive retransmits, like, well, nearly
everything over a second.

>
>
>
>> > b) Flow fairness (or user-fairness etc): this is a policy issue that
>> > needs to be built in a modular way, for optional addition to AQM.

I don't really understand what you are saying here. My take on it is that
all the different components of a queueing system need to be thought
about and integrated as a whole.

http://www.bufferbloat.net/projects/cerowrt/wiki/Smart_Queue_Management

>> > Therefore an AQM must also work well without fairness mechanisms.
>> > This conclusion was actually reached in the early sections, but it's
>> > not carried forward into the recommendations in section 4.
>> >
>> > If the conclusion is that AQM isn't intended to solve these two
>> > problems, we need to clearly say so. Most people who need to read
>> > this will be confused, so we shouldn't confuse them further!
>> >
>> OK - as long as we get agreement from the various AQM proposals, some
>> methods rely heavily on flow isolation to achieve their wanted behaviour=
.

Pie and codel are very comparable. In fact, people
are pushing ARED as well, with comparable (if, IMHO, overly
simplistic) benchmarks.

Now, if you are talking about some other proposal (SQF? LRED? SFQRED?) not =
yet
discussed here?

Anyway, on the two candidates:

ecn is off by default in both codel and pie because the results of all
the methods
tried to date for doing flood protection were less than satisfactory.

Pie got some ecn overflood protection that would be easy to add to
codel, and some
would like some stronger flooding protections in codel.

ecn is on by default in fq_codel because its method of dealing with
floods is more effective
than anything we've come up with for standalone single queue aqms -
and that too could be improved, but it's not been high on my radar,
and any improvement has a cpu cost that is hard to deal with on 10gigE
hardware.

So I'd say that "some methods rely heavily on flow isolation
integrated with aqm to achieve better behaviors than aqm alone" rather
than "some methods rely heavily on flow isolation to achieve their
wanted behaviour." in this case.

I do look forward to more/better algorithms being presented here one day.


>
> Indeed, my point about fairness is different from my point about collapse
> (which just isn't even relevant). Fairness isn't strictly relevant to AQM=
,
> but flow isolation is used to complement AQMs. And flow isolation (which =
the
> doc calls 'scheduling') can't be done without affecting fairness.
>
> So 2.1 concludes:
> "  In short, scheduling algorithms and queue management should be seen
>    as complementary, not as replacements for each other.
> "
> This is a conclusion that should be reflected in the recommendations and
> conclusions. I.e. if they are complements, they need to be separable, not
> integrated.

I agree with the complement language. I don't mind if they are separable.
Integration, however, is highly advantagous.

>Because scheduling requires policy and AQM doesn't.

Machine gunning down packets randomly until the flows start to behave
does not require any policy, agreed. a 5 tuple fq system is not a lot
of policy to impose. certainly
qos and rate scheduling systems impose a lot more policy.

> So operators
> don't want to have to face the dilemma of needing the AQM part, but not
> being able to have it because they don't want the policy implicit in the
> scheduling part.
>
> This is critical for fq_codel, because apparently CoDel alone is not
> recommended (which I would agree with).

Codel is being used stand alone in BSD with pretty good results with HFSC.

btw, if anyone here can describe how hfsc works in words of less than
4 syllables,
I'd love to hear it. It's apparently used a lot in the DSL world.

> This means that we really need fq_X,
> where X is something that can be recommended either alone or with fq.

Why? An algorithm's an algorithm. All algorithms have effects. To me
we need well described algorithms that have well described effects, and
that's it.

>
>
>
>
>> >
>> > 2) There's no statement of scope.
>> > Can we really make all these recommendations irrespective of whether
>> > we're talking about high stat-mux core links, low stat-mux access
>> > links, low-stat-mux data centre links, or host buffers? Are there
>> > different recommendations for edge links (on trust boundaries) vs
>> > interior links? Does AQM apply at L2 as well as L3 (of course it
>> > does)? Which recommendations are different for each layer? Does AQM
>> > apply for middleboxes (firewalls, NATs etc) as much as for switches
>> > and routers? If not why not (only need AQM if there can be queuing -
>> > perhaps due to processor overload)?

I agree that a more comprehensive, second set of documents would be good.
My hope was that we would build upon the evaluation guidelines
documents and tests
to eventually get to where these scenarios could be benchmarked and describ=
ed,
relative to the other tests developed in the other working groups.

>> >
>> > To illustrate the problem, our goal should be AQM in every buffer.
>> > But we really don't need and shouldn't have policing or isolation in
>> > every buffer.

I could argue the opposite - that we could have scheduling in every
buffer that handles mixed flows, and drop tail or hw flow suffices to handl=
e
the rest. Take a look at the tipc work, for example.

>> >
>> Hmmm... that will be interesting - suggest a para or two please?
>
>
> I'll try - but I'm having to write an ETSI doc at the mo (which is why I'=
m
> preferring to get distracted by AQM :)

Well, I'm trying to get a final release of cero done.

>
>
>> > 4) Because sections 1,2,3 focused heavily on the above two problems
>> > (collapse and fairness) that can't really be addressed by AQM, these
>> > sections also gave insufficient attention to problems that AQM does
>> > address (and should address), E.g.:
>> >
>> > * synchronisation and lock-out were both described as vaguely the
>> > same problem,
>> > * synchronisation wasn't explained,
>>
>> yes, agree completely should be added as a subsection in section 2 - Thi=
s
>> was overlooked.

yes, some reference to tcp global sync.

>>
>> > * lock-out wasn't explained but it was said to be vaguely to do with
>> > synchronisation and solving it would help low capacity bursty flows,
>> Comment on bullet 3 in Sect 2.
>>
>> > * large-packet lock-out problems weren't mentioned, only flow-level
>> > lock-out.

While we are here, talking about the problems induced by bursty loss
might be good.

>> >
>> OK - suggest a line or two of text please:-)
>
>
> Will do.
>
>
>
>> > Perhaps as a result, there's no recommendation on avoiding
>> > synchronisation (e.g. using randomness).
>> >
>> There should be.
>>
>> > 5) I said these are the MSB's only, but allow me one nit about the
>> > Intro:
>> >
>> > "  there is currently no consensus solution to controlling the
>> >     congestion caused by such aggressive flows; significant research a=
nd
>> >     engineering will be required before any solution will be available=
.
>> >     It is imperative that this work be energetically pursued, to ensur=
e
>> >     the future stability of the Internet.
>> > "
>> > The draft could at least mention congestion policing and ConEx RFCs
>> > coming out of the IETF right now (e.g. RFC6789 and
>> > draft-ietf-conex-abstract-mech, which is with the IESG).
>> >
>> >
>> > I promise I'll do a proper detailed review of the new text ASAP.
>
>
> Cheers
>
>
> Bob
>
>
>> >
>> >
>> > Bob
>> >
>> > At 13:13 15/05/2014, Wesley Eddy wrote:
>> >>On 5/15/2014 5:09 AM, Bob Briscoe wrote:
>> >> > Wes,
>> >> >
>> >> > I assume you also want comments on the new version. Is there a
>> >> deadline
>> >> > for comments?
>> >>
>> >>
>> >>Absolutely, yes.  There's no "deadline" at the moment, but it would
>> >>be good to get any out sooner rather than later, especially if they're
>> >>likely to need more discussion or are asking for major changes.
>> >>
>> >>
>> >> > I prepared comments on the previous version, but didn't get the tim=
e
>> >> to
>> >> > type them up. So I want to try to remedy this with the new version
>> >> (that
>> >> > I haven't read yet).
>> >>
>> >>
>> >>The diffs aren't huge, so many of your comments on the previous
>> >>revision might still be valid.
>> >>
>> >>
>> >>--
>> >>Wes Eddy
>> >>MTI Systems
>> >>
>> >>_______________________________________________
>> >>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
>> >
>
>
> ________________________________________________________________
> Bob Briscoe,                                                  BT
> _______________________________________________
> 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 Thu May 15 14:19:54 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 5C3981A014B for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 14:19:52 -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 mr2iSBo3z1SY for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 14:19:51 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A744E1A00E5 for <aqm@ietf.org>; Thu, 15 May 2014 14:19:50 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id t61so1709125wes.34 for <aqm@ietf.org>; Thu, 15 May 2014 14:19:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=IdWbugpPG9INbAi0e4HlDlNA+WoADRGEDP7TOrJnfYs=; b=okxxgpTUFVvadddSNmP+H0PhArlH//5/xUQavw/6lrWo/7uNPyCxXmqvTDsRFhTTll rpyAZITHS5ArueWT05iIXeP1kG71EiAd0JJxI9yikrd9Eak9e/zHpFHE8Dd2lpey+2JC MVNm2KZXB2tWx1hL7TWZrq7Kgf8NGBxkvpUM+uuBqoQtxoQ3/YwwrVcZOFf7AvZSnaYg k9AT0B5xgCLT3cEbuO+lgVp/3MSuA9bOaWH5KDRyjFM8zu0Jssty6pgl04UhCRaf8gH5 aYKqqGfUwgS7iEWchkSP1MN7DuzWltW0dFyd2SjRulkdIRhXik/S6OMiFXxTVnBLoS9U /VLQ==
MIME-Version: 1.0
X-Received: by 10.194.220.42 with SMTP id pt10mr4476657wjc.60.1400188782403; Thu, 15 May 2014 14:19:42 -0700 (PDT)
Received: by 10.216.207.82 with HTTP; Thu, 15 May 2014 14:19:42 -0700 (PDT)
Date: Thu, 15 May 2014 14:19:42 -0700
Message-ID: <CAA93jw6BWKBSGTuO6WC0+1gU=ydE2xxwajVUDWc+WGfT4h-tEw@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: "aqm@ietf.org" <aqm@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/ENpRp7DMMeEMQmMY3A0G2l5RmtI
Subject: [aqm] backpressure and combining aqm/fq/qos techniques
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, 15 May 2014 21:19:52 -0000

going back to the integrated vs separable vs complementary debate...

in order for any queuing system to have an effect, there needs to be a
queue for it to work on. If the egress rate exceeds the ingress rate,
no queueing system is needed.

Now, in either an AQM or FQ system, they need a queue to work on. If
you hook them up serially, one or the other has no queue backpressure
to work on,
unless you batch up delivery or decide to have a standing queue between the=
m.

doing both aqm + fq at the same time works more universally with a
greater probability of shooting at AND scheduling the right stuff,
starting with a queue length of 3.

If you settle on having a standing queue between the two (say for example,
10 packets) you are in a losing situation vs a vs latency in the first plac=
e.

The situation is mildly better on batching packet delivery (take
wireless-n or cable as an example) - there you could schedule the
flows to end-points, aqm/fq+aqm the flows, and furthermore treat the
bundles sanely at the hardware aggregate level as to what packets you
are willing to drop rather than retransmit.

At least in the case of wifi, the variable rate packet scheduler ->
aqm/fq -> qos -> txop batching -> packet drop in the air/retransmits
process needs to be a lot more complex to work well, and doesn't fit
into the line rate ethernet debate well at all, and there hasn't yet
been enough work done on it to get anywhere although I hold out great
hope for latency aware aqms to get wireless far more right.

All modern linux ethernet systems are doing some form of batching in
order to run at 10gig speeds - but JUST enough to keep the hardware
busy - that was the miracle of BQL - but most dma hardware is not
presently smart enough to do anything other than a tx ring for
handling packets on those batches.

--=20
Dave T=C3=A4ht


From nobody Thu May 15 15:42:28 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 AEC691A0195 for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 15:42:25 -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 0VQGLR3Pumb9 for <aqm@ietfa.amsl.com>; Thu, 15 May 2014 15:42:18 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C30A31A019C for <aqm@ietf.org>; Thu, 15 May 2014 15:42:09 -0700 (PDT)
Received: by mail-qg0-f43.google.com with SMTP id 63so2907111qgz.16 for <aqm@ietf.org>; Thu, 15 May 2014 15:42:02 -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=kEsKRYswb+dPI/RaOy5p04x50m+MB6UzPakLw/hGv7s=; b=s56yYEBxITpH+FQpMN/X2IHPmNMdhGNOiclurvxvQRW59fsXXV1AJgVO3HodR8P24W 6HR+/BELAY+ccNhcx3GaLyEuIv/yAJsVkWfOcr4Q4ACKA8H8Vl8z3iGsQ8JZ+AGQPYaY VplZ6/1IAlCYe7a4xVpZdV/sJr/bHAd+Cu81Ttv2nUpFa2JByBwMCg3q0leZRR+RwoXS lQEcK2rCJKQCd3byBin7HW/rHeoC1KLxR+mpJOVmozb37TNuR9IiEsrCpM56M84NIOy6 WynVW0dO2i/38NqH46N8pghYapie5spMK9Lz4s4HmcMYIzn7UILN+I630WO5uPjlFRlZ qJQA==
MIME-Version: 1.0
X-Received: by 10.140.27.245 with SMTP id 108mr18684482qgx.18.1400193722193; Thu, 15 May 2014 15:42:02 -0700 (PDT)
Received: by 10.140.37.133 with HTTP; Thu, 15 May 2014 15:42:02 -0700 (PDT)
In-Reply-To: <CAA93jw77Dr4=+DvTjHV_Jx6dC5Y69mU8whZy5GOkcHBWdtnsJg@mail.gmail.com>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk> <5374AF87.5080607@mti-systems.com> <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk> <914ee79e5406e90207a8d78cb1196470.squirrel@www.erg.abdn.ac.uk> <201405151617.s4FGHs2Q028155@bagheera.jungle.bt.co.uk> <CAA93jw77Dr4=+DvTjHV_Jx6dC5Y69mU8whZy5GOkcHBWdtnsJg@mail.gmail.com>
Date: Thu, 15 May 2014 15:42:02 -0700
Message-ID: <CAA93jw4n6YmfpmNgR7asxqGYoZOH7+=k2mZ+y3Y=6DYz1jLzqg@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Bob Briscoe <bob.briscoe@bt.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/tcFpnfGAz19EGSwMvXo53TjU2Yw
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Wesley Eddy <wes@mti-systems.com>, Fred Baker <fred@cisco.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 15 May 2014 22:42:25 -0000

>
> I agree with the complement language. I don't mind if they are separable.
> Integration, however, is highly advantagous.

I started another thread on the backlog issue.

>
>>Because scheduling requires policy and AQM doesn't.
>
> Machine gunning down packets randomly until the flows start to behave
> does not require any policy, agreed. a 5 tuple fq system is not a lot
> of policy to impose. certainly
> qos and rate scheduling systems impose a lot more policy.

Actually, I'm going to retract part of what I just said. Everything is a policy.

Drop tail is a policy, it's useful for e2e mechanisms like ledbat if
the queue size
is greater than 100ms. not helpful for bufferbloat.

Drop head is a policy, it's useful for voip (actually useful for tcp
too). Not helpful for ledbat.

Shooting randomly and increasingly until flows get under control, a
decent compromise
between drop head and drop tail, that also shoots at a lot of packets
it doesn't need to

drr is a policy that does better mixing and does byte fairness
sfq is a polic does better mixing of packet fairness
qfq does weighted fq

red/ared/wred is a policy.
hfsc is a policy that does interesting scheduling and drop things all its own
htb based policies are often complex and interesting

so the problem is in defining what policies are needed and what algorithms
can be used to implement that policy. May the ones that provide the best
QoE for the end user succeed in the marketplace, and networks get ever better.

https://www0.comp.nus.edu/~bleong/publications/pam14-ispcheck.pdf

>> So operators
>> don't want to have to face the dilemma of needing the AQM part, but not
>> being able to have it because they don't want the policy implicit in the
>> scheduling part.

A dilemma of choosing which single line of code to incorporate in an
otherwise far more complex system? I certainly do wish it was entirely
parameterless, and perhaps a future version could be more so than
this is today.

I can write up the complexity required to do for example qfq + pie but
it would be a great deal longer than the below, and qfq + RED or red alone,
is much longer than either. Scripting is needed to configure those...

# to do both AQM + DRR at the same time, with reasonable defaults for
4mbit-10gbit

tc qdisc add dev your_device root fq_codel

# AQM only
# ecn not presently recomended

tc qdisc add dev your_device root codel

# or (functional equivalent)

tc qdisc add dev your_device root fq_codel flows 1 noecn

# (you could also replace the default tc filter, to get, like,
# a 4 queued system on dscp...)

# DRR + SQF-like behavior with minimal AQM, probably mostly reverting
# to drop head from largest queue (with the largest delay I consider
# even slightly reasonable)

tc qdisc add dev your_device root fq_codel target 250ms interval 2500ms

# if your desire is to completely rip out the codel portion of fq_codel that's
# doable. I know a fq_pie exists, too.

# reasonable default for satellite systems (might need to be closer to 120ms,
# and given the speed of most satellites, quantum 300 makes sense as well as
# a reduced mtu and IW)

tc qdisc add dev your_device root fq_codel target 60ms interval 1200ms

# useful option for lower bandwidth systems is quantum 300

# Data center only use can run at reduced target and interval

tc qdisc add dev your_device root fq_codel target 500us interval 10ms

# above 10Gbit, increasing the packet limit is good, probably a good
idea to increase flows

# a current problematic interaction with htb below 2.5mb leads to a
need for a larger target
# (it would be better to fix htb or to write a better rate limiter)

It's about a page of directions to handle every use case. I'd LOVE to
have similar
guideline and cookbook page(s) for EVERY well known aqm and packet
scheduling system - notably red and ared. I lack data on pie's
scalability presently, too.

Most rate shaping code on top of this sort of stuff, and most
shaping/qos related code also
is orders of magnitude more complex than this. Take htb's compensator
for ATM and/or PPPoe framing. Please. OR the hideous QoS schemes
people have designed using DPI.

As things stand fq_codel is a simpler/faster/better
drop in replacement for tons of code that shaped and used RED, or shaped and
did sfq.

Sensing the line rate, choosing an appropriate packet limit based on
available memory,
and auto-choosing number of flows are things the C code could be
smarter about.

They are something I currently do in a shell script (that also tries to figure
out atm framing and a 3 tier qos system)

I think that adding a rate limiter directly to a fq_codel or wfq +
codel derived algo
is a great idea and would be better than htb or hfsc + X. Been meaning to polish
up the code...


>>
>> This is critical for fq_codel, because apparently CoDel alone is not
>> recommended (which I would agree with).

The present version of that is useful (without ecn) in many scenarios.
It has been used
in combination with hfsc, htb, and standalone.

We've long had a version that outcompetes pie in more scenarios in
both ns2 and cerowrt for 2 years now... but falls off a little more at
longer RTTs than we'd like. And pie, in it's current
form and defaults in the linux kernel performs nowhere near as well as
it did in the paper or
vs codel or ns2_codel.

fq_codel is merely better in every respect we care about - better
utilization & lower latency across a wide range of benchmarks on real
traffic. We have some voip related benchmarks
coming up soon....

I certainly agree that the data center case needs something faster
than "codel by default".
I have had pretty good results with target 500us interval 10ms in that
case, and I
am seriously encouraged by the new e2e approaches of sch_fq + pacing,
and for that
matter DCTCP (if only someone else would port it to a modern kernel) -

So maybe, if we clearly separate out use cases - move the data center
discussion over
to the newly formed dclc group, for example? we can get moving on
fixing the edge
of the internet more?


From nobody Fri May 16 00:59:08 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 395D21A016F for <aqm@ietfa.amsl.com>; Fri, 16 May 2014 00:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.252
X-Spam-Level: 
X-Spam-Status: No, score=-3.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, 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 G2Paihmsl0Io for <aqm@ietfa.amsl.com>; Fri, 16 May 2014 00:59:04 -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 CEB6C1A00C9 for <aqm@ietf.org>; Fri, 16 May 2014 00:59:03 -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.327.1; Fri, 16 May 2014 08:58:50 +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.279.1; Fri, 16 May 2014 08:58:53 +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; Fri, 16 May 2014 08:58:50 +0100
Received: from BTP075694.jungle.bt.co.uk ([10.111.16.164])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id s4G7wmmI031034;	Fri, 16 May 2014 08:58:48 +0100
Message-ID: <201405160758.s4G7wmmI031034@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 16 May 2014 08:58:48 +0100
To: <gorry@erg.abdn.ac.uk>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <b5bc1495b54673f9a69d0675776cfa48.squirrel@www.erg.abdn.ac. uk>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk> <5374AF87.5080607@mti-systems.com> <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk> <914ee79e5406e90207a8d78cb1196470.squirrel@www.erg.abdn.ac.uk> <201405151617.s4FGHs2Q028155@bagheera.jungle.bt.co.uk> <b5bc1495b54673f9a69d0675776cfa48.squirrel@www.erg.abdn.ac.uk>
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/nlJhL0c1Ddwc1-UynBeqOIsggqk
Cc: gorry@erg.abdn.ac.uk, Wesley Eddy <wes@mti-systems.com>, Fred Baker <fred@cisco.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 16 May 2014 07:59:06 -0000

Gorry,

I'm concerned that you've asked me to supply text to /add/ to the 
early sections, when they actually need a lot /subtracted/. They need 
to be written knowing where they want to go to, and just say enough 
to get there. Effectively a re-write.

A lot of people are confused about what AQM can and should do, so 
this doc should have an important role in deconfusing.

However, I don't have the b/w to volunteer to do this re-write.

Bob

At 17:27 15/05/2014, gorry@erg.abdn.ac.uk wrote:
> > Gorry,
>
>And just on this...
>
> >> > a) Congestion collapse: An AQM cannot prevent congestion collapse -
> >> > that is the job of congestion control and, failing that, of policing.
> >> > Even isolation (e.g. flow separation) doesn't prevent congestion
> >> > collapse, because collapse is caused by the load from new flow
> >> > arrivals exceeding the ability of the system to serve and clear load
> >> > from existing flows, most likely because many existing flows are not
> >> > sufficiently responsive to congestion, so retransmissions dominate
> >> > over goodput (even if each unresponsive flow is in an isolated silo).
> >> > Flow separation doesn't help when the problem is too many flows.
> >> >
> >>That would seem OK to call-out, at least to me.
> >
> > My concern is that it's wrong to introduce a doc with a description
> > of a problem that we're not addressing in the body of the doc (even
> > tho collapse is an important problem, AQM doesn't address it, so why
> > is it even relevant at all?). E.g. we could also add world hunger to
> > the introduction, but it wouldn't be relevant.
> >
>
>So, we will find some way on this topic - the current editors did not
>start this...  the document we update uses this language and I think in
>the update it needs to be confined to the early sections, possibly with
>your text on why there is not mention elsewhere.
>
>We look forward to the detailed comments.
>
>Gorry

________________________________________________________________
Bob Briscoe,                                                  BT 


From nobody Fri May 16 01:23:52 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 D7DD81A0133 for <aqm@ietfa.amsl.com>; Fri, 16 May 2014 01:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level: 
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 ST1KmJ163_hN for <aqm@ietfa.amsl.com>; Fri, 16 May 2014 01:23:48 -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 A21C61A01B6 for <aqm@ietf.org>; Fri, 16 May 2014 01:23:47 -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 76C1B2B43B3; Fri, 16 May 2014 09:23:39 +0100 (BST)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Fri, 16 May 2014 09:23:39 +0100
Message-ID: <e2dbff207973e02faf03e80feaba322c.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <201405160758.s4G7wmmI031034@bagheera.jungle.bt.co.uk>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk> <5374AF87.5080607@mti-systems.com> <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk> <914ee79e5406e90207a8d78cb1196470.squirrel@www.erg.abdn.ac.uk> <201405151617.s4FGHs2Q028155@bagheera.jungle.bt.co.uk> <b5bc1495b54673f9a69d0675776cfa48.squirrel@www.erg.abdn.ac.uk> <201405160758.s4G7wmmI031034@bagheera.jungle.bt.co.uk>
Date: Fri, 16 May 2014 09:23:39 +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/y-7Awgv9ciATjeagWVc24WYYT1o
Cc: gorry@erg.abdn.ac.uk, Wesley Eddy <wes@mti-systems.com>, Fred Baker <fred@cisco.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 16 May 2014 08:23:51 -0000

I agree the focus has been on updating the recommendations section.

I quite understand that you have other things to do, so I'll try and
summarise comments on the earlier sections and see if you agree. When we
have a list we (with AQM chairs) can then decide what to do (work out how
long it will take to complete the job).

If other people *DO* have comments against specific parts of the current
text, please do tell the list.

Gorry

> Gorry,
>
> I'm concerned that you've asked me to supply text to /add/ to the
> early sections, when they actually need a lot /subtracted/. They need
> to be written knowing where they want to go to, and just say enough
> to get there. Effectively a re-write.
>
> A lot of people are confused about what AQM can and should do, so
> this doc should have an important role in deconfusing.
>
> However, I don't have the b/w to volunteer to do this re-write.
>
> Bob
>
> At 17:27 15/05/2014, gorry@erg.abdn.ac.uk wrote:
>> > Gorry,
>>
>>And just on this...
>>
>> >> > a) Congestion collapse: An AQM cannot prevent congestion collapse -
>> >> > that is the job of congestion control and, failing that, of
>> policing.
>> >> > Even isolation (e.g. flow separation) doesn't prevent congestion
>> >> > collapse, because collapse is caused by the load from new flow
>> >> > arrivals exceeding the ability of the system to serve and clear
>> load
>> >> > from existing flows, most likely because many existing flows are
>> not
>> >> > sufficiently responsive to congestion, so retransmissions dominate
>> >> > over goodput (even if each unresponsive flow is in an isolated
>> silo).
>> >> > Flow separation doesn't help when the problem is too many flows.
>> >> >
>> >>That would seem OK to call-out, at least to me.
>> >
>> > My concern is that it's wrong to introduce a doc with a description
>> > of a problem that we're not addressing in the body of the doc (even
>> > tho collapse is an important problem, AQM doesn't address it, so why
>> > is it even relevant at all?). E.g. we could also add world hunger to
>> > the introduction, but it wouldn't be relevant.
>> >
>>
>>So, we will find some way on this topic - the current editors did not
>>start this...  the document we update uses this language and I think in
>>the update it needs to be confined to the early sections, possibly with
>>your text on why there is not mention elsewhere.
>>
>>We look forward to the detailed comments.
>>
>>Gorry
>
> ________________________________________________________________
> Bob Briscoe,                                                  BT
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>



From nobody Fri May 16 02:17:52 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 58C3B1A01C6 for <aqm@ietfa.amsl.com>; Fri, 16 May 2014 02:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.252
X-Spam-Level: 
X-Spam-Status: No, score=-3.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651, 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 lTajsE1CBb58 for <aqm@ietfa.amsl.com>; Fri, 16 May 2014 02:17:46 -0700 (PDT)
Received: from hubrelay-rd.bt.com (hubrelay-rd.bt.com [62.239.224.99]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D0131A01C5 for <aqm@ietf.org>; Fri, 16 May 2014 02:17:46 -0700 (PDT)
Received: from EVMHR72-UKRD.domain1.systemhost.net (10.36.3.110) by EVMHR67-UKRD.bt.com (10.187.101.22) with Microsoft SMTP Server (TLS) id 8.3.297.1; Fri, 16 May 2014 10:17:36 +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.279.1; Fri, 16 May 2014 10:17:36 +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; Fri, 16 May 2014 10:17:34 +0100
Received: from BTP075694.jungle.bt.co.uk ([10.111.16.164])	by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id s4G9HVmc031282;	Fri, 16 May 2014 10:17:32 +0100
Message-ID: <201405160917.s4G9HVmc031282@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 16 May 2014 10:17:31 +0100
To: Dave Taht <dave.taht@gmail.com>
From: Bob Briscoe <bob.briscoe@bt.com>
In-Reply-To: <CAA93jw77Dr4=+DvTjHV_Jx6dC5Y69mU8whZy5GOkcHBWdtnsJg@mail.g mail.com>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk> <5374AF87.5080607@mti-systems.com> <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk> <914ee79e5406e90207a8d78cb1196470.squirrel@www.erg.abdn.ac.uk> <201405151617.s4FGHs2Q028155@bagheera.jungle.bt.co.uk> <CAA93jw77Dr4=+DvTjHV_Jx6dC5Y69mU8whZy5GOkcHBWdtnsJg@mail.gmail.com>
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/oYnqq-n3qGFvNot0P__0TSFIiqY
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Wesley Eddy <wes@mti-systems.com>, Fred Baker <fred@cisco.com>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 16 May 2014 09:17:51 -0000

Dave,

At 21:25 15/05/2014, Dave Taht wrote:
>On Thu, May 15, 2014 at 9:17 AM, Bob Briscoe <bob.briscoe@bt.com> wrote:
> > Gorry,
> >
> >
> > At 16:55 15/05/2014, gorry@erg.abdn.ac.uk wrote:
> >>
> >> Great, I look forward to comments on the actual text. I agree the front
> >> part needs more structure and more topics called out. i started adding
> >> that in -04 and would be pleased to add a few more subsections if we=
 get
> >> agreement.
> >>
> >> I'll wait until I see comments before looking at updating the text with
> >> Fred.
> >>
> >> Gorry
> >>
> >> > Wes,
> >> >
> >> > Thx. In case I don't get time to read, then type, I'll shoot my mouth
> >> > off anyway...
> >> >
> >> > Sorry this is a bit rushed and dismissive. That's not my intention -
> >> > I'm v supportive of the recommendations that have now been carefully
> >> > and nicely worded. I will give more detailed comments, but these are=
 the
> >> > MSBs.
>
>I had hoped we were done.
>
>My only major objection at this point was that I=20
>would like *all* the references
>to have hyperlinks to the referenced material. Getting them online would
>be a few days work for someone willing to make a few phone calls and
>interlibrary loans.
>
>
> >> > 1) My main concern: The two halves of the document seemed nearly
> >> > unrelated (at least in draft-03 and it looks like draft-04 hasn't
> >> > changed this). The first half (Sections 1,2,&3) framed the problem as
> >> > primarily about preventing congestion collapse and preventing
> >> > flow-unfairness, while the recommendations (section 4) were about
> >> > AQM. The irony of this sentence is deliberate.
> >> >
> >> > I had few concerns about the recommendations text (section 4), which
> >> > we've all been focusing on, including me. But I hadn't realised the
> >> > introductory text was so out of kilter with the recommendations.
>
>Well as it built on the original document, it retains its structure
>and concerns,
>and is an easy read for those that had read the original.
>
>As apparently, not enough people paid attention to it the first time=
 around,
>perhaps more rewriting is required. I would certainly like to expose it to
>an audience of CTOs as a use test, and ask for their feedback.
>
> >> > Sections 1,2 and 3 seemed to focus on problems that I wouldn't even
> >> > address with AQM (from a quick scan it looks like these sections
> >> > haven't changed in this respect for draft-04):
> >> >
> >> > a) Congestion collapse: An AQM cannot prevent congestion collapse -
> >> > that is the job of congestion control and, failing that, of policing.
>
>I note that I explicitly deprecated conventional policing (a fixed size
>buffer on ingress) in the home-gateway draft I've been meaning to finish
>and keep thinking needs to be expanded into a
>"need-for-comprehensive-queue-management"
>draft. All these (aqm/fq/htb/policing/qos) concepts impact each other.
>
>running an aqm/packet scheduler/rate limiter on inbound makes more sense=
 than
>buffer limits, and indeed, works better while achieving the desired result.
>
>http://www.bufferbloat.net/projects/cerowrt/wiki/Wondershaper_Must_Die#Benc=
hmarking-Wondershaper-vs-CeroWrts-SQM
>
>As another example, how does the competing qos vs ecn enabled schemes
>for webrtc fit into our big picture?
>
>http://tools.ietf.org/html/draft-dhesikan-tsvwg-rtcweb-qos-01
>
>vs
>
>https://datatracker.ietf.org/doc/draft-zhu-rmcat-nada/

This is getting way-off the original point, which=20
was that collapse is not addressable by AQM, only=20
by congestion control and, failing that, policing.

Congestion collapse is a specific well-defined=20
condition. Let's not get side-tracked into=20
references about it, how to solve it, etc.=20
Because it's just not solvable using AQM or=20
flow-separation. It's irrelevant to this WG's=20
charter (not mentioned in the charter, and we=20
were right not to have mentioned it). Let's take=20
all the stuff about collapse out. Full stop.


> >> > Even isolation (e.g. flow separation) doesn't prevent congestion
> >> > collapse, because collapse is caused by the load from new flow
> >> > arrivals exceeding the ability of the system to serve and clear load
> >> > from existing flows, most likely because many existing flows are not
> >> > sufficiently responsive to congestion, so retransmissions dominate
> >> > over goodput (even if each unresponsive flow is in an isolated silo).
> >> > Flow separation doesn't help when the problem is too many flows.
> >> >
> >> That would seem OK to call-out, at least to me.
>
>Not sure where this goes in the text.
>
> >
> >
> > My concern is that it's wrong to introduce a doc with a description of a
> > problem that we're not addressing in the body of the doc (even tho=
 collapse
> > is an important problem, AQM doesn't address it, so why is it even=
 relevant
> > at all?). E.g. we could also add world hunger to the introduction, but=
 it
> > wouldn't be relevant.
>
>Well, a collapse concern that AQM solves is where buffering is so
>extreme as to start defeating
>that native retry/retransmit logic built into many protocols. Fred has
>shown pictures of TCP RTOs coming from excessive buffering fooling
>tcp, the early bufferbloat work was all showing tcp getting fooled on
>the overlong path, and there are plenty of other examples where
>excessive buffering leads to excessive retransmits, like, well, nearly
>everything over a second.

This is certainly a pathology that AQM solves but=20
sensible buffere sizing solves this too. Packets=20
aren't actually getting lost so they do leave the=20
buffer eventually and the flows will depart from=20
the system. TCP is retransmitting because it=20
thinks packets have probably got lost. So more=20
traffic is sent than needs to be sent. I'm not=20
convinced this will lead to the same conditions=20
as a congestion collapse, but it might... This=20
condition inflates the load on the network by a=20
proportion that depends on the flow lengths.

It's certainly not helpful to use the term=20
congestion collapse in this draft if this is what=20
we want to mean, 'cos the cause of collapse has=20
always been described as poor end-system=20
response, not stupidly bloated buffers that drive=20
the end-system response outside its normal range.

So again, I repeat that assigning a large part of=20
the introduction to talk about congestion collapse is not helpful.


> >
> >
> >
> >> > b) Flow fairness (or user-fairness etc): this is a policy issue that
> >> > needs to be built in a modular way, for optional addition to AQM.
>
>I don't really understand what you are saying here. My take on it is that
>all the different components of a queueing system need to be thought
>about and integrated as a whole.
>
>http://www.bufferbloat.net/projects/cerowrt/wiki/Smart_Queue_Management

This is an important difference in goals then. I=20
fundamentally disagree. I start from the end-to-end principle:
* queue management in /every/ buffer does the=20
minimum necessary to keep each queue short under /normal/ conditions.
* then per-user policing in /one/ edge buffer=20
protects users from each other where they share=20
the access into the network. The operator chooses the specifics (=3D policy)
* then intra-user, their applications and=20
transports aim to schedule traffic to best use=20
available bottleneck access capacity (application choices =3D app policy).
* then, the user /chooses/ a home gateway that=20
might contain scheduling to protect their=20
applications from each other, but might not (=3D policy).

Attempting to provide a completely integrated=20
solution implies the designer is closing off any=20
choice (policy) at these different decision stages.


> >> > Therefore an AQM must also work well without fairness mechanisms.
> >> > This conclusion was actually reached in the early sections, but it's
> >> > not carried forward into the recommendations in section 4.
> >> >
> >> > If the conclusion is that AQM isn't intended to solve these two
> >> > problems, we need to clearly say so. Most people who need to read
> >> > this will be confused, so we shouldn't confuse them further!
> >> >
> >> OK - as long as we get agreement from the various AQM proposals, some
> >> methods rely heavily on flow isolation to achieve their wanted=
 behaviour.
>
>Pie and codel are very comparable. In fact, people
>are pushing ARED as well, with comparable (if, IMHO, overly
>simplistic) benchmarks.
>
>Now, if you are talking about some other proposal (SQF? LRED? SFQRED?) not=
 yet
>discussed here?

I'm talking about PIE & CoDel here. I think you=20
(and others) do not recommend CoDel unless it is=20
integrated with FQ (=3Dflow queueing). Whereas PIE=20
is intended to work without any scheduling, but=20
FQ (=3D'fair' queueing) can be added if the vendor=20
/chooses/ then the user can /choose/ which=20
vendors don't make the wrong judgements about=20
their applications. This last choice still isn't=20
ideal, because users can't choose vendors that=20
don't screw with /future/ apps that will never be=20
deployed because of choices made earlier and embedded in network devices.

I'll come back to the rest later if time permits.=20
I've got to catch a train - got to take a load of=20
WW2 memorabilia to a film company - but that's another story!

I've tried to respond to your follow-up email on=20
policy, with my earlier comments in this email.


Bob


>Anyway, on the two candidates:
>
>ecn is off by default in both codel and pie because the results of all
>the methods
>tried to date for doing flood protection were less than satisfactory.
>
>Pie got some ecn overflood protection that would be easy to add to
>codel, and some
>would like some stronger flooding protections in codel.
>
>ecn is on by default in fq_codel because its method of dealing with
>floods is more effective
>than anything we've come up with for standalone single queue aqms -
>and that too could be improved, but it's not been high on my radar,
>and any improvement has a cpu cost that is hard to deal with on 10gigE
>hardware.
>
>So I'd say that "some methods rely heavily on flow isolation
>integrated with aqm to achieve better behaviors than aqm alone" rather
>than "some methods rely heavily on flow isolation to achieve their
>wanted behaviour." in this case.
>
>I do look forward to more/better algorithms being presented here one day.
>
>
> >
> > Indeed, my point about fairness is different from my point about=
 collapse
> > (which just isn't even relevant). Fairness isn't strictly relevant to=
 AQM,
> > but flow isolation is used to complement=20
> AQMs. And flow isolation (which the
> > doc calls 'scheduling') can't be done without affecting fairness.
> >
> > So 2.1 concludes:
> > "  In short, scheduling algorithms and queue management should be seen
> >    as complementary, not as replacements for each other.
> > "
> > This is a conclusion that should be reflected in the recommendations and
> > conclusions. I.e. if they are complements, they need to be separable,=
 not
> > integrated.
>
>I agree with the complement language. I don't mind if they are separable.
>Integration, however, is highly advantagous.
>
> >Because scheduling requires policy and AQM doesn't.
>
>Machine gunning down packets randomly until the flows start to behave
>does not require any policy, agreed. a 5 tuple fq system is not a lot
>of policy to impose. certainly
>qos and rate scheduling systems impose a lot more policy.
>
> > So operators
> > don't want to have to face the dilemma of needing the AQM part, but not
> > being able to have it because they don't want the policy implicit in the
> > scheduling part.
> >
> > This is critical for fq_codel, because apparently CoDel alone is not
> > recommended (which I would agree with).
>
>Codel is being used stand alone in BSD with pretty good results with HFSC.
>
>btw, if anyone here can describe how hfsc works in words of less than
>4 syllables,
>I'd love to hear it. It's apparently used a lot in the DSL world.
>
> > This means that we really need fq_X,
> > where X is something that can be recommended either alone or with fq.
>
>Why? An algorithm's an algorithm. All algorithms have effects. To me
>we need well described algorithms that have well described effects, and
>that's it.
>
> >
> >
> >
> >
> >> >
> >> > 2) There's no statement of scope.
> >> > Can we really make all these recommendations irrespective of whether
> >> > we're talking about high stat-mux core links, low stat-mux access
> >> > links, low-stat-mux data centre links, or host buffers? Are there
> >> > different recommendations for edge links (on trust boundaries) vs
> >> > interior links? Does AQM apply at L2 as well as L3 (of course it
> >> > does)? Which recommendations are different for each layer? Does AQM
> >> > apply for middleboxes (firewalls, NATs etc) as much as for switches
> >> > and routers? If not why not (only need AQM if there can be queuing -
> >> > perhaps due to processor overload)?
>
>I agree that a more comprehensive, second set of documents would be good.
>My hope was that we would build upon the evaluation guidelines
>documents and tests
>to eventually get to where these scenarios could be benchmarked and=
 described,
>relative to the other tests developed in the other working groups.
>
> >> >
> >> > To illustrate the problem, our goal should be AQM in every buffer.
> >> > But we really don't need and shouldn't have policing or isolation in
> >> > every buffer.
>
>I could argue the opposite - that we could have scheduling in every
>buffer that handles mixed flows, and drop tail or hw flow suffices to=
 handle
>the rest. Take a look at the tipc work, for example.
>
> >> >
> >> Hmmm... that will be interesting - suggest a para or two please?
> >
> >
> > I'll try - but I'm having to write an ETSI doc at the mo (which is why=
 I'm
> > preferring to get distracted by AQM :)
>
>Well, I'm trying to get a final release of cero done.
>
> >
> >
> >> > 4) Because sections 1,2,3 focused heavily on the above two problems
> >> > (collapse and fairness) that can't really be addressed by AQM, these
> >> > sections also gave insufficient attention to problems that AQM does
> >> > address (and should address), E.g.:
> >> >
> >> > * synchronisation and lock-out were both described as vaguely the
> >> > same problem,
> >> > * synchronisation wasn't explained,
> >>
> >> yes, agree completely should be added as a subsection in section 2 -=
 This
> >> was overlooked.
>
>yes, some reference to tcp global sync.
>
> >>
> >> > * lock-out wasn't explained but it was said to be vaguely to do with
> >> > synchronisation and solving it would help low capacity bursty flows,
> >> Comment on bullet 3 in Sect 2.
> >>
> >> > * large-packet lock-out problems weren't mentioned, only flow-level
> >> > lock-out.
>
>While we are here, talking about the problems induced by bursty loss
>might be good.
>
> >> >
> >> OK - suggest a line or two of text please:-)
> >
> >
> > Will do.
> >
> >
> >
> >> > Perhaps as a result, there's no recommendation on avoiding
> >> > synchronisation (e.g. using randomness).
> >> >
> >> There should be.
> >>
> >> > 5) I said these are the MSB's only, but allow me one nit about the
> >> > Intro:
> >> >
> >> > "  there is currently no consensus solution to controlling the
> >> >     congestion caused by such aggressive flows; significant research=
 and
> >> >     engineering will be required before any solution will be=
 available.
> >> >     It is imperative that this work be energetically pursued, to=
 ensure
> >> >     the future stability of the Internet.
> >> > "
> >> > The draft could at least mention congestion policing and ConEx RFCs
> >> > coming out of the IETF right now (e.g. RFC6789 and
> >> > draft-ietf-conex-abstract-mech, which is with the IESG).
> >> >
> >> >
> >> > I promise I'll do a proper detailed review of the new text ASAP.
> >
> >
> > Cheers
> >
> >
> > Bob
> >
> >
> >> >
> >> >
> >> > Bob
> >> >
> >> > At 13:13 15/05/2014, Wesley Eddy wrote:
> >> >>On 5/15/2014 5:09 AM, Bob Briscoe wrote:
> >> >> > Wes,
> >> >> >
> >> >> > I assume you also want comments on the new version. Is there a
> >> >> deadline
> >> >> > for comments?
> >> >>
> >> >>
> >> >>Absolutely, yes.  There's no "deadline" at the moment, but it would
> >> >>be good to get any out sooner rather than later, especially if=
 they're
> >> >>likely to need more discussion or are asking for major changes.
> >> >>
> >> >>
> >> >> > I prepared comments on the previous version, but didn't get the=
 time
> >> >> to
> >> >> > type them up. So I want to try to remedy this with the new version
> >> >> (that
> >> >> > I haven't read yet).
> >> >>
> >> >>
> >> >>The diffs aren't huge, so many of your comments on the previous
> >> >>revision might still be valid.
> >> >>
> >> >>
> >> >>--
> >> >>Wes Eddy
> >> >>MTI Systems
> >> >>
> >> >>_______________________________________________
> >> >>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
> >> >
> >
> >
> > ________________________________________________________________
> > Bob Briscoe,                                                  BT
> > _______________________________________________
> > aqm mailing list
> > aqm@ietf.org
> > https://www.ietf.org/mailman/listinfo/aqm
>
>
>
>--
>Dave T=C3=A4ht
>
>NSFW:=20
>https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indece=
nt.article
>
>_______________________________________________
>aqm mailing list
>aqm@ietf.org
>https://www.ietf.org/mailman/listinfo/aqm

________________________________________________________________
Bob Briscoe,                                                  BT=20


From nobody Fri May 16 04:02:20 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 ADD5C1A021A for <aqm@ietfa.amsl.com>; Fri, 16 May 2014 04:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R5xAuQaW0Iaq for <aqm@ietfa.amsl.com>; Fri, 16 May 2014 04:02:16 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A1FA1A0219 for <aqm@ietf.org>; Fri, 16 May 2014 04:02:15 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s4GB23sc006080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 16 May 2014 06:02:04 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s4GB22oG019666 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 16 May 2014 13:02:03 +0200
Received: from FR712WXCHMBA13.zeu.alcatel-lucent.com ([169.254.5.3]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Fri, 16 May 2014 13:02:03 +0200
From: "LAUTENSCHLAEGER, Wolfram (Wolfram)" <wolfram.lautenschlaeger@alcatel-lucent.com>
To: "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] last call results on draft-ietf-aqm-recommendation
Thread-Index: AQHPaArZtcFTfmjscESsNxa0jwrG8JtAxW8AgACD04CAADNugIAAJpcAgAFVcdA=
Date: Fri, 16 May 2014 11:02:01 +0000
Message-ID: <0A452E1DADEF254C9A7AC1969B87812806A3BB@FR712WXCHMBA13.zeu.alcatel-lucent.com>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk> <5374AF87.5080607@mti-systems.com> <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk>
In-Reply-To: <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.39]
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/cCCEcXn4AFoJEiSGr1f9o4Z_kxg
Cc: Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 16 May 2014 11:02:18 -0000

I strongly agree with Bob's concerns:

- Congestion collapse cannot be prevented by AQM
- Flow fairness is not a topic for AQM
- AQM should be possible without any knowledge of particular flows.=20
As such it is clearly a L2 mechanism (which does not mean that it
cannot be applied in L3 boxes).

Of course, in technical implementations an AQM could be combined
with fairness mechanisms like the fq_X proposals do. (I assume that
in such combination AQM and scheduling essentially operate on the=20
same queue or group of queues.) But for a clear understanding,=20
what a particular AQM does, I would prefer to see the AQM=20
algorithm in isolation.

AQM should be applied to every buffer that can be overloaded and=20
TCP is involved, i.e. where ingress rate can be higher the egress rate=20
and no backpressure is in place. In middleboxes with ingress =3D=3D egress
rates this is not the case, except the processing capacity is insufficient.

In my opinion AQM applies to multiplexed links, where several flows
share the same transmission capacity. AQM cannot do a lot for a=20
single flow on one link. In the capacity sharing case the effects of
synchronization and burstiness of drops are strongly tied together.
Removing the one also removes the other and this is the most what=20
AQM can afford.

Wolfram


> -----Urspr=FCngliche Nachricht-----
> Von: aqm [mailto:aqm-bounces@ietf.org] Im Auftrag von Bob Briscoe
> Gesendet: Donnerstag, 15. Mai 2014 16:32
> An: Wesley Eddy; Fred Baker; Gorry Fairhurst
> Cc: aqm@ietf.org
> Betreff: Re: [aqm] last call results on draft-ietf-aqm-recommendation
>=20
> Wes,
>=20
> Thx. In case I don't get time to read, then type, I'll shoot my mouth off
> anyway...
>=20
> Sorry this is a bit rushed and dismissive. That's not my intention - I'm =
v
> supportive of the recommendations that have now been carefully and nicely
> worded. I will give more detailed comments, but these are the MSBs.
>=20
> 1) My main concern: The two halves of the document seemed nearly
> unrelated (at least in draft-03 and it looks like draft-04 hasn't changed=
 this).
> The first half (Sections 1,2,&3) framed the problem as primarily about
> preventing congestion collapse and preventing flow-unfairness, while the
> recommendations (section 4) were about AQM. The irony of this sentence is
> deliberate.
>=20
> I had few concerns about the recommendations text (section 4), which
> we've all been focusing on, including me. But I hadn't realised the
> introductory text was so out of kilter with the recommendations.
>=20
> Sections 1,2 and 3 seemed to focus on problems that I wouldn't even addre=
ss
> with AQM (from a quick scan it looks like these sections haven't changed =
in
> this respect for draft-04):
>=20
> a) Congestion collapse: An AQM cannot prevent congestion collapse - that =
is
> the job of congestion control and, failing that, of policing.
> Even isolation (e.g. flow separation) doesn't prevent congestion collapse=
,
> because collapse is caused by the load from new flow arrivals exceeding t=
he
> ability of the system to serve and clear load from existing flows, most l=
ikely
> because many existing flows are not sufficiently responsive to congestion=
, so
> retransmissions dominate over goodput (even if each unresponsive flow is =
in
> an isolated silo).
> Flow separation doesn't help when the problem is too many flows.
>=20
> b) Flow fairness (or user-fairness etc): this is a policy issue that need=
s to be
> built in a modular way, for optional addition to AQM.
> Therefore an AQM must also work well without fairness mechanisms.
> This conclusion was actually reached in the early sections, but it's not =
carried
> forward into the recommendations in section 4.
>=20
> If the conclusion is that AQM isn't intended to solve these two problems,=
 we
> need to clearly say so. Most people who need to read this will be confuse=
d,
> so we shouldn't confuse them further!
>=20
>=20
> 2) There's no statement of scope.
> Can we really make all these recommendations irrespective of whether
> we're talking about high stat-mux core links, low stat-mux access links, =
low-
> stat-mux data centre links, or host buffers? Are there different
> recommendations for edge links (on trust boundaries) vs interior links? D=
oes
> AQM apply at L2 as well as L3 (of course it does)? Which recommendations
> are different for each layer? Does AQM apply for middleboxes (firewalls,
> NATs etc) as much as for switches and routers? If not why not (only need
> AQM if there can be queuing - perhaps due to processor overload)?
>=20
> To illustrate the problem, our goal should be AQM in every buffer.
> But we really don't need and shouldn't have policing or isolation in ever=
y
> buffer.
>=20
> 4) Because sections 1,2,3 focused heavily on the above two problems
> (collapse and fairness) that can't really be addressed by AQM, these sect=
ions
> also gave insufficient attention to problems that AQM does address (and
> should address), E.g.:
>=20
> * synchronisation and lock-out were both described as vaguely the same
> problem,
> * synchronisation wasn't explained,
> * lock-out wasn't explained but it was said to be vaguely to do with
> synchronisation and solving it would help low capacity bursty flows,
> * large-packet lock-out problems weren't mentioned, only flow-level lock-
> out.
>=20
> Perhaps as a result, there's no recommendation on avoiding synchronisatio=
n
> (e.g. using randomness).
>=20
> 5) I said these are the MSB's only, but allow me one nit about the Intro:
>=20
> "  there is currently no consensus solution to controlling the
>     congestion caused by such aggressive flows; significant research and
>     engineering will be required before any solution will be available.
>     It is imperative that this work be energetically pursued, to ensure
>     the future stability of the Internet.
> "
> The draft could at least mention congestion policing and ConEx RFCs comin=
g
> out of the IETF right now (e.g. RFC6789 and draft-ietf-conex-abstract-mec=
h,
> which is with the IESG).
>=20
>=20
> I promise I'll do a proper detailed review of the new text ASAP.
>=20
>=20
> Bob
>=20
> At 13:13 15/05/2014, Wesley Eddy wrote:
> >On 5/15/2014 5:09 AM, Bob Briscoe wrote:
> > > Wes,
> > >
> > > I assume you also want comments on the new version. Is there a
> > > deadline for comments?
> >
> >
> >Absolutely, yes.  There's no "deadline" at the moment, but it would be
> >good to get any out sooner rather than later, especially if they're
> >likely to need more discussion or are asking for major changes.
> >
> >
> > > I prepared comments on the previous version, but didn't get the time
> > > to type them up. So I want to try to remedy this with the new
> > > version (that I haven't read yet).
> >
> >
> >The diffs aren't huge, so many of your comments on the previous
> >revision might still be valid.
> >
> >
> >--
> >Wes Eddy
> >MTI Systems
> >
> >_______________________________________________
> >aqm mailing list
> >aqm@ietf.org
> >https://www.ietf.org/mailman/listinfo/aqm
>=20
> __________________________________________________________
> ______
> Bob Briscoe,                                                  BT
>=20
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm


From nobody Fri May 16 05:11:44 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 C5BB21A022B for <aqm@ietfa.amsl.com>; Fri, 16 May 2014 05:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level: 
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 eTU2TfTXKaaw for <aqm@ietfa.amsl.com>; Fri, 16 May 2014 05:11:37 -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 6B1391A0024 for <aqm@ietf.org>; Fri, 16 May 2014 05:11:37 -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 36CF12B43B3; Fri, 16 May 2014 13:11:29 +0100 (BST)
Received: from 2001:630:241:204:214:51ff:fe63:569f (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Fri, 16 May 2014 13:11:29 +0100
Message-ID: <3f13dad94a98b4a48f9cd25bc683b9e1.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <0A452E1DADEF254C9A7AC1969B87812806A3BB@FR712WXCHMBA13.zeu.alcatel-lucent.com>
References: <5366F905.7060905@mti-systems.com> <537415CE.20106@mti-systems.com> <201405150909.s4F99uTx026736@bagheera.jungle.bt.co.uk> <5374AF87.5080607@mti-systems.com> <201405151432.s4FEWeGd027834@bagheera.jungle.bt.co.uk> <0A452E1DADEF254C9A7AC1969B87812806A3BB@FR712WXCHMBA13.zeu.alcatel-lucent.com>
Date: Fri, 16 May 2014 13:11:29 +0100
From: gorry@erg.abdn.ac.uk
To: "LAUTENSCHLAEGER, Wolfram (Wolfram)" <wolfram.lautenschlaeger@alcatel-lucent.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/D6YeMPuyGz0gx_uCwtRkq_AlJac
Cc: "aqm@ietf.org" <aqm@ietf.org>, Bob Briscoe <bob.briscoe@bt.com>
Subject: Re: [aqm] last call results on draft-ietf-aqm-recommendation
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, 16 May 2014 12:11:43 -0000

See comments in-line, Gorry

First, is this based on teh discussion or the revised draft text in -04,
where the words were chosen to try to reflect this - but carefully avoid
saying you can not integrate AQM & scheduling?

> I strongly agree with Bob's concerns:
>
> - Congestion collapse cannot be prevented by AQM
> - Flow fairness is not a topic for AQM
> - AQM should be possible without any knowledge of particular flows.
> As such it is clearly a L2 mechanism (which does not mean that it
> cannot be applied in L3 boxes).
>
> Of course, in technical implementations an AQM could be combined
> with fairness mechanisms like the fq_X proposals do. (I assume that
> in such combination AQM and scheduling essentially operate on the
> same queue or group of queues.) But for a clear understanding,
> what a particular AQM does, I would prefer to see the AQM
> algorithm in isolation.
>
> AQM should be applied to every buffer that can be overloaded and
> TCP is involved, i.e. where ingress rate can be higher the egress rate
> and no backpressure is in place. In middleboxes with ingress == egress
> rates this is not the case, except the processing capacity is
> insufficient.
>
There can also questions with current algorithms about parameter settings
if you implement this away from the edge whre you don't know the flow path
RTT and other params - but  that's something to work upon.

> In my opinion AQM applies to multiplexed links, where several flows
> share the same transmission capacity. AQM cannot do a lot for a
> single flow on one link. In the capacity sharing case the effects of
> synchronization and burstiness of drops are strongly tied together.
> Removing the one also removes the other and this is the most what
> AQM can afford.
>
OK

> Wolfram
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: aqm [mailto:aqm-bounces@ietf.org] Im Auftrag von Bob Briscoe
>> Gesendet: Donnerstag, 15. Mai 2014 16:32
>> An: Wesley Eddy; Fred Baker; Gorry Fairhurst
>> Cc: aqm@ietf.org
>> Betreff: Re: [aqm] last call results on draft-ietf-aqm-recommendation
>>
>> Wes,
>>
>> Thx. In case I don't get time to read, then type, I'll shoot my mouth
>> off
>> anyway...
>>
>> Sorry this is a bit rushed and dismissive. That's not my intention - I'm
>> v
>> supportive of the recommendations that have now been carefully and
>> nicely
>> worded. I will give more detailed comments, but these are the MSBs.
>>
>> 1) My main concern: The two halves of the document seemed nearly
>> unrelated (at least in draft-03 and it looks like draft-04 hasn't
>> changed this).
>> The first half (Sections 1,2,&3) framed the problem as primarily about
>> preventing congestion collapse and preventing flow-unfairness, while the
>> recommendations (section 4) were about AQM. The irony of this sentence
>> is
>> deliberate.
>>
>> I had few concerns about the recommendations text (section 4), which
>> we've all been focusing on, including me. But I hadn't realised the
>> introductory text was so out of kilter with the recommendations.
>>
>> Sections 1,2 and 3 seemed to focus on problems that I wouldn't even
>> address
>> with AQM (from a quick scan it looks like these sections haven't changed
>> in
>> this respect for draft-04):
>>
>> a) Congestion collapse: An AQM cannot prevent congestion collapse - that
>> is
>> the job of congestion control and, failing that, of policing.
>> Even isolation (e.g. flow separation) doesn't prevent congestion
>> collapse,
>> because collapse is caused by the load from new flow arrivals exceeding
>> the
>> ability of the system to serve and clear load from existing flows, most
>> likely
>> because many existing flows are not sufficiently responsive to
>> congestion, so
>> retransmissions dominate over goodput (even if each unresponsive flow is
>> in
>> an isolated silo).
>> Flow separation doesn't help when the problem is too many flows.
>>
>> b) Flow fairness (or user-fairness etc): this is a policy issue that
>> needs to be
>> built in a modular way, for optional addition to AQM.
>> Therefore an AQM must also work well without fairness mechanisms.
>> This conclusion was actually reached in the early sections, but it's not
>> carried
>> forward into the recommendations in section 4.
>>
>> If the conclusion is that AQM isn't intended to solve these two
>> problems, we
>> need to clearly say so. Most people who need to read this will be
>> confused,
>> so we shouldn't confuse them further!
>>
>>
>> 2) There's no statement of scope.
>> Can we really make all these recommendations irrespective of whether
>> we're talking about high stat-mux core links, low stat-mux access links,
>> low-
>> stat-mux data centre links, or host buffers? Are there different
>> recommendations for edge links (on trust boundaries) vs interior links?
>> Does
>> AQM apply at L2 as well as L3 (of course it does)? Which recommendations
>> are different for each layer? Does AQM apply for middleboxes (firewalls,
>> NATs etc) as much as for switches and routers? If not why not (only need
>> AQM if there can be queuing - perhaps due to processor overload)?
>>
>> To illustrate the problem, our goal should be AQM in every buffer.
>> But we really don't need and shouldn't have policing or isolation in
>> every
>> buffer.
>>
>> 4) Because sections 1,2,3 focused heavily on the above two problems
>> (collapse and fairness) that can't really be addressed by AQM, these
>> sections
>> also gave insufficient attention to problems that AQM does address (and
>> should address), E.g.:
>>
>> * synchronisation and lock-out were both described as vaguely the same
>> problem,
>> * synchronisation wasn't explained,
>> * lock-out wasn't explained but it was said to be vaguely to do with
>> synchronisation and solving it would help low capacity bursty flows,
>> * large-packet lock-out problems weren't mentioned, only flow-level
>> lock-
>> out.
>>
>> Perhaps as a result, there's no recommendation on avoiding
>> synchronisation
>> (e.g. using randomness).
>>
>> 5) I said these are the MSB's only, but allow me one nit about the
>> Intro:
>>
>> "  there is currently no consensus solution to controlling the
>>     congestion caused by such aggressive flows; significant research and
>>     engineering will be required before any solution will be available.
>>     It is imperative that this work be energetically pursued, to ensure
>>     the future stability of the Internet.
>> "
>> The draft could at least mention congestion policing and ConEx RFCs
>> coming
>> out of the IETF right now (e.g. RFC6789 and
>> draft-ietf-conex-abstract-mech,
>> which is with the IESG).
>>
>>
>> I promise I'll do a proper detailed review of the new text ASAP.
>>
>>
>> Bob
>>
>> At 13:13 15/05/2014, Wesley Eddy wrote:
>> >On 5/15/2014 5:09 AM, Bob Briscoe wrote:
>> > > Wes,
>> > >
>> > > I assume you also want comments on the new version. Is there a
>> > > deadline for comments?
>> >
>> >
>> >Absolutely, yes.  There's no "deadline" at the moment, but it would be
>> >good to get any out sooner rather than later, especially if they're
>> >likely to need more discussion or are asking for major changes.
>> >
>> >
>> > > I prepared comments on the previous version, but didn't get the time
>> > > to type them up. So I want to try to remedy this with the new
>> > > version (that I haven't read yet).
>> >
>> >
>> >The diffs aren't huge, so many of your comments on the previous
>> >revision might still be valid.
>> >
>> >
>> >--
>> >Wes Eddy
>> >MTI Systems
>> >
>> >_______________________________________________
>> >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
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>



From nobody Thu May 22 18:40:57 2014
Return-Path: <denglingli@chinamobile.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 166751A02B3 for <aqm@ietfa.amsl.com>; Thu, 22 May 2014 18:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.871
X-Spam-Level: *
X-Spam-Status: No, score=1.871 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RELAY_IS_221=2.222, RP_MATCHES_RCVD=-0.651] 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 l_QXJ5P-CJIg for <aqm@ietfa.amsl.com>; Thu, 22 May 2014 18:40:54 -0700 (PDT)
Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.176.64.232]) by ietfa.amsl.com (Postfix) with SMTP id 27A9F1A02A3 for <aqm@ietf.org>; Thu, 22 May 2014 18:40:52 -0700 (PDT)
Received: from spf.mail.chinamobile.com (unknown[172.16.20.11]) by rmmx-oa_allagent01-12001 (RichMail) with SMTP id 2ee1537ea707fcb-5ffcb; Fri, 23 May 2014 09:40:24 +0800 (CST)
X-RM-TRANSID: 2ee1537ea707fcb-5ffcb
Received: from cmccPC (unknown[10.2.43.246]) by rmsmtp-oa_rmapp01-12001 (RichMail) with SMTP id 2ee1537ea702a7f-8bd98; Fri, 23 May 2014 09:40:24 +0800 (CST)
X-RM-TRANSID: 2ee1537ea702a7f-8bd98
From: =?utf-8?B?6YKT54G16I6JL0xpbmdsaSBEZW5n?= <denglingli@chinamobile.com>
To: "'Michael Welzl'" <michawe@ifi.uio.no>, <gorry@erg.abdn.ac.uk>
Date: Fri, 23 May 2014 09:40:48 +0800
Message-ID: <012201cf7628$06034240$1209c6c0$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0123_01CF766B.14268240"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac92KAWYNIfQhGK1SeGA+EVOujYrJA==
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/PDkXJw5H1cSQmt4ABiL7q8_gru0
Cc: aqm@ietf.org
Subject: [aqm] questions for 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, 23 May 2014 01:40:56 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0123_01CF766B.14268240
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Michael and Gorry,
=20
I am following the ECN progress at IETF, and heard your presentation for =
draft-welzl-ecn-benefits in London. I am highly interested in this =
topic.
=20
As you might know that 3GPP had long completed ECN specification for =
audio/video service on the base station for congestion notification over =
the wireless link, but there is few experience in real practice. I am =
therefore interested in your draft and would like to see how it may help =
us with cellular scenario.

=20

In particular, I believe the following questions regarding complications =
on ECN enabling from the network side are also relevant to this draft.=20

=20

1, There are various middle-boxes along the end-to-end path where ECN =
signal is supposed to be communicated but actually partitioned at the =
middle-boxes. What are your recommendations regarding these boxes would =
also be part of the conclusion. For instance, TCP/HTTP/RTP proxy.

2, Tunnels, where end-to-end congestion status is separated in different =
headers and need to be combined or dropped at the tunnel exit. For =
example, GRE/IPSec tunneling.

3, Deployment considerations, it is somehow related to the first two, do =
we have to assume a unified deployment of consistent end-to-end ECN =
behavior in order to achieve the optimal gain? If so, the above issues =
need to be addressed. Otherwise, how can one choose between end-to-end =
and hop-by hop?

=20

Looking forward to your reply and thanks in advance.

=20

Regards,

Lingli


------=_NextPart_000_0123_01CF766B.14268240
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 12 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:=E5=AE=8B=E4=BD=93;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:"\@=E5=AE=8B=E4=BD=93";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=E5=AE=8B=E4=BD=93;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLChar
	{mso-style-name:"HTML =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F Char";
	mso-style-priority:99;
	mso-style-link:"HTML =E9=A2=84=E8=AE=BE=E6=A0=BC=E5=BC=8F";
	font-family:=E5=AE=8B=E4=BD=93;}
.MsoChpDefault
	{mso-style-type:export-only;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DZH-CN link=3Dblue =
vlink=3Dpurple style=3D'text-justify-trim:punctuation'><div =
class=3DWordSection1><pre><span lang=3DEN-US>Hi Michael and =
Gorry,<o:p></o:p></span></pre><pre><span =
lang=3DEN-US>&nbsp;<o:p></o:p></span></pre><pre><span lang=3DEN-US>I am =
following the ECN progress at IETF, and heard your presentation for =
draft-welzl-ecn-benefits in London. I am highly interested in this =
topic.<o:p></o:p></span></pre><pre><span =
lang=3DEN-US>&nbsp;<o:p></o:p></span></pre><pre><span lang=3DEN-US>As =
you might know that 3GPP had long completed ECN specification for =
audio/video service on the base station for congestion notification over =
the wireless link, but there is few experience in real practice. I am =
therefore interested in your draft and would like to see how it may help =
us with cellular scenario.<o:p></o:p></span></pre><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:=E5=AE=8B=E4=BD=93'><o:p>&nbsp;</o:=
p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:=E5=AE=8B=E4=BD=93'>In particular, =
I believe the following questions regarding complications on ECN =
enabling from the network side are also relevant to this draft. =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:=E5=AE=8B=E4=BD=93'>=C2=A0<o:p></o:=
p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:=E5=AE=8B=E4=BD=93'>1, There are =
various middle-boxes along the end-to-end path where ECN signal is =
supposed to be communicated but actually partitioned at the =
middle-boxes. What are your recommendations regarding these boxes would =
also be part of the conclusion. For instance, TCP/HTTP/RTP =
proxy.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:=E5=AE=8B=E4=BD=93'>2, Tunnels, =
where end-to-end congestion status is separated in different headers and =
need to be combined or dropped at the tunnel exit. For example, =
GRE/IPSec tunneling.<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:=E5=AE=8B=E4=BD=93'>3, Deployment =
considerations, it is somehow related to the first two, do we have to =
assume a unified deployment of consistent end-to-end ECN behavior in =
order to achieve the optimal gain? If so, the above issues need to be =
addressed. Otherwise, how can one choose between end-to-end and hop-by =
hop?<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:=E5=AE=8B=E4=BD=93'><o:p>&nbsp;</o:=
p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:=E5=AE=8B=E4=BD=93'>Looking =
forward to your reply and thanks in advance.<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:=E5=AE=8B=E4=BD=93'><o:p>&nbsp;</o:=
p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:=E5=AE=8B=E4=BD=93'>Regards,<o:p></=
o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:12.0pt;font-family:=E5=AE=8B=E4=BD=93'>Lingli<o:p></o:=
p></span></p></div></body></html>
------=_NextPart_000_0123_01CF766B.14268240--




From nobody Fri May 23 01:18:21 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 E4DB71A03C0 for <aqm@ietfa.amsl.com>; Fri, 23 May 2014 01:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level: 
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651] 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 F0tcw7e6IMFq for <aqm@ietfa.amsl.com>; Fri, 23 May 2014 01:18:15 -0700 (PDT)
Received: from mail-out2.uio.no (mail-out2.uio.no [IPv6:2001:700:100:10::58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22CD01A03BE for <aqm@ietf.org>; Fri, 23 May 2014 01:18:14 -0700 (PDT)
Received: from mail-mx3.uio.no ([129.240.10.44]) by mail-out2.uio.no with esmtp (Exim 4.75) (envelope-from <michawe@ifi.uio.no>) id 1Wnkg6-0005fQ-7N; Fri, 23 May 2014 10:18:10 +0200
Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx3.uio.no with esmtpsa (TLSv1:AES128-SHA:128) user michawe (Exim 4.80) (envelope-from <michawe@ifi.uio.no>) id 1Wnkg5-0002jY-Lt; Fri, 23 May 2014 10:18:10 +0200
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_94AFCE1F-34D4-4024-A374-6EC431D57FF7"
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <012201cf7628$06034240$1209c6c0$@com>
Date: Fri, 23 May 2014 10:18:06 +0200
Message-Id: <CE46D820-C5EC-4DC6-9A72-E787CC744EA9@ifi.uio.no>
References: <012201cf7628$06034240$1209c6c0$@com>
To: =?utf-8?Q?=E9=82=93=E7=81=B5=E8=8E=89/Lingli_Deng?= <denglingli@chinamobile.com>
X-Mailer: Apple Mail (2.1283)
X-UiO-SPF-Received: 
X-UiO-Ratelimit-Test: rcpts/h 4 msgs/h 2 sum rcpts/h 6 sum msgs/h 3 total rcpts 16675 max rcpts/h 44 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-6.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-1.051, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 19C31F48AC08A3C2D7D9AFEABCBECE353587279A
X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -59 maxlevel 80 minaction 2 bait 0 mail/h: 2 total 5433 max/h 16 blacklist 0 greylist 0 ratelimit 0
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/1UirbBpvF0DmjywCIyatSdfl41A
Cc: gorry@erg.abdn.ac.uk, aqm@ietf.org
Subject: Re: [aqm] questions for 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, 23 May 2014 08:18:18 -0000

--Apple-Mail=_94AFCE1F-34D4-4024-A374-6EC431D57FF7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

Thanks for your interest! More below:

On 23. mai 2014, at 03:40, =E9=82=93=E7=81=B5=E8=8E=89/Lingli Deng =
wrote:

> Hi Michael and Gorry,
> =20
> I am following the ECN progress at IETF, and heard your presentation =
for draft-welzl-ecn-benefits in London. I am highly interested in this =
topic.
> =20
> As you might know that 3GPP had long completed ECN specification for =
audio/video service on the base station for congestion notification over =
the wireless link, but there is few experience in real practice. I am =
therefore interested in your draft and would like to see how it may help =
us with cellular scenario.
> =20
> In particular, I believe the following questions regarding =
complications on ECN enabling from the network side are also relevant to =
this draft.
> =20
> 1, There are various middle-boxes along the end-to-end path where ECN =
signal is supposed to be communicated but actually partitioned at the =
middle-boxes. What are your recommendations regarding these boxes would =
also be part of the conclusion. For instance, TCP/HTTP/RTP proxy.

Such boxes terminate TCP connections,right? So you can have ECN for each =
of them, influencing each congestion controller separately; in other =
words, I don't think you need to do anything special for these boxes.


> 2, Tunnels, where end-to-end congestion status is separated in =
different headers and need to be combined or dropped at the tunnel exit. =
For example, GRE/IPSec tunneling.

There is draft-briscoe-tsvwg-ecn-encap-guidelines


> 3, Deployment considerations, it is somehow related to the first two, =
do we have to assume a unified deployment of consistent end-to-end ECN =
behavior in order to achieve the optimal gain? If so, the above issues =
need to be addressed. Otherwise, how can one choose between end-to-end =
and hop-by hop?

If ECN is ignored by non-supportive systems (as they should), ECN only =
needs to operate at the bottleneck. This actually makes for a nice =
deployment situation in principle, given that the bottleneck is often =
the access link.  There are, of course, other deployment issues with =
ECN, and they are discussed at length in various recent and =
not-so-recent papers. I think citing them and discussing the current =
state of things briefly in this draft could be a good idea.

Cheers,
Michael


--Apple-Mail=_94AFCE1F-34D4-4024-A374-6EC431D57FF7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><base href=3D"x-msg://106/"></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 interest! =
More below:</div><div><br><div><div>On 23. mai 2014, at 03:40, =
=E9=82=93=E7=81=B5=E8=8E=89/Lingli Deng wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><pre style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; "><span lang=3D"EN-US">Hi Michael =
and Gorry,<o:p></o:p></span></pre><pre style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; "><span =
lang=3D"EN-US">&nbsp;<o:p></o:p></span></pre><pre style=3D"margin-top: =
0cm; margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93; "><span lang=3D"EN-US">I=
 am following the ECN progress at IETF, and heard your presentation for =
draft-welzl-ecn-benefits in London. I am highly interested in this =
topic.<o:p></o:p></span></pre><pre style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: =E5=AE=8B=E4=BD=93; "><span =
lang=3D"EN-US">&nbsp;<o:p></o:p></span></pre><pre style=3D"margin-top: =
0cm; margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93; "><span =
lang=3D"EN-US">As you might know that 3GPP had long completed ECN =
specification for audio/video service on the base station for congestion =
notification over the wireless link, but there is few experience in real =
practice. I am therefore interested in your draft and would like to see =
how it may help us with cellular scenario.<o:p></o:p></span></pre><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; text-align: justify; font-size: 10.5pt; =
font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; =
text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif; "><span lang=3D"EN-US" style=3D"font-size: 12pt; =
font-family: =E5=AE=8B=E4=BD=93; ">In particular, I believe the =
following questions regarding complications on ECN enabling from the =
network side are also relevant to this =
draft.<o:p></o:p></span></div><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; =
text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif; "><span lang=3D"EN-US" style=3D"font-size: 12pt; =
font-family: =E5=AE=8B=E4=BD=93; ">&nbsp;<o:p></o:p></span></div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; text-align: justify; font-size: 10.5pt; =
font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93; ">1, There =
are various middle-boxes along the end-to-end path where ECN signal is =
supposed to be communicated but actually partitioned at the =
middle-boxes. What are your recommendations regarding these boxes would =
also be part of the conclusion. For instance, TCP/HTTP/RTP =
proxy.</span></div></div></div></span></blockquote><div><br></div><div>Suc=
h boxes terminate TCP connections,right? So you can have ECN for each of =
them, influencing each congestion controller separately; in other words, =
I don't think you need to do anything special for these =
boxes.</div><div><br></div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; =
text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif; "><span lang=3D"EN-US" style=3D"font-size: 12pt; =
font-family: =E5=AE=8B=E4=BD=93; "><o:p></o:p></span></div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; text-align: justify; font-size: 10.5pt; =
font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93; ">2, Tunnels, =
where end-to-end congestion status is separated in different headers and =
need to be combined or dropped at the tunnel exit. For example, =
GRE/IPSec =
tunneling.</span></div></div></div></span></blockquote><div><br></div><div=
>There =
is&nbsp;draft-briscoe-tsvwg-ecn-encap-guidelines</div><div><br></div><br><=
blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0cm; =
margin-right: 0cm; margin-left: 0cm; margin-bottom: 0.0001pt; =
text-align: justify; font-size: 10.5pt; font-family: Calibri, =
sans-serif; "><span lang=3D"EN-US" style=3D"font-size: 12pt; =
font-family: =E5=AE=8B=E4=BD=93; "><o:p></o:p></span></div><div =
style=3D"margin-top: 0cm; margin-right: 0cm; margin-left: 0cm; =
margin-bottom: 0.0001pt; text-align: justify; font-size: 10.5pt; =
font-family: Calibri, sans-serif; "><span lang=3D"EN-US" =
style=3D"font-size: 12pt; font-family: =E5=AE=8B=E4=BD=93; ">3, =
Deployment considerations, it is somehow related to the first two, do we =
have to assume a unified deployment of consistent end-to-end ECN =
behavior in order to achieve the optimal gain? If so, the above issues =
need to be addressed. Otherwise, how can one choose between end-to-end =
and hop-by =
hop?</span></div></div></div></span></blockquote><div><br></div><div>If =
ECN is ignored by non-supportive systems (as they should), ECN only =
needs to operate at the bottleneck. This actually makes for a nice =
deployment situation in principle, given that the bottleneck is often =
the access link. &nbsp;There are, of course, other deployment issues =
with ECN, and they are discussed at length in various recent and =
not-so-recent papers. I think citing them and discussing the current =
state of things briefly in this draft could be a good =
idea.</div><div><br></div><div>Cheers,</div><div>Michael</div><div><br></d=
iv></div></div></body></html>=

--Apple-Mail=_94AFCE1F-34D4-4024-A374-6EC431D57FF7--


From nobody Fri May 23 05:07:39 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 2F8531A017F for <aqm@ietfa.amsl.com>; Fri, 23 May 2014 05:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.252
X-Spam-Level: 
X-Spam-Status: No, score=-7.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, 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 rah-4GR30BMY for <aqm@ietfa.amsl.com>; Fri, 23 May 2014 05:07:31 -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 4F6A61A0177 for <aqm@ietf.org>; Fri, 23 May 2014 05:07:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.98,893,1392192000";  d="scan'208,217";a="166126903"
Received: from vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) by mx12-out.netapp.com with ESMTP; 23 May 2014 05:07:29 -0700
Received: from SACEXCMBX02-PRD.hq.netapp.com ([169.254.1.105]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.03.0123.003; Fri, 23 May 2014 05:07:29 -0700
From: "Scheffenegger, Richard" <rs@netapp.com>
To: Michael Welzl <michawe@ifi.uio.no>, =?utf-8?B?6YKT54G16I6JL0xpbmdsaSBEZW5n?= <denglingli@chinamobile.com>
Thread-Topic: [aqm] questions for draft-welzl-ecn-benefits
Thread-Index: Ac92KAWYNIfQhGK1SeGA+EVOujYrJAAcizQAAAb8apA=
Date: Fri, 23 May 2014 12:07:28 +0000
Message-ID: <012C3117EDDB3C4781FD802A8C27DD4F4A3CC245@SACEXCMBX02-PRD.hq.netapp.com>
References: <012201cf7628$06034240$1209c6c0$@com> <CE46D820-C5EC-4DC6-9A72-E787CC744EA9@ifi.uio.no>
In-Reply-To: <CE46D820-C5EC-4DC6-9A72-E787CC744EA9@ifi.uio.no>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.53]
Content-Type: multipart/alternative; boundary="_000_012C3117EDDB3C4781FD802A8C27DD4F4A3CC245SACEXCMBX02PRDh_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/aqm/oTpy5Y_07n-UVy00BMzvFxyfMkM
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] questions for 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, 23 May 2014 12:07:35 -0000

--_000_012C3117EDDB3C4781FD802A8C27DD4F4A3CC245SACEXCMBX02PRDh_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

W2FzIGluZGl2aWR1YWxdDQoNCkhpIExpbmdsaSwNCg0KSWYgeW91IG1lYW4gYnkg4oCedW5pZmll
ZCBkZXBsb3ltZW504oCdIHRoYXQgeW91IG5lZWQgc2ltaWxhciBBUU0gc2NoZW1lcyB3aXRoIHRo
ZSBzYW1lIHBhcmFtZXRlcnMvZ29hbHMsIHRoZW4gbm87DQoNCkZvciBFQ04gdG8gYWNoaWV2ZSBp
dHMgZ29hbCAocHJvdmlkZWQgdGhlIGVuZCBob3N0cyBhcmUgcmVhY3RpdmUpLCBvbmx5IHRoZSBt
YXJraW5nIHByb2JhYmlsaXR5IG5lZWRzIHRvIGJlIHJvdWdobHkgcHJvcG9ydGlvbmFsIHRvIHRo
ZSBsZXZlbCBvZiBjb25nZXN0aW9uLiBJZiBhIHBhdGggaGFzIG11bHRpcGxlIGNvbmdlc3Rpb24g
cG9pbnRzIGF0IGRpZmZlcmVudCBsZXZlbHMsIHRoZSBFQ04gbWFya3Mgd2lsbCBpbmRpY2F0ZSB0
aGUgYXBwcm9wcmlhdGUgZW5kLXRvLWVuZCBjb25nZXN0aW9uIGxldmVsIHRoYXQgcGF0aCBzaG91
bGQgcmVhY3QgdXBvbi4gU28sIGRlcGxveWluZyBBUU0gd2l0aCBlbnRpcmVseSBkaWZmZXJlbnQg
YmVoYXZpb3VyIChpZS4gb25lIHRvIGtlZXAgcXVldWUgc29qb3VybiB0aW1lIGRvd24sIGFuZCBh
bm90aGVyIHRoYXQgc2ltcGx5IHRyaWVzIHRvIGtlZXAgdGhlIHF1ZXVlIGxlbmd0aCBzbGlnaHRs
eSBiZWxvdyBtYXhpbXVtKSBpcyBqdXN0IGZpbmUuDQoNClRoZXJlIGFyZSBvdGhlciBhc3BlY3Rz
IOKAkyBpbiB0aGUgZW5kIGhvc3RzIOKAkyB0aGF0IHNob3VsZCBiZSBpbXByb3ZlZCB1cG9uLCB0
aG91Z2guIE5vdCBhbGwgdHJhbnNwb3J0cyBmZWF0dXJlIGdyYW51bGFyIGVub3VnaCBmZWVkYmFj
ayBtZWNoYW5pc21zLCBhbmQgbm90IGFsbCB0cmFuc3BvcnRzIHN1cHBvcnQgZ3JhbnVsYXIgcmVz
cG9uc2VzIHRvIHZhcnlpbmcgbGV2ZWxzIG9mIEVDTiBmZWVkYmFjay4gSGF2aW5nIGNvbnNpc3Rl
bmN5IHRoZXJlIGlzIGltcG9ydGFudC4NCg0KDQozLCBEZXBsb3ltZW50IGNvbnNpZGVyYXRpb25z
LCBpdCBpcyBzb21laG93IHJlbGF0ZWQgdG8gdGhlIGZpcnN0IHR3bywgZG8gd2UgaGF2ZSB0byBh
c3N1bWUgYSB1bmlmaWVkIGRlcGxveW1lbnQgb2YgY29uc2lzdGVudCBlbmQtdG8tZW5kIEVDTiBi
ZWhhdmlvciBpbiBvcmRlciB0byBhY2hpZXZlIHRoZSBvcHRpbWFsIGdhaW4/IElmIHNvLCB0aGUg
YWJvdmUgaXNzdWVzIG5lZWQgdG8gYmUgYWRkcmVzc2VkLiBPdGhlcndpc2UsIGhvdyBjYW4gb25l
IGNob29zZSBiZXR3ZWVuIGVuZC10by1lbmQgYW5kIGhvcC1ieSBob3A/DQoNCklmIEVDTiBpcyBp
Z25vcmVkIGJ5IG5vbi1zdXBwb3J0aXZlIHN5c3RlbXMgKGFzIHRoZXkgc2hvdWxkKSwgRUNOIG9u
bHkgbmVlZHMgdG8gb3BlcmF0ZSBhdCB0aGUgYm90dGxlbmVjay4gVGhpcyBhY3R1YWxseSBtYWtl
cyBmb3IgYSBuaWNlIGRlcGxveW1lbnQgc2l0dWF0aW9uIGluIHByaW5jaXBsZSwgZ2l2ZW4gdGhh
dCB0aGUgYm90dGxlbmVjayBpcyBvZnRlbiB0aGUgYWNjZXNzIGxpbmsuICBUaGVyZSBhcmUsIG9m
IGNvdXJzZSwgb3RoZXIgZGVwbG95bWVudCBpc3N1ZXMgd2l0aCBFQ04sIGFuZCB0aGV5IGFyZSBk
aXNjdXNzZWQgYXQgbGVuZ3RoIGluIHZhcmlvdXMgcmVjZW50IGFuZCBub3Qtc28tcmVjZW50IHBh
cGVycy4gSSB0aGluayBjaXRpbmcgdGhlbSBhbmQgZGlzY3Vzc2luZyB0aGUgY3VycmVudCBzdGF0
ZSBvZiB0aGluZ3MgYnJpZWZseSBpbiB0aGlzIGRyYWZ0IGNvdWxkIGJlIGEgZ29vZCBpZGVhLg0K
DQoNCg0K

--_000_012C3117EDDB3C4781FD802A8C27DD4F4A3CC245SACEXCMBX02PRDh_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPGJhc2Ug
aHJlZj0ieC1tc2c6Ly8xMDYvIj48c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0K
QGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpTaW1TdW47DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEg
MSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlNpbVN1bjsNCglwYW5vc2UtMToy
IDEgNiAwIDMgMSAxIDEgMSAxO30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsN
CglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFt
aWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCkBmb250LWZh
Y2UNCgl7Zm9udC1mYW1pbHk6IlxAU2ltU3VuIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEg
MSAxO30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFs
LCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0K
CWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlm
Ijt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBz
cGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsN
CgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0
Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0Kc3Bhbi5hcHBsZS1zdHlsZS1zcGFuDQoJ
e21zby1zdHlsZS1uYW1lOmFwcGxlLXN0eWxlLXNwYW47fQ0Kc3Bhbi5IVE1MUHJlZm9ybWF0dGVk
Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCI7DQoJ
Zm9udC1mYW1pbHk6Q29uc29sYXM7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5
cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsN
Cgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9y
dC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6
NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3MC44NXB0IDcwLjg1cHQgMi4wY20gNzAuODVwdDt9
DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlk
bWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0
YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxi
b2R5IGxhbmc9IkRFLUFUIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9
IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlthcyBpbmRpdmlkdWFsXTxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5IaSBMaW5nbGksPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPklmIHlvdSBtZWFuIGJ5IOKAnnVuaWZpZWQgZGVwbG95bWVu
dOKAnSB0aGF0IHlvdSBuZWVkIHNpbWlsYXIgQVFNIHNjaGVtZXMgd2l0aCB0aGUgc2FtZSBwYXJh
bWV0ZXJzL2dvYWxzLCB0aGVuIG5vOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6
IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdE
Ij5Gb3IgRUNOIHRvIGFjaGlldmUgaXRzIGdvYWwgKHByb3ZpZGVkIHRoZSBlbmQgaG9zdHMgYXJl
IHJlYWN0aXZlKSwgb25seSB0aGUgbWFya2luZyBwcm9iYWJpbGl0eSBuZWVkcyB0byBiZSByb3Vn
aGx5IHByb3BvcnRpb25hbCB0byB0aGUgbGV2ZWwgb2YNCiBjb25nZXN0aW9uLiBJZiBhIHBhdGgg
aGFzIG11bHRpcGxlIGNvbmdlc3Rpb24gcG9pbnRzIGF0IGRpZmZlcmVudCBsZXZlbHMsIHRoZSBF
Q04gbWFya3Mgd2lsbCBpbmRpY2F0ZSB0aGUgYXBwcm9wcmlhdGUgZW5kLXRvLWVuZCBjb25nZXN0
aW9uIGxldmVsIHRoYXQgcGF0aCBzaG91bGQgcmVhY3QgdXBvbi4gU28sIGRlcGxveWluZyBBUU0g
d2l0aCBlbnRpcmVseSBkaWZmZXJlbnQgYmVoYXZpb3VyIChpZS4gb25lIHRvIGtlZXAgcXVldWUg
c29qb3Vybg0KIHRpbWUgZG93biwgYW5kIGFub3RoZXIgdGhhdCBzaW1wbHkgdHJpZXMgdG8ga2Vl
cCB0aGUgcXVldWUgbGVuZ3RoIHNsaWdodGx5IGJlbG93IG1heGltdW0pIGlzIGp1c3QgZmluZS48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+VGhlcmUgYXJlIG90aGVyIGFzcGVj
dHMg4oCTIGluIHRoZSBlbmQgaG9zdHMg4oCTIHRoYXQgc2hvdWxkIGJlIGltcHJvdmVkIHVwb24s
IHRob3VnaC4gTm90IGFsbCB0cmFuc3BvcnRzIGZlYXR1cmUgZ3JhbnVsYXIgZW5vdWdoIGZlZWRi
YWNrIG1lY2hhbmlzbXMsDQogYW5kIG5vdCBhbGwgdHJhbnNwb3J0cyBzdXBwb3J0IGdyYW51bGFy
IHJlc3BvbnNlcyB0byB2YXJ5aW5nIGxldmVscyBvZiBFQ04gZmVlZGJhY2suIEhhdmluZyBjb25z
aXN0ZW5jeSB0aGVyZSBpcyBpbXBvcnRhbnQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAw
Y20gNC4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWFsaWduOmp1c3RpZnkiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1mYW1pbHk6U2ltU3VuO21zby1mYXJlYXN0LWxhbmd1YWdlOlpILUNOIj4zLCBE
ZXBsb3ltZW50IGNvbnNpZGVyYXRpb25zLCBpdCBpcyBzb21laG93IHJlbGF0ZWQgdG8gdGhlIGZp
cnN0IHR3bywgZG8gd2UgaGF2ZSB0byBhc3N1bWUgYSB1bmlmaWVkIGRlcGxveW1lbnQgb2YgY29u
c2lzdGVudCBlbmQtdG8tZW5kDQogRUNOIGJlaGF2aW9yIGluIG9yZGVyIHRvIGFjaGlldmUgdGhl
IG9wdGltYWwgZ2Fpbj8gSWYgc28sIHRoZSBhYm92ZSBpc3N1ZXMgbmVlZCB0byBiZSBhZGRyZXNz
ZWQuIE90aGVyd2lzZSwgaG93IGNhbiBvbmUgY2hvb3NlIGJldHdlZW4gZW5kLXRvLWVuZCBhbmQg
aG9wLWJ5IGhvcD88L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O21zby1mYXJlYXN0
LWxhbmd1YWdlOlpILUNOIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPklmIEVDTiBpcyBpZ25vcmVkIGJ5IG5vbi1zdXBwb3J0aXZl
IHN5c3RlbXMgKGFzIHRoZXkgc2hvdWxkKSwgRUNOIG9ubHkgbmVlZHMgdG8gb3BlcmF0ZSBhdCB0
aGUgYm90dGxlbmVjay4gVGhpcyBhY3R1YWxseSBtYWtlcyBmb3IgYSBuaWNlIGRlcGxveW1lbnQg
c2l0dWF0aW9uIGluIHByaW5jaXBsZSwgZ2l2ZW4gdGhhdCB0aGUgYm90dGxlbmVjayBpcyBvZnRl
biB0aGUgYWNjZXNzIGxpbmsuICZuYnNwO1RoZXJlIGFyZSwNCiBvZiBjb3Vyc2UsIG90aGVyIGRl
cGxveW1lbnQgaXNzdWVzIHdpdGggRUNOLCBhbmQgdGhleSBhcmUgZGlzY3Vzc2VkIGF0IGxlbmd0
aCBpbiB2YXJpb3VzIHJlY2VudCBhbmQgbm90LXNvLXJlY2VudCBwYXBlcnMuIEkgdGhpbmsgY2l0
aW5nIHRoZW0gYW5kIGRpc2N1c3NpbmcgdGhlIGN1cnJlbnQgc3RhdGUgb2YgdGhpbmdzIGJyaWVm
bHkgaW4gdGhpcyBkcmFmdCBjb3VsZCBiZSBhIGdvb2QgaWRlYS48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_012C3117EDDB3C4781FD802A8C27DD4F4A3CC245SACEXCMBX02PRDh_--

