Re: [Dime] OLR applicable for any/all applications

<lionel.morand@orange.com> Tue, 03 December 2013 11:20 UTC

Return-Path: <lionel.morand@orange.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 5DB5A1AE0A0 for <dime@ietfa.amsl.com>; Tue, 3 Dec 2013 03:20:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] 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 8dkEqyywkDNZ for <dime@ietfa.amsl.com>; Tue, 3 Dec 2013 03:20:30 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by ietfa.amsl.com (Postfix) with ESMTP id 206781AE100 for <dime@ietf.org>; Tue, 3 Dec 2013 03:20:29 -0800 (PST)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id DC3E53B42E3; Tue, 3 Dec 2013 12:20:26 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id B1EF2158062; Tue, 3 Dec 2013 12:20:26 +0100 (CET)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH02.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0158.001; Tue, 3 Dec 2013 12:20:26 +0100
From: lionel.morand@orange.com
To: "Nirav Salot (nsalot)" <nsalot@cisco.com>, Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: OLR applicable for any/all applications
Thread-Index: Ac7wA2nX03YOMS5NT1qqOpqV4/v8iQAB0nIQAAOh7+A=
Date: Tue, 03 Dec 2013 11:20:25 +0000
Message-ID: <23791_1386069626_529DBE7A_23791_980_1_6B7134B31289DC4FAF731D844122B36E312AF4@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <087A34937E64E74E848732CFF8354B920972BE0C@ESESSMB101.ericsson.se> <A9CA33BB78081F478946E4F34BF9AAA014D22CDC@xmb-rcd-x10.cisco.com>
In-Reply-To: <A9CA33BB78081F478946E4F34BF9AAA014D22CDC@xmb-rcd-x10.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.5]
Content-Type: multipart/alternative; boundary="_000_6B7134B31289DC4FAF731D844122B36E312AF4PEXCVZYM13corpora_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.19.63615
Subject: Re: [Dime] OLR applicable for any/all applications
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: Tue, 03 Dec 2013 11:20:35 -0000

Hi Maria-Cruz,

I agree with Nirav's comment: No need of such optimization. OLR is per application and if more than one application is used between nodes, the OLR will be received on the application related answers.

Regards,

Lionel

De : DiME [mailto:dime-bounces@ietf.org] De la part de Nirav Salot (nsalot)
Envoyé : mardi 3 décembre 2013 10:41
À : Maria Cruz Bartolome; dime@ietf.org
Objet : Re: [Dime] OLR applicable for any/all applications

Maria-Cruz,

The existing OC-OLR definition (without "All Application" AVP) already addresses your use case. E.g. reporting  node includes same value of "Reduction-Percentage" in all the application messages sent by it. So we don't need "All Application" AVP additionally.
Besides, reporting "Reduction-Percentage" of a different application violates the basic principle of the piggybacking.
Finally, in 3GPP (as far as I remember) we do not have any use case of two nodes interfacing with each other over more than one application. i.e. we have only one application between any pair of nodes and if that is so then I fail to see the practicality of the use case you have mentioned below.

Regards,
Nirav.

From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of Maria Cruz Bartolome
Sent: Tuesday, December 03, 2013 2:13 PM
To: dime@ietf.org
Subject: [Dime] OLR applicable for any/all applications


Dear all,

There may be a need by a reporting node to request traffic reduction for all traffic, application independent, e.g. if an operator's network becomes severely overloaded, it may be of interest to signal directly general overload to the client.
In this case, since reacting node obtains affected application from the application message, we may need to extend OLR.

At least we got following options:



A)     Define a new optional AVP that could be included into OLR, like e.g.:

   OC-OLR ::= < AVP Header: TBD2 >

              < TimeStamp >

              [ Reduction-Percentage ]

              [ ValidityDuration ]

              [ ReportType ]

              [All applications]

            * [ AVP ]



B)      Extend  ReportTypes like e.g.:

   3  Destination-Host All Applications report.  Similar to Destination-Host report but it would apply to any application regardless the application message this report is received within.

   4  Realm (aggregated) All Applications report.  Similar to Realm report but it would apply to any application regardless the application message this report is received within.



I tend to prefer option A, but let me know your opinions and preferences.
Best regards
/MCruz



_________________________________________________________________________________________________________________________

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.