Re: [re-ECN] RE-ECN without ECN.

Fred Baker <fred@cisco.com> Mon, 05 October 2009 22:04 UTC

Return-Path: <fred@cisco.com>
X-Original-To: re-ecn@core3.amsl.com
Delivered-To: re-ecn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B9303A6A51 for <re-ecn@core3.amsl.com>; Mon, 5 Oct 2009 15:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.201
X-Spam-Level:
X-Spam-Status: No, score=-106.201 tagged_above=-999 required=5 tests=[AWL=0.398, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uHCVCSOJsJNe for <re-ecn@core3.amsl.com>; Mon, 5 Oct 2009 15:04:29 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 8CFE13A67AB for <re-ecn@ietf.org>; Mon, 5 Oct 2009 15:04:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1936; q=dns/txt; s=sjiport06001; t=1254780365; x=1255989965; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Fred=20Baker=20<fred@cisco.com>|Subject:=20Re: =20[re-ECN]=20RE-ECN=20without=20ECN.|Date:=20Mon,=205=20 Oct=202009=2015:05:58=20-0700|Message-Id:=20<9433BE42-0D0 7-4A4B-A0F5-052AB7A0B841@cisco.com>|To:=20Matt=20Mathis =20<matt.mathis@gmail.com>|Cc:=20re-ecn@ietf.org |Mime-Version:=201.0=20(Apple=20Message=20framework=20v93 6)|Content-Transfer-Encoding:=207bit|In-Reply-To:=20<fc0f f13d0910051445s62397c5co6b2e2de94268e20e@mail.gmail.com> |References:=20<fc0ff13d0910010936i5aa26e6esd830c958422e3 40d@mail.gmail.com>=20<3558451F-5A22-4E76-B2AA-A38026ECC9 69@cisco.com>=20<fc0ff13d0910051445s62397c5co6b2e2de94268 e20e@mail.gmail.com>; bh=iyuteprJbx3mf0wDmBf0sUE0oizsXfnuUPt42DmknAQ=; b=h0kgcDrVlFG/7RzW03snAMvqWsjdjUbc+n+TGCWoRW9p+n+zLVBuYxCM EKTgEW31jnw1T/TzRDvmWeuJTTc5RpRcE2ue65MUG5OnIs2W0E81xCEnA DJS68XcaBggYw8zHTmIEZnGYj6IKTutKXLxlHS9tcvyqYtokPrNE1rCGH I=;
Authentication-Results: sj-iport-6.cisco.com; dkim=pass (signature verified [TEST]) header.i=fred@cisco.com
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAKcKykqrR7O6/2dsb2JhbAC7IohhAY4zBoI7gW8
X-IronPort-AV: E=Sophos;i="4.44,508,1249257600"; d="scan'208";a="402568615"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 05 Oct 2009 22:05:58 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n95M5wi5020333; Mon, 5 Oct 2009 15:05:58 -0700
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n95M5w7l004447; Mon, 5 Oct 2009 22:05:58 GMT
Message-Id: <9433BE42-0D07-4A4B-A0F5-052AB7A0B841@cisco.com>
From: Fred Baker <fred@cisco.com>
To: Matt Mathis <matt.mathis@gmail.com>
In-Reply-To: <fc0ff13d0910051445s62397c5co6b2e2de94268e20e@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 5 Oct 2009 15:05:58 -0700
References: <fc0ff13d0910010936i5aa26e6esd830c958422e340d@mail.gmail.com> <3558451F-5A22-4E76-B2AA-A38026ECC969@cisco.com> <fc0ff13d0910051445s62397c5co6b2e2de94268e20e@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1936; t=1254780358; x=1255644358; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fred@cisco.com; z=From:=20Fred=20Baker=20<fred@cisco.com> |Subject:=20Re=3A=20[re-ECN]=20RE-ECN=20without=20ECN. |Sender:=20; bh=iyuteprJbx3mf0wDmBf0sUE0oizsXfnuUPt42DmknAQ=; b=tJWluA39heboo0C+FDHW4S37vypiycQn2MnPSP0o/jKDoXcThusYxBtsVL 39a/8ZogcFRUgDt4+5GJP+wzOoghX4HC7dPxQOC2jfUK54HxmCEPNFEmU5Py dfGlrrKPWi;
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] RE-ECN without ECN.
X-BeenThere: re-ecn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: re-inserted explicit congestion notification <re-ecn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/re-ecn>, <mailto:re-ecn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/re-ecn>
List-Post: <mailto:re-ecn@ietf.org>
List-Help: <mailto:re-ecn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/re-ecn>, <mailto:re-ecn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2009 22:04:31 -0000

On Oct 5, 2009, at 2:45 PM, Matt Mathis wrote:

> On Mon, Oct 5, 2009 at 3:03 PM, Fred Baker <fred@cisco.com> wrote:
>>
>> On Oct 1, 2009, at 9:36 AM, Matt Mathis wrote:
>>
>>> If you add the assumption that the network itself does not reorder
>>> packets, then the number of out-of-order packets is a direct measure
>>> of the upstream congestion.  (e.g. the first transmission was lost,
>>> and I see the retransmission).
>>
>> The assumption concerns me. There are probably places in the  
>> Internet where
>> loss is unusual and reordering is unusual, but making it a baseline
>> assumption... The Internet is still a best effort service, which is  
>> to say
>> that datagrams may be lost, duplicated, or reordered.
>
> Reordering is not insurmountable.   Network reordering is most often
> bound by some fairly small maximum offset related to the number of
> parallel paths or processing stripes.  Retransmissions are always
> out-of-order by slightly more than one full window of data.   At small
> window/low rates these are indistinguishable, but it probably isn't as
> important  to get it right.   At higher rates, these are likely to be
> different by an order of magnitude or more.  My hunch would be that a
> pretty simple adaptive controller might do well enough.

Well, yes, they are bounded, but that doesn't make them without effect.

Take for example one case that some of my customers report to be  
fairly common - the use of multiple parallel DSL, Frame Relay, or ect  
circuits at some point in their network. We have several ways of  
dealing with such, including both PPP Multilink (which tries to  
distribute load approximately evenly) and IP equal cost multipath  
routing. The latter can be used in a round-robin fashion or by hashing  
addresses as described in some RFC. the issue there is that in cases  
where reordering happens, it can be sustained for a while.