[re-ECN] Problem Statement (was Re: Pls bash: Congestion Exposure (re-ECN) BoF inHiroshima?)
ken carlberg <carlberg@g11.org.uk> Wed, 09 September 2009 12:26 UTC
Return-Path: <carlberg@g11.org.uk>
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 C62DD3A6B35 for <re-ecn@core3.amsl.com>;
Wed, 9 Sep 2009 05:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level:
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.232,
BAYES_00=-2.599]
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 NTImcRTaL6er for
<re-ecn@core3.amsl.com>; Wed, 9 Sep 2009 05:26:53 -0700 (PDT)
Received: from portland.eukhost.com (portland.eukhost.com [92.48.97.5]) by
core3.amsl.com (Postfix) with ESMTP id CBF733A6B39 for <re-ecn@ietf.org>;
Wed, 9 Sep 2009 05:26:53 -0700 (PDT)
Received: from c-76-111-69-4.hsd1.va.comcast.net ([76.111.69.4]:50258
helo=[192.168.0.20]) by portland.eukhost.com with esmtpa (Exim 4.69)
(envelope-from <carlberg@g11.org.uk>) id 1MlMGf-0004OR-N4;
Wed, 09 Sep 2009 12:27:21 +0000
Message-Id: <0B4C3431-5236-40BE-B5AB-9350A4826323@g11.org.uk>
From: ken carlberg <carlberg@g11.org.uk>
To: <toby.moncaster@bt.com> <toby.moncaster@bt.com>
In-Reply-To: <AEDCAF87EEC94F49BA92EBDD49854CC70CF81B7E@E03MVZ1-UKDY.domain1.systemhost.net>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 9 Sep 2009 08:27:23 -0400
References: <200909071019.n87AJgBB030579@bagheera.jungle.bt.co.uk><AEDCAF87EEC94F49BA92EBDD49854CC70CEB8418@E03MVZ1-UKDY.domain1.systemhost.net><8A82D1BFEDDE7E4597978355239BBBCB04389F@PACDCEXCMB06.cable.comcast.com><AEDCAF87EEC94F49BA92EBDD49854CC70CF2B7C9@E03MVZ1-UKDY.domain1.systemhost.net><20090907164107.GR8532@verdi><AEDCAF87EEC94F49BA92EBDD49854CC70CF2B885@E03MVZ1-UKDY.domain1.systemhost.net><200909080035.n880Zs1t012039@bagheera.jungle.bt.co.uk><AEDCAF87EEC94F49BA92EBDD49854CC70CF2BAD1@E03MVZ1-UKDY.domain1.systemhost.net><7D6FD9F3-B80E-4227-B215-EA22F20552CF@g11.org.uk>
<AEDCAF87EEC94F49BA92EBDD49854CC70CF2BCE5@E03MVZ1-UKDY.domain1.systemhost.net>
<AEDCAF87EEC94F49BA92EBDD49854CC70CF81803@E03MVZ1-UKDY.domain1.systemhost.net>
<6d30817f6dade196cfbb63326fc12bcb@petri-meat.com>
<AEDCAF87EEC94F49BA92EBDD49854CC70CF81B7E@E03MVZ1-UKDY.domain1.systemhost.net>
X-Mailer: Apple Mail (2.936)
X-AntiAbuse: This header was added to track abuse,
please include it with any abuse report
X-AntiAbuse: Primary Hostname - portland.eukhost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - g11.org.uk
Cc: re-ecn@ietf.org
Subject: [re-ECN] Problem Statement (was Re: Pls bash: Congestion Exposure
(re-ECN) BoF inHiroshima?)
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: Wed, 09 Sep 2009 12:26:54 -0000
Toby, here are some comments/questions as food for thought... > One of the strengths of the Internet is its ability to share > capacity and avoid congestion collapse by using distributed > algorithms executed on its end-hosts. While the resulting > allocation of capacity is fair in a certain mathematical sense, it > is not necessarily fair in other economic or philosophical senses. is "fairness" also determined by temporal qualities?...instantaneous condition versus some period of time, or accumulated accounting. > Further, end-hosts have means to "game the system" to increase their > access to capacity, and to progress communications even in the > presence of persistent congestion. As a consequence ISPs feel they > have to police "heavy users" to free up resources for the bulk of > their customers. This involves making assumptions about the wishes > of their customers which in turn is eroding trust between ISPs, > customers, content providers and application writers. > > ISPs have a variety of measures available to them to reduce > congestion, or to skew access to capacity amongst their users, > ranging from the complex (per-user fair queuing, volume-based > billing) to the crude (per-application prioritization or rate > capping). A problem with such mechanisms is that they control the > wrong quantity: it is not the total volume or absolute rate of > traffic of a particular user or application that impedes service to > other users; rather, it is the excess traffic that causes others to > experience congestion that is the real problem. at the risk of being picky, what is considered "excess traffic"? Is it traffic beyond that negotiated or configured per aggregate or application, or some standard deviation above previous traffic levels of a flow? As a reviewer, I could easily find myself asking "excess in relation to what?" > Current work at the IETF [LEDBAT, ALTO] and IRTF [ICCRG] is looking > at new approaches for controlling bulk data transfer rates. But > ISPs have no means for enforcing their use and indeed may even be > hindering their deployment through their crude attempts at traffic > control. This means the ISPs still have an incentive to deploy the > flawed tools at their disposal to manage capacity and reduce > congestion. What ISPs lack is a way to measure or even see the > congestion caused by a user’s excess traffic on an end-to-end > basis. Such a measure could be used to build trust between > operators and end-users and between different tiers of operators. In > short the Internet lacks a system for accountability if you are making an argument for "trust" between operators and end- users, don't you have to advocate complimentary efforts like integrity? Or is Security (other than recognizing its importance) outside the scope of the BoF? Finally, I'd also shy away from bringing up PCN at this point. There is no dependency on it, and I think its best not to increase the probability of confusing reviewers that have just a few cycles to read and decide what is being proposed. But I like what has been written so far. -ken
- [re-ECN] Pls bash: Congestion Exposure (re-ECN) B… Bob Briscoe
- [re-ECN] Fwd: Pls bash: Congestion Exposure (re-E… Bob Briscoe
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… toby.moncaster
- Re: [re-ECN] Fwd: Pls bash: Congestion Exposure (… toby.moncaster
- Re: [re-ECN] Fwd: Pls bash: Congestion Exposure (… marcelo bagnulo braun
- Re: [re-ECN] Fwd: Pls bash: Congestion Exposure (… Agarwal, Anil
- Re: [re-ECN] Fwd: Pls bash: Congestion Exposure (… Steven Blake
- Re: [re-ECN] Fwd: Pls bash: Congestion Exposure (… Bob Briscoe
- [re-ECN] Fwd: Pls bash: Congestion Exposure (re-E… Bob Briscoe
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… toby.moncaster
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… toby.moncaster
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… João Taveira Araújo
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… Woundy, Richard
- Re: [re-ECN] Fwd: Pls bash: Congestion Exposure (… arnaud.jacquet
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… toby.moncaster
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… John Leslie
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… toby.moncaster
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… Bob Briscoe
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… Bob Briscoe
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… toby.moncaster
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… Mirja Kuehlewind
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… Mirja Kuehlewind
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… ken carlberg
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… toby.moncaster
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… Bob Briscoe
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… toby.moncaster
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… João Taveira Araújo
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… slblake
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… toby.moncaster
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… Steven Blake
- [re-ECN] Problem Statement (was Re: Pls bash: Con… ken carlberg
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… Steven Blake
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… Bob Briscoe
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… toby.moncaster
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… João Taveira Araújo
- Re: [re-ECN] Pls bash: Congestion Exposure (re-EC… toby.moncaster