
From nobody Mon Feb  1 08:30:50 2016
Return-Path: <polina.goltsman@student.kit.edu>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50D001B3223 for <aqm@ietfa.amsl.com>; Mon,  1 Feb 2016 08:30:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bVdJmkDfFIk7 for <aqm@ietfa.amsl.com>; Mon,  1 Feb 2016 08:30:42 -0800 (PST)
Received: from scc-mailout-kit-02.scc.kit.edu (scc-mailout-kit-02.scc.kit.edu [IPv6:2a00:1398:9:f712::810d:e752]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7795B1B321F for <aqm@ietf.org>; Mon,  1 Feb 2016 08:30:42 -0800 (PST)
Received: from kit-msx-21.kit.edu ([2a00:1398:9:f612::21]) by scc-mailout-kit-02.scc.kit.edu with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (envelope-from <polina.goltsman@student.kit.edu>) id 1aQHN7-00055H-LA; Mon, 01 Feb 2016 17:30:39 +0100
Received: from [192.168.178.26] (84.179.109.186) by smtp.kit.edu (129.13.50.106) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Mon, 1 Feb 2016 17:30:37 +0100
To: Wesley Eddy <wes@mti-systems.com>, <aqm@ietf.org>
References: <20151127104351.5657.43384.idtracker@ietfa.amsl.com> <F3B0A07CFD358240926B78A680E166FF83E1D3@TW-MBX-P03.cnesnet.ad.cnes.fr> <565DF2D8.9010509@mti-systems.com> <56657C52.30300@student.kit.edu> <56A241B8.9040803@mti-systems.com>
From: Polina Goltsman <polina.goltsman@student.kit.edu>
Message-ID: <56AF8832.1010604@student.kit.edu>
Date: Mon, 1 Feb 2016 17:30:42 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56A241B8.9040803@mti-systems.com>
Content-Type: multipart/alternative; boundary="------------040208090202020001090700"
X-Originating-IP: [84.179.109.186]
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/x1vWXmX6i1yv-uhqGwURP_J65xo>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-eval-guidelines-09.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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2016 16:30:48 -0000

--------------040208090202020001090700
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit

Dear Wesley,

I apologize for the long delay. Below are responses to your emails 
regarding the draft-ietf-aqm-eval-guidelines.

------------------------------------------------------------------------

On 22.01.16 15:50, Wesley Eddy wrote:
> On 12/7/2015 7:32 AM, Polina Goltsman wrote:
>>
>> In the abstract, the document says that it describes characterization 
>> guidelines for an AQM proposal, to decide whether it should be 
>> adopted by the AQM WG. The WG currently has two AQMs 
>> (dropping/marking policy) in last call. Did someone evaluate these 
>> AQMs according to the specified guidelines?
>>
>
>
> In my opinion, for "standardization" it would be good to have crisp 
> guidelines.  For simply publishing RFCs that are experimental (not 
> standardized), it is much less important.
>
I have a question regarding "standardization". As I understand, no 
evaluation was performed based on these guidelines. Since the intended 
status of draft-ietf-aqm-eval-guidelines is "informational" too, this is 
also not an issue. Am I correct?
(see also an email from Dave Täht, quoted at the end of this email)
>
>> Moreover, it seems to me that the WG is about to conclude. What 
>> exactly is the purpose of standardizing this document then ?
>>
>
>
> It's definitely true that the activity level has been low, and so 
> we're trying to wrap up the outstanding work items before it flattens 
> completely.  This document is not proposed for standards track, only 
> "Informational".  The current goal as I see it (with co-chair hat on) 
> is to see if we have rough consensus that this is a useful 
> contribution to the community going forward, and that any small issues 
> can be addressed.
>
> As I understood your review (please correct if I'm wrong), a main 
> issue you see is that there isn't specific guidance about numeric 
> values or ranges to use in evaluations?  Nicolas explained why this 
> might be a bit difficult to do in general (and specific values 
> published in 2016 may be moot by 2018), so as I understand, one of the 
> limitations of this document is that it is only going to be able to 
> provide general descriptive guidance in terms of what kinds of tests 
> to run, and what types of things to look for, but not prescriptive 
> values and conditions to be met.  Do you think that's okay, even 
> though it's probably less directly useful than if there were specific 
> values

Yes, my concern was that the document did not contain enough detailed 
description of a test setup (capacities, RTT, etc). However, as Nicolas 
explained, the intention is that the test setup is selected by a tester  
for some specific environment. The results of an evaluation will then 
provide guidance for selecting an AQM for this specific environment. 
 From my point of view this is completely reasonable approach, however 
IMO  *the document should state this explicitly*.

 From answers to our (mine and Roland's) reviews we found out that the 
goals of the document are:

>We  believe that

>"

 >  AQM schemes need to be compared against both performance and

 >  deployment categories.

>"

(this one is present in the document in section 4.3)

>The main idea was to present the  available and useful metrics early

>in the document, so that the  tester can choose between them those that

>are of interest for the considered  scenario.

and finally

>The  scope of this document is to present how to assess the performance of 
AQMs – without focusing on a specific context ...
>...
>The unspecified  parameters do not require specific knowledge on AQMs – the unspecified 
parameters are (1) the RTT or the capacities, which are related to the 
network underneath; (2) and the characteristics of the traffic 
generation, which is related to the >traffic that is run between clients 
and servers.

(which I understand as stated above, correct me if I am wrong)
(this goal will be referred as [*] below)

Section 1.2 is intended to specify the goals of the document. I am not 
sure that everybody will understand the above stated goals from the text 
of Section 1.2. and the document would benefit if these goals were 
stated more explicitly (Well, I could not understand them without 
explanations from the authors).

------------------------------------------------------------------------

On 22.01.16 19:32, Klatsky, Carl wrote:
>
> Wes and all,
>
> My comment is in regard to Polina’s comment “The WG currently has two 
> AQMs (dropping/marking policy) in last call. Did someone evaluate 
> these AQMs according to the specified guidelines?”.  As I read over 
> draft-ietf-aqm-eval-guidelines, I did not think the objective of this 
> memo was to arrive at consensus to select one specific AQM.  I thought 
> the objective was to publish guidelines for implementers & service 
> providers on how they can select an AQM that is best for their 
> environment. And further that both AQMs in last call would complete 
> the process as valid AQMs for implementers & service providers as 
> available to use in their environment, with the guidelines helping 
> them to decide which is best for them. Some may chose PIE, some may 
> chose FQ_CODEL.  And possibly other future AQMs would go through the 
> IETF process for publication, and that would be an additional option 
> for implementers & service providers to evaluate according to the 
> guidelines as best for their environment.
>
> Is my understand of draft-ietf-aqm-eval-guidelines correct?
>
> Regards,
>
> Carl Klatsky
>
> Comcast
>
Again,  this is not what the document says. The document says (several 
times) that it is intended to be used by the AQM WG to evaluate 
proposals. If this (guidelines for the WG) is not the intended goal, 
then it is probably a good idea to remove this goal from the document.

------------------------------------------------------------------------

Next topic. Assuming that my understanding of the goals of the document 
(Section 1.2 + above) are correct, I find the following a little bit 
confusing.

1) The document does contain specific numbers in some scenarios, which, 
considering the goal [*], I find quite confusing ... . The RTTs in range 
[5ms-560ms] in Section 6 are, according to some TCP evaluation 
guidelines, currently seen RTTs in the Internet, where the latter is for 
satellite links, while the capacities "between 10Mbps an 100Mbps" in 
Section 8 are probably available Ethernet rates in range of available 
ADSL speeds. None of this makes sense if I decide to evaluate an AQM for 
a gigabit LAN in an office. So I think it might be a good idea to either 
introduce these numbers as "for example" and mentioning the setups for 
which these values are applicable (e.g., "for example the RTT range for 
general Internet is ...").

2) The document says:

> The guidelines also discuss methods to understand the
>  various aspects associated with safely deploying and operating the
>  AQM scheme.

I can't understand whether the document is intended to include 
requirements for an AQM specification document or not. Sections 8.3, 11, 
and 12 include requirements ("SHOULD") for an AQM proposal.

Since RFC7567 does not provide a recommendation in form of a list of 
what should be present in an AQM specification document, it might be a 
good idea to include this list in the eval-guidelines. However I suggest 
that these requirements be present as a separate section in the 
document, since AQM authors and testers are likely to be different people.

Moreover, since Sections 8.3, 11, and 12 include requirements for AQM 
proposals, what part of the document evaluates aspects associated with 
safe deployment of AQM? In particular:

Section 8.3 (stability analysis): an AQM proposal may or may not cover 
the particular test setup (capacity, RTT, etc), so the tester may need 
to specify whether their specific parameters are covered by an AQM 
proposal, and if not, perform the required analysis themselves.

Section 11 (implementation): AQM proposal SHOULD provide pseudocode. If 
the selected test setup includes specific device, then discussing 
device-specific implementation could be a part of an evaluation result. 
An AQM proposal cannot possibly discuss implementation on every 
available hardware.

(On the other hand, Section 12 requires to specify AQM parameters if 
they are not default, so it can be considered as an evaluation of safe 
deployment.)

3) Section 9.2 includes comments about DNS requests and SYN packets. I 
understand that this is a valid concern for an evaluation, but the 
scenarios in Section 9.2 do not evaluate this. I think it might be a 
good idea to provide a separate scenario with appropriate traffic mix 
and metrics, or, as a simpler solution, to discuss DNS and SYN packets 
in Section 2.2 - flow start-up metric.

4)  The document currently suggests using TCP congestion control 
according to RFC5681 with SACK. Is it even possible to use pure RFC5681 
on a real end-system? I think it might be a good idea to instead require 
that an implementation of a network stack on end hosts is disclosed in 
the evaluation results. For example, implementation of loss recovery can 
affect results and it may be not configurable: if I understand 
correctly, both proportional rate reduction (rfc6937) and a replacement 
for TCP ABC  cannot be turned off on Linux.

(the issue of network stack implementation on end-system is raised in 
*Yee-Ting Li, Douglas Leith, and Robert ******N. Shorten. 2007. 
Experimental evaluation of TCP protocols for****high-speed networks.)*

P.S. Is RFC5681 really NewReno and not Reno?

------------------------------------------------------------------------

On 22.01.16 15:52, Wesley Eddy wrote:
> With my co-chair hat on, I agree with this sentiment that it will 
> never be perfect.    To my knowledge, there aren't other resources 
> that have better information and guidance than this document when it 
> comes to the topic of characterizing AQMs.  The goal has been to 
> produce something useful to the community, compared to the current 
> guidance available (which is basically nothing), so I'm hopeful that 
> we can get a version of it with rough consensus to go forward.
I am not very familiar with the following topic, so if the following 
concerns are rubbish, please ignore them.

The sections for evaluating AQMs' performance (as opposed to deployment 
safety) can be divided into two groups: scenarios in sections 5 (except 
for 5.3), 6, 8, and 9.2 evaluate long-lived TCP flows, while scenarios 
in section 7 and 9.1 evaluate  traffic mixes including multimedia and 
web flows. There are several guidelines for evaluation of TCPs, some of 
which suggest evaluating TCP with AQM deployed. For eval-guidelines, 
they can be used as a source for additional information on how to choose 
and calculate metrics for the first group of scenarios. For the second 
group of scenarios, eval-guidelines  includes suggestion on how to 
generate "web-like" traffic and does not include suggestions on how to 
generate multimedia traffic. For both scenarios the document suggests 
using delay-throughput graph as well as "Metrics such as end-to-end 
latency, jitter, flow completion time MAY be generated" without 
suggesting particular metric for particular type of traffic (to my 
understanding, FCT does not make sense for a video stream and jitter for 
web flow).

Is there literature on how to generate and evaluate multimedia streams, 
including what metrics to choose and how to calculate them. Although 
there are some references in Section 2 (e.g., interval between 
consecutive losses), I think that the readers could benefit from 
additional references on the topic. Do I understand correctly that the 
universally accepted metric for web-flows is flow completion time?

------------------------------------------------------------------------

On 22.01.16 19:57, Dave Täht wrote:
> The evaluation guide needs to be executable, or rather, turned into
> public code and a standardized benchmark suite. Eventually.
>
> Iteratively, flent has many tests that have proven valuable and quite a
> few that have not.
>
> The tests in the aqm guide, need to be created, iterated on, and examined.
Totally agree. Implementing the tests for flent could be a perfect 
analogue for an "interoperability" test for these guidelines. Without 
any available result it is hard to say, whether the guidelines are 
useful or not.

Regards,
Polina






--------------040208090202020001090700
Content-Type: text/html; charset="windows-1252"
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Dear Wesley, <br>
    <br>
    I apologize for the long delay. Below are responses to your emails
    regarding the draft-ietf-aqm-eval-guidelines. <br>
    <br>
    <hr size="2" width="100%"><br>
    <div class="moz-cite-prefix">On 22.01.16 15:50, Wesley Eddy wrote:<br>
    </div>
    <blockquote cite="mid:56A241B8.9040803@mti-systems.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      On 12/7/2015 7:32 AM, Polina Goltsman wrote:<br>
      <blockquote cite="mid:56657C52.30300@student.kit.edu" type="cite">
        <br>
        In the abstract, the document says that it describes
        characterization guidelines for an AQM proposal, to decide
        whether it should be adopted by the AQM WG. The WG currently has
        two AQMs (dropping/marking policy) in last call. Did someone
        evaluate these AQMs according to the specified guidelines?<br>
        <br>
      </blockquote>
      <br>
      <br>
      In my opinion, for "standardization" it would be good to have
      crisp guidelines.  For simply publishing RFCs that are
      experimental (not standardized), it is much less important.<br>
      <br>
    </blockquote>
    I have a question regarding "standardization". As I understand, no
    evaluation was performed based on these guidelines. Since the
    intended status of draft-ietf-aqm-eval-guidelines is "informational"
    too, this is also not an issue. Am I correct?<br>
    (see also an email from Dave Täht, quoted at the end of this email)<br>
    <blockquote cite="mid:56A241B8.9040803@mti-systems.com" type="cite">
      <br>
      <blockquote cite="mid:56657C52.30300@student.kit.edu" type="cite">
        Moreover, it seems to me that the WG is about to conclude. What
        exactly is the purpose of standardizing this document then ?<br>
        <br>
      </blockquote>
      <br>
      <br>
      It's definitely true that the activity level has been low, and so
      we're trying to wrap up the outstanding work items before it
      flattens completely.  This document is not proposed for standards
      track, only "Informational".  The current goal as I see it (with
      co-chair hat on) is to see if we have rough consensus that this is
      a useful contribution to the community going forward, and that any
      small issues can be addressed.<br>
      <br>
      As I understood your review (please correct if I'm wrong), a main
      issue you see is that there isn't specific guidance about numeric
      values or ranges to use in evaluations?  Nicolas explained why
      this might be a bit difficult to do in general (and specific
      values published in 2016 may be moot by 2018), so as I understand,
      one of the limitations of this document is that it is only going
      to be able to provide general descriptive guidance in terms of
      what kinds of tests to run, and what types of things to look for,
      but not prescriptive values and conditions to be met.  Do you
      think that's okay, even though it's probably less directly useful
      than if there were specific values</blockquote>
    <br>
    Yes, my concern was that the document did not contain enough
    detailed description of a test setup (capacities, RTT, etc).
    However, as Nicolas explained, the intention is that the test setup
    is selected by a tester  for some specific environment. The results
    of an evaluation will then provide guidance for selecting an AQM for
    this specific environment. From my point of view this is completely
    reasonable approach, however IMO  *the document should state this
    explicitly*. <br>
    <br>
    From answers to our (mine and Roland's) reviews we found out that
    the goals of the document are:<br>
    <br>
    <meta charset="utf-8">
    <p dir="ltr"
      style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
      id="docs-internal-guid-db8b8049-8420-f0c0-26f1-ac4d3417d808"><span
style="font-size:14.666666666666666px;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">&gt;We
        believe that</span></p>
    <p dir="ltr"
      style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:14.666666666666666px;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">&gt;"</span></p>
    <p dir="ltr"
      style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:14.666666666666666px;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
        &gt;  AQM schemes need to be compared against both performance
        and</span></p>
    <p dir="ltr"
      style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:14.666666666666666px;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">
        &gt;  deployment categories.</span></p>
    <p dir="ltr"
      style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
style="font-size:14.666666666666666px;font-family:Arial;color:#000000;background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;">&gt;"</span></p>
    (this one is present in the document in section 4.3)<br>
    <br>
    <meta charset="utf-8">
    <p dir="ltr"
      style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"
      id="docs-internal-guid-db8b8049-8422-6661-b55a-ddf5a0910a1a"><span
        style="font-size: 14.6667px; font-family: Arial;
        background-color: transparent; font-weight: 400; font-style:
        normal; font-variant: normal; text-decoration: none;
        vertical-align: baseline;">&gt;The main idea was to present the
        available and useful metrics early</span></p>
    <p dir="ltr"
      style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span
        style="font-size: 14.6667px; font-family: Arial;
        background-color: transparent; font-weight: 400; font-style:
        normal; font-variant: normal; text-decoration: none;
        vertical-align: baseline;">&gt;in the document, so that the
        tester can choose between them those that</span></p>
    <span style="font-size: 14.6667px; font-family: Arial;
      background-color: transparent; font-weight: 400; font-style:
      normal; font-variant: normal; text-decoration: none;
      vertical-align: baseline;">&gt;are of interest for the considered
      scenario.</span><br>
    <br>
    and finally <br>
    <br>
    <span style="font-size: 11pt; font-family:
      &quot;Calibri&quot;,&quot;sans-serif&quot;;" lang="EN-US">&gt;The
      scope of this document is to present how to assess the performance
      of AQMs </span><span style="font-size: 11pt; font-family:
      &quot;Calibri&quot;,&quot;sans-serif&quot;;" lang="EN-US"> –
      without focusing on a specific context ...<br>
      <big>&gt;</big>...</span><br>
    <span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"
      lang="EN-US"> <font color="#000000">&gt;The unspecified
        parameters do not require specific knowledge on AQMs – the
        unspecified parameters are (1) the RTT or the capacities, which
        are related to the network underneath; (2) and the
        characteristics of the traffic generation, which is related to
        the &gt;traffic that is run between clients and servers. <br>
        <br>
        (which I understand as stated above, correct me if I am wrong)<br>
        (this goal will be referred as [*] below)<br>
      </font></span><br>
    Section 1.2 is intended to specify the goals of the document. I am
    not sure that everybody will understand the above stated goals from
    the text of Section 1.2. and the document would benefit if these
    goals were stated more explicitly (Well, I could not understand them
    without explanations from the authors).<br>
    <br>
    <hr size="2" width="100%"><br>
    <div class="moz-cite-prefix">On 22.01.16 19:32, Klatsky, Carl wrote:<br>
    </div>
    <blockquote
      cite="mid:ec9c9aa8b74b4ee7bc07f140d5555464@PACDCEX43.cable.comcast.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Wes
            and all,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">My
            comment is in regard to Polina’s comment “</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">The

            WG currently has two AQMs (dropping/marking policy) in last
            call. Did someone evaluate these AQMs according to the
            specified guidelines?”.  As I read over
            draft-ietf-aqm-eval-guidelines, I did not think the
            objective of this memo was to arrive at consensus to select
            one specific AQM.  I thought the objective was to publish
            guidelines for implementers &amp; service providers on how
            they can select an AQM that is best for their environment. 
            And further that both AQMs in last call would complete the
            process as valid AQMs for implementers &amp; service
            providers as available to use in their environment, with the
            guidelines helping them to decide which is best for them. 
            Some may chose PIE, some may chose FQ_CODEL.  And possibly
            other future AQMs would go through the IETF process for
            publication, and that would be an additional option for
            implementers &amp; service providers to evaluate according
            to the guidelines as best for their environment.<o:p></o:p></span>
        </p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Is
            my understand of draft-ietf-aqm-eval-guidelines correct?</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span>
        </p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p> </o:p></span></p>
        <div>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
          <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Carl
              Klatsky<o:p></o:p></span></p>
          <span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Comcast<o:p></o:p></span>
        </div>
        <br>
      </div>
    </blockquote>
    Again,  this is not what the document says. The document says
    (several times) that it is intended to be used by the AQM WG to
    evaluate proposals. If this (guidelines for the WG) is not the
    intended goal, then it is probably a good idea to remove this goal
    from the document.<br>
    <br>
    <hr size="2" width="100%"><br>
    Next topic. Assuming that my understanding of the goals of the
    document (Section 1.2 + above) are correct, I find the following a
    little bit confusing.<br>
    <br>
    1) The document does contain specific numbers in some scenarios,
    which, considering the goal [*], I find quite confusing ... . The
    RTTs in range [5ms-560ms] in Section 6 are, according to some TCP
    evaluation guidelines, currently seen RTTs in the Internet, where
    the latter is for satellite links, while the capacities "<span
      lang="EN-US">between 10Mbps an 100Mbps" in Section 8 are probably
      available Ethernet rates in range of available ADSL speeds. None
      of this makes sense if I decide to evaluate an AQM for a gigabit
      LAN in an office. So I think it might be a good idea to either
      introduce these numbers as "for example" and mentioning the setups
      for which these values are applicable (e.g., "for example the RTT
      range for general Internet is ...").<br>
      <br>
      2) The document says:</span><br>
    <pre class="newpage">&gt; The guidelines also discuss methods to understand the
&gt;  various aspects associated with safely deploying and operating the
&gt;  AQM scheme.
</pre>
    I can't understand whether the document is intended to include
    requirements for an AQM specification document or not. Sections 8.3,
    11, and 12 include requirements ("SHOULD") for an AQM proposal. <br>
    <br>
    Since RFC7567 does not provide a recommendation in form of a list of
    what should be present in an AQM specification document, it might be
    a good idea to include this list in the eval-guidelines. However I
    suggest that these requirements be present as a separate section in
    the document, since AQM authors and testers are likely to be
    different people.<br>
    <br>
    Moreover, since Sections 8.3, 11, and 12 include requirements for
    AQM proposals, what part of the document evaluates aspects
    associated with safe deployment of AQM? In particular:<br>
    <br>
    Section 8.3 (stability analysis): an AQM proposal may or may not
    cover the particular test setup (capacity, RTT, etc), so the tester
    may need to specify whether their specific parameters are covered by
    an AQM proposal, and if not, perform the required analysis
    themselves.<br>
    <br>
    Section 11 (implementation): AQM proposal SHOULD provide pseudocode.
    If the selected test setup includes specific device, then discussing
    device-specific implementation could be a part of an evaluation
    result. An AQM proposal cannot possibly discuss implementation on
    every available hardware.<br>
    <br>
    (On the other hand, Section 12 requires to specify AQM parameters if
    they are not default, so it can be considered as an evaluation of
    safe deployment.)<br>
    <br>
    3) Section 9.2 includes comments about DNS requests and SYN packets.
    I understand that this is a valid concern for an evaluation, but the
    scenarios in Section 9.2 do not evaluate this. I think it might be a
    good idea to provide a separate scenario with appropriate traffic
    mix and metrics, or, as a simpler solution, to discuss DNS and SYN
    packets in Section 2.2 - flow start-up metric.<br>
    <br>
    4)  The document currently suggests using TCP congestion control
    according to RFC5681 with SACK. Is it even possible to use pure
    RFC5681 on a real end-system? I think it might be a good idea to
    instead require that an implementation of a network stack on end
    hosts is disclosed in the evaluation results. For example,
    implementation of loss recovery can affect results and it may be not
    configurable: if I understand correctly, both proportional rate
    reduction (rfc6937) and a replacement for TCP ABC  cannot be turned
    off on Linux.<br>
    <br>
    (the issue of network stack implementation on end-system is raised
    in <b><span style="font-size: 14.6667px; background-color:
        transparent; font-weight: 400; font-style: normal; font-variant:
        normal; text-decoration: none; vertical-align: baseline;">Yee-Ting
        Li, Douglas Leith, and Robert </span></b><b><span
        style="font-size: 14.6667px; background-color: transparent;
        font-weight: 400; font-style: normal; font-variant: normal;
        text-decoration: none; vertical-align: baseline;"></span></b><b><span
        style="font-size: 14.6667px; background-color: transparent;
        font-weight: 400; font-style: normal; font-variant: normal;
        text-decoration: none; vertical-align: baseline;">    </span></b><b><span
        style="font-size: 14.6667px; background-color: transparent;
        font-weight: 400; font-style: normal; font-variant: normal;
        text-decoration: none; vertical-align: baseline;">N. Shorten.
        2007. Experimental evaluation of TCP protocols for</span></b><b><span
        style="font-size: 14.6667px; background-color: transparent;
        font-weight: 400; font-style: normal; font-variant: normal;
        text-decoration: none; vertical-align: baseline;"> </span></b><b><span
        style="font-size: 14.6667px; background-color: transparent;
        font-weight: 400; font-style: normal; font-variant: normal;
        text-decoration: none; vertical-align: baseline;">high-speed
        networks.)</span></b><br>
    <br>
    P.S. Is RFC5681 really NewReno and not Reno? <br>
    <br>
    <hr size="2" width="100%"><br>
    <div class="moz-cite-prefix">On 22.01.16 15:52, Wesley Eddy wrote:<br>
    </div>
    <blockquote cite="mid:56A24212.8030108@mti-systems.com" type="cite">With
      my co-chair hat on, I agree with this sentiment that it will never
      be perfect.    To my knowledge, there aren't other resources that
      have better information and guidance than this document when it
      comes to the topic of characterizing AQMs.  The goal has been to
      produce something useful to the community, compared to the current
      guidance available (which is basically nothing), so I'm hopeful
      that we can get a version of it with rough consensus to go
      forward.</blockquote>
    I am not very familiar with the following topic, so if the following
    concerns are rubbish, please ignore them. <br>
    <br>
    The sections for evaluating AQMs' performance (as opposed to
    deployment safety) can be divided into two groups: scenarios in
    sections 5 (except for 5.3), 6, 8, and 9.2 evaluate long-lived TCP
    flows, while scenarios in section 7 and 9.1 evaluate  traffic mixes
    including multimedia and web flows. There are several guidelines for
    evaluation of TCPs, some of which suggest evaluating TCP with AQM
    deployed. For eval-guidelines, they can be used as a source for
    additional information on how to choose and calculate metrics for
    the first group of scenarios. For the second group of scenarios,
    eval-guidelines  includes suggestion on how to generate "web-like"
    traffic and does not include suggestions on how to generate
    multimedia traffic. For both scenarios the document suggests using
    delay-throughput graph as well as "Metrics such as end-to-end
    latency, jitter, flow completion time MAY be generated" without
    suggesting particular metric for particular type of traffic (to my
    understanding, FCT does not make sense for a video stream and jitter
    for web flow).<br>
    <br>
    Is there literature on how to generate and evaluate multimedia
    streams, including what metrics to choose and how to calculate them.
    Although there are some references in Section 2 (e.g., interval
    between consecutive losses), I think that the readers could benefit
    from additional references on the topic. Do I understand correctly
    that the universally accepted metric for web-flows is flow
    completion time?<br>
    <br>
    <hr size="2" width="100%"><br>
    <div class="moz-cite-prefix">On 22.01.16 19:57, Dave Täht wrote:<br>
    </div>
    <blockquote cite="mid:56A27BAA.2080404@taht.net" type="cite">
      <pre wrap="">The evaluation guide needs to be executable, or rather, turned into
public code and a standardized benchmark suite. Eventually.

Iteratively, flent has many tests that have proven valuable and quite a
few that have not.

The tests in the aqm guide, need to be created, iterated on, and examined.</pre>
    </blockquote>
    Totally agree. Implementing the tests for flent could be a perfect
    analogue for an "interoperability" test for these guidelines.
    Without any available result it is hard to say, whether the
    guidelines are useful or not. <br>
    <br>
    Regards,<br>
    Polina<br>
    <br>
    <br>
    <br>
    <br>
    <br>
  </body>
</html>

--------------040208090202020001090700--


From nobody Tue Feb  2 07:09:52 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: aqm@ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ABCD01AC39E; Tue,  2 Feb 2016 07:09:51 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160202150951.20722.75936.idtracker@ietfa.amsl.com>
Date: Tue, 02 Feb 2016 07:09:51 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/7dsIOUxxaoBQe9WkVwdxY6JGV2Q>
Cc: aqm@ietf.org
Subject: [aqm] I-D Action: draft-ietf-aqm-eval-guidelines-10.txt
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 15:09:51 -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           : AQM Characterization Guidelines
        Authors         : Nicolas Kuhn
                          Preethi Natarajan
                          Naeem Khademi
                          David Ros
	Filename        : draft-ietf-aqm-eval-guidelines-10.txt
	Pages           : 35
	Date            : 2016-02-02

Abstract:
   Unmanaged large buffers in today's networks have given rise to a slew
   of performance issues.  These performance issues can be addressed by
   some form of Active Queue Management (AQM) mechanism, optionally in
   combination with a packet scheduling scheme such as fair queuing.
   This document describes various criteria for performing precautionary
   characterizations of AQM schemes.


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

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

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


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

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


From nobody Tue Feb  2 07:14:57 2016
Return-Path: <Nicolas.Kuhn@cnes.fr>
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 0B10A1B2C31 for <aqm@ietfa.amsl.com>; Tue,  2 Feb 2016 07:14:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.552
X-Spam-Level: 
X-Spam-Status: No, score=-1.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0uYu02bECJq7 for <aqm@ietfa.amsl.com>; Tue,  2 Feb 2016 07:14:53 -0800 (PST)
Received: from mx2.cnes.fr (mx2.cnes.fr [194.199.174.201]) by ietfa.amsl.com (Postfix) with ESMTP id 283101B2C35 for <aqm@ietf.org>; Tue,  2 Feb 2016 07:14:52 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.22,385,1449532800";  d="scan'208";a="1254608"
X-IPAS-Result: A2HpAgBTx7BW/wEBeApeGQEBAQEPAQEBAQYBAQEBgwBSbQaIU7FsAQ2BWwkXCoVsAoFEOBQBAQEBAQEBA3wLQRIBgWMhFxABAQEBAQEmAQEBAQEBIwI+LgEBAQMBAQFrGwIBBRAVHQcnCxQRAgQTCIgTDr5UAQEBAQYBAQEBARuOeIMrgQ8FjV2JFIVHiGF+SoN4gxqFOo4/HgEBQoNkPC6IHlEBewEBAQ
From: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
To: "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] I-D Action: draft-ietf-aqm-eval-guidelines-10.txt
Thread-Index: AQHRXcvUTJT9vby8/EO4wVMYxdBf9p8Y3Hyw
Date: Tue, 2 Feb 2016 15:14:50 +0000
Message-ID: <F3B0A07CFD358240926B78A680E166FF88C5B5@TW-MBX-P03.cnesnet.ad.cnes.fr>
References: <20160202150951.20722.75936.idtracker@ietfa.amsl.com>
In-Reply-To: <20160202150951.20722.75936.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tm-as-product-ver: SMEX-11.0.0.4179-8.000.1202-22108.000
x-tm-as-result: No--43.607500-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
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/t4vR7KOPrgo_0f_T2-FRPd2Rbr8>
Subject: [aqm] TR:  I-D Action: draft-ietf-aqm-eval-guidelines-10.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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 15:14:56 -0000

Dear all,=20

Following Polina's comments on the goals of the document that are not clear=
, we have clarified the link with the standardized algorithms and the goals=
 of the document.=20
Some highlights on the main changes:=20

"
   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Reducing the latency and maximizing the goodput . . . . .   5
     1.2.  Goals of this document  . . . . . . . . . . . . . . . . .   5

[...]

The goals of this document can thus be summarized as follows:

   o  The present characterization guidelines provide a non-exhaustive
      list of scenario to help ascertain whether an AQM is not only
      better than drop-tail (with BDP-sized buffer), but also safe to
      deploy;

   o  The present characterization guidelines (1) are not bound to a
      particular evaluation toolset and (2) can be used for various
      deployment scenarios;

   o  The present characterization guidelines provide guidance for
      better selecting an AQM for a specific environment; it is not
      required that an AQM proposal is evaluated following these
      guidelines for its standardization.
"

We hope that this clarifies the situation.=20
Kind regards,

Nicolas

-----Message d'origine-----
De=A0: aqm [mailto:aqm-bounces@ietf.org] De la part de internet-drafts@ietf=
.org
Envoy=E9=A0: mardi 2 f=E9vrier 2016 16:10
=C0=A0: i-d-announce@ietf.org
Cc=A0: aqm@ietf.org
Objet=A0: [aqm] I-D Action: draft-ietf-aqm-eval-guidelines-10.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Active Queue Management and Packet Schedu=
ling Working Group of the IETF.

        Title           : AQM Characterization Guidelines
        Authors         : Nicolas Kuhn
                          Preethi Natarajan
                          Naeem Khademi
                          David Ros
	Filename        : draft-ietf-aqm-eval-guidelines-10.txt
	Pages           : 35
	Date            : 2016-02-02

Abstract:
   Unmanaged large buffers in today's networks have given rise to a slew
   of performance issues.  These performance issues can be addressed by
   some form of Active Queue Management (AQM) mechanism, optionally in
   combination with a packet scheduling scheme such as fair queuing.
   This document describes various criteria for performing precautionary
   characterizations of AQM schemes.


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

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

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-aqm-eval-guidelines-10


Please note that it may take a couple of minutes from the time of submissio=
n 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 Thu Feb  4 06:30:05 2016
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 185F81B3046 for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 06:30:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_LOW=-0.7] 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 lvBBrTOmMK0k for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 06:30:02 -0800 (PST)
Received: from atl4mhob18.myregisteredsite.com (atl4mhob18.myregisteredsite.com [209.17.115.111]) by ietfa.amsl.com (Postfix) with ESMTP id 5419D1B3045 for <aqm@ietf.org>; Thu,  4 Feb 2016 06:30:02 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.209]) by atl4mhob18.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u14EU0WD047117 for <aqm@ietf.org>; Thu, 4 Feb 2016 09:30:00 -0500
Received: (qmail 16667 invoked by uid 0); 4 Feb 2016 14:30:00 -0000
X-TCPREMOTEIP: 65.189.201.79
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.104?) (wes@mti-systems.com@65.189.201.79) by 0 with ESMTPA; 4 Feb 2016 14:30:00 -0000
To: "aqm@ietf.org" <aqm@ietf.org>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56B36065.5050703@mti-systems.com>
Date: Thu, 4 Feb 2016 09:29:57 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/6xWGUd-TueMd4M1MhVwlDwwhAQI>
Subject: [aqm] status of WGLC on fq-codel
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 14:30:04 -0000

Hello, we started a working group last call for comments on this draft in December:
https://datatracker.ietf.org/doc/draft-ietf-aqm-fq-codel/
(this is the -03 version currently)

Some comments were received since then, and Toke updated the document:
https://kau.toke.dk/ietf/draft-ietf-aqm-fq-codel-04.html
(draft -04 version)

I think this update addresses all of the comments received.

I didn't see any feedback about document publication tracks (e.g. Standards Track, Informational, Experimental, etc).  We talked to the ADs briefly about this, and I think we are comfortable with Experimental for this document.  That is the appropriate track if the AQM working group thinks this is safe to deploy widely while experimenting with on the Internet (which I think is consistent with what section 7 describes -- it has already been widely deployed, though there are some items identified for future enquiry).  So, I think version -04 should be labelled with "Intended Status: Experimental".

My plan is to complete the shepherd writeup for this document in the next couple weeks, and if the editors push the -04 version of the draft, I think it will be ready to proceed for AD review.

Please shout if you have further comments.





From nobody Thu Feb  4 06:44:20 2016
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 0D0EF1B3090 for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 06:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 EANegwflfONz for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 06:44:16 -0800 (PST)
Received: from atl4mhob17.myregisteredsite.com (atl4mhob17.myregisteredsite.com [209.17.115.110]) by ietfa.amsl.com (Postfix) with ESMTP id 570811B3097 for <aqm@ietf.org>; Thu,  4 Feb 2016 06:44:16 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob17.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u14EiEg6009308 for <aqm@ietf.org>; Thu, 4 Feb 2016 09:44:14 -0500
Received: (qmail 7073 invoked by uid 0); 4 Feb 2016 14:44:14 -0000
X-TCPREMOTEIP: 65.189.201.79
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.104?) (wes@mti-systems.com@65.189.201.79) by 0 with ESMTPA; 4 Feb 2016 14:44:14 -0000
To: "aqm@ietf.org" <aqm@ietf.org>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56B363BC.2020705@mti-systems.com>
Date: Thu, 4 Feb 2016 09:44:12 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/2YH4gDRo9_VvdU-RAFSfPbe3jJU>
Subject: [aqm] status of codel WGLC
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 14:44:18 -0000

Hi, in December, we started a working group last call on:
https://datatracker.ietf.org/doc/draft-ietf-aqm-codel/
(the -02 version of the document)

A couple of small comments that I've seen since then, but don't think 
were addressed are in:
https://mailarchive.ietf.org/arch/msg/aqm/0NM0D2PtrF08XzTk5M9TLkkybyc

I think based on Dave's responses in that thread, they might be easy to 
address with simple editorial changes, but would like the editors to 
respond or post an update.

Also, the editors should take a quick look at the "idnits" output and 
fix a few errors/warnings (which should be easy):
https://www.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-aqm-codel-02.txt
- need a table of contents
- check the references

I didn't see any feedback about document publication tracks (e.g. 
Standards Track, Informational, Experimental, etc).  We talked to the 
ADs briefly about this, and I think we are comfortable with Experimental 
for this document.  That is the appropriate track if the AQM working 
group thinks this is safe to deploy widely while experimenting with on 
the Internet (which has been happening for quite some time already).  
So, I think version -04 should be labelled with "Intended Status: 
Experimental".

My plan is to complete the shepherd writeup for this document in the 
next couple weeks, and if the editors push the -03 version of the draft, 
I think it will be ready to proceed for AD review.

Please shout if you have further comments.


From nobody Thu Feb  4 09:22:42 2016
Return-Path: <jri@google.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 8F61A1A1A06 for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 09:22:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7By6zh9QUFm1 for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 09:22:39 -0800 (PST)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 001BF1A002C for <aqm@ietf.org>; Thu,  4 Feb 2016 09:22:38 -0800 (PST)
Received: by mail-ob0-x22e.google.com with SMTP id xk3so70842080obc.2 for <aqm@ietf.org>; Thu, 04 Feb 2016 09:22:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=z6mxF9aQ11c6QDqoIJ4bWlOzBXOLEamvn9EvgaA7Zp8=; b=V4kVVIClH/sAO80215pi4ec4Ts4n5dYBk48TqvVYG9aW9wBTDQcy5i9x64p6Nxf5EG 08a3ikGYu6JxA4N4Ucj4KvjGjVmp8UnNATB4e41VhjU7iSOb/okGRca62DIRI5FqlS+8 LWs8D+/hLK0BU9yWCh36IZRu5BWrFXMjf+EnxurK6JOwVGBQmzJ/R6HCk9f7WQMbtDTm bpwg9v185nHB9i6NKz1sL5oKuy5/cjfcWV7p9LIcPhOK8IifTC7wWRjHc8yBdOkjzmYD yaA8aLOShHmAfzwrq+haLHEN39Dkgp7BT9uSVYDqzK+Eb95r5kmDDzAxgD+DUjcbn9eP 8Akw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=z6mxF9aQ11c6QDqoIJ4bWlOzBXOLEamvn9EvgaA7Zp8=; b=UBgLd9UkAGctEM5nfSjL9k6W2A7Xkad2cdIr54oDxlxynp9l4IrxsiHrmdT55xYQH0 TL+wlaTRshnIV+J1d2ErCqP4AehqxUJNI5ENRqDQTZT11K+0HLvo2mMFJ0lwBBo9ZoIE 7Izb7hw1Y7ZRpkxPz8HYBfh40N0qG7xLJuq7NvX32wIrChmcvNUgycOlQduRJE6xmVGk atFWlG3SMITMlhxwAdGut3/nTv2oYifD8hys3Sgsm7K+1tXBvImfTDks+oNaiWAtp5UI 6N612s6pIwWD5X9Zqy/viHTGNt6/IjVvVmLZaY0go/r9ImBU9HRzdnZSw8/txYvyUPiN lJTA==
X-Gm-Message-State: AG10YOSFyrrhUdOP1Xbefl3oF4hkLG2jWCrAFUyhLwfogw3QCk354YZvykjY+/clNprbPXVAg094ksuMDBaSCS0a
MIME-Version: 1.0
X-Received: by 10.182.103.167 with SMTP id fx7mr8318895obb.36.1454606558266; Thu, 04 Feb 2016 09:22:38 -0800 (PST)
Received: by 10.76.3.79 with HTTP; Thu, 4 Feb 2016 09:22:38 -0800 (PST)
In-Reply-To: <56B363BC.2020705@mti-systems.com>
References: <56B363BC.2020705@mti-systems.com>
Date: Thu, 4 Feb 2016 09:22:38 -0800
Message-ID: <CAGD1bZbdDz350QoMvZDZsHym98XvXtb0NfMUQiRgCOR1O5nk7g@mail.gmail.com>
From: Jana Iyengar <jri@google.com>
To: Wesley Eddy <wes@mti-systems.com>
Content-Type: multipart/alternative; boundary=089e011602f831cfdf052af4fb59
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/mJolnwAA5_YTe2JzR1Gh3Rkp6uY>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] status of codel WGLC
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 17:22:40 -0000

--089e011602f831cfdf052af4fb59
Content-Type: text/plain; charset=UTF-8

Thanks Wes. We'll work on getting -03 out shortly.

- jana

On Thu, Feb 4, 2016 at 6:44 AM, Wesley Eddy <wes@mti-systems.com> wrote:

> Hi, in December, we started a working group last call on:
> https://datatracker.ietf.org/doc/draft-ietf-aqm-codel/
> (the -02 version of the document)
>
> A couple of small comments that I've seen since then, but don't think were
> addressed are in:
> https://mailarchive.ietf.org/arch/msg/aqm/0NM0D2PtrF08XzTk5M9TLkkybyc
>
> I think based on Dave's responses in that thread, they might be easy to
> address with simple editorial changes, but would like the editors to
> respond or post an update.
>
> Also, the editors should take a quick look at the "idnits" output and fix
> a few errors/warnings (which should be easy):
>
> https://www.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-aqm-codel-02.txt
> - need a table of contents
> - check the references
>
> I didn't see any feedback about document publication tracks (e.g.
> Standards Track, Informational, Experimental, etc).  We talked to the ADs
> briefly about this, and I think we are comfortable with Experimental for
> this document.  That is the appropriate track if the AQM working group
> thinks this is safe to deploy widely while experimenting with on the
> Internet (which has been happening for quite some time already).  So, I
> think version -04 should be labelled with "Intended Status: Experimental".
>
> My plan is to complete the shepherd writeup for this document in the next
> couple weeks, and if the editors push the -03 version of the draft, I think
> it will be ready to proceed for AD review.
>
> Please shout if you have further comments.
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>

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

<div dir=3D"ltr">Thanks Wes. We&#39;ll work on getting -03 out shortly.<div=
><br></div><div>- jana</div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Thu, Feb 4, 2016 at 6:44 AM, Wesley Eddy <span dir=3D"l=
tr">&lt;<a href=3D"mailto:wes@mti-systems.com" target=3D"_blank">wes@mti-sy=
stems.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, in D=
ecember, we started a working group last call on:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-aqm-codel/" rel=3D"n=
oreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-aq=
m-codel/</a><br>
(the -02 version of the document)<br>
<br>
A couple of small comments that I&#39;ve seen since then, but don&#39;t thi=
nk were addressed are in:<br>
<a href=3D"https://mailarchive.ietf.org/arch/msg/aqm/0NM0D2PtrF08XzTk5M9TLk=
kybyc" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.org/ar=
ch/msg/aqm/0NM0D2PtrF08XzTk5M9TLkkybyc</a><br>
<br>
I think based on Dave&#39;s responses in that thread, they might be easy to=
 address with simple editorial changes, but would like the editors to respo=
nd or post an update.<br>
<br>
Also, the editors should take a quick look at the &quot;idnits&quot; output=
 and fix a few errors/warnings (which should be easy):<br>
<a href=3D"https://www.ietf.org/tools/idnits?url=3Dhttps://www.ietf.org/arc=
hive/id/draft-ietf-aqm-codel-02.txt" rel=3D"noreferrer" target=3D"_blank">h=
ttps://www.ietf.org/tools/idnits?url=3Dhttps://www.ietf.org/archive/id/draf=
t-ietf-aqm-codel-02.txt</a><br>
- need a table of contents<br>
- check the references<br>
<br>
I didn&#39;t see any feedback about document publication tracks (e.g. Stand=
ards Track, Informational, Experimental, etc).=C2=A0 We talked to the ADs b=
riefly about this, and I think we are comfortable with Experimental for thi=
s document.=C2=A0 That is the appropriate track if the AQM working group th=
inks this is safe to deploy widely while experimenting with on the Internet=
 (which has been happening for quite some time already).=C2=A0 So, I think =
version -04 should be labelled with &quot;Intended Status: Experimental&quo=
t;.<br>
<br>
My plan is to complete the shepherd writeup for this document in the next c=
ouple weeks, and if the editors push the -03 version of the draft, I think =
it will be ready to proceed for AD review.<br>
<br>
Please shout if you have further comments.<br>
<br>
_______________________________________________<br>
aqm mailing list<br>
<a href=3D"mailto:aqm@ietf.org" target=3D"_blank">aqm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/aqm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/aqm</a><br>
</blockquote></div><br></div>

--089e011602f831cfdf052af4fb59--


From nobody Thu Feb  4 09:33:18 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: aqm@ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E7DE01A6F62; Thu,  4 Feb 2016 09:33:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160204173317.7367.52315.idtracker@ietfa.amsl.com>
Date: Thu, 04 Feb 2016 09:33:17 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/ZCfcSefDFZlIuUzu_vgESxbWtTU>
Cc: aqm@ietf.org
Subject: [aqm] I-D Action: draft-ietf-aqm-fq-codel-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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 17:33:18 -0000

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

        Title           : FlowQueue-Codel
        Authors         : Toke HÃ¸iland-JÃ¸rgensen
                          Paul McKenney
                          Dave Taht
                          Jim Gettys
                          Eric Dumazet
	Filename        : draft-ietf-aqm-fq-codel-04.txt
	Pages           : 19
	Date            : 2016-02-04

Abstract:
   This memo presents the FQ-CoDel hybrid packet scheduler/AQM
   algorithm, a powerful tool for fighting bufferbloat and reducing
   latency.

   FQ-CoDel mixes packets from multiple flows and reduces the impact of
   head of line blocking from bursty traffic.  It provides isolation for
   low-rate traffic such as DNS, web, and videoconferencing traffic.  It
   improves utilisation across the networking fabric, especially for
   bidirectional traffic, by keeping queue lengths short; and it can be
   implemented in a memory- and CPU-efficient fashion across a wide
   range of hardware.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-aqm-fq-codel-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-fq-codel-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 Thu Feb  4 10:33:29 2016
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 DE1FA1ACCED for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 10:33:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 FWnEsr0RAG-s for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 10:33:26 -0800 (PST)
Received: from atl4mhob19.myregisteredsite.com (atl4mhob19.myregisteredsite.com [209.17.115.112]) by ietfa.amsl.com (Postfix) with ESMTP id 9181C1ACCEA for <aqm@ietf.org>; Thu,  4 Feb 2016 10:33:26 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.210]) by atl4mhob19.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u14IXPip042898 for <aqm@ietf.org>; Thu, 4 Feb 2016 13:33:25 -0500
Received: (qmail 22039 invoked by uid 0); 4 Feb 2016 18:33:25 -0000
X-TCPREMOTEIP: 65.189.201.79
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.104?) (wes@mti-systems.com@65.189.201.79) by 0 with ESMTPA; 4 Feb 2016 18:33:25 -0000
To: aqm@ietf.org
References: <56A24463.9060100@mti-systems.com>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56B39972.5070400@mti-systems.com>
Date: Thu, 4 Feb 2016 13:33:22 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56A24463.9060100@mti-systems.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/d3GlEJnV15oQ9WhQhTKFXnLpcw0>
Subject: Re: [aqm] status of PIE drafts WGLC
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 18:33:29 -0000

Since none of the questions outstanding from WGLC seem to impact the 
DOCSIS PIE draft directly, I think that it is ready to move forward:
https://datatracker.ietf.org/doc/draft-ietf-aqm-docsis-pie/

Since it's describing what has already been done in DOCSIS, the 
Informational status seems appropriate, and consistent with other 
similar RFCs, so I think we're good there.

There are some small editorial nits found by "idnits" that we need to 
correct (add a security considerations section, add an IANA 
considerations section, and split references section into 
normative/informative):
https://www.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-aqm-docsis-pie-01.txt

I think that is all that needs to be done.




On 1/22/2016 10:01 AM, Wesley Eddy wrote:
> Hello; the working group last call on the PIE drafts generated some 
> emails, but I don't think I've seen any response from the editors. 
> Specifically, there were a couple of emails with algorithm description 
> questoins and technical comments from Rasool Al-Saadi and Ilpo 
> Jarvinen, both with specific points that should be addressed.
>
> For the most part, as I understand the comments, these are things that 
> can be relatively simply fixed up or the intent clarified, and not 
> catastrophic issues that would prevent the PIE docs from being 
> publishable.  Please correct me if I misunderstand though.
>
> If the editors can respond and work up a revision that addresses the 
> comments to the satisfaction of Rasool and Ilpo, I'd like to keep the 
> PIE documents moving forward.
>
>
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>
>


From nobody Thu Feb  4 15:26:35 2016
Return-Path: <g.white@CableLabs.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 E462B1B33F1 for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 15:26:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.234
X-Spam-Level: 
X-Spam-Status: No, score=0.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1yodzfxB18V9 for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 15:26:33 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id A6FA21B33F0 for <aqm@ietf.org>; Thu,  4 Feb 2016 15:26:33 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.7/8.14.7) with ESMTP id u14NQWAA013126; Thu, 4 Feb 2016 16:26:32 -0700
Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Thu, 04 Feb 2016 16:26:31 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com)
Received: from EXCHANGE.cablelabs.com ([::1]) by EXCHANGE.cablelabs.com ([::1]) with mapi id 14.03.0266.001; Thu, 4 Feb 2016 16:26:28 -0700
From: Greg White <g.white@CableLabs.com>
To: Wesley Eddy <wes@mti-systems.com>, "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] status of PIE drafts WGLC
Thread-Index: AQHRVSXaBtRWDHlp7kC75mCo06P1tZ8cwBoA///cj4A=
Date: Thu, 4 Feb 2016 23:26:28 +0000
Message-ID: <FFA5A6A6-1BEF-49A4-BF93-47E59900EB1F@cablelabs.com>
References: <56A24463.9060100@mti-systems.com> <56B39972.5070400@mti-systems.com>
In-Reply-To: <56B39972.5070400@mti-systems.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/0.0.0.160109
x-originating-ip: [10.4.11.75]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A6D7EC045E6341469921AFA7858433EB@cablelabs.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/aWSDILzthVntowGB9fAbWBbOcXM>
Subject: Re: [aqm] status of PIE drafts WGLC
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 23:26:35 -0000

VGhhbmtzIFdlcy4gIEkgc2hvdWxkIGJlIGFibGUgdG8gZ2V0IHRob3NlIHRha2VuIGNhcmUgb2Yg
aW4gdGhlIG5leHQgd2VlayBvciBzby4NCg0KLUdyZWcNCg0KDQoNCg0KT24gMi80LzE2LCAxMToz
MyBBTSwgImFxbSBvbiBiZWhhbGYgb2YgV2VzbGV5IEVkZHkiIDxhcW0tYm91bmNlc0BpZXRmLm9y
ZyBvbiBiZWhhbGYgb2Ygd2VzQG10aS1zeXN0ZW1zLmNvbT4gd3JvdGU6DQoNCj5TaW5jZSBub25l
IG9mIHRoZSBxdWVzdGlvbnMgb3V0c3RhbmRpbmcgZnJvbSBXR0xDIHNlZW0gdG8gaW1wYWN0IHRo
ZSANCj5ET0NTSVMgUElFIGRyYWZ0IGRpcmVjdGx5LCBJIHRoaW5rIHRoYXQgaXQgaXMgcmVhZHkg
dG8gbW92ZSBmb3J3YXJkOg0KPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0
LWlldGYtYXFtLWRvY3Npcy1waWUvDQo+DQo+U2luY2UgaXQncyBkZXNjcmliaW5nIHdoYXQgaGFz
IGFscmVhZHkgYmVlbiBkb25lIGluIERPQ1NJUywgdGhlIA0KPkluZm9ybWF0aW9uYWwgc3RhdHVz
IHNlZW1zIGFwcHJvcHJpYXRlLCBhbmQgY29uc2lzdGVudCB3aXRoIG90aGVyIA0KPnNpbWlsYXIg
UkZDcywgc28gSSB0aGluayB3ZSdyZSBnb29kIHRoZXJlLg0KPg0KPlRoZXJlIGFyZSBzb21lIHNt
YWxsIGVkaXRvcmlhbCBuaXRzIGZvdW5kIGJ5ICJpZG5pdHMiIHRoYXQgd2UgbmVlZCB0byANCj5j
b3JyZWN0IChhZGQgYSBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyBzZWN0aW9uLCBhZGQgYW4gSUFO
QSANCj5jb25zaWRlcmF0aW9ucyBzZWN0aW9uLCBhbmQgc3BsaXQgcmVmZXJlbmNlcyBzZWN0aW9u
IGludG8gDQo+bm9ybWF0aXZlL2luZm9ybWF0aXZlKToNCj5odHRwczovL3d3dy5pZXRmLm9yZy90
b29scy9pZG5pdHM/dXJsPWh0dHBzOi8vd3d3LmlldGYub3JnL2FyY2hpdmUvaWQvZHJhZnQtaWV0
Zi1hcW0tZG9jc2lzLXBpZS0wMS50eHQNCj4NCj5JIHRoaW5rIHRoYXQgaXMgYWxsIHRoYXQgbmVl
ZHMgdG8gYmUgZG9uZS4NCj4NCj4NCj4NCj4NCj5PbiAxLzIyLzIwMTYgMTA6MDEgQU0sIFdlc2xl
eSBFZGR5IHdyb3RlOg0KPj4gSGVsbG87IHRoZSB3b3JraW5nIGdyb3VwIGxhc3QgY2FsbCBvbiB0
aGUgUElFIGRyYWZ0cyBnZW5lcmF0ZWQgc29tZSANCj4+IGVtYWlscywgYnV0IEkgZG9uJ3QgdGhp
bmsgSSd2ZSBzZWVuIGFueSByZXNwb25zZSBmcm9tIHRoZSBlZGl0b3JzLiANCj4+IFNwZWNpZmlj
YWxseSwgdGhlcmUgd2VyZSBhIGNvdXBsZSBvZiBlbWFpbHMgd2l0aCBhbGdvcml0aG0gZGVzY3Jp
cHRpb24gDQo+PiBxdWVzdG9pbnMgYW5kIHRlY2huaWNhbCBjb21tZW50cyBmcm9tIFJhc29vbCBB
bC1TYWFkaSBhbmQgSWxwbyANCj4+IEphcnZpbmVuLCBib3RoIHdpdGggc3BlY2lmaWMgcG9pbnRz
IHRoYXQgc2hvdWxkIGJlIGFkZHJlc3NlZC4NCj4+DQo+PiBGb3IgdGhlIG1vc3QgcGFydCwgYXMg
SSB1bmRlcnN0YW5kIHRoZSBjb21tZW50cywgdGhlc2UgYXJlIHRoaW5ncyB0aGF0IA0KPj4gY2Fu
IGJlIHJlbGF0aXZlbHkgc2ltcGx5IGZpeGVkIHVwIG9yIHRoZSBpbnRlbnQgY2xhcmlmaWVkLCBh
bmQgbm90IA0KPj4gY2F0YXN0cm9waGljIGlzc3VlcyB0aGF0IHdvdWxkIHByZXZlbnQgdGhlIFBJ
RSBkb2NzIGZyb20gYmVpbmcgDQo+PiBwdWJsaXNoYWJsZS4gIFBsZWFzZSBjb3JyZWN0IG1lIGlm
IEkgbWlzdW5kZXJzdGFuZCB0aG91Z2guDQo+Pg0KPj4gSWYgdGhlIGVkaXRvcnMgY2FuIHJlc3Bv
bmQgYW5kIHdvcmsgdXAgYSByZXZpc2lvbiB0aGF0IGFkZHJlc3NlcyB0aGUgDQo+PiBjb21tZW50
cyB0byB0aGUgc2F0aXNmYWN0aW9uIG9mIFJhc29vbCBhbmQgSWxwbywgSSdkIGxpa2UgdG8ga2Vl
cCB0aGUgDQo+PiBQSUUgZG9jdW1lbnRzIG1vdmluZyBmb3J3YXJkLg0KPj4NCj4+DQo+Pg0KPj4g
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+IGFxbSBt
YWlsaW5nIGxpc3QNCj4+IGFxbUBpZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9hcW0NCj4+DQo+Pg0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+YXFtIG1haWxpbmcgbGlzdA0KPmFxbUBpZXRmLm9yZw0K
Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXFtDQo=


From nobody Thu Feb  4 16:55:51 2016
Return-Path: <ralsaadi@swin.edu.au>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA9B81B2B3A for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 16:55:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.197
X-Spam-Level: 
X-Spam-Status: No, score=-1.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VwR99O2R6v7c for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 16:55:48 -0800 (PST)
Received: from iport1.cc.swin.edu.au (iport1.cc.swin.edu.au [136.186.0.49]) by ietfa.amsl.com (Postfix) with ESMTP id A3D651B2B37 for <aqm@ietf.org>; Thu,  4 Feb 2016 16:55:47 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.22,398,1449493200"; d="scan'208";a="16993375"
Received: from gsp-ex01.ds.swin.edu.au (HELO outlook.swin.edu.au) ([136.186.126.17]) by iport1.cc.swin.edu.au with ESMTP; 05 Feb 2016 11:55:46 +1100
Received: from GSP-EX02.ds.swin.edu.au ([169.254.2.2]) by gsp-ex01.ds.swin.edu.au ([169.254.1.48]) with mapi id 14.03.0248.002; Fri, 5 Feb 2016 11:55:45 +1100
From: Rasool Al-Saadi <ralsaadi@swin.edu.au>
To: Wesley Eddy <wes@mti-systems.com>, "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] status of WGLC on fq-codel
Thread-Index: AQHRX1icJDxNBT5M1UmhxsCL9v/Lp58cnipQ
Date: Fri, 5 Feb 2016 00:55:45 +0000
Message-ID: <6545444AE21C2749939E637E56594CEA3C159109@gsp-ex02.ds.swin.edu.au>
References: <56B36065.5050703@mti-systems.com>
In-Reply-To: <56B36065.5050703@mti-systems.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.186.126.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/1bYjKQ9FMUxOio9azgDhW6Xxr_c>
Cc: Grenville Armitage <garmitage@swin.edu.au>
Subject: Re: [aqm] status of WGLC on fq-codel
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 00:55:49 -0000

Thanks Wesley.
fq_codel Internet draft- v4 addresses the question I raised and the text is=
 clear now. Also, I implemented fq_codel in FreeBSD based on the fq_codel I=
nternet draft- v04 and I got reasonable results.

Regards,
Rasool Al-Saadi

> -----Original Message-----
> From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Wesley Eddy
> Sent: Friday, 5 February 2016 1:30 AM
> To: aqm@ietf.org
> Subject: [aqm] status of WGLC on fq-codel
>=20
> Hello, we started a working group last call for comments on this draft in
> December:
> https://datatracker.ietf.org/doc/draft-ietf-aqm-fq-codel/
> (this is the -03 version currently)
>=20
> Some comments were received since then, and Toke updated the
> document:
> https://kau.toke.dk/ietf/draft-ietf-aqm-fq-codel-04.html
> (draft -04 version)
>=20
> I think this update addresses all of the comments received.
>=20
> I didn't see any feedback about document publication tracks (e.g. Standar=
ds
> Track, Informational, Experimental, etc).  We talked to the ADs briefly a=
bout
> this, and I think we are comfortable with Experimental for this document.
> That is the appropriate track if the AQM working group thinks this is saf=
e to
> deploy widely while experimenting with on the Internet (which I think is
> consistent with what section 7 describes -- it has already been widely
> deployed, though there are some items identified for future enquiry).  So=
, I
> think version -04 should be labelled with "Intended Status: Experimental"=
.
>=20
> My plan is to complete the shepherd writeup for this document in the next
> couple weeks, and if the editors push the -04 version of the draft, I thi=
nk it
> will be ready to proceed for AD review.
>=20
> Please shout if you have further comments.
>=20
>=20
>=20
>=20
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm


From nobody Thu Feb  4 17:19:14 2016
Return-Path: <dave@taht.net>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D4901B2BEA for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 17:19:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q17e8T3yyt7y for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 17:19:10 -0800 (PST)
Received: from mail.taht.net (mail.taht.net [IPv6:2a01:7e00::f03c:91ff:feae:7028]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A62991B2BEB for <aqm@ietf.org>; Thu,  4 Feb 2016 17:19:08 -0800 (PST)
Received: from dair-1120.lorna-side.hm.taht.net (c-73-252-201-217.hsd1.ca.comcast.net [73.252.201.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id 572451F466 for <aqm@ietf.org>; Fri,  5 Feb 2016 01:19:06 +0000 (UTC)
To: aqm@ietf.org
References: <56A24463.9060100@mti-systems.com> <56B39972.5070400@mti-systems.com>
From: =?UTF-8?Q?Dave_T=c3=a4ht?= <dave@taht.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B3F953.7000402@taht.net>
Date: Thu, 4 Feb 2016 17:22:27 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B39972.5070400@mti-systems.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/nuSnqAF6z-Yauu3fcK-JfVUp6-c>
Subject: [aqm] Experimental vs informational vs standards track
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 01:19:12 -0000

Dear wes:

Please take my name off the cc if you want your co's mail server to not
bounce my mail. the ietf's list mailer handles it fine.

On 2/4/16 10:33 AM, Wesley Eddy wrote:
> Since none of the questions outstanding from WGLC seem to impact the
> DOCSIS PIE draft directly, I think that it is ready to move forward:
> https://datatracker.ietf.org/doc/draft-ietf-aqm-docsis-pie/
> 
> Since it's describing what has already been done in DOCSIS, the
> Informational status seems appropriate, and consistent with other
> similar RFCs, so I think we're good there.

I do not really understand how this criterion promotes docsis-pie from
experimental to informational (or the reverse: demotes fq_codel from
informational to experimental, which happened this morning...

I realize now that there was a call as to what status it should be
a while.  I figured silence meant there was consensus on informational,
so I was a bit surprised when it was changed. You got my attention!

so, what criteria apply for experimental vs informational vs standards
track?

What blockers apply later, were, for example, another RFC to rely on an
experimental vs informational fq_codel rfc? For example, right now,
fq_codel is the defacto fq+aqm for homenet...

vs standards track?

No field data exists for docsis-pie. Most of the data on pie is from
sims.  Outside of the docsis standard I know of no deployments of pie
and no hardware support for it (please, someone? is there a roadmap from
any manufacturer with pie in it?).

and conversely, since the fq-codel draft describes what has already been
done in linux, deployed in systemd, openwrt, the edgerouter products (as
what it is), as part of more than a few other products, (rebranded),
inside several major cos, and with at least one well known deployed ISP...

...

I regarded fq_codel as experimental 4 years ago. it has survived the
test of time with no substantial changes. Certainly I'd like it to be
self tuning below 2.5mbits, but pie does badly there also without tuning.

...

As for declaring a "proposed standard", it seems as though pie's
standardization status itself has not yet been discussed on this list,
either.

My vote is for docis-pie, pie and fq_codel to have the same status,
whatever it winds up being. Informational seemed fine, across the board.
I'm all in favor of more deployment experience.



> 
> There are some small editorial nits found by "idnits" that we need to
> correct (add a security considerations section, add an IANA
> considerations section, and split references section into
> normative/informative):
> https://www.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-aqm-docsis-pie-01.txt
> 
> 
> I think that is all that needs to be done.
> 
> 
> 
> 
> On 1/22/2016 10:01 AM, Wesley Eddy wrote:
>> Hello; the working group last call on the PIE drafts generated some
>> emails, but I don't think I've seen any response from the editors.
>> Specifically, there were a couple of emails with algorithm description
>> questoins and technical comments from Rasool Al-Saadi and Ilpo
>> Jarvinen, both with specific points that should be addressed.
>>
>> For the most part, as I understand the comments, these are things that
>> can be relatively simply fixed up or the intent clarified, and not
>> catastrophic issues that would prevent the PIE docs from being
>> publishable.  Please correct me if I misunderstand though.
>>
>> If the editors can respond and work up a revision that addresses the
>> comments to the satisfaction of Rasool and Ilpo, I'd like to keep the
>> PIE documents moving forward.
>>
>>
>>
>> _______________________________________________
>> 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 Feb  4 17:26:50 2016
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 7D5261B2C1C for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 17:26:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 sxhbvb03x-Zy for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 17:26:48 -0800 (PST)
Received: from atl4mhob14.myregisteredsite.com (atl4mhob14.myregisteredsite.com [209.17.115.52]) by ietfa.amsl.com (Postfix) with ESMTP id 00C501B2C1B for <aqm@ietf.org>; Thu,  4 Feb 2016 17:26:47 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.203]) by atl4mhob14.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u151QkPr014767 for <aqm@ietf.org>; Thu, 4 Feb 2016 20:26:46 -0500
Received: (qmail 5604 invoked by uid 0); 5 Feb 2016 01:26:46 -0000
X-TCPREMOTEIP: 69.81.157.131
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.120?) (wes@mti-systems.com@69.81.157.131) by 0 with ESMTPA; 5 Feb 2016 01:26:46 -0000
To: aqm@ietf.org
References: <56A24463.9060100@mti-systems.com> <56B39972.5070400@mti-systems.com> <56B3F953.7000402@taht.net>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56B3FA52.2050104@mti-systems.com>
Date: Thu, 4 Feb 2016 20:26:42 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B3F953.7000402@taht.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/gpF2zGLElqhWH4sdtFxM8P1Rz7w>
Subject: Re: [aqm] Experimental vs informational vs standards track
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 01:26:49 -0000

On 2/4/2016 8:22 PM, Dave Täht wrote:
> I do not really understand how this criterion promotes docsis-pie from
> experimental to informational (or the reverse: demotes fq_codel from
> informational to experimental, which happened this morning...

Hi Dave, I'm not ignoring the rest of your message, but do need to 
correct one misconception first.

There is no higher or lower relationship between Informational and 
Experimental.

There is IESG explanation of the distinction here:
https://www.ietf.org/iesg/informational-vs-experimental.html



From nobody Thu Feb  4 17:30:18 2016
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 8B29D1B2C28 for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 17:30:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.898
X-Spam-Level: 
X-Spam-Status: No, score=0.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.793] 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 EO2l8zOi8vtZ for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 17:30:15 -0800 (PST)
Received: from atl4mhob21.registeredsite.com (unknown [209.17.115.115]) by ietfa.amsl.com (Postfix) with ESMTP id 4F6A31B2C1D for <aqm@ietf.org>; Thu,  4 Feb 2016 17:30:15 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob21.registeredsite.com (8.14.4/8.14.4) with ESMTP id u151UDpe101929 for <aqm@ietf.org>; Thu, 4 Feb 2016 20:30:13 -0500
Received: (qmail 13000 invoked by uid 0); 5 Feb 2016 01:30:13 -0000
X-TCPREMOTEIP: 69.81.157.131
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.120?) (wes@mti-systems.com@69.81.157.131) by 0 with ESMTPA; 5 Feb 2016 01:30:13 -0000
To: aqm@ietf.org
References: <56A24463.9060100@mti-systems.com> <56B39972.5070400@mti-systems.com> <56B3F953.7000402@taht.net> <56B3FA52.2050104@mti-systems.com>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56B3FB22.3080309@mti-systems.com>
Date: Thu, 4 Feb 2016 20:30:10 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B3FA52.2050104@mti-systems.com>
Content-Type: multipart/alternative; boundary="------------040208080403000505040100"
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/6g6nLkHY9iR4-Mc7JyH6K-1I70w>
Subject: Re: [aqm] Experimental vs informational vs standards track
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 01:30:16 -0000

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

On 2/4/2016 8:26 PM, Wesley Eddy wrote:
>
> There is IESG explanation of the distinction here:
> https://www.ietf.org/iesg/informational-vs-experimental.html
>

Quoting from that, I think this is the criteria that makes it most clear 
Informational is appropriate for DOCSIS-PIE:
"""

 1. If it's not going to be changed no matter what the result is, it's
    Informational. This is typically the case with vendor protocols; the
    vendor will publish it for the good of the community, but retains
    full change control, and gives no promises about listening to
    community feedback. Case in point: "Microsoft Point-To-Point
    Encryption (MPPE) Protocol" (RFC 3078).

"""

It's simply what was done elsewhere, and not going to be changed.  Greg 
was kind enough to write it up, and it's useful information for the 
community, so the WG had decided to put it forward as Informational.

Does that make sense?




--------------040208080403000505040100
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 2/4/2016 8:26 PM, Wesley Eddy wrote:<br>
    <blockquote cite="mid:56B3FA52.2050104@mti-systems.com" type="cite">
      <br>
      There is IESG explanation of the distinction here:
      <br>
      <a class="moz-txt-link-freetext" href="https://www.ietf.org/iesg/informational-vs-experimental.html">https://www.ietf.org/iesg/informational-vs-experimental.html</a>
      <br>
      <br>
    </blockquote>
    <br>
    Quoting from that, I think this is the criteria that makes it most
    clear Informational is appropriate for DOCSIS-PIE:<br>
    """<br>
    <ol class="text" style="color: rgb(0, 0, 0); font-family: Verdana,
      Arial, Helvetica, sans-serif; font-size: 12.6667px; font-style:
      normal; font-variant: normal; font-weight: normal; letter-spacing:
      normal; line-height: normal; orphans: auto; text-align: left;
      text-indent: 0px; text-transform: none; white-space: normal;
      widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      background-color: rgb(255, 255, 255);">
      <li>If it's not going to be changed no matter what the result is,
        it's Informational. This is typically the case with vendor
        protocols; the vendor will publish it for the good of the
        community, but retains full change control, and gives no
        promises about listening to community feedback. Case in point:
        "Microsoft Point-To-Point Encryption (MPPE) Protocol" (RFC
        3078).</li>
    </ol>
    <p>"""<br>
    </p>
    <p>It's simply what was done elsewhere, and not going to be
      changed.  Greg was kind enough to write it up, and it's useful
      information for the community, so the WG had decided to put it
      forward as Informational.<br>
    </p>
    <p>Does that make sense?<br>
      <br>
    </p>
    <p><br>
    </p>
    <br>
  </body>
</html>

--------------040208080403000505040100--


From nobody Thu Feb  4 18:14:45 2016
Return-Path: <dave@taht.net>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B93F91B2CE0 for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 18:14:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.602
X-Spam-Level: 
X-Spam-Status: No, score=-1.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id calvUtCL52sR for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 18:14:42 -0800 (PST)
Received: from mail.taht.net (mail.taht.net [176.58.107.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A15FE1B2CDD for <aqm@ietf.org>; Thu,  4 Feb 2016 18:14:42 -0800 (PST)
Received: from dair-1120.lorna-side.hm.taht.net (c-73-252-201-217.hsd1.ca.comcast.net [73.252.201.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id E4C8D1F466 for <aqm@ietf.org>; Fri,  5 Feb 2016 02:14:40 +0000 (UTC)
To: aqm@ietf.org
References: <56A24463.9060100@mti-systems.com> <56B39972.5070400@mti-systems.com> <56B3F953.7000402@taht.net> <56B3FA52.2050104@mti-systems.com> <56B3FB22.3080309@mti-systems.com>
From: =?UTF-8?Q?Dave_T=c3=a4ht?= <dave@taht.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B40659.9020002@taht.net>
Date: Thu, 4 Feb 2016 18:18:01 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B3FB22.3080309@mti-systems.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/YuTJFr22QPUdM79tK6Jag2Jpoho>
Subject: Re: [aqm] Experimental vs informational vs standards track
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 02:14:43 -0000

On 2/4/16 5:30 PM, Wesley Eddy wrote:
> On 2/4/2016 8:26 PM, Wesley Eddy wrote:
>>
>> There is IESG explanation of the distinction here:
>> https://www.ietf.org/iesg/informational-vs-experimental.html
>>
> 
> Quoting from that, I think this is the criteria that makes it most clear
> Informational is appropriate for DOCSIS-PIE:
> """
> 
>  1. If it's not going to be changed no matter what the result is, it's
>     Informational. This is typically the case with vendor protocols; the
>     vendor will publish it for the good of the community, but retains
>     full change control, and gives no promises about listening to
>     community feedback. Case in point: "Microsoft Point-To-Point
>     Encryption (MPPE) Protocol" (RFC 3078).
> 
> """
> 
> It's simply what was done elsewhere, and not going to be changed.  Greg
> was kind enough to write it up, and it's useful information for the
> community, so the WG had decided to put it forward as Informational.
> 
> Does that make sense?

Sure. I'm OK with informational status for docsis-pie.

But: It is roughly the same box that the Linux community would put
fq_codel in (at this point), if you consider them a "vendor".
Informational was the status of the draft for the past several years,
til it changed this morning.

Can you address the rest of my message? (notably: what effect does the
status of the document have on other standards that might rely on it?).

We've not discussed "Standards track" for fq_codel. By what criteria
would it qualify or not? I figured it was mostly blocked on an
implementation from the draft.

Pie itself is proposed as standards track, despite the lack of field
data, a 15 page criticism from bob briscoe of the public implementation,
and other open issues like that. Personally I've been waiting for an
actual modem to test on before bothering to explore more deeply results
from pie than we already have. (There is a study starting up soon where
I hope to finally A/B the stuff)

And:

I've only recently discovered the pain that "experimental" can cause
when other ietf standards are attempted to be layered on top of it (in
the nascent babel wg). It didn't sound like informational would cost the
same pain. Am I wrong in that assumption?


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


From nobody Thu Feb  4 18:50:42 2016
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 844241B2D8A for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 18:50:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 i6S7xPi_Ai92 for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 18:50:39 -0800 (PST)
Received: from atl4mhob19.myregisteredsite.com (atl4mhob19.myregisteredsite.com [209.17.115.112]) by ietfa.amsl.com (Postfix) with ESMTP id 6223F1B2D87 for <aqm@ietf.org>; Thu,  4 Feb 2016 18:50:39 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.209]) by atl4mhob19.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u152obS3044453 for <aqm@ietf.org>; Thu, 4 Feb 2016 21:50:37 -0500
Received: (qmail 13938 invoked by uid 0); 5 Feb 2016 02:50:37 -0000
X-TCPREMOTEIP: 69.81.157.131
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.120?) (wes@mti-systems.com@69.81.157.131) by 0 with ESMTPA; 5 Feb 2016 02:50:37 -0000
To: aqm@ietf.org
References: <56A24463.9060100@mti-systems.com> <56B39972.5070400@mti-systems.com> <56B3F953.7000402@taht.net>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56B40DFA.8060105@mti-systems.com>
Date: Thu, 4 Feb 2016 21:50:34 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B3F953.7000402@taht.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/qRPXa6BTgZgRpdvCE_mJ0jwjyJM>
Subject: Re: [aqm] Experimental vs informational vs standards track
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 02:50:41 -0000

Dave, here is a longer answer to your specific questions; I hope this 
helps calibrate where I'm coming from at least:


On 2/4/2016 8:22 PM, Dave Täht wrote:
> I realize now that there was a call as to what status it should be
> a while.  I figured silence meant there was consensus on informational,
> so I was a bit surprised when it was changed. You got my attention!

I think we had discussed focusing on document quality and collecting 
evaluations, test results, etc., and then when ready to publish each 
algorithm, deciding what document track to go on.

For the DOCSIS one, I'm pretty sure there was never any other option 
than Informational, since it was not something IETF was working on. I 
think it is similar in a way to RFC 6057, and others.


> so, what criteria apply for experimental vs informational vs standards
> track?

For Informational vs Experimental, there is the IESG statement:
https://www.ietf.org/iesg/informational-vs-experimental.html

For the relation with the standards track, I don't know anything that 
describes Experimental vs Standards Track outside of RFC 2026.

AQM's charter allows us to publish on the Standards Track.  I haven't 
seen very much push to do so, personally, and IMHO the standards track 
is not to be taken lightly.  If a lot of people say "yes, definitely, 
algorithm X should be on standards track, and we're comfortable with 
that", that will be convincing ... but the feedback is really light so far.


> What blockers apply later, were, for example, another RFC to rely on an
> experimental vs informational fq_codel rfc? For example, right now,
> fq_codel is the defacto fq+aqm for homenet...
>
> vs standards track?


I don't think there's really any distinction there.  For the IESG, 
Standards Track (or BCP) is definitely better to normatively reference 
from other documents going onto Standards Track, since otherwise the AD 
has to do explain and catalogue the "downref" for IETF Last Call.  
However, this is not uncommon, or very burdensome. There is a running 
list of downrefs, and once an RFC is on it, that can be referenced for 
future IETF LCs:
https://trac.tools.ietf.org/group/iesg/trac/wiki/DownrefRegistry


>
> No field data exists for docsis-pie. Most of the data on pie is from
> sims.  Outside of the docsis standard I know of no deployments of pie
> and no hardware support for it (please, someone? is there a roadmap from
> any manufacturer with pie in it?).

I don't know about this, but it sounds like a good reason why 
Informational and Experimental tracks would be preferable at the moment 
to Standards Track.


> and conversely, since the fq-codel draft describes what has already been
> done in linux, deployed in systemd, openwrt, the edgerouter products (as
> what it is), as part of more than a few other products, (rebranded),
> inside several major cos, and with at least one well known deployed ISP...
>
> ...
>
> I regarded fq_codel as experimental 4 years ago. it has survived the
> test of time with no substantial changes. Certainly I'd like it to be
> self tuning below 2.5mbits, but pie does badly there also without tuning.
>
> ...

I believe the Experimental vs Standards Track decision on FQ-CoDel is 
independent of anything to do with PIE.


> As for declaring a "proposed standard", it seems as though pie's
> standardization status itself has not yet been discussed on this list,
> either.

I also would like to see more discussion of what people want to do with 
these documents.  I've tried to be clear about my own thoughts.  As a 
chair, my default is to NOT go standards track unless there's explicit 
push from the working group.


> My vote is for docis-pie, pie and fq_codel to have the same status,
> whatever it winds up being. Informational seemed fine, across the board.
> I'm all in favor of more deployment experience.
>

Understood, though I'm doubtful that our publication track will impact 
deployment.  I believe we need to make the proper choice for each 
algorithm on its own merits, and not tie them together, personally.  
However, if the working group wants to keep everything at an even status 
though, please shout and tell us what that status is!





From nobody Thu Feb  4 18:58:41 2016
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 9E5391B2DB2 for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 18:58:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 BbY__E3qkhPF for <aqm@ietfa.amsl.com>; Thu,  4 Feb 2016 18:58:39 -0800 (PST)
Received: from atl4mhob07.myregisteredsite.com (atl4mhob07.myregisteredsite.com [209.17.115.45]) by ietfa.amsl.com (Postfix) with ESMTP id 52D121B2DB5 for <aqm@ietf.org>; Thu,  4 Feb 2016 18:58:39 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.207]) by atl4mhob07.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u152wcV8023286 for <aqm@ietf.org>; Thu, 4 Feb 2016 21:58:38 -0500
Received: (qmail 12059 invoked by uid 0); 5 Feb 2016 02:58:38 -0000
X-TCPREMOTEIP: 69.81.157.131
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.120?) (wes@mti-systems.com@69.81.157.131) by 0 with ESMTPA; 5 Feb 2016 02:58:37 -0000
To: aqm@ietf.org
References: <56A24463.9060100@mti-systems.com> <56B39972.5070400@mti-systems.com> <56B3F953.7000402@taht.net> <56B3FA52.2050104@mti-systems.com> <56B3FB22.3080309@mti-systems.com> <56B40659.9020002@taht.net>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56B40FDA.4090302@mti-systems.com>
Date: Thu, 4 Feb 2016 21:58:34 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B40659.9020002@taht.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/O1i2641BWRIYAX56SadFpTorKUw>
Subject: Re: [aqm] Experimental vs informational vs standards track
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 02:58:40 -0000

On 2/4/2016 9:18 PM, Dave Täht wrote:
> Pie itself is proposed as standards track, despite the lack of field
> data, a 15 page criticism from bob briscoe of the public implementation,
> and other open issues like that. Personally I've been waiting for an
> actual modem to test on before bothering to explore more deeply results
> from pie than we already have. (There is a study starting up soon where
> I hope to finally A/B the stuff)

Before going to the IESG, we need to make sure there is consensus on 
that publication track for PIE.  As you have seen, I'm trying to address 
that for each document as all of the technical WGLC comments are 
addressed and closed out.  I think the PIE editors would like Standards 
Track, if I understand correctly.  I do feel like the working group 
needs to speak up about whether they agree, because as a chair, I 
haven't heard much feedback about it.


> And:
>
> I've only recently discovered the pain that "experimental" can cause
> when other ietf standards are attempted to be layered on top of it (in
> the nascent babel wg). It didn't sound like informational would cost the
> same pain. Am I wrong in that assumption?

I'm not familiar with this case, but was on the IESG in the past, and am 
not aware of Experimental causing any real issues for layering or 
referencing in other standards.  This is simply called out in the IETF 
Last Call as a downref, recorded in the downref registry, and life goes 
on.  The running code doesn't care how the document is labelled either :)

IMHO, Standards Track carries more weight to say that there are no sharp 
corners, and the IETF is pretty sure this works well. Experimental is 
more cautious saying this looks pretty useful, and you should consider 
trying it out, but it might have some rough edges (e.g. like open 
research questions, identified in several of the AQM drafts).

Just my 2 cents.


From nobody Fri Feb  5 02:06:34 2016
Return-Path: <toke@toke.dk>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB4261B2D12 for <aqm@ietfa.amsl.com>; Fri,  5 Feb 2016 02:06:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.693
X-Spam-Level: 
X-Spam-Status: No, score=-0.693 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_DK=1.009, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5huyhPcPf2kI for <aqm@ietfa.amsl.com>; Fri,  5 Feb 2016 02:06:31 -0800 (PST)
Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AD391B2CB9 for <aqm@ietf.org>; Fri,  5 Feb 2016 02:06:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at mail2.tohojo.dk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1454666788; bh=80MgoaJEHqixjlnrotEwj9RA1IWnX2CeBBAN63OSPZs=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=KCU6RbN5HqsrBK55u6ZMDQggGG7aU2zo3mNfpU67FOxfZ+hF7VKSzJEm/hXqyoFtD Y9vWbXgeEU7GrPPvtInWogAxrUJCy40GREd0oPFQ9Mm48LYxyg/VRMe9cUJIdWgjcb LxJdNiwqD1XQH5EmaG/UhnFm7d7K07DGidnQXUcg=
Sender: toke@toke.dk
Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 5343D4FB0E; Fri,  5 Feb 2016 11:06:27 +0100 (CET)
From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
To: Wesley Eddy <wes@mti-systems.com>
References: <56A24463.9060100@mti-systems.com> <56B39972.5070400@mti-systems.com> <56B3F953.7000402@taht.net> <56B3FA52.2050104@mti-systems.com> <56B3FB22.3080309@mti-systems.com> <56B40659.9020002@taht.net> <56B40FDA.4090302@mti-systems.com>
Date: Fri, 05 Feb 2016 11:06:27 +0100
In-Reply-To: <56B40FDA.4090302@mti-systems.com> (Wesley Eddy's message of "Thu, 4 Feb 2016 21:58:34 -0500")
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87twlnxyho.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/qKg0PZFXHcoEysGYDbvrOWUE4Ss>
Cc: aqm@ietf.org
Subject: Re: [aqm] Experimental vs informational vs standards track
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 10:06:33 -0000

Wesley Eddy <wes@mti-systems.com> writes:

> IMHO, Standards Track carries more weight to say that there are no
> sharp corners, and the IETF is pretty sure this works well.
> Experimental is more cautious saying this looks pretty useful, and you
> should consider trying it out, but it might have some rough edges
> (e.g. like open research questions, identified in several of the AQM
> drafts).

Well, for the FQ-CoDel algorithm the caveats are more of the form
"fairness queueing in some cases have limitations", not "this particular
algorithm has limitations". So if we assume that people know what a
fairness queueing algorithm is, I think that FQ-CoDel can most certainly
be considered to "work well". I think the fact that it is now on *by
default* in a whole range of Linux distributions should attest to that.

-Toke


From nobody Fri Feb  5 06:55:34 2016
Return-Path: <polina.goltsman@student.kit.edu>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65F511B39F8 for <aqm@ietfa.amsl.com>; Fri,  5 Feb 2016 06:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level: 
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zrhof7cS7j3Z for <aqm@ietfa.amsl.com>; Fri,  5 Feb 2016 06:55:31 -0800 (PST)
Received: from scc-mailout-kit-01-web.scc.kit.edu (scc-mailout-kit-01-web.scc.kit.edu [IPv6:2a00:1398:9:f712::810d:e75d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AB591B39DB for <aqm@ietf.org>; Fri,  5 Feb 2016 06:55:31 -0800 (PST)
Received: from kit-msx-26.kit.edu ([2a00:1398:9:f612::26]) by scc-mailout-kit-01.scc.kit.edu with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (envelope-from <polina.goltsman@student.kit.edu>) id 1aRhnD-00085M-Gp; Fri, 05 Feb 2016 15:55:28 +0100
Received: from [192.168.178.25] (84.179.99.207) by smtp.kit.edu (129.13.50.106) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Fri, 5 Feb 2016 15:55:27 +0100
To: =?UTF-8?Q?Dave_T=c3=a4ht?= <dave@taht.net>, <aqm@ietf.org>
References: <56A24463.9060100@mti-systems.com> <56B39972.5070400@mti-systems.com> <56B3F953.7000402@taht.net> <56B3FA52.2050104@mti-systems.com> <56B3FB22.3080309@mti-systems.com> <56B40659.9020002@taht.net>
From: Polina Goltsman <polina.goltsman@student.kit.edu>
Message-ID: <56B4B7E3.3030304@student.kit.edu>
Date: Fri, 5 Feb 2016 15:55:31 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <56B40659.9020002@taht.net>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [84.179.99.207]
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/xCs03W38TbcNrOfZ6gBeW6vSrIw>
Subject: Re: [aqm] Experimental vs informational vs standards track
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 14:55:33 -0000

On 02/05/2016 03:18 AM, Dave Täht wrote:
> Pie itself is proposed as standards track, despite the lack of field
> data, a 15 page criticism from bob briscoe of the public implementation,
> and other open issues like that.
if "the public implementation" refers to Linux kernel module sch_pie, 
then it is no longer standard-conform

(http://www.ietf.org/mail-archive/web/aqm/current/msg01667.html, 
somewhere at the end)


From nobody Wed Feb 10 11:27:07 2016
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 D41151B2EF6 for <aqm@ietfa.amsl.com>; Wed, 10 Feb 2016 11:27:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 iK7ZkCNYKA0r for <aqm@ietfa.amsl.com>; Wed, 10 Feb 2016 11:27:04 -0800 (PST)
Received: from atl4mhob18.myregisteredsite.com (atl4mhob18.myregisteredsite.com [209.17.115.111]) by ietfa.amsl.com (Postfix) with ESMTP id 31C801B2EDB for <aqm@ietf.org>; Wed, 10 Feb 2016 11:27:04 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.203]) by atl4mhob18.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u1AJR3Gt046320 for <aqm@ietf.org>; Wed, 10 Feb 2016 14:27:03 -0500
Received: (qmail 26919 invoked by uid 0); 10 Feb 2016 19:27:03 -0000
X-TCPREMOTEIP: 65.189.201.79
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.104?) (wes@mti-systems.com@65.189.201.79) by 0 with ESMTPA; 10 Feb 2016 19:27:02 -0000
To: "aqm@ietf.org" <aqm@ietf.org>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56BB8F05.2030006@mti-systems.com>
Date: Wed, 10 Feb 2016 14:27:01 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/PjG4O_OObv-7ZHhIW9Py6Z_tkZE>
Subject: [aqm] AQM plans
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 19:27:06 -0000

Hello AQMers, this is just a quick note to be clear on working group 
status and forward planning.

Currently, all of the active drafts are either in WGLC, or in the 
process of shepherd writeups to go the the AD.

Once we get the current set of drafts out for publication, there are a 
few things the WG can do:
- close down
- remain open to continue coordinating and advance algorithms (e.g. 
within the standards track)
- remain open as a venue for potential new work (e.g. the DualQ Coupled AQM)

I think we should discuss this and plan to make a decision after the 
IETF 96 meeting in Berlin (July 17-22).  We can have a "closing or 
re-chartering" meeting in Berlin if it will benefit from face-to-face 
discussion.



From nobody Wed Feb 10 11:27:18 2016
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 91F251B2EFD for <aqm@ietfa.amsl.com>; Wed, 10 Feb 2016 11:27:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 Nveg9BITDI8i for <aqm@ietfa.amsl.com>; Wed, 10 Feb 2016 11:27:16 -0800 (PST)
Received: from atl4mhob19.myregisteredsite.com (atl4mhob19.myregisteredsite.com [209.17.115.112]) by ietfa.amsl.com (Postfix) with ESMTP id 74E2E1B2EFF for <aqm@ietf.org>; Wed, 10 Feb 2016 11:27:14 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.211]) by atl4mhob19.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u1AJRCHE042324 for <aqm@ietf.org>; Wed, 10 Feb 2016 14:27:12 -0500
Received: (qmail 12833 invoked by uid 0); 10 Feb 2016 19:27:12 -0000
X-TCPREMOTEIP: 65.189.201.79
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.104?) (wes@mti-systems.com@65.189.201.79) by 0 with ESMTPA; 10 Feb 2016 19:27:12 -0000
To: aqm@ietf.org
References: <56A24463.9060100@mti-systems.com>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56BB8F0F.7050007@mti-systems.com>
Date: Wed, 10 Feb 2016 14:27:11 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56A24463.9060100@mti-systems.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/kqK6Ut51piF4b1XiFHlqxfOwoKI>
Subject: Re: [aqm] status of PIE drafts WGLC
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 19:27:17 -0000

On 1/22/2016 10:01 AM, Wesley Eddy wrote:
> Hello; the working group last call on the PIE drafts generated some 
> emails, but I don't think I've seen any response from the editors. 
> Specifically, there were a couple of emails with algorithm description 
> questoins and technical comments from Rasool Al-Saadi and Ilpo 
> Jarvinen, both with specific points that should be addressed.
>
> For the most part, as I understand the comments, these are things that 
> can be relatively simply fixed up or the intent clarified, and not 
> catastrophic issues that would prevent the PIE docs from being 
> publishable.  Please correct me if I misunderstand though.
>
> If the editors can respond and work up a revision that addresses the 
> comments to the satisfaction of Rasool and Ilpo, I'd like to keep the 
> PIE documents moving forward.
>


To be clear also, I think at this stage, the feedback received from the 
working group isn't supporting Proposed Standard, and that the next 
update should be targeted "Experimental".   I can mark it that way in 
the datatracker, but can't edit the document header myself, and these 
need to be consistent before going to the IESG.

I've heard a couple other people seem to agree with going Experimental 
for the CoDel, FQ-CoDel, and PIE drafts and getting all three into the 
RFC Editor's hands sooner rather than later. (DOCSIS-PIE will be 
Informational.)  I've not yet heard folks saying that they really need a 
PS now and that PIE should be a PS now.

Definitely shout and correct me here if I'm wrong here, but I think this 
is the fastest path forward.





From nobody Wed Feb 10 12:15:51 2016
Return-Path: <Carl_Klatsky@cable.comcast.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 F0D471B2F60 for <aqm@ietfa.amsl.com>; Wed, 10 Feb 2016 12:15:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.234
X-Spam-Level: 
X-Spam-Status: No, score=0.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bktGR0QRy_IP for <aqm@ietfa.amsl.com>; Wed, 10 Feb 2016 12:15:48 -0800 (PST)
Received: from pacdcmhout01.cable.comcast.com (PACDCMHOUT01.cable.comcast.com [68.87.31.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9F841B2F63 for <aqm@ietf.org>; Wed, 10 Feb 2016 12:15:47 -0800 (PST)
X-AuditID: 44571fa7-f78ff6d00000187c-e9-56bb9a45da64
Received: from PACDCEX46.cable.comcast.com (cas-umc02.ndceast.pa.bo.comcast.net [68.87.34.28]) (using TLS with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by pacdcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id BF.9C.06268.54A9BB65; Wed, 10 Feb 2016 15:15:01 -0500 (EST)
Received: from PACDCEX43.cable.comcast.com (24.40.2.142) by PACDCEX46.cable.comcast.com (24.40.2.145) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Wed, 10 Feb 2016 15:14:00 -0500
Received: from PACDCEX43.cable.comcast.com ([fe80::3aea:a7ff:fe36:87a8]) by PACDCEX43.cable.comcast.com ([fe80::3aea:a7ff:fe36:87a8%19]) with mapi id 15.00.1130.005; Wed, 10 Feb 2016 15:14:00 -0500
From: "Klatsky, Carl" <Carl_Klatsky@cable.comcast.com>
To: 'Wesley Eddy' <wes@mti-systems.com>, "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] status of PIE drafts WGLC
Thread-Index: AQHRVSXeSNxlgLgHFk+EmI42gWBw5Z8mG5mA//+31UA=
Date: Wed, 10 Feb 2016 20:13:59 +0000
Message-ID: <f0ec2d997aab465786b259ce1649fe1a@PACDCEX43.cable.comcast.com>
References: <56A24463.9060100@mti-systems.com> <56BB8F0F.7050007@mti-systems.com>
In-Reply-To: <56BB8F0F.7050007@mti-systems.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [68.87.29.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGIsWRmVeSWpSXmKPExsXiEq4ko+s6a3eYwdJ5KhZr9klaXP/O7sDk sWTJTyaPk6d62QKYorhsUlJzMstSi/TtErgyTj/fz1bQJlwx9+le9gbG1fxdjJwcEgImElu3 X2CHsMUkLtxbz9bFyMUhJLCdSeLBlqtMEM4uRol5yxoYIZyTjBI3O1qBHA4ONgEziYd7/EG6 RQTcJM5cewQ2SVhAR+LlxNnMEHFdiTPPetkgbCuJvpl3WEBaWQRUJdrbnUHCvAJeEhvvPgYr ERIIllg0vQlsDKeAvsS+A//BbEag476fWsMEYjMLiEvcejKfCeJoAYkle84zQ9iiEi8f/2OF sA0kti7dB7ZKQkBe4uNcqFYdiQW7P7FB2NoSyxa+ZoY4QVDi5MwnLBCt4hKHj+xgncAoMQvJ tllI2mchaZ+FpH0BI8sqRrmCxOSU5NyM/NISA0O95MSknFS95Pzc5MTiEhC9iREce/LLdzDe e+F0iFGAg1GJhzeuf3eYEGtiWXFl7iFGCQ5mJRFehVqgEG9KYmVValF+fFFpTmrxIUZpDhYl cd7da/vChATSE0tSs1NTC1KLYLJMHJxSDYyTVXY+XvVpSe+iQJNnV36edTPybei8m+L3i6uH z1HcqSJ6KWfGuqkmVwN6W9gbI2/XxJ60WVX7prjM7ECcTNi/FbUtase//L5y+1nJ9HNOU08c 4X1rYNDrf+FHOUtaW3HThD+9W6Zwzb+jbPbDYHfMDm+Xb8L9monpsuwu9o120VrHX9ycc1uJ pTgj0VCLuag4EQAKxMZ6uQIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/yL2IdYNrMpWX9pyn04Zxf0TJ0Zg>
Subject: Re: [aqm] status of PIE drafts WGLC
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 20:15:50 -0000

Wes,

If the 'algorithm' drafts (CoDel, FQ-CoDel, and PIE) are targeted as Experi=
mental, does that mean at some time later their status moves onto either PS=
 (if real-world testing & use pans out) or Informational (if no activity fu=
rther proves it out but the authors want to keep the info out there for the=
 community)?  If so, how does that occur of the WG closes down?

Regards,

Carl Klatsky
Comcast
215-286-8256


-----Original Message-----
From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Wesley Eddy
Sent: Wednesday, February 10, 2016 2:27 PM
To: aqm@ietf.org
Subject: Re: [aqm] status of PIE drafts WGLC

On 1/22/2016 10:01 AM, Wesley Eddy wrote:
> Hello; the working group last call on the PIE drafts generated some=20
> emails, but I don't think I've seen any response from the editors.
> Specifically, there were a couple of emails with algorithm description=20
> questoins and technical comments from Rasool Al-Saadi and Ilpo=20
> Jarvinen, both with specific points that should be addressed.
>
> For the most part, as I understand the comments, these are things that=20
> can be relatively simply fixed up or the intent clarified, and not=20
> catastrophic issues that would prevent the PIE docs from being=20
> publishable.  Please correct me if I misunderstand though.
>
> If the editors can respond and work up a revision that addresses the=20
> comments to the satisfaction of Rasool and Ilpo, I'd like to keep the=20
> PIE documents moving forward.
>


To be clear also, I think at this stage, the feedback received from the wor=
king group isn't supporting Proposed Standard, and that the next=20
update should be targeted "Experimental".   I can mark it that way in=20
the datatracker, but can't edit the document header myself, and these need =
to be consistent before going to the IESG.

I've heard a couple other people seem to agree with going Experimental for =
the CoDel, FQ-CoDel, and PIE drafts and getting all three into the RFC Edit=
or's hands sooner rather than later. (DOCSIS-PIE will be
Informational.)  I've not yet heard folks saying that they really need a PS=
 now and that PIE should be a PS now.

Definitely shout and correct me here if I'm wrong here, but I think this is=
 the fastest path forward.




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


From nobody Wed Feb 10 12:26:33 2016
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 51AF11B2F7E for <aqm@ietfa.amsl.com>; Wed, 10 Feb 2016 12:26:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 n5WwUr3ks9iP for <aqm@ietfa.amsl.com>; Wed, 10 Feb 2016 12:26:31 -0800 (PST)
Received: from atl4mhob12.myregisteredsite.com (atl4mhob12.myregisteredsite.com [209.17.115.50]) by ietfa.amsl.com (Postfix) with ESMTP id ED05E1B2F7B for <aqm@ietf.org>; Wed, 10 Feb 2016 12:26:30 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.205]) by atl4mhob12.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u1AKQThl004616 for <aqm@ietf.org>; Wed, 10 Feb 2016 15:26:29 -0500
Received: (qmail 14320 invoked by uid 0); 10 Feb 2016 20:26:29 -0000
X-TCPREMOTEIP: 65.189.201.79
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.104?) (wes@mti-systems.com@65.189.201.79) by 0 with ESMTPA; 10 Feb 2016 20:26:29 -0000
To: "Klatsky, Carl" <Carl_Klatsky@cable.comcast.com>, "aqm@ietf.org" <aqm@ietf.org>
References: <56A24463.9060100@mti-systems.com> <56BB8F0F.7050007@mti-systems.com> <f0ec2d997aab465786b259ce1649fe1a@PACDCEX43.cable.comcast.com>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56BB9CF4.8080608@mti-systems.com>
Date: Wed, 10 Feb 2016 15:26:28 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <f0ec2d997aab465786b259ce1649fe1a@PACDCEX43.cable.comcast.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/HfJ-ilXCV9a-h5Li0avXueusIAg>
Subject: Re: [aqm] status of PIE drafts WGLC
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 20:26:32 -0000

On 2/10/2016 3:13 PM, Klatsky, Carl wrote:
> Wes,
>
> If the 'algorithm' drafts (CoDel, FQ-CoDel, and PIE) are targeted as Experimental, does that mean at some time later their status moves onto either PS (if real-world testing & use pans out) or Informational (if no activity further proves it out but the authors want to keep the info out there for the community)?  If so, how does that occur of the WG closes down?
>


If there's thrust to go Standards Track this can be done in a number of 
ways, mostly up to the discretion of the Area Directors:
1. done by AQM if it stays open longer-term
2. done by another relevant working group (e.g. TSVWG), if AQM is closed 
down
3. done by a re-incarnation of AQM working group (e.g. a PIE or CODEL 
working group)
4. done by "AD-sponsoring" of an update

In any case, the ADs need to be supportive of the path.

If for some reason any document needed to be deprecated, this could be 
done without the WG, and simply by marking as Obsolete in the RFC Editor 
database.  This would ideally be accompanied and requested by an RFC 
that describes what was found to be wrong, and what the impact is.

So ... in general, I think there's no real limitation imposed on the 
options of what can happen in the future.  However, things are 
definitely easier to do confidently when the working group is open and 
active, because consensus is simpler to judge.


From nobody Fri Feb 12 16:53:38 2016
Return-Path: <jri@google.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 6ECD01ACEA2 for <aqm@ietfa.amsl.com>; Fri, 12 Feb 2016 16:53:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Y4bnSEKbhQ3 for <aqm@ietfa.amsl.com>; Fri, 12 Feb 2016 16:53:34 -0800 (PST)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4AEC1ACE9E for <aqm@ietf.org>; Fri, 12 Feb 2016 16:53:34 -0800 (PST)
Received: by mail-ob0-x229.google.com with SMTP id gc3so44346700obb.3 for <aqm@ietf.org>; Fri, 12 Feb 2016 16:53:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=twgRIJBU2EWKLQKIAS7xOA2biYvoNXRNesJdYRXSbz4=; b=A8G5AWtXdyLmcvivKYvGU/r5EiVt4B8u3xAw2VCsmDs6Bw+esDxzC7uEjmNpDcr3Wl /gIaGshDSaFf62YLQ+4KXcQWNze3/oupNCJwi4i7aHNZQH5NdwTVnI8d5nGf5ukHsmdH tPWDwwjNCnjeT3olpZIJL/aYY+WS9tGHGIoIV43tDyX9FQrhbcp9UruxVRNZhYBuMwar AwyYkHLDzUdU7yH9Y5+pFa97NF4eMCJ8tUFfMAT/+5cUPtzEL3D/it56Ho/aUNOhKO3Q Bol0j1BtfO/7h9zJE5ry50vGTbqE1QIyYCmh/B213cHaN4yGaqccnR3baSgO7cucjtt7 gA8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=twgRIJBU2EWKLQKIAS7xOA2biYvoNXRNesJdYRXSbz4=; b=FuPKSQznR63lRtbWdus38Hm5pc7+QrfJeFpamWe6Gg1FA2gtyD5xIBDZ0uhPAg7Sxo tLy9t/14el8RxfB9mtJ5SgDDXcTcQJL/QqkS8owpJ102+MNNPqcuIDTmVmkQGbqjJVL5 2btNW8JN/uCkqT3Xdtz5a5x1i0RNiL5rK1ol2/Z37sr6SpacHaX6U0WNvlmXvLpqzLIi TvLk/3rJxyQ9kdVpTlGO61D+q/1sCo+wFw38bEbZkZGxPKaIXZGQ/ZpUdNnlDaN26ixI LMoT4AwUOpmzeAunzSjLsxH4VLpc4nDuauQ1zCzLfw4BjAf0tnJLZqEj5xZq3aX/KBH/ T8bQ==
X-Gm-Message-State: AG10YOSes1Qy8AZqRI+U5RJYOgJJCr6HIDh40i0aA230nniIwvXqsU7NY5sSj+9fhGDSULiU74ozyQUVBw1tJkDV
MIME-Version: 1.0
X-Received: by 10.182.110.193 with SMTP id ic1mr3905490obb.78.1455324814051; Fri, 12 Feb 2016 16:53:34 -0800 (PST)
Received: by 10.76.150.164 with HTTP; Fri, 12 Feb 2016 16:53:33 -0800 (PST)
In-Reply-To: <6545444AE21C2749939E637E56594CEA3C10FA8B@gsp-ex02.ds.swin.edu.au>
References: <6545444AE21C2749939E637E56594CEA3C10FA8B@gsp-ex02.ds.swin.edu.au>
Date: Fri, 12 Feb 2016 16:53:33 -0800
Message-ID: <CAGD1bZYtt6n9KR6zFoCsdPEySpo5=JRALZSr2hQGbKoDAmk6vA@mail.gmail.com>
From: Jana Iyengar <jri@google.com>
To: Rasool Al-Saadi <ralsaadi@swin.edu.au>
Content-Type: multipart/alternative; boundary=089e0112d06a9350ea052b9c3660
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/ygKGYFa4ZRn5wWe-l1etYDN2-Ig>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] An independent implementation of CoDel in FreeBSD/ipfw/dummynet
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Feb 2016 00:53:36 -0000

--089e0112d06a9350ea052b9c3660
Content-Type: text/plain; charset=UTF-8

Thanks much, Rasool, Grenville! And apologies for the late response. More
inline.

On Wed, Dec 16, 2015 at 3:35 AM, Rasool Al-Saadi <ralsaadi@swin.edu.au>
wrote:

> Hello all,
>
> I am Rasool Al-Saadi, a PhD student at Centre for Advanced Internet
> Architectures - Swinburne University of Technology. I and my supervisor
> Grenville Armitage are implementing CoDel (and eventually PIE, FQ_CoDel and
> FQ_PIE) in FreeBSD targeting ipfw/dummynet framework as a small project
> funded by Comcast Corporation, USA.
>
> We used CoDel I-D (https://datatracker.ietf.org/doc/draft-ietf-aqm-codel/)
> as the main source to implement CoDel and we believe that the information
> in the latest draft (draft-ietf-aqm-codel-02) sufficient and the
> pseudo-code is straightforward to create functional CoDel code. However, we
> have some questions/confusion regarding CoDel I-D:
>
> 1- There is little confusion in the text. In section 3.3, the text says
> "... the initial drop spacing SHOULD be set to the estimator's interval
> plus twice the target (i.e., initial drop spacing = 1.1 * interval) ...",
> while in section 4.1, the text says "As discussed in section 3.3, the
> initial next drop spacing is intended to be long enough to give the
> endpoints time to react to the single drop so SHOULD be set to a value of
> 1.0 to 1.1 times the interval."
>

I've changed the second occurrence to say "1.1 times the interval", to
avoid ambiguity.


> 2- In section 3.2 and 4.4, the text says the ideal setpoint is 5-10% of
> the interval (connection RTT). So, should we allow the user to specify the
> target value as a percentage of the interval or an absolute value?
>

While this is descriptive text, the recommendation in the draft is to use
5ms for Internet traffic. There's normative text in the same section that
says "Thus target SHOULD be set to 5ms for normal Internet traffic." I'm
leaving this text as is, unless you have a specific suggestion -- happy to
take it!

Thanks again for your careful read, and for your implementation work!
- jana


> Regards,
> Rasool
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
>

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

<div dir=3D"ltr">Thanks much, Rasool, Grenville! And apologies for the late=
 response. More inline.<div class=3D"gmail_extra"><br><div class=3D"gmail_q=
uote">On Wed, Dec 16, 2015 at 3:35 AM, Rasool Al-Saadi <span dir=3D"ltr">&l=
t;<a href=3D"mailto:ralsaadi@swin.edu.au" target=3D"_blank">ralsaadi@swin.e=
du.au</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204=
,204);border-left-style:solid;padding-left:1ex">Hello all,<br>
<br>
I am Rasool Al-Saadi, a PhD student at Centre for Advanced Internet Archite=
ctures - Swinburne University of Technology. I and my supervisor Grenville =
Armitage are implementing CoDel (and eventually PIE, FQ_CoDel and FQ_PIE) i=
n FreeBSD targeting ipfw/dummynet framework as a small project funded by Co=
mcast Corporation, USA.<br>
<br>
We used CoDel I-D (<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-a=
qm-codel/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.or=
g/doc/draft-ietf-aqm-codel/</a>) as the main source to implement CoDel and =
we believe that the information in the latest draft (draft-ietf-aqm-codel-0=
2) sufficient and the pseudo-code is straightforward to create functional C=
oDel code. However, we have some questions/confusion regarding CoDel I-D:<b=
r>
<br>
1- There is little confusion in the text. In section 3.3, the text says &qu=
ot;... the initial drop spacing SHOULD be set to the estimator&#39;s interv=
al plus twice the target (i.e., initial drop spacing =3D 1.1 * interval) ..=
.&quot;, while in section 4.1, the text says &quot;As discussed in section =
3.3, the initial next drop spacing is intended to be long enough to give th=
e endpoints time to react to the single drop so SHOULD be set to a value of=
 1.0 to 1.1 times the interval.&quot;<br></blockquote><div><br></div><div>I=
&#39;ve changed the second occurrence to say &quot;1.1 times the interval&q=
uot;, to avoid ambiguity.</div><div>=C2=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
2- In section 3.2 and 4.4, the text says the ideal setpoint is 5-10% of the=
 interval (connection RTT). So, should we allow the user to specify the tar=
get value as a percentage of the interval or an absolute value?<br></blockq=
uote><div><br></div><div>While this is descriptive text, the recommendation=
 in the draft is to use 5ms for Internet traffic. There&#39;s normative tex=
t in the same section that says &quot;Thus target SHOULD be set to 5ms for =
normal Internet traffic.&quot; I&#39;m leaving this text as is, unless you =
have a specific suggestion -- happy to take it!<br></div><div><br></div><di=
v>Thanks again for your careful read, and for your implementation work!</di=
v><div>- jana</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">
Regards,<br>
Rasool<br>
<br>
_______________________________________________<br>
aqm mailing list<br>
<a href=3D"mailto:aqm@ietf.org">aqm@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/aqm" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/aqm</a><br>
</blockquote></div><br></div></div>

--089e0112d06a9350ea052b9c3660--


From nobody Mon Feb 15 01:48:26 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: aqm@ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4719A1B2FC4; Mon, 15 Feb 2016 01:48:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160215094825.24357.56396.idtracker@ietfa.amsl.com>
Date: Mon, 15 Feb 2016 01:48:25 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/YreryPYbZdPAfHt9hqhpO8mt8YU>
Cc: aqm@ietf.org
Subject: [aqm] I-D Action: draft-ietf-aqm-eval-guidelines-11.txt
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2016 09:48:25 -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 of the IETF.

        Title           : AQM Characterization Guidelines
        Authors         : Nicolas Kuhn
                          Preethi Natarajan
                          Naeem Khademi
                          David Ros
	Filename        : draft-ietf-aqm-eval-guidelines-11.txt
	Pages           : 35
	Date            : 2016-02-15

Abstract:
   Unmanaged large buffers in today's networks have given rise to a slew
   of performance issues.  These performance issues can be addressed by
   some form of Active Queue Management (AQM) mechanism, optionally in
   combination with a packet scheduling scheme such as fair queuing.
   This document describes various criteria for performing precautionary
   characterizations of AQM schemes.


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

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

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


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

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


From nobody Mon Feb 15 01:52:38 2016
Return-Path: <Nicolas.Kuhn@cnes.fr>
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 EFAB61B2ACB for <aqm@ietfa.amsl.com>; Mon, 15 Feb 2016 01:52:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.557
X-Spam-Level: 
X-Spam-Status: No, score=-1.557 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xPvwQejb9Us0 for <aqm@ietfa.amsl.com>; Mon, 15 Feb 2016 01:52:35 -0800 (PST)
Received: from mx1.cnes.fr (mx1.cnes.fr [194.199.174.200]) by ietfa.amsl.com (Postfix) with ESMTP id 1A0A81B2BE9 for <aqm@ietf.org>; Mon, 15 Feb 2016 01:52:32 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.22,449,1449532800";  d="scan'208";a="1540471"
X-IPAS-Result: A2HmAwDknsFW/wUBeApeGQEBAQEPAQEBAQYBAQEBgwBSbQa6EwENgVsMFwqFaAICAoErOBQBAQEBAQEBA3wLgjchFxABAQEBAQEmAQEBAQEBIwI+LgEBAQMBAQFrGwIBBQMNFR0HJwsUEQIEEwiIEg68NQEBAQEGAQEBARyKRoQCEQEegyuBDwWNX4kahU+IZH5Kg3mDGoU7jj4eAQFCg2M8LodINAF7AQEB
From: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
To: "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] I-D Action: draft-ietf-aqm-eval-guidelines-11.txt
Thread-Index: AQHRZ9YI4WCwXWdYz0aari2WvIAa8Z8s3QQA
Date: Mon, 15 Feb 2016 09:52:28 +0000
Message-ID: <F3B0A07CFD358240926B78A680E166FF89BEBE@TW-MBX-P03.cnesnet.ad.cnes.fr>
References: <20160215094825.24357.56396.idtracker@ietfa.amsl.com>
In-Reply-To: <20160215094825.24357.56396.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tm-as-product-ver: SMEX-11.0.0.4179-8.000.1202-22132.006
x-tm-as-result: No--45.151000-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
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/cWIxCxCYfDtaB-CeMCRywwyHWM4>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-eval-guidelines-11.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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2016 09:52:38 -0000

All,

This updated version integrates some typos correction (based on Greg Skinne=
r's comment) and some reformulation in the "goal description section" based=
 on Polina's personal email.=20

Cheers,=20

Nico

-----Message d'origine-----
De=A0: aqm [mailto:aqm-bounces@ietf.org] De la part de internet-drafts@ietf=
.org
Envoy=E9=A0: lundi 15 f=E9vrier 2016 10:48
=C0=A0: i-d-announce@ietf.org
Cc=A0: aqm@ietf.org
Objet=A0: [aqm] I-D Action: draft-ietf-aqm-eval-guidelines-11.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the Active Queue Management and Packet Schedul=
ing of the IETF.

        Title           : AQM Characterization Guidelines
        Authors         : Nicolas Kuhn
                          Preethi Natarajan
                          Naeem Khademi
                          David Ros
	Filename        : draft-ietf-aqm-eval-guidelines-11.txt
	Pages           : 35
	Date            : 2016-02-15

Abstract:
   Unmanaged large buffers in today's networks have given rise to a slew
   of performance issues.  These performance issues can be addressed by
   some form of Active Queue Management (AQM) mechanism, optionally in
   combination with a packet scheduling scheme such as fair queuing.
   This document describes various criteria for performing precautionary
   characterizations of AQM schemes.


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

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

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-aqm-eval-guidelines-11


Please note that it may take a couple of minutes from the time of submissio=
n 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 Mon Feb 15 20:30:31 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: aqm@ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 835BF1B3323; Mon, 15 Feb 2016 20:30:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160216043029.9805.51183.idtracker@ietfa.amsl.com>
Date: Mon, 15 Feb 2016 20:30:29 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/nzNL-L5rhbBFbialuE-9tpQmVnM>
Cc: aqm@ietf.org
Subject: [aqm] I-D Action: draft-ietf-aqm-docsis-pie-02.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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2016 04:30:29 -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 of the IETF.

        Title           : A PIE-Based AQM for DOCSIS Cable Modems
        Authors         : Greg White
                          Rong Pan
	Filename        : draft-ietf-aqm-docsis-pie-02.txt
	Pages           : 15
	Date            : 2016-02-15

Abstract:
   Cable modems based on the DOCSIS(R) specification provide broadband
   Internet access to over one hundred million users worldwide.  In some
   cases, the cable modem connection is the bottleneck (lowest speed)
   link between the customer and the Internet.  As a result, the impact
   of buffering and bufferbloat in the cable modem can have a
   significant effect on user experience.  The CableLabs DOCSIS 3.1
   specification introduces requirements for cable modems to support an
   Active Queue Management (AQM) algorithm that is intended to alleviate
   the impact that buffering has on latency sensitive traffic, while
   preserving bulk throughput performance.  In addition, the CableLabs
   DOCSIS 3.0 specifications have also been amended to contain similar
   requirements.  This document describes the requirements on Active
   Queue Management that apply to DOCSIS equipment, including a
   description of the "DOCSIS-PIE" algorithm that is required on DOCSIS
   3.1 cable modems.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-aqm-docsis-pie-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-docsis-pie-02


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

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


From nobody Mon Feb 15 20:33:53 2016
Return-Path: <g.white@CableLabs.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 0C9041B3288 for <aqm@ietfa.amsl.com>; Mon, 15 Feb 2016 20:33:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.229
X-Spam-Level: 
X-Spam-Status: No, score=0.229 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEmW2KYSLkhN for <aqm@ietfa.amsl.com>; Mon, 15 Feb 2016 20:33:50 -0800 (PST)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id E12BE1ACDD3 for <aqm@ietf.org>; Mon, 15 Feb 2016 20:33:49 -0800 (PST)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.7/8.14.7) with ESMTP id u1G4XnTE003104; Mon, 15 Feb 2016 21:33:49 -0700
Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Mon, 15 Feb 2016 21:33:48 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com)
Received: from EXCHANGE.cablelabs.com ([::1]) by EXCHANGE.cablelabs.com ([::1]) with mapi id 14.03.0266.001; Mon, 15 Feb 2016 21:33:48 -0700
From: Greg White <g.white@CableLabs.com>
To: Wesley Eddy <wes@mti-systems.com>, "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] status of PIE drafts WGLC
Thread-Index: AQHRVSXaBtRWDHlp7kC75mCo06P1tZ8cwBoA///cj4CAEZ9+gA==
Date: Tue, 16 Feb 2016 04:33:48 +0000
Message-ID: <E8B5796F-100C-4E19-B235-06FE167F20D7@cablelabs.com>
References: <56A24463.9060100@mti-systems.com> <56B39972.5070400@mti-systems.com> <FFA5A6A6-1BEF-49A4-BF93-47E59900EB1F@cablelabs.com>
In-Reply-To: <FFA5A6A6-1BEF-49A4-BF93-47E59900EB1F@cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/0.0.0.160109
x-originating-ip: [10.5.0.27]
Content-Type: text/plain; charset="utf-8"
Content-ID: <7F430A2C0409F741BDDCAAF48E88CE5A@cablelabs.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/_SwST8_5wwnJJWvopGhDANgJ7d4>
Subject: Re: [aqm] status of PIE drafts WGLC
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2016 04:33:52 -0000

QSBuZXcgdmVyc2lvbiAoZHJhZnQtaWV0Zi1hcW0tZG9jc2lzLXBpZS0wMikgaGFzIGJlZW4gdXBs
b2FkZWQgdGhhdCBhZGRyZXNzZXMgdGhlIGlkbml0cy4NCg0KVGhhbmtzLA0KR3JlZw0KDQoNCg0K
DQoNCg0KDQpPbiAyLzQvMTYsIDQ6MjYgUE0sICJhcW0gb24gYmVoYWxmIG9mIEdyZWcgV2hpdGUi
IDxhcW0tYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2YgZy53aGl0ZUBDYWJsZUxhYnMuY29t
PiB3cm90ZToNCg0KPlRoYW5rcyBXZXMuICBJIHNob3VsZCBiZSBhYmxlIHRvIGdldCB0aG9zZSB0
YWtlbiBjYXJlIG9mIGluIHRoZSBuZXh0IHdlZWsgb3Igc28uDQo+DQo+LUdyZWcNCj4NCj4NCj4N
Cj4NCj5PbiAyLzQvMTYsIDExOjMzIEFNLCAiYXFtIG9uIGJlaGFsZiBvZiBXZXNsZXkgRWRkeSIg
PGFxbS1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiB3ZXNAbXRpLXN5c3RlbXMuY29tPiB3
cm90ZToNCj4NCj4+U2luY2Ugbm9uZSBvZiB0aGUgcXVlc3Rpb25zIG91dHN0YW5kaW5nIGZyb20g
V0dMQyBzZWVtIHRvIGltcGFjdCB0aGUgDQo+PkRPQ1NJUyBQSUUgZHJhZnQgZGlyZWN0bHksIEkg
dGhpbmsgdGhhdCBpdCBpcyByZWFkeSB0byBtb3ZlIGZvcndhcmQ6DQo+Pmh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtYXFtLWRvY3Npcy1waWUvDQo+Pg0KPj5TaW5j
ZSBpdCdzIGRlc2NyaWJpbmcgd2hhdCBoYXMgYWxyZWFkeSBiZWVuIGRvbmUgaW4gRE9DU0lTLCB0
aGUgDQo+PkluZm9ybWF0aW9uYWwgc3RhdHVzIHNlZW1zIGFwcHJvcHJpYXRlLCBhbmQgY29uc2lz
dGVudCB3aXRoIG90aGVyIA0KPj5zaW1pbGFyIFJGQ3MsIHNvIEkgdGhpbmsgd2UncmUgZ29vZCB0
aGVyZS4NCj4+DQo+PlRoZXJlIGFyZSBzb21lIHNtYWxsIGVkaXRvcmlhbCBuaXRzIGZvdW5kIGJ5
ICJpZG5pdHMiIHRoYXQgd2UgbmVlZCB0byANCj4+Y29ycmVjdCAoYWRkIGEgc2VjdXJpdHkgY29u
c2lkZXJhdGlvbnMgc2VjdGlvbiwgYWRkIGFuIElBTkEgDQo+PmNvbnNpZGVyYXRpb25zIHNlY3Rp
b24sIGFuZCBzcGxpdCByZWZlcmVuY2VzIHNlY3Rpb24gaW50byANCj4+bm9ybWF0aXZlL2luZm9y
bWF0aXZlKToNCj4+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvdG9vbHMvaWRuaXRzP3VybD1odHRwczov
L3d3dy5pZXRmLm9yZy9hcmNoaXZlL2lkL2RyYWZ0LWlldGYtYXFtLWRvY3Npcy1waWUtMDEudHh0
DQo+Pg0KPj5JIHRoaW5rIHRoYXQgaXMgYWxsIHRoYXQgbmVlZHMgdG8gYmUgZG9uZS4NCj4+DQo+
Pg0KPj4NCj4+DQo+Pk9uIDEvMjIvMjAxNiAxMDowMSBBTSwgV2VzbGV5IEVkZHkgd3JvdGU6DQo+
Pj4gSGVsbG87IHRoZSB3b3JraW5nIGdyb3VwIGxhc3QgY2FsbCBvbiB0aGUgUElFIGRyYWZ0cyBn
ZW5lcmF0ZWQgc29tZSANCj4+PiBlbWFpbHMsIGJ1dCBJIGRvbid0IHRoaW5rIEkndmUgc2VlbiBh
bnkgcmVzcG9uc2UgZnJvbSB0aGUgZWRpdG9ycy4gDQo+Pj4gU3BlY2lmaWNhbGx5LCB0aGVyZSB3
ZXJlIGEgY291cGxlIG9mIGVtYWlscyB3aXRoIGFsZ29yaXRobSBkZXNjcmlwdGlvbiANCj4+PiBx
dWVzdG9pbnMgYW5kIHRlY2huaWNhbCBjb21tZW50cyBmcm9tIFJhc29vbCBBbC1TYWFkaSBhbmQg
SWxwbyANCj4+PiBKYXJ2aW5lbiwgYm90aCB3aXRoIHNwZWNpZmljIHBvaW50cyB0aGF0IHNob3Vs
ZCBiZSBhZGRyZXNzZWQuDQo+Pj4NCj4+PiBGb3IgdGhlIG1vc3QgcGFydCwgYXMgSSB1bmRlcnN0
YW5kIHRoZSBjb21tZW50cywgdGhlc2UgYXJlIHRoaW5ncyB0aGF0IA0KPj4+IGNhbiBiZSByZWxh
dGl2ZWx5IHNpbXBseSBmaXhlZCB1cCBvciB0aGUgaW50ZW50IGNsYXJpZmllZCwgYW5kIG5vdCAN
Cj4+PiBjYXRhc3Ryb3BoaWMgaXNzdWVzIHRoYXQgd291bGQgcHJldmVudCB0aGUgUElFIGRvY3Mg
ZnJvbSBiZWluZyANCj4+PiBwdWJsaXNoYWJsZS4gIFBsZWFzZSBjb3JyZWN0IG1lIGlmIEkgbWlz
dW5kZXJzdGFuZCB0aG91Z2guDQo+Pj4NCj4+PiBJZiB0aGUgZWRpdG9ycyBjYW4gcmVzcG9uZCBh
bmQgd29yayB1cCBhIHJldmlzaW9uIHRoYXQgYWRkcmVzc2VzIHRoZSANCj4+PiBjb21tZW50cyB0
byB0aGUgc2F0aXNmYWN0aW9uIG9mIFJhc29vbCBhbmQgSWxwbywgSSdkIGxpa2UgdG8ga2VlcCB0
aGUgDQo+Pj4gUElFIGRvY3VtZW50cyBtb3ZpbmcgZm9yd2FyZC4NCj4+Pg0KPj4+DQo+Pj4NCj4+
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPj4+IGFx
bSBtYWlsaW5nIGxpc3QNCj4+PiBhcW1AaWV0Zi5vcmcNCj4+PiBodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2FxbQ0KPj4+DQo+Pj4NCj4+DQo+Pl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PmFxbSBtYWlsaW5nIGxpc3QNCj4+YXFt
QGlldGYub3JnDQo+Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXFtDQo+
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5hcW0gbWFp
bGluZyBsaXN0DQo+YXFtQGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9hcW0NCg==


From nobody Fri Feb 19 05:28:22 2016
Return-Path: <ietf@bobbriscoe.net>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ECD51B2EC2; Fri, 19 Feb 2016 05:28:18 -0800 (PST)
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_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W3tu7sovRIWN; Fri, 19 Feb 2016 05:28:15 -0800 (PST)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5ACBD1B2B1C; Fri, 19 Feb 2016 05:28:12 -0800 (PST)
Received: from 154.236.199.146.dyn.plus.net ([146.199.236.154]:56076 helo=[192.168.0.3]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86) (envelope-from <ietf@bobbriscoe.net>) id 1aWl6Q-00075F-14; Fri, 19 Feb 2016 13:28:10 +0000
To: tcpm IETF list <tcpm@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>, AQM IETF list <aqm@ietf.org>, TCP Prague List <tcpPrague@ietf.org>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <56C71869.9080503@bobbriscoe.net>
Date: Fri, 19 Feb 2016 13:28:09 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------090006030305010904050805"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/F6paStW6B2EC5LhXgIvA4VCRjmw>
Cc: "De Schepper, Koen \(Koen\)" <koen.de_schepper@nokia.com>
Subject: [aqm] (Bar) BoF @IETF-95 'Ultra-Low Queuing Delay for All' (L4S, DualQ Coupled AQM, TCP Prague)?
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2016 13:28:18 -0000

This is a multi-part message in MIME format.
--------------090006030305010904050805
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Folks,

I'm cross-posting 'cos this impacts 3 IETF WGs and interested implementers.

We would like to propose a Bar BoF at the Buenos Aires IETF, about L4S, 
DualQ and solutions to the TCP Prague Requirements.

If you don't know what all these buzzwords mean, pls read 'Background' 
at the end first.
If you don't know what a Bar BoF is, see https://www.ietf.org/tao.html

At least two purposes:
i) Updates so everyone can see progress on design, implementation, 
evaluation, specification of the different parts, who is working on what 
etc.
    Note: You might be working on, say, an improvement to DCTCP without 
being motivated by all this L4S stuff, but it might be relevant.
ii) To discuss how best to standardise all the different parts
iii) Anything else? Perhaps interop testing, but it's probably too early 
for that

Shout now, if you think this should be a real BoF, not just a Bar BoF, 
cos the deadline for BoF proposals is about 11 hrs from now: UTC 23:59 
2016-02-19 (Friday).
Also shout - either on or off list - if you have something relevant you 
would like to present at item (i)

Regarding item (ii) on how best to standardise all this, we've been 
talking with the Transport ADs and relevant WG chairs, and there are two 
possible routes forward:
* Proposal #1: Standardise the pieces in their relevant existing WGs. Ie:
   - the IP packet identifier for the L4S service in tsvwg, e.g. 
<draft-briscoe-tsvwg-ecn-l4s-id 
<https://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-l4s-id>>
   - the AQM mechanism in the aqm wg, e.g. 
<draft-briscoe-aqm-dualq-coupled 
<https://tools.ietf.org/html/draft-briscoe-aqm-dualq-coupled>>
   - The essential TCP Prague requirements 
<https://mailarchive.ietf.org/arch/msg/tcpprague/mwWncQg3egPd15FItYWiEvRDrvA> 
in the tcpm wg (the essential requirements happen to all be applicable 
to regular TCP congestion avoidance as well)
   - The 'optional' TCP Prague requirements 
<https://mailarchive.ietf.org/arch/msg/tcpprague/mwWncQg3egPd15FItYWiEvRDrvA> 
(performance improvements) in perhaps the IRTF iccrg or tcpm, whichever 
is most appropriate.
* Proposal #2: A new WG to do all the above.

Discuss!


*Background**
*Back in July'15, at the IETF AQM wg in Prague, we presented the DualQ 
Coupled AQM. <draft-briscoe-aqm-dualq-coupled 
<https://tools.ietf.org/html/draft-briscoe-aqm-dualq-coupled>>
And we demonstrated it later that week at IETF bits-n-bites exhibition.

The message is, once you partition off the queuing delay of 'Classic' 
TCP congestion control (Reno, Cubic, etc), it's really easy to get 
ultra-low queueing delay with the family of TCPs that includes Data 
Center TCP (DCTCP).

The DCTCP family is more aggressive, so normally they would starve a 
Classic TCP flow. This coexistence problem is why it hasn't so far been 
possible to release DCTCP on the public Internet.
The DualQ solves this coexistence problem. it is like a semi-permeable 
membrane: it partitions delay, but flows share bandwidth across the 
divide as if they are all the same type of TCP.
So, as a fortunate side-effect, DualQ also solves the problem of scaling 
TCP throughput long term. {Note 1}

We are proposing that senders will identify packets for this new L4S 
queue with the ECT(1) codepoint. <draft-briscoe-tsvwg-ecn-l4s-id 
<https://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-l4s-id>>
We call the service offered by this new queue 'L4S' for 'Low Delay, Low 
Loss, Scalable throughput'
DCTCP works OK as it is, but it will need some safety features. There 
was a lot of energy in an ad hoc session in Prague back last July, which 
produced a prioritised list, including performance improvements (see TCP 
Prague Requirements 
<https://mailarchive.ietf.org/arch/msg/tcpprague/mwWncQg3egPd15FItYWiEvRDrvA>) 
but then everyonr went home, went on summer holidays, returned to their 
day jobs and it all went quiet...

If you missed all the above, we've pulled together videos of demos, 
short papers, I-Ds etc here: https://riteproject.eu/dctth/
Incuding this particularly useful 2-pager: â€œUltra-Low Delay for All 
<http://www.internetsociety.org/publications/ietf-journal-november-2015/ultra-low-delay-for-all>â€� 
IETF Journal, Nov 2015.

Cheers


Bob Briscoe & Koen De Schepper

{Note 1} As the window scales, the number of congestion signals per RTT 
remains the same, whereas with classic TCPs it gets smaller.

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/


--------------090006030305010904050805
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Folks,<br>
    <br>
    I'm cross-posting 'cos this impacts 3 IETF WGs and interested
    implementers.<br>
    <br>
    We would like to propose a Bar BoF at the Buenos Aires IETF, about
    L4S, DualQ and solutions to the TCP Prague Requirements. <br>
    <br>
    If you don't know what all these buzzwords mean, pls read
    'Background' at the end first.<br>
    If you don't know what a Bar BoF is, see
    <a class="moz-txt-link-freetext" href="https://www.ietf.org/tao.html">https://www.ietf.org/tao.html</a><br>
    <br>
    At least two purposes:<br>
    i) Updates so everyone can see progress on design, implementation,
    evaluation, specification of the different parts, who is working on
    what etc.<br>
    Â Â  Note: You might be working on, say, an improvement to DCTCP
    without being motivated by all this L4S stuff, but it might be
    relevant.<br>
    ii) To discuss how best to standardise all the different parts<br>
    iii) Anything else? Perhaps interop testing, but it's probably too
    early for that<br>
    <br>
    Shout now, if you think this should be a real BoF, not just a Bar
    BoF, cos the deadline for BoF proposals is about 11 hrs from now:
    UTC 23:59 2016-02-19 (Friday).<br>
    Also shout - either on or off list - if you have something relevant
    you would like to present at item (i)<br>
    <br>
    Regarding item (ii) on how best to standardise all this, we've been
    talking with the Transport ADs and relevant WG chairs, and there are
    two possible routes forward:<br>
    * Proposal #1: Standardise the pieces in their relevant existing
    WGs. Ie:<br>
    Â  - the IP packet identifier for the L4S service in tsvwg, e.g. &lt;<a
      href="https://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-l4s-id">draft-briscoe-tsvwg-ecn-l4s-id</a>&gt;<br>
    Â  - the AQM mechanism in the aqm wg, e.g. &lt;<a
      href="https://tools.ietf.org/html/draft-briscoe-aqm-dualq-coupled">draft-briscoe-aqm-dualq-coupled</a>&gt;<br>
    Â  - The essential <a
href="https://mailarchive.ietf.org/arch/msg/tcpprague/mwWncQg3egPd15FItYWiEvRDrvA">TCP
      Prague requirements</a> in the tcpm wg (the essential requirements
    happen to all be applicable to regular TCP congestion avoidance as
    well)<br>
    Â  - The 'optional' <a
href="https://mailarchive.ietf.org/arch/msg/tcpprague/mwWncQg3egPd15FItYWiEvRDrvA">TCP
      Prague requirements</a> (performance improvements) in perhaps the
    IRTF iccrg or tcpm, whichever is most appropriate.<br>
    * Proposal #2: A new WG to do all the above.<br>
    <br>
    Discuss!<br>
    <br>
    <br>
    <b>Background</b><b><br>
    </b>Back in July'15, at the IETF AQM wg in Prague, we presented the
    DualQ Coupled AQM. &lt;<a
      href="https://tools.ietf.org/html/draft-briscoe-aqm-dualq-coupled">draft-briscoe-aqm-dualq-coupled</a>&gt;<br>
    And we demonstrated it later that week at IETF bits-n-bites
    exhibition.<br>
    <br>
    The message is, once you partition off the queuing delay of
    'Classic' TCP congestion control (Reno, Cubic, etc), it's really
    easy to get ultra-low queueing delay with the family of TCPs that
    includes Data Center TCP (DCTCP).<br>
    <br>
    The DCTCP family is more aggressive, so normally they would starve a
    Classic TCP flow. This coexistence problem is why it hasn't so far
    been possible to release DCTCP on the public Internet.<br>
    The DualQ solves this coexistence problem. it is like a
    semi-permeable membrane: it partitions delay, but flows share
    bandwidth across the divide as if they are all the same type of TCP.<br>
    So, as a fortunate side-effect, DualQ also solves the problem of
    scaling TCP throughput long term. {Note 1}<br>
    <br>
    We are proposing that senders will identify packets for this new L4S
    queue with the ECT(1) codepoint. &lt;<a
      href="https://tools.ietf.org/html/draft-briscoe-tsvwg-ecn-l4s-id">draft-briscoe-tsvwg-ecn-l4s-id</a>&gt;<br>
    We call the service offered by this new queue 'L4S' for 'Low Delay,
    Low Loss, Scalable throughput' <br>
    DCTCP works OK as it is, but it will need some safety features.
    There was a lot of energy in an ad hoc session in Prague back last
    July, which produced a prioritised list, including performance
    improvements (see <a
href="https://mailarchive.ietf.org/arch/msg/tcpprague/mwWncQg3egPd15FItYWiEvRDrvA">TCP
      Prague Requirements</a>) but then everyonr went home, went on
    summer holidays, returned to their day jobs and it all went quiet...<br>
    <br>
    If you missed all the above, we've pulled together videos of demos,
    short papers, I-Ds etc here: <a
      href="https://riteproject.eu/dctth/"><a class="moz-txt-link-freetext" href="https://riteproject.eu/dctth/">https://riteproject.eu/dctth/</a></a><br>
    Incuding this particularly useful 2-pager: â€œ<a
href="http://www.internetsociety.org/publications/ietf-journal-november-2015/ultra-low-delay-for-all">Ultra-Low
      Delay for All</a>â€� IETF Journal, Nov 2015.<br>
    <br>
    Cheers<br>
    <br>
    <br>
    Bob Briscoe &amp; Koen De Schepper<br>
    <br>
    {Note 1} As the window scales, the number of congestion signals per
    RTT remains the same, whereas with classic TCPs it gets smaller.<br>
    <pre class="moz-signature" cols="72">-- 
________________________________________________________________
Bob Briscoe                               <a class="moz-txt-link-freetext" href="http://bobbriscoe.net/">http://bobbriscoe.net/</a></pre>
  </body>
</html>

--------------090006030305010904050805--


From nobody Fri Feb 19 10:24:08 2016
Return-Path: <john@jlc.net>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFBBE1B2B05; Fri, 19 Feb 2016 10:24:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.206
X-Spam-Level: 
X-Spam-Status: No, score=-4.206 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006] 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 H-4ECxd_b1U4; Fri, 19 Feb 2016 10:24:04 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 377471ACE6C; Fri, 19 Feb 2016 10:24:04 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 69834C94BF; Fri, 19 Feb 2016 13:23:59 -0500 (EST)
Date: Fri, 19 Feb 2016 13:23:59 -0500
From: John Leslie <john@jlc.net>
To: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <20160219182359.GA74531@verdi>
References: <56C71869.9080503@bobbriscoe.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <56C71869.9080503@bobbriscoe.net>
User-Agent: Mutt/1.4.1i
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/bRe9OIkIo9bNSMQC2-vApYIooVs>
Cc: tcpm IETF list <tcpm@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>, AQM IETF list <aqm@ietf.org>, TCP Prague List <tcpPrague@ietf.org>, tsv-ads@ietf.org, "De Schepper, Koen \(Koen\)" <koen.de_schepper@nokia.com>
Subject: Re: [aqm] [tsvwg] (Bar) BoF @IETF-95 'Ultra-Low Queuing Delay for All' (L4S, DualQ Coupled AQM, TCP Prague)?
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2016 18:24:05 -0000

Bob Briscoe <ietf@bobbriscoe.net> wrote:
> 
> I'm cross-posting 'cos this impacts 3 IETF WGs and interested implementers.
> 
> We would like to propose a Bar BoF at the Buenos Aires IETF, about L4S, 
> DualQ and solutions to the TCP Prague Requirements.

   This feels like it belongs as a non-WG-forming formal BoF.

   It describes work spanning at least three WGs; and could benefit from
formal scheduling to avoid conflicts with those WGs and others.

   OTOH, it really isn't to the point where a WG charter can reasonably
be drafted. First we must decide whether the work _can_ be split among
existing WGs.

   However this may turn out, I wish to participate remotely.

--
John Leslie <john@jlc.net>


From nobody Mon Feb 22 00:54:17 2016
Return-Path: <ietf@bobbriscoe.net>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9FC91B2B6F; Mon, 22 Feb 2016 00:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H9LR2nYLJL4q; Mon, 22 Feb 2016 00:54:12 -0800 (PST)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AA8B1B2B32; Mon, 22 Feb 2016 00:54:12 -0800 (PST)
Received: from 238.28.198.146.dyn.plus.net ([146.198.28.238]:60114 helo=[192.168.0.3]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86) (envelope-from <ietf@bobbriscoe.net>) id 1aXmFu-0008GS-0W; Mon, 22 Feb 2016 08:54:10 +0000
To: John Leslie <john@jlc.net>
References: <56C71869.9080503@bobbriscoe.net> <20160219182359.GA74531@verdi>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <56CACCB1.2080502@bobbriscoe.net>
Date: Mon, 22 Feb 2016 08:54:09 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160219182359.GA74531@verdi>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/BgJTUOq1srkf_Xa7GpiDSYrRBbI>
Cc: tcpm IETF list <tcpm@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>, tsv-ads@ietf.org, TCP Prague List <tcpPrague@ietf.org>, "De Schepper, Koen \(Koen\)" <koen.de_schepper@nokia.com>, AQM IETF list <aqm@ietf.org>
Subject: Re: [aqm] [tcpPrague] [tsvwg] (Bar) BoF @IETF-95 'Ultra-Low Queuing Delay for All' (L4S, DualQ Coupled AQM, TCP Prague)?
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2016 08:54:16 -0000

John,

On 19/02/16 18:23, John Leslie wrote:
> Bob Briscoe <ietf@bobbriscoe.net> wrote:
>> I'm cross-posting 'cos this impacts 3 IETF WGs and interested implementers.
>>
>> We would like to propose a Bar BoF at the Buenos Aires IETF, about L4S,
>> DualQ and solutions to the TCP Prague Requirements.
>     This feels like it belongs as a non-WG-forming formal BoF.
>
>     It describes work spanning at least three WGs; and could benefit from
> formal scheduling to avoid conflicts with those WGs and others.
>
>     OTOH, it really isn't to the point where a WG charter can reasonably
> be drafted. First we must decide whether the work _can_ be split among
> existing WGs.
>
>     However this may turn out, I wish to participate remotely.
OK, we'll see if the secretariat can help us with that.
Unfortunately we ran out of time for the formal BoF deadline on Friday.


Bob

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

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/


From nobody Mon Feb 22 08:14:54 2016
Return-Path: <session_request_developers@ietf.org>
X-Original-To: aqm@ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D39BC1A923D; Wed, 17 Feb 2016 13:51:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Meeting Session Request Tool\"" <session_request_developers@ietf.org>
To: <session-request@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160217215156.28079.45493.idtracker@ietfa.amsl.com>
Date: Wed, 17 Feb 2016 13:51:56 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/lOThL5muql6rIt1aoeDs03kboRU>
X-Mailman-Approved-At: Mon, 22 Feb 2016 08:14:51 -0800
Cc: wes@mti-systems.com, mls.ietf@gmail.com, aqm-chairs@ietf.org, aqm@ietf.org
Subject: [aqm] aqm - Not having a session at IETF 95
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Feb 2016 21:51:57 -0000

Wesley Eddy, a chair of the aqm working group, indicated that the aqm working group does not plan to hold a session at IETF 95.

This message was generated and sent by the IETF Meeting Session Request Tool.



From nobody Mon Feb 22 09:21:32 2016
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CD2B1ACF19; Mon, 22 Feb 2016 09:21:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id adofOQvtrqQY; Mon, 22 Feb 2016 09:21:25 -0800 (PST)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F68B1A8796; Mon, 22 Feb 2016 09:21:25 -0800 (PST)
Received: by mail-yw0-x236.google.com with SMTP id u200so124504136ywf.0; Mon, 22 Feb 2016 09:21:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bHev+2W9a4ZjGp3R/8N28gupmZwanuXHCSwd0Hr0Kow=; b=QNWBbxUYD+769XYgmsT2Vj8DZkxf39GXopOKdgQ4PIkSWVRHHpsyodbqDaGpCd+liP /YRN9VYKe9lohGgN6oQCc0aQtaFcql1xDRcgI6PDbILwxQfXRW3vX7GLTuFuXzEqBQIP jzRPy8wOtU3ap5Z+MCj73WJmlKo8zHf35O/WJtyYIyLMdmZmAwEE1hXyodRPdWuV4J9k krfRG+u5WAB3PXhirxjBkM4pYGY9n78dH94ZbVc39JqhtYjcfN/7utlYtB37JrwEi9gq ks9IgczgfGNHdzRUfsN5tpIaqoohW8W3G++NscE0jG8iwQjXUkJrYV4YH7hQRBpjZuho ukKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=bHev+2W9a4ZjGp3R/8N28gupmZwanuXHCSwd0Hr0Kow=; b=S9mQDtHXdeRMbijQvAFQrtn3Vd1yBs22gG7V9SW3pSSyVux8CaYMZZTJi8X5HXxnxO fdOUETrkTf602KodKnRSFpvI9UgEAagKP4E89okyS4lQUqOIAONb8c8jmyJOue0Abwv1 cYYUTSfnk7V4cf9a//wdLLhHxm796FWzjrBNEhVIyRiVTxCRxYHNEKQJmc5aN0wsXK/k IOjWAlkS0AJ1A2CGBs9rznIpujQ+9mQb1E8bRtjHHp5wR98EvfnvGR9Yp4N/r2f+ggsh DduXNubavxzZcORvly865G5r/0ZugP/M3jcXhzyrSOh5WudkN+iSPfXMPWk8aSCj1MYI PsUQ==
X-Gm-Message-State: AG10YOTUqpNfTF2g6QCEbxUSXgEWUmQ7sBY/bX0gDCmyvXxIoHPu4npfVjKsKkMFdxKHQO+4txuPS/s+/+6g9w==
MIME-Version: 1.0
X-Received: by 10.13.210.7 with SMTP id u7mr14225566ywd.100.1456161684492; Mon, 22 Feb 2016 09:21:24 -0800 (PST)
Received: by 10.37.99.65 with HTTP; Mon, 22 Feb 2016 09:21:24 -0800 (PST)
In-Reply-To: <56CACCB1.2080502@bobbriscoe.net>
References: <56C71869.9080503@bobbriscoe.net> <20160219182359.GA74531@verdi> <56CACCB1.2080502@bobbriscoe.net>
Date: Mon, 22 Feb 2016 11:21:24 -0600
Message-ID: <CAKKJt-cE7xH9v+mZV=F-qntpkWggW0SUKY4HyYKyA0TOVZy59g@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Bob Briscoe <ietf@bobbriscoe.net>
Content-Type: multipart/alternative; boundary=001a114e7e78f0aa6b052c5f0fd5
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/4TFMRzTOosxrziqPVQ0XVsN5IgE>
Cc: tcpm IETF list <tcpm@ietf.org>, tsvwg IETF list <tsvwg@ietf.org>, John Leslie <john@jlc.net>, TCP Prague List <tcpPrague@ietf.org>, "tsv-ads@ietf.org" <tsv-ads@ietf.org>, AQM IETF list <aqm@ietf.org>, "De Schepper, Koen \(Koen\)" <koen.de_schepper@nokia.com>
Subject: Re: [aqm] [tcpPrague] [tsvwg] (Bar) BoF @IETF-95 'Ultra-Low Queuing Delay for All' (L4S, DualQ Coupled AQM, TCP Prague)?
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2016 17:21:29 -0000

--001a114e7e78f0aa6b052c5f0fd5
Content-Type: text/plain; charset=UTF-8

Just to try to be helpful ...

On Mon, Feb 22, 2016 at 2:54 AM, Bob Briscoe <ietf@bobbriscoe.net> wrote:

> John,
>
> On 19/02/16 18:23, John Leslie wrote:
>
>> Bob Briscoe <ietf@bobbriscoe.net> wrote:
>>
>>> I'm cross-posting 'cos this impacts 3 IETF WGs and interested
>>> implementers.
>>>
>>> We would like to propose a Bar BoF at the Buenos Aires IETF, about L4S,
>>> DualQ and solutions to the TCP Prague Requirements.
>>>
>>     This feels like it belongs as a non-WG-forming formal BoF.
>>
>>     It describes work spanning at least three WGs; and could benefit from
>> formal scheduling to avoid conflicts with those WGs and others.
>>
>>     OTOH, it really isn't to the point where a WG charter can reasonably
>> be drafted. First we must decide whether the work _can_ be split among
>> existing WGs.
>>
>>     However this may turn out, I wish to participate remotely.
>>
> OK, we'll see if the secretariat can help us with that.
>

I believe that happens at http://www.ietf.org/meeting/amreq.html. If you
put "TSV" in as "type of meeting", your happy TSV ADs would see the request.

Thanks,

Spencer


> Unfortunately we ran out of time for the formal BoF deadline on Friday.
>
>
> Bob
>
>
>> --
>> John Leslie <john@jlc.net>
>>
>> _______________________________________________
>> tcpPrague mailing list
>> tcpPrague@ietf.org
>> https://www.ietf.org/mailman/listinfo/tcpprague
>>
>
> --
> ________________________________________________________________
> Bob Briscoe                               http://bobbriscoe.net/
>
>

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

<div dir=3D"ltr">Just to try to be helpful ...<div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Mon, Feb 22, 2016 at 2:54 AM, Bob Briscoe <=
span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@bobbriscoe.net" target=3D"_blan=
k">ietf@bobbriscoe.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">John,<span=
 class=3D""><br>
<br>
On 19/02/16 18:23, John Leslie wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
Bob Briscoe &lt;<a href=3D"mailto:ietf@bobbriscoe.net" target=3D"_blank">ie=
tf@bobbriscoe.net</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
I&#39;m cross-posting &#39;cos this impacts 3 IETF WGs and interested imple=
menters.<br>
<br>
We would like to propose a Bar BoF at the Buenos Aires IETF, about L4S,<br>
DualQ and solutions to the TCP Prague Requirements.<br>
</blockquote>
=C2=A0 =C2=A0 This feels like it belongs as a non-WG-forming formal BoF.<br=
>
<br>
=C2=A0 =C2=A0 It describes work spanning at least three WGs; and could bene=
fit from<br>
formal scheduling to avoid conflicts with those WGs and others.<br>
<br>
=C2=A0 =C2=A0 OTOH, it really isn&#39;t to the point where a WG charter can=
 reasonably<br>
be drafted. First we must decide whether the work _can_ be split among<br>
existing WGs.<br>
<br>
=C2=A0 =C2=A0 However this may turn out, I wish to participate remotely.<br=
>
</blockquote></span>
OK, we&#39;ll see if the secretariat can help us with that.<br></blockquote=
><div><br></div><div>I believe that happens at=C2=A0<a href=3D"http://www.i=
etf.org/meeting/amreq.html">http://www.ietf.org/meeting/amreq.html</a>. If =
you put &quot;TSV&quot; in as &quot;type of meeting&quot;, your happy TSV A=
Ds would see the request.</div><div><br></div><div>Thanks,</div><div><br></=
div><div>Spencer</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb=
(204,204,204);border-left-style:solid;padding-left:1ex">
Unfortunately we ran out of time for the formal BoF deadline on Friday.<spa=
n class=3D""><font color=3D"#888888"><br>
<br>
<br>
Bob<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<br>
--<br>
John Leslie &lt;<a href=3D"mailto:john@jlc.net" target=3D"_blank">john@jlc.=
net</a>&gt;<br>
<br>
_______________________________________________<br>
tcpPrague mailing list<br>
<a href=3D"mailto:tcpPrague@ietf.org" target=3D"_blank">tcpPrague@ietf.org<=
/a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/tcpprague" rel=3D"noreferr=
er" target=3D"_blank">https://www.ietf.org/mailman/listinfo/tcpprague</a><b=
r>
</blockquote></font></span><div class=3D""><div class=3D"h5">
<br>
-- <br>
________________________________________________________________<br>
Bob Briscoe=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://bobbrisco=
e.net/" rel=3D"noreferrer" target=3D"_blank">http://bobbriscoe.net/</a><br>
<br>
</div></div></blockquote></div><br></div></div>

--001a114e7e78f0aa6b052c5f0fd5--


From nobody Wed Feb 24 09:37:58 2016
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 DE2F01B3A8A for <aqm@ietfa.amsl.com>; Wed, 24 Feb 2016 09:37:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 BfPT4kQkEDyj for <aqm@ietfa.amsl.com>; Wed, 24 Feb 2016 09:37:55 -0800 (PST)
Received: from atl4mhob17.myregisteredsite.com (atl4mhob17.myregisteredsite.com [209.17.115.110]) by ietfa.amsl.com (Postfix) with ESMTP id 601231B3A8F for <aqm@ietf.org>; Wed, 24 Feb 2016 09:37:55 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.211]) by atl4mhob17.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u1OHbsRB003871 for <aqm@ietf.org>; Wed, 24 Feb 2016 12:37:54 -0500
Received: (qmail 17938 invoked by uid 0); 24 Feb 2016 17:37:54 -0000
X-TCPREMOTEIP: 65.189.201.79
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.104?) (wes@mti-systems.com@65.189.201.79) by 0 with ESMTPA; 24 Feb 2016 17:37:54 -0000
To: aqm@ietf.org
References: <20160215094825.24357.56396.idtracker@ietfa.amsl.com> <F3B0A07CFD358240926B78A680E166FF89BEBE@TW-MBX-P03.cnesnet.ad.cnes.fr>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56CDEA68.8000008@mti-systems.com>
Date: Wed, 24 Feb 2016 12:37:44 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <F3B0A07CFD358240926B78A680E166FF89BEBE@TW-MBX-P03.cnesnet.ad.cnes.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/3_BiEYRJndzaOApdnUeU0ORC9Wo>
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-eval-guidelines-11.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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2016 17:37:57 -0000

On 2/15/2016 4:52 AM, Kuhn Nicolas wrote:
> All,
>
> This updated version integrates some typos correction (based on Greg Skinner's comment) and some reformulation in the "goal description section" based on Polina's personal email.
>


Hi, I've started the shepherd write-up for this and am planning to 
submit it in the next week.  I mention this in case there are still 
comments or concerns that someone has.

In the write-up, I will explain:
- how it changed scope a few times over its lifetime
- that ideally there would be running code (as mentioned by Dave, among 
others) for performing the characterizations
- that where it sits now, it's suitable as Informational guidance, but 
it's not a prescriptive and fully defined spec, like for an IPPM metric

I think this will be sufficient, but would like to know if anyone still 
has further thoughts, or strong feeling that this should be held for 
some other update before AD review?





From nobody Fri Feb 26 03:23:10 2016
Return-Path: <koen.de_schepper@nokia.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 E0C091B29B0 for <aqm@ietfa.amsl.com>; Fri, 26 Feb 2016 03:23:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 pM40PdoekGMc for <aqm@ietfa.amsl.com>; Fri, 26 Feb 2016 03:23:05 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-02.alcatel-lucent.com [135.245.210.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A5F31B29CA for <aqm@ietf.org>; Fri, 26 Feb 2016 03:23:05 -0800 (PST)
Received: from fr711umx2.dmz.alcatel-lucent.com (unknown [135.245.210.39]) by Websense Email Security Gateway with ESMTPS id 81FACED2E919B; Fri, 26 Feb 2016 11:23:01 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr711umx2.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u1QBN2kB012037 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 26 Feb 2016 11:23:02 GMT
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id u1QBN07m010027 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 26 Feb 2016 12:23:02 +0100
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.15]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.03.0195.001; Fri, 26 Feb 2016 12:23:00 +0100
From: "De Schepper, Koen (Nokia - BE)" <koen.de_schepper@nokia.com>
To: Wesley Eddy <wes@mti-systems.com>, "aqm@ietf.org" <aqm@ietf.org>
Thread-Topic: [aqm] AQM plans
Thread-Index: AQHRZDkKKSzleqJMiUCb6eN7wPD4ip8+GC/g
Date: Fri, 26 Feb 2016 11:23:00 +0000
Message-ID: <BF6B00CC65FD2D45A326E74492B2C19FB763038A@FR711WXCHMBA05.zeu.alcatel-lucent.com>
References: <56BB8F05.2030006@mti-systems.com>
In-Reply-To: <56BB8F05.2030006@mti-systems.com>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/HZZEeMhTZRIQDBuHpkxt9s7MbXg>
Subject: Re: [aqm] AQM plans
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2016 11:23:10 -0000

Hi Wes,

Just to let you know that we are still working on AQMs that support scalabl=
e (L4S) TCPs.
We could present some of our latest results (if there will be a meeting in =
Buenos Aires, otherwise in Berlin?)

* Performance of HTTP Adaptive Video Streaming (HAS) with different TCP's a=
nd AQMs
   o HAS is currently ~30% of Internet traffic, but no AQM testing so far h=
as included it
   o the results are very poor with a particular popular AQM
Presenter: Inton Tsang
Duration: 10mins
Draft: Comparative testing of draft-ietf-aqm-pie-01, draft-ietf-aqm-fq-code=
l-04, draft-briscoe-aqm-dualq-coupled

For experiment write-up, see Section 3 of https://riteproject.files.wordpre=
ss.com/2015/12/rite-deliverable-3-3-public1.pdf

* PI^2: PI simplified with a square
   o PIE embeds some auto-tuning and heuristics, which can be removed by si=
mple transformation of a variable
   o Allows PIE to control also scalable congestion controls (DCTCP, ...)
Presenter: Koen De Schepper
Duration: 15mins
Draft: (probably impacted)  draft-ietf-aqm-pie

* DualQ update
   o extensive additional tests, including different RTTs and mixed RTTs, b=
etter visualization
   o using other AQMs than Curvy-RED for 'Classic' traffic, e.g. PI^2
Presenter: Koen De Schepper
Duration: 20min
Draft: draft-briscoe-aqm-dualq-coupled-01

Regards,
Koen.


> -----Original Message-----
> From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Wesley Eddy
> Sent: woensdag 10 februari 2016 20:27
> To: aqm@ietf.org
> Subject: [aqm] AQM plans
>=20
> Hello AQMers, this is just a quick note to be clear on working group
> status and forward planning.
>=20
> Currently, all of the active drafts are either in WGLC, or in the
> process of shepherd writeups to go the the AD.
>=20
> Once we get the current set of drafts out for publication, there are a
> few things the WG can do:
> - close down
> - remain open to continue coordinating and advance algorithms (e.g.
> within the standards track)
> - remain open as a venue for potential new work (e.g. the DualQ Coupled
> AQM)
>=20
> I think we should discuss this and plan to make a decision after the
> IETF 96 meeting in Berlin (July 17-22).  We can have a "closing or
> re-chartering" meeting in Berlin if it will benefit from face-to-face
> discussion.
>=20
>=20
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm


From nobody Fri Feb 26 06:17:14 2016
Return-Path: <ralsaadi@swin.edu.au>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 381461B2C60 for <aqm@ietfa.amsl.com>; Fri, 26 Feb 2016 06:17:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.006] 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 UnMvvi-lzfLU for <aqm@ietfa.amsl.com>; Fri, 26 Feb 2016 06:17:11 -0800 (PST)
Received: from iport2.cc.swin.edu.au (iport2.cc.swin.edu.au [136.186.0.52]) by ietfa.amsl.com (Postfix) with ESMTP id 1301D1B2C5F for <aqm@ietf.org>; Fri, 26 Feb 2016 06:17:10 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.22,498,1449493200"; d="scan'208";a="17481774"
Received: from gsp-ex01.ds.swin.edu.au (HELO outlook.swin.edu.au) ([136.186.126.17]) by iport2.cc.swin.edu.au with ESMTP; 27 Feb 2016 01:17:09 +1100
Received: from GSP-EX02.ds.swin.edu.au ([169.254.2.71]) by gsp-ex01.ds.swin.edu.au ([169.254.1.193]) with mapi id 14.03.0266.001; Sat, 27 Feb 2016 01:17:14 +1100
From: Rasool Al-Saadi <ralsaadi@swin.edu.au>
To: "aqm@ietf.org" <aqm@ietf.org>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, "freebsd-ipfw@freebsd.org" <freebsd-ipfw@freebsd.org>
Thread-Topic: Dummynet AQM v0.1- CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet 
Thread-Index: AdFwoEB9RcA1ON/lTEC2HgPx0zqG6g==
Date: Fri, 26 Feb 2016 14:17:14 +0000
Message-ID: <6545444AE21C2749939E637E56594CEA3C187192@gsp-ex02.ds.swin.edu.au>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.186.127.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/Gs-beGUV9YsoqvZfC0UJjzfYfWU>
Cc: Grenville Armitage <garmitage@swin.edu.au>
Subject: [aqm] Dummynet AQM v0.1- CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2016 14:17:13 -0000

Dear all,

I would like to announce that we (myself and Grenville Armitage) released D=
ummynet AQM v0.1, which is an independent implementation of CoDel and FQ-Co=
Del for FreeBSD's ipfw/dummynet framework, based on the IETF  CoDel [1] and=
 FQ-CoDel [2] Internet-Drafts.
We prepared patches for FreeBSD11-CURRENT-r295345  and FreeBSD 10.x-RELEASE=
 (10.0, 10.1, 10.2), and a technical report  of our implementation.

Patches and documentation can be found in:
http://caia.swin.edu.au/freebsd/aqm

Technical report:
http://caia.swin.edu.au/reports/160226A/CAIA-TR-160226A.pdf



[1] "Controlled Delay Active Queue Management",  https://tools.ietf.org/htm=
l/draft-ietf-aqm-codel-02
[2] "FlowQueue-Codel" , https://tools.ietf.org/html/draft-ietf-aqm-fq-codel=
-04

Regards,
Rasool Al-Saadi


From nobody Fri Feb 26 14:04:58 2016
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 25C6E1B317D for <aqm@ietfa.amsl.com>; Fri, 26 Feb 2016 14:04:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 ptMStp2Z4lfw for <aqm@ietfa.amsl.com>; Fri, 26 Feb 2016 14:04:55 -0800 (PST)
Received: from atl4mhob03.myregisteredsite.com (atl4mhob03.myregisteredsite.com [209.17.115.41]) by ietfa.amsl.com (Postfix) with ESMTP id 25BC41B3175 for <aqm@ietf.org>; Fri, 26 Feb 2016 14:04:55 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.209]) by atl4mhob03.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id u1QM4rD1022206 for <aqm@ietf.org>; Fri, 26 Feb 2016 17:04:53 -0500
Received: (qmail 9570 invoked by uid 0); 26 Feb 2016 22:04:53 -0000
X-TCPREMOTEIP: 65.189.201.79
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.104?) (wes@mti-systems.com@65.189.201.79) by 0 with ESMTPA; 26 Feb 2016 22:04:53 -0000
To: "De Schepper, Koen (Nokia - BE)" <koen.de_schepper@nokia.com>, "aqm@ietf.org" <aqm@ietf.org>
References: <56BB8F05.2030006@mti-systems.com> <BF6B00CC65FD2D45A326E74492B2C19FB763038A@FR711WXCHMBA05.zeu.alcatel-lucent.com>
From: Wesley Eddy <wes@mti-systems.com>
Message-ID: <56D0CBFA.5030106@mti-systems.com>
Date: Fri, 26 Feb 2016 17:04:42 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <BF6B00CC65FD2D45A326E74492B2C19FB763038A@FR711WXCHMBA05.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/VFChZNMG7_OXR2jdeHn7ISOxses>
Subject: Re: [aqm] AQM plans
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2016 22:04:57 -0000

Hi, I'm now sorry that we didn't schedule an AQM meeting slot in Buenos 
Aires.  We can certainly pre-load an agenda for Berlin with these topics 
though.  That is a long way in the future, however, so please use the 
mailing list to discuss tests and metrics, share results, advertise 
papers, etc, in the meantime on these topics!



On 2/26/2016 6:23 AM, De Schepper, Koen (Nokia - BE) wrote:
> Hi Wes,
>
> Just to let you know that we are still working on AQMs that support scalable (L4S) TCPs.
> We could present some of our latest results (if there will be a meeting in Buenos Aires, otherwise in Berlin?)
>
> * Performance of HTTP Adaptive Video Streaming (HAS) with different TCP's and AQMs
>     o HAS is currently ~30% of Internet traffic, but no AQM testing so far has included it
>     o the results are very poor with a particular popular AQM
> Presenter: Inton Tsang
> Duration: 10mins
> Draft: Comparative testing of draft-ietf-aqm-pie-01, draft-ietf-aqm-fq-codel-04, draft-briscoe-aqm-dualq-coupled
>
> For experiment write-up, see Section 3 of https://riteproject.files.wordpress.com/2015/12/rite-deliverable-3-3-public1.pdf
>
> * PI^2: PI simplified with a square
>     o PIE embeds some auto-tuning and heuristics, which can be removed by simple transformation of a variable
>     o Allows PIE to control also scalable congestion controls (DCTCP, ...)
> Presenter: Koen De Schepper
> Duration: 15mins
> Draft: (probably impacted)  draft-ietf-aqm-pie
>
> * DualQ update
>     o extensive additional tests, including different RTTs and mixed RTTs, better visualization
>     o using other AQMs than Curvy-RED for 'Classic' traffic, e.g. PI^2
> Presenter: Koen De Schepper
> Duration: 20min
> Draft: draft-briscoe-aqm-dualq-coupled-01
>
> Regards,
> Koen.
>
>
>> -----Original Message-----
>> From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Wesley Eddy
>> Sent: woensdag 10 februari 2016 20:27
>> To: aqm@ietf.org
>> Subject: [aqm] AQM plans
>>
>> Hello AQMers, this is just a quick note to be clear on working group
>> status and forward planning.
>>
>> Currently, all of the active drafts are either in WGLC, or in the
>> process of shepherd writeups to go the the AD.
>>
>> Once we get the current set of drafts out for publication, there are a
>> few things the WG can do:
>> - close down
>> - remain open to continue coordinating and advance algorithms (e.g.
>> within the standards track)
>> - remain open as a venue for potential new work (e.g. the DualQ Coupled
>> AQM)
>>
>> I think we should discuss this and plan to make a decision after the
>> IETF 96 meeting in Berlin (July 17-22).  We can have a "closing or
>> re-chartering" meeting in Berlin if it will benefit from face-to-face
>> discussion.
>>
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>


From nobody Sat Feb 27 09:07:23 2016
Return-Path: <dave@taht.net>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1F41ACE37 for <aqm@ietfa.amsl.com>; Sat, 27 Feb 2016 09:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.607
X-Spam-Level: 
X-Spam-Status: No, score=-1.607 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jS3dB_qbrHIi for <aqm@ietfa.amsl.com>; Sat, 27 Feb 2016 09:07:20 -0800 (PST)
Received: from mail.taht.net (mail.taht.net [176.58.107.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09E791ACDF4 for <aqm@ietf.org>; Sat, 27 Feb 2016 09:07:19 -0800 (PST)
Received: from dair-1314.local (c-73-252-201-217.hsd1.ca.comcast.net [73.252.201.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id 617F91F4B6 for <aqm@ietf.org>; Sat, 27 Feb 2016 17:07:16 +0000 (UTC)
To: aqm@ietf.org
References: <56BB8F05.2030006@mti-systems.com> <BF6B00CC65FD2D45A326E74492B2C19FB763038A@FR711WXCHMBA05.zeu.alcatel-lucent.com> <56D0CBFA.5030106@mti-systems.com>
From: =?UTF-8?Q?Dave_T=c3=a4ht?= <dave@taht.net>
Message-ID: <56D1D8B5.2010701@taht.net>
Date: Sat, 27 Feb 2016 09:11:17 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56D0CBFA.5030106@mti-systems.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/iHCfcUzeioFDnmwcWf-UHpUfYVw>
Subject: Re: [aqm] AQM plans
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2016 17:07:22 -0000

On 2/26/16 2:04 PM, Wesley Eddy wrote:
> Hi, I'm now sorry that we didn't schedule an AQM meeting slot in Buenos
> Aires.  We can certainly pre-load an agenda for Berlin with these topics
> though.  That is a long way in the future, however, so please use the
> mailing list to discuss tests and metrics, share results, advertise
> papers, etc, in the meantime on these topics!

I plan to make the Berlin meeting. Whether I/we'll have anything to talk
about is still up in the air... "cake" has been 98% done for a while,
and there has been some nice progress lately on beginning to apply these
techniques to wifi in the linux kernel stack, but much work remains.


> 
> 
> 
> On 2/26/2016 6:23 AM, De Schepper, Koen (Nokia - BE) wrote:
>> Hi Wes,
>>
>> Just to let you know that we are still working on AQMs that support
>> scalable (L4S) TCPs.
>> We could present some of our latest results (if there will be a
>> meeting in Buenos Aires, otherwise in Berlin?)
>>
>> * Performance of HTTP Adaptive Video Streaming (HAS) with different
>> TCP's and AQMs
>>     o HAS is currently ~30% of Internet traffic, but no AQM testing so
>> far has included it
>>     o the results are very poor with a particular popular AQM
>> Presenter: Inton Tsang
>> Duration: 10mins
>> Draft: Comparative testing of draft-ietf-aqm-pie-01,
>> draft-ietf-aqm-fq-codel-04, draft-briscoe-aqm-dualq-coupled
>>
>> For experiment write-up, see Section 3 of
>> https://riteproject.files.wordpress.com/2015/12/rite-deliverable-3-3-public1.pdf
>>
>>
>> * PI^2: PI simplified with a square
>>     o PIE embeds some auto-tuning and heuristics, which can be removed
>> by simple transformation of a variable
>>     o Allows PIE to control also scalable congestion controls (DCTCP,
>> ...)
>> Presenter: Koen De Schepper
>> Duration: 15mins
>> Draft: (probably impacted)  draft-ietf-aqm-pie
>>
>> * DualQ update
>>     o extensive additional tests, including different RTTs and mixed
>> RTTs, better visualization
>>     o using other AQMs than Curvy-RED for 'Classic' traffic, e.g. PI^2
>> Presenter: Koen De Schepper
>> Duration: 20min
>> Draft: draft-briscoe-aqm-dualq-coupled-01
>>
>> Regards,
>> Koen.
>>
>>
>>> -----Original Message-----
>>> From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Wesley Eddy
>>> Sent: woensdag 10 februari 2016 20:27
>>> To: aqm@ietf.org
>>> Subject: [aqm] AQM plans
>>>
>>> Hello AQMers, this is just a quick note to be clear on working group
>>> status and forward planning.
>>>
>>> Currently, all of the active drafts are either in WGLC, or in the
>>> process of shepherd writeups to go the the AD.
>>>
>>> Once we get the current set of drafts out for publication, there are a
>>> few things the WG can do:
>>> - close down
>>> - remain open to continue coordinating and advance algorithms (e.g.
>>> within the standards track)
>>> - remain open as a venue for potential new work (e.g. the DualQ Coupled
>>> AQM)
>>>
>>> I think we should discuss this and plan to make a decision after the
>>> IETF 96 meeting in Berlin (July 17-22).  We can have a "closing or
>>> re-chartering" meeting in Berlin if it will benefit from face-to-face
>>> discussion.
>>>
>>>
>>> _______________________________________________
>>> aqm mailing list
>>> aqm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/aqm
>>
> 
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm


From nobody Sat Feb 27 09:17:54 2016
Return-Path: <dave@taht.net>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91F5A1ACE6D for <aqm@ietfa.amsl.com>; Sat, 27 Feb 2016 09:17:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.093
X-Spam-Level: *
X-Spam-Status: No, score=1.093 tagged_above=-999 required=5 tests=[BAYES_50=0.8, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AWcfYs2QSgV2 for <aqm@ietfa.amsl.com>; Sat, 27 Feb 2016 09:17:51 -0800 (PST)
Received: from mail.taht.net (mail.taht.net [IPv6:2a01:7e00::f03c:91ff:feae:7028]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E8151ACE6B for <aqm@ietf.org>; Sat, 27 Feb 2016 09:17:51 -0800 (PST)
Received: from dair-1314.local (c-73-252-201-217.hsd1.ca.comcast.net [73.252.201.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id 4A5C41F4B6; Sat, 27 Feb 2016 17:17:49 +0000 (UTC)
To: aqm@ietf.org, adrian@freebsd.org
References: <6545444AE21C2749939E637E56594CEA3C187192@gsp-ex02.ds.swin.edu.au>
From: =?UTF-8?Q?Dave_T=c3=a4ht?= <dave@taht.net>
Message-ID: <56D1DB2E.1050903@taht.net>
Date: Sat, 27 Feb 2016 09:21:50 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <6545444AE21C2749939E637E56594CEA3C187192@gsp-ex02.ds.swin.edu.au>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/zVyfyhSscHoJsnm51NF7Tr5KLOo>
Subject: Re: [aqm] Dummynet AQM v0.1- CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2016 17:17:52 -0000

On 2/26/16 6:17 AM, Rasool Al-Saadi wrote:
> Dear all,
> 
> I would like to announce that we (myself and Grenville Armitage) released Dummynet AQM v0.1, which is an independent implementation of CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet framework, based on the IETF  CoDel [1] and FQ-CoDel [2] Internet-Drafts.
> We prepared patches for FreeBSD11-CURRENT-r295345  and FreeBSD 10.x-RELEASE (10.0, 10.1, 10.2), and a technical report  of our implementation.
> 
> Patches and documentation can be found in:
> http://caia.swin.edu.au/freebsd/aqm
> 
> Technical report:
> http://caia.swin.edu.au/reports/160226A/CAIA-TR-160226A.pdf

In browsing this it appears that shaped rates were tested only (?). I am
curious what native performance (10,100,1gbit) looked like. I think that
freebsd lacks a BQL-like mechanism to control the driver queues, and on
the other hand freebsd did not go as nuts with offloads as linux did. Is
this code generally applicable (to things like pfsense?)

Aside from that, looks pretty good. I am curious also as to what caused
the offset difference in sawtooth pattern between linux and bsd
implementations (like in fig 2) Different initcwnd? ssthresh? don't seem
to be it -  linux reno vs bsd reno?

> 
> 
> 
> [1] "Controlled Delay Active Queue Management",  https://tools.ietf.org/html/draft-ietf-aqm-codel-02
> [2] "FlowQueue-Codel" , https://tools.ietf.org/html/draft-ietf-aqm-fq-codel-04
> 
> Regards,
> Rasool Al-Saadi
> 
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm
> 


From nobody Sat Feb 27 09:53:54 2016
Return-Path: <polina.goltsman@student.kit.edu>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE4D81AD186 for <aqm@ietfa.amsl.com>; Sat, 27 Feb 2016 09:53:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.606
X-Spam-Level: 
X-Spam-Status: No, score=-1.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.006] 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 FfPq9Fn3vT35 for <aqm@ietfa.amsl.com>; Sat, 27 Feb 2016 09:53:50 -0800 (PST)
Received: from scc-mailout-kit-02.scc.kit.edu (scc-mailout-kit-02.scc.kit.edu [IPv6:2a00:1398:9:f712::810d:e752]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30D391AD0D6 for <aqm@ietf.org>; Sat, 27 Feb 2016 09:53:50 -0800 (PST)
Received: from kit-msx-32.kit.edu ([2a00:1398:9:f612::32]) by scc-mailout-kit-02.scc.kit.edu with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (envelope-from <polina.goltsman@student.kit.edu>) id 1aZj3o-0002d4-Ty; Sat, 27 Feb 2016 18:53:47 +0100
Received: from localhost.localdomain (84.179.102.22) by smtp.kit.edu (129.13.50.106) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Sat, 27 Feb 2016 18:53:44 +0100
To: =?UTF-8?Q?Dave_T=c3=a4ht?= <dave@taht.net>, AQM IETF list <aqm@ietf.org>
References: <6545444AE21C2749939E637E56594CEA3C187192@gsp-ex02.ds.swin.edu.au> <56D1DB2E.1050903@taht.net>
From: Polina Goltsman <polina.goltsman@student.kit.edu>
Message-ID: <56D1E2AF.8030802@student.kit.edu>
Date: Sat, 27 Feb 2016 18:53:51 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <56D1DB2E.1050903@taht.net>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [84.179.102.22]
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/ftFFUQN1de4eQUJBU-fMJvRF7Do>
Subject: Re: [aqm] Dummynet AQM v0.1- CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2016 17:53:53 -0000

On 02/27/2016 06:21 PM, Dave Täht wrote:
>
> On 2/26/16 6:17 AM, Rasool Al-Saadi wrote:
>> Dear all,
>>
>> I would like to announce that we (myself and Grenville Armitage) released Dummynet AQM v0.1, which is an independent implementation of CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet framework, based on the IETF  CoDel [1] and FQ-CoDel [2] Internet-Drafts.
>> We prepared patches for FreeBSD11-CURRENT-r295345  and FreeBSD 10.x-RELEASE (10.0, 10.1, 10.2), and a technical report  of our implementation.
>>
>> Patches and documentation can be found in:
>> http://caia.swin.edu.au/freebsd/aqm
>>
>> Technical report:
>> http://caia.swin.edu.au/reports/160226A/CAIA-TR-160226A.pdf
> In browsing this it appears that shaped rates were tested only (?). I am
> curious what native performance (10,100,1gbit) looked like. I think that
> freebsd lacks a BQL-like mechanism to control the driver queues, and on
> the other hand freebsd did not go as nuts with offloads as linux did. Is
> this code generally applicable (to things like pfsense?)
>
> Aside from that, looks pretty good. I am curious also as to what caused
> the offset difference in sawtooth pattern between linux and bsd
> implementations (like in fig 2) Different initcwnd? ssthresh? don't seem
> to be it -  linux reno vs bsd reno?
I can't distinguish between the maximum congestion windows, but Linux's RTT
(especially the minimum one) is smaller on all three figures (2,3, and 4),
and packet losses for FreeBSD are a little less frequent. So, assuming that
the AQM behaves the same, there is another queue somewhere.

What is strange is that Linux's goodput is higher on figures 2 and 3 
despite
lower queueing delay. On the other hand for Cubic both delay and goodput are
slightly smaller. Is that advanced loss recovery in Linux?

Also, is it normal that NewReno resets its congestion window (to initcwnd)
after each packet loss aka. why it looks like Tahoe? Does CoDeL go into
dropping more than one packet per RTT if the RTT is much smaller than an
interval?
>>
>>
>> [1] "Controlled Delay Active Queue Management",  https://tools.ietf.org/html/draft-ietf-aqm-codel-02
>> [2] "FlowQueue-Codel" , https://tools.ietf.org/html/draft-ietf-aqm-fq-codel-04
>>
>> Regards,
>> Rasool Al-Saadi
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm


From nobody Sat Feb 27 11:00:46 2016
Return-Path: <dave@taht.net>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42ADF1A88E8 for <aqm@ietfa.amsl.com>; Sat, 27 Feb 2016 11:00:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.693
X-Spam-Level: *
X-Spam-Status: No, score=1.693 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_102=0.6, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j9P9c8xNkqRE for <aqm@ietfa.amsl.com>; Sat, 27 Feb 2016 11:00:43 -0800 (PST)
Received: from mail.taht.net (mail.taht.net [IPv6:2a01:7e00::f03c:91ff:feae:7028]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C9E61B2B0B for <aqm@ietf.org>; Sat, 27 Feb 2016 11:00:42 -0800 (PST)
Received: from dair-1314.local (c-73-252-201-217.hsd1.ca.comcast.net [73.252.201.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id 2CAE01F4B6; Sat, 27 Feb 2016 19:00:40 +0000 (UTC)
To: aqm@ietf.org, bloat@lists.bufferbloat.net
References: <56BB8F05.2030006@mti-systems.com> <BF6B00CC65FD2D45A326E74492B2C19FB763038A@FR711WXCHMBA05.zeu.alcatel-lucent.com>
From: =?UTF-8?Q?Dave_T=c3=a4ht?= <dave@taht.net>
Message-ID: <56D1F349.6040601@taht.net>
Date: Sat, 27 Feb 2016 11:04:41 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <BF6B00CC65FD2D45A326E74492B2C19FB763038A@FR711WXCHMBA05.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/nitx49a2YDQJ-4z1KOpAQMorO-k>
Subject: [aqm] review: Deployment of RITE mechanisms, in use-case trial testbeds report part 1
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2016 19:00:45 -0000

On 2/26/16 3:23 AM, De Schepper, Koen (Nokia - BE) wrote:
> Hi Wes,
> 
> Just to let you know that we are still working on AQMs that support scalable (L4S) TCPs.
> We could present some of our latest results (if there will be a meeting in Buenos Aires, otherwise in Berlin?)
> 
> * Performance of HTTP Adaptive Video Streaming (HAS) with different TCP's and AQMs
>    o HAS is currently ~30% of Internet traffic, but no AQM testing so far has included it

I am aware of several unpublished studies. There was also something that
compared 1-3 HAS flows from several years back from stanford that I've
longed to be repeated against these aqm technologies.

https://reproducingnetworkresearch.wordpress.com/2014/06/03/cs244-14-confused-timid-and-unstable-picking-a-video-streaming-rate-is-hard/

>    o the results are very poor with a particular popular AQM

Define "very poor". ?

> Presenter: Inton Tsang
> Duration: 10mins
> Draft: Comparative testing of draft-ietf-aqm-pie-01, draft-ietf-aqm-fq-codel-04, draft-briscoe-aqm-dualq-coupled



> 
> For experiment write-up, see Section 3 of https://riteproject.files.wordpress.com/2015/12/rite-deliverable-3-3-public1.pdf

At the risk of sounding grumpy and pedantic, partially driven by trying
to read through 58 pages of text on a b/w kindle (before I switched to
something higher res)

No source, can't reproduce.

The diagrams of the topology, etc, were quite helpful. Insight into the
actual complexity of BT's network was quite useful. I would love to know
the actual usage of the various QoS queues in terms of real traffic...

Has DCTP's not responding to drop properly problem been fixed in linux
yet? (sec 3.3.2). That remains a scary bug....

More detailed comments:

The tests tested download traffic only and seem to have assumed that the
uplink would never have been a bottleneck. Home connections are
asymmetric and increasingly so - comcast, for example is now putting out
links with 75Mbit down, 5.5Mbit up. It is not clear what the uplink rate
of the emulated or real network is in this paper.

2) Section 2 - would have been tons more interesting had it evaluated
the effects of other workloads against actual "twitch" games such as any
of the quake series, call of duty, or starcraft. The game chosen was
quite uninteresting from "needing a low latency and jitter to win" on,
front.

Applying interesting background network workloads while game bots
competed as in here http://sscaitournament.com/ would have been great
fun! - injecting random jitter and delay into the network stack has been
what Karl Auerbach has been doing to the competitors at the DARPA robot
competitions, and he's probably been the cause of quite a few of those
real-life robots falling over (I can hear his evil chuckles now).

Artificially applying a wifi loss rate of 1.5% is a far cry from what
actually happens on wifi, where what you see is more typically large
spikes in l2 delay, nowadays.

3) As for section 3 - it uses a "bottleneck of 20Mbps and RTT of 20ms,
ten TCP long file download flows as background traffic and one HAS
request, which launch two TCP flows." I will try to restrain myself, but:

A) In a cable modem scenario, the typical uplink varies from 2mbit to
4mbit on a 20mbit link. I am not aware of many 20mbit symmetric links,
aside from FIOS. I would love symmetry on home links, is BT deploying that??

B) this is a workload that has very little resemblance to any reality I
can think of and seems expressly designed to show the burst tolerance
and additional latency induced by pie and dualQ to an advantage, and
fq_codel at a local minimum.

For the sake of science, varying the number of long running downloads
from, say, 2,4,8 and 16, would have provided a more rounded picture.
Still I am really hard pressed to think of any case where home HAS
traffic will be competing with more than 2-3 long running full rate
downloads in your typical home. I HAVE seen 3 android devices attempt to
update themselves all at once, but that's it....

Using bittorrent to generate 5-15 flows down, perhaps? Even then, most
real world torrents are not running very fast, there's utp based
congestion control, and torrenters spend way more time in the upload
phase than the download.

...

Using web access bursts (10-100 flows lasting for 2-8 seconds), chock
full of dns accesses, seems to be a good test against HAS traffic. I see
there is a section doing that, but it is against 5 background flows,
also and I'm pretty sure there will be a pause between bursts, and
although the "The web requests followed an exponential arrival process,
while the size of the downloaded files were designed to represent actual
Internet web objects following a Pareto distribution with size between 1
Kbyte and 1 Mbyte" is documented...

I could do the math assuming that distribution * the number of files...
but I would prefer the total size of the web transfer be documented, and
it's time to complete a load presented... nor is it clear if dns lookups
are enabled or counted. Unless I missed it somewhere? If you are going
to measure two loads - one HAS, one web, presenting the results for both
for contrast, seems logical.

"Figure 3.22 shows that HAS-DCTCP can maintain its performance even with
the additional 100 web traffic request per second as background traffic.
It consistently delivered segments of 2056 Kbps encoding
bit rate. In contrast, under the same network condition, the additional
web traffic deteriorate further the performance of HAS-CTCP as the
delivered segment alternated qualities between 688 Kbps and
991 Kbps encoding rates. This had a lower overall quality when compared
with the previous experiment, which without the additional web traffic
could achieved a sustainable delivery of segment with 991 Kbps
encoding rates, as shown in Figure 3.18"

This kind of stuff really gets under my skin. What was the web page
completion time? Which matters more to the users of the household? a
slight decline in video quality, or a web page load?

Sacrificing all other network applications on the crucible of 4k video
is really not my goal in life, I would like to see videoconferencing,
gaming, web, in particular, work well in the presence of HAS.

Please, please, please, put web page completion times in this document?

...

Also that sort of web traffic would probably cycle on a 30-60 second
basis at most - people just can't read that fast! Secondly, a search
engine query often precedes an actual web page lookup.

 (I note that web page size growth has slowed dramatically since this wg
started, it is now well below the projections we had a few years ago
(7mbit by 20XX, more like 4 now, but I'd have to go redo the math -
growth went from exponential-looking in 2012 to linear now...). There's
also some data presented recently by some googlers at netconf 1.1 that
showed the impact and commonality of dns failures across their
subscriber base.....

I freely confess that maybe i'm out of touch, that maybe having perfect
television quality while waiting seconds for web pages to load, is what
most internet users want, and they deserve to get it, good and hard,
along with their supersized mcgreasy burgers and calming drugs delivered
to their door.

C) And no reverse traffic whatsoever in section three.

In your typical HAS video streaming home scenario, the worst behaviors I
can think of would be bittorrent generated *on the upload*, but the
simplest case of a single upload happening at all - tends towards
starving the ack streams and ramp up times on the video download flows.
Which was not tested. Sigh. How long have I banged on this drum?

D) It is unproven from a QOE perspective (I think) that having a video
stream change qualities on a "better average" basis is of benefit to the
user - seeing a stream never pause "for buffering", and consistent
quality, seems saner. I notice when the quality changes down, but rarely
up. "buffering" - that I seriously notice.

I would have liked reference data for drop tail vs the various
experiments in this paper. Typical amounts of head end buffering on
docsis 3.0 arris cmtss seem to be in the 800ms range at 20mbit.

E) A workload that I would like to see tested with some rigor is a
family of four - one doing a big upload (facebook/instagram), another
browsing the web, another doing a phone call or videoconference, and a
fourth attempting to watch a movie at the highest possible resolution.

The bar for the last has moved to SD or HD quality in the past few years
- 18mbits is a number I keep seeing more and more. Someone with a 20Mbit
link IS going to try for the highest quality, and showing the dynamic
range of that (1-18mbits) would be more interesting than 1mbit to 2, as
in in this paper.

I also would welcome 2-3 HAS testing on downloads against these AQMs,
attempting those rates, along the lines of the stanford thing I
mentioned first.

I petered out before reading sections 4 and 5. I will try to get to it
this week.


From nobody Sat Feb 27 11:03:05 2016
Return-Path: <chromatix99@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 46CA81B2B1B for <aqm@ietfa.amsl.com>; Sat, 27 Feb 2016 11:03:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jkr03DQ-hsy0 for <aqm@ietfa.amsl.com>; Sat, 27 Feb 2016 11:03:02 -0800 (PST)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05D731B2B18 for <aqm@ietf.org>; Sat, 27 Feb 2016 11:03:01 -0800 (PST)
Received: by mail-lf0-x232.google.com with SMTP id l83so23482859lfd.3 for <aqm@ietf.org>; Sat, 27 Feb 2016 11:03:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xKV4S6dqEAH0qRoQ4PLCljeOIQMBSP3yUHOIGJ2kHBI=; b=P3D9uSfofG6TAwsIflxUSRAd/Z9Hdb150a26F/Vr/S/xFScRlTnAlFmKgswRDXcQbQ VgWHfnkzyqH/6QphoBPE4hl8J0ViPAoi8LDTqVawH2HqVrsMGwHvJhZ2qPHzIi1QIYAq FSB7vXN4BVs0cluxYWmS8jVGSdbj/4KuhdXMbaJnwLAMRx3z00mu99ZtCq7hLZEfhzDA Bysp5pvHN+A882JwJhDrBORtUakaCVfngnxiBixPfappRurtuaVneG6gH/Wa5rtpqdpp sY6NK4xat+V8gRK0N9xbtfX+B1kjLZNgPXhEGy5Cnf0IiLN5mTlSK4dstupMN0+ozj5I OdPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xKV4S6dqEAH0qRoQ4PLCljeOIQMBSP3yUHOIGJ2kHBI=; b=aJIgew8JPlHqxIHmcbAwLM1oj98e0C7pbon4kG8EmjSx2pmuy6BVEd0UQzbMpvNaTS QrHaOy+eIB4j9ruQD12GmuuUNtH+WMaK9Ha3tgsyPdXnJ2BOI3mfvrhlpoHmd5PUJi7P l62GreakSYJOd0Q02g0ypNYVTXHfNzpRtD7ZKwR2jY8zquOyUdJGYzPj1J6uDnS+vy7G 1ytKOjMRn8zscEnO4e8BdHFhcqYwQibVcJnrdpP+cuxMq6KsqnNyVxUw7W4fSNK7z0/R EtZapCZGhD04fz7eFykjBe+QlQRnXvEwAPRxiEnmhFnVk2eFeKPsbmCJNPh+QnR+0LIq lA5w==
X-Gm-Message-State: AD7BkJJLYZrBSj/J+7OLvcb5iuDbqYIYcgdzJvwQvYtBv6tRKR7VHJPVJS8WDputLkDzoQ==
X-Received: by 10.25.19.151 with SMTP id 23mr1113250lft.126.1456599780232; Sat, 27 Feb 2016 11:03:00 -0800 (PST)
Received: from bass.home.chromatix.fi (37-33-67-252.bb.dnainternet.fi. [37.33.67.252]) by smtp.gmail.com with ESMTPSA id ra6sm2638282lbb.33.2016.02.27.11.02.59 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 27 Feb 2016 11:02:59 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Jonathan Morton <chromatix99@gmail.com>
In-Reply-To: <56D1E2AF.8030802@student.kit.edu>
Date: Sat, 27 Feb 2016 21:02:57 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A51CC60-D684-4E35-9C6F-9D0ED3EFA15A@gmail.com>
References: <6545444AE21C2749939E637E56594CEA3C187192@gsp-ex02.ds.swin.edu.au> <56D1DB2E.1050903@taht.net> <56D1E2AF.8030802@student.kit.edu>
To: Polina Goltsman <polina.goltsman@student.kit.edu>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/Oj2tdJOpx2DN6Qqyj5SvxuaIm0U>
Cc: =?windows-1252?Q?Dave_T=E4ht?= <dave@taht.net>, AQM IETF list <aqm@ietf.org>
Subject: Re: [aqm] Dummynet AQM v0.1- CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2016 19:03:03 -0000

> On 27 Feb, 2016, at 19:53, Polina Goltsman =
<polina.goltsman@student.kit.edu> wrote:
>=20
> Does CoDeL go into
> dropping more than one packet per RTT if the RTT is much smaller than =
an
> interval?

No - quite the opposite.  It is more likely to drop more than one packet =
per RTT when the actual RTT is *greater* than the interval setting.

 - Jonathan Morton


From nobody Mon Feb 29 00:58:25 2016
Return-Path: <garmitage@swin.edu.au>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0605F1B2E55 for <aqm@ietfa.amsl.com>; Mon, 29 Feb 2016 00:58:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.697
X-Spam-Level: 
X-Spam-Status: No, score=0.697 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.006] 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 lS_39E82crVi for <aqm@ietfa.amsl.com>; Mon, 29 Feb 2016 00:58:21 -0800 (PST)
Received: from gpo4.cc.swin.edu.au (gpo4.cc.swin.edu.au [136.186.1.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF2191B2E51 for <aqm@ietf.org>; Mon, 29 Feb 2016 00:58:20 -0800 (PST)
Received: from [136.186.229.37] (garmitage.caia.swin.edu.au [136.186.229.37]) by gpo4.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id u1T8wHtU017118 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);  Mon, 29 Feb 2016 19:58:17 +1100
To: aqm@ietf.org
References: <6545444AE21C2749939E637E56594CEA3C187192@gsp-ex02.ds.swin.edu.au> <56D1DB2E.1050903@taht.net>
From: grenville armitage <garmitage@swin.edu.au>
Message-ID: <56D40829.5060608@swin.edu.au>
Date: Mon, 29 Feb 2016 19:58:17 +1100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <56D1DB2E.1050903@taht.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/pNHCv5EFDS-O43RrSuxZrVC_TjE>
Subject: Re: [aqm] Dummynet AQM v0.1- CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Feb 2016 08:58:23 -0000

On 02/28/2016 04:21, Dave T=E4ht wrote:
>
> On 2/26/16 6:17 AM, Rasool Al-Saadi wrote:
     [..]
>>
>> Technical report:
>> http://caia.swin.edu.au/reports/160226A/CAIA-TR-160226A.pdf
> In browsing this it appears that shaped rates were tested only (?).

Yes.

>   I am
> curious what native performance (10,100,1gbit) looked like. I think tha=
t
> freebsd lacks a BQL-like mechanism to control the driver queues, and on=

> the other hand freebsd did not go as nuts with offloads as linux did. I=
s
> this code generally applicable (to things like pfsense?)

We haven't tested pfSense, but as their website says pfSense 2.2 is based=
 on FreeBSD 10.1, and our patch applies to stock ipfw and dummynet under =
FreeBSD 10.1, it may well simply drop-in just fine.

> Aside from that, looks pretty good. I am curious also as to what caused=

> the offset difference in sawtooth pattern between linux and bsd
> implementations (like in fig 2) Different initcwnd? ssthresh? don't see=
m
> to be it -  linux reno vs bsd reno?

The only change in e.g. Fig.2 was to reboot the bottleneck router between=
 Linux and FreeBSD -- the source was the same TCP stack in either case. W=
e haven't dug into the reasons for observed differences yet, although the=
y may be related to the slightly higher RTTs observed when using FreeBSD =
+ our patched dummynet. Future work ;)

cheers,
gja



From nobody Mon Feb 29 01:05:05 2016
Return-Path: <garmitage@swin.edu.au>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 564021B2E65 for <aqm@ietfa.amsl.com>; Mon, 29 Feb 2016 01:05:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.006] 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 FOcD7DKADEQA for <aqm@ietfa.amsl.com>; Mon, 29 Feb 2016 01:05:03 -0800 (PST)
Received: from gpo4.cc.swin.edu.au (gpo4.cc.swin.edu.au [136.186.1.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67AA11B2E64 for <aqm@ietf.org>; Mon, 29 Feb 2016 01:05:03 -0800 (PST)
Received: from [136.186.229.37] (garmitage.caia.swin.edu.au [136.186.229.37]) by gpo4.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id u1T9512H018866 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);  Mon, 29 Feb 2016 20:05:01 +1100
To: aqm@ietf.org
References: <6545444AE21C2749939E637E56594CEA3C187192@gsp-ex02.ds.swin.edu.au> <56D1DB2E.1050903@taht.net> <56D1E2AF.8030802@student.kit.edu>
From: grenville armitage <garmitage@swin.edu.au>
Message-ID: <56D409BC.5070006@swin.edu.au>
Date: Mon, 29 Feb 2016 20:05:00 +1100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <56D1E2AF.8030802@student.kit.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/FiD3oOg88zo4NQnMDjC81L649UY>
Subject: Re: [aqm] Dummynet AQM v0.1- CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Feb 2016 09:05:04 -0000

On 02/28/2016 04:53, Polina Goltsman wrote:
>
>
>
     [..]
> Also, is it normal that NewReno resets its congestion window (to initcwnd)
> after each packet loss aka.

More an artefact of FreeBSD's NewReno implementation temporarily overloading the internal cwnd variable during FR/FR. Our cwnd tracking is event-driven rather than polled, so we 'see' sudden drops and rapid regrowth of FreeBSD's cwnd during the brief time period after a loss is detected.

cheers,
gja


From nobody Mon Feb 29 08:15:36 2016
Return-Path: <dhavey@gmail.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 481711B3541 for <aqm@ietfa.amsl.com>; Mon, 29 Feb 2016 08:15:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hw8TNA8O40vR for <aqm@ietfa.amsl.com>; Mon, 29 Feb 2016 08:15:33 -0800 (PST)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 593711B3540 for <aqm@ietf.org>; Mon, 29 Feb 2016 08:15:33 -0800 (PST)
Received: by mail-qg0-x22d.google.com with SMTP id b67so118988750qgb.1 for <aqm@ietf.org>; Mon, 29 Feb 2016 08:15:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=+ZnMouNznbkbxK5iXycCG7SkkTtoadLjKSXGYfNUKC4=; b=wfT/az6E5U5IL6xXfJo//wjbYe1/LMen92+fSiyN9pu7qjQFfhZl57y59NGEpFCtJH ohNJp3OKvbQam/vRiWfS3kjCRD6G+HFzu98sSjWW0CRC2o5wB67UMuDcUhhr4wwPtUnK IoyFB81jIPsJHpU8hUdVt+70Pd04rZrORiop2HWngpmKSOVSkW40yGLWqQsuT3ZChYvm pBVV364EKqY/4Oqn/jKR8POGRaXOL2RDClwhwDjdY+LXdUSWDdr3GGVXw1i5mylG9ZQc LRJxh3x691o4tjSnQnn9XM1KIdwoPWZb8uegBrZxr8h3fOgvjw5GEX1XxA21ep2W6M47 2AWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=+ZnMouNznbkbxK5iXycCG7SkkTtoadLjKSXGYfNUKC4=; b=hui/bK4IrmPFTbHZ2xvqrkKr5MeTyn6GWWtWKWVFcOgPmkNvKtKFoCf9EIK5Dl7l/2 4/4ehKQGx7NmtU9CVlvRjgXjzJjG1CoAQKNd+b79Z0tGXi9U4IF66jmCtMM5smmJjKYe IF6Js/WCcmn2FwIwroNBoKoK2UKDKpaQ4bnXPq3Yfa9FKDvSwSZLggvmZuUBcDz7aaHi ihLtU5ms9THJMAm8K/IuXw/kuCppTghqJwaNyltJgXo9Cof03pDGEa8Ukte7wPZj2WXR JPzt6kLyEYIp7UXy/wnDuTcLL1ujYISWs9M17yc7K++cFVIglavuXENyTahLY2SNSutF UWvQ==
X-Gm-Message-State: AD7BkJIKvy+a7vJ4McRsWY6xZeJTPoddRqtEO9YGHo75sq6T7G06My61FucgqXlFKpVNSFno8voHsi+YVukQ1g==
MIME-Version: 1.0
X-Received: by 10.140.155.196 with SMTP id b187mr21416743qhb.14.1456762532404;  Mon, 29 Feb 2016 08:15:32 -0800 (PST)
Received: by 10.55.36.72 with HTTP; Mon, 29 Feb 2016 08:15:32 -0800 (PST)
In-Reply-To: <56D1D8B5.2010701@taht.net>
References: <56BB8F05.2030006@mti-systems.com> <BF6B00CC65FD2D45A326E74492B2C19FB763038A@FR711WXCHMBA05.zeu.alcatel-lucent.com> <56D0CBFA.5030106@mti-systems.com> <56D1D8B5.2010701@taht.net>
Date: Mon, 29 Feb 2016 08:15:32 -0800
Message-ID: <CAO1c0ASNSL6On85PMrwoytUyVtKejpp8shMw8sNBXb-+fPUMUQ@mail.gmail.com>
From: Daniel Havey <dhavey@gmail.com>
To: =?UTF-8?Q?Dave_T=C3=A4ht?= <dave@taht.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/Q8VSk9vNwjc8V-xmcUVYLNIx6BE>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] AQM plans
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Feb 2016 16:15:35 -0000

Just wanted to add a quick data point.  I am interested in the
possibilities of using AQM at endpoints.  Not sure how this jibes with
the goals of the working group, but, if anyone is interested I would
like to keep the endpoints in the conversation.

thanxs ;^)
...Daniel

On Sat, Feb 27, 2016 at 9:11 AM, Dave T=C3=A4ht <dave@taht.net> wrote:
>
>
> On 2/26/16 2:04 PM, Wesley Eddy wrote:
>> Hi, I'm now sorry that we didn't schedule an AQM meeting slot in Buenos
>> Aires.  We can certainly pre-load an agenda for Berlin with these topics
>> though.  That is a long way in the future, however, so please use the
>> mailing list to discuss tests and metrics, share results, advertise
>> papers, etc, in the meantime on these topics!
>
> I plan to make the Berlin meeting. Whether I/we'll have anything to talk
> about is still up in the air... "cake" has been 98% done for a while,
> and there has been some nice progress lately on beginning to apply these
> techniques to wifi in the linux kernel stack, but much work remains.
>
>
>>
>>
>>
>> On 2/26/2016 6:23 AM, De Schepper, Koen (Nokia - BE) wrote:
>>> Hi Wes,
>>>
>>> Just to let you know that we are still working on AQMs that support
>>> scalable (L4S) TCPs.
>>> We could present some of our latest results (if there will be a
>>> meeting in Buenos Aires, otherwise in Berlin?)
>>>
>>> * Performance of HTTP Adaptive Video Streaming (HAS) with different
>>> TCP's and AQMs
>>>     o HAS is currently ~30% of Internet traffic, but no AQM testing so
>>> far has included it
>>>     o the results are very poor with a particular popular AQM
>>> Presenter: Inton Tsang
>>> Duration: 10mins
>>> Draft: Comparative testing of draft-ietf-aqm-pie-01,
>>> draft-ietf-aqm-fq-codel-04, draft-briscoe-aqm-dualq-coupled
>>>
>>> For experiment write-up, see Section 3 of
>>> https://riteproject.files.wordpress.com/2015/12/rite-deliverable-3-3-pu=
blic1.pdf
>>>
>>>
>>> * PI^2: PI simplified with a square
>>>     o PIE embeds some auto-tuning and heuristics, which can be removed
>>> by simple transformation of a variable
>>>     o Allows PIE to control also scalable congestion controls (DCTCP,
>>> ...)
>>> Presenter: Koen De Schepper
>>> Duration: 15mins
>>> Draft: (probably impacted)  draft-ietf-aqm-pie
>>>
>>> * DualQ update
>>>     o extensive additional tests, including different RTTs and mixed
>>> RTTs, better visualization
>>>     o using other AQMs than Curvy-RED for 'Classic' traffic, e.g. PI^2
>>> Presenter: Koen De Schepper
>>> Duration: 20min
>>> Draft: draft-briscoe-aqm-dualq-coupled-01
>>>
>>> Regards,
>>> Koen.
>>>
>>>
>>>> -----Original Message-----
>>>> From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Wesley Eddy
>>>> Sent: woensdag 10 februari 2016 20:27
>>>> To: aqm@ietf.org
>>>> Subject: [aqm] AQM plans
>>>>
>>>> Hello AQMers, this is just a quick note to be clear on working group
>>>> status and forward planning.
>>>>
>>>> Currently, all of the active drafts are either in WGLC, or in the
>>>> process of shepherd writeups to go the the AD.
>>>>
>>>> Once we get the current set of drafts out for publication, there are a
>>>> few things the WG can do:
>>>> - close down
>>>> - remain open to continue coordinating and advance algorithms (e.g.
>>>> within the standards track)
>>>> - remain open as a venue for potential new work (e.g. the DualQ Couple=
d
>>>> AQM)
>>>>
>>>> I think we should discuss this and plan to make a decision after the
>>>> IETF 96 meeting in Berlin (July 17-22).  We can have a "closing or
>>>> re-chartering" meeting in Berlin if it will benefit from face-to-face
>>>> discussion.
>>>>
>>>>
>>>> _______________________________________________
>>>> aqm mailing list
>>>> aqm@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/aqm
>>>
>>
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>
> _______________________________________________
> aqm mailing list
> aqm@ietf.org
> https://www.ietf.org/mailman/listinfo/aqm


From nobody Mon Feb 29 10:55:13 2016
Return-Path: <dave@taht.net>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B13A71B39FC for <aqm@ietfa.amsl.com>; Mon, 29 Feb 2016 10:55:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.607
X-Spam-Level: 
X-Spam-Status: No, score=-1.607 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U59fTzH2vJzG for <aqm@ietfa.amsl.com>; Mon, 29 Feb 2016 10:55:09 -0800 (PST)
Received: from mail.taht.net (mail.taht.net [176.58.107.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FB201B39E9 for <aqm@ietf.org>; Mon, 29 Feb 2016 10:55:09 -0800 (PST)
Received: from dair-1314.local (c-73-252-201-217.hsd1.ca.comcast.net [73.252.201.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id 745561F4B6 for <aqm@ietf.org>; Mon, 29 Feb 2016 18:55:07 +0000 (UTC)
To: AQM IETF list <aqm@ietf.org>
References: <6545444AE21C2749939E637E56594CEA3C187192@gsp-ex02.ds.swin.edu.au> <56D1DB2E.1050903@taht.net> <56D1E2AF.8030802@student.kit.edu>
From: =?UTF-8?Q?Dave_T=c3=a4ht?= <dave@taht.net>
Message-ID: <56D494FF.5070209@taht.net>
Date: Mon, 29 Feb 2016 10:59:11 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56D1E2AF.8030802@student.kit.edu>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/S2E6PyLTUF4LHNUxK0PwvM9Zb6w>
Subject: Re: [aqm] Dummynet AQM v0.1- CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet
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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Feb 2016 18:55:11 -0000

On 2/27/16 9:53 AM, Polina Goltsman wrote:
> 
> 
> On 02/27/2016 06:21 PM, Dave Täht wrote:
>>
>> On 2/26/16 6:17 AM, Rasool Al-Saadi wrote:
>>> Dear all,
>>>
>>> I would like to announce that we (myself and Grenville Armitage)
>>> released Dummynet AQM v0.1, which is an independent implementation of
>>> CoDel and FQ-CoDel for FreeBSD's ipfw/dummynet framework, based on
>>> the IETF  CoDel [1] and FQ-CoDel [2] Internet-Drafts.
>>> We prepared patches for FreeBSD11-CURRENT-r295345  and FreeBSD
>>> 10.x-RELEASE (10.0, 10.1, 10.2), and a technical report  of our
>>> implementation.
>>>
>>> Patches and documentation can be found in:
>>> http://caia.swin.edu.au/freebsd/aqm
>>>
>>> Technical report:
>>> http://caia.swin.edu.au/reports/160226A/CAIA-TR-160226A.pdf
>> In browsing this it appears that shaped rates were tested only (?). I am
>> curious what native performance (10,100,1gbit) looked like. I think that
>> freebsd lacks a BQL-like mechanism to control the driver queues, and on
>> the other hand freebsd did not go as nuts with offloads as linux did. Is
>> this code generally applicable (to things like pfsense?)
>>
>> Aside from that, looks pretty good. I am curious also as to what caused
>> the offset difference in sawtooth pattern between linux and bsd
>> implementations (like in fig 2) Different initcwnd? ssthresh? don't seem
>> to be it -  linux reno vs bsd reno?
> I can't distinguish between the maximum congestion windows, but Linux's RTT
> (especially the minimum one) is smaller on all three figures (2,3, and 4),
> and packet losses for FreeBSD are a little less frequent. So, assuming that
> the AQM behaves the same, there is another queue somewhere.

Two other variables worth tweaking on a linux server and client (besides
the kernel version) are sch_fq and tcp_limit_output_bytes. On bare metal
this was set to 4k or so, which proved too small to drive linux wifi's
existing drivers on certain tests, got bumped to 128k, and then the xen
folk noticed that regressed their throughput by like 30%, so it got
bumped again to 256k default.

I liked it at 4k. A lot. :) it is plausible that tweaking
tcp_limit_output_bytes will change your results.

> What is strange is that Linux's goodput is higher on figures 2 and 3
> despite
> lower queueing delay. On the other hand for Cubic both delay and goodput
> are
> slightly smaller. Is that advanced loss recovery in Linux?
> 
> Also, is it normal that NewReno resets its congestion window (to initcwnd)
> after each packet loss aka. why it looks like Tahoe? Does CoDeL go into
> dropping more than one packet per RTT if the RTT is much smaller than an
> interval?
>>>
>>>
>>> [1] "Controlled Delay Active Queue Management", 
>>> https://tools.ietf.org/html/draft-ietf-aqm-codel-02
>>> [2] "FlowQueue-Codel" ,
>>> https://tools.ietf.org/html/draft-ietf-aqm-fq-codel-04
>>>
>>> Regards,
>>> Rasool Al-Saadi
>>>
>>> _______________________________________________
>>> 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 Mon Feb 29 23:41:47 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: aqm@ietf.org
Delivered-To: aqm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A8371A9253; Mon, 29 Feb 2016 23:41:44 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.15.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160301074144.7440.49538.idtracker@ietfa.amsl.com>
Date: Mon, 29 Feb 2016 23:41:44 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/QmKElRUK_GkdxUmNmmfNCGEtuiU>
Cc: aqm@ietf.org
Subject: [aqm] I-D Action: draft-ietf-aqm-pie-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: <https://mailarchive.ietf.org/arch/browse/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Mar 2016 07:41:44 -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 of the IETF.

        Title           : PIE: A Lightweight Control Scheme To Address the Bufferbloat Problem
        Authors         : Rong Pan
                          Preethi Natarajan
                          Fred Baker
	Filename        : draft-ietf-aqm-pie-04.txt
	Pages           : 26
	Date            : 2016-02-29

Abstract:
   Bufferbloat is a phenomenon where excess buffers in the network cause
   high latency and jitter. As more and more interactive applications
   (e.g. voice over IP, real time video streaming and financial
   transactions) run in the Internet, high latency and jitter degrade
   application performance. There is a pressing need to design
   intelligent queue management schemes that can control latency and
   jitter; and hence provide desirable quality of service to users.

   This document presents a lightweight active queue management design,
   called PIE (Proportional Integral controller Enhanced), that can
   effectively control the average queueing latency to a target value.
   Simulation results, theoretical analysis and Linux testbed results
   have shown that PIE can ensure low latency and achieve high link
   utilization under various congestion situations. The design does not
   require per-packet timestamp, so it incurs very small overhead and is
   simple enough to implement in both hardware and software.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-aqm-pie-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-aqm-pie-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/

