Re: [aqm] Alia Atlas' Yes on draft-ietf-aqm-fq-implementation-03: (with COMMENT)

"Fred Baker (fred)" <fred@cisco.com> Thu, 22 October 2015 16:07 UTC

Return-Path: <fred@cisco.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A8451B3876; Thu, 22 Oct 2015 09:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.51
X-Spam-Level:
X-Spam-Status: No, score=-114.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id heibDB7Noafq; Thu, 22 Oct 2015 09:07:19 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5B291A0137; Thu, 22 Oct 2015 09:07:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11540; q=dns/txt; s=iport; t=1445530039; x=1446739639; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=DZX49RfDhyw/92k+VXkoIUyX5cjAEhpELF3KISvnxW4=; b=O/0bJM+SI8kmZh2x6FMim6cu+qZIV8WUsG3IvKOH2Y2XKIoqc2+iJFv5 p+ov3S9urfMNf0Kir3C0vbsfLWtA8NIVC4FqRti5rimogCuVH5ZyRMZTW dNIpajfeidQxt8mlZarwOL9QVj3e4B2zsD7plBrYgq7WY/wXyEd3KAG47 0=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CxAgCQCClW/49dJa1egzZUbwa5d4QhDoFZIYV8AoFFOBQBAQEBAQEBgQqELgEBAQMBeQULAgEIDgonByERFBECBA4FDogNAwoIDcBBDYRnAQEBAQEBAQEBAQEBAQEBAQEBAQEBDwmJB4JuglCBWhEBTQQHgxqBFAWHQI5rAYJNgWFqhhCBdYFYhD+DJIseg12DbwEfAUOCRIE/cgGFAjqBBgEBAQ
X-IronPort-AV: E=Sophos;i="5.20,183,1444694400"; d="asc'?scan'208,217";a="43519787"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-3.cisco.com with ESMTP; 22 Oct 2015 16:07:17 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t9MG7HhO021948 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 22 Oct 2015 16:07:17 GMT
Received: from xch-aln-013.cisco.com (173.36.7.23) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 22 Oct 2015 11:06:57 -0500
Received: from xch-aln-013.cisco.com ([173.36.7.23]) by XCH-ALN-013.cisco.com ([173.36.7.23]) with mapi id 15.00.1104.000; Thu, 22 Oct 2015 11:06:57 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Alia Atlas <akatlas@gmail.com>
Thread-Topic: [aqm] Alia Atlas' Yes on draft-ietf-aqm-fq-implementation-03: (with COMMENT)
Thread-Index: AQHRDOOsMEzKEVrvZEq8V8EevQ08IA==
Date: Thu, 22 Oct 2015 16:06:56 +0000
Message-ID: <4299F160-7A02-48FA-BC05-B9F3BC045E5A@cisco.com>
References: <20151021222220.6495.73596.idtracker@ietfa.amsl.com> <46491C99-5218-42E2-A088-EAF8892D8706@cisco.com> <CAG4d1re7Rytoj2rvC-htEm3fHB7YLx0JXmt6Eo6K2dG1_MGQyQ@mail.gmail.com>
In-Reply-To: <CAG4d1re7Rytoj2rvC-htEm3fHB7YLx0JXmt6Eo6K2dG1_MGQyQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.183.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_AA560109-6CC8-4D04-9DA5-98E0A1F89A2F"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/YvhBmiGd7Aztph-4rNOw_cqOfaI>
Cc: "draft-ietf-aqm-fq-implementation@ietf.org" <draft-ietf-aqm-fq-implementation@ietf.org>, Wesley Eddy <wes@mti-systems.com>, AQM IETF list <aqm@ietf.org>, The IESG <iesg@ietf.org>, "aqm-chairs@ietf.org" <aqm-chairs@ietf.org>
Subject: Re: [aqm] Alia Atlas' Yes on draft-ietf-aqm-fq-implementation-03: (with COMMENT)
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <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, 22 Oct 2015 16:07:21 -0000

> On Oct 22, 2015, at 12:01 PM, Alia Atlas <akatlas@gmail.com> wrote:
> 
> Fred,
> 
> What I am saying is that I have worked with and verified implementations of
> Weighted Fair Queuing - and it is not Calendar Queues - certainly not as this
> draft describes it.  Can you please provide a reference to what Weighted Fair
> Queues means - if it isn't Weighted Fair Queuing, or fix the draft's description
> (which could be merely mentioning Weighted Fair Queuing as a different
> work-conserving approach).
> 
> I realize that this is tangential to the point of the draft (or it would have been
> a Discuss), but I still would strongly prefer accuracy.

I can include a link to http://www.isi.edu/nsnam/ns/doc/node643.html#Brow88:Calendar <http://www.isi.edu/nsnam/ns/doc/node643.html#Brow88:Calendar> if that helps.

> Regards,
> Alia
> 
> On Thu, Oct 22, 2015 at 11:57 AM, Fred Baker (fred) <fred@cisco.com <mailto:fred@cisco.com>> wrote:
> 
> > On Oct 21, 2015, at 6:22 PM, Alia Atlas <akatlas@gmail.com <mailto:akatlas@gmail.com>> wrote:
> >
> > Alia Atlas has entered the following ballot position for
> > draft-ietf-aqm-fq-implementation-03: Yes
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html <https://www.ietf.org/iesg/statement/discuss-criteria.html>
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-aqm-fq-implementation/ <https://datatracker.ietf.org/doc/draft-ietf-aqm-fq-implementation/>
> >
> >
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > Thank you for a clear and well-written draft.
> >
> > I would like to understand the reference of "Weighted Fair Queues" and have that clarified in the draft. It's a technical concern, but I have confidence that the authors and ADs will address it.
> >
> > 1) Sec 2.2.3 refers to "Weighted Fair Queues" as well as "Calendar Queues". Perhaps it is due to a lack in my recent background - but what's described is nothing like Weighted Fair Queuing (https://en.wikipedia.org/wiki/Weighted_fair_queueing <https://en.wikipedia.org/wiki/Weighted_fair_queueing>). Do you have a reference for "Weighted Fair Queues" or something else in mind??
> 
> Thanks for your question. The original intent of this draft was simply to support a discussion, which I expected might be closed without needing to publish an RFC. The working group decided that it wanted to adopt and publish the note, which is fine as well.
> 
> I think what you're looking at is the difference between theory and practice. As you know, in theory, they are the same thing, and in practice there can be important differences. If you read early papers, such as McKenny's SFQ or Lixia Zhang's Virtual Clock, they talk a lot about WRR-based implementations; calendar queues came later. But no real implementation I am aware of (I have written two and am aware of several others) attempts to implement GPS as the GPS paper describes it - nor does the GPS paper expect them to. That's why that section in the draft is titled "Approximations to GPS" - any implementation is necessarily an approximation, and GPS describes the theoretical best case they are trying to approximate.
>