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

"Don Bowman" <don@sandvine.com> Fri, 04 September 2009 19:57 UTC

Return-Path: <don@sandvine.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 40B573A68AC for <re-ecn@core3.amsl.com>; Fri, 4 Sep 2009 12:57:39 -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 TBg98e-hIuPr for <re-ecn@core3.amsl.com>; Fri, 4 Sep 2009 12:57:36 -0700 (PDT)
Received: from mail2.sandvine.com (Mail1.sandvine.com [64.7.137.134]) by core3.amsl.com (Postfix) with ESMTP id 716453A6784 for <re-ecn@ietf.org>; Fri, 4 Sep 2009 12:57:36 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Sep 2009 15:57:02 -0400
Message-ID: <EB618291F3454E4DA10D152B9045C017020779AC@exchange-2.sandvine.com>
In-Reply-To: <200909041943.n84Jhson001249@bagheera.jungle.bt.co.uk>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Pls respond: Do we have a Congestion Exposure community?
Thread-Index: AcotmBOQg6lI+qM5R86PqPGnHsZ8BgAAHcYw
References: <200909041943.n84Jhson001249@bagheera.jungle.bt.co.uk>
From: "Don Bowman" <don@sandvine.com>
To: <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 19:57:39 -0000

> >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.

I would be very interested. I am with Sandvine, one of the larger
vendors of network policy control, including congestion and traffic
management.

I could share some of our successes and frustrations in this space, and
the things that would help as part of the standard. re-ECN is something
that i would like to use as part of our fairshare traffic management
product.

One of the significant challenges we have is detecting congestion on a
per link basis, where congestion is defined as traffic that must get
through that is kicked around, rather than simple as free capacity.

One of the things i can bring is specific measurements from consumer
wireless and broadband networks, and an explanation of how those
networks function. These are the highest-scale shared pipe systems out
there today.

--don