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

John Leslie <john@jlc.net> Thu, 02 May 2013 16:44 UTC

Return-Path: <john@jlc.net>
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 23E7921F85C3 for <aqm@ietfa.amsl.com>; Thu, 2 May 2013 09:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.372
X-Spam-Level:
X-Spam-Status: No, score=-106.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 xlqwqNjNGF9b for <aqm@ietfa.amsl.com>; Thu, 2 May 2013 09:43:59 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id DF52F21F8437 for <aqm@ietf.org>; Thu, 2 May 2013 09:43:58 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id CC9F133C26; Thu, 2 May 2013 12:43:58 -0400 (EDT)
Date: Thu, 02 May 2013 12:43:58 -0400
From: John Leslie <john@jlc.net>
To: Wesley Eddy <wes@mti-systems.com>
Message-ID: <20130502164358.GF23227@verdi>
References: <8C48B86A895913448548E6D15DA7553B82A5E5@xmb-rcd-x09.cisco.com> <517FF171.4010306@mti-systems.com> <4A95BA014132FF49AE685FAB4B9F17F645B16159@dfweml509-mbx.china.huawei.com> <5181D8E2.1040306@mti-systems.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <5181D8E2.1040306@mti-systems.com>
User-Agent: Mutt/1.4.1i
Cc: aqm@ietf.org, Linda Dunbar <linda.dunbar@huawei.com>
Subject: Re: [aqm] Question re draft-baker-aqm-recommendations recomendation #2
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: Thu, 02 May 2013 16:44:04 -0000

Wesley Eddy <wes@mti-systems.com> wrote:
> On 4/30/2013 6:17 PM, Linda Dunbar wrote:
>> 
>> Do you mean that downstream nodes treat packets with ECN bits marked
>> differently than that packets whose ECN bits are not marked? 
>> In another words, is "congestion experienced (CE)" encoded in the packets? 
> 
>... all that it's saying is that the congested queue set the CE bit
> (when ECT is set), per normal ECN protocol. It isn't saying anything
> new about the downstream nodes that see CE has already been set.

   A downstream node _could_ treat the packet differently: it wouldn't
matter much for what we're interested in.

   Note that a downstream node could reasonably drop a packet already
CE-marked if that node _also_ is congested. It wouldn't actually help
IMHO if the flow containing the marked packet is well-behaved; but
there's really no way to tell whether the flow is well-behaved.

   With room for doubt, it's arguably right to drop it at an even
lighter level of congestion: in all reasonable cases of two or more
nodes congested on the path, we should expect another packet to come
along _not_ already CE-marked.

   (I'm not actually proposing this -- least of all proposing to
_standardize_ this; but perhaps it will help folks to think through
the issue.)

   In some future "perfect world", where CE can mark packets _before_
there is any reason to drop any, I might talk about standardizing
such a practice. ;^)

--
John Leslie <john@jlc.net>