Re: [Dime] [dime] #34: Semantics of OC-Report-Type AVP

[Steve Donovan <[e-mail]>]

It makes more sense to me for a realm report to apply to all requests
targeted for that realm, independent the type of request.  This implies
that it would apply to requests that also have a Destination-Host specified.

If this is the definition of a realm report then we need to specify the
interaction between realm reports and host reports.

I propose that throttling would occur on the realm first and the host
second.  If a message targetted for the host is throttled as a result of
realm overload then that throttled message would count as part of the
reduction needed to address the host overload.  Messages to the host
that survive realm abatement would then be candidates for host overload.

Steve

On 2/4/14 11:12 AM, [e-mail] wrote:
> The case "Realm" as described below raises another question: is it prohibited for a realm to only rely on a global overload report for the whole realm, whatever the nodes inside this realm?
> If not, only OLR with the report type "realm" would be received by the reacting node. And the reduction indicated in the OLR will apply always for the realm, whatever the presence of Destination-host AVP in the request... except if an explicit report with the type "Host" as been received for this destination-host.
>
> Does it make sense?
>
> Lionel
>
> -----Message d'origine-----
> De : dime issue tracker [mailto:[e-mail]] 
> Envoyé : mardi 4 février 2014 09:55
> À : MORAND Lionel IMT/OLN
> Cc : [e-mail]
> Objet : [dime] #34: Semantics of OC-Report-Type AVP
>
> #34: Semantics of OC-Report-Type AVP
>
>  Text in clause 4.6  does not fully explain to which requests overload
>  treatment of a given report type applies.
>  Proposal:
>
>     0  A host report.  The overload treatment should apply to requests
>        for which all of the following conditions are true:
>        a) The Destination-Host AVP is present in the request and its value
>           matches the value of the Origin-Host AVP of the received message
>           that contained the OC-OLR AVP.
>        b) The value of the Destination-Realm AVP in the request matches the
>           value of the Origin-Realm AVP of the received message
>           that contained the OC-OLR AVP.
>        c) The value of the Application-ID in the Diameter Header of the
>           request matches the value of the Application-ID of the Diameter
>           Header of the received message that contained the OC-OLR AVP.
>
>
>
>     1  A realm report.  The overload treatment should apply to
>        requests for which all of the following conditions are true:
>        a) The Destination-Host AVP is absent in the request.
>        b) The value of the Destination-Realm AVP in the request matches the
>           value of the Origin-Realm AVP of the received message
>           that contained the OC-OLR AVP.
>        c) The value of the Application-ID in the Diameter Header of the
>           request matches the value of the Application-ID of the Diameter
>           Header of the received message that contained the OC-OLR AVP.
>