Re: [Dime] [dime] #54: OC-Report-Type as mandatory AVP
"TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <jean-jacques.trottin@alcatel-lucent.com> Thu, 13 February 2014 08:55 UTC
Return-Path: <jean-jacques.trottin@alcatel-lucent.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 112EC1A015B for <dime@ietfa.amsl.com>; Thu, 13 Feb 2014 00:55:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pPF0I3n4HRNe for <dime@ietfa.amsl.com>; Thu, 13 Feb 2014 00:55:47 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 31A3C1A0085 for <dime@ietf.org>; Thu, 13 Feb 2014 00:55:47 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s1D8tfwb017259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 13 Feb 2014 02:55:43 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s1D8teJ2032019 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 13 Feb 2014 09:55:41 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Thu, 13 Feb 2014 09:55:40 +0100
From: "TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <jean-jacques.trottin@alcatel-lucent.com>
To: "dime@ietf.org" <dime@ietf.org>, "maria.cruz.bartolome@ericsson.com" <maria.cruz.bartolome@ericsson.com>
Thread-Topic: [Dime] [dime] #54: OC-Report-Type as mandatory AVP
Thread-Index: AQHPJ/5W67jltt6LBECHcH6+O45QI5qxoXkAgAE/IXA=
Date: Thu, 13 Feb 2014 08:55:40 +0000
Message-ID: <E194C2E18676714DACA9C3A2516265D2026649A3@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <075.72da31b401c033905a4fb81d09a8b4aa@trac.tools.ietf.org> <7077_1392216348_52FB891B_7077_4146_1_6B7134B31289DC4FAF731D844122B36E49E1A4@PEXCVZYM13.corporate.adroot.infra.ftgroup>
In-Reply-To: <7077_1392216348_52FB891B_7077_4146_1_6B7134B31289DC4FAF731D844122B36E49E1A4@PEXCVZYM13.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [Dime] [dime] #54: OC-Report-Type as mandatory AVP
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 13 Feb 2014 08:55:50 -0000
Hi Mcruz The current description indicates that when not present the OLR is of type Host, which was fine for me and keeps my preference. We may have deployments where Realm OLR is not used, or where statistically the HOST type is the most frequent, so to have the grouped OLR-AVP containing a minimum of AVPs minimizes parsing. I agree it is a small optimization. Best regards JJacques -----Message d'origine----- De : DiME [mailto:dime-bounces@ietf.org] De la part de lionel.morand@orange.com Envoyé : mercredi 12 février 2014 15:46 À : dime@ietf.org; maria.cruz.bartolome@ericsson.com Objet : Re: [Dime] [dime] #54: OC-Report-Type as mandatory AVP Hi Maria Cruz, I'm assuming that you mean "required" instead of "mandatory", right? So instead of: OC-OLR ::= < AVP Header: TBD2 > < OC-Sequence-Number > [ OC-Report-Type ] [ OC-Reduction-Percentage ] [ OC-Validity-Duration ] * [ AVP ] You would prefer: OC-OLR ::= < AVP Header: TBD2 > < OC-Sequence-Number > { OC-Report-Type } [ OC-Reduction-Percentage ] [ OC-Validity-Duration ] * [ AVP ] And I'm fine with this proposal. Cheers, Lionel -----Message d'origine----- De : DiME [mailto:dime-bounces@ietf.org] De la part de dime issue tracker Envoyé : mercredi 12 février 2014 15:26 À : maria.cruz.bartolome@ericsson.com Cc : dime@ietf.org Objet : [Dime] [dime] #54: OC-Report-Type as mandatory AVP #54: OC-Report-Type as mandatory AVP Now in chapter 4.6: The default value of the OC-Report-Type AVP is 0 (i.e. the host report). This AVP is always required, right? Then, I think it is more precise that we define this AVP as mandatory. -- -----------------------------------------------+------------------------ -----------------------------------------------+--- Reporter: maria.cruz.bartolome@ericsson.com | Owner: MCruz Type: defect | Bartolomé Priority: major | Status: new Component: draft-docdt-dime-ovli | Milestone: Severity: Active WG Document | Version: 1.0 | Keywords: -----------------------------------------------+------------------------ -----------------------------------------------+--- Ticket URL: <http://trac.tools.ietf.org/wg/dime/trac/ticket/54> dime <http://tools.ietf.org/wg/dime/> _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ DiME mailing list DiME@ietf.org https://www.ietf.org/mailman/listinfo/dime
- [Dime] [dime] #54: OC-Report-Type as mandatory AVP dime issue tracker
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… lionel.morand
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Jouni Korhonen
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Steve Donovan
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Ben Campbell
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Maria Cruz Bartolome
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Jouni Korhonen
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Jouni Korhonen
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Steve Donovan
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Maria Cruz Bartolome
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Steve Donovan
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Jouni Korhonen
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Steve Donovan
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… lionel.morand
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Steve Donovan
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Steve Donovan
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… lionel.morand
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… lionel.morand
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… lionel.morand
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… lionel.morand
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Maria Cruz Bartolome
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Steve Donovan
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… lionel.morand
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… lionel.morand
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… lionel.morand
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Shishufeng (Susan)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… lionel.morand
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- [Dime] Large messages on list? David Mitton
- Re: [Dime] [dime] #54: OC-Report-Type as mandator… Benoit Claise
- Re: [Dime] [dime] #54 (draft-ietf-dime-ovli): OC-… dime issue tracker
- Re: [Dime] [dime] #54 (draft-ietf-dime-ovli): OC-… dime issue tracker