Re: [re-ECN] Charter Question

John Leslie <john@jlc.net> Mon, 10 May 2010 20:55 UTC

Return-Path: <john@jlc.net>
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 94D0B3A6C13 for <re-ecn@core3.amsl.com>; Mon, 10 May 2010 13:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.531
X-Spam-Level:
X-Spam-Status: No, score=-3.531 tagged_above=-999 required=5 tests=[AWL=0.468, 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 9sO7uuW9YgVj for <re-ecn@core3.amsl.com>; Mon, 10 May 2010 13:55:33 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.9]) by core3.amsl.com (Postfix) with ESMTP id 483393A6D31 for <re-ecn@ietf.org>; Mon, 10 May 2010 13:52:00 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 8226E33D15; Mon, 10 May 2010 16:51:49 -0400 (EDT)
Date: Mon, 10 May 2010 16:51:49 -0400
From: John Leslie <john@jlc.net>
To: Ron Bonica <rbonica@juniper.net>
Message-ID: <20100510205149.GL48545@verdi>
References: <4BE42A91.2040202@juniper.net> <20100507165938.GB48545@verdi> <4BE83730.1030809@juniper.net> <EE00404438E9444D90AEA84210DC4067AF13BB@pacdcexcmb05.cable.comcast.com> <4BE86A12.6020402@juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4BE86A12.6020402@juniper.net>
User-Agent: Mutt/1.4.1i
Cc: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>, 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:55:34 -0000

Ron Bonica <rbonica@juniper.net> wrote:
> On 5/10/2010 2:25 PM, Woundy, Richard wrote:
>> [Ron Bonica wrote:]
>> 
>>> This is troubling. Before we invest in tool development, we really
>>> should know something about the intended use of the tool.
>> 
>> I think I gave an example on this list last Friday.
>> 
>> See <http://www.ietf.org/mail-archive/web/re-ecn/current/msg00690.html>.
> 
> I think that you gave a very fine example. Unfortunately, according to
> John, it is out of scope.

   There may be some misunderstanding here...

] [Ron Bonica wrote:]
]] If I do have this right, who will those routers use this information?
]
] I believe we consider that question out of scope;

   I do consider the quetion of what any existing router does with the
information out of scope.

   But we have a pre-WG document which I believe _will_ see some work
after the WG is formed:

http://tools.ietf.org/html/draft-tschofenig-conex-ps-02

describing the problem we set out to address.

   I can understand that someone working for a router manufacturer may
be concerned how this will affect router design.

   But there appears to be a consensus (whatever that may mean in the
absence of a WG) that the answer is, "Not at all." We're thinking in
terms of middlebox operations, and asking no more of existing routers
than to perform ECN marking if it's convenient.

   (BTW, draft-tschofenig-conex-ps basically says that ISPs want to do
the right thing, but in the absence of congestion exposure they're
forced to use less appropriate metrics to "estimate" congestion.)

> Rather than putting it out of scope, I think that it should be the WGs
> first order of business.

   I agree a Problem Statement deserves to be an early milestone.
What do you think is needed that's not in draft-tschofenig-conex-ps?

--
John Leslie <john@jlc.net>