Re: [aqm] 答复: [iccrg] [tcpm] ECN support and usage on the Internet

Mikael Abrahamsson <swmike@swm.pp.se> Wed, 20 March 2013 04:01 UTC

Return-Path: <swmike@swm.pp.se>
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 44DA421F8EF2; Tue, 19 Mar 2013 21:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.091
X-Spam-Level:
X-Spam-Status: No, score=0.091 tagged_above=-999 required=5 tests=[AWL=-2.155, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_GB2312=1.345]
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 Pa1z3GoIxTxq; Tue, 19 Mar 2013 21:01:24 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id A749921F8F22; Tue, 19 Mar 2013 21:01:24 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id A878A9C; Wed, 20 Mar 2013 05:01:22 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A37A79A; Wed, 20 Mar 2013 05:01:22 +0100 (CET)
Date: Wed, 20 Mar 2013 05:01:22 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Jim Gettys <jg@freedesktop.org>
In-Reply-To: <CAGhGL2AbSUvm-XcgH6y2gRy_hYj4mc4YU+u7LeuiCp0DzfsRDg@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1303200451270.2309@uplift.swm.pp.se>
References: <201303190904.32180.mkuehle@ikr.uni-stuttgart.de> <alpine.DEB.2.00.1303191014021.2309@uplift.swm.pp.se> <51487A27.7010904@hp.com> <CAGhGL2D=qncZZ0YG2jLfXwJLXLrXj4dXns_u66qPNBEVH2ZR4A@mail.gmail.com> <B2CE202A35DFDD4A904DA7497D7D2B9830F98A@CNHZ-EXMAIL-10.ali.com> <CAGhGL2AbSUvm-XcgH6y2gRy_hYj4mc4YU+u7LeuiCp0DzfsRDg@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Cc: "tcpm@ietf.org" <tcpm@ietf.org>, "aqm@ietf.org" <aqm@ietf.org>, "iccrg@irtf.org" <iccrg@irtf.org>
Subject: Re: [aqm] 答复: [iccrg] [tcpm] ECN support and usage on the Internet
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: Wed, 20 Mar 2013 04:01:25 -0000

On Tue, 19 Mar 2013, Jim Gettys wrote:

> I worry about bufferbloat in the HARQ layer of cellular networks not

This might be from just one vendor, but the Radio Link Control (RLC) layer 
on our equipment will buffer up to 400 packets before it does tail-drop. 
There might be additional buffering in GGSN/SGSN doing rate-shaping before 
it's even sent to the RNC (which terminates the RLC layer between the RNC 
and the end user terminal equipment). All this buffering is strict FIFO.

I personally belive that AQM at each of these buffering points would be 
beneficial to the end user equipment.

> My intuition is to get VOIP reliable over WiFI on a busy network (or 
> when far away from the AP) we'll want to classify the VOIP packets 
> anyway and use the right hardware class in WiFi; this is primarily to 
> get priority access to a transmit opportunity on WiFi rather than the 
> previous reasons we've had.  Certainly on other media we've seen little 
> reason to have to do any explicit classification for VOIP anymore once 
> running fq_codel.  Things generally "just work" without all that hair 
> for VOIP traffic.

I agree, fq_codel probably needs some DSCP handling so that VOIP packets 
(EF marked) would end up in a different hardware queue. For mobile, the 
bearer model would mean there would be an L4 inspection engine putting the 
traffic into the correct bearer anyway (that's the 3GPP way), so here 
codel probably wouldn't need to do anything (because there would be 
several codel instances running, one per bearer).

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