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

"PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be> Sat, 05 September 2009 12:34 UTC

Return-Path: <Dimitri.Papadimitriou@alcatel-lucent.be>
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 347483A683B for <re-ecn@core3.amsl.com>; Sat, 5 Sep 2009 05:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.906
X-Spam-Level:
X-Spam-Status: No, score=-4.906 tagged_above=-999 required=5 tests=[AWL=1.342, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, 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 LEIOWBUWbNIO for <re-ecn@core3.amsl.com>; Sat, 5 Sep 2009 05:34:38 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [62.23.212.57]) by core3.amsl.com (Postfix) with ESMTP id AB0353A67F2 for <re-ecn@ietf.org>; Sat, 5 Sep 2009 05:34:37 -0700 (PDT)
Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.dc-m.alcatel-lucent.com [155.132.6.74]) by smail2.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id n85CXtl6004439; Sat, 5 Sep 2009 14:33:55 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.53]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Sat, 5 Sep 2009 14:33:55 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA2E25.21D64FDF"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Sat, 5 Sep 2009 14:33:54 +0200
Message-ID: <00275A5B436CA441900CB10936742A3801B7878C@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] Pls respond: Do we have a Congestion Exposure community?
Thread-Index: Acor66FstcD06PbfRe6EfopwB/3H7gCOJcjx
References: <200909021633.n82GXbsp012052@bagheera.jungle.bt.co.uk>
From: "PAPADIMITRIOU Dimitri" <Dimitri.Papadimitriou@alcatel-lucent.be>
To: "Bob Briscoe" <rbriscoe@jungle.bt.co.uk>, <re-ecn@ietf.org>
X-OriginalArrivalTime: 05 Sep 2009 12:33:55.0513 (UTC) FILETIME=[22270290:01CA2E25]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.80
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: Sat, 05 Sep 2009 12:34:39 -0000

I am convinced more work is needed in this area. A BoF should help determining objectives, refine space of investigation (towards specification), and specifically look at interaction/impact on inter-domain / inter-connection and traffic regulation.

As involvement, I should (at least) actively participate to the mailing list discussions, and review/comment on documents.

Thanks,
-dimitri.
-----Original Message-----
From: re-ecn-bounces@ietf.org on behalf of Bob Briscoe
Sent: Wed 02/09/2009 18:33
To: re-ecn@ietf.org
Subject: [re-ECN] Pls respond: Do we have a Congestion Exposure community?
 
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