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

Bob Briscoe <rbriscoe@jungle.bt.co.uk> Wed, 09 September 2009 21:27 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 B740228C117 for <re-ecn@core3.amsl.com>; Wed, 9 Sep 2009 14:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.86
X-Spam-Level:
X-Spam-Status: No, score=-1.86 tagged_above=-999 required=5 tests=[AWL=0.257, 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 K7keD9fyNL4R for <re-ecn@core3.amsl.com>; Wed, 9 Sep 2009 14:27:28 -0700 (PDT)
Received: from smtp2.smtp.bt.com (smtp2.smtp.bt.com [217.32.164.150]) by core3.amsl.com (Postfix) with ESMTP id A31673A68BC for <re-ecn@ietf.org>; Wed, 9 Sep 2009 14:27:28 -0700 (PDT)
Received: from i2kc06-ukbr.domain1.systemhost.net ([193.113.197.70]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 9 Sep 2009 22:28:00 +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:28:00 +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 1252531679388; Wed, 9 Sep 2009 22:27:59 +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 n89LRsAc021392; Wed, 9 Sep 2009 22:27:56 +0100
Message-Id: <200909092127.n89LRsAc021392@bagheera.jungle.bt.co.uk>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 09 Sep 2009 22:27:53 +0100
To: Aaron Falk <falk@bbn.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <4AA7AE21.5040600@bbn.com>
References: <200909041554.n84FsXEU029017@bagheera.jungle.bt.co.uk> <4AA7AE21.5040600@bbn.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:28:00.0479 (UTC) FILETIME=[6817C6F0:01CA3194]
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] Fwd: 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:27:35 -0000

Aaron

At 14:31 09/09/2009, Aaron Falk wrote:
>Hi Folks-
>
>I see I've missed the deadline for this note.  Sorry, I've been on
>vacation...
>
>FWIW, I think re-ECN is a cool, albeit unproven, idea and further
>development and experimentation will help build understanding of the
>benefits and missing pieces.  This work seems like a very good fit for
>R&D at the intersection of the research, standardization, and operations
>community.  IETF meetings are about as close as one can get, although
>getting the right folks into the room takes work and shouldn't be
>assumed.  One possible, useful outcome of a re-ECN BoF could be an
>effort around developing an experimental protocol and encouraging
>limited deployments, as the HIP advocates have done.

Definitely - HIP & LISP are the models of IETF process that we are 
learning from.

more...

>I regret that I do not have the cycles to actively participate so
>consider this standing on the sidelines and nudging.  :)
>
>cheers,
>
>--aaron
>
>ps.  I'm also thinking that "future Internet" research infrastructure,
>like GENI, could provide instrumented, controlled -- and, over the next
>few years, at-scale -- environments for  re-ECN (and other congestion
>control) experiments but I don't think that is really a factor in the
>BoF decision just a matter of my personal interest.

Beg to differ - an interest / commitment to find a way to test 
re-ECN's claims would be a v important part of an experimental track 
protocol. If it's experimental, we have to do experiments to prove it 
can move on. The pre-requisite question to answer is "will 
experiments get done?"

It's even possible re-ECN could be used to share GENI resources. With 
a bit of imagination, it might even be possible to use it to drive 
the time-slot scheduling across slots not just between slots - rather 
than (or complementary to) resource reservations. I know 
repeatability is a big GENI thing, but that can't preclude multiplexing.

...Just arm-waving thoughts that would need deeper thought.



Bob





> > 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
>_______________________________________________
>re-ECN mailing list
>re-ECN@ietf.org
>https://www.ietf.org/mailman/listinfo/re-ecn

________________________________________________________________
Bob Briscoe,               Networks Research Centre, BT Research