Re: [Dime] Diameter Group: Type?

Mark Jones <mark@azu.ca> Fri, 28 January 2011 12:10 UTC

Return-Path: <mark@azu.ca>
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 E286B3A6804 for <dime@core3.amsl.com>; Fri, 28 Jan 2011 04:10:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.914
X-Spam-Level:
X-Spam-Status: No, score=-2.914 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 gPRsv5-y6sO2 for <dime@core3.amsl.com>; Fri, 28 Jan 2011 04:10:33 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id AFC303A67EC for <dime@ietf.org>; Fri, 28 Jan 2011 04:10:33 -0800 (PST)
Received: by qyk34 with SMTP id 34so739158qyk.10 for <dime@ietf.org>; Fri, 28 Jan 2011 04:13:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.84.203 with SMTP id k11mr874123qcl.281.1296216819040; Fri, 28 Jan 2011 04:13:39 -0800 (PST)
Received: by 10.229.219.197 with HTTP; Fri, 28 Jan 2011 04:13:37 -0800 (PST)
In-Reply-To: <3EB9A6A055A0A74D816B7BA703D4054101A8963DCF@ILHODMAIL1.corp.amdocs.com>
References: <3EB9A6A055A0A74D816B7BA703D4054101A8963DCF@ILHODMAIL1.corp.amdocs.com>
Date: Fri, 28 Jan 2011 13:13:37 +0100
Message-ID: <AANLkTin1r1hJsOusMyYcfo-0efNdsJVQNSp1j3o0E=by@mail.gmail.com>
From: Mark Jones <mark@azu.ca>
To: Erez Nassimi <erez.nassimi@amdocs.com>
Content-Type: multipart/alternative; boundary="0016364ef3220d12ea049ae6ff8a"
Cc: "dime@ietf.org" <dime@ietf.org>
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: Fri, 28 Jan 2011 12:10:35 -0000

Hi Erez,

Will you be raising an issue on 3588bis so the authors can fix this bug?

Thanks
Mark

On Fri, Jan 28, 2011 at 1:20 AM, Erez Nassimi <erez.nassimi@amdocs.com>wrote:

>  Guys,
>
>
>
> Thank you for the comments. I think everyone agrees there is a bug in RFC. But this can lead us to 2 different interpretations:
>
> 1.  Based on “an unrecognized bit SHOULD be considered an error”, we could assume that “subsequent Diameter applications MAY define additional bits within the AVP Header”, should have read “subsequent Diameter versions”.
>
> 2.  But the words are very clear and as of now it says “subsequent Diameter applications”.
>
> In any case, my point was rather conceptual than technical. Defining a
> Grouped AVP as a type, is similar to classifying C++ classes in the same
> category as simple types as int, char, etc. There is a difference after all.
> I found it important enough to differentiate between them with a “G” bit.
>
>
>
> Regards,
>
> *Erez Nassimi*
>
> 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
>
>