IETF Logo Mail Archive

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

<lionel.morand@orange.com> Wed, 05 February 2014 15:18 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 83ACD1A0216 for <dime@ietfa.amsl.com>; Wed, 5 Feb 2014 07:18:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=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 RSKAzkSLTQTf for <dime@ietfa.amsl.com>; Wed, 5 Feb 2014 07:18:49 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 6DDDF1A0202 for <dime@ietf.org>; Wed, 5 Feb 2014 07:18:48 -0800 (PST)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 7F7F73B4109; Wed, 5 Feb 2014 16:18:47 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 5FFEB35C06C; Wed, 5 Feb 2014 16:18:47 +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.0174.001; Wed, 5 Feb 2014 16:18:47 +0100
From: lionel.morand@orange.com
To: "Wiehe, Ulrich (NSN - DE/Munich)" <ulrich.wiehe@nsn.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [dime] #34: Semantics of OC-Report-Type AVP
Thread-Index: AQHPIcxQ8/v/z65LoEmP8SlQdkHvG5qme77QgABKjdA=
Date: Wed, 05 Feb 2014 15:18:46 +0000
Message-ID: <7451_1391613527_52F25657_7451_48_1_6B7134B31289DC4FAF731D844122B36E487279@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <066.b54c2f5aeb31c9b3f88c96008120290d@trac.tools.ietf.org> <24563_1391533955_52F11F82_24563_614_1_6B7134B31289DC4FAF731D844122B36E477563@PEXCVZYM13.corporate.adroot.infra.ftgroup> <5BCBA1FC2B7F0B4C9D935572D9000668151B2062@DEMUMBX014.nsn-intra.net>
In-Reply-To: <5BCBA1FC2B7F0B4C9D935572D9000668151B2062@DEMUMBX014.nsn-intra.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.20.60015
Subject: Re: [Dime] [dime] #34: Semantics of OC-Report-Type 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: Wed, 05 Feb 2014 15:18:52 -0000

Here, you assume both types of reports sent back to the client.
My point was: if only realm-based report are sent to the client, the abatement will apply whatever the type of requests sent to the realm, with or without destination-host... whereas in your description for realm report it was said that the destination-host was absent.

This point is clarified in the other mail, in response/complement to Steve.

Lionel



-----Message d'origine-----
De : Wiehe, Ulrich (NSN - DE/Munich) [mailto:ulrich.wiehe@nsn.com] 
Envoyé : mercredi 5 février 2014 12:38
À : MORAND Lionel IMT/OLN; dime@ietf.org
Objet : RE: [dime] #34: Semantics of OC-Report-Type AVP

Sorry, I don't understand the question.

An agent that is configured to take the role of a reporting node for a realm 
- will send (insert) realm type OLRs in answer messages that correspond to realm type request messages (request messages that do not contain a destination host), and
- will be transparent with regard to host type request messages (request messages that contain a destination hostand answer messages) and the corresponding answer messages.
Consequently the reacting node will receive realm type OLRs from the agent and host type OLRs from the servers.
The received realm type OLR will be relevant for the reacting node when sending/throttling realm type requests; the received host type OLR will be relevant for the reacting node when sending/throttling host type requests.



+--------+                                         +--------+                +--------+
| Client |                                         | Agent  |                | Server |
|        |                                         |        |                |        |
|        |                                         |        |                |        | 
+--------+                                         +--------+                +--------+
    |                                                |                             |
    |<---DOIC association 1------------------------->|<-------DOIC association 2-->|
    |                                                |                             |
    |<-----------------DOIC association 3----------------------------------------->|
    |                                                |                             |
    |                                                |                             |
    |                                                |                             |
    |---1.xxR-----(realm type request)-------------->|agent selects server         |
    |                                                |--------2.xxR--------------->| 
    |                                                |<-------3.xxA----------------|
    |<--4.xxA-----(realm type OLR )------------------|agent inserts OLR            |
    |                                                |                             |
    |                                                |                             |
    |                                                |                             |
    |                                                |                             |
    |                                                |                             |
    |                                                |                             |
    |---5.xxR-----(host type request)----------------|---------------------------->|
    |                                                |agent is transparent         |
    |<--6.xxA-----(host type OLR)--------------------|-----------------------------|
    |                                                |                             |
    |                                                |                             |
    |---7.xxR--(realm type request)->x throttled     |                             |
    |                                  according to  |                             |
    |                                  the receive   |                             |
    |                                  realm type OLR|                             |
    |                                                |                             |
    |                                                |                             |
    |---8.xxR--(host type request)->x  throttled     |                             |
    |                                  according to  |                             |
    |                                  the receive   |                             |
    |                                  host type OLR |                             |
    |                                                |                             |
    |                                                |                             | 
-----Original Message-----
From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of ext lionel.morand@orange.com
Sent: Tuesday, February 04, 2014 6:13 PM
To: dime@ietf.org
Subject: Re: [Dime] [dime] #34: Semantics of OC-Report-Type AVP

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:trac+dime@trac.tools.ietf.org] 
Envoyé : mardi 4 février 2014 09:55
À : MORAND Lionel IMT/OLN
Cc : dime@ietf.org
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.

-- 
--------------------------------------+--------------------------
 Reporter:  lionel.morand@orange.com  |      Owner:  Ulrich Wiehe
     Type:  defect                    |     Status:  new
 Priority:  major                     |  Milestone:
Component:  draft-docdt-dime-ovli     |    Version:
 Severity:  Active WG Document        |   Keywords:
--------------------------------------+--------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/dime/trac/ticket/34>
dime <http://tools.ietf.org/wg/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

_________________________________________________________________________________________________________________________

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.

v2.23.0 | Report a Bug | By Email