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

"Livingood, Jason" <Jason_Livingood@cable.comcast.com> Fri, 11 September 2009 18:54 UTC

Return-Path: <jason_livingood@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 413C53A6881 for <re-ecn@core3.amsl.com>; Fri, 11 Sep 2009 11:54:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.385
X-Spam-Level:
X-Spam-Status: No, score=-1.385 tagged_above=-999 required=5 tests=[AWL=3.614, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067]
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 hSSs-Rj6KaAP for <re-ecn@core3.amsl.com>; Fri, 11 Sep 2009 11:54:00 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id C281A3A688C for <re-ecn@ietf.org>; Fri, 11 Sep 2009 11:53:59 -0700 (PDT)
Received: from ([24.40.15.118]) by pacdcimo01.cable.comcast.com with ESMTP id 5503620.53134672; Fri, 11 Sep 2009 14:54:33 -0400
Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PACDCEXCSMTP04.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 11 Sep 2009 14:54:34 -0400
Received: from 147.191.227.143 ([147.191.227.143]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.153]) with Microsoft Exchange Server HTTP-DAV ; Fri, 11 Sep 2009 18:54:33 +0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Fri, 11 Sep 2009 14:54:28 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: <re-ecn@ietf.org>
Message-ID: <C6D01524.12783%Jason_Livingood@cable.comcast.com>
Thread-Topic: Pls respond: Do we have a Congestion Exposure community?
Thread-Index: AcotdpKriAHQRpZIQiefCaNSkHgKRwFkkl8KAAIbbKk=
In-Reply-To: <C6D00700.1274F%Jason_Livingood@cable.comcast.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3335525669_1902697"
X-OriginalArrivalTime: 11 Sep 2009 18:54:34.0140 (UTC) FILETIME=[4D836DC0:01CA3311]
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, 11 Sep 2009 18:54:05 -0000

Been on vacation so late in responding to this thread, though I see others
have done so (incl. my colleague Rich Woundy).  This seems like an
interesting area of work and, barring obvious conflicts with other BoFs and
WGs at IETF 76, I¹m interested in attending and participating on some level.

Regards
Jason


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