Re: [aqm] ECT(1)

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 06 August 2015 20:39 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 2B7011A0193 for <aqm@ietfa.amsl.com>; Thu, 6 Aug 2015 13:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level:
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, 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 lyKHMQZMDLb5 for <aqm@ietfa.amsl.com>; Thu, 6 Aug 2015 13:38:59 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49EFB1A017F for <aqm@ietf.org>; Thu, 6 Aug 2015 13:38:59 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 611E2A2; Thu, 6 Aug 2015 22:38:55 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1438893535; bh=rCBFeVrhuUbDXlSL9FhjDT0zYfXVht7lSiZi6pEHZpc=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=wK04VC/xHabmMUMfPxU8ZNQFcxEJ25MgdJzJcbJZOib0qdBMc+8OzJP2EkYLf/y75 uN6GhLdwAZXLxjnRw7LW/shKuQKfhNNBIo29SOsXnyGfy3hEgDR4QRoaRiHm9Wr51z PaGWif5CFHrwZqzmqVFdBBgqEAAZF9Qeg+LCM2oY=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 5D8FFA1; Thu, 6 Aug 2015 22:38:55 +0200 (CEST)
Date: Thu, 06 Aug 2015 22:38:55 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Bob Briscoe <research@bobbriscoe.net>
In-Reply-To: <55BFF7EC.1010608@bobbriscoe.net>
Message-ID: <alpine.DEB.2.02.1508061242450.11810@uplift.swm.pp.se>
References: <ba3b6f6b4d3d453d887c451fbca412fa@hioexcmbx05-prd.hq.netapp.com> <CAA93jw5WrT0Azcew_gic5H-tJtBo62m-f4fBB0=qQp01uf3VuQ@mail.gmail.com> <8a1ed5a975d44a7bad88dc573971ded5@hioexcmbx05-prd.hq.netapp.com> <20150728145036.GK96964@verdi> <55BFF7EC.1010608@bobbriscoe.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; format="flowed"; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/aqm/CB5zY0Sne7VwgE1TLNly1wT1iOA>
Cc: "aqm@ietf.org" <aqm@ietf.org>
Subject: Re: [aqm] ECT(1)
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, 06 Aug 2015 20:39:01 -0000

On Tue, 4 Aug 2015, Bob Briscoe wrote:

> *Combining ECT(0) and CE with a globally assigned DSCP solely during initial 
> deployment of L4S seems the least worst choice.

Having the same bits in the header mean different things in combination 
with DSCP seems like a really hard to get deployed Internet-wide.

ECN is just now gaining traction and seems like it might actually see real 
deployment. Repurposing those bits just now would most likely just cause 
confusion.

I started using ECN when it first appeared in the Linux kernel around 2001 
or whenever it was. I had to immediately turn it off because some 
firewalls dropped those packets. Now almost 15 years later after this 
sitting in the operating systems for at least 10 years, we're now getting 
to a point where we're ready to start turning it on widely because things 
do not break when it's turned on.

So whatever you come up with now that requires host stack changes, expect 
5-10 years at least until it can be deployed. This means you have to be 
really sure this is what you actually want before you start to push for 
deployment. Also, deployment impacts should be taken a lot into account 
when deciding what to do.

So how sure are you that L4S as it currently stands is the way to go? If 
you think you're going to invent something new in 2-3 years, then please 
wait until then. Experimentation is all fine and dandy, but until we can 
actually get DSCP codepoints working on Internet-wide scale, this approach 
isn't feasable for that use-case (which for me is close to "the only" 
use-case).

My proposal has been before that we should try to get 7 DSCP codepoints 
deployed by using 000xxx, and nudge providers to incrementally just not 
bleach them and treat them as BE in their core networks, so we can use 
them on the edge to influence AQM there.

So, if we're going to invent new meaning of ECN bits in combination with 
DSCP, then that needs to be coupled with work of getting some DSCP working 
Internet-wide in a fashion that someone actually believes will work out, 
as in actually getting significant Internet-wide deployment.

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