Re: [Dime] Issue #23 Proposed resolution

Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com> Tue, 25 February 2014 09:04 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 AE3A21A0649 for <dime@ietfa.amsl.com>; Tue, 25 Feb 2014 01:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.239
X-Spam-Level:
X-Spam-Status: No, score=-1.239 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 mE6uu6QS-MmE for <dime@ietfa.amsl.com>; Tue, 25 Feb 2014 01:04:48 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id E0ED61A033F for <dime@ietf.org>; Tue, 25 Feb 2014 01:04:47 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-f4-530c5cae1648
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 7B.6E.04853.EAC5C035; Tue, 25 Feb 2014 10:04:46 +0100 (CET)
Received: from ESESSMB101.ericsson.se ([169.254.1.28]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.02.0387.000; Tue, 25 Feb 2014 10:04:45 +0100
From: Maria Cruz Bartolome <maria.cruz.bartolome@ericsson.com>
To: "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] Issue #23 Proposed resolution
Thread-Index: AQHPMYgSECydxGIpskK7qjdEofxvM5rExTAw///3QwCAAO+3EA==
Date: Tue, 25 Feb 2014 09:04:44 +0000
Message-ID: <087A34937E64E74E848732CFF8354B9209784E89@ESESSMB101.ericsson.se>
References: <530B84F8.5030006@usdonovans.com> <087A34937E64E74E848732CFF8354B9209784BED@ESESSMB101.ericsson.se> <530B9FF4.4070108@usdonovans.com>
In-Reply-To: <530B9FF4.4070108@usdonovans.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_087A34937E64E74E848732CFF8354B9209784E89ESESSMB101erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrALMWRmVeSWpSXmKPExsUyM+Jvje66GJ5gg0WfFS3m9q5gc2D0WLLk J1MAYxSXTUpqTmZZapG+XQJXxqHmFYwFl1IqHj95zdjAeCWsi5GTQ0LARGLBmS5mCFtM4sK9 9WxdjFwcQgInGCWWHbjGDOEsZpTYMvkSI0gVm4CdxKXTL5i6GDk4RASUJU7/cgAxhQUMJb5/ EASpEBEwkmj4MpsJwnaS6Fi6CWw+i4CqxPXD/WBxXgFfif9rnjFBjJ8KtKtrCQtIglNAT+La z042EJsR6KDvp9aANTALiEvcejKfCeJQAYkle85DHS0q8fLxP1YIW0micckTVoj6fIlP09ax QywTlDg58wnLBEaRWUhGzUJSNgtJGURcR2LB7k9sELa2xLKFr5lh7DMHHjMhiy9gZF/FKFmc Wlycm25koJebnluil1qUmVxcnJ+nV5y6iREYSwe3/DbawXhyj/0hRmkOFiVx3uusNUFCAumJ JanZqakFqUXxRaU5qcWHGJk4OKUaGP02nCpZ//P0Z5fY+j2r1hfGbby/aZ7Su/fXpeqln38y WCxvavtIW3p5Slt77u1zHMxG6p/q5+t5HL1r57neNte3fULggy3PXon/u3d8B5fn4tApz0Jz 1wWefB5p9in+s2eGxpHsty4BL1f9m5148aCC/8JDD0tnvZy394SuT4ZhxhGjXs3dj14qsRRn JBpqMRcVJwIA+v6e13MCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/RVHdcAemmqM0-F5hpo7c0x0-Jo0
Subject: Re: [Dime] Issue #23 Proposed resolution
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, 25 Feb 2014 09:04:51 -0000

Steve,

The discussion started around some proposed use cases by Ulrich, and to my knowledge that discussion is not concluded.
Then we have not agreed (at least yet) on having a differentiation between realm and realm-routed.
Even more, as far as I understand the proposal it is related to the ability (by agent) to select the a server (in a farm, providing service to a realm) for new session establishment. This is something we discussed long time ago, and at that point in time we tend to agree that it was not required, but up to different applications to decide based on realm overload.
Enhancements could be done on top of this, but first we need to agree on the basic use cases.

I hope this clarifies
Cheers
/MCruz

From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of Steve Donovan
Sent: lunes, 24 de febrero de 2014 20:40
To: dime@ietf.org
Subject: Re: [Dime] Issue #23 Proposed resolution

Maria Cruz,

I thought you had asserted that there was a 3GPP requirement to have the ability to have a realm report that control the total amount of traffic sent to a realm.  There is certainly an IETF DOC requirement to this effect.

The proposal is to have three report types (or four depending on the resolution of the per client host report discussion).

- Host report - Apply to all requests sent to a host.  The host is indicated by the origin-host AVP in the answer message carrying the report.  Can be generated by a server or by an agent acting as a front-end to a group of servers.

- Realm-routed-request report - Applies to all requests sent to a realm without a destination-host AVP in the request message.  Can be generated by a server or by an agent acting as a front-end to a group of servers.

- Realm report - Applies to all requests sent to the realm, independent of the presence or absence of a destination-host AVP in the request message.  Can be generated by a server or an agent.  The method for determining the realm state is out of scope for the DOIC document.

Steve
On 2/24/14 1:12 PM, Maria Cruz Bartolome wrote:
Hello,

I do not think we have agreed so far on the need to have two different reports (so called realm-routed and just realm).
Regards
/MCruz

From: DiME [mailto:dime-bounces@ietf.org] On Behalf Of Steve Donovan
Sent: lunes, 24 de febrero de 2014 18:44
To: dime@ietf.org<mailto:dime@ietf.org>
Subject: [Dime] Issue #23 Proposed resolution

I propose the following resolution for issue 23:



Proposal - Change the name of realm report.

Proposed name - "Realm-Routed-Request" report.

Proposal - Update all discussion on "Realm-Routed-Request" reports to indicate that they apply only to requests targeted to a realm when there is no destination-host AVP in the request.  Specifically, section 4.6 requires updating.

There is also a proposal to add a new report type to handle all transactions to a realm.  This is addressed by ticket number 55.

Regards,

Steve




_______________________________________________

DiME mailing list

DiME@ietf.org<mailto:DiME@ietf.org>

https://www.ietf.org/mailman/listinfo/dime