Re: [Dime] Diameter Group: Type?

jouni korhonen <jouni.nospam@gmail.com> Fri, 28 January 2011 13:23 UTC

Return-Path: <jouni.nospam@gmail.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 2AFD13A688B for <dime@core3.amsl.com>; Fri, 28 Jan 2011 05:23:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 V7528jBiOPwN for <dime@core3.amsl.com>; Fri, 28 Jan 2011 05:23:26 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id B2B213A67AD for <dime@ietf.org>; Fri, 28 Jan 2011 05:23:25 -0800 (PST)
Received: by wyf23 with SMTP id 23so3294895wyf.31 for <dime@ietf.org>; Fri, 28 Jan 2011 05:26:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=1O2Aln5C8daAMtWFXzlHzQ5FbNa/g0NGdmwFU86jPDE=; b=Yb1zwzN9iaPJkAziP6ciKZ9mmfY40neIc32xBrRS7NAqrTr/9/mRkWb83cE63Mp4VM PH8GYweOEM4gUCh4JHA4ptTb+2XVCaxmtFpGexY9lzULi7g/J+xuufbgrbhUQ0uEK5qV Qutsxk9Mk48OePQaHucl2iyk/D5agqirto17E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=HA1mmAmMJcACDmmqfsrEXZR2SP5Y8xkQI0ek6MgjtzOoV+Yv5Du0O4wAaMl1z34wPv AHbsuTXuvxAiLYMy5oS9fDH/TTSf7THbgCaoj5LGApVRKAjz7fnuzH3C6nF26BKkzexQ pKjZO3SU4wXMiVKK30HObz7kS6AnFIjuUKHR0=
Received: by 10.216.143.17 with SMTP id k17mr7548783wej.74.1296221191310; Fri, 28 Jan 2011 05:26:31 -0800 (PST)
Received: from [10.255.136.113] ([192.100.123.77]) by mx.google.com with ESMTPS id u2sm6424036weh.12.2011.01.28.05.26.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 28 Jan 2011 05:26:29 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="windows-1252"
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <AANLkTin1r1hJsOusMyYcfo-0efNdsJVQNSp1j3o0E=by@mail.gmail.com>
Date: Fri, 28 Jan 2011 15:26:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <56FEA2B3-8A50-4606-B0F1-108A79C0A8DA@gmail.com>
References: <3EB9A6A055A0A74D816B7BA703D4054101A8963DCF@ILHODMAIL1.corp.amdocs.com> <AANLkTin1r1hJsOusMyYcfo-0efNdsJVQNSp1j3o0E=by@mail.gmail.com>
To: dime@ietf.org
X-Mailer: Apple Mail (2.1078)
Cc: Erez Nassimi <erez.nassimi@amdocs.com>
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 13:23:27 -0000

I would encourage 3588bis authors to look into this specific place. I also think it is an error that needs to be fixed.

- Jouni

On Jan 28, 2011, at 2:13 PM, Mark Jones wrote:

> 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
> 
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime