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

Mikael Abrahamsson <swmike@swm.pp.se> Wed, 13 May 2015 08:47 UTC

Return-Path: <swmike@swm.pp.se>
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 641581A92B8 for <aqm@ietfa.amsl.com>; Wed, 13 May 2015 01:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.361
X-Spam-Level:
X-Spam-Status: No, score=-3.361 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_SE=0.35, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 yfB7N6AesRxt for <aqm@ietfa.amsl.com>; Wed, 13 May 2015 01:47:25 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E2331A92AE for <aqm@ietf.org>; Wed, 13 May 2015 01:47:25 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id DD5EDA2; Wed, 13 May 2015 10:47:22 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1431506842; bh=2CRzxhODPN2ROEMQ+Y061odiBBJkQJf3KK1JW7QA/h4=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=mA05e212znT4b+bJHElGBpZoJyRO16/C9ICfKf/USHe2+ySBA/5wCQJOgUBRlonDy 2VAMOyaA/4hJwBYEnnmXm7arkGLxlXcWfqsEyzYmDe3VD0ipqAnfbfg78ZRpJHvvIx 4UJGb+F86vunxNW+kwZYMbxOn3t6SPts71n8S2Gc=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D859CA1; Wed, 13 May 2015 10:47:22 +0200 (CEST)
Date: Wed, 13 May 2015 10:47:22 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Simon Barber <simon@superduper.net>
In-Reply-To: <5552CDA8.3040305@superduper.net>
Message-ID: <alpine.DEB.2.02.1505131034140.32169@uplift.swm.pp.se>
References: <20140514180039.16149.79444.idtracker@ietfa.amsl.com> <554D8240.7050809@superduper.net> <20150510015811.GB53172@verdi> <5552CDA8.3040305@superduper.net>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/zNbiGhrX16hBDA9-TJunM7rVktw>
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: Wed, 13 May 2015 08:47:27 -0000

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.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se