Re: [re-ECN] Pls respond: Do we have a Congestion Exposure Community?
Markku Kojo <kojo@cs.helsinki.fi> Mon, 07 September 2009 17:22 UTC
Return-Path: <kojo@cs.helsinki.fi>
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 A89F33A67A6 for <re-ecn@core3.amsl.com>;
Mon, 7 Sep 2009 10:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
tests=[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 R3c9Xx+Jw8fk for
<re-ecn@core3.amsl.com>; Mon, 7 Sep 2009 10:22:11 -0700 (PDT)
Received: from mail.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by
core3.amsl.com (Postfix) with ESMTP id B0D5C3A6801 for <re-ecn@ietf.org>;
Mon, 7 Sep 2009 10:22:11 -0700 (PDT)
Received: from wox-18.cs.helsinki.fi (wox-18.cs.helsinki.fi [128.214.11.68])
(AUTH: PLAIN cs-relay, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by
mail.cs.helsinki.fi with esmtp;
Mon, 07 Sep 2009 20:22:35 +0300 id 0006C556.4AA5415B.00001CCD
Received: by wox-18.cs.helsinki.fi (Postfix, from userid 3011) id A6AC8358B3;
Mon, 7 Sep 2009 20:22:35 +0300 (EEST)
Received: from localhost (localhost [127.0.0.1]) by wox-18.cs.helsinki.fi
(Postfix) with ESMTP id A4E72358B2; Mon, 7 Sep 2009 20:22:35 +0300 (EEST)
Date: Mon, 7 Sep 2009 20:22:35 +0300 (EEST)
From: Markku Kojo <kojo@cs.helsinki.fi>
To: re-ecn@ietf.org
Message-ID: <Pine.LNX.4.64.0909071941190.12772@wox-18.cs.helsinki.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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: Mon, 07 Sep 2009 17:22:12 -0000
Hi, sorry for the late response... Yes, I'd like to see this to be discussed in a BoF at the Hiroshima IETF. This has a lot of potential, and getting it done properly is important. My level of involvement is still open as it's a bit hard to know right now how much cycles I may be able to invest in this in the future, if a wg gets created. Hope to be able to contribute anyway as my group is working on related issues. Best regards, /Markku >Date: Wed, 02 Sep 2009 17:33:36 +0100 >To: re-ecn@ietf.org >From: Bob Briscoe <rbriscoe@jungle.bt.co.uk> >Subject: 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