Re: [Dime] New I-D Submitted: draft-bertz-dime-predictunits

Yuval Lifshitz <> Thu, 21 July 2016 22:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9323D12D7DE for <>; Thu, 21 Jul 2016 15:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.206
X-Spam-Status: No, score=-3.206 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RHy3kfzkgycE for <>; Thu, 21 Jul 2016 15:20:37 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6CF8C12D7D8 for <>; Thu, 21 Jul 2016 15:20:37 -0700 (PDT)
Received: from ([fe80::68ac:f071:19ff:3455]) by ([::1]) with mapi id 14.03.0294.000; Thu, 21 Jul 2016 18:20:36 -0400
From: Yuval Lifshitz <>
To: "Bertz, Lyle T [CTO]" <>, "" <>
Thread-Topic: New I-D Submitted: draft-bertz-dime-predictunits
Thread-Index: AdHXpgQdMKqoCHiaRIyWNoRHauEl3gLuMLEwAAClcYMADyWvEA==
Date: Thu, 21 Jul 2016 22:20:35 +0000
Message-ID: <>
References: <>, <> <>
In-Reply-To: <>
Accept-Language: en-CA, en-US
Content-Language: en-US
x-originating-ip: []
x-c2processedorg: b2f06e69-072f-40ee-90c5-80a34e700794
Content-Type: multipart/alternative; boundary="_000_C43C255C7106314F8D13D03FA20CFE4930CAA2F9wtlexchp2sandvi_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Dime] New I-D Submitted: draft-bertz-dime-predictunits
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: Thu, 21 Jul 2016 22:20:40 -0000

Thanks for clarifying.
The load on the client (at least in clients I know) is measured with: # concurrent subscribers, # concurrent flows, bits/sec, packets/sec.
I assume that the server could estimate (based on past experience) the above, but as you mentioned below, they are all time based. Even # concurrent flows is driven by time, as we are not interested in the total amount of lows the user had, but only how many it had at the same time.
In addition, don't think that the server could be estimating the cpu impact on the client.

From: Bertz, Lyle T [CTO] []
Sent: Thursday, July 21, 2016 5:11 PM
To: Yuval Lifshitz
Subject: Re: New I-D Submitted: draft-bertz-dime-predictunits


Sends units back to the client like a G-S-U or U-S-U so that it can get an estimate of load.  However, I would suspect it will send back multiple values representing different dimensions (the *[AVP] cop out).   One thing I struggled with and have asked some for advice on is whether it should be given a time range and respond from Server to Client as a list?

e.g. [ uses X Mbps, Y% CPU, 3K packets from T1 to T2 ], [ uses A Mbps, B% CPU, C packets from T2 to T3 ]

it definitely needs improvement

From: Yuval Lifshitz <<>>
Sent: Thursday, July 21, 2016 9:48 AM
To: Bertz, Lyle T [CTO]
Cc: Yuval Lifshitz
Subject: RE: New I-D Submitted: draft-bertz-dime-predictunits

I really don't understand this one. How is load translated to bytes, time etc? How would the server know how much the user is going to consume?
In general would be good to understand the usecase behind.

From: DiME [] On Behalf Of Bertz, Lyle T [CTO]
Sent: Wednesday, July 06, 2016 6:56 PM
Subject: [Dime] New I-D Submitted: draft-bertz-dime-predictunits


I have uploaded a new I-D for consideration.  It permits a Diameter Client, upon authorization for Service usage, to receive a prediction (estimation) of the unit load.  This is intended to assist Clients in estimating load of authorized usage.

Thank you.


Learn more on how to switch to Sprint and save 50% on most Verizon, AT&T or T-Mobile rates. See<> for details.

This e-mail may contain Sprint proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.