Re: [Dime] Conclusion for the Report Type

"TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <> Mon, 16 December 2013 17:53 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 0AD111AE0C3 for <>; Mon, 16 Dec 2013 09:53:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id eYa8UHglTe-r for <>; Mon, 16 Dec 2013 09:52:58 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id EECF21ADF9B for <>; Mon, 16 Dec 2013 09:52:57 -0800 (PST)
Received: from ( []) by (8.13.8/IER-o) with ESMTP id rBGHqtVM005678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <>; Mon, 16 Dec 2013 11:52:56 -0600 (CST)
Received: from ( []) by (GMO) with ESMTP id rBGHqsFG009208 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <>; Mon, 16 Dec 2013 18:52:54 +0100
Received: from ([]) by ([]) with mapi id 14.02.0247.003; Mon, 16 Dec 2013 18:52:54 +0100
To: " list" <>
Thread-Topic: [Dime] Conclusion for the Report Type
Thread-Index: AQHO9NZTfmjwZl8bgUqgMbcmsBQ2dppXB06AgAAcu4A=
Date: Mon, 16 Dec 2013 17:52:54 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on
Subject: Re: [Dime] Conclusion for the Report Type
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 16 Dec 2013 17:53:00 -0000


About Enumerated versus unsigned (flag vector), Lionel is in favour of using unsigned (flag vector) due to the issue  for adding a new emulated value in the future to the existing one, creating backward compatibility. In  3GPP CT4 it is the unsigned (flag vector rule we apply for new AVPs, so I would prefer to be consistent by using the same rule. It would be good to have Lionel's view on this.

Best regards



-----Message d'origine-----
De : DiME [] De la part de Maria Cruz Bartolome
Envoyé : lundi 16 décembre 2013 18:04
À : Jouni Korhonen; list
Objet : Re: [Dime] Conclusion for the Report Type


I agree on the principles.
Enumerated is fine for me as well.

Best regards

-----Original Message-----
From: DiME [] On Behalf Of Jouni Korhonen
Sent: lunes, 09 de diciembre de 2013 13:00
To: list
Subject: [Dime] Conclusion for the Report Type


We need a conclusion here so that I can actually write something into the -01. How about the following (I try to reflect as many points given here as possible):

1) The basic principle for the Report Type use is that only one
   OLR per report type is allowed unless the report type and the
   OLR reflecting the new report type define exact semantics how
   to differentiate between multiple OLRs with the same report
   type. In 3GPP context, for example, a report type with an AVP
   that identifies an APN could be such a differentiator.. and that
   would need a new report type where an implementation exactly
   knows to look for this additional AVP without guesswork or 
   fuzzy heuristics.

2) A new report type or a set of new report types require a new
   feature to be allocated/defined so that both endpoints know how
   to handle the new report type that was defined after the
   publication of the baseline specification. The handling of the
   new report types must be defined (along with the new AVPs it
   might need to be included into the OC-OLR AVP).

3) With 2) in place I do not care whether the OC-Report-Type is
   enumerated or unsigned (flag vector?). I still favour Enumerated
   myself as it forces the protocol designer to come up with a 
   cleaner design ;)

4) For the baseline we only define host and realm report types.
   We do not allow multiple OLRs with these report types i.e.
   single instances of OLRs with host and/or realm are allowed.

- Jouni
DiME mailing list
DiME mailing list