IETF Logo Mail Archive

Re: [Dime] Charter update

Ben Campbell <ben@nostrum.com> Fri, 17 August 2012 04:56 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06B5E21F8522 for <dime@ietfa.amsl.com>; Thu, 16 Aug 2012 21:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level:
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nqaplTNhKl5M for <dime@ietfa.amsl.com>; Thu, 16 Aug 2012 21:56:01 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 55A1D21F8467 for <dime@ietf.org>; Thu, 16 Aug 2012 21:56:01 -0700 (PDT)
Received: from [10.0.1.30] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q7H4txCO020782 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 16 Aug 2012 23:55:59 -0500 (CDT) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <78E86CCF-4D11-40BF-A02B-1F5364AECD65@iki.fi>
Date: Thu, 16 Aug 2012 23:56:00 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <651528FD-F859-44B4-8978-460039563FC6@nostrum.com>
References: <2D1E666F-1BA7-4FCA-800B-D01E5E5756D1@iki.fi> <196921E1-E38D-4342-AC06-57D0FB746394@nostrum.com> <78E86CCF-4D11-40BF-A02B-1F5364AECD65@iki.fi>
To: jouni korhonen <jouni.korhonen@iki.fi>
X-Mailer: Apple Mail (2.1485)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: dime@ietf.org, dime-chairs@tools.ietf.org
Subject: Re: [Dime] Charter update
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Aug 2012 04:56:02 -0000

On Aug 14, 2012, at 2:47 PM, jouni korhonen <jouni.korhonen@iki.fi> wrote:

>> Is this language intended to cover work on the mechanism as well as work on requirements? As written, it 
> 
> Yes. Sloppy wording. Lets try tweaking the wording a bit:
> 
> - Diameter overload control. The aim of this work is to identify the
> limitations of the current Diameter base protocol overload control
> mechanisms and based on the identified limitations define a set of
> requirements for an overall Diameter overload control solution. The
> solution would need to fulfill the requirements.

I may be being overly pedantic, but I still don't see that language as saying to actually define the solution. Here's a suggested further tweak:

"- Diameter overload control. The aim of this work is to identify the
limitations of the current Diameter base protocol for overload control purposes. Based on the identified limitations 
the working group will specify a set of requirements for an overall Diameter overload control solution and define 
a solution that meets those requirements."

Thanks!

Ben.

v2.23.0 | Report a Bug | By Email