Re: [Dime] Diameter Group: Type?

"David Lehmann" <dlehmann@ulticom.com> Mon, 24 January 2011 21:10 UTC

Return-Path: <dlehmann@ulticom.com>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA17E3A696D for <dime@core3.amsl.com>; Mon, 24 Jan 2011 13:10:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 jwI1+JyyCBCk for <dime@core3.amsl.com>; Mon, 24 Jan 2011 13:10:04 -0800 (PST)
Received: from bw.ulticom.com (bw.ulticom.com [208.255.120.43]) by core3.amsl.com (Postfix) with ESMTP id B7E9F3A6A7F for <dime@ietf.org>; Mon, 24 Jan 2011 13:10:02 -0800 (PST)
Received: from colby.ulticom.com (colby.ulticom.com [192.73.206.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bw.ulticom.com (BorderWare Security Platform) with ESMTP id F9A0924F45E24389; Mon, 24 Jan 2011 16:12:56 -0500 (EST)
Received: from MTLEXVS01.ulticom.com (mtlex01.ulticom.com [172.16.40.5]) by colby.ulticom.com (8.13.4/8.12.10) with ESMTP id p0OLCdWh002779; Mon, 24 Jan 2011 16:12:44 -0500 (EST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBBC0B.6EB6A05A"
Date: Mon, 24 Jan 2011 16:12:39 -0500
Message-ID: <A51D8ACD861B7E41BFC7FE5C64BE9648135ADE1D@MTLEXVS01.ulticom.com>
In-Reply-To: <3EB9A6A055A0A74D816B7BA703D4054101A889BD37@ILHODMAIL1.corp.amdocs.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Dime] Diameter Group: Type?
Thread-Index: Acu7zcw3QXkiybOzQuybqghTUo6vYgAOXkgA
References: <3EB9A6A055A0A74D816B7BA703D4054101A889BD37@ILHODMAIL1.corp.amdocs.com>
From: David Lehmann <dlehmann@ulticom.com>
To: Erez Nassimi <erez.nassimi@amdocs.com>, dime@ietf.org
Received-SPF: pass
Subject: Re: [Dime] Diameter Group: Type?
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 24 Jan 2011 21:10:05 -0000

Erez,

 

I agree there should be a bit identifying the grouped AVPs.

 

--

David Lehmann

Ulticom, Inc.

856-787-2952

 

From: dime-bounces@ietf.org [mailto:dime-bounces@ietf.org] On Behalf Of Erez Nassimi
Sent: Monday, January 24, 2011 8:51 AM
To: dime@ietf.org
Subject: [Dime] Diameter Group: Type?

 

To whom it may concern:

======================

 

Dealing with the Diameter standard for more than 2 years, I always had the following question, I never dared to ask. But even after 2 years, I do not seem to have a good answer for it:

 

In RFC 3588, section 4.2 – AVP Data Formats, “Grouped” is defined as a “basic type”. Doesn’t it make more sense to set a flag for Grouped AVP in flags section? Group may be basic but it is not a real type. It’s just an indication of a complex data structure.

 

If “Grouped” is defined as a flag, it will simplify any parser’s work – and performance is such a rare resource.

 

Thanks in advance,

Erez Nassimi

erezna@amdocs.com <mailto:erezn@hotmail.com> 

Desk : +972-9-77-86073

Cell : +972-54-7296230

Fax  : +972-9-77-61783

 

Did you know…?

With Amdocs’ innovative new “Turbo Charging” <http://www.amdocs.com/Site/News/News+Articles/2008/Press+Releases/Turbo+Charging.htm>  complex event processing technology, service providers can process thousands of charging events per CPU in real-time over low-cost hardware (like blade servers), all with the comprehensive functionality of Amdocs CES – Billing 7.5.

 

This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp