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

"Anna Charny (acharny)" <acharny@cisco.com> Sun, 06 September 2009 12:17 UTC

Return-Path: <acharny@cisco.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 6F30128C0FD for <re-ecn@core3.amsl.com>; Sun, 6 Sep 2009 05:17:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 ZvhVL5ecprps for <re-ecn@core3.amsl.com>; Sun, 6 Sep 2009 05:17:47 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 12B973A6891 for <re-ecn@ietf.org>; Sun, 6 Sep 2009 05:17:46 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkIFAJNFo0pAZnme/2dsb2JhbACCJi+8JIhDAY5wBYIjgXU
X-IronPort-AV: E=Sophos; i="4.44,341,1249257600"; d="scan'208,217"; a="56974874"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 06 Sep 2009 12:18:11 +0000
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n86CIB1b020716 for <re-ecn@ietf.org>; Sun, 6 Sep 2009 08:18:11 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n86CIBEK015528 for <re-ecn@ietf.org>; Sun, 6 Sep 2009 12:18:11 GMT
Received: from xmb-rtp-203.amer.cisco.com ([64.102.31.20]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 6 Sep 2009 08:18:11 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA2EEC.19B0650F"
Date: Sun, 6 Sep 2009 08:18:14 -0400
Message-ID: <BABC859E6D0B9A4D8448CC7F41CD2B07098A6A23@xmb-rtp-203.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Re: [re-ECN] Pls respond: Do we have a Congestion Exposure community?
Thread-Index: Acou7BvYiVRQx01RTKORgKRenE0VPQ==
From: "Anna Charny (acharny)" <acharny@cisco.com>
To: <re-ecn@ietf.org>
X-OriginalArrivalTime: 06 Sep 2009 12:18:11.0530 (UTC) FILETIME=[19E862A0:01CA2EEC]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4676; t=1252239491; x=1253103491; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=acharny@cisco.com; z=From:=20=22Anna=20Charny=20(acharny)=22=20<acharny@cisco.c om> |Subject:=20Re=3A=20[re-ECN]=20Pls=20respond=3A=20Do=20we=2 0have=20a=20Congestion=20Exposure=20community?=20 |Sender:=20 |To:=20<re-ecn@ietf.org>; bh=wCCZiWnh7RCr2SiGcsb+00gJ0RE6dsQTaa2An5NecLY=; b=fNnc9Urq7cDAk95BjL2LJ9aikw1mpXl4laXyb3SC7JHwY+Ciqcy2RV//ux 5efyUTsd8UwmPW15hTfANcaaRw8PxQbqGJv+WNxCOWoTKs8tc8CyhS3syn0Z 0X79efDViD;
Authentication-Results: rtp-dkim-1; header.From=acharny@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim1001 verified; );
X-Mailman-Approved-At: Sun, 06 Sep 2009 08:12:29 -0700
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: Sun, 06 Sep 2009 12:17:48 -0000

Hi Bob,
 
I would definitely be very interested in this BoF.
 
Anna Charny
 
Bob Briscoe wrote:


	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