Re: [Dime] DOIC Default Algorithm Specification

"TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <jean-jacques.trottin@alcatel-lucent.com> Tue, 25 March 2014 09:02 UTC

Return-Path: <jean-jacques.trottin@alcatel-lucent.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DFE01A0396 for <dime@ietfa.amsl.com>; Tue, 25 Mar 2014 02:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MfWw_t0w98a2 for <dime@ietfa.amsl.com>; Tue, 25 Mar 2014 02:02:38 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 640E61A0379 for <dime@ietf.org>; Tue, 25 Mar 2014 02:02:38 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s2P92Z4A019806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <dime@ietf.org>; Tue, 25 Mar 2014 04:02:36 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s2P92Z7e026466 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dime@ietf.org>; Tue, 25 Mar 2014 10:02:35 +0100
Received: from FR712WXCHMBA12.zeu.alcatel-lucent.com ([169.254.8.164]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Tue, 25 Mar 2014 10:02:35 +0100
From: "TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <jean-jacques.trottin@alcatel-lucent.com>
To: "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] DOIC Default Algorithm Specification
Thread-Index: AQHPQg1mSrntxLF47UmNCQBgXGvw6JrrxgcAgAXFv4A=
Date: Tue, 25 Mar 2014 09:02:34 +0000
Message-ID: <E194C2E18676714DACA9C3A2516265D202672BC2@FR712WXCHMBA12.zeu.alcatel-lucent.com>
References: <4857132E-EB7E-4844-B9F4-81DD209E0705@nostrum.com> <5750EB10-9E07-4CD7-A122-CD5DDBD73003@gmail.com>
In-Reply-To: <5750EB10-9E07-4CD7-A122-CD5DDBD73003@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/rMIhyQvVt0g78Sz5XJf-etAXDds
Subject: Re: [Dime] DOIC Default Algorithm Specification
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 25 Mar 2014 09:02:40 -0000

Hi

I agree with Ben to differentiate general statements which are algorithm independent from the ones particular to the default algorithm, otherwise it may be a source of ambiguities/ misinterpretations . Now is this statement grouping into a referenced section easy? I do not know. I hope this will not have a too large impact on the draft.

Best regards

JJacques 




-----Message d'origine-----
De : DiME [mailto:dime-bounces@ietf.org] De la part de Jouni Korhonen
Envoyé : vendredi 21 mars 2014 18:46
À : Ben Campbell
Cc : dime@ietf.org list
Objet : Re: [Dime] DOIC Default Algorithm Specification




On Mar 18, 2014, at 2:18 AM, Ben Campbell <ben@nostrum.com> wrote:

> Hi,
> 
> In re-reading dime-ovli, I noticed that the procedures for the "default" abatement algorithm are spread through several parts of the text. That's going to make life difficult down the road for a couple of reasons:
> 
> 1) There's no easily referenced section that fully defines the algorithm. That will be a problem for other docs that want to talk about the algorithm (e.g. 3GPP specs), or even other sections in dime-ovli that want to mention the default algorithm by reference.
> 
> 2) It makes extensibility harder, as it will be more difficult to define new algorithms, if they need to modify behavior that is spread throughout dime-ovli, rather than simply supersede a specific section of dime-ovli.
> 
> I propose that we move all algorithm-specific behavior to its own section, and have any other sections that need to talk about the default algorithm reference that section rather than attempt to describe the behavior.

That would work for me.

- Jouni


> 
> Thanks!
> 
> Ben.
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime

_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime