IETF Logo Mail Archive

Re: [Dime] [dime] #34: Semantics of OC-Report-Type AVP

"TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <jean-jacques.trottin@alcatel-lucent.com> Mon, 17 February 2014 17:53 UTC

Return-Path: <jean-jacques.trottin@alcatel-lucent.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 E05E41A0527 for <dime@ietfa.amsl.com>; Mon, 17 Feb 2014 09:53:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] 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 IUmjDUORaO5L for <dime@ietfa.amsl.com>; Mon, 17 Feb 2014 09:53:20 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 55C771A051E for <dime@ietf.org>; Mon, 17 Feb 2014 09:53:20 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s1HHrGva015833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <dime@ietf.org>; Mon, 17 Feb 2014 11:53:17 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s1HHrFcq018829 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dime@ietf.org>; Mon, 17 Feb 2014 18:53:15 +0100
Received: from FR712WXCHMBA12.zeu.alcatel-lucent.com ([169.254.8.164]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Mon, 17 Feb 2014 18:53:15 +0100
From: "TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <jean-jacques.trottin@alcatel-lucent.com>
To: "dime@ietf.org" <dime@ietf.org>
Thread-Topic: [Dime] [dime] #34: Semantics of OC-Report-Type AVP
Thread-Index: AQHPIcx34wrZRRvx1EKFdFq4TjstmpqmsICAgAAE6ICAABUugIACvZWAgAAwCoCAADL/AIAEjBxA///7RACAABhCgIABTnoAgAACQICAADisgIAADXYAgAAEyICAAAGagIAAZP8wgAAbz4CAAnLKgIACNiuAgARQJICAACoWIA==
Date: Mon, 17 Feb 2014 17:53:14 +0000
Message-ID: <E194C2E18676714DACA9C3A2516265D2026697DE@FR712WXCHMBA12.zeu.alcatel-lucent.com>
References: <066.b54c2f5aeb31c9b3f88c96008120290d@trac.tools.ietf.org> <E194C2E18676714DACA9C3A2516265D202663C4A@FR712WXCHMBA11.zeu.alcatel-lucent.com> <087A34937E64E74E848732CFF8354B9209772EF4@ESESSMB101.ericsson.se> <19874_1392116210_52FA01F2_19874_3990_1_6B7134B31289DC4FAF731D844122B36E499C4E@PEXCVZYM13.corporate.adroot.infra.ftgroup> <087A34937E64E74E848732CFF8354B9209773085@ESESSMB101.ericsson.se> <52FA3CC6.905020 5@usdonovans.com> <17910_1392132298_52FA40CA_17910_2863_1_6B7134B31289DC4FAF731D844122B36E49A28D@PEXCVZYM13.corporate.adroot.infra.ftgroup> <11546_1392132645_52FA4225_11546_3173_1_0aa80fb0-8382-459e-aebf-2ee5d5f70edc@PEXCVZYH02.corporate.adroot.infra.ftgroup> <E194C2E18676714DACA9C3A2516265D2026644D6@FR712WXCHMBA11.zeu.alcatel-lucent.com> <D2D4DD91-8F3D-4C24-9E3A-E2AE3918D468@gmail.com> <52FCBBF7.7000700@usdonovans.com> <D4BE67F7-6D7B-4DB2-8DF0-D430A8FC6582@nostrum.com> <5302351F.6050902@usdonovans.com>
In-Reply-To: <5302351F.6050902@usdonovans.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: multipart/alternative; boundary="_000_E194C2E18676714DACA9C3A2516265D2026697DEFR712WXCHMBA12z_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dime/Cnf-HYXNg5VGR5Izn06yISQyB8g
Subject: Re: [Dime] [dime] #34: Semantics of OC-Report-Type AVP
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: Mon, 17 Feb 2014 17:53:23 -0000

Hi

I share the view to analyze the overload of the realm as a whole in a separate extension  and see if this lead to another report type.

Best regards

JJacques


De : DiME [mailto:dime-bounces@ietf.org] De la part de Steve Donovan
Envoyé : lundi 17 février 2014 17:13
À : Ben Campbell
Cc : dime@ietf.org list
Objet : Re: [Dime] [dime] #34: Semantics of OC-Report-Type AVP

I do think it would be a new report type, as it would require different behavior from reacting nodes.

I'm ok with this being in a separate extension if the group thinks this is the correct approach.  We are creating a good number of relatively small extensions.  It might lead to the need to pull them all together in a future version of the DOIC draft/RFC.

Steve
On 2/14/14 4:21 PM, Ben Campbell wrote:

(Apologies for coming late to this thread)



On Feb 13, 2014, at 6:35 AM, Steve Donovan <srdonovan@usdonovans.com><mailto:srdonovan@usdonovans.com> wrote:



Ok, Ok, no reason to gang up on me. :-)

What we have here is an overload report to reduce realm routed requests.  I think we should be explicit in the draft to define it as such.





At the risk of joining the anti-Steve gang, I feel the need to belatedly mention that my personal intent way back when we talked about the mixed-state problem was that realm reports applied to realm-routed requests.



I am still concerned that we do not have a way to indicate overload of the realm as a whole.  I'll enter a new trouble ticket to capture this issue.





I do not object to adding that ability. Would it be a new OLR type? If so, would it need to go in the base draft or could it be an extension?



Steve

v2.23.0 | Report a Bug | By Email