Re: [Dime] DOIC Section 5.5.2 Diameter application

Jouni <jouni.nospam@gmail.com> Tue, 17 December 2013 09:53 UTC

Return-Path: <jouni.nospam@gmail.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 9308F1ADFD1 for <dime@ietfa.amsl.com>; Tue, 17 Dec 2013 01:53:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 jewIJfmM0Oi7 for <dime@ietfa.amsl.com>; Tue, 17 Dec 2013 01:53:52 -0800 (PST)
Received: from mail-bk0-x235.google.com (mail-bk0-x235.google.com [IPv6:2a00:1450:4008:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id C432E1ADFB2 for <dime@ietf.org>; Tue, 17 Dec 2013 01:53:51 -0800 (PST)
Received: by mail-bk0-f53.google.com with SMTP id na10so2711157bkb.40 for <dime@ietf.org>; Tue, 17 Dec 2013 01:53:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QoyPpF+0N9Zpl31zWKSvUMIOg5NJ5WgWWTZpeQvLubk=; b=luK/Pj9mkuoCvikLNq6zLqJBKfkm/h+aEhnk70Nu544rbmBe0pGa/i9MUC3TZq49+n lfHWplxi/Jd/y6pDQaASZRhPtMnnS5AmPYs/AE23gQbcK6jR/yCP5LjyVDSE975lXtKE gLaPcs2SgEzG4GoaQaWJXJv7X8RV3BEnoVchTs71ewL5BIB+Wr2qECz0BtMFGK2rQb2W nAE7Td3m/rZKlZj60DHiVayibMFgU0K61tHgru+vLt6CCXDqFj5kitii9++8p/cvkVz0 ITIAuz7nlUPvxkVu1XK1ywJtkBv1LvqTBZDIoQR7mVp/k8KHbrd+Gw9y+VTPAitB7Don 7blw==
X-Received: by 10.204.171.15 with SMTP id f15mr302226bkz.116.1387274030279; Tue, 17 Dec 2013 01:53:50 -0800 (PST)
Received: from ?IPv6:2001:1bc8:101:f101:8d49:90a9:b3bb:5ae9? ([2001:1bc8:101:f101:8d49:90a9:b3bb:5ae9]) by mx.google.com with ESMTPSA id bf8sm13023276bkb.14.2013.12.17.01.53.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Dec 2013 01:53:47 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Jouni <jouni.nospam@gmail.com>
In-Reply-To: <E194C2E18676714DACA9C3A2516265D201CB5BC9@FR712WXCHMBA12.zeu.alcatel-lucent.com>
Date: Tue, 17 Dec 2013 11:53:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C49E6F9-37B4-4DC8-B9AD-D074E4B36100@gmail.com>
References: <7921F977B17D5B49B8DCC955A339D2F02ACC8A68@US70UWXCHMBA05.zam.alcatel-lucent.com> <E194C2E18676714DACA9C3A2516265D201CB5B9A@FR712WXCHMBA12.zeu.alcatel-lucent.com> <E194C2E18676714DACA9C3A2516265D201CB5BC9@FR712WXCHMBA12.zeu.alcatel-lucent.com>
To: "TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <jean-jacques.trottin@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1283)
Cc: "dime@ietf.org list" <dime@ietf.org>
Subject: Re: [Dime] DOIC Section 5.5.2 Diameter application
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, 17 Dec 2013 09:53:53 -0000

Good point. Will clarify.

On Dec 17, 2013, at 10:54 AM, TROTTIN, JEAN-JACQUES (JEAN-JACQUES) wrote:

>  
> In 5.5.2 Reacting nodes consideration., it is well mentioned that the OLR applies to the Host identified by Origin-Host AVP or the  Realm identified by Origin-Realm AVP., but nothing is said about the Diameter Application identified  by the Application ID, so I propose, to add the following paragraph in 5.5.2 :
>  
> The reacting node learns the Diameter application to which the overload report applies from the Application-ID of the answer message containing the OC-OLR AVP.
>  
> This paragraph  can be inserted just before the hereafter  existing paragraph
>    From the OC-Report-Type AVP the reacting node learns whether the
>    overload condition report concerns a specific host (as identified by
>    the Origin-Host AVP of the answer message containing the OC-OLR AVP)
>    or the entire realm (as identified by the Origin-Realm AVP of the
>    answer message containing the OC-OLR AVP). 
>  
>  
> Best regards
>  
> JJacques
>  
>  
>  
> _______________________________________________
> DiME mailing list
> DiME@ietf.org
> https://www.ietf.org/mailman/listinfo/dime