IETF Logo Mail Archive

Re: [aqm] Question re draft-baker-aqm-recommendations recomendation #4

"Fred Baker (fred)" <fred@cisco.com> Mon, 06 May 2013 16:49 UTC

Return-Path: <fred@cisco.com>
X-Original-To: aqm@ietfa.amsl.com
Delivered-To: aqm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 840BA21F90DF for <aqm@ietfa.amsl.com>; Mon, 6 May 2013 09:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.372
X-Spam-Level:
X-Spam-Status: No, score=-110.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k+vi97YQRbL6 for <aqm@ietfa.amsl.com>; Mon, 6 May 2013 09:49:06 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id A222421F90B1 for <aqm@ietf.org>; Mon, 6 May 2013 09:49:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2163; q=dns/txt; s=iport; t=1367858946; x=1369068546; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=9YHVV7+dWmhANfsG9ObKYD03cNskbPNs9wkScd5f1Ew=; b=lCK222NIbJkiRE2gDJhrN+pw6ScVkjEAH/2O0lkxVl2gBoTcSvxem/Am 80rKbUzN7/EK1zKWMa8YlyrQKj+XnASPtGgsKVDGHVmq6HBTZMP5JS2zM HGm3qTe6uaMc9eRYElXpiEpKlj/NV3g4SxmY4LiunhNIdozCJTOw2pP6L o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAMHdh1GtJV2Y/2dsb2JhbABQgwc3vnyBAhZ0gh8BAQEDAQEBATc0CwULAgEIDgoKFBAnCyUCBA4FCId+Bgy/bI5+AjEHgnJhA5NfhHWQDoMNgic
X-IronPort-AV: E=Sophos;i="4.87,622,1363132800"; d="scan'208";a="206973149"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-6.cisco.com with ESMTP; 06 May 2013 16:49:06 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r46Gn6Te012608 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 May 2013 16:49:06 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.125]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Mon, 6 May 2013 11:49:05 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Michael Welzl <michawe@ifi.uio.no>
Thread-Topic: [aqm] Question re draft-baker-aqm-recommendations recomendation #4
Thread-Index: AQHOSnmeXY+bsHW5GUOsXJsz145jDQ==
Date: Mon, 06 May 2013 16:49:05 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B8512B5@xmb-rcd-x09.cisco.com>
References: <8C48B86A895913448548E6D15DA7553B850ECE@xmb-rcd-x09.cisco.com> <41E8D91E-658B-4B44-92D2-5EB0329781A5@ifi.uio.no>
In-Reply-To: <41E8D91E-658B-4B44-92D2-5EB0329781A5@ifi.uio.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.116]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F4667653811B9B439C13408796C16338@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] Question re draft-baker-aqm-recommendations recomendation #4
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2013 16:49:11 -0000

On May 6, 2013, at 7:25 AM, Michael Welzl <michawe@ifi.uio.no> wrote:

> Hi,
> 
> First of all, I'd like to say that I agree with all the recommendations you asked about so far. I hesitated to answer as I wasn't sure if a ton of "yes I do" responses are useful?!
> 
> About this recommendation, I agree regarding what it actually recommends, but I have a comment about the wording. This bit:
> 
> "Hence, Active Queue Management algorithms that are effective with all of those transports and the applications that use them are to be preferred."
> 
> sounds as if it would be the most normal thing in the world for an AQM algorithm to make a decision based on the transport protocol, which I think it shouldn't. To me, ECN is an IP-layer signal and routers shouldn't have to investigate what's layered on it (which may go beyond just looking at the "protocol" field in case of tunnels) in order to make their decisions.

Thanks. I certainly agree that we should not be making transport-specific modifications; that was one thing that bothered me with cones, that it seemed to expect a different ECN encoding based on the DSCP. My point in this, if you can think of a better way to phrase it, is that the AQM algorithm someone implements needs to demonstrably work with the transports and applications it will be affecting.

> I tried to come up with a better phrasing but failed... maybe it could be an idea to just add a sentence after this one, saying something like "Such algorithms do not need to consider any information in the packet beyond its IP header."
> 
> Cheers,
> Michael
> 
> 
> On 6. mai 2013, at 16:00, Fred Baker (fred) wrote:
> 
>> Do we generally agree with the recommendation of http://tools.ietf.org/html/draft-baker-aqm-recommendation-01#section-4.4? This is the question of ensuring that AQM technologies are applicable to all Internet traffic - not just TCP, but UDP, SCTP, and so on.
>> 
>> 
>> _______________________________________________
>> aqm mailing list
>> aqm@ietf.org
>> https://www.ietf.org/mailman/listinfo/aqm
>

v2.23.0 | Report a Bug | By Email