Re: [Dime] Mirja Kühlewind's Discuss on draft-ietf-dime-drmp-05: (with DISCUSS and COMMENT)

Alexe Melnikov <> Wed, 11 May 2016 17:11 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1CC1512B01F for <>; Wed, 11 May 2016 10:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Status: No, score=-2.72 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key) header.b=ThrGrASp; dkim=pass (1024-bit key) header.b=X6DmfpvR
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tuuQ5fs8zT3m for <>; Wed, 11 May 2016 10:11:41 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id ADE0312B03F for <>; Wed, 11 May 2016 10:11:40 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal []) by mailout.nyi.internal (Postfix) with ESMTP id 20B0521069 for <>; Wed, 11 May 2016 13:05:47 -0400 (EDT)
Received: from frontend2 ([]) by compute3.internal (MEProxy); Wed, 11 May 2016 13:05:47 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=8T8o514658riwxaaQAXp8H+G5uw=; b=ThrGrA SpH+8uSsNGecYdoSrTRI5L2l0X1baaDN73ExABD3YPaR8EU2aHRTClORSYUY2vhY gqG6xYPAxR683TDH0Hy5MZnwKrj0lGw1pjP24N5Jp0g0zn4lErefeNv8oqXaa+hi y2JxJdawEQal4bL6fLTOO/RgfGOQq16z2ZdRc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=8T8o514658riwxa aQAXp8H+G5uw=; b=X6DmfpvR9GoQPQUbJI2LswUi51xFjY93Vx/M/50Y+RZqNi6 ZBCyuxtMLU9J1pqUINn/TWrXZqMpEF+LKbucDmLfKmvTCqLSxonrZe14HcuSjDme NVSjUzMz4q3nVpjOMVRoo/6hl2pA33DMixpecKISwe58sGbJlx5T0vtDgbHI=
X-Sasl-enc: nxb1D0O4FYxde5idrHX9hkCi/l4E6fO0Zclp7FMoTDpB 1462986346
Received: from [] ( []) by (Postfix) with ESMTPA id B93B168026B; Wed, 11 May 2016 13:05:46 -0400 (EDT)
Content-Type: text/plain; charset="windows-1251"
Mime-Version: 1.0 (1.0)
From: Alexe Melnikov <>
X-Mailer: iPad Mail (13E238)
In-Reply-To: <>
Date: Wed, 11 May 2016 13:13:47 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <>
To: "Mirja Kuehlewind (IETF)" <>
Archived-At: <>
Cc:,,, The IESG <>
Subject: Re: [Dime] Mirja Kühlewind's Discuss on draft-ietf-dime-drmp-05: (with DISCUSS and COMMENT)
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: Wed, 11 May 2016 17:11:47 -0000

Hi Mirja,

> On 11 May 2016, at 07:07, Mirja Kuehlewind (IETF) <> wrote:
> Okay let me go for an example here and see if that can be a use case that we are talking about.

Yes, this is helpful.
> You have a system where some clients run a communication service for emergency doctors as well as for firefighters and then there are also ‚normal‘ users that run some kind of communication service.
> Now you actually have an emergency: some part of the system is down and the number of request is high such that the system is overloaded.
> Both the emergency doctors have would have two different priority classes, one for important message about instruction (what and where people should do something) and one for communication between the doctors/firefighters which has still higher priority than any other communication of the other people (as you assume doctors and firefighters are more responsible to not misuse this communication channel).
> Now only the emergency doctors communication service was upgraded to use this extension, but the firefighter’s administrations is just too slow or they currently have not enough money because they have specialized expensive hardware and software that is not easy to change.

"Doctor, it hurts when I do that..." - "Don't do that!"

I don't think this would be a common deployment case.

I agree that there is an issue in the scenario you specified. Default priority helps with a single application + normal (unupgraded) traffic. I do think it helps with the most common case. So instead of having lots of SHOULDs and MAYs, I suggest we add text describing possible issues and when multiple DIAMETER applications are deployed we either recommend that all clients are upgraded to support this extension at the same time or at least deployments specify compatible policies for different applications.

I can suggest some text.

> Is it okay in this situation that the private chat of two doctors about their last ski-holidays starves requests to access the network to send instructor message to the firefighters?

We can't prevent all problems like this, as the above is really a social problem combined with misconfiguration. But we can warn about it.
> (And how do i make sure that that all other other requests actually select a lower priority than 10…? But that’s a different question…)
> Mirja
>> Am 11.05.2016 um 06:59 schrieb Alexey Melnikov <>:
>> Hi Mirja,
>> On 10 May 2016, at 17:59, Mirja Kuehlewind (IETF) <> wrote:
>>>>> I don’t think it is a good idea to assign a default priority to non-priority-defined requests at all. If you have high priority traffic that does not support this extension (yet) this traffic could be starved by lower priority traffic when assigning a middle range priority. I don’t think that is what you want to achieve.
>>>> SRD> Actually, this is what we want to achieve.  It is an requirement that messages explicitly marked as high priority get treated even if it results in starving lower priority messages.  The starving of lower priority messages is not an problem, it is a requirement.
>>> I think we are still talking past each other.
>> Most definitely :-).
>>> If you explicitly assign a priority, starvation might be okay. However, if you don’t have a priority explicitly signaled, the transaction might have a very high priority
>> So some agent in the system needs to decide that a transaction is important.
>>> but you just don’t know and by assigning a random mid-range priority this important request could get starved.
>> Here I disagree with you, because the way to know that a transaction is important is to upgrade client to explicitly assign high priority to it. So default priority is a backward compatibility mechanism, that would work for most common cases. You seem to be suggesting that when this extension is deployed all clients need to be updated at the same time. This is not realistic.