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