Re: [Dime] Issue#35 conclusion

<lionel.morand@orange.com> Thu, 06 March 2014 08:11 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 9FAF31A012E for <dime@ietfa.amsl.com>; Thu, 6 Mar 2014 00:11:55 -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 Uu1HmeOPp_8u for <dime@ietfa.amsl.com>; Thu, 6 Mar 2014 00:11:52 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by ietfa.amsl.com (Postfix) with ESMTP id 3DDD41A0131 for <dime@ietf.org>; Thu, 6 Mar 2014 00:11:51 -0800 (PST)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda11.si.francetelecom.fr (ESMTP service) with ESMTP id 6FA3C1B8269; Thu, 6 Mar 2014 09:11:46 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.183]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 1FD9D384084; Thu, 6 Mar 2014 09:11:46 +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; Thu, 6 Mar 2014 09:11:45 +0100
From: lionel.morand@orange.com
To: Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com>, "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] Issue#35 conclusion
Thread-Index: Ac8uORl1kE6lHJqaEUSwRUSn1ZjUWwATUamAABiWF1AACvi8gACOgNbAAAHYfYAAAac4cAAA5h9wAABcWDAAAG750P//+8MAgAAelYCAACgCgIAABcUAgAAC24CAAAHxAIAAB4sAgADmaQD//ugSYIACz7WAgAHjQYCAABptAIAAKB6A//41l0CACoSUgP//gt7QAD7NCQD//+z8YA==
Date: Thu, 06 Mar 2014 08:11:45 +0000
Message-ID: <1387_1394093506_53182DC2_1387_1629_1_6B7134B31289DC4FAF731D844122B36E4E56A7@PEXCVZYM13.corporate.adroot.infra.ftgroup>
References: <5BCBA1FC2B7F0B4C9D935572D9000668151B3F63@DEMUMBX014.nsn-intra.net> <530B6B9D.6010601@usdonovans.com> <087A34937E64E74E848732CFF8354B9209784B4E@ESESSMB101.ericsson.se> <087A34937E64E74E848732CFF8354B9209784B72@ESESSMB101.ericsson.se> <530B9469.4070403@usdonovans.com> <16141_1393268235_530B960B_16141_14014_1_6B7134B31289DC4FAF731D844122B36E4BC596@PEXCVZYM13.corporate.adroot.infra.ftgroup> <530B9C5E.90800@usdonovans.com> <087A34937E64E74E848732CFF8354B9209784EA0@ESESSMB101.ericsson.se> <E194C2E18676714DACA9C3A2516265D20266B9E6@FR712WXCHMBA12.zeu.alcatel-lucent.com> <5BCBA1FC2B7F0B4C9D935572D9000668151B4999@DEMUMBX014.nsn-intra.net> <087A34937E64E74E848732CFF8354B9209787161@ESESSMB101.ericsson.se> <5BCBA1FC2B7F0B4C9D935572D9000668151B4CE2@DEMUMBX014.nsn-intra.net> <530F9BC3.1010003@usdonovans.com> <E194C2E18676714DACA9C3A2516265D20266D671@FR712WXCHMBA12.zeu.alcatel-lucent.com> <5316EDEB.9080606@usdonovans.com> <E194C2E18676714DACA9C3A2516265D20266DE20@FR712WXCHMBA12.zeu.alcatel-lucent.com> <087A34937E64E74E848732CFF8354B9209789FEE@ESESSMB101.ericsson.se>
In-Reply-To: <087A34937E64E74E848732CFF8354B9209789FEE@ESESSMB101.ericsson.se>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.197.38.6]
Content-Type: multipart/alternative; boundary="_000_6B7134B31289DC4FAF731D844122B36E4E56A7PEXCVZYM13corpora_"
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/M9GHczOV_34H_CQpVM7i2l9eX_M
Subject: Re: [Dime] Issue#35 conclusion
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: Thu, 06 Mar 2014 08:11:55 -0000

I agree on the approach proposed below.

About the "any change to the actual draft", I think that draft needs anyway to reflect this clarification on the agent behavior :)

Lionel

De : DiME [mailto:dime-bounces@ietf.org] De la part de Maria Cruz Bartolome
Envoyé : jeudi 6 mars 2014 08:57
À : dime@ietf.org
Objet : Re: [Dime] Issue#35 conclusion

Dear all,

This mail thread started proposing new OLR reports to request reduction for one specific client.
However, the discussion clarified that as it is the draft today, Host-report is sent from a reporting node towards the client from where it receives the request. Then, reduction is requested per client in all cases already.
There is one special case here, when the agent is acting on behalf of the client (i.e. for a non-supporting client or for an agent SFE with topology hiding). In this case, the reporting node sends host-report to agent. Here we have two options:


a)      We expect the agent to apply the host-report received in an answer to specifically the client that sent the corresponding request

This requires some extra complexity at agent side.

But here we have one more option: allow the reporting node to choose whether it prefers to apply this host-report to "all-client" vs "one-client". That increases again the complexity (at reporting node, protocol-wise, and at agent).



b)      We expect the agent to apply this host-report to any client that is sending a request towards this agent

In my opinion, this is the best approach, it reduces complexity and increases robustness.

Therefore, I will be in favor of option b), which does not require any changes to the actual draft.

Let me know your opinions.
Best regards
/MCruz


_________________________________________________________________________________________________________________________

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.