Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-04.txt

Simon Barber <simon@superduper.net> Sun, 24 May 2015 18:08 UTC

Return-Path: <simon@superduper.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 76F681ACD81 for <aqm@ietfa.amsl.com>; Sun, 24 May 2015 11:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.589
X-Spam-Level:
X-Spam-Status: No, score=0.589 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, J_CHICKENPOX_21=0.6, T_RP_MATCHES_RCVD=-0.01] 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 qF-AuTNp7RWO for <aqm@ietfa.amsl.com>; Sun, 24 May 2015 11:08:18 -0700 (PDT)
Received: from masada.superduper.net (masada.superduper.net [85.119.82.91]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FA241ACD7E for <aqm@ietf.org>; Sun, 24 May 2015 11:08:17 -0700 (PDT)
Received: from 199-116-72-167.public.monkeybrains.net ([199.116.72.167] helo=[192.168.0.7]) by masada.superduper.net with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <simon@superduper.net>) id 1YwaJn-0002qu-Lx; Sun, 24 May 2015 19:08:14 +0100
Message-ID: <5562138B.2050507@superduper.net>
Date: Sun, 24 May 2015 11:08:11 -0700
From: Simon Barber <simon@superduper.net>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <20140514180039.16149.79444.idtracker@ietfa.amsl.com> <554D8240.7050809@superduper.net> <20150510015811.GB53172@verdi> <5552CDA8.3040305@superduper.net> <alpine.DEB.2.02.1505131034140.32169@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1505131034140.32169@uplift.swm.pp.se>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/ZyzlU7mMqKavEsO9gQyUYlT5ThA>
Cc: John Leslie <john@jlc.net>, aqm@ietf.org
Subject: Re: [aqm] I-D Action: draft-ietf-aqm-recommendation-04.txt
X-BeenThere: aqm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for active queue management and flow isolation." <aqm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/aqm>, <mailto:aqm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/aqm/>
List-Post: <mailto:aqm@ietf.org>
List-Help: <mailto:aqm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/aqm>, <mailto:aqm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 May 2015 18:08:22 -0000

Hi Mikael,

I can't find reference to DSCP 000010 or 000110, where are they defined?

I know the title 'assured forwarding' seems to imply better than best 
effort, but I think this is a mistake for AF1 - which seems to be 
recommended for bulk traffic that is not latency sensitive. You can't 
make everything high priority! I believe AF1 according to the list of 
recommended applications, would be better served at less than best 
effort priority - so the 4 queue 1a mapping based on the top 3 bits of 
the TOS byte would be OK. AF2 -> lower than best effort would be wrong 
however.

Simon


On 5/13/2015 1:47 AM, Mikael Abrahamsson wrote:
> On Tue, 12 May 2015, Simon Barber wrote:
>
>> Hi John,
>>
>> Where would be the best place to see if it would be possible to get 
>> agreement on a global low priority DSCP?
>
> Currently the general assumption among ISPs is that DSCP should be 
> zeroed between ISPs unless there is a commercial agreement saying that 
> it shouldn't. This is generally accepted (there are NANOG mailing list 
> threads on several occasions in the past 5-10 years where this was the 
> outcome).
>
> The problem is quite complex if you actually want things to act on 
> this DSCP value, as there are devices with default behaviour is 4 
> queue 802.1p, with 1 and 2 (which will match AF1x and AF2x) will have 
> lower priority than 0 and 3 (BE and AF3x), and people doing DSCP based 
> forwarding, usually does things the other way around.
>
> It might be possible to get the last DSCP bits to map into this, 
> because for DSCP-ignorant quipment, this would still be standard BE to 
> something only looking at CSx (precedence), but that would be lower 
> than 000000. So DSCP 000110 (high drop BE) might work, because it's 
> incremental. Possibly DSCP 000010 (low drop BE) might be able to get 
> some agreement because it doesn't really cause any problems in the 
> existing networks (most likely) and it could be enabled incrementally.
>
> I would suggest bringing this kind of proposal to operator 
> organizations and the IETF. It needs to get sold to the ISPs mostly, 
> because in this aspect the IETF decision will mostly be empty 
> hand-waving unless the operators do something.
>