Re: [Dime] [dime] #69 (draft-ietf-dime-ovli): Report Type - Realm, with absent Destination-Host

Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com> Fri, 26 September 2014 09:58 UTC

Return-Path: <maria.cruz.bartolome@ericsson.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 D70DC1A1ABB for <dime@ietfa.amsl.com>; Fri, 26 Sep 2014 02:58:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 QtdoOuum2ZgJ for <dime@ietfa.amsl.com>; Fri, 26 Sep 2014 02:58:10 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CF8D1A1ABF for <dime@ietf.org>; Fri, 26 Sep 2014 02:58:08 -0700 (PDT)
X-AuditID: c1b4fb30-f79736d0000053b8-17-542538af2945
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 11.D4.21432.FA835245; Fri, 26 Sep 2014 11:58:07 +0200 (CEST)
Received: from ESESSMB101.ericsson.se ([169.254.1.19]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0174.001; Fri, 26 Sep 2014 11:58:06 +0200
From: Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com>
To: "TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <jean-jacques.trottin@alcatel-lucent.com>, "dime@ietf.org" <dime@ietf.org>, "draft-ietf-dime-ovli@tools.ietf.org" <draft-ietf-dime-ovli@tools.ietf.org>
Thread-Topic: [Dime] [dime] #69 (draft-ietf-dime-ovli): Report Type - Realm, with absent Destination-Host
Thread-Index: AQHPyNyuNnzaufIU0EqXUbjmECT9z5vydJoAgAr8v/CAFLcIUIAA7XjggAA4s8A=
Date: Fri, 26 Sep 2014 09:58:05 +0000
Message-ID: <087A34937E64E74E848732CFF8354B920983BF65@ESESSMB101.ericsson.se>
References: <075.41a258960641a985e7e7d8a618123b41@trac.tools.ietf.org> <5409C5A4.5090203@usdonovans.com> <E194C2E18676714DACA9C3A2516265D2026C30A4@FR712WXCHMBA12.zeu.alcatel-lucent.com> <087A34937E64E74E848732CFF8354B920983BD00@ESESSMB101.ericsson.se> <E194C2E18676714DACA9C3A2516265D2026CCAD1@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <E194C2E18676714DACA9C3A2516265D2026CCAD1@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.150]
Content-Type: multipart/mixed; boundary="_002_087A34937E64E74E848732CFF8354B920983BF65ESESSMB101erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAIsWRmVeSWpSXmKPExsUyM+Jvje56C9UQgwMPhC3m9q5gs1h+vIHZ YtP5dSwOzB6tz/ayeixZ8pPJ48vlz2wBzFFcNimpOZllqUX6dglcGdO2HWQq2PSJsWLbmpvM DYzTHzN2MXJySAiYSHzpWsAKYYtJXLi3ng3EFhI4yiixb61VFyMXkL2YUeLCpXawIjYBO4lL p18wgSREBI4xSjRPfMkEkhAWyJL40LeVHcQWEciWuNW6nBHC9pNY+HUqC4jNIqAqcWnjbmYQ m1fAV+La7Z+MEBuuMElc2LINrJlTIFai8fJGsKGMQCd9P7UGzGYWEJe49WQ+E8SpIhIPL55m g7BFJV4+/gf1gpLEiu2XGCHqMyWWr25kh1gmKHFy5hOWCYwis5CMmoWkbBaSMoi4nsSNqVPY IGxtiWULXzND2HUS91rPMkLYxhInNj4FquECsvcwSqzddQqqSFFiSvdD9gWMnKsYRYtTi5Ny 042M9FKLMpOLi/Pz9PJSSzYxAqP04JbfBjsYXz53PMQowMGoxMO74IRKiBBrYllxZe4hRmkO FiVx3oXn5gULCaQnlqRmp6YWpBbFF5XmpBYfYmTi4JRqYOxia1J4PenYpI2J3d/5akv+rU7c qf63trL05tnrElvElb5uLAxmjGLK+x/2VM2vrviExplz/12fbZm2qLxy55H/3yvO3ljWlv/z sNApxWcZ4fodU9v8hPatm/K14sf06tV8p/gvbGU3Xq63/ULsd7viDcubU7f95bfaU2mnHv1t fUtm1coNd38qsRRnJBpqMRcVJwIArAE+3rMCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/GPHOXwxiE6x7MnEpkj1tr0bNtuA
Subject: Re: [Dime] [dime] #69 (draft-ietf-dime-ovli): Report Type - Realm, with absent Destination-Host
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: Fri, 26 Sep 2014 09:58:13 -0000

Dear JJ, all

I think I understand your concern.
I modified text in clause 6.6 to clarify this point. Attached.
Let me know your opinions.
Best regards
/MCruz


-----Original Message-----
From: TROTTIN, JEAN-JACQUES (JEAN-JACQUES) [mailto:jean-jacques.trottin@alcatel-lucent.com] 
Sent: viernes, 26 de septiembre de 2014 10:12
To: Maria Cruz Bartolome; dime@ietf.org; draft-ietf-dime-ovli@tools.ietf.org
Subject: RE: [Dime] [dime] #69 (draft-ietf-dime-ovli): Report Type - Realm, with absent Destination-Host


Hi Maria Cruz

1) The hereafter proposed text  is in a sub part of section 6.6 addressing  the overload treatment when the  OC-report type indicates realm report so according to a Realm type OLR. The proposed  text mentions "...Origin-Host AVP of the received message that contained the OC-OLR AVP". This  OC-OLR AVP can be understood  as the Realm type OLR subject of this section 6.6 subpart (this was my first reading), but it is another report which is a host type OLR generated by this peer. 
As you said we have to distinguish when either a host or a realm report to be applied, so here the proposal is to exclude from the text the case where the reacting node has an active type Host type OLR of which the Origin Host match the peer identity, as for this case the host type OLR will be applied. On this basis I would propose write "Host type OC-OLR AVP" as hereafter.   

"The Destination-Host AVP is absent in the request and the value of peer identity associated with the connection used to send the request does not match the value of the Origin-Host AVP of a received message that contained a Host type OC-OLR AVP"

2) When thinking a bit more to this case where the reacting node is directly connected to the reporting node (eg a Client directly connected to two or more servers, without intermediate DA, or a DA acting as a reacting node directly connected to servers). The servers usually only send Host type reports (I know there  is a  debate on servers sending realm reports), so the reacting node will not receive Realm reports.  For requests for which there is no destination Host, the reacting node will select the peer according to the host OLRs  it has or not for each of the peers (eg a peer that is not overload or with a small overload )  and then apply the abatement/throttling according to the Host type OLR of this peer. I think we have the same understanding.       


Best regards

JJacques 

-----Message d'origine-----
De : Maria Cruz Bartolome [mailto:maria.cruz.bartolome@ericsson.com]
Envoyé : jeudi 25 septembre 2014 18:28
À : TROTTIN, JEAN-JACQUES (JEAN-JACQUES); dime@ietf.org; draft-ietf-dime-ovli@tools.ietf.org
Objet : RE: [Dime] [dime] #69 (draft-ietf-dime-ovli): Report Type - Realm, with absent Destination-Host

Dear JJ,

I do not understand your point.

Proposed clarification has the purpose to allow a reacting node to distinguish when either a host or a realm report shall apply.

Some time ago we based such a distinction on the presence (meaning host report) or absence (meaning realm report).
Now we have covered the case for host reports when the host is absent but it refers to the directly connected peer. Therefore, just absence does not allow the reacting node to identify it has to apply a realm report.

Let me know if this clarifies, or if I may be missing your point.
Thanks
/MCruz


-----Original Message-----
From: TROTTIN, JEAN-JACQUES (JEAN-JACQUES) [mailto:jean-jacques.trottin@alcatel-lucent.com]
Sent: viernes, 12 de septiembre de 2014 14:13
To: dime@ietf.org; draft-ietf-dime-ovli@tools.ietf.org; Maria Cruz Bartolome
Subject: RE: [Dime] [dime] #69 (draft-ietf-dime-ovli): Report Type - Realm, with absent Destination-Host

Hi MCruz

The proposed  text applies to the realm report. 

Realm OLRs (in particular with same seq number) may be conveyed in answers with different Origin-host (but with same Origin realm), so what means to refer "to the Origin-Host AVP of the received message that contained the (realm type) OC-OLR AVP". This is different  from the Host report, where the host type OC-OLR always refers to the origin host  of the answer.
  
Can you  clarify and give a use case / topology case.

Best regards

JJacques


-----Message d'origine-----
De : DiME [mailto:dime-bounces@ietf.org] De la part de Steve Donovan Envoyé : vendredi 5 septembre 2014 16:16 À : dime@ietf.org; draft-ietf-dime-ovli@tools.ietf.org; maria.cruz.bartolome@ericsson.com Objet : Re: [Dime] [dime] #69 (draft-ietf-dime-ovli): Report Type - Realm, with absent Destination-Host

I agree.

On 9/5/14, 2:40 AM, dime issue tracker wrote:
> #69: Report Type - Realm, with absent Destination-Host
>
>   In clause 6.6, host report was updated to add:
>
>   ... or 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.
>
>   but this clarification needs to be included as well for realm report.
>
>   Original text:
>
>      1  A realm report.  The overload treatment should apply to requests
>         for which all of the following conditions are true:
>
>         The Destination-Host AVP is absent in the request.
>
>         ...
>
>   Proposed text:
>
>      1  A realm report.  The overload treatment should apply to requests
>         for which all of the following conditions are true:
>
>         The Destination-Host AVP is absent in the request and the the value
>   of peer identity associated with the connection used to send the request
>   does not match the value of the Origin-Host AVP of the received message
>   that contained the OC-OLR AVP.
>

_______________________________________________
DiME mailing list
DiME@ietf.org
https://www.ietf.org/mailman/listinfo/dime