Re: [Dime] [dime] #34: Semantics of OC-Report-Type AVP
<lionel.morand@orange.com> Wed, 05 February 2014 15:14 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 E39B51A01F1 for <dime@ietfa.amsl.com>; Wed, 5 Feb 2014 07:14:01 -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 T7eaaPFQ1FDT for <dime@ietfa.amsl.com>; Wed, 5 Feb 2014 07:13:58 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by ietfa.amsl.com (Postfix) with ESMTP id AA3841A01F0 for <dime@ietf.org>; Wed, 5 Feb 2014 07:13:57 -0800 (PST)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id 781DF3B4539; Wed, 5 Feb 2014 16:13:56 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id 53E1815804E; Wed, 5 Feb 2014 16:13:56 +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:13:56 +0100
From: lionel.morand@orange.com
To: Steve Donovan <srdonovan@usdonovans.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] [dime] #34: Semantics of OC-Report-Type AVP
Thread-Index: AQHPIoJ24+/FEd2zJkuheqQLvDc97ZqmxBJg
Date: Wed, 05 Feb 2014 15:13:55 +0000
Message-ID: <32153_1391613236_52F25534_32153_19305_1_6B7134B31289DC4FAF731D844122B36E487240@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <066.b54c2f5aeb31c9b3f88c96008120290d@trac.tools.ietf.org> <24563_1391533955_52F11F82_24563_614_1_6B7134B31289DC4FAF731D844122B36E477563@PEXCVZYM13.corporate.adroot.infra.ftgroup> <52F25115.9030204@usdonovans.com>
In-Reply-To: <52F25115.9030204@usdonovans.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.1]
Content-Type: multipart/alternative; boundary="_000_6B7134B31289DC4FAF731D844122B36E487240PEXCVZYM13corpora_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.2.4.90915
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:14:02 -0000
I tend to agree except that I would reverse the logic as for the routing principles: the Destination-host takes precedence when present over Destination-Realm. So the realm abatement is applied in any case except if there is an explicit report for the destination-host. Lioenl De : DiME [mailto:dime-bounces@ietf.org] De la part de Steve Donovan Envoyé : mercredi 5 février 2014 15:56 À : dime@ietf.org Objet : Re: [Dime] [dime] #34: Semantics of OC-Report-Type AVP 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, lionel.morand@orange.com<mailto:lionel.morand@orange.com> 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:trac+dime@trac.tools.ietf.org] Envoyé : mardi 4 février 2014 09:55 À : MORAND Lionel IMT/OLN Cc : dime@ietf.org<mailto: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. _________________________________________________________________________________________________________________________ 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] [dime] #34: Semantics of OC-Report-Type AVP dime issue tracker
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Jouni Korhonen
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Jouni Korhonen
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Jouni Korhonen
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Jouni Korhonen
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Nirav Salot (nsalot)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Nirav Salot (nsalot)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Nirav Salot (nsalot)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… lionel.morand
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Jouni Korhonen
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Ben Campbell
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Maria Cruz Bartolome
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… TROTTIN, JEAN-JACQUES (JEAN-JACQUES)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Ben Campbell
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Ben Campbell
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Ben Campbell
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Steve Donovan
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Ben Campbell
- Re: [Dime] [dime] #34: Semantics of OC-Report-Typ… Wiehe, Ulrich (NSN - DE/Munich)
- Re: [Dime] [dime] #34 (draft-docdt-dime-ovli): Se… dime issue tracker
- Re: [Dime] [dime] #34 (draft-docdt-dime-ovli): Se… Steve Donovan
- Re: [Dime] [dime] #34 (draft-ietf-dime-ovli): Sem… dime issue tracker