[Dime] DOIC Section 5.5.2 Diameter application

"TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <jean-jacques.trottin@alcatel-lucent.com> Tue, 17 December 2013 08:54 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 425A21AE134 for <dime@ietfa.amsl.com>; Tue, 17 Dec 2013 00:54:44 -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 rRlbljUEJsiq for <dime@ietfa.amsl.com>; Tue, 17 Dec 2013 00:54:42 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 8F83B1AE12C for <dime@ietf.org>; Tue, 17 Dec 2013 00:54:42 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id rBH8scl9027388 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <dime@ietf.org>; Tue, 17 Dec 2013 02:54:39 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rBH8sb6B024952 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dime@ietf.org>; Tue, 17 Dec 2013 09:54:37 +0100
Received: from FR712WXCHMBA12.zeu.alcatel-lucent.com ([169.254.8.241]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Tue, 17 Dec 2013 09:54:37 +0100
From: "TROTTIN, JEAN-JACQUES (JEAN-JACQUES)" <jean-jacques.trottin@alcatel-lucent.com>
To: "dime@ietf.org list" <dime@ietf.org>
Thread-Topic: DOIC Section 5.5.2 Diameter application
Thread-Index: AQHO+wWdMUNdyIGkS0C4YandtgshKQ==
Date: Tue, 17 Dec 2013 08:54:36 +0000
Message-ID: <E194C2E18676714DACA9C3A2516265D201CB5BC9@FR712WXCHMBA12.zeu.alcatel-lucent.com>
References: <7921F977B17D5B49B8DCC955A339D2F02ACC8A68@US70UWXCHMBA05.zam.alcatel-lucent.com> <E194C2E18676714DACA9C3A2516265D201CB5B9A@FR712WXCHMBA12.zeu.alcatel-lucent.com>
In-Reply-To: <E194C2E18676714DACA9C3A2516265D201CB5B9A@FR712WXCHMBA12.zeu.alcatel-lucent.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_E194C2E18676714DACA9C3A2516265D201CB5BC9FR712WXCHMBA12z_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: [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 08:54:44 -0000

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