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

"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Wed, 02 September 2009 18:43 UTC

Return-Path: <richard_woundy@cable.comcast.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 CE91F3A6D26 for <re-ecn@core3.amsl.com>; Wed, 2 Sep 2009 11:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[AWL=1.214, BAYES_00=-2.599, GB_FREEBONUS=1, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8]
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 cxEGB9uP7SwM for <re-ecn@core3.amsl.com>; Wed, 2 Sep 2009 11:43:29 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 845863A6A93 for <re-ecn@ietf.org>; Wed, 2 Sep 2009 11:43:29 -0700 (PDT)
Received: from ([24.40.15.118]) by pacdcimo01.cable.comcast.com with ESMTP id 5503620.52104174; Wed, 02 Sep 2009 14:41:36 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by PACDCEXCSMTP04.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 2 Sep 2009 14:41:36 -0400
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: Wed, 2 Sep 2009 14:41:35 -0400
Message-ID: <8A82D1BFEDDE7E4597978355239BBBCB17491B@PACDCEXCMB06.cable.comcast.com>
In-Reply-To: <0B0A20D0B3ECD742AA2514C8DDA3B065029068C3@VGAEXCH01.hq.corp.viasat.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [re-ECN] Pls respond: Do we have a Congestion Exposurecommunity?
Thread-Index: Acor65gF7Zh6ZqksTAOi2QvCMGJ13QADUOFAAADLtHA=
References: <200909021633.n82GXbsp012052@bagheera.jungle.bt.co.uk> <0B0A20D0B3ECD742AA2514C8DDA3B065029068C3@VGAEXCH01.hq.corp.viasat.com>
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Bob Briscoe" <rbriscoe@jungle.bt.co.uk>, <re-ecn@ietf.org>
X-OriginalArrivalTime: 02 Sep 2009 18:41:36.0625 (UTC) FILETIME=[005C4E10:01CA2BFD]
Cc: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
Subject: Re: [re-ECN] Pls respond: Do we have a Congestion Exposurecommunity?
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 18:43:31 -0000

Bob,

I am definitely interested in being involved in the re-ECN efforts,
including co-authoring/reviewing documents, participating in the mailing
list discussions, figuring out applications for the protocol (and the
concept of 'congestion transparency', figuring out costs / benefits for
service providers and other stakeholders, and figuring out service
provider deployment considerations.

Plus you get "standing on the sidelines booing or clapping" as a free
bonus. :)

-- Rich

-----Original Message-----
From: re-ecn-bounces@ietf.org [mailto:re-ecn-bounces@ietf.org] On Behalf
Of Bob Briscoe
Sent: Wednesday, September 02, 2009 12:34 PM
To: re-ecn@ietf.org
Subject: [re-ECN] 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
_______________________________________________
re-ECN mailing list
re-ECN@ietf.org
https://www.ietf.org/mailman/listinfo/re-ecn