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

Bob Briscoe <rbriscoe@jungle.bt.co.uk> Wed, 02 September 2009 16:36 UTC

Return-Path: <rbriscoe@jungle.bt.co.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 A8BC428C119 for <re-ecn@core3.amsl.com>; Wed, 2 Sep 2009 09:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.854
X-Spam-Level:
X-Spam-Status: No, score=-1.854 tagged_above=-999 required=5 tests=[AWL=0.263, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, RCVD_IN_DNSWL_LOW=-1]
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 j7Y04z3KSopa for <re-ecn@core3.amsl.com>; Wed, 2 Sep 2009 09:36:21 -0700 (PDT)
Received: from smtp4.smtp.bt.com (smtp4.smtp.bt.com [217.32.164.151]) by core3.amsl.com (Postfix) with ESMTP id A8E2F28C68F for <re-ecn@ietf.org>; Wed, 2 Sep 2009 09:36:20 -0700 (PDT)
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 2 Sep 2009 17:33:41 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by i2kc08-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 2 Sep 2009 17:33:41 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1251909220167; Wed, 2 Sep 2009 17:33:40 +0100
Received: from MUT.jungle.bt.co.uk ([10.215.130.87]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id n82GXbsp012052 for <re-ecn@ietf.org>; Wed, 2 Sep 2009 17:33:37 +0100
Message-Id: <200909021633.n82GXbsp012052@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 02 Sep 2009 17:33:36 +0100
To: re-ecn@ietf.org
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 02 Sep 2009 16:33:41.0237 (UTC) FILETIME=[21790A50:01CA2BEB]
Subject: [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: Wed, 02 Sep 2009 16:36:27 -0000

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