Re: [Dime] DOIC: Multiple instance of OC-OLR AVP (of the same type) within a response message

Ben Campbell <ben@nostrum.com> Tue, 10 December 2013 03:10 UTC

Return-Path: <ben@nostrum.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 B3E171AE128 for <dime@ietfa.amsl.com>; Mon, 9 Dec 2013 19:10:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level:
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311] autolearn=no
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 1iX8-RnmPfUL for <dime@ietfa.amsl.com>; Mon, 9 Dec 2013 19:10:14 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 898511AE11B for <dime@ietf.org>; Mon, 9 Dec 2013 19:10:14 -0800 (PST)
Received: from [10.0.1.29] (cpe-173-172-146-58.tx.res.rr.com [173.172.146.58]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id rBA3A0Zl042762 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 9 Dec 2013 21:10:02 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <26C84DFD55BC3040A45BF70926E55F2587C1D6BB@SZXEMA512-MBX.china.huawei.com>
Date: Mon, 09 Dec 2013 21:09:59 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <641914EC-C7D2-4059-A0B2-E8AE672C3F82@nostrum.com>
References: <A9CA33BB78081F478946E4F34BF9AAA014D1EC79@xmb-rcd-x10.cisco.com>, <2901_1385634414_52971A6E_2901_2686_1_6B7134B31289DC4FAF731D844122B36E307743@PEXCVZYM13.corporate.adroot.infra.ftgroup> <A9CA33BB78081F478946E4F34BF9AAA014D1EDDE@xmb-rcd-x10.cisco.com> <26C84DFD55BC3040A45BF70926E55F2587C1D016@SZXEMA512-MBX.china.huawei.com> <345A59EB-A13B-4E0A-A616-94D0A82A4D99@nostrum.com> <26C84DFD55BC3040A45BF70926E55F2587C1D6BB@SZXEMA512-MBX.china.huawei.com>
To: "Shishufeng (Susan)" <susan.shishufeng@huawei.com>
X-Mailer: Apple Mail (2.1822)
Received-SPF: pass (shaman.nostrum.com: 173.172.146.58 is authenticated by a trusted mechanism)
Cc: "dime@ietf.org" <dime@ietf.org>
Subject: Re: [Dime] DOIC: Multiple instance of OC-OLR AVP (of the same type) within a response message
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, 10 Dec 2013 03:10:15 -0000

On Dec 9, 2013, at 8:46 PM, Shishufeng (Susan) <susan.shishufeng@huawei.com> wrote:

> Try to make it more clear. 
> 
> So far, there are only two report types defined, i.e. host and realm. In the future, if more overload reports are needed for the same report type, e.g. for the same host but for different APNs, it should be up to the Diameter application where this is to be applied to define how to differentiate and use the multiple OC-OLR instances. One possible way could be to extend the report type with more types or values for such differentiation, as discussed previously, while there might be other ways e.g. with definition of new AVPs inside or outside OC-OLR AVP.

Okay, then I partially agree. But I think the rules for whether (and how) you allow multiple instances of the same report type should be per report type, rather than per application. I have trouble thinking of a situation where the rules for a given report type would be different between one application and another. (But I would welcome an example to change my mind :-)  )

Thanks!

Ben.