Re: [aqm] adoption of draft-white-aqm-docsis-pie-01

"Rong Pan (ropan)" <ropan@cisco.com> Thu, 02 April 2015 21:49 UTC

Return-Path: <ropan@cisco.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B50BE1A7005 for <aqm@ietfa.amsl.com>; Thu, 2 Apr 2015 14:49:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 Vw2a0_n3yEdc for <aqm@ietfa.amsl.com>; Thu, 2 Apr 2015 14:49:55 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22BB21A6FEE for <aqm@ietf.org>; Thu, 2 Apr 2015 14:49:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6909; q=dns/txt; s=iport; t=1428011395; x=1429220995; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=hS1kTA8m55417xoj5tNHvDKDfn5fCfpjl8tAtUu1lRQ=; b=SQaP946q4nWzWG5FPHIA1wf2DPkiUjH28jcv9WcxTTxKrma1vj4PUlbg UN7GwP2tmle2Q1e/HyCR7KpL8/geJL261pa+q3LmVNvD4BCLNRs9rw5Rd E6W8bWLmurubPS6yKhKdBNnXtq33Aq/Kiok+LzrUnXglHDskqxKY+xKes g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AxBQCnuB1V/5tdJa1QDIMIUlwFxVoKhX0CgUxMAQEBAQEBfoQeAQEBBAEBARpRCwwEAgEIDgMEAQEBJwcnCxQJCAEBBAENBYguAQ3NUwEBAQEBAQEBAQEBAQEBAQEBAQEBARMEiip/hBEBZwIFBoQnBYpxg1mCIIN1gieDZIEdgzSCXlWFR4M1g0giggMcgVBvAYFDfwEBAQ
X-IronPort-AV: E=Sophos;i="5.11,513,1422921600"; d="scan'208";a="137827683"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP; 02 Apr 2015 21:49:54 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t32LnsPA010538 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Apr 2015 21:49:54 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.109]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Thu, 2 Apr 2015 16:49:53 -0500
From: "Rong Pan (ropan)" <ropan@cisco.com>
To: Greg White <g.white@CableLabs.com>, Dave Dolson <ddolson@sandvine.com>, "Scheffenegger, Richard" <rs@netapp.com>, Mikael Abrahamsson <swmike@swm.pp.se>, Szilveszter Nadas <Szilveszter.Nadas@ericsson.com>
Thread-Topic: [aqm] adoption of draft-white-aqm-docsis-pie-01
Thread-Index: AdBR0qmLD+JlLAXWSZym1tRD+kojwQXBCieAAIs1spAAoLDJAP//74WA
Date: Thu, 2 Apr 2015 21:49:53 +0000
Message-ID: <D143071B.DA34%ropan@cisco.com>
References: <96cffe6791f54a67ae6b6359de6a3d6e@hioexcmbx05-prd.hq.netapp.com> <e9e3d9dc0435474283180936c371e0db@hioexcmbx05-prd.hq.netapp.com> <E8355113905631478EFF04F5AA706E9830BB08C1@wtl-exchp-2.sandvine.com> <D142ED5C.47F52%g.white@cablelabs.com>
In-Reply-To: <D142ED5C.47F52%g.white@cablelabs.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [171.70.247.185]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <680A089E985D444C9715132B5341A79A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/LxahrRMWqXGTYy3ML895_YJ61pY>
Cc: "'aqm@ietf.org'" <aqm@ietf.org>, "aqm-chairs@tools.ietf.org" <aqm-chairs@tools.ietf.org>
Subject: Re: [aqm] adoption of draft-white-aqm-docsis-pie-01
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Apr 2015 21:49:57 -0000

Greg,

Good suggestion of keeping DOCSIS-PIE and PIE drafts consistent. Let's
sync up and make sure they are consistent.

Thanks,

Rong

On 4/2/15 1:48 PM, "Greg White" <g.white@CableLabs.com> wrote:

>Thanks for the review Dave.
>
>I double checked with Rong, and the exponential decay of drop probability
>was inadvertently removed from the PIE pseudocode (I think she mentioned
>this in the other thread as well).
>
>In terms of enable/disable, there are two aspects.  One is that the
>DOCSIS-PIE algorithm is enabled by default, but can be disabled via
>explicit configuration by the network operator. The other is that the PIE
>algorithm has a built-in concept of being ACTIVE vs INACTIVE.  In the
>pseudocode of the PIE draft these capitalized terms are used, but in the
>description in section 5.1 of the PIE draft, this same functionality is
>referred to as "Turning PIE on and off".  Maybe this is an opportunity to
>clean up the language in the PIE draft so it is more consistent.
>DOCSIS-PIE supports the Active/Inactive aspect, but makes some adjustments
>to the logic from what is included in the PIE pseudocode (and uses
>different terminology).  I'll add a section that describes the deltas
>there and also I'll try to re-align the terminology in the DOCSIS-PIE
>pseudocode so that it matches PIE.
>
>-Greg
>
>
>On 4/1/15, 2:51 PM, "Dave Dolson" <ddolson@sandvine.com> wrote:
>
>>I'm also reviewing draft-ietf-aqm-docsis-pie-00
>>(https://tools.ietf.org/html/draft-ietf-aqm-docsis-pie-00)
>>
>>In section 3.4, an exponential delay aspect of PIE is mentioned. I just
>>read https://tools.ietf.org/html/draft-ietf-aqm-pie-00 and saw no mention
>>of this exponential delay. Did I miss it, or is it a mistake for the
>>docsis document to reference this?
>>
>>
>>draft-ietf-aqm-docsis-pie-00 documents enabling and disabling of PIE
>>control. Is enable/disable used with docsis-pie, or is it always on?
>>
>>
>>Otherwise, the document seems to contain enough information to document
>>docsis-pie.
>>The algorithm in section A.2 has quite a few aspects that are not
>>explained, but it seems precise.
>>(I don't have the knowledge to comment on whether it is accurate.)
>>
>>
>>-Dave
>>
>>
>>-----Original Message-----
>>From: Scheffenegger, Richard [mailto:rs@netapp.com]
>>Sent: Friday, March 27, 2015 5:53 PM
>>To: Greg White; Mikael Abrahamsson; Dave Dolson; Szilveszter Nadas
>>Cc: aqm-chairs@tools.ietf.org; 'aqm@ietf.org'
>>Subject: RE: [aqm] adoption of draft-white-aqm-docsis-pie-01
>>
>>Hi group,
>>
>>as there haven't been any objections, but some indications of support on
>>the list, and based on the responses in the IETF92 meeting in Dallas, we
>>chairs think this document can be adopted as WG-item at this time.
>>
>>
>>Greg, can you please upload the most recent version as
>>draft-ietf-aqm-docsis-pie-00?
>>
>>Also, as mentioned in the meeting, and to make true of my promise, I
>>would like to invite the following individuals to review this draft, once
>>the updated version becomes available.
>>
>>Mikael Abrahamsson
>>Dave Dolson
>>Szilveszter Nádas
>>
>>Mostly everybody else who has commented during the meeting is already
>>assigned to other documents (Nobody will be left out :)
>>
>>Thanks,
>>  Richard (co-chair)
>>
>>
>>
>>> -----Original Message-----
>>> From: aqm [mailto:aqm-bounces@ietf.org] On Behalf Of Scheffenegger,
>>> Richard
>>> Sent: Donnerstag, 26. Februar 2015 08:45
>>> To: Greg White; 'aqm@ietf.org'
>>> Cc: Rong Pan (ropan); aqm-chairs@tools.ietf.org
>>> Subject: Re: [aqm] adoption of draft-white-aqm-docsis-pie-01
>>> 
>>> Hi Greg, group,
>>> 
>>> 
>>> 
>>> Regarding the adoption call, this is something we can actually (and
>>> should) start on the list.
>>> 
>>> We can confirm that during the Dallas meeting in the room, but even
>>>before
>>> that, we'd like to get responses on the list now...
>>> 
>>> Perhaps we have some volunteers to review this new version as well...
>>> 
>>> 
>>> Best regards,
>>>   Richard
>>> 
>>> 
>>> 
>>> > -----Original Message-----
>>> > From: Greg White [mailto:g.white@CableLabs.com]
>>> > Sent: Donnerstag, 26. Februar 2015 01:13
>>> > To: aqm-chairs@tools.ietf.org
>>> > Cc: Rong Pan (ropan)
>>> > Subject: Re: [aqm] agenda for IETF 92 / Dallas
>>> >
>>> > Wes & Richard,
>>> >
>>> > Unfortunately I will not be at IETF92 in person, but will attend
>>> remotely.
>>> >  For draft-white-aqm-docsis-pie, Rong & I updated it in January and
>>> > included a new appendix to give a change log, which reads:
>>> >
>>> > ===============
>>> > Appendix B.  Change Log
>>> > B.1.  Since draft-white-aqm-docsis-pie-01
>>> >
>>> >    Added Change Log.
>>> >
>>> >    Removed discussion of Packet drop de-randomization, Enhanced burst
>>> >    protection, and 16ms update interval, as these are now included in
>>> >    [I-D.ietf-aqm-pie].
>>> >
>>> > ===============
>>> >
>>> >
>>> > Regarding WG adoption, I saw some support from Lars (and no
>>>objections)
>>> to
>>> > adopting it on an Informational track.   Will you do an official
>>> adoption
>>> > call at the Dallas meeting?
>>> >
>>> > -Greg
>>> >
>>> >
>>> > On 2/23/15, 8:40 PM, "Wesley Eddy" <wes@mti-systems.com> wrote:
>>> >
>>> > >Greetings AQMers!  We requested a short AQM meeting slot at the
>>> > >upcoming IETF 92 meeting in Dallas, and we received a 1-hour slot on
>>> Tuesday:
>>> > >https://datatracker.ietf.org/meeting/92/agenda.html
>>> > >
>>> > >Since this is not a lot of time, we'll need to prioritize the work
>>> > >that is discussed to what requires the face-to-face time in order to
>>> > >make progress on.
>>> > >
>>> > >For active draft editors, please let us know via this list or
>>> > >aqm-chairs@tools.ietf.org what you think your meeting time needs
>>>are,
>>> > >so we can put together an agenda.  If you don't need meeting time
>>> > >now, or would like to use an interim telecon to assist in gathering
>>> > >feedback, please also let us know.
>>> > >
>>> > >For others, please read the drafts, comment on this mailing list,
>>>and
>>> > >help us to review and complete them:
>>> > >https://datatracker.ietf.org/wg/aqm/documents/
>>> > >
>>> > >Thanks in advance!
>>> > >
>>> > >--
>>> > >Wes Eddy
>>> > >MTI Systems
>>> > >
>>> > >_______________________________________________
>>> > >aqm mailing list
>>> > >aqm@ietf.org
>>> > >https://www.ietf.org/mailman/listinfo/aqm
>>> 
>>> _______________________________________________
>>> 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