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

Bob Briscoe <rbriscoe@jungle.bt.co.uk> Wed, 09 September 2009 21:05 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 C48E93A6A60 for <re-ecn@core3.amsl.com>; Wed, 9 Sep 2009 14:05:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.856
X-Spam-Level:
X-Spam-Status: No, score=-1.856 tagged_above=-999 required=5 tests=[AWL=0.261, 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 2jzqR21C6n3Y for <re-ecn@core3.amsl.com>; Wed, 9 Sep 2009 14:05:51 -0700 (PDT)
Received: from smtp1.smtp.bt.com (smtp1.smtp.bt.com [217.32.164.137]) by core3.amsl.com (Postfix) with ESMTP id C2F353A6993 for <re-ecn@ietf.org>; Wed, 9 Sep 2009 14:05:50 -0700 (PDT)
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by smtp1.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 9 Sep 2009 22:06:23 +0100
Received: from cbibipnt05.iuser.iroot.adidom.com ([147.149.196.177]) by i2kc06-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 9 Sep 2009 22:06:22 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt05.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1252530381641; Wed, 9 Sep 2009 22:06:21 +0100
Received: from MUT.jungle.bt.co.uk ([10.73.61.4]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id n89L6HTi021175; Wed, 9 Sep 2009 22:06:17 +0100
Message-Id: <200909092106.n89L6HTi021175@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 09 Sep 2009 22:06:16 +0100
To: "Piers O'Hanlon" <p.ohanlon@cs.ucl.ac.uk>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <abe39f780909080451s5723b591kef876931be377df3@mail.gmail.co m>
References: <200909041611.n84GBpnS029196@bagheera.jungle.bt.co.uk> <abe39f780909080451s5723b591kef876931be377df3@mail.gmail.com>
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: 09 Sep 2009 21:06:22.0828 (UTC) FILETIME=[62A1F2C0:01CA3191]
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: Wed, 09 Sep 2009 21:05:57 -0000

Piers,

At 12:51 08/09/2009, Piers O'Hanlon wrote:
>I know I'm a little late but I'd like to register my interest in this
>BoF. I'm involved in some drafts using ECN for RTP which would be
>relevant to such work.

If we get moving, you might end up adding re-ECN to RTP at the same 
time as you add ECN :)


Bob


>Cheers,
>
>Piers O'Hanlon
>
>
> > 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
>
>________________________________________________________________
>Bob Briscoe,               Networks Research Centre, BT Research
>_______________________________________________
>re-ECN mailing list
>re-ECN@ietf.org
>https://www.ietf.org/mailman/listinfo/re-ecn

________________________________________________________________
Bob Briscoe,               Networks Research Centre, BT Research