Re: [re-ECN] Viability issue #1
John Leslie <john@jlc.net> Fri, 06 November 2009 14:52 UTC
Return-Path: <john@jlc.net>
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 11BFE3A684D for <re-ecn@core3.amsl.com>;
Fri, 6 Nov 2009 06:52:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.494
X-Spam-Level:
X-Spam-Status: No, score=-6.494 tagged_above=-999 required=5 tests=[AWL=0.105,
BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 e3cmBOsPk8Qu for
<re-ecn@core3.amsl.com>; Fri, 6 Nov 2009 06:52:09 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.9]) by
core3.amsl.com (Postfix) with ESMTP id 4BF443A67D6 for <re-ecn@ietf.org>;
Fri, 6 Nov 2009 06:52:09 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 5A12433C98;
Fri, 6 Nov 2009 09:52:25 -0500 (EST)
Date: Fri, 6 Nov 2009 09:52:25 -0500
From: John Leslie <john@jlc.net>
To: Leslie Daigle <leslie@thinkingcat.com>
Message-ID: <20091106145225.GI53843@verdi>
References: <4AF26B57.3030601@thinkingcat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AF26B57.3030601@thinkingcat.com>
User-Agent: Mutt/1.4.1i
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] Viability issue #1
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: Fri, 06 Nov 2009 14:52:13 -0000
Leslie Daigle <leslie@thinkingcat.com> wrote: > > 1/ This is about network flows, not applications or services, so it will > serve future network uses (application types). The idea is right -- but it's hard to comprehend. Rather than "about", I'd say CONEX distinguishes "congestion" within the forwarding networks from application or services congestion. We probably also need to introduce the point that at every forwarding step, there's an indication of how much "congestion" is expected from the flow of packets heading toward that path (one RTT ago). And rather than some vague "future network uses", we should perhaps mention delay-sensitive traffic (which now isn't served at all well). (I wonder if we should start another thread on what "congestion" means: granted, CONEX is pretty agnostic on the actual meaning, but it feels to me as if folks need to escape the "congestion==packet-drop" mindset in order to understand how CONEX can help without giving "unfair" advantage to marked traffic.) -- John Leslie <john@jlc.net>
- [re-ECN] Viability issue #1 Leslie Daigle
- Re: [re-ECN] Viability issue #1 toby.moncaster
- Re: [re-ECN] Viability issue #1 John Leslie
- Re: [re-ECN] Viability issue #1 Leslie Daigle
- Re: [re-ECN] Viability issue #1 Matt Mathis