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

Not exactly.
It was opposition to duplicate information.

Cheers
/MCruz

-----Original Message-----
From: Jouni Korhonen [mailto:jouni.nospam@gmail.com] 
Sent: martes, 03 de diciembre de 2013 10:26
To: Maria Cruz Bartolome
Cc: dime@ietf.org
Subject: Re: [Dime] OLR applicable for any/all applications

Hmm.. wasn't there just recently rather strong opposition to include anything beyond "implicit" information into the OLR?

- Jouni

On Dec 3, 2013, at 10:42 AM, Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com> wrote:

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