Re: [Dime] Diameter Group: Type?
Sebastien Decugis <sdecugis@nict.go.jp> Tue, 25 January 2011 01:17 UTC
Return-Path: <sdecugis@nict.go.jp>
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 D12883A699F for <dime@core3.amsl.com>; Mon, 24 Jan 2011 17:17:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.186
X-Spam-Level:
X-Spam-Status: No, score=-2.186 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 eWHJ9nK9Ul-4 for <dime@core3.amsl.com>; Mon, 24 Jan 2011 17:17:34 -0800 (PST)
Received: from sd-22293.dedibox.fr (sd-22293.dedibox.fr [88.191.125.50]) by core3.amsl.com (Postfix) with ESMTP id 3A6EB3A6973 for <dime@ietf.org>; Mon, 24 Jan 2011 17:17:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sd-22293.dedibox.fr (Postfix) with ESMTP id CC46528064 for <dime@ietf.org>; Tue, 25 Jan 2011 02:20:12 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at sd-22293.dedibox.fr
Received: from sd-22293.dedibox.fr ([127.0.0.1]) by localhost (sd-22293.dedibox.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdW0+cFiJz+R for <dime@ietf.org>; Tue, 25 Jan 2011 02:20:06 +0100 (CET)
Received: from [202.249.37.5] (morbier.koganei.wide.ad.jp [202.249.37.5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by sd-22293.dedibox.fr (Postfix) with ESMTPSA id EC43394119 for <dime@ietf.org>; Tue, 25 Jan 2011 02:20:05 +0100 (CET)
Message-ID: <4D3E2541.4000704@nict.go.jp>
Date: Tue, 25 Jan 2011 10:20:01 +0900
From: Sebastien Decugis <sdecugis@nict.go.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: dime@ietf.org
References: <C9636A72.C0C0%avi@bridgewatersystems.com>
In-Reply-To: <C9636A72.C0C0%avi@bridgewatersystems.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
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: Tue, 25 Jan 2011 01:17:35 -0000
I agree with Avi, I think having the "grouped" information as a type makes more sense than as a flag. If the AVP code/vendor combination is unknown in the local dictionary, there is no point in being able to "parse" the inside AVPs -- and I think doing so (which would be possible with a "G"rouped flag in AVP header) would actually do more harm than good. As you wrote, parser's performance is a resource not to be wasted. Therefore, what is the point of parsing the "inside" level of AVPs when you don't understand the semantics of the grouped AVP that surrond them ? Best regards, Sebastien. Le 25/01/2011 07:48, Avi Lior a écrit : > Well, Lets say you are right. Don't you think that this is a bit late? > > But I don't agree with you that a Group is not a kind of type and > hence it could be a basic type (if you get my meaning) > > Could you explain why do you think that a flag will simplify parsing? > > -- Avi Lior > --Bridgewater Systems > > > From: Erez Nassimi <erez.nassimi@amdocs.com > <mailto:erez.nassimi@amdocs.com>> > Date: Mon, 24 Jan 2011 08:51:27 -0500 > To: "dime@ietf.org <mailto:dime@ietf.org>" <dime@ietf.org > <mailto: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 areal 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 > > > _______________________________________________ > DiME mailing list > DiME@ietf.org > https://www.ietf.org/mailman/listinfo/dime -- Sebastien Decugis Research fellow Network Architecture Group NICT (nict.go.jp)
- [Dime] Diameter Group: Type? Erez Nassimi
- Re: [Dime] Diameter Group: Type? David Lehmann
- Re: [Dime] Diameter Group: Type? Avi Lior
- Re: [Dime] Diameter Group: Type? Sebastien Decugis
- Re: [Dime] Diameter Group: Type? Ivan Skytte Jørgensen
- Re: [Dime] Diameter Group: Type? Erez Nassimi
- Re: [Dime] Diameter Group: Type? jouni korhonen
- Re: [Dime] Diameter Group: Type? Mark Jones
- Re: [Dime] Diameter Group: Type? David Lehmann
- Re: [Dime] Diameter Group: Type? David Lehmann
- Re: [Dime] Diameter Group: Type? Erez Nassimi
- Re: [Dime] Diameter Group: Type? Mark Jones
- Re: [Dime] Diameter Group: Type? jouni korhonen
- Re: [Dime] Diameter Group: Type? Glen Zorn
- Re: [Dime] Diameter Group: Type? Mark Jones
- Re: [Dime] Diameter Group: Type? David Lehmann
- Re: [Dime] Diameter Group: Type? Sebastien Decugis
- Re: [Dime] Diameter Group: Type? Avi Lior
- [Dime] rfc3588bis next revision; was Re: Diameter… jouni korhonen
- Re: [Dime] rfc3588bis next revision; was Re: Diam… Glen Zorn
- Re: [Dime] rfc3588bis next revision; was Re: Diam… jouni korhonen
- Re: [Dime] rfc3588bis next revision; was Re: Diam… lionel.morand
- Re: [Dime] rfc3588bis next revision; was Re: Diam… Glen Zorn
- Re: [Dime] rfc3588bis next revision; was Re: Diam… Romascanu, Dan (Dan)