Re: [re-ECN] Charter Question
bmanning@vacation.karoshi.com Mon, 10 May 2010 20:39 UTC
Return-Path: <bmanning@karoshi.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 C6AE528C28E for <re-ecn@core3.amsl.com>; Mon, 10 May 2010 13:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.394
X-Spam-Level:
X-Spam-Status: No, score=-4.394 tagged_above=-999 required=5 tests=[AWL=-0.395, BAYES_50=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 aMKP9NeMbbW3 for <re-ecn@core3.amsl.com>; Mon, 10 May 2010 13:39:55 -0700 (PDT)
Received: from vacation.karoshi.com (vacation.karoshi.com [198.32.6.68]) by core3.amsl.com (Postfix) with ESMTP id AC8C83A67C2 for <re-ecn@ietf.org>; Mon, 10 May 2010 13:33:16 -0700 (PDT)
Received: from karoshi.com (localhost.localdomain [127.0.0.1]) by vacation.karoshi.com (8.12.8/8.12.8) with ESMTP id o4AKVxtG029421; Mon, 10 May 2010 20:32:15 GMT
Received: (from bmanning@localhost) by karoshi.com (8.12.8/8.12.8/Submit) id o4AKVYXp029416; Mon, 10 May 2010 20:31:34 GMT
Date: Mon, 10 May 2010 20:31:29 +0000
From: bmanning@vacation.karoshi.com
To: John Leslie <john@jlc.net>
Message-ID: <20100510203129.GC28328@vacation.karoshi.com.>
References: <4BE42A91.2040202@juniper.net> <20100507165938.GB48545@verdi> <4BE83730.1030809@juniper.net> <20100510174353.GI48545@verdi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20100510174353.GI48545@verdi>
User-Agent: Mutt/1.4.1i
Cc: re-ecn@ietf.org
Subject: Re: [re-ECN] Charter Question
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: Mon, 10 May 2010 20:39:56 -0000
On Mon, May 10, 2010 at 01:43:53PM -0400, John Leslie wrote: > Ron Bonica <rbonica@juniper.net> wrote: > > > >>> If I do have this right, who will those routers use this information? > >> > >> I believe we consider that question out of scope; > > > > This is troubling. Before we invest in tool development, we really > > should know something about the intended use of the tool. > > We certainly have a lot of information on that developed by Bob > Briscoe, e.g. > > http://bobbriscoe.net/projects/refb/ > > I realize that not everyone agrees with Bob; so let me try to give > an independent viewpoint on use of a ConEx tool. > > Recall, the proposed charter says: > ] > ] The mechanism to be developed by the CONEX WG will enable the sender > ] to also relay the congestion information back into the IP layer, > ] such that the total level of congestion is visible to all IP devices > ] along the path. > > Thus, at any point along the path -- most likely near the sender > or near the receiver -- it will be practical to aggregate the expected > congestion for some flows and see whether this is consistent with the > contractual arrangement. > > What to do if it isn't is clearly out-of-scope. er... you have already proposed a use for the congestion information, i.e. aggregate flows... and then, its no longer the original sender/recevier, is the node that has chosen to mediate/aggregate and the source/target (or other middle-box that has chosen to aggregate/deaggregate based on local policy) Just saying. > This -- and only this -- is "the intended use of the tool". me thinks this vastly exceeds Bobs description - its moved past a protocol change; "relay congesstion information back into the IP layer" to a specific implementation choice. > Being who we are, we inevitably speculate about other uses such > a tool will enable. Any good tool enables uses beyond the one it > was designed for. amen - but lets get the tool working before we try and use it for a given purpose. > > I wouldn't mind letting the BoF spend some time bringing this question > > into focus before chartering a WG. > > What "better focus" would you like, Ron? > > -- > John Leslie <john@jlc.net> > _______________________________________________ > re-ECN mailing list > re-ECN@ietf.org > https://www.ietf.org/mailman/listinfo/re-ecn
- [re-ECN] Charter Question Ron Bonica
- Re: [re-ECN] Charter Question Ron Bonica
- Re: [re-ECN] Charter Question John Leslie
- Re: [re-ECN] Charter Question bmanning
- Re: [re-ECN] Charter Question John Leslie
- Re: [re-ECN] Charter Question bmanning
- Re: [re-ECN] Charter Question John Leslie
- Re: [re-ECN] Charter Question Woundy, Richard
- Re: [re-ECN] Charter Question Stewart Bryant
- Re: [re-ECN] Charter Question Ron Bonica
- Re: [re-ECN] Charter Question John Leslie
- Re: [re-ECN] Charter Question Woundy, Richard
- Re: [re-ECN] Charter Question Ron Bonica
- Re: [re-ECN] Charter Question bmanning
- Re: [re-ECN] Charter Question John Leslie
- Re: [re-ECN] Charter Question John Leslie
- Re: [re-ECN] Charter Question Bob Briscoe
- Re: [re-ECN] Charter Question David Harrington
- Re: [re-ECN] Charter Question John Leslie
- Re: [re-ECN] Charter Question McCann Peter-A001034
- [re-ECN] Preferential Dropping John Leslie
- Re: [re-ECN] Charter Question Bob Briscoe
- Re: [re-ECN] Preferential Dropping McCann Peter-A001034
- Re: [re-ECN] Preferential Dropping John Leslie
- Re: [re-ECN] Preferential Dropping Bob Briscoe
- Re: [re-ECN] Preferential Dropping McCann Peter-A001034
- Re: [re-ECN] Preferential Dropping Bob Briscoe
- Re: [re-ECN] Preferential Dropping McCann Peter-A001034