Re: [Dime] Definition of host report

<lionel.morand@orange.com> Tue, 08 April 2014 13:23 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 E52771A03C4 for <dime@ietfa.amsl.com>; Tue, 8 Apr 2014 06:23:31 -0700 (PDT)
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 1cKtjCTkWmIn for <dime@ietfa.amsl.com>; Tue, 8 Apr 2014 06:23:27 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) by ietfa.amsl.com (Postfix) with ESMTP id CC9151A0379 for <dime@ietf.org>; Tue, 8 Apr 2014 06:23:26 -0700 (PDT)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id C8A7F3B41F0; Tue, 8 Apr 2014 15:23:25 +0200 (CEST)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id ABAACC807F; Tue, 8 Apr 2014 15:23:25 +0200 (CEST)
Received: from PEXCVZYM13.corporate.adroot.infra.ftgroup ([fe80::cc7e:e40b:42ef:164e]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0181.006; Tue, 8 Apr 2014 15:23:25 +0200
From: <lionel.morand@orange.com>
To: Steve Donovan <srdonovan@usdonovans.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] Definition of host report
Thread-Index: AQHPUytwZFDFsRdQF02SAbAlZFyGjJsHsYJg
Date: Tue, 8 Apr 2014 13:23:24 +0000
Message-ID: <29259_1396963405_5343F84D_29259_1241_1_6B7134B31289DC4FAF731D844122B36E54C7C3@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <5342AAD9.9030803@usdonovans.com> <28937_1396879717_5342B165_28937_9147_1_6B7134B31289DC4FAF731D844122B36E548C2D@PEXCVZYM13.corporate.adroot.infra.ftgroup> <534318C7.1060502@usdonovans.com> <7558_1396959635_5343E993_7558_7400_1_6B7134B31289DC4FAF731D844122B36E54C514@PEXCVZYM13.corporate.adroot.infra.ftgroup> <5343F470.50808@usdonovans.com>
In-Reply-To: <5343F470.50808@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.2]
Content-Type: multipart/alternative; boundary="_000_6B7134B31289DC4FAF731D844122B36E54C7C3PEXCVZYM13corpora_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.19.63615
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/xFiAYLLLFhUSRgUTFomvPAu9xu8
Subject: Re: [Dime] Definition of host report
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, 08 Apr 2014 13:23:32 -0000

I see my mistake. I was confused by "the overloaded Diameter node identified by the Diameter ID in the OLR"
Therefore, I agree with the proposed change. In order to keep the existing text, do you think that the following wording would be clear enough:


      Either 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; Either the Destination-Host is not present

      in the request but the value of peer identity associated with the connection

      used to send the request matches the value of the Origin-Host AVP of the

      received message that contained the OC-OLR AVP.

Regards,

Lionel

De : Steve Donovan [mailto:srdonovan@usdonovans.com]
Envoyé : mardi 8 avril 2014 15:07
À : MORAND Lionel IMT/OLN; dime@ietf.org
Objet : Re: [Dime] Definition of host report

Lionel,

I'm not proposing adding an AVP to the overload report.  I should have said the Diameter ID in the overload control state.  I agree completely that the Diameter ID comes from the Origin-Host AVP in the answer message containing the OLR.

Regards,

Steve
On 4/8/14 7:20 AM, lionel.morand@orange.com<mailto:lionel.morand@orange.com> wrote:

Hi Steve,



I understand your point now. Thank you for the clarification.



However, I don't think that it leads necessarily to the need for a Diameter Id in the OLR.



The clarification could be that, in case of direct connection between clients and servers, the Host report type applies also to the peer connection for which the peer id is equal to the origin-host in the answer containing the OLR. Such binding is required and the Diameter Id in the OLR will not provide added-value compared to the origin-host of the answer.



Regards,



Lionel





De : Steve Donovan [mailto:srdonovan@usdonovans.com]

Envoyé : lundi 7 avril 2014 23:30

À : MORAND Lionel IMT/OLN; dime@ietf.org<mailto:dime@ietf.org>

Objet : Re: [Dime] Definition of host report



Lionel,



Please see inline.



Steve

On 4/7/14 9:07 AM, lionel.morand@orange.com<mailto:lionel.morand@orange.com> wrote:

Hi Steve,



As defined today, the originator of a Host-based report is the node identified by the Origin-host in the answer. I don't understand what is wrong with the existing definition in the draft.



Please see below.



Regards,



Lionel



De : DiME [mailto:dime-bounces@ietf.org] De la part de Steve Donovan

Envoyé : lundi 7 avril 2014 15:41

À : dime@ietf.org<mailto:dime@ietf.org>

Objet : [Dime] Definition of host report



All,



I believe that the current definition of the host report needs to be enhanced.



The following is what is currently in the -02 draft:

   0  A host report.  The overload treatment should apply to requests

      for which all of the following conditions are true:



      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.



      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.



      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.



The second paragraph says that only requests that contain a Destination-Host AVP can be used for overload treatment.



This does not address the case where there is no agent between the reacting and reporting nodes.

[LM] I think you mean: this does ONLY address, right?

SRD> No, I mean the case where a client is connected directly to a set of servers.  One of the servers becomes overloaded and sends a host report.  The server is telling clients to reduce the traffic sent to it by x%.  The client selects a route for the request.  Any request that would be routed to the connection to the server should be a candidate for overload treatment.  If this is not the case then how do you protect a server for an application that has 100% realm routed requests?



In other words, the reacting node has a direct connection to the reporting node.  In this case the reacting node should include all messages that would be sent to the reporting node, including those that do not contain a Destination-Host AVP and those that the reacting node would sent to the reporting node through normal route selection for requests that do not contain a Destination-Host AVP.

[LM] I'm not sure to understand the reasoning above. Why should a reacting node include request with no Dest-Host AVP?

SRD> Because there is nothing else in the network that can manage that traffic.







I propose that the second paragraph be changed to the following:



"The reacting node knows that the request will be routed to the overloaded Diameter node identified by the Diameter ID in the OLR.  This is the value of the Origin-Host AVP in the message that carried the OLR.  There are two cases where the reacting node will know that the request will be routed to the overloaded node.  The first is the request contains a Destination-Host AVP that matches the Diameter ID contained in the OLR.  The second is when the reacting node selects a route that is a direct connection to the overloaded Diameter node."

[LM] this is not needed if the Origin-host in the answer is enough to identify which node is overloaded, that is the current assumption in the draft.



Regards,



Steve



_________________________________________________________________________________________________________________________



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.









_________________________________________________________________________________________________________________________



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.






_________________________________________________________________________________________________________________________

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.