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

Steven Blake <slblake@petri-meat.com> Fri, 04 September 2009 20:03 UTC

Return-Path: <slblake@petri-meat.com>
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 72A7F3A6A9B for <re-ecn@core3.amsl.com>; Fri, 4 Sep 2009 13:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 OwVHqLs4Rwih for <re-ecn@core3.amsl.com>; Fri, 4 Sep 2009 13:03:04 -0700 (PDT)
Received: from elom.tchmachines.com (elom.tchmachines.com [208.76.80.198]) by core3.amsl.com (Postfix) with ESMTP id 8BD6C3A6A9A for <re-ecn@ietf.org>; Fri, 4 Sep 2009 13:03:04 -0700 (PDT)
Received: from cpe-024-211-224-078.nc.res.rr.com ([24.211.224.78]) by elom.tchmachines.com with esmtpa (Exim 4.69) (envelope-from <slblake@petri-meat.com>) id 1MjczE-0002WB-HJ; Fri, 04 Sep 2009 13:54:12 -0400
From: Steven Blake <slblake@petri-meat.com>
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Content-Type: text/plain
Date: Fri, 04 Sep 2009 13:54:16 -0400
Message-Id: <1252086856.1118.47.camel@tachyon>
Mime-Version: 1.0
X-Mailer: Evolution 2.24.5 (2.24.5-2.fc10)
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - elom.tchmachines.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - petri-meat.com
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: Fri, 04 Sep 2009 20:03:05 -0000

On Wed, 02 Sep 2009 17:33:36 +0100 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.

I am interested in making congestion exposure happen, and am willing to
work on documents, write code, participate in demos, etc.


Regards,

// Steve