Re: [re-ECN] Pls bash: Congestion Exposure (re-ECN) BoF inHiroshima?

João Taveira Araújo <j.araujo@ee.ucl.ac.uk> Thu, 10 September 2009 10:42 UTC

Return-Path: <j.araujo@ee.ucl.ac.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 A995E3A69F2 for <re-ecn@core3.amsl.com>; Thu, 10 Sep 2009 03:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level:
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 Z78MuXK+utH4 for <re-ecn@core3.amsl.com>; Thu, 10 Sep 2009 03:42:06 -0700 (PDT)
Received: from dax.ee.ucl.ac.uk (dax.ee.ucl.ac.uk [128.40.42.12]) by core3.amsl.com (Postfix) with ESMTP id 23F7E3A69D9 for <re-ecn@ietf.org>; Thu, 10 Sep 2009 03:42:05 -0700 (PDT)
Received: from [144.82.248.242] (dhcp-248-242.visi.ucl.ac.uk [144.82.248.242]) (authenticated bits=0) by dax.ee.ucl.ac.uk (8.13.8/8.13.8) with ESMTP id n8AAcwgx028878 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Sep 2009 11:39:05 +0100 (BST)
Message-ID: <4AA8D7F8.9090106@ee.ucl.ac.uk>
Date: Thu, 10 Sep 2009 11:42:00 +0100
From: =?UTF-8?B?Sm/Do28gVGF2ZWlyYSBBcmHDumpv?= <j.araujo@ee.ucl.ac.uk>
Organization: UCL
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: toby.moncaster@bt.com
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>
In-Reply-To: <AEDCAF87EEC94F49BA92EBDD49854CC70CF81B7E@E03MVZ1-UKDY.domain1.systemhost.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-UCL_EE-MailScanner-Information: Please contact mailhelp@ee.ucl.ac.uk for more information
X-MailScanner-ID: n8AAcwgx028878
X-UCL_EE-MailScanner: Found to be clean
X-UCL_EE-MailScanner-From: j.araujo@ee.ucl.ac.uk
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] 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: Thu, 10 Sep 2009 10:42:07 -0000

Hi,

toby.moncaster@bt.com wrote
>
> 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. 
>
> 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.

I'm not entirely sure people unfamiliar with the flow fairness debate 
will understand what "certain mathematical sense" means, or why it's 
suddenly an issue. Suggestion:

"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. The resulting capacity allocation has reflected a 
single definition of fairness however, and has remained inflexible in 
adapting to differing needs as the Internet has scaled to include new 
and often conflicting stakeholders."

I'm fine with the second paragraph, but if you want to avoid the "game 
the system" bit here's my suggestion. Not sure it's clearer though:

"Further, current capacity allocation is prone to self-interest and 
malice, and has resulted in a system where few can obtain more at the 
expense of many. Faced with such vicarious punishment for the bulk of 
their customers, ISPs resort to policing and throttling "heavy users", 
which in turn is eroding trust between ISPs, customers, content 
providers and application writers."

Joao.