Re: [Dime] Use of SourceID AVP in Agent Overload and Load control drafts

Maria Cruz Bartolome <> Fri, 06 May 2016 10:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CECF312D954 for <>; Fri, 6 May 2016 03:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1Z9CNFxl9wf2 for <>; Fri, 6 May 2016 03:14:37 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 28C1912D955 for <>; Fri, 6 May 2016 03:14:36 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-cd-572c6e8b3886
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id F6.5C.27088.B8E6C275; Fri, 6 May 2016 12:14:35 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0248.002; Fri, 6 May 2016 12:14:34 +0200
From: Maria Cruz Bartolome <>
To: "" <>, "" <>
Thread-Topic: Use of SourceID AVP in Agent Overload and Load control drafts
Thread-Index: AdGcl068okSqgAUnQBa17vO+IzGcqwK6A60w
Date: Fri, 06 May 2016 10:14:34 +0000
Message-ID: <>
References: <20257_1461331744_571A2720_20257_12979_1_6B7134B31289DC4FAF731D844122B36E01E43A7C@OPEXCLILM43.corporate.adroot.infra.ftgroup>
In-Reply-To: <20257_1461331744_571A2720_20257_12979_1_6B7134B31289DC4FAF731D844122B36E01E43A7C@OPEXCLILM43.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRmVeSWpSXmKPExsUyM2K7nG53nk64wfmVEhZze1ewWdzenunA 5LFkyU8mj5ZnJ9kCmKK4bFJSczLLUov07RK4MhZ2TWcqWCpXsXL+V9YGxq0SXYycHBICJhLT nu9lhbDFJC7cW8/WxcjFISRwhFHi26/PUM5iIKfrPFgVm4CdxKXTL5hAbBGBGIlZ598yg9jC Al4SXS8XQ8W9JbqmHmCFsI0kNrY2MILYLAIqEqcmt7KB2LwCvhLtk5ewQizoZJQ4se09mMMp 0MUocavnNVgHI9BN30+tAZvKLCAucevJfCaIWwUkluw5zwxhi0q8fPwPqJkDyFaSmLY1DaJc R2LB7k9sELa2xLKFr5khFgtKnJz5hGUCo+gsJFNnIWmZhaRlFpKWBYwsqxhFi1OLk3LTjYz0 Uosyk4uL8/P08lJLNjECI+Xglt8GOxhfPnc8xCjAwajEw7vgl3a4EGtiWXFl7iFGCQ5mJRFe xiydcCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8/i8Vw4UE0hNLUrNTUwtSi2CyTBycUg2M3lzz 5Zm0onZGJxnHCgnP9jk+fWFaeKy9W07qn3nWvIv+bOXriLo8Y8pfzu9fPbesvhXJePSIpfHn n5E667IrLx5KEH16frL07PrA0Iq9vsvXfp3wU8J7g9bjK6snHPVof6R57uH1NwuiTkaY97vO 22a5qLJF9brwW/ezLKK9m+QCc6dPyNfapsRSnJFoqMVcVJwIAFZf86qQAgAA
Archived-At: <>
Subject: Re: [Dime] Use of SourceID AVP in Agent Overload and Load control drafts
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 06 May 2016 10:14:40 -0000

Hello Lionel, all,

I think there is not a need to define two AVPs, when in fact the purpose of the AVP in both case is the same, i.e. identify the Diameter node that inserts this AVP. Then, that diameter node is considered as the source of the Load information (if inserted in Load AVP) or the Overload Information (if inserted in OC-OLR AVP).

If the problem you want to solve is the dependency of one draft to another, I will propose to simply progress first the one that we consider is more relevant, according to last emails it seems that Load is progressing faster, then we can simply have the definition of the SourceID AVP in the Load draft. Then, this definition should be generic enough, to allow a direct applicability to Agent Overload draft.

Would that work for you?
Best regards

-----Original Message-----
From: DiME [] On Behalf Of
Sent: viernes, 22 de abril de 2016 15:29
Subject: [Dime] Use of SourceID AVP in Agent Overload and Load control drafts


At the last IETF meeting, we have discussed the interdependence between the load control and the Agent Overload draft regarding the use of the SourceID AVP.

First of all, there is some inconsistency in the agent overload draft. The AVP is sometimes named OC-SourceID AVP and sometimes OC-SourcedID. This needs to be fixed.

Now, if we look at the definition of the OC-SourceID in the agent overload draft , we find:

6.3.  OC-SourceID

   The [OC-]SourceID AVP (AVP code TBD2) is of type DiameterIdentity and is
   inserted by the DOIC node that either indicates support for this
   feature (in the OC-Supported-Features AVP) or that generates an OC-
   OLR AVP with a report type of peer.

   It contains the Diameter Identity of the inserting node.  This is
   used by other DOIC nodes to determine if the a peer indicated support
   this feature or inserted the peer report.

This definition is interesting and should be kept from my point of view. I think that having an AVP identifying the source of DOIC node is a good point and this should remain.
I would be then in favor to define two separate AVPs, one identifying a OC source, another identifying a Load source.
I propose to keep "OC-SourceID" for the first one and "Load-SourceID" for the second one.

Additional advantage: if this approach is agreed, there is no need to link both drafts anymore.

Does it sound acceptable?

I will initiate issues aligned with this proposal. According to the conclusion of this discussion, they can be accepted or rejected later.




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.

DiME mailing list