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

Steve Donovan <srdonovan@usdonovans.com> Tue, 03 December 2013 15:39 UTC

Return-Path: <srdonovan@usdonovans.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 ED5511AE19A for <dime@ietfa.amsl.com>; Tue, 3 Dec 2013 07:39:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level:
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_NEUTRAL=0.779] autolearn=no
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 RSNsVamNxfja for <dime@ietfa.amsl.com>; Tue, 3 Dec 2013 07:39:46 -0800 (PST)
Received: from biz131.inmotionhosting.com (biz131.inmotionhosting.com [173.247.247.114]) by ietfa.amsl.com (Postfix) with ESMTP id 6931B1AE187 for <dime@ietf.org>; Tue, 3 Dec 2013 07:39:46 -0800 (PST)
Received: from cpe-76-187-100-94.tx.res.rr.com ([76.187.100.94]:50135 helo=SDmac.local) by biz131.inmotionhosting.com with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <srdonovan@usdonovans.com>) id 1Vns4Z-00064i-8u for dime@ietf.org; Tue, 03 Dec 2013 07:39:43 -0800
Message-ID: <529DFB3B.3080109@usdonovans.com>
Date: Tue, 03 Dec 2013 09:39:39 -0600
From: Steve Donovan <srdonovan@usdonovans.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: dime@ietf.org
References: <087A34937E64E74E848732CFF8354B920972BE0C@ESESSMB101.ericsson.se> <A9CA33BB78081F478946E4F34BF9AAA014D22CDC@xmb-rcd-x10.cisco.com>
In-Reply-To: <A9CA33BB78081F478946E4F34BF9AAA014D22CDC@xmb-rcd-x10.cisco.com>
Content-Type: multipart/alternative; boundary="------------080302000405000505090503"
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz131.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - usdonovans.com
X-Get-Message-Sender-Via: biz131.inmotionhosting.com: authenticated_id: srdonovan@usdonovans.com
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 15:39:49 -0000

Nirav,

Agents handle multiple applications over a single connection.

It is also possible that implementations can support multiple 3GPP
functions in a single node.  For instance, someone might decide to
implement a combined HSS and EIR, causing the MME to communicate S6a and
S13 over the same connection.

Steve

On 12/3/13 3:41 AM, Nirav Salot (nsalot) wrote:
>
> 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 Applicationsreport.  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
>
>  
>
>  
>
>
>
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime