Re: [re-ECN] Pls respond: Do we have a Congestion Exposure community?

marcelo bagnulo braun <marcelo@it.uc3m.es> Sun, 06 September 2009 16:13 UTC

Return-Path: <marcelo@it.uc3m.es>
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 B03B33A68B7 for <re-ecn@core3.amsl.com>; Sun, 6 Sep 2009 09:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.377
X-Spam-Level:
X-Spam-Status: No, score=-6.377 tagged_above=-999 required=5 tests=[AWL=-0.078, 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 vxfMv7BH4+uf for <re-ecn@core3.amsl.com>; Sun, 6 Sep 2009 09:13:13 -0700 (PDT)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by core3.amsl.com (Postfix) with ESMTP id 749043A67EC for <re-ecn@ietf.org>; Sun, 6 Sep 2009 09:13:13 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (126.pool85-53-142.dynamic.orange.es [85.53.142.126]) by smtp02.uc3m.es (Postfix) with ESMTP id 9E5A565A3AD; Sun, 6 Sep 2009 18:13:36 +0200 (CEST)
Message-ID: <4AA3DFB0.2000105@it.uc3m.es>
Date: Sun, 06 Sep 2009 18:13:36 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Jo=E3o_Taveira_Ara=FAjo?= <j.araujo@ee.ucl.ac.uk>
References: <200909021633.n82GXbsp012052@bagheera.jungle.bt.co.uk> <4AA29944.3050900@ee.ucl.ac.uk> <4AA2B014.9040606@it.uc3m.es> <4AA3D620.8070803@ee.ucl.ac.uk>
In-Reply-To: <4AA3D620.8070803@ee.ucl.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16872.000
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] Pls respond: Do we have a Congestion Exposure community?
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: Sun, 06 Sep 2009 16:13:14 -0000

Hi Joao,


João Taveira Araújo escribió:
> Hi Marcelo,
>
> Re-ECN reveals rest-of-path congestion, so any (interested) network 
> node can estimate how much congestion a given stream of packets is 
> expected to experience. In the TE case this information might be 
> useful to balance traffic more efficiently than simply resorting to 
> load factor and other local information.
>
I see what you mean and i agree that that is a very interesting application.


> I also believe it might be an interesting catalyst for new routing 
> models as it realigns incentives at the transit level. Hesitant 
> providers might warm up to the idea of providing multiple routes if 
> there was something in it for them too. As it stands current multipath 
> work (afaict) is bypassing the network entirely and providing a pure 
> e2e solution. Not that this is wrong, but it is one of many 
> approaches. Whether we're gravitating towards it because it's the only 
> deployable option or on technical merits alone is not entirely clear 
> to me.
I think there are several reasons why we are doing it e2e.
A major one, is that the stability issues for the e2 model have been 
worked out while the ones for the router based still need work, afaik.
BEsides, the actual model for load balancing changes significantly when 
doing it at the endpoints and when doing it in the routers

But, i certainly beleive this has a lot of potential and that is a very 
interesting applications of congestion information exposure.

Regards, marcelo


>
>
> Cheers,
> Joao.
>
> marcelo bagnulo braun wrote:
>> Hi Joao,
>>
>> could you expand on the relation between re-ecn and TE/routing?
>>
>> Regards, marcelo
>>
>>
>> João Taveira Araújo escribió:
>>> Hi Bob,
>>>
>>> As you know, I'm very much interested in re-ECN, particularly in 
>>> using some of its properties in other areas like TE/routing. I have 
>>> cycles to spare so feel free to count on me for 
>>> reviewing/coding/booing and clapping.
>>>
>>> Cheers,
>>> Joao.
>>>
>>> Bob Briscoe wrote:
>>>> Folks,
>>>>
>>>> I'd like to try to arrange a Congestion Exposure (re-ECN) BoF in 
>>>> Nov at the Hiroshima IETF. If so, we have to notify the area 
>>>> directors v soon - by 24:00 UTC Mon 7 Sep 09. #1 gating function 
>>>> for Area Directors: activity on an ietf list.
>>>>
>>>> Therefore, pls respond preferably *on this list* if you're 
>>>> interested in being involved, no matter how insignificantly, e.g.
>>>>
>>>> - you want congestion visibility for other stuff you're doing
>>>>   (but don't intend to work on it itself)
>>>> - reviewing docs,
>>>> - alternative way to achieve congestion exposure
>>>> - participate in mailing list discussion,
>>>> - co-authoring docs
>>>> - design ways to do incremental deployment
>>>> - using code for other stuff you're doing
>>>> - thinking up new uses for the protocol
>>>> - breaking it
>>>> - analysing benefits/costs
>>>> - implement protocol
>>>> - implement a demo
>>>> - running or participating in trials
>>>> - standing on the sidelines booing or clapping
>>>> - whatever
>>>>
>>>> Perceived problem:
>>>> Most people want to work on something finite like a new cool 
>>>> non-TCP-friendly congestion control. Less people want to go into an 
>>>> pseudo-infinite loop fixing IP to allow other cool stuff to happen. 
>>>> If you want something like re-ECN to be there, but don't have the 
>>>> bandwidth to work on it, that's cool too - please say this - it's 
>>>> still palpable support. And you will be likely to have review 
>>>> comments related to how you want to use it.
>>>>
>>>> Cheers
>>>>
>>>>
>>>> Bob
>>>>
>>>>
>>>> ________________________________________________________________
>>>> Bob Briscoe,               Networks Research Centre, BT Research
>>>> _______________________________________________
>>>> re-ECN mailing list
>>>> re-ECN@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/re-ecn
>>>
>>> _______________________________________________
>>> re-ECN mailing list
>>> re-ECN@ietf.org
>>> https://www.ietf.org/mailman/listinfo/re-ecn
>>>
>>
>> _______________________________________________
>> re-ECN mailing list
>> re-ECN@ietf.org
>> https://www.ietf.org/mailman/listinfo/re-ecn
>
>